Posts tagged "Configuration"

Quick and Easy steps to run Author & Publish Systems of Correspondence Management ES4

Steps to setup Correspondence Management system with author and publish instances configured

It’s recommended to perform these steps on your development system where you would like to  have a setup in less amount of time to get started with the application

For stage, UA or prod systems please follow the detailed install & config guides

 

  1. Run LiveCycle installer and complete installation , before running LCM follow as mentioned in next step
  2. Go to <LC_Root_Directory>/jboss/server , create a copy of lc_turnkey under the same folder but with different name .. say lc_publish_turnkey (Publish instance needs a separate JBoss profile so this new profile can be used for publish instance)
  3. Now run LCM and complete the configuration manager – After completing LCM run You will have Author instance of CM up and running , now you need to perform few more steps to have author and publish running on same machine and configured to talk to each other
  4. LCM creates a folder with name crx-repository under <LC_Home_Directory> which is used as a repository for author instance
  5. Create a new folder under <LC_Home_Directory> with name “crx-publish-repository” (without quotes) , Go to <LC_Home_Directory>\configurationManager\export\crx-quickstart and copy install folder along with it’s contents and paste it under <LC_Home_Directory>\crx-publish-repository such that the contents under publish repository would appear like this after pasting the contents <LC_Home_Directory>\crx-publish-repository\install\
  6. Go to <LC_Home_Directory>\configurationManager\export Copy adobe-livecycle-cq-publish.ear file and paste it in <LC_Home_Directory>\jboss\server\lc_publish_turnkey\deploy folder
  7. Start lc_publish_turnkey profile from command prompt using command as “run -c lc_publish_turnkey -Dcom.adobe.livecycle.crx.home=”C:/pathToLCHomeDirectory/crx-publish-repository” -Djboss.service.binding.set=ports-01 -b 0.0.0.0” [o is zero in case you try to copy paste this content]
  8. For the first time start up of publish instance , It takes around ten minutes to completely start as it unpacks packages and creates repository , When the server is up and running You can use following URLs to log on to author and publish systems
  9. Author Manage Assets UI – http://hostname:8080/lc/cm , Publish Manage Assets UI – http://hostname:8180/lc/cm (You can login as default super admin i.e administrator/password – Change the password if needed)
  10. One last setting before you are done – Go to http://authorinstancehostname:8080/lc/etc/replication/agents.author/publish.html  , Login as admin\admin , Click Edit , Go to Transport tab and modify URL to http://localhost:8180/lc/bin/receive?sling:authRequestLogin=1 , Click OK , Click Test Connection and ensure that you see success message

Now you have running Correspondence Management system with author instance running on port 8080 and publish instance running on port 8180

 

Santosh

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.

 

.