Configuring IBM Business Automation Workflow with an existing external Content Platform Engine

You can configure IBM® Business Automation Workflow to work with an existing external Content Platform Engine, also called an external Enterprise Content Management (ECM) system.

1. Begin your configuration by checking there is no content such as folders and documents in the IBM Business Automation Workflow object store. Use the IBM Administration Console for Content Platform Engine to check there is no content.
   1. In the domain navigation tree, open Object Stores > docs.
   2. In the object store navigation tree, open Search.
   3. Click New Object Store Search.
   4. For each of the following classes, run a search: Document.
   5. If the result set is empty, there is no existing content.
   See Using the IBM Administration Console for Content Platform Engine

   Note: Any content that you do not remove from the BPM content store is deleted when you complete this configuration.
2. Check the version level of the FileNet Content Manager. It must be a supported version to work with IBM Business Automation Workflow. See Planning for an external Content Platform Engine.
3. Configure single sign-on (SSO) security for the external FileNet Content Manager, including the configuration of the user registry and trusted realm. Follow the instructions in Configuring single sign-on for an external Content Platform Engine.
4. Stop the IBM Business Automation Workflow deployment environment.
5. Start the IBM Business Automation Workflow deployment manager to have the changes take effect.
6. Designate a user from the shared repository to be the administrator for the object store. Business Automation Workflow uses this user to do administrative operations like the creation of document class definitions. Then, map this user to the IBM Business Automation Workflow EmbeddedECMTechnicalUser role.
   1. Check that the user defined in the Authentication Alias assigned to the EmbeddedECMTechnicalUser role is a user from the shared repository.
      1. Select Servers > Deployment Environments > DE name > Authentication aliases. Note the alias name that is used for the EmbeddedECMTechnicalUser role.
      2. Select Security > Global Security. Expand the Java Authentication and Authorization Service section and select J2C authentication data. Verify that the user assigned to the EmbeddedECMTechnicalUser alias is a user from the shared user repository.
   2. If the user assigned to the EmbeddedECMTechnicalUser does not qualify, that is, the user is not from the shared repository, do the following steps.
      1. Create an authentication alias with credentials from the shared user repository for the Content Platform Engine administrator.
         1. In the WebSphere administrative console for the IBM Business Automation Workflow server, select Security > Global Security. The Global Security page opens.
         2. Expand the Java Authentication and Authorization Service section and select J2C authentication data. The JAAS - J2C Authentication Data page opens.
         3. Click New and add an authentication alias with LDAP credentials for the object store administrator.
      2. Change the EmbeddedECMTechnicalUser role to use the new authentication alias that you created. This authentication alias is for FileNet Content Manager. To change the EmbeddedECMTechnicalUser role to use the new authentication alias, in the WebSphere administrative console, select Servers > Deployment Environments. Select your deployment environment and continue to Authentication Aliases. You see the EmbeddedECMTechnicalUser and can modify that alias.
7. Grant administrator roles to the user that you chose for the EmbeddedECMTechnicalUser role.
   1. Go to Users and Groups > Administrative user roles and click Add.
   2. Select Administrator, Deployer, Operator roles in the Roles list and click Search.
   3. In the Available user list, select the EmbeddedECMTechnicalUser role mapped user and add it to the Mapped to role list. Click OK to apply all changes.
   4. Log in to the Process Admin Console. In the Group Management window, search for the tw_admins and tw_authors groups, and add the EmbeddedECMTechnicalUser role mapped user to both groups.
8. Restart the IBM Business Automation Workflow deployment manager.
9. Synchronize the custom profiles with the deployment manager profile.
   For each custom profile, run the following command on the custom node:

   custom_profile_install_root/bin/syncNode.bat dmgr_hostname dmgr_soap_port -user de_admin_user -password de_admin_password

10. Configure the FileNet Content Platform Engine.
    1. Log in to the IBM Administration Console for Content Platform Engine on the FileNet Content Platform Engine as a domain administrator.
    2. If you are creating a new Content Platform Engine environment, create the three object stores for the IBM Business Automation Workflow document store, design object store, and target object store. If you are augmenting IBM Case Manager, you already have the design object store and target object store and need to create only the IBM Business Automation Workflow document store. Use the IBM Administration Console for Content Platform Engine on the FileNet Content Platform Engine as described in Creating an object store. Use the following settings:
       • Use the user from step 6 when granting administrative access to this object store. You may also use a group that contains this user.
       • Grant all users that work with IBM Business Automation Workflow basic access. You might want to use the #AUTHENTICATED-USERS security identifier as grantee to allow all users to work with the object store. The individual instance objects are automatically protected based on the teams you create in IBM Business Automation Workflow.
       • When you choose the add-ons, check that the following extensions are installed. The add-ons are part of the default configuration.
         • For IBM Business Automation Workflow document store:
           • Base Content Engine Extensions
         • For IBM Business Automation Workflow design object store and target object store:
           • Base Application Extension
           • Base Content Engine Extensions
           • Process Engine Extensions
           • Publishing Extensions
           • Stored Search Extensions
           • Worksplace Access Roles Extensions
           • Worksplace Base Extensions
           • Worksplace E-mail Extensions
           • Worksplace Forms Extensions
           • Worksplace Template Extensions
           • Worksplace XT Extensions
       • After the object stores are created, the only access rights that you will need to add to the administrative user is PRIVILEGED_WRITE. In IBM Administration Console for Content Platform Engine on FileNet Content Manager, the check box that you must select is Modify certain system properties (in English).
       • After the target object store is created, you must create a new "Workflow System" for it. Open the target document store, go to Administrative > Workflow System, click New, and enter the values for your environment. Make a note of the connection point name because you will need it in a later step when you run the case configuration tasks in the Case configuration tool. You can ignore the Broker servlet URL and Public listener URL in the Process Orchestration section.

       After the object stores are created, you can add a user with administrative permissions on the object store. See Update object store with new users and groups. The permissions that you must grant to the user are listed in Permissions required for the new object store.
11. Running a command and then starting IBM Business Automation Workflow finishes the configuration. However, you must also verify that the configuration is working.
    1. Run the setBPMExternalECM admin command to configure IBM Business Automation Workflow to use an external Content Platform Engine.
       1. Ensure the IBM Business Automation Workflow deployment manager and the Content Platform Engine are running.
       2. Run wsadmin using the parameter -conntype SOAP from the dmgr_profile_root/bin directory.
       3. Run the setBPMExternalECM admin command and save your changes. Use NEW_EXTERNAL_OBJECT_STORE as the value for the -ecmEnvironment parameter. For example:
          Important: This command results in execution times that exceed the default timeout setting for wsadmin command execution. To change the default to allow for the execution time required, open the profile_root/properties/soap.client.props file and change the value for com.ibm.SOAP.requestTimeout to 0, which means no timeout. Remember to restore the previous value after running the command.

          This command takes a long time to run. Do not close the command window.

          wsadmin -conntype SOAP -port 8880 -host myHostName.mycompany.com -user admin_user -password admin_password -lang jython
          wsadmin>print AdminTask.setBPMExternalECM(['-clientDownloadServicePort', '9081', '-de', 'De1', '-ceUrl', 'iiop://CE.mycompany.com:2809/FileNet/Engine', '-ecmEnvironment', 'NEW_EXTERNAL_OBJECT_STORE', '-domainName', 'p8domain', '-objectStoreName', 'bpmdocs', '-designObjectStoreName', 'bpmdos'])
          wsadmin>AdminConfig.save()

          Notes:

          • The -objectStoreName and -designObjectStoreName parameters are case-sensitive.
          • If you see a message that updated .jar files exist on this deployment manager node machine, you must manually copy the updated files to the other custom node machines.
          See setBPMExternalECM command.
       4. If you started the deployment manager and node agents, manually restart them.
       5. Synchronize the configuration of the nodes.
       6. Restart the IBM Business Automation Workflow deployment environment by using the BPMConfig command. BPMConfig -start. See BPMConfig command-line utility.
    2. Check for errors in the IBM Business Automation Workflow logs. If you discover errors, resolve them and restart the IBM Business Automation Workflow server.
    3. Check the CMIS component in the Component Health Center (Servers > Deployment Environments > de_name > Health Center) to verify that your external Content Platform Engine is up and running. The switch to the external Content Platform Engine removes the BPM content store configuration. Therefore, you cannot check the EmbeddedECM component anymore. Instead, check the CMIS component. The CMIS component also reports errors for the connection to the external Content Platform Engine. See Component Health Center.
    You have now configured the external Content Platform Engine. To configure case management, do the remaining steps.
12. Optional: If you are planning to use an external IBM Content Navigator and it is not yet configured, follow the instructions in Configuring IBM Business Automation Workflow with an external IBM Content Navigator to configure it. Then, return and complete the remaining steps to configure case management..
13. Start the IBM Business Automation Workflow Case configuration tool by running configmgr.exe in the directory workflow-home/CaseManagement/configure.
    If the tool is run on Windows, it should be run with administrative privileges.

    Tip: If security is not a concern, enable saving passwords in the file system by clicking Windows > Preferences and selecting the Save all passwords check box.
14. Open the profile configuration file with the extension .cfgp that was created when you configured your deployment environment.
    This profile file, which contains the default settings, is located in either dmgr-profile-root/CaseManagement/de name/profiles/ICM_dev or dmgr-profile-root/CaseManagement/de name/profiles/ICM_prod.
15. Edit the setting for the remote Content Platform Engine server connection properties.
    1. Click File > Edit Profile Properties.
    2. In the first panel, click Test Connection to verify that the default values are correct and then click Next.
    3. In the second panel, click Test Connection to verify that the default values are correct and then click Next.
    4. In the third panel, replace the default settings for the embedded Content Platform Engine server with the settings for the external Content Platform Engine and then click Test Connection.
    5. Click Finish.
16. Run the enabled configuration tasks in the order in which they are listed in the Case configuration tool.
    For the details of each task, see the topic for your environment.

    • Workflow Center: Running the development environment case configuration tasks
    • Workflow Server: Running the production environment configuration tasks
17. Copy the ejb-lookup.jar file from install_root/CaseManagement/configure/deploy to the Content Platform Engine_install_root/lib/ext directory.
18. Restart the external Content Platform Engine to cause the configuration changes to take effect.
19. Restart the IBM Business Automation Workflow environment.
20. For verification, see the topic for your environment.
    • Workflow CenterVerifying the case applications in the development environment
    • Workflow ServerVerifying the IBM Business Automation Workflow applications in the production environment