Overview

The XD Connector is designed to request workload execution, return status on executing workload, and return the job output and the job log, via the Web Services interface in the IBM WebSphere XD environment.

Logical System Flow

The following figure illustrates a more detailed logical flow of the XD connector operation.

Logical System Flow Description

The flow is described as follows (from left to right):

Step 1	Scheduler invokes the UCMD Manager with the appropriate command line options.
Step 2	UCMD Manager reads the script file that contains that contains the XD Connector command options.
Step 3	UCMD Manager reads the xJCL file from STDIN, as indicated by the UCMD options.
Step 4	UCMD Manager requests action by the Broker, which spawns the UCMD Server and sets up communication between the UCMD Manager and UCMD Server.
Step 5	UCMD Server sends the XD Connector command options and xJCL to UAI via STDIN.
Step 6	UAI validates the command options and builds a SOAP message containing the command options and xJCL and sends it to UAC. This is a request / reply operation, so UAI blocks for the reply.
Step 7	UAC, based on the PROTOCOL value, will invoke the XD Connector. The XD Connector creates the XD SOAP message and sends it to WebSphere.
Step 8	WebSphere replies to the XD Connector with the Job ID which will be needed for the status and job log operations for the current transaction.
Step 9	XD Connector initiates the status operation. When a success or error status is received, the return code, the job output, and the job log are returned to UCMD Manager. At this point, the transaction is considered complete. Please note that the job output is returned on STDOUT and the job log is returned on STDERR.

Physical System Flow

The following figure illustrates the physical system flow of the XD Connector.

Browser not supported