Deployment scenario (Enterprise Manager only)

A customized XML file contains metadata and other objects exported from an object store created in a test environment. The sample described here applies four scripts to this import process. These scripts modify the imported objects to function in the new environment.

The sample deployment scripts set up the objects by using the import facility as follows:

1. Add Active Directory users and groups data.
2. Set the default instance security on the new objects as they are created.
3. Set both default and regular security on the objects in the object store.

After importing and modifying those objects during the import process, you can use the bulk operations utility in Enterprise Manager to update information pertinent to Content Platform Engine.

VBScript sample entry points (Enterprise Manager only)

Use either the manual or automatic import methods by calling the functions from the entry points. When you use a single file, you can code the different entry points to call a different function in the script. You can use either VBScript or JScript.

'This function is called once before any importing is done.
 Public Sub PreImportScriptMethod (domDoc,objStore)

'This function is called each time an object is imported but not yet saved.
 Public Sub PreSaveScriptMethod (objGeneric)

'This function is called each time an object is imported and saved for the first time.
 Public Sub PostSaveScriptMethod (objGeneric)

'This function is called once after all importing is done.
 Public Sub PostImportScriptMethod (objStore)

The VBScript script entry point used for bulk operations is:

'This function is called for each object selected by the query.
Public Sub OnCustomProcess (CEObject)

Using import scripts to deploy data

Use either the PreImport or PostImport option for data not bound to specific single Content Platform Engine objects, such as Active Directory information. If you want to apply the data, such as security information, to one or more Content Platform Engine objects, use the PreImport option to create the data and the PreSave option to apply it.

Using bulk operations to deploy data

Build a query to select the objects you want, and then run a script on each object selected by the query. The bulk operations scripts use the OnCustomProcess entry point.

Sample deployment scenario

The FileNet P8 Platform software was used to develop a sample application in a test environment. It is now ready for deployment on a production environment. This sample assumes that the test environment is not in the same Windows domain as the new environment. Therefore, this data includes users and groups in the operating system, Content Platform Engine data such as document classes and other metadata, and the security settings for each type of object. If the users are in the same domain, you must re-create the users and groups.

Data to be transferred during the import process include:

• Non-Content Platform Engine data: Windows Users and Groups required in the new environment
• Content Platform Engine data: class definitions, folders, custom objects to be imported into a new Object Store
• Content Platform Engine-related data: New users and groups applied to imported Content Platform Engine objects as default security settings

To import these objects and set them up in the new environment, use the following sample scripts:

• Use the VBScript sample "Active Directory Users and Groups" to create the users, and then the groups that contain those users, in the new domain. Run this script by using the PreImport run type.
• Use the VBScript sample "Object Permissions" to apply the appropriate users and groups to each imported object. Run this script by using the PreSave run type.
• Use the VBScript sample "Object Store Permission" to set the object store level security. Run this script by using the PreSave run type.
• After importing all objects, use the Enterprise Manager bulk operations facility to update the workflow definitions by using the VBScript sample "Workflow Subscription Update".

Creating Users and Groups uses the following FileNet P8-provided functions:

• HandleAnyErrorCondition 
• CreateUsers
• CreateADUser
• CreateGroups
• CreateADGroup

Setting object permissions when the object is imported uses the following FileNet P8-provided functions:

• HandleAnyErrorCondition
• SetObjectConstants
• ModifyDefaultPermissions
• ModifyPermissions

Setting object store permissions uses the following FileNet P8-provided functions:

• HandleAnyErrorCondition
• SetObjectStoreConstants
• SetObjectStoreSecurity
• AddGroupToClasses
• AddGroupToFolder
• AddGroupToWorkflowEventActionObject
• AddGroupToEachItemInCollection
• WriteToLogFile
• AddGroupToObject

Updating workflow subscriptions uses the following FileNet P8-provided function:

• UpdateWFVersion