4.2 Preparing Connectors for ECM for upgrade

If you are upgrading the Connector for EMC Documentum, Connector for IBM FileNet, or Connector for IBM Content Manager, from LiveCycle ES Update 1 or LiveCycle ES2, you must configure an application server system after you install LiveCycle and before you start Configuration Manager to complete the upgrade process.

Note: If you are not upgrading on a new computer, skip to step 2.
  1. (For out-of-place upgrade to a new computer only) Install the client for your ECM repository on the new computer that hosts the new application server.

  2. Perform all settings related to Connectors for ECM (except for Administration Console settings) on the new application server prior to beginning the upgrade. See the “Configuring the Connector for ...” section of the Post-Deployment Activities chapter in this guide.

  3. Navigate to the [JBoss root]/bin directory on your existing LiveCycle server and copy the adobe-component-ext.properties file to the corresponding directory on the target server.

  4. Restart the application server.

You can now continue to run Configuration Manager to upgrade to LiveCycle ES3.

Important: For Connector for EMC Documentum or Connector for IBM FileNet, the default repository must be set to LiveCycle Native Repository Provider or the upgrade deployment will fail. If you have configured the ECM repository provider as the default repository for either of these connectors, open the Administration Console and navigate to Services > LiveCycle ES Update1 or LiveCycle ES2 [connector type] > Configuration Settings. Select the LiveCycle ES Update1 Repository Provider or LiveCycle ES2 Repository Provider option and then click Save.

// Ethnio survey code removed