WebSphere Message Brokers
File: ad20950_
Writer: Kate Hostler

Reference topic

This build: July 31, 2007 21:26:19

Generate WSDL wizard: Configure binding details - SOAP/JMS (optional)

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

Generate WSDL wizard

The following panels are shown by the Generate WSDL wizard:

Panel properties

This panel is displayed only when you have selected SOAP/JMS from the previous panel.

SOAP/HTTP
Select this option to generate a new WSDL definition using existing message definitions. This option is shown as not selected.
SOAP/JMS
Select this option to load the WSDL export wizard. This option is shown as selected.

The following properties are displayed for you to specify the bindings for SOAP/JMS:

Destination Style
This field is predefined as 'queue' and cannot be edited.
Initial Context Factory
This is the name of a Java class which will allows the SOAP client or server to perform naming and directory service functions through the standard JNDI interface to a particular type of repository.

The following predefined Java classes are offered, or the user can enter their own:

  • com.ibm.websphere.naming.WsnInitialContextFactory - This corresponds to a repository type of WebSphere Application Server Common Object Services Name Server (part of the CORBA standard)
  • com.sun.jndi.ldap.LdapCtxFactory - This has a repository type of LDAP (Lightweight Directory Access Protocol)
  • com.sun.jndi.fscontext.RefFSContextFactory - This has a file system repository type.

The named class must be available on the classpath for a SOAP client or server using this WSDL binding.

If one of these is selected, the corresponding JNDI Provider Type is selected automatically . If a user-defined value is supplied for the Initial Context Factory, the Provider Type field defaults to LDAP.

Note: The value of this field will determine the Provider Type and additional details that you will need to provide in the JNDI Provider Type Properties section of this wizard panel.
JNDI Connection Factory
This is the JNDI name used to bind to the JMS connection factory and must match your JMS configuration.
JNDI Destination Name
This is the JNDI name for the JMS destination factory and must match your JMS configuration.
Host Name
The host name or IP address of the machine hosting the JNDI provider
Port Number
The port number on the host machine at which the JNDI provider can be contacted
Target Context
The JNDI context in which the search is to be performed
JNDI Provider URL
This is the resulting URL as used by JNDI and is read only. It is comprised of the host name and port number and optionally the target context. For example, iiop://hostname[:port] /[?TargetContext=ctx] (where [] define what is optional and should not be included in the string).
Service Name
The Service Name will be the value of the name attribute on the service element in the generated WSDL. The exact use of the name depends on products that subsequently use the WSDL such as the SOAP toolkits and UDDI repositories. For example if you subsequently use a SOAP toolkit to generate Java from your WSDL, the Service Name is likely to become the Java interface name.
Port Name
This is the name of a specific WSDL port for this service and would usually 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 will be the value of name attribute on the port element in the generated WSDL. The exact use of the name depends on products that subsequently use the WSDL such as the 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.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:26:19

ad20950_ This topic's URL is: