From the command line, you can generate all of the required
configuration XML files for Content Platform Engine at
the same time with a single command.
About this task
When you run
the generateconfig command, all the required configuration
XML files are created.
Procedure
To generate
all the configuration XML files at the same time:
- Log on to the Content Platform Engine server as config_mgr_user,
the user who runs Configuration Manager.
- Change the current directory
to ce_install_path/tools/configure,
where ce_install_path is the location where the Content Platform Engine software is installed.
- Run the following command. Do not
type any line breaks when you enter the command.
- WebSphere® Application
Server
configmgr_cl generateconfig -appserver app_server_type
-license license_type
-repositorytype ldap_repository_type
-db db_type -ldap ldap_type
-bootstrap bootstrap_operation
-deploy deploy_type -profile myprofile
- Oracle WebLogic Server
configmgr_cl generateconfig -appserver app_server_type
-license license_type
-db db_type -ldap ldap_type
-bootstrap bootstrap_operation
-deploy deploy_type -profile myprofile
- JBoss Application Server
configmgr_cl generateconfig -appserver app_server_type
-appserverVersion app_server_version
-license license_type
-db db_type -ldap ldap_type
-bootstrap bootstrap_operation
-deploy deploy_type -profile myprofile
Where:
- -appserver appserver_name
- The -appserver appserver_type parameter
specifies the type of application server and must be WebSphere, JBoss, or WebLogic.
- -appserverVersion appserverVersion
- JBoss Application Server only. The -appserverVersion appserverVersion parameter
specifies the JBoss Application Server version.
The valid values are 5.x_EAP and 5.x_AS.
- -license license_type
- The -license license_type parameter
specifies the type of license and must be UVU, "PVU
Production", or "PVU Non-Production". Note
that the parameter value must be delimited by double quotes (") if
it contains embedded blanks.
- -repositorytype ldap_repository_type
- WebSphere Application
Server only. The -repositorytype ldap_repository_type parameter
specifies the type of LDAP repository to use and must be standalone or federated.
- -db database_type
- The -db database_type parameter
is required only when you are generating all the files at the same
time or when you are generating a single file by using the configurejdbcgcd option
or the configurejdbcos option. This parameter specifies
the type of database to be used by Content Platform Engine and must be mssql, oracle, oracle_rac, db2, db2zos,
or db2pshadr.
- -ldap ldap_type
- The -ldap ldap_type parameter
is required only when you are generating all the files at the same
time or when you are generating a single file by using the configureldap option.
This parameter specifies the type of directory service repository
that Content Platform Engine uses
for authenticating users and must be activedirectory, adam, ca, edirectory, oid, oracledirectoryse,
or tivoli. The adam value applies
to both Microsoft ADAM
and AD LDS.
- -bootstrap bootstrap_operation
- The -bootstrap bootstrap_operation parameter
is required only when you are generating all the files at the same
time or when you are generating a single file by using the configurebootstrap option.
This parameter specifies the bootstrap and text extraction operation
for the profile and must be new, modify,
or upgrade.
- -deploy deploy_type
- The -deploy deploy_type parameter
is required only when you are generating all the files at the same
time or when you are generating a single file by using the deployapplication option.
This parameter specifies the type of Content Platform Engine deployment. The value
must be standard, cluster, or netdeploy (network
deployment).
Specify standard if you are deploying Content Platform Engine to a stand-alone (that
is, a server that is neither managed nor clustered) WebSphere Application
Server, JBoss Application Server or Oracle WebLogic Server.
Specify cluster if
you are deploying Content Platform Engine to
a WebSphere Application
Server, JBoss Application Server or Oracle WebLogic Server cluster.
Specify netdeploy if
you are deploying Content Platform Engine to
a managed WebSphere Application
Server instance.
That is, you are using Network Deployment to manage individual servers
that are not in a cluster.
- -profile myprofile
- The -profile myprofile parameter
specifies the profile to use. The myprofile value
can be one of the following items:
- The name of the profile, such as ce_was_tiv_db2. The profile must
be located in the ce_install_path/tools/configure/profiles directory,
where ce_install_path is the location where the Content Platform Engine software is installed.
- The absolute path to the profile directory, such as "C:\Program
Files\IBM\FileNet\ContentEngine\tools\configure\profiles\ce_was_tiv_db2" or /opt/IBM/FileNet/ContentEngine/tools/configure/profiles/ce_was_tiv_db2.
- The fully qualified path to the profile input file, such as "C:\Program
Files\IBM\FileNet\ContentEngine\tools\configure\profiles\ce_was_tiv_db2\ce_was_tiv_db2.cfg" or /opt/IBM/FileNet/ContentEngine/tools/configure/profiles/ce_was_tiv_db2/ce_was_tiv_db2.cfg.
Remember: If the path includes a directory name with
spaces, enclose the entire path in quotation marks. For example, enter "C:\Program
Files\IBM\FileNet\ContentEngine\tools\configure\profiles\ce_was_tiv_db2\ce_was_tiv_db2.cfg".
Example
For example,
the following command generates all the configuration XML files for
a new installation profile for a standard deployment on WebSphere with IBM®
Tivoli® Directory Server that uses a stand-alone
LDAP repository and DB2® in
the ce_install_path/tools/configure/profiles/wstdb2 directory:
configmgr_cl generateconfig -appserver WebSphere
-license "PVU Production"
-repositorytype standalone -db db2 -ldap tivoli
-bootstrap new -deploy standard -profile wstdb2