Posts tagged "Experience Server"

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.

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.

 

.