IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Input fields for the New Web Services Connector wizard

This section describes the input fields for the New Web Services Connector wizard.

Select WSDL page

Web Service Definition

The Web service definition language (WSDL) file describes where the Web service is deployed and what operations the Web service provides. The WSDL file also contains information on the message formats, datatypes, and message transport protocols that should be used between a Web service requester and a Web service provider. The WSDL file is provided by the service provider.

The location of the WSDL. The WSDL can be retrieved from:
  • A URL
  • Your local workspace
  • A registry. IBM® WebSphere® Service Registry and Repository (WSRR) is the registry that hosts the Web service descriptions of WebSphere Multichannel Bank Transformation Toolkit.

Generate Web Services Client page

The Web services client is the application that is used to invoke Web services.

Source Folder
Is the folder in which the Java classes of the Web services client will be generated. The Java classes of the Web services client are used to invoke Web services.
Target Package
Is the package under the folder you specified in the Source Folder field that stores the Java classes of the Web services client. If you do not specify a target package, the Java classes will be stored in the default package under the folder you specified in the Source Folder field.
Generate portable client
This checkbox is selected by default. Accepting the default Generate portable client selection will allow you to copy the WSDL file that you require to another workspace.
Enable MTOM
Enabling MTOM (Message Transmission Optimization Mechanism) optimizes the transmission of messages between the Web services requester and the Web services provider.
Note: For WebSphere Multichannel Bank Transformation Toolkit version 7.1, the Enable MTOM function is not supported. The transmission of messages between the Web services requester and the Web services provider is not affected whether you choose to select or deselect Enable MTOM.
JAX-WS Version
Is the version of JAX-WS used to create the Web services client. JAX-WS is an abbreviation for Java API for XML Web services, and it is a technology that is used to create both Web services and Web services clients.

Service Information page

On the Service Information page, provide detailed information on the Web services connector that you are creating.

Service Definition
Is the location of the WSDL file that is used by the Web services connector and the Web services access operation to invoke Web services.
Note: For WebSphere Multichannel Bank Transformation Toolkit version 7.1, the location of the WSDL file is specified by default in the Service Definition field and cannot be changed.
WSConnector
Is the class of the Web services connector.
Namespace URI
Is the namespace URI for the Web services connector.
Service Name
Is the name of the Web service that you want to invoke and implement.
Port Name
Is the name of the port that the Web services provider is using to receive messages from the Web services requester.
User Name
Is the user name required by the Web services requester to invoke Web services.
Note: For WebSphere Multichannel Bank Transformation Toolkit version 7.1, the User Name field is not supported. Whether or not you specify a user name in the User Name field, a user name is not required to invoke Web services.
Password
Is the password used by the user defined above to invoke Web services.
Note: For WebSphere Multichannel Bank Transformation Toolkit version 7.1, the Password field is not supported. Whether or not you specify a password in the Password field, a password is not required to invoke Web services.
Endpoint address
Is the URL of the Web services that is being invoked.
Note: For WebSphere Multichannel Bank Transformation Toolkit version 7.1, the Endpoint address field is not supported. If you enter a URL in the Endpoint address field, it is not the address used by the Web services access operation to invoke Web services. Instead, the endpoint address specified in the WSDL file you select is used by default to invoke Web services.
Always Generate BTT Web Services Operation
Select this check box if you want to immediately generate a Web services access operation and create data mappings between the WebSphere Multichannel Bank Transformation Toolkit operation context and the Web services data model. If do not want to immediately generate a Web services access operation and create data mappings between the WebSphere Multichannel Bank Transformation Toolkit operation context and the Web services data model, clear this check box.

Derive Self-defined Operations page

Note: This page is used only if you are creating a Web services connector for an automatically generated self-defined operation.
Service Definition
Is the location of the WSDL file that is used by the Web services connector and the Web services access operation to invoke and implement Web services.
Note: For WebSphere Multichannel Bank Transformation Toolkit version 7.1, the location of the WSDL file is specified by default in the Service Definition field and cannot be changed.
Operations list
Is a list of the Web services operations that are described in the WSDL file. From the Operations list, select the Web services operation that you want to invoke. A WebSphere Multichannel Bank Transformation Toolkit self-defined operation will then be automatically generated. This automatically generated WebSphere Multichannel Bank Transformation Toolkit self-defined operation is required to use the Web services operation you selected from the Operations list.
Generated data will use typed data

Typed data are data elements that represent business objects such as Date, Account, and Money. Typed data elements use property descriptors to describe the business object they represent. For example, a property descriptor for a data element of type Money would refer to the single instance of the type Money. Property descriptors use parameters in the form of key-value pairs to add attributes to the type, set attributes as mandatory, or specify an initial value for an attribute. For example, an Account instance must have an account number. The descriptor for the account number field uses the isMandatory="true" key-value pair to indicate this. Non-typed data elements do not have property descriptors.

If you require the automatically generated self-described operation to use typed data, accept the default Generated data will use typed data check box selection. If you do not require the automatically generated self-described operation to use typed data, clear the check box.



Feedback