Deploying to Production

To deploy your Process application from your development system to a production site, use the following procedure:

Note This procedure is Process application-specific and assumes you have already completed other steps for deploying applications to production, such as configuring users and groups in your LDAP directory service, importing object definitions, setting security on object definitions, importing classes and metadata into the Content Engine object store, and so on. For additional information and a description of all the steps needed for deploying a FileNet P8 Platform application to production, see "Deploying a Solution" in the FileNet P8 Developer's Roadmap.

  1. If you have not already done so, using the Process Task Manager, configure the Process Engine connection to the LDAP directory service (either Active Directory or SunONE) and assign a unique user ID to each of the users in the LDAP directory service (User IDs must be assigned before the users can access the Process Engine). Note that you must be a member of the Domain Admins group to configure the connection. For information, see Configuring the LDAP Connection.
  2. Move the Process queues from the development isolated region to the production Process Engine isolated region, as follows:
    1. Create a .cdl file by running the vwtool dump command at the command line. Note that you must be root or a member of the fnadmin group (i.e., have SysAdmin permissions) to run vwtool. For information, see Help for vwtool.
    2. Transfer the Process Engine database objects in each working development isolated region in either of two ways:
      • Use the Process Configuration Console to copy the development isolated region to the production isolated region (must already have been created). For information, see the Process Configuration Console topic, Copy an Isolated Region.
      • Or by entering the following at the command line:
        vwtfer -o <region information>.cdl -r n

        where <region information>.cdl is user-defined (for example: developer_region.cdl) and n is the number of the production isolated region.

      Caution vwtfer is an undocumented system support tool. If not used correctly, it can be destructive and should not be used without FileNet support assistance.

    3. Check the properties of the production isolated region configuration using vwtool. For example:
  3. vwtool -r n
    config
    where n is the number of the production isolated region.
  4. Using the Process Designer, import the workflow definitions.
  5. Update subscriptions (the version number of a workflow definition is contained in the Content Engine VWVersion property). If you are deploying a P8-based application using FileNet Workplace, use the Enterprise Manager to update subscriptions. For information, see "Deploying a Solution" in the FileNet P8 Developer's Roadmap.
  6. If you are deploying a P8-based application using FileNet Workplace, copy your web application tree and move it and any .JSP files to an appropriate location on the production Application Engine. Similarly, to deploy an application using FileNet Web Services or FileNet Open Client, copy your web application tree and any associated files to the production server. For additional information, see "Deploying Java Applications/Applets" and/or "Deploying a Solution" in the FileNet P8 Developer's Roadmap.