5.3 Deploying to JBoss Application Server

Deploy LiveCycle modules to JBoss Application Server by copying the deployable components to the deploy directory. JBoss Application Server can be running or stopped when you copy the files to the directory. After you copy the files, start or restart the server to ensure that the services start correctly.

To deploy LiveCycle modules to JBoss Application Server:

Copy the following files from the [LiveCycle root]/configurationManager/export directory to the following directory: (Manually-configured JBoss) [appserver root]/server/all/deploy or (Adobe-preconfigured JBoss) [appserver root]/server/lc_<db-name>/deploy:
- adobe-livecycle-native-jboss-[OS].ear
- adobe-livecycle-jboss.ear
- adobe-workspace-client.ear (Process Management only)
You can optionally deploy the Adobe® LiveCycle® Forms Standard 11, Adobe® LiveCycle® Output 11, Adobe® LiveCycle® Mobile Forms, and Assembler IVS EARs as well.

To create publish instance for Correspondence Management, deploy adobe-livecycle-cq-publish.ear. Ensure that adobe-livecycle-cq-publish.ear is deployed on a different server. Do not deploy adobe-livecycle-cq-publish.ear on LiveCycle server. For detailed information about configuring the publish instance, see 6.3.2 Configure the Publish instance

Note: The data source definition files have to be modified to point to the database server and database. For more information, see Appendix - Manually Configuring Data Sources.

Important: Deploying the IVS EAR files to a production environment is not recommended.