Posts tagged "CM"

Content Services clear cache and index check

This blog is relevant to all LiveCycle Content Services customers who are using CS directly or might be using applications that use CS (like CM 2.5 or customized Workspace to use CS in background).

In case if you see any inconsistency in search results of the assets that are stored in Content Services then you may follow below steps to troubleshoot that issue.

I would recommend performing these on development and test environments and not on production system. These steps do not cause any side effects but it is advised to perform these in assistance with LiveCycle support if you are doing it on production systems ( just to avoid any user errors while performing these steps)

One of the reasons for search result inconsistency could be due to cache. Follow the below steps to clear cache and then use your application to check if search results are as expected.

Steps to clean cache :

  1. Log on to http://hostname:port/contentspace as administrator
  2. In the same browser session change the above URL in address bar to http://[hostname]:[port]/contentspace/wcservice/adobe/cms/cleancache/webscript
  3. Hit Enter
  4. You would see a success message after the cache is cleaned
  5. Check the search behavior now from customized workspace UI and/or from CM Manage Assets UI

If the issue still persists , check if the indexes are out of sync

  1. Go to http://hostname:port/contentspace/service/enterprise/admin/indexcheck URL, login as administrator
  2. Click on Check all txn ids (warning: this may take some time)

Note: This operation will take some time and is recommended to be performed when the load on the system is very low (post business hours) or during weekends when no one or not many people are using the system for development or testing.

Also if your development or test  system is cluster, perform these steps on all the nodes separately.

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

Correspondence Management Letter Preview Issues in Chrome and Firefox

 

If you are unable to preview the letter in Correspondence Management Create Correspondence UI and wondering what might have happened – this blog tries to explain the reason behind it

If you are using Chrome , you may be seeing the issue as shown in the below screen shot

Letter preview in Chrome

Chrome Preview

 

 

 

 

 

 

 

 

If you are using Firefox , you may be seeing the issue as shown in the below screen shot

 

Letter preview in Firefox

Letter preview in Firefox

 

 

 

 

 

 

 

 

When a letter is opened for preview the Create Correspondence UI opens and this UI is split in to two halves

On the left hand side the contents that are used in the letter are shown in the Flex UI and on the right hand side the preview of final correspondence is shown as PDF

In order to display the PDF on RHS one would need PDF plug-in in the browser that is being used.

The latest versions of modern browsers like Chrome and Firefox have their own in-built PDF Viewers

Chrome’s inbuilt PDF viewer is Chrome PDF Viewer , Latest versions of Firefox has a PDF.js plug-in which shows the PDF in html form

 

The PDF that is shown on the right hand side of create correspondence UI is an XFA form based PDF and the built-in PDF viewers of Chrome and Firefox do not support the preview of these PDFs

The solution to resolve this issue is to set Adobe’s Acrobat/Reader plug-in as the default plug-in to open PDF files inside the browser

 

Follow the below steps to set Acrobat/Reader plug-in as default plug-in to open PDFs in Chrome

1. Open Chrome browser

2. type chrome://plugins in omnibar and press Enter

3. If Chrome PDF Viewer is enabled , you should see something as below in your browser (Notice the Disable on Chrome PDF Viewer – which means it is currently enabled , user can click the link to disable it)

Chrome Plugins

Chrome Plugins

 

 

 

 

 

 

3. Disable Chrome PDF Viewer and Enable Adobe Reader PDF plug-in , after Reader plug-in is enabled you should see something as below in your browser (In this example Adobe Reader is shown but if you have Acrobat installed on your system , the Acrobat plug-in should be enabled)

Chrome Plugins

Chrome Plugins

 

 

 

 

 

 

4. Try to preview the letter again after Reader plug-in is enabled , The letter should render fine now

 

Letter preview

Letter preview

 

 

 

 

 

 

 

 

Follow the below steps to set Acrobat/Reader plug-in as default plug-in to open PDFs in Firefox

 

1. Open Firefox browser

2. type about:config  in address bar

3. type pdfjs in the browser search box

4. In the preferences, select pdfjs.disabled – the option would be enabled by default , set it to false

aboutconfig

aboutconfig

 

 

 

 

 

5. Also in the preferences , ensure that the Acrobat/Reader is selected as the application to open PDF files

6. Restart the browser

 

If the above steps are followed to set Acrobat or Reader PDF plug-in as the default of Chrome or Firefox then the XFA form based PDF would appear properly on the RHS of the Correspondence Management Create Correspondence UI

Letter preview

Letter preview

 

 

 

 

 

 

 

 

Note : In case if the PDF viewer is properly configured to Acrobat or Reader plug-in but if you still see issues in viewing letters there could be some other issue.

 

I will post a seperate blog to investigate how the letter preview issues can be debugged … stay tuned….

 

 

 

 

 

 

Create Correspondence UI view preferences

 

Correspondence Management create correspondence UI is split in to two columns.

LHS shows the contents that are used in the letter and RHS shows the PDF preview.

CCR view has a drop down that changes the view on left hand side to data entry view or content view based on value selected in the drop down

Create Correspondence UI

Create Correspondence UI

 

 

 

 

 

There is some logic that determines the default view on left hand side (Flex UI) and shows content view or data view depending specific to letter

If a letter contains only layout fields that are user fillable – default view is data entry view

If a letter contains any content (like text , condition , image and/or list ) – default view is content view

There are some customer use cases where they always want the default view to be data even if the letter has content data modules.

To enforce Create Correspondence UI to always show data entry view (by default) follow the steps mentioned below :

 

  • Log on to CRX DE Lite http://hostname:port/lc/crx/de/index.jsp as admin
  • Navigate to /content/cm/tbxeditor-config.xml
  • set ccr default view as DATA (default would be AUTO , change it to DATA)

<!– In Create Coorspondence UI, LHS should default to what view: DATA|CONTENT|AUTO–>

<CCRDefaultView>DATA</CCRDefaultView>

  • Click Save All
  • Repeat the above steps on all instances (author & publish)
tbxeditor-config

tbxeditor-config

 

 

 

 

 

 

 

Now for any letter preview the default view would be data entry view (data is selected in the drop down by default) but users can switch to content view by changing the value of drop down to content

some customers had a requirement to completely hide the content tab , I will blog a separate post to select the default view to data and completely hide the data/content drop down

stay tuned…

Announcing LiveCycle ES4

We are proud to announce our next and major release of LiveCycle a.k.a Adobe LiveCycle ES4 with loads and loads of new features.

 

Significant features include :

  1. Mobile forms support
  2. Mobile Workspace application
  3. Forms management capabilities
  4. Integration with Adobe Experience Manager
  5. Extended rights management
  6. Addition of new features in Correspondence Management
  7. Inclusion of new features that are added as CCR on previous releases which will be available for upgrade customers

 

For more information go to official press release of Adobe

Also watch a cool 5 minute video that showcases and explains most of the new features of LiveCycle ES4

 

 

Copy paste of text content from MS-Office applications

LiveCycle Correspondence Management solution users often use text content from MS-Office applications like Word and Excel.

The text content can be copied from MS-Office applications and pasted to Rich Text Editor of Correspondence Management.

Currently the content copying is supported but any rich text formatting applied to the text in external applications like MS-Office applciations will not be retained.

 

If the user copies (to clipboard) below content from MS-Word

 

 

 

 

 

 

and pastes it in CM text content area of Rich Text editor , the text would appear like

 

 

 

 

 

 

Lot of customers are asking us to provide a functionality to copy paste content from MS-Office applications that supports copying of text content along with the formatting. This is currently on the roadmap but there are no fixed timelines when this feature would be available in the product.

stay tuned …….

 

20 reasons to upgrade to ES3 Correspondence Management solution

 

First version of LiveCycle Correspondence Management solution was delivered along with LiveCycle ES2 service pack 2.

Based on the customer feedback and requirements from various existing and prospective customers lot of new features have been added and existing features have been improved in Correspondence Management solution.

If you are an existing customer of Correspondence Management but are on LiveCycle version earlier to ES3 , Here are the 20 reasons why you should consider upgrading to LiveCycle ES3 Correspondence Management.

If you are a LiveCycle ES or LiveCycle ES2 customer and considering to buy and implement Correspondence Management as well , Here are the same 20 reasons why you should consider upgrading LiveCycle as well in order to make use of latest Correspondence Management solution.

 

(Please click the image to enlarge it and clearly view the content)

 

 

 

 

 

http://about.me/nskumar

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.