For those of you who are new to the Adobe Digital Enterprise Platform (ADEP), the short (but concise) 10 minute video below is a MUST watch, for an introduction to the platform.
Watch out for the ADEP Developers Channel on YouTube for more…
Original article at http://blogs.adobe.com/saket/adep-10-minute-intro/.
While the out-of-the-box experience of the Manage Assets interface will blow you away, it is worth noting that the interface itself is highly configurable, given that deployments of the Correspondence Management solution may need a different/customized look-n-feel of this interface, based on specific customer requirements.
To know more about the customization, read the complete post here.
The campaign is the highest layer in the Integrated Content Review object hierarchy. The project is the second layer in the object hierarchy and the asset is the third layer. In fact, an asset is the basic unit of work — a work item — in the Integrated Content Review workflow.
Multiple levels of project nesting are supported.
Assets are actively managed through review cycles and drive all statuses in the campaign. For example, if an asset is late, the status of the parent campaign automatically becomes red. If all the constituent assets of a campaign are on time or green, the status of the campaign is green. Therefore, the status of a campaign is derived bottom-up instead of top-down.
Team member inheritance
Teams are built in a bottom-up fashion. Team members at any level in the campaign hierarchy include team members from lower levels. In other words, a campaign includes all members of a project. A project, in turn, includes all members of the assets within it.
Additionally, at any level in the campaign, a new member can be added directly to the team list. These new members have no responsibilities towards the campaign, but they receive notifications when statuses change. They also get access to the solution interface so that they can proactively see how the campaign is progressing.
For background information, you can refer to the Integrated Content Review Solution Guide.
Original article at http://blogs.adobe.com/samartha/2011/09/project-and-team-hierarchy-in-icr.html.
Ok, this is going to be a short one…
While building custom OSGi bundles or components over the Adobe Digital Enterprise Platform (which contains the Apache Felix OSGi container) or any other OSGi container for that matter, you may often come across a need to access and hence introduce OSGi bundles of other enterprise thirdparty libraries within the container.
A common way to achieve this is to create a wrapper bundle for these libraries using the BND tool. However, thanks to SpringSource, we already have the OSGi-ready versions of hundreds of open source enterprise libraries that are commonly used/needed, hosted for public use. So, you can easily search for the library you are looking for here, before creating one on your own (in case the one you are looking for does not exist – which should be quite rare).
Original article at http://blogs.adobe.com/saket/osgified-libraries/.
These are not simply sequential, but rather a continuum of phases existing within the context of CX.CX is not something you just bolt on to your existing enterprise architecture.
With social media, bad CX stories can escalate virally and ruin the reputation of a business in weeks or even days. People notice BAD experiences and get emotional! They want a good customer experience.
Original article at http://technoracle.blogspot.com/2011/04/what-is-customer-experience-management.html.
Solutions over ADEP have introduced the concept of an application context (aka app context), which can be seen as a unique identifier, that various server side modules use to identify the execution context (from the current execution thread) and process requests in context of that solution. For instance, when persisting content/assets onto the CRX repository, the platform’s persistence module (official known as Platform Content) uses the current (invoking) app context to determine where to store the content/assets, and what configurations to use (which would typically be different for different solutions). See snapshot below, indicating the solution specific content areas.
Note that the storage location is /content/apps/cm for Correspondence Management, and /content/apps/icr for Integrated Content Review, which happen to be the app contexts for the two solutions.
Since it is essential for the server to identify the execution context, if you do not set or establish the application context before you make calls to the solution APIs, you will encounter a server error that says : “Unable to fetch application context“. To set the app context, use one of the two methods:
App context in your Flex application
If you are invoking a solution API from a flex application, ensure that you set the app context using:
var appToken:AsyncToken = com.adobe.ep.ux.content.services.search.lccontent.LCCQueryServiceFactory.getInstance().setAppContextService("/content/apps/cm"); // setting app context for the CM solution
appToken.addResponder(new mx.rpc.Responder(<your success handler>, <your fault handler>));
App context in your Java application
If you are invoking a solution API from a java based application, ensure that you set the app context using:
com.adobe.livecycle.content.appcontext.AppContextManager.setCurrentAppContext("/content/apps/cm"); // setting app context for the CM solution
The app context concept is also used (or rather leveraged) in other scenarios such as driving solution specific Building Block (BB) configurations. Since a Building Block is meant to be reusable across solutions, it exposes certain configurations that can be different for different solutions. Hence, the BB needs to behave differently depending upon the context in which it is being used or invoked. Below is an example where the Data Dictionary BB is used by two solutions – CM and ICR – and has configurations specific to each solution, lying within the solution’s specific app context - /apps/cm for CM and /apps/icr for ICR.
Original article at http://blogs.adobe.com/saket/solutions-and-the-application-context/.
Although you can start your ADEP Experience Server by double-clicking the Quickstart JAR file or the Windows batch file, most people will find it convenient to install the Experience Server as a Windows service. It will configure the Experience Server to start automatically when your Windows restarts and, helps you control the start and stop operations of the Experience server by using the Services control panel.
Install Experience Server as a Windows service
To install a Windows service for your Experience Server:
- Open the command line interface and navigate to the [ExperienceServer root]/opt/helpers/ directory.
- Execute the
instsrv.bat <serviceName>command to install the Experience Server as a Windows service.
Verify the installed Windows service
You can verify the installed Windows service in the Services control panel. To open the Services control panel, execute the
start services.msc command from the command line interface or select Start > Administrative Tools > Services.
Windows service operations
To start the Windows service, do one of the following:
- In the Services control panel, select the Windows service and click Start.
- In the command line interface, execute the
net start <serviceName>command.
To stop or restart the Windows service for the Experience Server, click Stop or Restart, on the Services control panel.
Uninstall the Windows service
To uninstall the Windows service, execute the
instsrv.bat -uninstall <serviceName> command on the command line interface. The Windows service gets removed from the Services control panel.
Original article at http://blogs.adobe.com/ADEPhelp/2011/09/installing-windows-service-for-adep-experience-server.html.
If you have not already got a chance to explore the various uber cool features of the all new Correspondence Management Solution 3.0, here are my top 10 ones that you should look out for…
1. With the all new Create Correspondence (aka Document Composer) UI, composing Letters was never so easy! . The new interface provides an easy, intuitive way of composing Letters. With a lot more controls available, such as indentation adjustments, new line, free text, one can design/create a Letter exactly as required.
2. Highlighting of the currently selected asset in the PDF Preview when composing a Letter. Wouldn’t it be a great composing experience if selecting an asset on the flex app. automatically takes you to the respective page, exactly where your content lies within the PDF!? …and then highlight the selected content as well as the target in which the content lies, so you don’t have to search/scroll-over for your content within the PDF. The solution now brings along this amazingly convenient experience for the users.
3. Working on multiple assets at a time. With the all new Manage Assets interface, one can now work on multiple assets (possibly, related to each other) at a time, by virtue of each asset/editor being opened in a new tab in the Editors view. Of course, you can also switch between tabs when working with multiple assets. Here’s a snapshot:
4. Content Preview is yet another amazing addition to the asset authoring experience, wherein you can hover over your asset (in all views that present a list of assets) and see a Preview of the asset content and metadata, be it Texts, Images, Lists, Conditions, etc. So, you no longer need to go back and open the asset editor to see what’s in it. Use the Preview experience to identify the desired asset!
5. Creating numbered and bulleted list content. You can now easily design numbered and bulleted content, by authoring List assets using the List Editor. You can control indentation on paragraph(s) (or even images), specify custom prefix/suffix characters, and much more…
6. The all new Rich Text Editor, that has great text formatting capabilities that includes styling such as Bold/Italic/Underline, Font controls, letter Spacing, line height, Margin controls, Alignment controls. The editor also allows creating advanced bulleted and numbered content, using the appropriate toolbar controls.
Spell Check (English) is another great feature that enhances the text authoring experience.
7. Ability to Publish assets and enhanced version management, with the ability to create different versions of an asset, view previous versions, revert back to last published version, etc. See this post for more on publishing assets.
8. Import/ Export of selective assets is now possible using CM 3.0 via the Manage Assets interface itself. One can select the assets to be exported and simply press the “Export Assets” button. The exported ZIP can then be imported on any other system, using the “Import Assets” action on the Manage Assets interface.
Import/Export of all assets is also now possible right from the Manage Assets (Admin) interface itself, with a single click of a button (rather than the cumbersome steps in Contentspace, as in ES 2.5).
9. CM 3.0 introduces the ability to author Tables (dynamic or static) within your correspondence.
Here’s the Fund Allocation table in the Welcome Kit letter (that is part of the CM sample assets).
10. The Asset Dependencies Browser is an excellent tool/interface to view the dependencies of an asset, and be able to generate a report out of the same.
Note : Users can further drill down into the related assets by double-clicking on the asset, which will then show the dependencies for that asset. One can switch back-n-forth using the breadcrumbs on the top bar.
These are just 10 key features that you just cannot afford to miss. There is a lot more to the solution, the details of which can be seen on this post.
Original article at http://blogs.adobe.com/saket/adobe-correspondence-management-solution-top-10-items-to-look-out-for/.
We are also introducing the new Adobe Digital Enterprise Platform (ADEP), which embodies multiple functionalities formerly offered by Adobe LiveCycle ES, Day Software, and more. ADEP is a bold platform, which solves a major issue emerging in modern enterprise architecture. The architectural discipline of Customer Experience Management (CEM) is important for modern enterprises to grasp and act upon. CEM is described from an architectural perspective within the blog post and video here.
ADEP offers customers many choices (such as HTML5 or SWF), which I believe is best decided on a per requirements basis. A further explanation from the Adobe website reveals some of the problems ADEP solves:
“Companies that want to differentiate themselves from the competition realize that they must deliver applications that engage customers as they access information and interact with the business and its frontline employees. And customers want access on
any device or across any channel. Central to accomplishing that goal is simple, yet engaging, interfaces that enable customers to access information and processes, even if they are contained in corporate systems. Efforts to merely extend access to such systems have not proven successful due to the complexity of user interfaces that have been designed for specialists, not customers and the frontline employees who serve them.”
The obvious enrichment a platform can deliver is a common pipeline for data and processing, designed from the bottom up with Cloud and Social Media DNA. The data modeling capabilities also offer enterprise developers some really cool new features.
Over the next few weeks we will continue to post articles to expose bits of the platform and explain what it means in terms of existing LiveCycle ES customers.
Hope to see you at Adobe MAX 2011!
Original article at http://technoracle.blogspot.com/2011/06/adobe-digital-enterprise-platform.html.
In my role I spend a lot of time talking with organizations in both Corporate and Government sectors about creating great customer experiences. In fact, understanding the challenges and opportunities for these organizations is the aspect of my role that I enjoy the most. These organizations all want to achieve great digital customer experiences…who wouldn’t? [...]
Original article at http://www.avoka.com/blog/?p=1424.