Configuring the batch processor to trigger a BPM workflow

The batch processor is able to trigger a Business Process Management (BPM) workflow when a batch job is started, resumed, stopped, or completed. This capability enables you to incorporate batch jobs into business processes.

About this task

To enable the batch processor to trigger a BPM workflow, make the following changes in the Batch.properties file:

Procedure

  1. Uncomment the following line: 
    #job.chainevent.handler=com.ibm.mdm.batchframework.bpm.BPMTaskChainEventHandler
  2. Configure the following BPM connection properties:
    • bpm.host – the URL for the BPM REST service, such as http://localhost:9080
    • bpm.user – the user name that will call the BPM REST service.
    • bpm.password – the password for the user.
    Tip: You can encrypt the bpm.password property using an IBM® WebSphere® Application Server command:
    • For Microsoft Windows systems, use the command: 
      $NODE_HOME\bin\PropFilePasswordEncoder.bat <path_to_props_file>\Batch.properties bpm.password
    • For UNIX or Linux systems, use the command: 
      $NODE_HOME/bin/PropFilePasswordEncoder.sh <path_to_props_file>/Batch.properties bpm.password
    $NODE_HOME represents the home folder of the WebSphere Application Server node.
  3. Optionally, you can use HTTPS to secure the communication between the batch processor and the BPM server:
    1. Configure the bpm.host property to use the HTTPS protocol, such as https://localhost:9443.
    2. When you run a batch activity and connect to the server using the HTTPS protocol for the first time, you are prompted to verify the SSL signer certificate of the BPM server. Reply y to add the signer to the trust store.
      Note: For more information on configuring SSL properties, see the WebSphere Application Server documentation.

What to do next

Tip: By default, the batch processor automatically detects and triggers the BPM workflow of the most recent snapshot in the BPM server. However, if you wish to use the workflow of an older snapshot, you can specify it using the bpm.snapshotId property. For example:
bpm.snapshotId=2064.3d28e8ce-dc63-4ffa-9ed0-9e510509ebb4