You can reassign object stores to make them accessible to users from a different FileNet® P8 domain without moving any content.
Overview
You can reassign object stores from one FileNet P8 domain (the source domain) to a different FileNet P8 domain (the destination domain). After the reassignment is complete, users can access the object stores and other reassigned entities from the destination FileNet P8 domain. The reassign process moves information from the source global configuration data to the destination global configuration data. The process does not involve moving any content.
Handling dependencies
Important: When you use the reassign capability be aware of any dependencies between the reassigned objects and other objects in the source FileNet P8 domain, and develop a plan for handling these dependencies. For example, when you reassign an object store, make sure that you understand the status of the following resources, references, codes, and settings:
- Dependencies between the object stores you want to reassign and
other objects in the source domain.
- Conflicts that might exist between the objects that are reassigned
and other objects in the destination domain.
- Configuration settings, such as application server JDBC data sources
- Other application controlled information that is related to the entities that are reassigned. For example, Case Manager solution deployment definitions that are stored in an IBM® Case Manager design object store when an IBM Case Manager target object store is reassigned.
Specifically, one or more of the following entities
might need to be reassigned with an object store:
- Workflow system
- Case Analyzer store
- Case History store
If there are more entities that are associated with the
object store that is being reassigned, the reassign process can be
successful only if the following conditions exist:
- The entities all share database connections that are not shared
with entities that are not being reassigned
- The required options are selected during the reassign process
that enables all the associated entities to be reassigned
For more information about restrictions, prerequisites,
and other dependencies, see "Reassign object stores validation".
FileNet P8 domains at different levels
The
source domain for the reassign process can be at an earlier release
level than the destination domain. If the source and destination domains
are at different levels, the reassign process results in the initiation
of an automatic upgrade of the entities that are reassigned.
Use case scenarios
As a method to deploy all
assets in an object store to a new environment, you can reassign an
object store to a destination domain instead of deploying object store
assets to a new object store in the destination. Consider reassigning
object stores from multiple domains to a single domain to enable queries
across object stores or to facilitate central management of information
assets. To improve scalability or to better align object stores with
the business organization, consider reassigning multiple object stores
from a single domain to more than one domain.
Supported interfaces
You can reassign object stores from the FileNet Deployment Manager graphical user interface with the
Reassign Object Stores wizard or from the FileNet Deployment Manager command line interface to reassign one or more object stores. The following topics describe how to reassign an object store from the graphical user interface and from the command line interface:
- Reassigning an object store from the graphical user interface
- Reassigning an object store from the command line interface