6.11 Configure Correspondence Management Solution

Perform the following tasks to configure Correspondence Management Solution.

    6.11.1 Configure the Author instance

    The Author instance is embedded within the LiveCycle server. This implies that you do not need to make any configuration updates to the Author instance. The instance inherits all the configuration settings from the LiveCycle instance.

    6.11.2 Configure the Publish instance

    You must run separate author and publish instances for Correspondence Management Solution. However, you can configure the two instances on the same or on different machines.

    Note: Before configuring the publish instance, ensure that your author instance is configured and deployed. You can verify by successfully logging in to the solution template for Correspondence management Solution. See 6.7.8 Access Correspondence Management Solution templatefor more information.

    1. Create a new appserver profile for the publish instance on the same or on a different machine.

    2. On the author instance, navigate to the [LiveCycle root]/configurationManager/export/ directory.

    3. Copy the adobe-livecycle-cq-publish.ear file and deploy it to the appserver profile created in step 1.

    4. Copy the [LiveCycle root]/configurationManager/export/crx-repository directory to the file server for the publish instance.

    5. Start the publish server with -Dcom.adobe.livecycle.crx.home=<location for crx-repository> parameter, where <location for crx-repository> is the location where you copied the crx-repository directory for the publish instance.

    Note: If author and publish instances are on the same machine, ensure that you start the publish instance using a different port.

    Now that the publish instance is up and running, you need to configure the two instances to communicate with each other.

    Important: If you are setting up clustering on your Correspondence Management solution, you need to ensure that there are no spaces in your CRX repository path.

    6.11.3 Communicating between the Author and Publish instances

    You need to perform certain configuration changes to enable two-way communication between the Author and Publish instances.

    6.11.3.1 Define Publish instance URL

    1. Go to http://<authorHost>:<authorPort>/lc/etc/replication/agents.author/publish.html.

    2. Click Edit. The Agent Settings dialog opens.

    3. Click the Transport tab and specify the URL to the publish server in the URI field.

      http://<publishHost>:<publishPort>/lc/bin/receive?sling:authRequestLogin=1
      Note: If there are multiple publish instances managed by a Load Balancer, specify the URL to the load balancer in the URI field.

    4. Click OK.

    Note: For author clusters, these steps need to be performed on one author instance (preferably a master instance).

    6.11.3.2 Define publish instance URL for ActivationManagerImpl

    1. Go to http://<authorHost>:<authorPort>/lc/system/console/configMgr.

    2. Find and click the Edit icon next to the com.adobe.livecycle.content.activate.impl.ActivationManagerImpl.name setting.

    3. In the ActivationManager Publish URL field, specify the URL for the corresponding publish instance.

    4. Click Save.

    6.11.3.3 Configure reverse replication queue

    1. Go to http://<authorHost>:<authorPort>/lc/etc/replication/agents.author/publish_reverse.html.

    2. Click Edit. The Agent Settings dialog opens.

    3. Click the Transport tab and specify the URL to the corresponding publish server in the URI field.

      Note: If there are multiple publish instances managed by a Load Balancer, specify the URL to the load balancer in the URI field.

    4. Click OK.

    6.11.3.4 Define author instance URL

    1. Go to http://<publishHost>:<publishPort>/lc/system/console/configMgr.

    2. Find and click the Edit icon next to the com.adobe.livecycle.content.activate.impl.VersionRestoreManagerImpl.name setting.

    3. In the VersionRestoreManager Author URL field, specify the URL for the corresponding author instance.

      Note: If there are multiple author instances managed by a Load Balancer, specify the URL to the load balancer in the VersionRestoreManager Author URL field.

    4. Click Save.

    6.11.4 Install sample users and assets

    You can install sample users with predefined user permissions to further explore the solution template, which you can customize to build your own solution.

    1. Go to http://<authorHost>:<authorPort>/lc/crx/explorer/index.jsp.

    2. Log in using LiveCycle administrator credentials and click Package Manager.

    3. In Package Manager, upload the samples-correspondencemanagement-pkg-<version>.zip package from <LC_HOME>/deploy/crx.

    4. Click Install once the package uploads successfully.

    5. Click Install on the confirmation dialog to install the sample users and assets.

    For more information about the sample users and guidelines to implement a solution using the solution template, see Correspondence Management Solution Guide.
    Note: For author clusters, these steps need to be performed on one author instance (preferably a master instance).

    6.11.5 Configure IPv6 implementation

    Note: Perform these steps only if Correspondence Management Solution is running on a machine that uses an IPv6 address.

    To map the IPv6 address to a hostname on the server and client machines:

    1. Navigate to the C:\Windows\System32\drivers\etc directory.

    2. Open the hosts file in a text editor.

    3. Add a mapping for the IPv6 address to a host name. For example:

      2001:1890:110b:712b:d1d:9c99:37ef:7281 <ipv6_hostname>

    4. Save and close the file.

    Ensure that you use the mapped host name instead of the IPv6 address to access Correspondence Management Solution.

    6.11.6 Install Japanese fonts for Adobe Reader

    If your Correspondence Management assets use Japanese fonts, you must install the Japanese Language Support Package for Adobe Reader. Otherwise, your letters and forms will not render and function properly. For installing language packs, visit the downloads page for Adobe Reader.

    // Ethnio survey code removed