Deploying to Production

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

This procedure is specific to Process applications 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, and importing classes and metadata into the Content Engine object store.

  1. If you have not already done so, using the Process Task Manager, configure the Process Engine security connection. For information, see Configure Process Engine security.
  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 a superuser or a member of the fnadmin group to run vwtool. For information, see vwtool.
    2. Transfer the Process Engine database objects in each working development isolated region in either of two ways:
      • Use Process Configuration Console to duplicate the development isolated region in the (existing) production isolated region, by exporting and importing the development isolated region. For information on exporting and importing isolated regions, see Manage Isolated Regions.
      • Enter the following at the command line:
           vwtfer -o region_information.cdl -r n
        

        where region_information.cdl is user-defined (such as, developer_region.cdl) and n is the number assigned to 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:
         vwtool -r n
         config
      

      where n is the number assigned to the production isolated region.

  3. Using Process Designer, import the workflow definitions.
  4. 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 Enterprise Manager to update subscriptions.
  5. If you are deploying a P8-based application using FileNet Workplace, copy your Web application tree and move it and any Java™Server Pages (JSP) files to an appropriate location on the production Application Engine server. 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.