You must create the JDBC data sources for each
object store that Content Engine uses.
You must generate, edit, and execute a new configurejdbc-os.xml file
for each object store in your environment.
Be sure that you have available
the Installation and Upgrade Worksheet that was completed during your
planning activities.
If you generated all of the configuration profiles
at the same time, you have already created an initial configurejdbc-os.xml file
for the initial object store data sources. If you have an existing configurejdbc-os.xml file,
you can generate another file for each additional object store. Each
additional file that you add is named configurejdbc-os.n.xml.
You can generate multiple configurejdbc-os.n.xml files
as needed, depending on the number of object stores in your environment.
For best results, create an additional file for each object store.
- Open your completed Installation and Upgrade Worksheet
file.
Tip: In the worksheet file, verify
that the command is enabled.
To view only Configuration Manager values for this task, filter by CM:
Configure Object Store JDBC Data sources (object store 1) in
the Installation or Configuration Program column.
- Log on to the application server as config_mgr_user,
the user who runs Configuration Manager.
- If you did not
generate all the configuration files at the same time or if you must
create another file, generate the configurejdbc-os.n.xml file
by running the following command:
configmgr_cl generateConfig -appserver app_server_type -db db_type
-task configurejdbcos -profile myprofile
where:
- -appserver appserver_name
- The -appserver appserver_type specifies
the type of application server and must be WebSphere®, WebLogic, or JBoss.
- -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 or configurejdbcos option.
This parameter specifies the type of database to be used by Content Engine and must
be mssql, oracle, oracle_rac, db2,
or db2zos.
- -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 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 absolute 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".
- Use a text editor to open the configurejdbc-os.n.xml file
and edit it as follows:
- Provide the entries that are required for your environment
by using the values in your worksheet.
- Replace each occurrence of ****INSERT VALUE**** with
a value appropriate for your site. See the descriptions in the file
for more information.
- Verify that the default values for the remaining properties
are correct for your site.
- Set the enabled attribute value
in the <configuration> tag to true so
that you can run the configuration task in 6.
- Save your edits.
- Run the storepasswords command to encrypt
and store the required passwords.
configmgr_cl storepasswords -profile myprofile
Tip: If the storepasswords command
prompts you to store passwords in configuration files on disk, you
must respond with yes or no (instead
of y or n).
- Run the following
command to execute the configurejdbc.n.xml file:
configmgr_cl execute -task configurejdbcos -profile myprofile
- Optional: Check the completion status by running
the following command:
configmgr_cl checkStatus -task configurejdbcos -task configurejdbc.n.xml
-profile myprofile
Where configurejdbc.n.xml is
the task file for the object store.
- Repeat 3 through 6 as needed for each
additional object store.