Set ALBPM properties for WebSphere

You must configure your Process Engine with some WebSphere-related properties via ALBPM Process Administrator.

You must have an ALBPM Engine for WebSphere configured in order to define this configuration properties.

  1. Login to ALBPM Process Administrator. By default, it runs on http://host:8686/webconsole.
  2. Click on Engines and then click on the name of your ALBPM Engine for WebSphere. You should see the configuration properties for your Engine.
  3. Click on the Application Server tab.
  4. In the JMX Engine Management Configuration section you must specify the Host and Port of one of the WebSphere servers that will be running ALBPM Engine.

    The port number is that of the WebSphere server's SOAP Connector address. You can obtain this value from the WebSphere Administration console: go to Servers > Application servers > YOUR_SERVER (e.g. server1) > Ports, and look for the value of the SOAP_CONNECTOR_ADDRESS property.

    For example, on a default single-node WebSphere configuration where ALBPM Process Admin is running on the same host as WebSphere you would use:
    Host localhost
    Port 8880
  5. Locate the BPM Application Deployer URL field, and change its value to match your WebSphere configuration.

    For example, on a default single-node WebSphere configuration, it would be:

    http://localhost:9080/fuego/deployer/servlet/worker

    The URL should be that of the WebSphere server where ALBPM Deployer is installed, which must be your WebSphere's Deployment Manager server (dmgr).

    Refer to Install WAS Deployer for more details.

  6. Change the WebSphere Server/Cluster Name field to match your WebSphere configuration. This is the name of the WebSphere Server or Cluster where you want to install the ALBPM applications.

    For example, on a default single-node WebSphere configuration, it would be: server1.