Generating the deployapplication.xml file

The deployapplication.xml file contains settings for deploying the Content Platform Engine application. You must use the generateConfig command to create the XML file.

About this task

The deployapplication.xml file is created when you generate all files at the same time or when you generate the deployapplication task. If you generated all the files at the same time, you already have deployapplication.xml file and you a can skip this procedure.

To generate the deployapplication.xml file:

Procedure

  1. Log on to the application server as config_mgr_user, the user who will run Configuration Manager.
  2. Change the current directory to ce_install_path/tools/configure , where ce_install_path is the location where is Content Platform Engine is installed.
  3. Enter the following command without line breaks to generate the deployapplication.xml file: 
    configmgr_cl generateconfig -appserver app_server_type -deploy deploy_type
 -task deployapplication -profile myprofile
    Where:
    -appserver appserver_name
    The -appserver appserver_type specifies the type of application server and must be WebSphere or WebLogic.
    -deploy deploy_type
    The -deploy deploy_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 deployapplication option. This parameter specifies the type of Content Platform Engine deployment. The value must be 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 not managed or clustered) WebSphere® Application Server or Oracle WebLogic Server.

    Specify cluster if you are deploying Content Platform Engine to a WebSphere Application Server or Oracle WebLogic Server cluster.

    Specify netdeploy if you are deploying Content Platform Engine to a managed WebSphere 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.cfgp" or /opt/IBM/FileNet/ContentEngine/tools/configure/profiles/ce_was_tiv_db2/ce_was_tiv_db2.cfgp.
    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.cfgp".