IBM FileNet P8, Version 5.2.1            

What's new for deployment

Content Platform Engine V5.2.1 introduces new features and other enhancements for deploying applications. These changes apply to both the FileNet® Deployment Manager user interface and the command-line interface.

Improved migration and deployment model
The documentation for the migration and deployment of FileNet P8 applications and data has been improved. Additional information more fully describes the application migration and deployment model. The procedures for implementing the application migration and deployment model by using the FileNet Deployment Manager tool have been clarified and streamlined. Enhanced information is also available for products and assets that must use other tools for all or part of their migration and deployment processes. New information about the use of FileNet Deployment Manager to migrate data has been added.

FileNet Deployment Manager supports workflow system configuration assets and thus reduces the number of tools that are required for migration and deployment of an application that is based on Content Platform Engine. Metadata from the global configuration data, object store, and workflow system can be placed into a single deployment package, making it easier to migrate and deploy application assets together.

For more information, see Workflow system assets.

Managing source and destination differences
More detailed information is available on the changes that were or will be made to the destination system when a deployment data set with object store assets is imported:
  • Import options can be preconfigured and saved, and then reused for multiple operations. By doing so, operations can be performed with a consistent set of options.
  • The existing import operation captures finer detail on differences between assets in the destination FileNet P8 domain and the assets in the deployment data set. This capture includes the values of all properties that are different and a complete audit of new objects, including their properties.
  • The import operation can be run in an "audit only" mode, allowing the differences to be captured without making any changes to the destination environment.
  • Detailed audit reports of all properties for objects that are modified or created can be generated at any time.

For more information, see FileNet(r) P8 asset deployment.

You have more control when class definitions on the destination system will not match those on the source system after import due to the removal of property definitions. More control is provided by an import option to remove property definitions from the destination environment that were deleted from the source environment class definitions. You might use this option if you previously imported class definitions into the destination environment, and then modified those class definitions at the source to remove some property definitions. When you perform another import into the destination environment, you want those property definitions that were removed from the source environment to also be removed from the destination environment. For more information, see Import options.

Adding assets to an export manifest by using an SQL search
You can locate object store assets to add to an export manifest by using either a saved search that was previously created by using Administration Console for Content Platform Engine or by directly entering a SQL query, Retrieved assets can be selected from the query results or a new option allows for all assets that are returned by the search criteria to be added to the export manifest. For more information, see Adding assets to an export manifest by using a SQL search.
Import and export support for additional assets that are managed by an object store
  • Class definitions that are based on the Abstract Search Results base class
  • Background Search Template definitions and supporting constructs
  • Background Search Results class definitions
  • Search Function Definition
  • Email templates (derived from the Email Services Extensions add-on classes)
  • Sweep management class definitions and objects, including sweep actions, sweep policies, queue sweeps, and sweep target class definitions.
  • IBM® Content Navigator entry templates
  • Mapping of advanced storage areas
  • Mapping of connection points

For more information, see Object store assets.

Updates to the FileNet Deployment Manager command-line interface
The following commands have been added:
  • RetrievePrincipalInfoFromLDAP
  • RetrievePrincipalInfoFromDeployDataSet
  • RetrieveObjectStoreInfoFromDomain
  • RetrieveObjectStoreInfoFromDeployDataSet
  • RetrieveServiceInfoFromDeployDataSet
  • RetrieveInfoFromEnvironment
  • CreateEnvironment
  • ReassignObjectStores
  • MapData
  • ConvertDeployDataSet
  • AnalyzeDeployDataSet
  • ExportDeployDataSet
  • ImportDeployDataSet
  • CreateDeployPackage
  • ExpandDeployPackage
The following commands have been deprecated:
  • CEExport
  • CEImport
  • ConvertCEExportXML
  • ConvertPEExportXML
  • RetrieveObjectStoreInfo
  • RetrieveObjectStoreInfoFromCEDeployDataSet
  • RetrievePrincipalInfoFromCEDeployDataSet
  • RetrievePrincipalInfoFromLDAP
  • RetrievePrincipalInfoFromPEConfigExportXML
  • RetrieveServiceInfoFromCEDeployDataSet
  • RetrieveServicesFromPEConfig
  • ValidateCEExportXML
  • ValidatePEConfigData
  • AnalysisReportFileName
  • analysisFailuresLimit
  • importUpdateOption
  • importCreateOption
  • ValidationOutput

For more information, see Deployment operation files.



Last updated: October 2015
wn_cpe_deploy.htm

© Copyright IBM Corporation 2015.