Deploy changes to an existing application

Sample scenario of how an administrator can take steps to update application assets that are already deployed.

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 Content Cortex 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 Content Cortex 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.

LDAP Source	Object Name
SourceGroup1 SourceGroup2 SourceGroup3 SourceGroup4 SourceGroup5	SourceGroup1 SourceGroup2 SourceGroup3 SourceGroup4 SourceGroup5
Admin	Admin
SourceUser1 SourceUser2 SourceUser3 SourceUser4 SourceUser5	SourceUser1 SourceUser2 SourceUser3 SourceUser4 SourceUser5

LDAP Destination	Object Name
DestinationGroup1 DestinationGroup2 DestinationGroup3 DestinationGroup4 DestinationGroup5	DestinationGroup1 DestinationGroup2 DestinationGroup3 DestinationGroup4 DestinationGroup5
Admin	Admin
DestinationUser1 DestinationUser2 DestinationUser3 DestinationUser4 DestinationUser5	DestinationUser1 DestinationUser2 DestinationUser3 DestinationUser4 DestinationUser5

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.

Source Object Store	Destination Object Store
P8Demo	P8Demo
SourceOS1	DestinationOS1

Content Cortex assets

The following Content Cortex 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 Content Cortex 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.

Content Platform Engine Core	Object Name	Content Platform Engine Object Type	Source LDAP Assignment	Destination LDAP Assignment	Location
1 new property template (which is displayed on the Invoice class definition)	InvoiceCustNameChar_PropTemplate	Property Template	SourceGroup1 SourceGroup2 Admin	DestinationGroup1 DestinationGroup2 Admin	Object Stores > SourceOS1 > Data Design > Property Templates
Updated Invoice document class definition with new property from InvoiceCustNameChar_PropTemplate	Invoice_DocClass v2	Document Class	SourceGroup1 SourceGroup2 Admin The following security principals are removed: SourceGroup3 SourceGroup4 SourceGroup5	DestinationGroup1 DestinationGroup2 Admin The following security principals are removed: DestinationGroup3 DestinationGroup4 DestinationGroup5	Object Stores > SourceOS1 > Data Design > Classes > Document
Updated folder of type CustomerInvoices with new title	Customer Invoices Folder v2	Folder	SourceGroup1 SourceGroup2 Admin The following security principals are removed: SourceGroup3 SourceGroup4 SourceGroup5	DestinationGroup1 DestinationGroup2 Admin The following security principals are removed: DestinationGroup3 DestinationGroup4 DestinationGroup5	Object Stores > SourceOS1 > Browse > Root Folder > Customer Invoices Folder v2
Changed document of type Invoice (in-place property value change - new title, not a new version)	Invoice Document	Document	SourceGroup1 SourceGroup2 Admin	DestinationGroup1 DestinationGroup2 Admin	Object Stores > SourceOS1 > Browse > Root Folder > Customer Invoices Folder v2
Updated workflow definition document, with workflow step name changed from Activity to Activity (v2) - new version of document	InvoiceWorkflowDefinition v2	Workflow Definition	SourceGroup3 SourceGroup4 Admin	DestinationGroup3 DestinationGroup4 Admin	Object Stores > SourceOS1 > Browse > Root Folder > Customer Invoices Folder v2
1 workflow subscription, which is updated to point to the new version of the workflow definition	InvoiceWorkflowSubscription v2	Workflow Subscription	SourceGroup3 SourceGroup4 Admin	DestinationGroup3 DestinationGroup4 Admin	Object Stores > SourceOS1 > >Events, Actions, Processes > Events > Subscriptions

Workflow system	Object Name	Content Platform Engine Object Type	Source LDAP Assignment	Destination LDAP Assignment	Location
Updated workflow queue definition - added F_StepName to the list of System fields	WorkflowQueueDefinition	Workflow Queue Definition	SourceGroup3 SourceGroup4 Admin	DestinationGroup3 DestinationGroup4 Admin	The workflow system asset is not stored in the object store. It is referenced by the workflow definition document in Object Stores > SourceOS1 > Root Folder > Customer Invoices Folder v2.

IBM Content Navigator	Object Name	Content Platform Engine Object Type	Source LDAP Assignment	Destination LDAP Assignment	Location
Updated stored search - changed document content, which creates a new document version object; not a change to the properties of the existing object.	StoredSearch v2	Stored Search	SourceGroup3 SourceGroup4 Admin	DestinationGroup3 DestinationGroup4 Admin	Object Stores > SourceOS1 > Root Folder > Customer Invoices Folder v2