BPMSyncTeamBindings command

Use the BPMSyncTeamBindings command to copy teams between two snapshots.

This utility copies the teams from the source snapshot to the target snapshot.

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

Prerequisites

The following conditions must be met:
  • Run the command in the connected mode; that is, do not use the wsadmin -conntype none option.
  • In a network deployment environment, an application cluster member runs the Process Server and Process Center applications. Therefore, you must run this command on the node that contains that application cluster member. Do not run the command from the deployment manager profile.
When you copy a large number of variables using the BPMSyncEnvironmentVariables command, it is possible that you could encounter timeout exceptions if the migration time exceeds 120 seconds. These exceptions are captured by first failure data capture (FFDC) and logged to the SystemOut.log file. You can prevent timeout exceptions from occurring by increasing the timeout value for both the SOAP connector connection and the server transaction service. To increase the timeout value for the SOAP connector connection, read the instructions in the topic Connection timeout when running a wsadmin script. To increase the timeout value for the server transaction service, complete the following steps:
  1. In the tree view of the IBM Process Server administrative console, select Servers > All servers.
  2. In the Middleware Servers pane, click the link on the name of the middleware server. For example, SingleClusterMember1.
  3. Expand Container services and click the Transaction service link.
  4. In the Total transaction lifetime timeout field, specify a larger value.
  5. Click Apply and then click the Save link to save the changes to the master configuration.
Note: If you are using a SOAP connection, the command can take longer to complete than the specified SOAP timeout value. Although the command continues to run until it is finished, you might see the exception java.net.SocketTimeoutException: Read timed out. To prevent this exception, set a higher value for the com.ibm.SOAP.requestTimeout property in the profile_root/properties/soap.client.props file.

Location

Start the wsadmin scripting client from the install_root/profiles/node_profile/bin directory.

Syntax

BPMSyncTeamBindings 
-containerAcronym process_application_acronym
-sourceContainerSnapshotAcronym snapshot_acronym
-targetContainerSnapshotAcronym snapshot_acronym

Parameters

-containerAcronym String
A required parameter that identifies the process application or toolkit that contains the snapshots. For example, the BillingDispute process application might have an acronym of BILLDISP.
-sourceContainerSnapshotAcronym String
This parameter identifies the snapshot that contains the teams that you want to copy.
-targetContainerSnapshotAcronym String
This parameter identifies the snapshot that you want to copy the teams to.

Example

The following example illustrates how to establish a SOAP connection to the Process Center server and then copy teams from one snapshot to another.

Important: In a network deployment environment, use the port configured for the application cluster member that runs the Process Server or Process Center applications. To determine the correct port number, see the WebSphere administrative console Ports collection page (click Servers > Server Types > WebSphere application servers > server_name > Communications > Ports and find the value for SOAP_CONNECTOR_ADDRESS). 
wsadmin -conntype SOAP -port 8880 -host ProcessCenterServer01.mycompany.com 
-user admin ID -password administrator password -lang jython

wsadmin>AdminTask.BPMSyncTeamBindings(’[-containerAcronym HSS -sourceContainerSnapshotAcronym "V1" -targetContainerSnapshotAcronym "V2"]’)
Parent topic: Commands (wsadmin scripting)