Sample scenario of assets to deploy and object name, type, LDAP source, and destination and asset location information.
This sample scenario takes you through the steps of a first-time deployment of an application; that is, the assets of the application in the source environment do not yet exist in the destination environment. The scenario lists a set of sample FileNet® P8 asset to be deployed, and specifies the steps to deploy the assets and to verify the deployment on the destination environment.
Using high-level deployment steps, here is an example of each step, illustrated with the actions of a third-person administrator, who operates in the context of the sample scenario. The sample scenario assumes that the source and destination systems are available to the administrator.
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. Therefore, the administrator must map the source security principals to the destination security principals.
LDAP Source | Object Name |
---|---|
SourceGroup1 |
SourceGroup1 |
Admin | Admin |
SourceUser1 |
SourceUser1 |
LDAP Destination | Object Name |
---|---|
DestinationGroup1 |
DestinationGroup1 |
Admin | Admin |
DestinationUser1 |
DestinationUser1 |
Object stores
The source and destination environments each contain two object stores. The application assets to be deployed are on SourceOS1, and are deployed to DestinationOS1. Therefore, the administrator must map these two object stores to each other. The P8Demo object stores are not used for deployment.
Source Object Store | Destination Object Store |
---|---|
P8Demo | P8Demo |
SourceOS1 | DestinationOS1 |
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 by using IBM® Administration Console for Content Platform Engine.
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 Workplace XT and workflow systems, which integrate with Content Platform Engine.
In this sample scenario, the assets to be deployed are customer invoice-related objects, consisting primarily of an invoice folder, its contained documents, and associated metadata (property template and classes). Other invoice-related objects are a workflow subscription, a workflow definition that is referenced by the workflow subscription, and a stored search.
After the assets are imported to the destination environment, the assets in this 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.
The tools that are required for deploying this sample set of assets are FileNet Deployment Manager and IBM Administration Console for Content Platform Engine.
Content Platform Engine Core | Object Name | Content Platform Engine Object Type | Source LDAP Assignment | Destination LDAP Assignment | Location |
---|---|---|---|---|---|
1 property template (which is displayed on the new class definitions) | InvoiceNumChar_PropTemplate | Property Template | SourceGroup1 |
DestinationGroup1 |
Object Stores > SourceOS1 > Data Design > Property Templates |
1 new "Invoice" document class definition | Invoice_DocClass | Document Class | SourceGroup1 |
DestinationGroup1 |
Object Stores > SourceOS1 > Data Design > Classes > Document |
1 new "CustomerInvoices" folder class definition | Invoice_FolderClass | Folder Class | SourceGroup1 |
DestinationGroup1 |
Object Stores > SourceOS1 > Browse > Root Folder > Other Classes > Folder |
1 folder of type CustomerInvoices | Customer Invoices Folder | Folder | SourceGroup1 |
DestinationGroup1 |
Object Stores > SourceOS1 > Browse > Root Folder > Customer Invoices |
1 document of type Invoice | Invoice Document | Document | SourceGroup1 |
DestinationGroup1 |
Object Stores > SourceOS1 > Browse> Root Folder > Customer Invoices Folder |
1 workflow definition document | InvoiceWorkflowDefinition | Workflow Definition | SourceGroup3 |
DestinationGroup3 |
Object Stores > SourceOS1 > Browse > Root Folder > Customer Invoices Folder |
1 workflow subscription | InvoiceWorkflowSubscription | Workflow Subscription | SourceGroup3 |
DestinationGroup3 |
Object Stores > SourceOS1 > Events, Actions, Processes > Events > Subscriptions |
Workflow system | Object Name | Content Platform Engine Object Type | Source LDAP Assignment | Destination LDAP Assignment | Location |
---|---|---|---|---|---|
1 workflow queue definition | WorkflowQueueDefinition | Workflow Queue Definition | SourceGroup3 |
DestinationGroup3 |
This workflow system asset is not stored in the object store. It is referenced by the workflow definition document in Object Stores > SourceOS1 > Browse > Root Folder > Customer Invoices Folder v2. |
IBM Content Navigator | Object Name | Content Platform Engine Object Type | Source LDAP Assignment | Destination LDAP Assignment | Location |
---|---|---|---|---|---|
1 stored search | StoredSearch | Stored Search | SourceGroup3 |
DestinationGroup3 |
Object Stores > SourceOS1 > Browse > Root Folder > Customer Invoices Folder v2. |