From the command line, you can run each of the required
configuration XML files one file at a time. You must run each of the
required files to complete the Content Platform Engine configuration.
Before you begin
If you are running tasks for a profile that was created or
edited in the
Configuration Manager graphical
user interface, verify that the XML files contain values for the required
passwords before you attempt to run the configuration XML files. See
Handling passwords in Configuration Manager for more information.
About this task
You must run the configuration XML files for each of the
required configuration tasks:
- Apply the bootstrap properties file by using the configurebootstrap option.
If
your FileNet® P8 domain
uses multiple non-managed application servers, then you use a copy
of a single EAR file with the bootstrap settings on all the servers.
After you apply the bootstrap properties file on the initial server,
you copy the EAR file with the bootstrap settings to the profiles
directory on the additional servers. Then, when you run the tasks
for the additional servers, do not use the configurebootstrap option.
Only run the tasks for configuring the JDBC data sources for the global configuration database (GCD), configuring the JDBC
data sources for the object stores, and configuring the LDAP provider.
For
all other configurations, you can run all the tasks on each Content Platform Engine server.
- Choose
Licenses by using the configurepricingmodel option.
- Configure the JDBC Data Sources for the GCD by using
the configurejdbcgcd option.
- Configure the JDBC Data Sources for a single object
store database by using the configurejdbcos option.
- Configure the LDAP provider by using the configureldap option.
Oracle WebLogic Server only.
When you run the task using the
configureldap option,
the
weblogic.security.providers.authentication.DefaultAuthenticator.ControlFlag
value
is set to SUFFICIENT for authenticating users.
- Configure the login modules by using the configureloginmodules option.
Procedure
To
run the configuration XML files one file at a time:
- Change the current directory to ce_install_path/tools/configure, where ce_install_path is
the location where Content Platform Engine is
installed.
- Run the appropriate command for
the task that you need to complete. Do not type any line breaks when
you enter the command.
- Run the configurepricingmodel.xml file in
a profile with one configurepricingmodel task for
the licenses:
configmgr_cl execute -task configurepricingmodel -profile myprofile
- Run the configurejdbcos.xml file in a profile
with one configurejdbcos task:
configmgr_cl execute -task configurejdbcos -profile myprofile
- Run the configurejdbc.2.xml file in a profile
with multiple configurejdbcos tasks:
configmgr_cl execute -taskfile configurejdbc.2.xml
-profile myprofile
- Run the configureldap.xml file in a profile
with one configureldap task:
configmgr_cl execute -task configureldap -profile myprofile
- Run the configureldap.3.xml file in a profile
with multiple configureldap tasks:
configmgr_cl execute -taskfile configureldap.3.xml -profile myprofile
- Run the configureloginmodules.xml file:
configmgr_cl execute -task configureloginmodules -profile myprofile
- Run the configurebootstrap.xml file in a
profile with one configurebootstrap task:
configmgr_cl execute -task configurebootstrap -profile myprofile
Where:
- -taskfile task_file_name
- The -taskfile task_file_name parameter
specifies the configuration XML file to use.
If only one task file
exists for the task_type, then the -taskfile task_file_name parameter
is optional, but do not use the -task task_type parameter
with the -taskfile task_file_name parameter.
If
more than one task file for the task_type exists,
then you must include the -taskfile task_file_name parameter.
You can omit the -task task_type parameter
when you specify the -taskfile task_file_name parameter.
- -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".
Remember: The values that
you entered for the configurejdbcgcd task were for
the GCD data sources. You must edit and run the configurejdbcos task
once for each object store later in the installation process.
- If your FileNet P8 domain uses multiple non-managed application
servers, then copy the ce_install_path/ContentEngine/tools/configure/profiles/my_profile/ear/Engine-app_server_type.ear file
to the directory on each additional Content Platform Engine server.
- install_dir
- The location where Content Platform Engine is
installed.
- my_profile
- The directory for the Configuration Manager profile that
you created.
- Engine-app_server_type.ear
- The
EAR file for your application server type: Engine-ws.ear, Engine-wl.ear, Engine-jb.ear, Engine-jbc.ear,
or Engine-jb6eap.ear.
Important: For each additional non-managed
server, only run the tasks for configuring the JDBC data sources for
the GCD, configuring the JDBC data sources for the object stores,
and configuring the LDAP provider. When you run the tasks for the
additional servers, do not use the configurebootstrap option
on the additional servers.
- Repeat this procedure as needed to run one of the other
configuration XML files until you run the files for each of the four
required tasks on this server.
Results
The task execution status messages are displayed.