The generateconfig command generates the configuration XML file for the specified configuration task. The command name is not case sensitive.
The following syntax includes line breaks to format the command for reading. Enter the command and options on a single line, without any line breaks.
configmgr_cl generateconfig -appserver app_server_type -repositorytype ldap_repository_type -db database_type -ldap ldap_type -bootstrap bootstrap_operation -deploy deploy_type -task task_type -taskname display_name -profile myprofile [-silent] [-force] [-help]
Specify standard if you are deploying Content Engine to a stand-alone (that is, a server that is not managed or clustered) WebSphere Application Server, Oracle WebLogic Server, or JBoss Application Server.
Specify cluster if you are deploying Content Engine to a WebSphere Application Server, Oracle WebLogic Server, or JBoss Application Server cluster.
Specify netdeploy if you are deploying Content Engine to a managed WebSphere Application Server instance. That is, you are using Network Deployment to manage individual servers that are not necessarily in a cluster.
Option | Configuration file to generate | Description |
---|---|---|
omitted | applicationserver.xml configurebootstrap.xml configurejdbcgcd.xml configurejdbcos.xml configureldap.xml configureloginmodules.xml deployapplication.xml |
If you omit the -task task_type parameter and the -taskfile task_file_name parameter, then all the default configuration files for a profile are created. |
configurebootstrap | applicationserver.xml configurebootstrap.xml configurebootstrap.n.xml, where n is an integer starting with 2 |
Generates the file for the application server properties and the file with the settings for the Content Engine bootstrap on the application server. The bootstrap information is needed for creating the Global Configuration Data and for starting Content Engine When you generate a second bootstrap configuration file, it is named configurebootstrap.2.xml. The filename increments for each new file you generate. You cannot change the filename, but you can edit the value in the file for the name of the task. For example, you might must generate the initial bootstrap task for the new profile and then generate a second bootstrap task for modifying the EAR file to apply a fix pack. If the profile already contains an applicationserver.xml file, the existing file is retained. |
configurejdbcgcd | applicationserver.xml configurejdbcgcd.xml |
Generates the file for the application server properties and the file with the settings for configuring the JDBC connections to the Global Configuration Data (CGD) database used by Content Engine. If the profile already contains an applicationserver.xml file, the existing file is retained. |
configurejdbcos | applicationserver.xml configurejdbcos.xml configurejdbcos.n.xml, where n is an integer starting with 2 |
Generates the file for the application server properties and the file with the settings for configuring JDBC connections to a single object store database used by Content Engine. You need to generate, edit, and apply the configurejdbcos task settings for each object store in your database. When you generate a second object store JDBC configuration file, it is named configurejdbcos.2.xml. The filename increments for each new file you generate. You cannot change the filename, but you can edit the value in the file for the name of the task. If the profile already contains an applicationserver.xml file, the existing file is retained. |
configureldap | applicationserver.xml configureldap.xml configureldap.n.xml, where n is an integer starting with 2 |
Generates the file for the application server properties and the file for configuring the connection to the directory server for authenticating Content Engine users. (WebSphere Application Server or Oracle WebLogic Server only.) When you generate a second LDAP configuration file, it is named configureldap.2.xml. The filename increments for each new file you generate. You cannot change the filename, but you can edit the value in the file for the name of the task. JBoss does not support multiple LDAP tasks. If the profile already contains an applicationserver.xml file, the existing file is retained. |
configureloginmodules | applicationserver.xml configureloginmodules.xml |
(WebSphere Application Server or JBoss Application Server only.) Generates the file for the application server properties and the files for the login modules for the Content Engine application. If the profile already contains an applicationserver.xml file, the existing file is retained. |
deployapplication | applicationserver.xml deployapplication.xml |
Generates the file for the application server properties and the file with settings for deploying the Content Engine application on the application server. If the profile already contains an applicationserver.xml file, the existing file is retained. |
registerem | registerem.xml | Generates the file for registering or unregisteringEnterprise Manager from the Windows® Registry. |
The following examples include line breaks to format the command for reading. Enter the command and options on a single line, without any line breaks.
configmgr_cl generateconfig -appserver websphere -repositorytype standalone -db db2 -ldap tivoli -bootstrap new -deploy standard -profile wstdb2
configmgr_cl generateconfig -appserver websphere -repositorytype standalone -task configurejdbcos -profile wstdb2jdbc
configmgr_cl generateconfig -appserver websphere -repositorytype standalone -task configurejdbcos -taskname "Configure Object Store OS23 Data Sources" -profile wstdb2jdbc
configmgr_cl generateconfig -help