Deployment Scenario

The Content Engine provides sample scripts used to deploy a FileNet P8 application in a production environment.

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 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 successfully importing and modifying those objects during the import process, you can use Enterprise Manager's bulk operations utility to update information pertinent to the Process Engine.

VBScript sample entry points

Use either the manual or automatic import methods by calling the functions from the entry points. When using 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.

The VBScript script entry points used during the import process are:

'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 Engine objects, such as Active Directory information. If you want to apply the data, such as security information, to one or more Content 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 desired objects, then run a script on each object selected by the query. The bulk operations scripts use the OnCustomProcess entry point.

Sample deployment scenario

We used FileNet P8 Platform software to develop a sample application in a test environment. It is now ready for deployment on a production environment. This sample assumes 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 Engine data such as document classes and other Metadata, and the security settings desired for each type of object. If the users were in the same domain, you would not need to recreate the users and groups.

Data to be transferred during import include:

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

Creating Users and Groups uses the following FileNet provided functions:

Setting object permissions upon import uses the following FileNet provided functions:

Setting Object Store permissions uses the following FileNet provided functions:

Updating Workflow subscriptions uses the following FileNet provided function: UpdateWFVersion

NOTE  Use the bulk operations utility to update Workflow subscriptions.