Collecting intercepted jobs periodically for BC-XBP 3.0
With the BC-XBP 3.0 interface, you can configure the job interception collector using an HCL Workload Automation job that periodically retrieves intercepted jobs and relaunches them.
About this task
Released
and then
Intercepted
status until they are relaunched, you need to use the SAP interception collector task to collect
and relaunch them. To define an HCL Workload Automation job that collects and relaunches
jobs use the following syntax:
ENGINE_NAME_HOSTING_XA#[folder/]JOBNAME
DOCOMMAND "TWA_home/methods/r3batch -t HIJ -c UNIQUE_ID -- \
"-profile_id profile_ID_number\""
STREAMLOGON TWSuser
DESCRIPTION "Collects intercepted jobs on SAP XA XA_Unique_ID"
TASKTYPE UNIX
RECOVERY STOP
where, - ENGINE_NAME_HOSTING_XA
- The name of the engine workstation hosting the XA workstation with the r3batch access method that communicates with the SAP system.
- JOBNAME
- Name of the HCL Workload Automation job and the folder within which it is defined, if any.
- TWA_home
- Fully qualified path to your HCL Workload Automation installation.
- XA_Unique_ID
- The unique identifier for the extended agent workstation. See UNIQUE_ID for more details about retrieving the unique identifier.
- –t HIJ
- This is the SAP task
type to run the job interception collector. HIJ stands for
Handle Intercepted Jobs
. - - profile_id profile_ID_number
- Specifies the identification number of the interception criteria profile on the SAP system for XBP 3.0.
- TWSuser
- Name of the HCL Workload Automation user that launches the access method.
The interception collector job runs at periodical intervals; for example, every 10 minutes. It retrieves all the jobs that have been intercepted since the last run of the interception collector, and launches them again according to a template.
Note: If the interception collector
is configured for XBP 3.0 job interception, but the XBP 2.0 interface is configured on the SAP system, the collector fails. Ensure the
XBP interface versions are synchronized.