Posted on June 07, 2016

Note:

Contact Support for more information or to obtain the QF.

Issues fixed in the QF

  • Export All on ADEP was failing due to corrupt assets. (Ref# NPR-9591)

Impacted modules

  • Correspondence Management

Prerequisites to installing the QF

You can install this patch only after you have ensured that you have installed or applied the following list of prerequisites.

  1. Adobe Digital Enterprise Platform (ADEP) 10.0
  2. CRX-HF 2.2.0.54-2.3.24
  3. CQ 5.4.0 Hotfix 39881
  4. LCDS bundles

Note:

If you have already applied any of the above patches, you do not need to reapply them.  You must install CRX-HF 2.2.0.54-2.3.24 first and then install CQ 5.4.0 Hotfix39881.

Installing the prerequisite patches

If you have not already applied any of the patches described in the prerequisite section above, you need to apply these patches before you install Patch M03 P10.

Installing CRX-HF 2.2.0.54-2.3.24

Install CRX-HF 2.2.0.54-2.3.24 on Cluster

  1. Copy the crx-hotfixpack-2.2.0.54-2.3.24.zip on the local disk.
  2. Install the crx-hotfixpack-2.2.0.54-2.3.24 package through Package Manager on master instance.
  3. Restart the cluster (both master and slave instances):
    • First stop the slave instance. Wait for slave to stop and then ensure that the Java process corresponding to the slave instance is no longer running.
    • Then, stop the master instance. Wait for master to stop and then ensure that the Java process corresponding to the master instance is no longer running.
    • Start the master instance. Wait for the master to start and then verify that all bundles in Felix console are in active state.
    • Finally, start the slave instance. Wait for the slave to start and then verify that all bundles in Felix console are in active state.
  4. After you restart the cluster, on the master instance, navigate to http://<servername>:<author port>/system/console/bundles.
  5. Ensure that there are no bundles in the resolved and installed state.
    • If the bundles are in resolved and/or installed state, explicitly start the bundle(s).
  6. Navigate to http://<servername>:<author port>/crx/packmgr/index.jsp on the slave instance. Verify that the package installed on the master instance is also installed on slave instance.
  7. Repeat steps 4 & 5 for the slave instance.

Install CRX-HF 2.2.0.54-2.3.24 on Publish Instance (s)

  1. Copy the crx-hotfixpack-2.2.0.54-2.3.24.zip on the local disk.
  2. Install crx-hotfixpack-2.2.0.54-2.3.24 through Package Manager on the Publish instance.
  3. Restart the Publish Instance.
  4. After restart, navigate to http://<servername>:<author port>/system/console/bundles
  5. Ensure that there are no bundles in the Resolved & Installed state.
    • If the bundles are in Resolved and/or Installed state, explicitly start the bundle(s).
  6. Repeat all above steps for each Publish instance.

Installing CQ 5.4.0 Hotfix 39881

Install CQ 5.4.0 Hotfix 39881 on Cluster

  1. Copy the HF cq-5.4.0-hotfix-39881.zip on the local disk.
  2. Unpack the hotfix zip file.
    • It contains org.apache.sling.installer.core-3.3.5-R1242752 and cq-5.4.0-hotfix-35597.zip.
  3. On the Master instance navigate to, http://<servername>:<author port>/system/console/bundles & install the bundle org.apache.sling.installer.core-3.3.5-R1242752.
    • Verify that the bundle version is now 3.3.5.R1242752.
  4. On Slave instance navigate to, http://<servername>:<author port>/system/console/bundles &install the bundleorg.apache.sling.installer.core-3.3.5-R1242752.
    • Verify the bundle version is now 3.3.5.R1242752.
  5. On the Master instance, install the package cq-5.4.0-hotfix-35597.zip via Package Manager.
  6. On the Master instance, navigate to http://<servername>:<authorport>/system/console/bundles.
  7. Ensure that no bundles should be in resolved and installed state. If the bundles are in resolved and/or installed state, explicitly start the bundle(s).
  8. Navigate to http://<servername>:<author port>/crx/packmgr/index.jsp of slave instance. Verify that the package installed on master is also installed on slave instance.
  9. Repeat steps 6 & 7 for slave instance also.

Install CQ 5.4.0 Hotfix 39881 on Publish Instance(s)

  1. Copy the HF cq-5.4.0-hotfix-39881.zip on the local disk.
  2. Unpack the hotfix zip file. It contains org.apache.sling.installer.core-3.3.5-R1242752 and cq-5.4.0-hotfix-35597.zip.
  3. On one of the Publish instance, navigate to http://<servername>:<author port>/system/console/bundles & install the bundle org.apache.sling.installer.core-3.3.5-R1242752
  4. Then, install the package cq-5.4.0-hotfix-35597.zip via Package Manager on the same instance.
  5. Navigate to http://<servername>:<authorport>/system/console/bundles
  6. Ensure that there are no bundles in the resolved and installed state.
    • If the bundles are in resolved and/or installed state, explicitly start the bundle(s).
  7. Repeat all above steps for each Publish instance.

Installing LCDS Bundles

Installing LCDS Bundles

  1. Copy the rds-bundle-4.6.1-0004.jar and dataservices-bundle-4.6.1-0004.jar on the local disk
  2. Navigate to http://<servername>:<author port>/system/console/bundles
  3. Click Install/Update.
  4. Browse to the above bundles and enable StartBundle.
  5. Click Install or Update.
  6. Verify the version of updated bundles:
    • DataServicesCombinedBundlecom.adobe.livecycle.dataservices.dataservices-bundle:  4.6.1.0004
    • Data Services RDS Bundlecom.adobe.livecycle.dataservices.rds-bundle: 4.6.1.0004
  7. Repeat above steps for all master, slave, and Publish instances.

Installing and configuring the QF

Install Correspondence Management and Content Package on Cluster

  1. Copy the solution-correspondencemanagement-pkg-1.3.22.zip on the local disk.
  2. Install the solution-correspondencemanagement-pkg-1.3.22 package through Package Manager on the master instance.
  3. Copy the platform-content-pkg-1.0.104.zip on the local disk.
  4. Install the Platform-content-pkg-1.0.104.zip package through Package Manager on master instance.
  5. Restart the Cluster (both master and slave instances):
    • First stop the slave instance. Wait for the slave to stop and then ensure that the Java process corresponding to slave instance is no longer running.
    • Then, stop the master instance. Wait for the master to stop and then ensure that the Java process corresponding to the master instance is no longer running.
    • Start the master instance. Wait for the master to start and then verify that all bundles in Felix console are in active state.
    • Finally, start the slave instance. Wait for the slave to start and then verify that all bundles in Felix console are in active state.
  6. After restart of the cluster, on the master instance, navigate to http://<servername>:<author port>/system/console/bundles
  7. Ensure that there are no bundles in the resolved and Installed state. If the bundles are in resolved and/or installed state, explicitly start the bundle(s).
  8. Navigate to http://<servername>:<author port>/crx/packmgr/index.jsp of the Slave instance. Verify that the package installed on master is also installed on slave instance.
  9. Repeat steps 4 & 5 for the Slave instance.
  10. Navigate to http://<servername>:<author port>/system/console/bundles on both master and slave instances and verify the versions of the following bundles:

Adobe Data Dictionary Building Block Bundle (com.adobe.dct): 1.3.12

Adobe Asset Composer Building Block Bundle (com.adobe.livecycle.acm): 1.3.26

Adobe Correspondence Management Solution Bundle (com.adobe.livecycle.cm): 1.3.22

Content Activate/Version Restore Bundlecom.adobe.livecycle.content.activate-bundle: 1.0.104

Content Core Bundlecom.adobe.livecycle.content.core-bundle: 1.0.104

Content LCDS Integration Bundlecom.adobe.livecycle.content.lcds-bundle: 1.0.104

Content Package Manager Bundlecom.adobe.livecycle.content.package-bundle: 1.0.104

Data Services Combined Bundlecom.adobe.livecycle.dataservices.dataservices-bundle: 4.6.1.0004

Data Services RDS Bundlecom.adobe.livecycle.dataservices.rds-bundle: 4.6.1.0004

Install Correspondence Management and Content Package on Publish Instance(s)

  1. Copy the solution-correspondencemanagement-pkg-1.3.22.zip on the local disk.
  2. Install the solution-correspondencemanagement-pkg-1.3.22 package through Package Manager on the Publish instance.
  3. Copy the Platform-content-pkg-1.0.104.zip on the local disk.
  4. Install the Platform-content-pkg-1.0.104.zip through Package Manager on the master instance.
  5. After restart, go to http://<servername>:<author port>/system/console/bundles
  6. Ensure that there are no bundles in the resolved and installed state. If the bundles are in resolved and/or installed state, explicitly start the bundle(s).
  7. Repeat all above steps for each Publish instance.
  8. Navigate to http://<servername>:<author port>/system/console/bundles on each Publish instance & verify the versions of the following bundles:

Adobe Data Dictionary Building Block Bundle (com.adobe.dct): 1.3.12

Adobe Asset Composer Building Block Bundle (com.adobe.livecycle.acm): 1.3.26

Adobe Correspondence Management Solution Bundle (com.adobe.livecycle.cm): 1.3.22

Content Activate/Version Restore Bundlecom.adobe.livecycle.content.activate-bundle: 1.0.104

Content Core Bundlecom.adobe.livecycle.content.core-bundle: 1.0.104

Content LCDS Integration Bundlecom.adobe.livecycle.content.lcds-bundle: 1.0.104

Content Package Manager Bundlecom.adobe.livecycle.content.package-bundle: 1.0.104

Data Services Combined Bundlecom.adobe.livecycle.dataservices.dataservices-bundle: 4.6.1.0004

Data Services RDS Bundlecom.adobe.livecycle.dataservices.rds-bundle: 4.6.1.0004

Post deployment

Adding metadata to existing assets

There is some additional metadata added for data modules which needs updates to the existing assets. Do the following:

  1. Open http://<servername>:<port> and login as admin user.
  2. Go to the URL http://<hostname>:<port>/apps/solutions/cm/migrate/PopulateAssetInfo to run migration.

Perform the above steps on all DEV and QE clusters, which means on all master author instances and publish instances.

Note:

This is a one-time activity and has no impact on any of the existing functionalities.

Configuring the Publish Instance

  1. Navigate to http://<servername>:<author port>/system/console/configMgr (Login as admin user)
  2. Clickcom.adobe.livecycle.content.activate.impl.ActivationManagerImpl.
  3. The default value for Publish URL is set to http://localhost:4503/bin/remoting/lc.content.remote.activate.activationManager
    • Username: admin
    • Password: admin
  4. Update the above values to point to the correct publish instance and also update corresponding authentication. Click Save.
  5. Navigate to http://<servername>:<port>/system/console/bundles and log in as an admin user.
  6. Search for Content Activate/Version RestoreBundle.
  7. Stop the bundle.
  8. Start the bundle after it has moved to the resolved state.

Perform the above steps on all the master author instances of DEV and QE clusters.

Customization

New SDKs have been uploaded along with the patch. Customization merge needs to be done using the new SDKs. The new SDK versions are as follows:

  • EXM SDK Package: bb-expressionmanager-sdk-pkg-1.0.44.zip
  • CT SDK Package:  bb-datadictionary-sdk-pkg-1.3.12.zip ACM
  • SDKPackage:bb-assetcomposer-sdk-pkg-1.3.26.zip
  • ES SDK Package: es-sdk-pkg-1.0.357.zip

For more details on customizing Correspondence Management, see Correspondence Management Developer Guide.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy