IBM FileNet P8, Version 5.2.1            

Deploying objects and property templates

The following steps describe how to apply changes to an existing application; that is, redeploying objects in the source environment that currently exist in the destination environment, and, how to deploy a new property template to the destination environment.

This scenario assumes that the application's deployment configuration that was created for the First-time deployment of an application scenario remains in place, allowing the update scenario to skip the following deployment tasks:
  • Create a source and destination environment (source-destination pair). The update scenario uses the existing source-destination pair, SourceEnv, and DestEnv.
  • Create lists of environment-specific data from each environment. Because environment-specific data is the same as the first-time deployment of the application, this update scenario uses the existing object store, security principal, and service half maps.
  • Create the data maps. The update scenario uses the existing object store, security principal, and service data maps.
  1. Identify the data that is required by the application.

    For this sample scenario, the administrator identifies data to deploy, as listed in FileNet P8 assets. To avoid potential deployment issues, the administrator verifies that each asset in the list is prepared properly. See FileNet® P8 Assets.

  2. Export the data from the source environment.
    1. Using FileNet Deployment Manager, create the export manifest file. See Create or update an export manifest.

      The administrator adds the Customer Invoices Folder v2 and the updated queue definition in the SourceOS1 object store to the export manifest. In the Include Options window for that object, the administrator keeps the default settings. Because all 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_ExportManifestUpdate.xml.

    2. Using FileNet Deployment Manager, export the source objects that are listed in the export manifest file. FileNet Deployment Manager creates a deployment data set directory of exported objects. See Create deployment data set.

      The administrator runs the operation and specifies SourceOS1_ExportManifestUpdate.xml as the export manifest file, and CE_Update as the deployment data set of exported objects.

  3. Update the environment-specific attributes in the data.
    1. Convert the Content Platform Engine deployment data set. This operation converts the exported objects from the source environment with environment information specific to the destination environment, and saves the converted objects in a deployment data set directory, which is used for the analysis and import operations. See Convert objects for import.

      The administrator runs the operation, specifying CE_Update 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_Update.converted.

  4. Analyze converted objects.

    FileNet Deployment Manager includes the Change Impact Analysis operation that 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. See About change impact analysis and Analyze objects for import.

    1. Analyze the converted Content Platform Engine deployment data set.

      The administrator accepts the default directory for the deployment data set for converted objects: P8DeploymentData\Environments\DestEnv\Assets\CE_Update.converted.

  5. Import the data to the destination environment.
    1. Using FileNet Deployment Manager, import converted Content Platform Engine objects. See Import converted objects.
      For importing data in the sample, the administrator sets the options in the Import Options wizard:
      • Select Deploy DatasetThis option accepts the default deployment data set directory for converted objects: P8DeploymentData\Environments\DestEnv\Assets\CE_Update.converted.
      • Select Storage Policy for Imported Objects This option selects Take the storage policy from the class definition at the destination. For this scenario, the administrator cannot assume that the storage policy in the source exists in the destination, so the administrator chooses the default storage policy from the destination class definition of an imported document.
      • Import Security Permissions This option preserves the permissions that are assigned to the source objects.
      • Import Owner This option preserves the owners that are assigned to the source objects.
      • Import Object ID This option preserves the relationships to other exported objects that reference the object that is imported. For most scenarios, you would select this option.
      • Use Original Create/Update Timestamps and Users This option preserves the original time stamp and modifying-user information from the source objects.
        Tip: 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, set the Modify certain system properties permission.
      • Update Options This option selects Update if newer to update only the objects that changed in the source environment. Because the administrator exported the source objects with all associated objects included (as specified in the export manifest), objects that were not updated in the source, like the CustomerInvoices folder class definition, were exported. However, with Update if newer set, exported objects that were not updated is not imported to the destination environment.

        The administrator does not use scripts for importing because no special processing is required before or after you import each object.

  6. Perform extra configuration.

    Depending on the contents of the deployed data set and the import options that are used, extra configuration might be necessary in the destination environment. For this sample, a workflow definition and the workflow subscription are included in the imported data. Complete the following steps for the workflow definitions and subscriptions:

    1. Transfer the workflow definition.

      The sample workflow description (InvoiceWorkflowDefinition v2) was imported to the Customer Invoices Folder v2 on the DestinationOS1 object store. The administrator transfers InvoiceWorkflowDefinition v2 to the destination workflow system.

    2. Update the workflow subscription. See Update workflow subscriptions.

      The administrator uses the Workflow Subscription wizard to modify the imported workflow subscription, InvoiceWorkflowSubscription v2. The administrator selects the transferred InvoiceWorkflowDefinition v2 as the workflow definition for the subscription.



Last updated: October 2015
scenario_update_01.htm

© Copyright IBM Corporation 2015.