IBM FileNet P8, Version 5.2.1            

Object identifier stability

An important key to maintaining consistency of assets as they migrate between environments is keeping a constant and unique identification for objects.

For FileNet® P8 domain or object store objects in Content Platform Engine, unique object identification is accomplished by using a globally unique identifier (GUID). A GUID is a 128-bit data identifier that is used to distinguish objects from each other. If there is a need to merge objects from multiple object stores into a common object store, GUIDs help with that process. GUIDs ensure that objects maintain their uniqueness and do not collide with each other in the common object store.

GUIDs also reduce the complexity of inter-object relationships by providing a well-managed reference value. With the GUID as a reference value, objects and their dependent objects can be quickly and reliably located within the object store in which they are stored.

For workflow system objects, such as queues, application spaces, or transferred workflows, identification is by name. During an import, if the object has the same name as one that exists in the system, it is considered to be the same element.

When you move objects between multiple environments, you must consider dependencies. Objects are often dependent on other objects in the object store, in the workflow system, or on external resources. The following examples show these types of dependencies:

The extra effort of maintaining the dependencies in the destination environment can be reduced by establishing and following a pattern of having stable GUIDs. Deployment and migration tasks might require extra deployment logic if a stable GUID pattern is not followed.

For example, the following two options might be used to deploy a search template that has a dependency on a folder structure:
Option Result
Option 1: Stable GUIDs are used FileNet Deployment Manager or a FileNet Content Manager addOn is used to import the folder with the same GUID. Because the same GUID is used, no additional corrections are needed when you are deploying the search template.
Option 2: New GUIDs are used A new folder is created in the destination object store and the system is allowed to generate a new GUID. Because a different GUID is used, the search template must be manually changed to refer to the newly created folder.

Some assets, such as the IBM® Case Manager Form and Content List widgets, IBM Forms, and FileNet P8 eForms form templates, require the original design tools to manually repair a dependent reference. However, these design tools are not available in a non-development environment. Therefore, the use of stable GUIDs across all environments is mandatory when these assets are used. FileNet Deployment Manager must be used to migrate assets and their object identifiers between environments to ensure stable GUIDs.



Last updated: March 2016
p8pdb008.htm

© Copyright IBM Corporation 2016.