Service Adapter Functionality

Topics: Composite Command Service Simple and API Commands

The Service adapter:

• Receives request documents.
• Interprets the request to be either a simple or a composite command.
• Constructs the command and process accordingly.
• Invokes the command and process on the target Connect:Direct server.
• Transforms the Connect:Direct response to a valid XML document according to the published schemas.
• Returns the response document to the invoking component.

The adapter does not require any pre-processing or post-processing logic and also does not enforce any kind of security. Security is provided as part of the iWay container.

In order to fully expose the integration between iWay and Connect Direct, the adapter includes two service types:

• Composite Command Service. The composite command service can be used to construct and submit a Connect:Direct process.
• Simple and API Commands. Simple and API commands are directly invoked as atomic API requests to the Connect:Direct application. These commands include statistics, process, and node commands among others.

The composite command service differs from the simple and API command service as follows:

• There is no API specification for the composite commands. Composite commands are built according to the syntax used to build a .cdp file. A Connect:Direct process is saved on disk as a .cdp file. The syntax of a .cdp file can be found by referring to the CDRequester tool.
• The composite commands have to be invoked within the context of a process command. Since composite commands cannot be invoked on their own, they can be considered as nested commands.
• Since composite commands are submitted as part of a process, command execution may not be performed immediately. The process can be scheduled to start at a specified time.
• Simple commands are directly invoked against the Connect:Direct target server and usually are immediately executed.