Macromedia live cycle 7.2 Manual
44
6
Configuring LiveCycle Products
This chapter applies to all LiveCycle security products.
This chapter describes how to configure LiveCycle products for deployment.
This chapter assumes that you have installed your LiveCycle products. If you have not installed the
products, see
products, see
.
The instance of Configuration Manager that is installed with one LiveCycle product can be used with all
LiveCycle products. When you run Configuration Manager, you can specify the LiveCycle products that you
are configuring as well as the type of application server that you are leveraging in the solution. You can
also set run-time properties for LiveCycle products and enable or disable security.
LiveCycle products. When you run Configuration Manager, you can specify the LiveCycle products that you
are configuring as well as the type of application server that you are leveraging in the solution. You can
also set run-time properties for LiveCycle products and enable or disable security.
If you are already running one or more LiveCycle products, you must configure and assemble those
existing products with the new one that you want to configure. To do this, you must undeploy the
previously deployed products and select all of the products that you want to assemble during
configuration. The previously deployed products are then included in the LiveCycle.ear file and deployed
with the new product when you deploy the file to the application server.
existing products with the new one that you want to configure. To do this, you must undeploy the
previously deployed products and select all of the products that you want to assemble during
configuration. The previously deployed products are then included in the LiveCycle.ear file and deployed
with the new product when you deploy the file to the application server.
Note:
To assemble multiple LiveCycle products, each product must be installed in the same [LiveCycle
root] directory.
root] directory.
When Configuration Manager completes the configuration of the products, it places the applicable files to
be deployed to the application server (LiveCycle.ear, adobe-FontManager.ear, LiveCycle-security.ear, and
edc-server.ear) in the following directory:
be deployed to the application server (LiveCycle.ear, adobe-FontManager.ear, LiveCycle-security.ear, and
edc-server.ear) in the following directory:
●
(Windows) [LiveCycle root]\configurationManager\export
●
(Linux) [LiveCycle root]/configurationManager/export
Note:
Ensure that the application server is running before starting Configuration Manager. This applies to
standalone and remote scenarios. Also ensure that Configuration Manager is running on the same
computer that is hosting the application server. All configuration settings are final and cannot be
reversed. There is not a cache of old or overwritten configuration settings.
standalone and remote scenarios. Also ensure that Configuration Manager is running on the same
computer that is hosting the application server. All configuration settings are final and cannot be
reversed. There is not a cache of old or overwritten configuration settings.
If any errors occur during the configuration, Configuration Manager creates a log file called lcm.log, which
may contain the error message. The log file is located in the [LiveCycle root]/configurationManager
directory.
may contain the error message. The log file is located in the [LiveCycle root]/configurationManager
directory.
Creating an endorsed directory
This section applies to LiveCycle Policy Server only.
Before running Configuration Manager for LiveCycle Policy Server, you must create an endorsed directory.