IBM Integration Bus, Version 10.0.0.2 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Message Sets: Generate WSDL wizard: Configure binding details

Use this panel to specify your SOAP/HTTP or SOAP/JMS binding details.

Generate WSDL wizard

The following panels are shown by the Generate WSDL wizard:

Panel properties

Service name
The Service Name is the value of the name attribute on the service element in the generated WSDL. The exact use of the name depends on products that later use the WSDL such as the SOAP toolkits and UDDI repositories. For example if you later use a SOAP toolkit to generate Java™ from your WSDL, the Service Name is likely to become the Java interface name.
Port name
This property is the name of a specific WSDL port for this service and would typically be derived from the Service Name. One convention would be to provide a Service Name of <xyz> Service and a Port Name of <xyz> Provider.

The Port Name is the value of the name attribute on the port element in the generated WSDL. The exact use of the name depends on products that later use the WSDL such as SOAP toolkits and UDDI repositories. For example if you use a SOAP toolkit to generate Java from your WSDL, the Port Name could become a Java class name.

A choice of two options is presented:

SOAP/HTTP
Select this option to generate a new WSDL definition using existing message definitions with an HTTP transport. This is the default option.
SOAP/JMS
Select this option to generate a new WSDL definition using existing message definitions with a JMS transport.

If you select SOAP/HTTP, the following additional properties are displayed:

SOAP action
This property defines the value for the HTTP SoapAction header. It is possible that an application will use the SoapAction as a mechanism for relating a SOAP message to an implementation method. This is often true with rpc-style WSDL.

If the WSDL definition is to contain multiple operations and they use different SOAP actions, you must add the unique SOAP action values to the WSDL after it has been generated. If all operations use the same SOAP action, specify the value here.

Port address
This property defines the address at which the service is made available. It must be a valid URL and it must include the port number, if it is different from the default HTTP port. An example of a port address is: http://localhost:9080/wassoap/servlet/router

If you select SOAP/JMS, the following additional properties are displayed:

Destination style
The style in which you specify the destination name of the JMS message. The default value is jndi.
Destination name
The name of the destination of the JMS message. This property must be specified according to the Destination style property.
JMS provider name
Select a JMS vendor name from the list. When you select a name from the list, the Initial context factory property is updated automatically with the relevant Java class. The name must match the name of a configurable service that is defined for the integration node to which you deploy the message flow.
Initial context factory

The starting point for a JNDI namespace. A JMS application uses the initial context to obtain and look up the connection factory and queue or topic objects for the JMS provider. When you select a JMS provider name from the list in JMS provider name, the Initial context factory property is updated automatically with the relevant Java class. The default value is com.sun.jndi.fscontext.RefFSContextFactory, which defines the file-based Initial context factory for the WebSphere® MQ JMS provider.

JNDI connection factory
The name of the connection factory that is used. This name must exist in the bindings file. The JNDI connection factory is a JMS QueueConnectionFactory. Alternatively, you can specify the generic JMS ConnectionFactory.
JNDI URL
The JNDI URL for the JMS provider.
Delivery mode
This property controls the persistence mode used for a message. Valid values are:
  • Persistent: the message survives if the JMS provider has a system failure.
  • Non Persistent: the message is lost if the JMS provider has a system failure.
Request message lifetime
This property controls the length of time, in seconds, for which the output JMS message is kept. The default value, 0, is used to indicate that the message must not expire.
JMS request message priority

This property assigns relative importance to the message and can be used for message selection by a receiving web service.

Select a value between 0 (lowest priority) and 9 (highest priority). The default value is 4, which indicates medium priority. Priorities in the range 0 - 4 indicate typical delivery. Priorities in the range 5 - 9 indicate faster delivery.

Reply to Name
The name of the JMS destination to which the receiving application must send a reply message. For a reply message to be returned to this JMS destination, the JMS destination name must be known to the domain of the JMS provider that is used by the receiving client.
Specify JNDI parameters
Enter JNDI context parameters, to be included in the generated WSDL URI, in this table as name-value pairs. If the Use SOAP/JMS interoperability protocol check box is cleared, the JNDI parameters table is disabled, and its values are not generated in the resultant WSDL.
Specify user parameters
Enter additional user parameters, to be included in the generated WSDL URI, in this table as name-value pairs.
Use SOAP/JMS interoperability protocol
This check box is selected by default. If this check box is selected, the generated SOAP/JMS WSDL is in the W3C format, otherwise it is IBM-style WSDL. If you clear this check box, the JNDI parameters table is disabled, and its values are not generated in the resultant WSDL.

ad20940_.htm | Last updated 2015-09-24 12:52:31