The following steps describe deploying new objects; that is, deploying objects that exist in the source environment but that do not currently exist in the destination environment.
For this sample scenario, the administrator identifies data to deploy, as listed in Assets to be Deployed. To avoid potential deployment issues, the administrator verifies that each asset in the list is prepared properly. See FileNet® P8 Assets.
Setting up a deployment for a source and destination environment (source-destination pair) for the first time, the administrator must perform configuration steps that define the relationship between the two environments. For this sample, the source and destination environments are referred to as SourceEnv and DestEnv.
The administrator creates the source environment, which is identified as SourceEnv in the FileNet P8 deployment tree, and then defines a connection to the Content Platform Engine with the SourceOS1 object store. When later created, the half maps for the source environment are displayed under the SourceEnv node in the deployment tree.
The administrator creates the destination environment, which is identified as DestEnv in the FileNet P8 deployment tree, and then defines a connection to the Content Platform Engine with the DestinationOS1 object store. When later created, the half maps for the destination environment are displayed under the DestEnv node in the deployment tree.
The administrator creates the source-destination pair, identified as SourceEnv-to-DestEnv in the FileNet P8 deployment tree. When later created, the data maps, used to convert source objects for the destination environment, is displayed under the SourceEnv-to-DestEnv node in the deployment tree.
The administrator adds the Customer Invoices Folder in the SourceOS1 object store to the export manifest. In the Include Options dialog box for that object, the administrator keeps the default settings. Because all of the objects are filed in the Customer Invoices Folder, or are associated with the objects in that folder, all the other objects are exported by using the include options.
The administrator saves the export manifest to SourceOS1_ExportManifest.xml.
The administrator runs the operation and specifies SourceOS1_ExportManifest.xmll as the export manifest file, and CE_Create as the deployment data set of exported objects.
Although workflow definitions are stored in the Content Platform Enginerepository, the queues, rosters, logs, user information, system properties, all transferred workflows, running work items, and other configuration information are stored in an isolated workflow system region.
From the source environment, the administrator saves the exported queue definition to PE_Config.xml.
The administrator retrieves the object store names from the source environment: P8Demo and SourceOS1.
The administrator retrieves security principals from the source environment. Because the LDAP server contains only a small set of groups and users, the administrator retrieves the security principals from the server.
The administrator retrieves the object store names from the destination environment: P8Demo and SourceOS1.
The administrator retrieves security principals from the destination environment. Because the LDAP server contains only a small set of groups and users, the administrator retrieves the security principals from the server.
For object stores, the administrator maps SourceOS1 to DestinationOS1 because there are no key fields in common, that is, the symbolic names and IDs are different for the two object stores. The administrator enters the label OS1 to map the SourceOS1 and DestinationOS1 entries in the source and destination half maps.
For security principals, the administrator maps SourceGroupN to DestinationGroupN, and SourceUserN to DestinationUserN. The administrator does not map the source Admin security principal because the key fields in the Admin entries in both environments are the same. The key fields are security ID (SID) and the short name.
The administrator runs the operation and views the object store map UI, which shows that the source and destination object stores, P8Demo and SourceOS1, are mapped by using matching labels. It also shows that the P8Demo object stores in the source and destination environments are mapped because their symbolic names are the same (matching labels are not required).
The administrator runs the operation and views the security principal map UI, which shows that the source and destination LDAP groups and users are mapped by using matching labels, except for the Admin user.
The administrator runs the operation, specifying CE_Create as the deployment data set of exported objects. For the output directory for the deployment data set of converted objects, the administrator accepts the default directory: P8DeploymentData\Environments\DestEnv\Assets\CE_Create.converted.
FileNet Deployment Manager includes the change impact analysis operation, which reports on the potential import errors in the destination environment, on the change impact on the destination environment, and on the estimated size of the imported data. The operation uses a converted deployment data set and connects to a destination environment to do the analysis. Note, however, that the operation provides information only; it does not import exported data, or modify the destination environment.
You can run this operation on the converted deployment data set for the Content Platform Engine or the workflow system isolated region configuration data file. See About change impact analysis and Analyze objects for import.
The administrator accepts the default directory for the deployment data set for converted objects: P8DeploymentData\Environments\DestEnv\Assets\CE_Create.converted.
The administrator specifies the queue definition configuration file (PE_Config.xml).
Note For this option to work, the importing user must have privileged write access on the destination object store. (From the Security tab of the object store property sheet in Administration Console for Content Platform Engine, the Modify certain system properties permission must be set.)
The administrator does not use scripts for importing because no special processing is necessary before or after you import each object.
Depending on the contents of a deployed data set and the FileNet Deployment Manager import options, you might need to complete extra configuration in the destination environment. For this sample, a workflow definition and the workflow subscription are included in the imported data, necessitating the following steps.
The sample workflow description (InvoiceWorkflowDefinition) was imported to the Customer Invoices Folder on the DestinationOS1 object store. The administrator transfers InvoiceWorkflowDefinition to the destination server.
The administrator modifies the imported workflow subscription, InvoiceWorkflowSubscription. The administrator selects the transferred InvoiceWorkflowDefinition as the workflow definition for the subscription.