You can deploy
an upgraded Content Engine instance
on a web application
server by using the command-line version of Configuration Manager. Deploying makes
the Content Engine application
available for use.
Ensure that the application server is running or stopped:
Table 1. Required Application Server StateOption |
Description |
WebSphere® Application
Server |
Start the application server if it is not already
running. |
JBoss Application Server |
Stop the application server. |
WebLogic Server |
Start the application server if it is not already
running. |
Important: When deploying
Content Engine in a highly available environment
you must specify the cluster as the deployment target.
See Configuration Manager command-line reference for syntax details.
To deploy a
Content Engine instance from the command
line:
- Log on to the application server machine as the config_mgr_user user,
which is the Configuration Manager user.
- If you upgraded the version
of your application server, or if you moved it to a new directory
or device and then redeployed Content Engine before
upgrading Content Engine to version
5.0.0 from version 4.0.1, 4.5.0, or 4.5.1, perform the following substeps:
- Open the applicationserver.xml file
for editing.
- Correct any obsolete parameter values for your application
server type.
- Save your edits.
- Set the current directory to ce_install_path/tools/configure, where
ce_install_path is the path
where you installed Content Engine.
- Run the following command to apply the settings in the deployapplication.xml file:
configmgr execute -task deployapplication -profile myprofile
where 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".
- Optional: Run the following command to check
the completion status of the DeployApplication task.
configmgr checkstatus -task deployapplication -profile myprofile
- Repeat this procedure as needed to deploy any additional Content Engine instances.