BPMListServers command

This command lists all of the Process Server instances that are federated into the Process Center.

Purpose

Use the BPMListServers command in connected mode from the Process Center server. It has no parameters, and returns a list of Process Server instances.In a network deployment environment, you must run this command on the node containing the application cluster member that handles Process Server or Process Center applications. Do not run this command from the deployment manager profile.

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.

Example

The following example illustrates how to list all federated Process Server instances for a Process Center. In the example, the user establishes a SOAP connection to the Process Center server.

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).

Jython example

wsadmin -conntype SOAP -port 8880 -host ProcessCenterServer01.mycompany.com -user admin -password admin -lang jython

AdminTask.BPMListServers

Tip: Add the jython print statement before the command when you want to see formatted output.

Jacl example

wsadmin -conntype SOAP -port 8880 -host ProcessCenterServer01.mycompany.com -user admin -password admin

$AdminTask BPMListServers

The output is a list of servers that contains the following information.

Name:serverName
URL:URL

It looks similar to the following example.

Name:TEST_SERVER_1
URL:corbaname:iiop:server1.mycompany.com:2816

Name:TEST_SERVER_2
URL:corbaname:iiop:server2.mycompany.com:2816