Web services access

The Web services access component consists of a set of infrastructure modules that enables IBM® WebSphere® Multichannel Bank Transformation Toolkit applications to interact with Web services.

Figure 1. Infrastructure of the WebSphere Multichannel Bank Transformation Toolkit Web services component.
Infrastructure of the WebSphere Multichannel Bank Transformation Toolkit Web services access component.

WebSphere Multichannel Bank Transformation Toolkit programming model overview

In the WebSphere Multichannel Bank Transformation Toolkit programming model, a UI flow is the set of tasks that are required to complete a basic financial transaction, including data input, data validation, and interaction with external services. Services provide high-level application functions to support objects such as host communications and printers. Operations manage the operation context and the operation formatter. The context hierarchy stores the data that is required by the services. During the execution of an operation, data is formatted and sent to the services, and then the reply data is unformatted from the service back to the context. The operation formatters build the formatted data that is interchanged with the services and interpret data that is received from the services.

Web services invocation for WebSphere Multichannel Bank Transformation Toolkit Web services applications

Web services invocation for WebSphere Multichannel Bank Transformation Toolkit applications follows the WebSphere Multichannel Bank Transformation Toolkit programming model. The Web services access component consists of the following modules:
Web services access operation
Is a server operation in the presentation layer that reroutes a request to the remote operations that are encapsulated in the Web services.
Web services connector
Is the component that is required by the Web service access operation to access Web services.
Web services mapper
Is a formatter that is required by a Web services access operation to map data between the WebSphere Multichannel Bank Transformation Toolkit context and the Web services JavaBeans.

During a Web service invocation, the Web services access operation first retrieves data from the WebSphere Multichannel Bank Transformation Toolkit context. The Web services access operation then calls the Web services mapper to build the JavaBeans that are required as input parameters by the Web services provider. The JavaBeans that have been built by the Web services mapper are then used by the Web services connector to invoke a remote Web services operation. After the Web services have been invoked, the Web services connector returns JavaBeans from the Web services to the WebSphere Multichannel Bank Transformation Toolkit application, and the Web services mapper maps data that has been sent from the Web services provider to the WebSphere Multichannel Bank Transformation Toolkit context.

Tooling provided by WebSphere Multichannel Bank Transformation Toolkit to invoke Web services.

As shown in Figure 1, an integrated development environment (IDE) is provided by WebSphere Multichannel Bank Transformation Toolkit for application development. The IDE provided by WebSphere Multichannel Bank Transformation Toolkit provides the tooling that is required to invoke Web services. For more information on WebSphere Multichannel Bank Transformation Toolkit Web services tooling, refer to the Web services tooling topic.