Content Platform Engine, Version 5.2

Deploying instances by using the graphical user interface

You can deploy a Content Platform Engine Server instance on the web application server by using the graphical user interface. Deploying makes the Content Platform Engine application available for use.

Be sure that you have available the Installation and Upgrade Worksheet that was completed during your planning activities.

Tip: For more information on the properties and values you set in the Configuration Manager, roll your mouse over the property name to view the hover help for the property.

To deploy Content Platform Engine:

Open your completed Installation and Upgrade Worksheet file.
Tip: In the worksheet file, verify that the Data > Filter > AutoFilter command is enabled. To view only Configuration Manager deployment values for this task, filter by CM: Deploy Application in the Installation or Configuration Program column.
Log on to the application server machine as config_mgr_user, which is the Configuration Manager user.

Start Configuration Manager.

Option	Description
AIX®, Solaris, HPUX, HPUXi, Linux, Linux on System z®	Type the following command: `ce_install_path`/tools/configure/configmgr where `ce_install_path` is the location where the Content Platform Engine server software is installed
Windows	Complete one of the following actions: Double-click the FileNet® Configuration Manager desktop shortcut. Select Start > All Programs > IBM® FileNet P8 Platform > FileNet Configuration Manager. Run `ce_install_path` \tools\configure\configmgr.exe. where `ce_install_path` is the location where the Content Platform Engine server software is installed

Option

Description

AIX®, Solaris, HPUX, HPUXi, Linux, Linux on System z®

Type the following command:

ce_install_path/tools/configure/configmgr

where ce_install_path is the location where the Content Platform Engine server software is installed

Windows

Complete one of the following actions:

Double-click the FileNet® Configuration Manager desktop shortcut.
Select Start > All Programs > IBM® FileNet P8 Platform > FileNet Configuration Manager.
Run ce_install_path \tools\configure\configmgr.exe.
where ce_install_path is the location where the Content Platform Engine server software is installed

Select File > Open Configuration Profile.
Enter the path to the profile for this Content Platform Engine instance, or click Browse to locate the profilename.cfgp profile file.
Click OK.
Right-click the Deploy Application task in the profile pane (left pane), and select Edit Selected Task.
Provide the property values for your deployment by using the values in your worksheet.
(Application server cluster configurations only) Make sure the following settings are used in a high availability environment using cluster configurations:
Deployment type

Verify that Deployment type is set to Cluster.

Application server name

Enter the name of the highly available cluster that you have configured.
This configures the global configuration database (GCD) data sources and security settings at the administrative level so that all cluster nodes have access to this vital configuration information.

Restriction: JBoss Application Server clusters do not have an administrative server. When installing Content Platform Engine choose a single JBoss Application Server node on which to install Content Platform Engine, then copy the necessary files to the rest of the nodes in the cluster. To deploy a Content Platform Engine instance on each additional JBoss Application Server in your cluster, follow the instructions for deploying Content Platform Engine to additional JBoss servers in a cluster.
Select File > Save.
Enable the task. When the task is disabled, the task name includes the text (Disabled). To enable the task, select Deploy Application (Disabled) in the profile pane, and then either right-click and choose Enable Selected Task from the context menu, or click the Enable the Selected Task icon in the task toolbar.
Right-click the Deploy Application task in the left pane, and select Run Task .
Running the deploy task might take several minutes. The task status messages are displayed in the Console pane below the deploy application properties.