IBM FileNet P8, Version 5.2.1

Workflow system assets

Each type of workflow system asset has specific capabilities and limitations that you must consider when you deploy it. Provides definitions, deployment mechanism, dependency, enivronment-specific data, and other information about workflow system assets.

Workflow systems: object store assets

Workflow definition

Description	Provides an electronic representation of the activities and resources that are required to accomplish a business process. A workflow definition acts as a processing template that workflow systems use each time that the workflow runs. The workflow routes the work to the specified participants, along with data, attachments, and other information that is required to complete the activities.
Deployment Mechanism	FileNet® Deployment Manager: Create deployment data set Convert objects for import Analyze objects for import Import converted objects
Dependencies	If a workflow definition contains references to attachments, those attachments must exist in the specified object store in the destination environment before the workflow is processed. You are responsible for deploying the attachments. If a workflow definition is used in a workflow subscription, the workflow subscription must be exported to the destination environment. If a workflow definition contains user-defined queues, rosters, event logs, they must be deployed as well. If a workflow definition contains specific LDAP user name and groups, they must be available in the destination environment. Tip: Alternatively, you can use FileNet Deployment Manager to map and convert the values to use during the import process. See Extracting a service half map for information on extracting and mapping LDAP user and group names from a workflow definition. See Common dependencies between objects.
Environment-specific data	References to attachments identify the object store in which the attachments are found. FileNet Deployment Manager converts the object store references when you convert the workflow definition. Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission.
Restriction:	The workflow definition contains the data that is required to create an executable workflow. Before you can run the workflow in the destination environment, you must transfer the workflow definition into the database to create the executable workflow. For more information, see Transfer workflow definition.

Workflow subscription

Description	Provides an association between a class or an object and a workflow definition. The subscription can specify which events trigger an automatic launch of the workflow or if a user must start the workflow manually.
Deployment Mechanism	FileNet Deployment Manager: Create deployment data set Convert objects for import Analyze objects for import Import converted objects
Dependencies	The workflow definition that is referenced by the workflow subscription must be transferred to the database. See Common dependencies between objects.
Environment-specific data	Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission.
Restriction:	The workflow subscription requires the version ID of the executable workflow that is created when you transfer the workflow definition to the database. See Updating workflow definitions.

Database assets

Application space

Description	Provides a mechanism for organizing the resources for a mashup application or other custom application that uses a workflow.
Deployment Mechanism	FileNet Deployment Manager: Create deployment data set Convert objects for import Analyze objects for import Import converted objects
Dependencies	None
Environment-specific data	If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.
Restriction:	Application spaces must exist in the destination environment for the workflow definitions to work.

Event log

Description	Contains a record of system or workflow events for each isolated region. This type of logging is useful for tracking workflow activity. Each event that is logged is part of an event category, and has an associated event number.
Deployment Mechanism	FileNet Deployment Manager: Create deployment data set Convert objects for import Analyze objects for import Import converted objects
Dependencies	None
Environment-specific data	If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.
Restriction:	Event logs must exist in the destination environment for the workflow definitions to work.

Isolated region properties

Description	Configuration information for a particular isolated region such as step processors and event logging options.
Deployment Mechanism	FileNet Deployment Manager: Create deployment data set Convert objects for import Analyze objects for import Import converted objects
Dependencies	None
Environment-specific data	If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.

Queue

Description	Provides a workflow database table to contain work items. There are 4 types of queues: user queues, work queues, component queues, and system queues.
Deployment Mechanism	FileNet Deployment Manager: Create deployment data set Convert objects for import Analyze objects for import Import converted objects
Dependencies	None
Environment-specific data	If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.
Restriction:	Queues must exist in the destination environment for workflow definitions to work. Queue names are not converted, and are assumed to be the same in both the source and destination environments. If not, queue names must be manually corrected in the destination environment.

Roster

Description	Provides a database table that contains the current location of and other information about all workflows.
Deployment Mechanism	FileNet Deployment Manager: Create deployment data set Convert objects for import Analyze objects for import Import converted objects
Dependencies	None
Environment-specific data	If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.
Restriction:	Rosters must exist in the destination environment for workflow definitions to work.

User information

Description	Contains user preferences such as email addresses, notification flags, and proxy user information.
Deployment Mechanism	FileNet Deployment Manager: Create deployment data set Convert objects for import Analyze objects for import Import converted objects
Dependencies	None
Environment-specific data	If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.

Workflow system properties

Description	Properties of the global workflow system configuration such as language packs and SMTP settings.
Deployment Mechanism	FileNet Deployment Manager: Create deployment data set Convert objects for import Analyze objects for import Import converted objects
Dependencies	None
Environment-specific data