Component Manager Web Services

Use the Web Services tab to specify various Web Services information for each Component Manager.

Web Services settings

If you have a farmed system, specify (or modify) the Web Services settings on each Application Engine (AE) or Workplace XT server in the farm.

TIP In a non-farmed system, these settings are automatically defined the first time an applet is executed in the associated application. You do not need to take any further action.

The Web Services Settings include these fields:

Listener URL

Specifies the URL of the Workplace or Workplace XT application associated with this Component Manager.

CAUTION  In an environment configured for single sign-on (SSO), do not use the SSO server name in the URL, even if Process Task Manager displays it by default.

In a load-balanced system, specify the URL of the load balancer server, not the AE or Workplace XT server. For example, consider a farmed AE system with a load balancer server named ae_load_balancer, and two AE servers named ae_server1 and ae_server2. The Listener URL might look like http://ae_load_balancer:7001/Workplace.

Listener Local Host

Specifies the URL of the local host server. In most cases, the Listener Local Host is the same for all Component Managers running on the same AE or Workplace XT server.

Enter the Listener Local Host in the following format:
<Application Engine or Workplace XT server name>:<Application Engine Workplace or Workplace XT port number>

In a load-balanced system, the Listener Local Host specifies the local AE or Workplace XT server. Using the example described in Listener URL above, enter ae_server1 or ae_server2 (depending on which AE server you are configuring) for the Listener Local Host.

Web Services Java™ Secure Socket Extension (JSSE) settings

Component Manager uses JSSE to invoke a Secure Socket Layer (SSL) web service. Part of the JSSE functionality is to accept server certificates as part of the SSL handshake. In most cases, the server certificate is signed with a well-known certificate authority, such as Verisign, whose root certificates are in the default Java™ Runtime Environment (JRE) trust store. However, since Component Manager is running without any user intervention, you may want to have self-signed certificates automatically accepted. (This is similar to Internet Explorer prompting you with a dialog box asking if you want to trust certificates, for example, from ABC whenever you use https://xxx, with a self-signed or unknown certificate).

Complete the following steps to enable BPM Process Orchestration and CE operations to function correctly in an SSL environment.

  1. Install the application server certificate. See Download certificate for instructions.
  2. In Task Manager > Component Manager, select the connection point node and stop it.
  3. On the Web Services > JSSE setting tab, enter both the Key store password and the Trust store password.
  4. Apply the change and restart the CM node.

TIP If you are invoking Web Services referenced via secure WebSphere WSRR, either select Automatically add server certificates to trust store, or download the WSRR server certificate to the trust store.

The Web Services JSSE Settings include these fields:

Key store file

The location of the file containing the certificates to be sent for an SSL connection with a server that requires client authentication

Key store password

The password used to secure the Key store file. By default the password is as installed with the JRE, with changeit as the password.

Trust store file The location of the file containing the trusted server certificates.
Trust store password

The password used to secure the Trust store file. By default the password is as installed with the JRE, with changeit as the password.

Automatically add server certificates to trust store

If this box is checked, the server certificate, if not already in the trust store, is automatically trusted and added to the store for the next usage. If this box is not checked, you must manually save the server certificate and specify the trust store information.

Reliable Messaging settings

The Reliable Messaging Settings include these fields:

Inactivity timeout The amount of time, in milliseconds, that must pass before Component Manager stops waiting for a reply.
Base retransmission interval The amount of time, in milliseconds, that must pass before Component Manager initially retries a request. The interval increases for each subsequent retry, until the total time reaches the value indicated in Inactivity timeout.