setBPMExternalECM command

Use the setBPMExternalECM command to configure IBM® Business Automation Workflow to use an external Enterprise Content Management server.

IBM Business Automation Workflow V19.0.0.3

Note: This command retains the initial setting for content object support. However, if the Content Platform Engine version is earlier than 5.5.3, the command automatically disables content object support. If content object support is disabled and you upgrade Content Platform Engine to version 5.5.3 or later, you can manually enable content object support by using the BPMConfig command and the -update and -enableContentObjectSupport parameters, as described in the topic BPMConfig command-line utility. You can also use the same command and parameter to disable content object support regardless of the Content Platform Engine version.

If you are using Content Platform Engine as a container for integration with Business Automation Workflow and the Content Platform Engine version is 5.5.3, you must run the BPMConfig command and the -update and -enableContentObjectSupport parameters to disable content object support.

The setBPMExternalECM command is run by using the AdminTask object of the wsadmin scripting client.

Prerequisites

The following conditions must be met:

Before the setBPMExternalECM command is run, the Business Automation Workflow system must be at version 8.5.6 or higher with any necessary upgrade or migration procedures already completed. If the startDocumentStoreMigration command needs to be run, it must be run before you run the setBPMExternalECM command.
In clustered environments, the command must be run on the deployment manager node. In non-clustered environments, the command must be run on the stand-alone server.
If the deployment manager or stand-alone server is stopped, use the wsadmin -conntype none option to run the command in disconnected mode (which is the recommended mode for this command).
If the deployment manager or stand-alone server is running, you must connect with a user ID that has WebSphere Application Server configurator privileges. Do not use the wsadmin -conntype none option.
The Content Platform Engine must not be shut down.

Important: Running this command in connected mode 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.

Location

Start the wsadmin scripting client from the profile_root/bin directory. The setBPMExternalECM command does not write to a log file, but the wsadmin scripting client always writes a profile_root/logs/wsadmin.traceout log file where you find exception stack traces and other information.

Syntax

setBPMExternalECM
[-de deployment_environment_name]
-ceUrl external_FileNet_content_engine_url

-ecmEnvironment NEW_EXTERNAL_OBJECT_STORE
-domainName external_FileNet_domain_name
-objectStoreName external_FileNet_object_store_name
-designObjectStoreName external_FileNet_design_object_store_name
-clientDownloadServicePort port_number
-clientDownloadServiceHostname CPE_server_hostname

Parameters

-de deployment_environment_name

A parameter that specifies the name of the current deployment environment. If there is only one deployment environment in the WebSphere cell, you can omit this parameter.

-ceUrl external_FileNet_content_engine_url

A required parameter that specifies the external Content Platform Engine URL address. For a highly available configuration that uses an application server cluster, see Content Platform Engine in an application server cluster by using EJB transport.

-ecmEnvironment NEW_EXTERNAL_OBJECT_STORE

A required parameter that specifies how the external Enterprise Content Management server is used.

NEW_EXTERNAL_OBJECT_STORE is used if you created a new object store on an existing external Content Platform Engine. Select this option if you followed the instructions in Configuring an existing external Content Platform Engine.

-domainName external_FileNet_domain_name

A required parameter if you select NEW_EXTERNAL_OBJECT_STORE. This parameter specifies the external Content Platform Engine domain name.

-objectStoreName external_FileNet_object_store_name

A required parameter if you select NEW_EXTERNAL_OBJECT_STORE. This parameter specifies the external Content Platform Engine object store name. The default object store name, docs, cannot be specified as a value.

Tip: This parameter is case-sensitive.

-designObjectStoreName external_FileNet_design_object_store_name

A required parameter if you select NEW_EXTERNAL_OBJECT_STORE. This parameter specifies the external Content Platform Engine design object store name.

Tip: This parameter is case-sensitive.

-clientDownloadServicePort port_number

A required parameter that specifies the HTTP or HTTPS port number of the server where the external Content Platform Engine application is deployed. The default port numbers are 9080 and 9443. IBM Business Automation Workflow V
19.0.0.2

IBM Business Automation Workflow V
19.0.0.2

If you are using V19.0.0.2 or later, you must use the HTTPS port number, 9443.

To test the connection to the Client Download Servlet, enter the following URL in a web browser:

http://host_name:port_number/clientDownload?command=getVersion

This parameter checks whether the local Content Platform Engine client JAR files must be updated. If it updates the JAR files, it lists the updated files for you. Copy the files from the deployment manager to the same installation directory on each custom node in your deployment environment.

-clientDownloadServiceHostname CPE_server_hostname

An optional parameter that specifies the hostname where the Content Platform Engine server is running. If this parameter is not specified, the first hostname extracted from the -ceUrl parameter is used to connect to the Content Platform Engine.

Examples

Note: The examples are for illustrative purposes only. They include variable values and are not meant to be reused as snippets of code.

The following Jython example uses the setBPMExternalECM command to configure Business Automation Workflow to use an existing external Content Platform Engine server.

wsadmin -user admin -password admin -lang jython
wsadmin>print AdminTask.setBPMExternalECM(['-clientDownloadServicePort', '9444', '-de', 'De1', '-ceUrl', 'iiop://CE.mycompany.com:2809/FileNet/Engine', '-ecmEnvironment', 'NEW_EXTERNAL_OBJECT_STORE', '-domainName', 'p8domain', '-objectStoreName', 'bpmdocs', '-designObjectStoreName', 'bpmdos'])
wsadmin>AdminConfig.save()

The following Jython example is similar to the previous example. However, this example includes the -clientDownloadServiceHostname parameter, which you can use to specify the hostname of the Content Platform Engine server when it differs from the hostname extracted from the -ceUrl parameter.

wsadmin -user admin -password admin -lang jython
wsadmin>print AdminTask.setBPMExternalECM(['-clientDownloadServicePort', '9444', '-clientDownloadServiceHostname', 'CPE_server_hostname', '-de', 'De1', '-ceUrl', 'iiop://CE.mycompany.com:2809/FileNet/Engine', '-ecmEnvironment', 'NEW_EXTERNAL_OBJECT_STORE', '-domainName', 'p8domain', '-objectStoreName', 'bpmdocs', '-designObjectStoreName', 'bpmdos'])
wsadmin>AdminConfig.save()

Example of a ceUrl parameter URL: iiop://external FileNet Content Engine server:2809/FileNet/Engine

Example of a ceUrl parameter URL in a clustered environment: corbaloc::node1_hostname:BOOTSTRAP_ADDRESS, :node2_hostname:BOOTSTRAP_ADDRESS/cell/clusters/your_websphere_cluster_name/FileNet/Engine where hostname is the host name of a Content Platform Engine cluster member and BOOTSTRAP_ADDRESS is the bootstrap address port of a Content Platform Engine cluster member.

A configuration changes over time. For example, a cluster member is added. Use the updateBPMExternalECM command to update your configuration. See updateBPMExternalECM command.