This topic applies only to the IBM Business Process Manager Advanced configuration.

Querying and replaying failed messages, using administrative scripts

Use the queryNumberOfFailedMessages.py administrative script to determine whether there are any failed messages for BPEL processes or human tasks. If there are any failed messages, use the replayFailedMessages.py administrative script, to retry processing them.

Before you begin

The following conditions must be met:
  • Run the script in connected mode, that is, do not use the wsadmin -conntype none option.
  • At least one cluster member must be running.
  • Include the wsadmin -user and -password options to specify a user ID that has operator authority.
  • If you are not working with the default profile, use the wsadmin -profileName profile option to specify the profile.

About this task

When a problem occurs while processing an internal message, this message ends up on the retention queue or hold queue. To determine whether any failed messages exist, and to send those messages to the internal queue again:

Procedure

  1. Change to the Business Process Choreographer subdirectory where the administrative script is located.
    For Linux operating systemFor UNIX operating systemEnter the following command:
    cd install_root/ProcessChoreographer/admin
    For Windows operating systemEnter the following command:
    cd install_root\ProcessChoreographer\admin
  2. Query the number of failed messages on both the retention and hold queues.

    For Linux operating systemFor UNIX operating systemEnter the following command:

    install_root/bin/wsadmin.sh -f queryNumberOfFailedMessages.py
               -cluster clusterName
               [ -bfm | -htm ]

    For Windows operating systemEnter the following command:

    install_root\bin\wsadmin -f queryNumberOfFailedMessages.py
               -cluster clusterName
               [ -bfm | -htm ]

    Where:

    -cluster clusterName
    The name of the cluster where Business Process Choreographer is configured. In a multicluster setup, you must specify the application cluster because that is where Business Process Choreographer is configured.
    -bfm | -htm
    These keywords are optional and mutually exclusive. The default, if neither option is specified is to replay failed messages for both BPEL processes and human tasks. If you want to only replay the messages for BPEL processes, specify the -bfm option. If you want to only replay messages for human tasks, specify the -htm option.
  3. Replay all failed messages on the hold queue, retention queue, or both queues.

    For Linux operating systemFor UNIX operating systemEnter the following command:

    install_root/bin/wsadmin.sh -f replayFailedMessages.py
           -cluster cluster_name
           -queue replayQueue
           [ -bfm | -htm ]
       

    For Windows operating systemEnter the following command:

    install_root\bin\wsadmin -f replayFailedMessages.py
           -cluster cluster_name
           -queue replayQueue
           [ -bfm | -htm ]

    Where:

    -cluster clusterName
    The name of the cluster where Business Process Choreographer is configured. In a multicluster setup, you must specify the application cluster because that is where Business Process Choreographer is configured.
    -queue replayQueue
    Optionally specifies the queue to replay. replayQueue can have one of the following values:
    • holdQueue (this is the default value)
    • retentionQueue (only valid when the -bfm option is specified)
    • both (not valid when the -htm option is specified)
    -bfm | -htm
    These keywords are optional and mutually exclusive. The default, if neither option is specified is to replay failed messages for both BPEL processes and human tasks. If you want to only replay the messages for BPEL processes, specify the -bfm option. If you want to only replay messages for human tasks, specify the -htm option.