AEM forms on JEE provides a Command Line Interface (CLI)
for the Configuration Manager. The CLI is intended to be used by
advanced users of AEM forms on JEE, for example in server environments
which do not support the use of the Graphical User Interface (GUI)
of the Configuration Manager.
8.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:
-
Configure AEM forms on JEE.
-
Configure CRX
-
Validate
application server topology.
-
Validate
the database connectivity.
-
Configure
the application server.
-
Validate
the application server configurations.
-
Deploy
AEM forms on JEE.
-
Initialize AEM forms on JEE.
-
Validate AEM forms on JEE.
-
Deploy the AEM forms on JEE modules.
-
Validate the AEM forms on JEE module deployment.
-
Check system readiness for PDF Generator.
-
Add administrator user for PDF Generator.
-
Configure Connector for IBM Content Manager.
-
Configure Connector for IBM FileNet.
-
Configure Connector for EMC Documentum.
-
Configure Connector for SharePoint.
8.2 Command Line Interface property file
The
Configuration Manager CLI requires a property file containing the
defined properties for your AEM forms on JEE environment. The template
for the properties file, cli_propertyFile_template.txt, is located
in the
[aem-forms root]
/configurationManager/bin folder.
You must create a copy of this file and edit the values. You can
customize this file based on the Configuration Manager operations
you intend to use. The following section describes the properties
and values required.
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.
-
Use
the property file cli_propertyFile_template.txt file as a 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
[aem-forms root]
/configurationManager/bin/ConfigurationManager.bat/sh file,
the userValuesForCLI.properties file is created in the
[aem-forms 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
.
Note:
The
following modules depend on ALC-LFS-ContentRepository. If you are using
the cli_propertyFile_template.txt as template then either remove
the ALC-LFS-ContentRepository from excludedSolutionComponents list
or add the following LFS in excludedSolutionComponents list:
-
ALC-LFS-ProcessManagement
-
ALC-LFS-CorrespondenceManagement
-
ALC-LFS-ContentRepository
-
ALC-LFS-MobileForms
-
ALC-LFS_FormsManager
8.3 General configuration properties
8.3.1 Common properties
Common properties are:
WebLogic and WebSphere specific properties:
Required
for the Configure Application Server, Deploy AEM forms on JEE, Validate
Application Server Topology and Validate Application Server Configurations
operations.
AEM forms on JEE Server specific properties:
Required
for the Initialize AEM forms on JEE and Deploy AEM forms on JEE
Components operations.
These properties are required for the following operations:
Property
|
Values
|
Description
|
targetServer.topologyType
|
server or cluster
|
The type of application server topology
for which you are deploying AEM forms on JEE.
|
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 application
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.
|
localServer.appServerRootDir
|
Default:
(Windows) C:\Program Files\IBM\
WebSphere\AppServer
(Linux, Solaris) /opt/IBM/WebSphere/AppServer
(AIX)
/usr/IBM/WebSphere/AppServer
|
The root directory of the application server instance
that you are configuring locally (on which you plan to deploy AEM
forms on JEE or that you will use to communicate with a remote server
on which you plan to deploy AEM forms on JEE).
|
AEM forms on JEE Server specific properties
|
LCHost
|
String
|
The hostname of the server where AEM forms
on JEE will be deployed.
|
LCPort
|
Integer
|
The web port number where AEM forms on JEE 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
ALC-LFS-CorrespondenceManagement,
ALC-LFS-ContentRepository,
ALC-LFS-MobileForms,
ALC-LFS_FormsManager
|
(Optional) List the AEM forms on JEE modules you
do not want to configure. Specify the excluded modules in a comma
separated list.
|
includeCentralMigrationService
|
true: to include service
false: to
exclude servcie
|
The property to include or exclude Central Migration
Bridge Service.
|
CRX Content repository
The following
properties are specified in the
cli_propertyFile_crx_template.txt
file.
|
true:
false:
|
|
contentRepository.rootDir
|
|
Path of the CRX repository.
|
use.crx3.mongo
|
true: false:
|
If you have performed a fresh installation,
to use Mongo DB with CRX3 set value to true. If the value is false
CRX3 TAR is configured.
|
mongo.db.uri
|
<URI of Mongo DB>
|
If you are using Mongo DB, set URI of Mongo
DB
|
mongo.db.name
|
<name of Mongo DB>
|
If you are using Mongo DB, provide name
of Mongo DB instance
|
8.3.2 Configure AEM forms on JEE properties
These properties only apply to the configure AEM forms
on JEE operation.
Property
|
Values
|
Description
|
AdobeFontsDir
|
String
|
Location of the Adobe server fonts directory.
This
path must be accessible from the server being deployed to.
|
customerFontsDir
|
String
|
Location of the customer fonts directory.
This
path must be accessible from the server being deployed to.
|
systemFontsDir
|
String
|
Location of the system fonts directory.
This
path must be accessible from the server being deployed to.
|
LCTempDir
|
String
|
Location of the temporary directory.
This
path must be accessible from the server 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.
This
path must be accessible from the server 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.
|
8.3.3 Configure or validate application server properties
8.3.3.1 Configure or Validate WebSphere properties
The Configuration Manager can configure or validate your
WebSphere application server as required by AEM forms on JEE.
These properties apply to the following operations:
-
Configure Application Server
-
Validate Application Server Topology
-
Validate Application Server Configurations
-
Validate Database Connectivity
8.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:
2048
|
The maximum heap size, in MB, for the JVM.
|
WebLogic and WebSphere Cluster only
|
cache.useUDP
|
true
|
Set the value to
true
if
AEM forms on JEE uses UDP to implement caching.
Set to
false
if
AEM forms on JEE 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.
|
Datasource configuration
|
datasource.dbType
|
Choose:
|
The type of database configured to use with
AEM forms on JEE.
|
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 AEM forms on JEE will
use when communicating with the database.
|
datasource.dbUser
|
String
|
The user ID AEM forms on JEE 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 the server being configured.
|
datasource.local.driverPath
|
String
|
Local JDBC driver. This value is used for
testing direct database connection.
|
8.3.4 Deploy AEM forms on JEE properties
These Deploy AEM forms on JEE properties only apply to
the deploy AEM forms on JEE operation.
Property
|
Values
|
Description
|
For more information, see
8.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.
|
targetServer.virtualHost
|
String
|
Virtual host of your WebSphere application server.
The
default values are admin_host, default_host, proxy_host.
|
8.3.5 Initialize AEM forms on JEE properties
These initialize AEM forms on JEE properties only apply
to the initialize AEM forms on JEE operation.
8.3.6 Deploy AEM forms on JEE Components properties
These properties apply to the following operations:
-
Deploy AEM forms on JEE Components
-
Validate AEM forms on JEE Component Deployment
-
Validate AEM forms on JEE Server.
Property
|
Values
|
Description
|
You must configure the AEM forms on JEE Server Information section. For more information, see
Common
properties
|
LCAdminUserID
|
String
|
The user ID to assign to the AEM forms on
JEE Administrator user. This User ID is used to login to the Administrator
Console.
|
LCAdminPassword
|
String
|
The password to assign to the AEM forms
on JEE Administrator user. This password is used to login to the
Administrator Console.
|
8.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 AEM forms on JEE Server is installed.
|
LCPort
|
Integer
|
Port number where AEM forms on JEE application
server is configured
|
LCAdminUserID
|
String
|
The user ID to assign to the AEM forms on
JEE Administrator user. This User ID is used to login to the Administrator
Console.
|
LCAdminPassword
|
String
|
The password to assign to the AEM forms
on JEE 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 AEM forms on JEE
|
LCServerMachineAdminUserPasswd
|
String
|
The password of the Administrator user of
the Operation System hosting AEM forms on JEE
|
8.3.8 Configure Connector for IBM Content Manager
Property
|
Values
|
Description
|
LCHost
|
String
|
Hostname where AEM forms on JEE Server is installed.
|
LCPort
|
Integer
|
Port number where AEM forms on JEE application
server is configured
|
LCAdminUserID
|
String
|
The user ID to assign to the AEM forms on
JEE Administrator user. This User ID is used to login to the Administrator
Console.
|
LCAdminPassword
|
String
|
The password to assign to the AEM forms
on JEE Administrator user. This password is used to login to the
Administrator Console.
|
jndiPortNumber
|
String
|
JNDI port corresponding to AEM forms on
JEE 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 AEM forms on JEE)
|
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).
|
8.3.9 Configure Connector for IBM FileNet
Property
|
Values
|
Description
|
LCHost
|
String
|
Hostname where AEM forms on JEE Server is installed.
|
LCPort
|
Integer
|
Port number where AEM forms on JEE application
server is configured
|
LCAdminUserID
|
String
|
The user ID to assign to the AEM forms on
JEE Administrator user. This User ID is used to login to the Administrator
Console.
|
LCAdminPassword
|
String
|
The password to assign to the AEM forms
on JEE Administrator user. This password is used to login to the
Administrator Console.
|
jndiPortNumber
|
String
|
JNDI port corresponding to AEM forms on
JEE 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 AEM forms on JEE)
|
ConfigureFilenetCE
|
true or false
|
Specify true to configure Connector for
IBM Filenet
|
FilenetConfigureCEVersion
|
String
|
The FileNet client version to configure.
Specify FilenetClientVersion5.0 or FilenetClientVersion5.2
|
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
|
8.3.10 Configure Connector for EMC Documentum
Property
|
Values
|
Description
|
LCHost
|
String
|
Hostname where AEM forms on JEE Server is installed.
|
LCPort
|
Integer
|
Port number where AEM forms on JEE application
server is configured
|
LCAdminUserID
|
String
|
The user ID to assign to the AEM forms on
JEE Administrator user. This User ID is used to login to the Administrator
Console.
|
LCAdminPassword
|
String
|
The password to assign to the AEM forms
on JEE Administrator user. This password is used to login to the
Administrator Console.
|
jndiPortNumber
|
String
|
JNDI port corresponding to AEM forms on
JEE 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 AEM forms on JEE)
|
ConfigureDocumentum
|
true or false
|
Specify true to configure Connector for
EMC Documentum
|
DocumentumClientVersion
|
String
|
The EMC Documentum client version to configure.
Specify DocumentumClientVersion6.7 or DocumentumClientVersion7.0
|
DocumentumClientPathDirectory
|
String
|
Location of EMC Documentum 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
|
8.3.11 Configure Connector for Microsoft SharePoint
Property
|
Values
|
Description
|
LCHost
|
String
|
Hostname where AEM forms on JEE Server is installed.
|
LCPort
|
Integer
|
Port number where AEM forms on JEE application
server is configured
|
LCAdminUserID
|
String
|
The user ID to assign to the AEM forms on
JEE Administrator user. This User ID is used to login to the Administrator
Console.
|
LCAdminPassword
|
String
|
The password to assign to the AEM forms
on JEE Administrator user. This password is used to login to the
Administrator Console.
|
jndiPortNumber
|
String
|
JNDI port corresponding to AEM forms on
JEE 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 AEM forms on JEE)
|
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
|
ConnectionString
|
String
|
Additional arguments used in the connection string
to connect to the Sharepoint Server(optional
|
8.3.12 Command Line Interface Usage
Once you have configured your property file, you must navigate
to the
[AEM forms on JEE root]
/configurationManager/bin folder.
To view a complete description of the Configuration Manager CLI
commands, type:
ConfigurationManagerCLI help
<command name>
.
8.3.12.1 Configure AEM forms on JEE CLI Usage
The Configure AEM forms on JEE operation requires the following
syntax:
configureLiveCycle -f
<propertyFile>
Where:
8.3.12.2 Configure CRX CLI Usage
The Configure CRX Repository requires the following syntax:
configureCRXRepository -f
<propertyFile>
Where:
8.3.12.3 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.
8.3.12.4 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.
8.3.12.5 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.
8.3.12.6 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.
8.3.12.7 (WebSphere and Weblogic Only) Deploy AEM forms on JEE CLI Usage
The Deploy AEM forms on JEE 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 AEM
forms on JEE operation.
8.3.12.8 Manually deploy configured EAR files
8.3.12.9 Initialize AEM forms on JEE CLI Usage
The initialize AEM forms on JEE operation requires the
following syntax:
initializeLiveCycle -f
<propertyFile>
Where:
8.3.12.10 Validate AEM forms on JEE Server CLI Usage
The Validate AEM forms on JEE 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.
8.3.12.11 Deploy AEM forms on JEE Components CLI Usage
The Deploy AEM forms on JEE 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.
8.3.12.12 Validate AEM forms on JEE Component Deployment CLI Usage
The Validate AEM forms on JEE 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.
8.3.12.13 Check system readiness for PDF Generator
The Checking system readiness for PDF Generator operation
requires the following syntax:
pdfg-checkSystemReadiness
8.3.12.14 Adding administrator user for PDF Generator
The adding administrator user for PDF Generator operation
requires the following syntax:
pdfg-addAdminUser -f
<propertyFile>
Where:
8.3.12.15 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
[aem-forms root]
\configurationManager\bin\
directory.
Perform
the following steps manually to complete the configuration for Connector
for IBM Content Manager.
-
Copy
the
adobe-component-ext.properties
file from
[aem-forms root]
/configurationManager/configure-ecm/websphere
to the following [appserver root]/profiles/[profile_name] directory.
-
Restart the Application Server.
-
Start the following services from Administration Console
-
IBMCMAuthProviderService
-
IBMCMConnectorService
8.3.12.16 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
[aem-forms root]
\configurationManager\bin\
directory.
Perform the following steps manually to complete the configuration
for Connector for IBM Content Manager.
-
Copy
the
adobe-component-ext.properties
file from
[aem-forms root]
/configurationManager/configure-ecm/websphere
to the following [appserver root]/profiles/[profile_name] directory.
-
Locate
the wsjass.conf file in the [appserver root]/profiles/[profile name]/properties
directory and add to it contents of wsjass.conf file available in
[aem-forms root]/configurationManager/configure-ecm/websphere directory.
-
Restart the Application Server.
-
Start the following services from Administration Console
-
IBMFileNetAuthProviderService
-
IBMFileNetContentRepositoryConnector
-
IBMFileNetRepositoryProvider
-
IBMFileNetProcessEngineConnector(If configured)
8.3.12.17 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
[aem-forms root]
\configurationManager\bin\
directory.
Perform the following steps manually to complete the configuration
for Connector for EMC Documentum.
-
Copy
the
adobe-component-ext.properties
file from
[aem-forms root]
/configurationManager/configure-ecm/websphere
to the following [appserver root]/profiles/[profile_name] directory.
-
Restart the Application Server.
-
Start the following services from Administration Console
-
EMCDocumentumAuthProviderService
-
EMCDocumentumRepositoryProvider
-
EMCDocumentumContentRepositoryConnector
8.3.12.18 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
[aem-forms root]
\configurationManager\bin\
directory.
8.4 Examples Usage
From the C:\Adobe\Adobe_Experience_Manager_forms\configurationManager\bin,
type:
ConfigurationManagerCLI configureLiveCycle -f cli_propertyFile.txt
Where
cli_propertyFile.txt
is the name of the property
file you created.
8.5 Configuration Manager CLI Logs
If an error occurs, you can review the CLI logs located
here in the
[aem-forms 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.
8.6 Next steps
If you used Configuration Manager CLI to configure and
deploy AEM forms on JEE, you can now do the following tasks:
|
|
|