Posts tagged "ADEP"

Adobe announces release of LiveCycle Enterprise Suite 3

Adobe has announced release of Adobe® LiveCycle® Enterprise Suite 3 (ES3) software on March 13  2012. Here is the link to press release

Document and DataServices capabilities of Adobe Digital Enterprise Platform (ADEP) are not part of Adobe LiveCycle ES3

Click here to access Online help documentation for ES3 is available

A link will be provided soon with details to download a trial for those who would like to try the new features of Adobe LiveCycle.

There are lot of new features in various document services of Adobe LiveCycle ES3 and it’s Correspondence Management Solution.

 

Future of Correspondence Management Solution

We ( Correspondence Management Solution team ) are currently working hard to add numerous features that are requested by various customers in to the solution. These features will be part of next Adobe LiveCycle release and available out-of-the-box to new customers and customers on previous versions can upgrade to this version to make use of these new features

We have recently released first service pack of ADEP Document Services which is available for download at this link

Adobe has recently outlined growth strategy with increased focus on Digital Marketing and Digital Media opportunities.

To know more about future investments and priorities on Adobe LiveCycle visit Arun’s (VP & GM) blog

ADEP Solutions YouTube Channel

If you are interested in learning about new features/functionality of ADEP solutions like Correspondence Management or Integrated Content Review you can go through this YouTube Channel

 

If you are interested in getting any updates related to ADEP Solutions you can follow ADEP Solutions facebook page

 

 

 

 

 

 

Deploying CM on production server

Experience Server Solutions QuickStart provides some sample collateral and creates some sample users so that developers can directly start using the OOTB reference application and make use of samples to know about and learn the product capabilities, *but* It is highly recommended to remove these sample assets and sample users when the solution is deployed on to a production server.

 

I will take you through the steps to remove:

1)      Sample assets from the system and

  1. By uninstalling them from package manager
  2. By Removing sample assets package from SQS

2)      Sample users from the system

  1. Removing sample users from CRX user administration
  2. modifying a configuration file

 

Removing Sample assets & sample users from a production system:

There are two ways to remove the sample assets from the system one can follow any way that suits them.

Steps to remove sample assets and sample users from a running server:

1.a. Removing Sample assets by uninstalling them from package manager [Please do not start SQS as a publish instance till the step it is specified to do so]

  • Go to http://[hostname:port]/crx  (on author instance)
  • Login as admin
  • Click Package Manager
  • Click on Package with name “cm-sampleassets.zip”
  • Click More dropdown in action bar (This action bar has other actions like Edit Build etc.,. , More option is in the right most area of this bar)
  • Click Uninstall
  • Click Uninstall again on confirmation dialog
  • Wait for sometime till you see a message like “Package uninstalled in <some>ms” in the Activity Log
  • Now if you log on to CM Manage Assets UI , you will not see any sample assets. If you are still seeing them then clear your browser cache and then try.

2.a Removing sample users from CRX user administration

  • Go to http://[hostname:port]/crx (on author instance)
  • Login as admin
  • Click User Administration
    • CM creates following users OOTB
      • Todd Goldman (tgoldman)
      • Caleb Lopez (clopez)
      • Gloria Rios (grios)
      • Frank Kricfalusi (fkricfalusi)
      • Jocelyn Robinson (jrobinson)
      • Heather Douglas (hdouglas)
      • In user administration dialog , Navigate to each of these users and click Remove user , Now if you try to log on to CM Manage Assets UI with any of the above usernames , You are not allowed to login

After completing steps mentioned in 1.a & 2.a , You can start the publish instance , Follow the steps mentioned above in 2.a and remove sample users from publish instance as well.

 

Now I will take you through the steps 1.b & 2.b in order to stop creation of sample assets and sample users by making some changes in SQS jar

Steps to remove sample assets and sample users from SQS when server is down (or not even started once):

1.b Steps to stop sample assets creation

  • Open SQS jar using a zip utility
  • Navigate to <SQS jar>\static\repository\install
  • Open solution-correspondencemanagement-pkg-<version>.zip file
  • Navigate to solution-correspondencemanagement-pkg-<version>.zip\ jcr_root\etc\packages\adobe\aep\solutions
  • Select samples-correspondencemanagement-pkg-<version>.zip
  • Click Delete
  • Save the changes to jar
  • Re-open the SQS jar with any zip utility and validate that the samples-correspondencemanagement-pkg-<version>.zip is not shown in the location from where you deleted it
  • This package creates sample assets , If we delete it we can stop the creation of sample assets on production system

2.b Steps to stop creation of sample users

  • Open SQS jar using a zip utility
  • Navigate to <SQS jar>\static\repository\install
  • Open solution-correspondencemanagement-pkg-<version>.zip file
  • Navigate to solution-correspondencemanagement-pkg-<version>.zip\ jcr_root\etc\packages\adobe\aep\solutions
  • Open template-correspondencemanagement-pkg-<version>.zip
  • Navigate to template-correspondencemanagement-pkg-<version>.zip \jcr_root\apps\solutions\cm
  • Edit CMGroupsAndUsers.xml to make following changes
    • Remove the below section from xml [Remove block and lines highlighted here]

 

  • Use the modified xml in template-correspondencemanagement-pkg-<version>.zip
  • Save changes to SQS jar
  • Re-open the SQS jar with zip utility and check that the changes to CMGroupsAndUsers.xml are properly saved

Now use this SQS jar to run author and publish instances , Sample assets and sample users will not be created after these changes

 

Note:

These steps are just to give an overview, Please do not follow them as is on any production server. Contact ADEP Engineering/Support/PS before you try these on a production system so that they can provide more and in-detail steps to achieve this, which best suits your deployment topology and any other specific needs.

If double-click doesn’t work

 

With ADEP release running an Experience Server is as simple as double-clicking Solutions Quickstart

One needs to obtain a license file, copy license file and Solutions Quickstart to some folder and double-click Solutions Quickstart to get everything up and running *but* at times you may notice that Experience Server does not start [though it's not a problem with Solutions Quickstart] on double-click.

Solutions Quickstart is a jar file and it doesn’t start on double-click if some other program has hijacked the jar file extension i.e when we install JRE on Windows system the file “jar” is correctly associated with javaw.exe and if any other program like a zip utility is installed that utility modifies the association of jar file and when you double click Solution Quickstart instead of starting Experience Server it just opens up the file or does nothing.

In order to fix this problem, I suggest four ways :

  1. Right click on Solutions Quickstart jar file , In context sensitive menu Go to open with , Select Java(TM) Platform SE binary. If this option is not visible in context sensitive menu click Choose Program and Browse to <Java_Home>\jre\bin\javaw.exe , Select Java(TM) Platform SE binary in Open with dialog , Check “Always use selected program to open this kind of file”, Click OK
  2. Tweak the registry key “HKEY_CLASSES_ROOT\jarfile\shell\open\command” to “<prefix_correct_path_till_Java_Folder>\\jre6\bin\javaw.exe” -jar “%1″ %*
  3. There are scores of jarfix utilities that are available on internet , You can use any such utility , One such utility is available here [Read terms & conditions , license agreement before using this utility or any such utility]
  4. Re-install JRE
Any of the ways suggested above should fix the problem and you should be able to start Experience Server with just a click of a button.
Alternatively Solutions Quickstart can also be started from command prompt for more information on this refer to my earlier post [Installation section] on my blog

 

CC User forums

 

If you are a user of Customer Experience Solutions and need any help/information about Customer Communications , Please post your queries or issues and get immediate responses from experts on CC user forums

 

 

 

 

 

 

 

 

 

 

 

Error – Server.Processing

 

At times users may encounter the below error message with Title “Error – Server.Processing” and message “An error occured while fetching configuration”.

When the above message is shown on Correspondence Management Manage Assets UI screen , It could be due to either of the following two things :

  1. Experience Server is not properly configured with a Document Server or
  2. Experience Server is unable to communicate with the configured Document Server

 

How do I check if Experience Server is properly configured with a Document Server ( Issue # 1 above )?

1. If Experience Server is running on the same machine where Document Server is run in turnkey mode [ JBoss using default ports] no additional configuration is needed to be done by user , Experience server configurations include URL to connect to Document Server running on same machine using default JBoss port

2. If Experience Server is running on a different machine than the machine that runs Document Server or If Experience Server needs to use Document Server running on JBoss using non-default port of any other supported application server like WebLogic or WebSphere then follow below steps to check the configuratio

2.1 Log on to Felix Web console http://[hostname]:[port]/system/console/bundles as admin (default admin credentials , username : admin , password:admin )

2.2 Click “Document Services Settings” Tab

2.3 Enter correct Document Server Url , username , password and Experience Server Url values and click configure

 

If Experience Server is properly configured with Document Server but still you are seeing the above Error (Issue # 2 mentioned above)

  • Then check if you are able to connect to Document Server from the machine where you are running Experience Server
  • Try to access Document Server adminui page using a browser from Experience Server  http://[hostname]:[port]/adminui

 

If you are thinking of why should we configure Experience Server with a Document Server? :-)

  • Correspondence Management needs ADEP Forms or Output running on Document Server in order to preview or submit any letter and to kick off any post-process if attached to the letter after letter submission

 

Refer to more detailed install docs on official Adobe help documentation for configuring Experience Server with Document Server.

 

.

ADEP CM : Documentation

 

Adobe® Digital Enterprise Platform (ADEP) offers an integrated set of capabilities and technologies that enable organizations to create Customer Experience Management solutions.

ADEP comprises of two servers :

  1. Document Server :  All the services related to documents and process (of earlier LiveCycle) are now part of ADEP Document Server
  2. Experience Server : All Solutions (applications) and content are part of Experience Server [ Solutions like CM & ICR used Alfresco based Content Services to store all the content in earlier versions , now they use Day’s [now part of Adobe] CRX content repository to store all the content]

 

Architecture diagram :

For more information on understanding ADEP architecture refer documentation

 

 

Installation :

Installation of Experience server is as simple as a double click.

Refer to installation document for Experience Server for system requirements and installation steps and steps to configure Experience Server to work with Document server

You can watch following video for the same

 

Release Notes :

Before getting started with the ADEP CM , please spend sometime to go through Release Notes for known issues

 

API Reference Documentation :

What CM includes?
The following picture explains what CM includes :
Solution Guide :
The Correspondence Management Solution Guide provides guidelines to implement correspondence management solutions.
Developer Guide :
For developers who wants to extend the OOTB CM solution to add some new capabilities , they can go through Developer guide
Correspondence Management solution comprises of following three building blocks :
Click on above links for Technical guides of the CM building blocks

Adobe LiveCycle Rebranding

 

With the release of ADEP (Adobe Digital Enterprise Platform) Adobe is discontinuing the usage of LiveCycle brand name and will use the name of ADEP.

There are changes to various other products of LiveCycle , Here are a few :

  • Adobe Livecycle Enterprise Suite will now be called as ADEP
  • Solution Accelerators  -> Customer Experience Solutions
  • Correspondence Management Solution Accelerator -> Customer Communications Correspondence Management
  • Mosaic -> Composite Application Framework
  • Managed Review and Approval Solution Accelerator -> Integrated Content Review

If you are a customer of LiveCycle and/or Solution Accelerator(s) it is recommended to go through the FAQ

 

Customer Communications – Correspondence Management

 

What is Correspondence Management : Procedures established for systematic dispatch, receipt,filing, storage, retrieval, and disposition of communicationrecords. (source www.businessdictionary.com)

The Customer Communications Correspondence Management Solution (part of Adobe Digital Enterprise Platform ) streamlines personalized correspondence creation and management. It is an enterprise software for B2C , B2B , G2C applications. It can be used in wide array of industry sectors like BFSI and Government.

Correspondence Management Solution helps businesses & Governments meet all their correspondence management needs , both System generated correspondence like payment reminders , trade confirmations etc.,. and User Generated Correspondence like insurance policy , welcome kits etc.,.

It centralizes and manages the creation , assembly and delivery of correspondence, It helps organizations

  • Create personalized & tailored communications from predefined content to templates
  • Mitigate compliance and regulatory risk through usage of pre-approved content
  • Decrease IT dependency – Business users can create and manage correspondence templates, speeding up process significantly

 

Click here for more information on CC CM