You can configure an upgraded Content Platform Engine instance on a web application
server by using the command-line version of Configuration Manager.
Before you begin
Ensure that you have the required accounts and appropriate permissions before you
begin.
Procedure
To configure the upgraded Content Platform Engine instance:
- On the machine where Content Platform Engine is installed, log on
as config_mgr_user, the Configuration Manager user.
- Change the current directory to ce_install_path/tools/configure. ce_install_path is
the path where you installed Content Platform Engine.
For example, ce_install_path might be /opt/FileNet/ContentEngine.
- From the command line, run the generateupgrade command to generate the
upgrade profile.
Important: If
you are upgrading from version 4.5.1, be aware that Configuration Manager retains your version 4.5.1 profile. That is, Configuration Manager uses the existing version 4.5.1 profile to deploy
Content Platform Engine. It does not create a new profile and it modifies
only the applicationserver.xml file.
Enter the command on one line without line breaks:configmgr_cl generateupgrade [-appserver app_server_type] -server server_name
[-deploy deploy_type] -profile myprofile [-silent] [-force] [-help]
Where:
- -server
server_name
- The -server
server_name parameter indicates the server to create the upgrade profile for. Use
the listservers command to display a list of valid server_name
values from the Servers.xml file before you run the
generateupgrade command.
- -appserver
appserver_type
- The -appserver
appserver_type parameter is required only if the
ce_install_path/Servers.xml file does not exist or does not
contain any servers. This parameter specifies the type of application server and must be one of the
following values: WebSphere, WebLogic, or
JBoss.
- -deploy
deploy_type
- The -deploy
deploy_type parameter is required only if the
ce_install_path/Servers.xml file does not exist or does not
contain the deployment type for the selected server. This parameter specifies the type of Content Platform Engine deployment. If a value for the deployment type exists in the
Servers.xml file for the selected server, then the value from the
Servers.xml file is used instead the value you specify on the command
line.
Select one of the following values: 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, Oracle WebLogic Server, or JBoss Application Server.
Specify
cluster if you are deploying Content Platform Engine
to a WebSphere Application
Server, Oracle WebLogic Server, or
JBoss Application Server cluster
Specify netdeploy if you are deploying
Content Platform Engine to a managedWebSphere 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 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".
- -silent
- The -silent parameter is optional. When -silent is
specified, then no prompts or informational messages are displayed
in the console, but the errors are written to the log. Failure messages
and validation error messages are displayed as needed, such as messages
about missing passwords or invalid port numbers. If you run the execute command
to run all the tasks in a profile, and you specify the -silent parameter,
you must also specify the -force parameter.
- -help
- The -help parameter is optional and displays
a brief message on the command syntax instead of running the command.
The upgrade.xml file and one directory named for each existing Content Platform Engine instance is created in the profile directory.
- You must verify or edit the contents of applicationserver.xml file,
depending on how you run the generateupgrade command:
- If you run the command interactively, respond to the command prompts
to verify all the property values in the applicationserver.xml file.
- If you run the command silently, it creates a new applicationserver.xml file
with the property values from the existing profile. You must then
edit the property values in the file to match your upgraded environment.
Then run the storepasswords command, which prompts
you (respond with yes or no)
to choose whether to encrypt and store the web application server
administrator password to the applicationserver.xml file.
- Verify and edit the application server properties for each Content Platform Engine instance directory
that was created to match your upgraded environment as needed.
- If you are upgrading FileNet® P8 from a version prior to 5.2.0,
run the execute command from the command line to configure the Process Engine JDBC data sources:
configure_cl execute -task configurejdbcos -profile myprofile
- From the command line, run the execute command to configure the bootstrap
properties.
configmgr_cl execute -task configurebootstrap -profile myprofile
- (WebSphere and JBoss Application Server
only) If you are upgrading Content Engine from version 4.5.1, run the
execute command from the command line to configure the login modules:
configmgr_cl execute -task configureloginmodules -profile myprofile
- Run the execute command from the command line to configure LDAP:
configmgr_cl execute -task configureldap -profile myprofile
- Optional: From the command line, check the completion status of the task by running the
checkStatus command.
configmgr checkStatus -task configurebootstrap -profile myprofile