LiveCycle Configuration Manager (LCM) offers a Command Line Interface (CLI) for configuring the appserver instance.
Using this CLI, you can automate the deployment of LiveCycle, including building the EAR files, configuring the appserver, deploying the EAR files to the appserver, bootstrapping the database, deploying DSCs, and validating these operations. You cannot deploy Samples using the CLI.
You need to create/edit a properties file with configuration settings that fit your environment and requirements which serves as input to the CLI commands. Please download a working (Windows) sample CLI_properties.txt.
Copy this file to the \bin folder of LCM ($LC_INSTALL_ROOT/configurationManager/bin/).
Appendix B ("Appendix - LCM Command Line Interface") of the 'Installing and Deploying LiveCycle ES" Guides provide detailed information regarding the use of the LCM CLI version.
Run the following commands (sequence matters):
1) Build the EAR files
ConfigurationManagerCLI.bat configureLiveCycle -f CLI_properties.txt
2) Configure the appserver (JDBC data source is configured manually)
ConfigurationManagerCLI.bat configureApplicationServer -f CLI_properties.txt -skip Datasource
Please note that you should manually deploy and start \configurationManager\deploy\adobe-lcm-lcvalidator.ear first. Also, make sure that all cluster members are running, otherwise this will fail
3) Deploy the EAR files to the appserver. Manual deployment is recommended although CLI can be used.
4) Re-start the appserver instance or cluster
5) Bootstrap (Initialize the database)
ConfigurationManagerCLI.bat initializeLiveCycle -f CLI_properties.txt
6) Deploy DSCs (Components)
ConfigurationManagerCLI.bat deployLiveCycleComponents -f CLI_properties.txt
Leave a comment