Deploy changes to an existing application

This sample scenario takes you through the steps of updating application assets that were initially deployed in the First-time deployment of an application scenario. The first-time scenario shows how to deploy a set of sample FileNet® P8 assets from a source environment to a destination environment where the assets do not currently exist. In this scenario, the previously deployed assets now existing in the destination environment must be updated with subsequent changes made to the assets in the source environment. This update scenario assumes that the deployment configuration created in the First-time deployment of an application procedure exists, and that both the source and destination systems are available to the administrator.

The following sample scenario provides high-level deployment steps and illustrates each step with the actions of a third-person administrator.

Assets to be deployed

The following tables identify the authorized LDAP users for the source and destination systems, the source and destination object stores, and the FileNet P8 assets to be deployed.

LDAP users

Except for the Admin user, the authorized LDAP users for the source and destination environments are different. When the application was initially deployed, the administrator mapped the source security principals to the destination security principals.

Object stores

The source and destination environments each contain two object stores. In the First-time deployment of an application scenario, assets on SourceOS1 were deployed to DestinationOS1. In this scenario, the assets on DestinationOS1 must be updated with the modified assets on SourceOS1. The P8Demo object stores are not used for deployment.

FileNet P8 assets

The following FileNet P8 assets are stored on the source Content Platform Engine, unless otherwise noted. The Location column specifies the navigation path to the asset that uses Add Asset dialog box in FileNet Deployment Manager.

The assets are grouped by the FileNet P8 system that they support. Included in a Content Platform Engine installation are the core Content Platform Engine assets. The other assets support IBM® Content Navigator and workflow systems, which integrate with Content Platform Engine.

In this sample scenario, the assets to be deployed are customer invoice-related objects, most of which were previously deployed in the First-time deployment of an application scenario. As described in the following table, these objects were updated in the source environment. Security principals were removed for some of the objects. The deployment updates objects in the destination environment, and creates a property template added to the application since the initial deployment.

After the assets are imported to the destination environment, the assets in the list are deployed, except for the workflow definition and the workflow subscription. After you import the workflow definition and workflow subscription to the destination Content Platform Engine, the administrator must manually transfer the workflow definition to the destination workflow system. Then, the administrator must modify the workflow subscription configuration to use the transferred workflow definition.

FileNet Deployment Manager is used to deploy this sample set of assets.