The Web services access operation is an IBM® WebSphere® Multichannel Bank Transformation Toolkit server operation that is located on the presentation server side.
Because the Web services access operation is an extension of a WebSphere Multichannel Bank Transformation Toolkit operation, the Web services access operation can be used in a similar way to a WebSphere Multichannel Bank Transformation Toolkit operation. The Web services access operation enables a WebSphere Multichannel Bank Transformation Toolkit application to access Web services and to execute a Web service operation without changing the architecture of the application.
The Web services access operation can be called from a flow processor by using the following two components: the Operation state and the executeOperationAct method.
As shown in Figure 1, the WSAccessOp class extends the BTTServerOperation class to inherit the behavior that is required by a WebSphere Multichannel Bank Transformation Toolkit server operation.
The Web services access operation requires the Web services connector (WSConnector) to enable a WebSphere Multichannel Bank Transformation Toolkit application to access a Web service. Because of the dependency between the WSAccessOp and the WSConnector, the WSAccessOp must be configured to work with the WSConnector. For information on how to configure the WS Access Operation using the external definitions, refer to the Defining the Web services access operation topic.
The WSAccessOp class contains two protected methods that are called to enable a Web service to be invoked: the prepareExecution method and the postExecution method. The prepareExecution method maps data from a WebSphere Multichannel Bank Transformation Toolkit context to the JavaBeans of the Web service. The postExecution method then maps the Web service JavaBeans to data from the WebSphere Multichannel Bank Transformation Toolkit context. If you want to create custom data mappings, you can override the prepareExecution and the postExecution methods.