12 Appendix - Configuration Manager Command Line Interface

LiveCycle provides a Command Line Interface (CLI) for the Configuration Manager. The CLI is intended to be used by advanced users of LiveCycle, for example in server environments which do not support the use of the Graphical User Interface (GUI) of the Configuration Manager.

    12.1 Order of operations

    The Configuration Manager CLI must follow the same order of operations as the GUI version of the Configuration Manager. Ensure that you use the CLI operations in this order:

    1. Configure LiveCycle.

    2. Validate application server topology.

    3. Validate the database connectivity.

    4. Configure the application server.

    5. Validate the application server configurations.

    6. Deploy LiveCycle.

    7. Initialize LiveCycle.

    8. Validate LiveCycle.

    9. Deploy the LiveCycle modules.

    10. Validate the LiveCycle module deployment.

    11. Check system readiness for PDF Generator.

    12. Add administrator user for PDF Generator.

    13. Configure Connector for IBM Content Manager.

    14. Configure Connector for IBM FileNet.

    15. Configure Connector for EMC Documentum.

    16. Configure Connector for SharePoint.

    17. Configure Correspondance Mangement.

    Important: You must restart each of your cluster nodes after you complete Configuration Manager CLI operations.

      12.2 Command Line Interface property file

      You should create the property file according to your installation. Use one of the following methods.

      • Create a property file and populate the values according to your installation and configuration scenarios.

      • Copy the property file cli_propertyFile_template.txt to use them as cli_propertyFileupgrade_template.txt template and edit the values based on the Configuration Manager operations you intend to use.

      • Use the GUI of the Configuration Manager and then use the property file created by the GUI version as the CLI version property file. When you run the [LiveCycle root]/configurationManager/bin/ConfigurationManager.bat file, the userValuesForCLI.properties file is created in the [LiveCycle root]/configurationManager/config directory. You can use this file as input for the Configuration Manager CLI.

        Note: In the CLI properties file, you must use the escape character (\) for Windows paths directory separator (\). For example, if the Fonts folder to be mentioned is C:\Windows\Fonts, in the Configuration Manager CLI script, you should enter it as C:\\Windows\\Fonts.

        12.3 General configuration properties

          12.3.1 Common properties

          Common properties are:

          WebLogic and WebSphere specific properties: Required for the Configure the Application Server, Deploy LiveCycle, Validate Application Server Topology and Validate Application Server Configurations operations.

          LiveCycle Server specific properties: Required for the Initialize LiveCycle and Deploy LiveCycle Components operations.

          These properties are required for the following operations:

          • Initialize LiveCycle

          • Deploy LiveCycle components.

          Property

          Values

          Description

          targetServer.topologyType

          server or cluster

          The type of application server topology for which you are deploying LiveCycle.

          targetServer.name

          String

          The name assigned to the application server/admin server node or cluster.

          targetServer.adminHost

          String

          Default is localhost

          The hostname of the server where the Admin server is installed.

          targetServer.adminPort

          Integer

          The port number the admin server uses to listen for SOAP requests.

          targetServer.adminUserID

          String

          The administrative user ID to use when accessing the application server.

          targetServer.adminPassword

          String

          The password associated with the WebLogic administrative user ID.

          localServer.appServerRootDir

          (Windows) WebLogic 11g C:\Oracle\Middleware\wlserver_10.3

          (Linux, Solaris) WebLogic 11g /opt/Oracle/Middleware/wlserver_10.3

          The root directory of the application server instance that you are configuring locally (on which you plan to deploy LiveCycle or that you will use to communicate with a remote server on which you plan to deploy LiveCycle).

          targetServer.appServerRootDir

          Default:

          (Windows) WebLogic 11g C:\Oracle\Middleware\wlserver_10.3

          (Linux, Solaris) WebLogic 11g /opt/Oracle/Middleware/wlserver_10.3

          The root directory of the application server instance that you are configuring on a remote server (on which you plan to deploy LiveCycle).

          LiveCycle Server specific properties

          LCHost

          String

          The hostname of the server where LiveCycle will be deployed.

          For cluster deployments, hostname of any one of the cluster nodes where the application server is running.

          LCPort

          Integer

          The web port number where LiveCycle will be deployed.

          excludedSolutionComponents

          String. Values include:

          ALC-LFS-Forms,

          ALC-LFS-ConnectorEMCDocumentum,

          ALC-LFS-ConnectorIBMFileNet,

          ALC-LFS-ConnectorIBMContentManager,

          ALC-LFS-DigitalSignatures,

          ALC-LFS-DataCapture,

          ALC-LFS-Output,

          ALC-LFS-PDFGenerator,

          ALC-LFS-ProcessManagement,

          ALC-LFS-ReaderExtensions,

          ALC-LFS-RightsManagement

          (Optional) List the LiveCycle modules you do not want to configure. Specify the excluded modules in a comma separated list.

          excludedSolution

          ALC-SA-CorrespondenceManagement

          You can include or exclude Correspondence Management Solution by specifying this property.

          12.3.2 Configure LiveCycle properties

          These properties only apply to the configure LiveCycle operation.

          Property

          Values

          Description

          AdobeFontsDir

          String

          Location of the Adobe server fonts directory.

          This path must be accessible from all cluster nodes being deployed to.

          customerFontsDir

          String

          Location of the customer fonts directory.

          This path must be accessible from all cluster nodes being deployed to.

          systemFontsDir

          String

          Location of the system fonts directory.

          This path must be accessible from all cluster nodes being deployed to.

          LCTempDir

          String

          Location of the temporary directory.

          This path must be accessible from all cluster nodes being deployed to.

          LCGlobalDocStorageDir

          String

          The global document storage root directory.

          Specify a path to an NFS shared directory used to store long-lived documents and to share them among all cluster nodes.

          Specify this property only when deploying LiveCycle components in a clustered environment.

          This path must be accessible from all cluster nodes being deployed to.

          EnableDocumentDBStorage

          true or false

          Default: false

          Enables or disables document storage in database for persistent documents.

          Even if you enable document storage in database, you will need the file system directory for GDS.

          contentServices.indexesDir

          String

          [Content Services only] Specify the indexes directory used by Content Services. This directory is unique for each cluster node and must have the same name and location on all nodes. For example, contentServices.indexesDir=C:\\Adobe\\Adobe LiveCycle ES3\\lccs_indexes

          12.3.3 Configure or validate application server properties

            12.3.3.1 Configure or Validate WebLogic properties

            The Configuration Manager can configure or validate your WebLogic application server as required by LiveCycle.

            These properties apply to the following operations:

            • Configure Application Server

            • Validate Application Server Topology

            • Validate Application Server Configurations

            • Validate Database Connectivity

            12.3.3.2 Application server properties

            Property

            Values

            Description

            You must configure the application server-specific properties section. For more information see Common properties

            		 

            jvm.initialHeapSize

            Default:

            256

            The initial heap size, in MB, for the JVM.

            jvm.maxHeapSize

            Default:

            1792

            The maximum heap size, in MB, for the JVM.

            WebLogic and WebSphere Cluster only

            cache.useUDP

            true

            Set the value to true if LiveCycle uses UDP to implement caching.

            Set to false if LiveCycle uses TCP to implement caching.

            cache.udp.port

            Default:

            33456

            The port number that the primary computer uses for UDP-based caching communication.

            Configure only if cache.useUDP=true.

            cache.tcpip.primaryhost

            String

            The host name of the computer where the primary application server is installed.

            Configure only if cache.useUDP!=true.

            cache.tcpip.primaryport

            Default:

            22345

            The port number that the primary application server computer uses for TCP-based caching communication.

            Configure only if cache.useUDP!=true.

            cache.tcpip.secondaryhost

            String

            The host name of the computer where the secondary application server is installed.

            Configure only if cache.useUDP!=true.

            cache.tcpip.secondaryport

            Default:

            22345

            The port number that the secondary application server computer uses for TCP-based caching communication.

            Configure only if cache.useUDP!=true.

            WebLogic server core classpath configuration

            classpath.targetServer.javaHome

            String

            Configuration of target application server requires the location of the Java Home that is used to run the target application server.

            This path must be accessible from all the cluster nodes being configured.

            classpath.targetServer.pop3JarPath

            String

            Path to the Pop3 JAR file that is accessible to the target application server. This path must be accessible from the server being configured.

            Datasource configuration

            datasource.dbType

            Choose:

            • oracle

            • db2

            • sqlserver

            The type of database configured to use with LiveCycle.

            datasource.dbName

            String

            The name of the database.

            datasource.dbHost

            String

            The host name or IP address of the server where the database is located.

            datasource.dbPort

            Integer

            The database port LiveCycle will use when communicating with the database.

            datasource.dbUser

            String

            The user ID LiveCycle will use when accessing the database.

            datasource.dbPassword

            String

            The password associated with the database user ID.

            datasource.target.driverPath

            String

            JDBC driver in the application server lib directory.

            This path must be valid and accessible from all cluster nodes being configured.

            datasource.local.driverPath

            String

            Local JDBC driver. This value is used for testing direct database connection.

            12.3.4 Deploy LiveCycle properties

            These Deploy LiveCycle properties only apply to the deploy LiveCycle operation.

            Property

            Values

            Description

            For more information, see 12.3.1 Common properties

            deployment.includeIVS

            false

            Specifies whether IVS EAR files are included in the deployment.

            It is recommended not to include IVS EAR files in a production environment.

            12.3.5 Initialize LiveCycle properties

            These initialize LiveCycle properties only apply to the initialize LiveCycle operation.

            Property

            Values

            Description

            For more information, see 12.3.1 Common properties

            12.3.6 Deploy LiveCycle Components properties

            These properties apply to the following operations:

            • Deploy LiveCycle Components

            • Validate LiveCycle Component Deployment

            • Validate LiveCycle Server.

              Property

              Values

              Description

              You must configure the LiveCycle Server Information section. For more information, see Common properties

              LCAdminUserID

              String

              The user ID to assign to the LiveCycle Administrator user. This User ID is used to login to the Administrator Console.

              LCAdminPassword

              String

              The password to assign to the LiveCycle Administrator user. This password is used to login to the Administrator Console.

            12.3.7 Add administrator user for PDF Generator

            These properties apply only to the adding administrator user for PDF Generator operation. These properties are present in cli_propertyFile_pdfg_template.txt

            Property

            Values

            Description

            LCHost

            String

            Hostname where LiveCycle Server is installed.

            LCPort

            Integer

            Port number where LiveCycle application server is configured

            LCAdminUserID

            String

            The user ID to assign to the LiveCycle Administrator user. This User ID is used to login to the Administrator Console.

            LCAdminPassword

            String

            The password to assign to the LiveCycle Administrator user. This password is used to login to the Administrator Console.

            LCServerMachineAdminUser

            String

            The user ID of the Administrator user of the Operation System hosting LiveCycle

            LCServerMachineAdminUserPasswd

            String

            The password of the Administrator user of the Operation System hosting LiveCycle

            12.3.8 Configure Connector for IBM Content Manager

            Property

            Values

            Description

            LCHost

            String

            Hostname where LiveCycle Server is installed.

            LCPort

            Integer

            Port number where LiveCycle application server is configured

            LCAdminUserID

            String

            The user ID to assign to the LiveCycle Administrator user. This User ID is used to login to the Administrator Console.

            LCAdminPassword

            String

            The password to assign to the LiveCycle Administrator user. This password is used to login to the Administrator Console.

            jndiPortNumber

            String

            JNDI port corresponding to LiveCycle application server.

            jboss.clientjar.location

            String

            The location of the jbossall-client.jar file (JBoss only)

            CDVTopology.appserverrootdir

            String

            The root directory of the application server instance that you are configuring on a remote server (on which you plan to deploy LiveCycle)

            ConfigureIBMCM

            true or false

            Specify true to configure Connector for IBM Content Manager

            IBMCMClientPathDirectory

            String

            Location of IBM Content Manager client installation directory.

            DataStoreName

            String

            Name of the DataStore of IBM Content Manager Server that you want to connect to

            IBMCMUsername

            String

            The user name assign to the IBM Content Manager Administrator user. This User ID is used to login to the IBM Content Manager.

            IBMCMPassword

            String

            The password to assign to the IBM Content Manager Administrator user. This password is used to login to the IBM Content Manager.

            ConnectionString

            String

            Additional arguments used in the connection string to connect to IBM Content Manager(Optional).

            12.3.9 Configure Connector for IBM FileNet

            Property

            Values

            Description

            LCHost

            String

            Hostname where LiveCycle Server is installed.

            LCPort

            Integer

            Port number where LiveCycle application server is configured

            LCAdminUserID

            String

            The user ID to assign to the LiveCycle Administrator user. This User ID is used to login to the Administrator Console.

            LCAdminPassword

            String

            The password to assign to the LiveCycle Administrator user. This password is used to login to the Administrator Console.

            jndiPortNumber

            String

            JNDI port corresponding to LiveCycle application server.

            jboss.clientjar.location

            String

            The location of the jbossall-client.jar file (JBoss only)

            CDVTopology.appserverrootdir

            String

            The root directory of the application server instance that you are configuring on a remote server (on which you plan to deploy LiveCycle)

            ConfigureFilenetCE

            true or false

            Specify true to configure Connector for IBM Filenet

            FilenetConfigureCEVersion

            String

            The FileNet client version to configure. Specify FilenetClientVersion4.0 or FilenetClientVersion4.5

            FilenetCEClientPathDirectory

            String

            Location of IBM Filenet Content Manager client installation directory.

            ContentEngineName

            String

            Hostname or IP address of the machine where IBM Filenet Content Engine is installed

            ContentEnginePort

            String

            The port number used by IBM Filenet Content Engine

            CredentialProtectionSchema

            CLEAR or SYMMETRIC

            Specify the level of protection.

            EncryptionFileLocation

            String

            Location of the encryption file. This is required only when you select SYMMETRIC option for CredentialProtectionSchema attribute.

            Use a forward slash (/) or double backward slashes (\\) as a path seperator.

            DefaultObjectStore

            String

            Name of the ObjectStore for the Connector for IBM Filenet Content Server.

            FilenetContentEngineUsername

            String

            The user ID to connect to the IBM FileNet Content server.

            The user ID with read-access privileges would be allowed to connect to the Default object Store.

            FilenetContentEnginePassword

            String

            The password to assigned to the IBM FileNet user. This password is used to connect to Default object Store.

            ConfigureFilenetPE

            true or false

            Specify true to configure Connector for IBM FileNet

            FilenetPEClientPathDirectory

            String

            Location of IBM FIleNet client installation directory

            FilenetProcessEngineHostname

            String

            Hostname or IP address of the process router.

            FilenetProcessEnginePortNumber

            Integer

            Port number for IBM FileNet Content Server

            FilenetPERouterURLConnectionPoint

            String

            Name of the process router.

            FilenetProcessEngineUsername

            String

            The user ID to connect to the IBM FileNet Content Server

            FilenetProcessEnginePassword

            String

            The password to connect to the IBM FileNet Content Server

            12.3.10 Configure Connector for EMC Documentum

            Property

            Values

            Description

            LCHost

            String

            Hostname where LiveCycle Server is installed.

            LCPort

            Integer

            Port number where LiveCycle application server is configured

            LCAdminUserID

            String

            The user ID to assign to the LiveCycle Administrator user. This User ID is used to login to the Administrator Console.

            LCAdminPassword

            String

            The password to assign to the LiveCycle Administrator user. This password is used to login to the Administrator Console.

            jndiPortNumber

            String

            JNDI port corresponding to LiveCycle application server.

            jboss.clientjar.location

            String

            The location of the jbossall-client.jar file (JBoss only)

            CDVTopology.appserverrootdir

            String

            The root directory of the application server instance that you are configuring on a remote server (on which you plan to deploy LiveCycle)

            ConfigureDocumentum

            true or false

            Specify true to configure Connector for EMC Documentum

            DocumentumClientVersion

            String

            The EMC Documentum client version to configure. Specify DocumentumClientVersion6.0 or DocumentumClientVersion6.0

            DocumentumClientPathDirectory

            String

            Location of EMC Docum,entum client installation directory

            ConnectionBrokerHostName

            String

            Hostname or IP address of the EMC Documentum Content Server.

            ConnectionBrokerPortNumber

            String

            Port number for EMC Documentum Content Server

            DocumentumUsername

            String

            The user ID to connect to the EMC Documentum Content Server.

            DocumentumPassword

            String

            The password ID to connect to the EMC Documentum Content Server.

            DocumentumDefaultRepositoryName

            String

            Name of the default repository of MC Documentum Content Server

            12.3.11 Configure Connector for Microsoft SharePoint

            Property

            Values

            Description

            LCHost

            String

            Hostname where LiveCycle Server is installed.

            LCPort

            Integer

            Port number where LiveCycle application server is configured

            LCAdminUserID

            String

            The user ID to assign to the LiveCycle Administrator user. This User ID is used to login to the Administrator Console.

            LCAdminPassword

            String

            The password to assign to the LiveCycle Administrator user. This password is used to login to the Administrator Console.

            jndiPortNumber

            String

            JNDI port corresponding to LiveCycle application server.

            jboss.clientjar.location

            String

            The location of the jbossall-client.jar file (JBoss only)

            CDVTopology.appserverrootdir

            String

            The root directory of the application server instance that you are configuring on a remote server (on which you plan to deploy LiveCycle)

            ConfigureSharePoint

            true or false

            Specify true to configure Connector for Microsoft SharePoint

            SharePointServerAddress

            String

            Hostname or IP address of the Sharepoint Server

            SharePointUsername

            String

            The user ID to connect to the Sharepoint Server

            SharePointPassword

            String

            The password to connect to the Sharepoint Server

            SharePointDomain

            String

            The Domain Name of the Sharepoint Server

            SharePointVersion

            String

            The version of the Microsoft Sharepo installed for LiveCycle.

            ConnectionString

            String

            Additional arguments used in the connection string to connect to the Sharepoint Server(optional

            12.3.12 Command Line Interface Usage

            Once you have configured your property file, you must navigate to the [LiveCycle root]/configurationManager/bin folder.

            To view a complete description of the Configuration Manager CLI commands, type: ConfigurationManagerCLI help <command name>.

            Configure LiveCycle CLI usage

            The Configure LiveCycle operation requires the following syntax:

            configureLiveCycle -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            Extract CRX Bundles in LiveCycle

            The Configure CRX Repository requires the following syntax:

            extractCRXInstallationContent [- crx_password<password>] -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            Configure Correspondence Management

            The Configure CRX Repository requires the following syntax:

            configureCRXRepository -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            12.3.12.1 Configure LiveCycle CLI Usage

            The Configure LiveCycle operation requires the following syntax:

            configureLiveCycle -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            12.3.12.2 Configure the Application Server CLI Usage

            The Configure Application Server operation requires the following syntax:

            configureApplicationServer -targetServer_AdminPassword <password> -f <propertyFile> [-skip <configurationsToSkipList>]

            Where:

            • -targetServer_AdminPassword <password>: Allows you to set the Administrator password on the command line. If this argument is present, it will override the targetServer_AdminPassword property in the property file.

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            • -skip <configurationsToSkipList>: This is an optional parameter which allows you to list the application server components you do not want to configure. Specify the excluded components in a comma separated list. Valid options are Datasource or Core.

            12.3.12.3 (WebSphere and Weblogic Only) Deploy LiveCycle CLI Usage

            The Deploy LiveCycle operation requires the following syntax:

            deployLiveCycle -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.
              Important: You must restart your application server after you complete Deploy LiveCycle operation.

            12.3.12.4 Initialize LiveCycle CLI Usage

            The initialize LiveCycle operation requires the following syntax:

            initializeLiveCycle -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            12.3.12.5 Deploy LiveCycle Components CLI Usage

            The Deploy LiveCycle Components operation requires the following syntax:

            deployLiveCycleComponents -f <propertyFile> -LCAdminPassword <password>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            • -LCAdminPassword <password>: Allows you to set the Admin password on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.

            12.3.12.6 Validate Application Server Topology CLI Usage

            The Validate Application Server Topology operation is optional and requires the following syntax:

            validateApplicationServerTopology -f <propertyFile> -targetServer_AdminPassword <password>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            • -targetServer_AdminPassword <password>: Allows you to set the Admin password on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.

            12.3.12.7 Validate database connectivity CLI Usage

            The validate Database Connectivity operation is optional and requires the following syntax:

            validateDBConnectivity -f <propertyFile> -datasource_dbPasssword <password>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            • -datasource_dbPassword <password>: Allows you to set the database user password on the command line. If this argument is present, it will override the datasource.dbPassword property in the property file.

            12.3.12.8 Validate Application Server Configurations CLI Usage

            The Validate Application Server Configurations operation is optional and requires the following syntax:

            validateApplicationServerConfigurations -f <propertyFile> -targetServer_AdminPassword <password>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            • -targetServer_AdminPassword <password>: Allows you to set the Admin password on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.

            12.3.12.9 Validate LiveCycle Server CLI Usage

            The Validate LiveCycle Server operation is optional and requires the following syntax:

            validateLiveCycleServer -f <propertyFile> -LCAdminPassword <password>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            • -LCAdminPassword <password>: Allows you to set the Admin password on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.

            12.3.12.10 Validate LiveCycle Component Deployment CLI Usage

            The Validate LiveCycle Component Deployment operation is optional and requires the following syntax:

            validateLiveCycleComponentDeployment -f <propertyFile> -LCAdminPassword <password>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            • -LCAdminPassword <password>: Allows you to set the Admin password on the command line. If this argument is present, it will override the targetServer.adminPassword property in the property file.

            12.3.12.11 Check system readiness for PDF Generator

            The Checking system readiness for PDF Generator operation requires the following syntax:

            pdfg-checkSystemReadiness

            12.3.12.12 Adding administrator user for PDF Generator

            The adding administrator user for PDF Generator operation requires the following syntax:

            pdfg-addAdminUser -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

            12.3.12.13 Configure Connector for IBM Content Manager

            The Configure Connector for IBM Content Manager operation is optional and requires the following syntax:

            IBMCM-configurationCLI -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

              Important: Modify the <propertyFile> called cli_propertyFile_ecm_ibmcm_template.txt located in the [LiveCycle root]\configurationManager\bin\ directory.

            1. Copy the adobe-component-ext.properties file from [LiveCycle root]/configurationManager/configure-ecm/weblogic to the following [appserver root]/users_projects/domain/[appserverdomain] directory.

            2. Restart the Application Server.

            3. Start the following services from LiveCycle Administration Console

              • IBMCMAuthProviderService

              • IBMCMConnectorService

            12.3.12.14 Configure Connector for IBM FileNet

            The Configure Connector for IBM FileNet operation is optional and requires the following syntax:

            filenet-configurationCLI -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

              Important: Modify the <propertyFile> called cli_propertyFile_ecm_filenet_template.txt located in the [LiveCycle root]\configurationManager\bin\ directory.

            Perform the following steps manually to complete the configuration for Connector for IBM Content Manager.

            1. Copy the adobe-component-ext.properties file from [LiveCycle root]/configurationManager/configure-ecm/weblogic to the following [appserver root]/users_projects/domain/[appserverdomain] directory.

            2. If your deployment uses a custom JAAS file, locate the custom JAAS file and add to it contents of jaas.conf.WSI file available in [LiveCycle root]/configurationManager/configure-ecm/weblogic directory. Otherwise, add the location of the file jaas.conf.WSI as the following Java option in the WebLogic Server start command

              -Djava.security.auth.login.config=[LiveCycle root]/configurationManager/configure-ecm/weblogic/jaas.conf.WSI.

            3. (Only for FileNet 4.x) Add the Java option -Dwasp.location=[FileNetClient root]/wsi to the Application Server startup options.

            4. Restart the Application Server.

            5. Start the following services from LiveCycle Administration Console

              • IBMFileNetAuthProviderService

              • IBMFileNetContentRepositoryConnector

              • IBMFileNetRepositoryProvider

              • IBMFileNetProcessEngineConnector(If configured)

            12.3.12.15 Configure Connector for EMC Documentum

            The Configure Connector for EMC Documentum operation is optional and requires the following syntax:

            documentum-configurationCLI -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

              Important: Modify the <propertyFile> called cli_propertyFile_ecm_documentum_template.txt located in the [LiveCycle root]\configurationManager\bin\ directory.

            Perform the following steps manually to complete the configuration for Connector for EMC Documentum.

            1. Copy the adobe-component-ext.properties file from [LiveCycle root]/configurationManager/configure-ecm/weblogic to the following [appserver root]/users_projects/domain/[appserverdomain] directory.

            2. Restart the Application Server.

            3. Start the following services from LiveCycle Administration Console

              • EMCDocumentumAuthProviderService

              • EMCDocumentumRepositoryProvider

              • EMCDocumentumContentRepositoryConnector

            12.3.12.16 Configure Connector for Microsoft SharePoint

            The Configure Connector for Microsoft SharePoint operation is optional and requires the following syntax:

            sharepoint-configurationCLI -f <propertyFile>

            Where:

            • -f <propertyFile>: A property file containing the required arguments. For more information on creating a property file, see Command Line Interface property file.

              Important: Modify the <propertyFile> called cli_propertyFile_ecm_sharepoint_template.txt located in the [LiveCycle root]\configurationManager\bin\ directory.

            12.4 Examples Usage

            From the C:\Adobe\Adobe LiveCycle ES3\configurationManager\bin, type: 

            ConfigurationManagerCLI configureLiveCycle -f cli_propertyFile.txt

            Where cli_propertyFile.txt is the name of the property file you created.

              12.5 Configuration Manager CLI Logs

              If an error occurs, you can review the CLI logs located here in the [LiveCycle root]\configurationManager\log folder. The log file generated will have a naming convention such as lcmCLI.0.log where the number in the filename (0) will increment when the log files are rolled over.

                12.6 Next steps

                If you used Configuration Manager CLI to configure and deploy LiveCycle, you can now do the following tasks:

                  // Ethnio survey code removed