Configure endpoint URL information for JMS bindings
WebSphere Application Server supports the use of the Java Message Service (JMS) API to transport web services requests, as an alternative to using HTTP.
The application server supports use of the Java Message Service (JMS) API to transport web services requests, as an alternative to HTTP transport. Read about using the Java Message Service (JMS) to transport web services requests to learn more about how web service clients and servers can communicate through JMS queues and topics instead of through HTTP connections.
We can use either the console or property files to configure and manage JMS endpoint URL fragments. To learn about using property files to set and manage the URL fragments, see the information about working with web services endpoint URL fragment property files.
This task describes using the console to configure endpoint URL information for JMS bindings.
Configure a service endpoint is necessary to connect web service clients to any web services among the components being assembled or to any external web services. We can configure the endpoint URL information for JMS during application installation
In this task, enter the JMS endpoint URL prefix to use for each web service-enabled EJB JAR file that belong to the application. The JMS endpoint URLs are included in the Web Services Description Language (WSDL) files published for clients to use.
We can specify HTTP URL prefixes for web services that are accessed through HTTP using the Provide HTTP endpoint URL information panel in the console. These prefixes are used to form complete endpoint addresses that are included in WSDL files when published.
We can specify JMS URL prefixes using the Provide JMS and EJB endpoint URL information panel in the console during or after application installation.
This task applies for JAX-WS and JAX-RPC web services.
To configure JMS URL prefixes:
- Open the console.
- Click Applications > Enterprise Applications > application_instance > Provide JMS and EJB endpoint URL information.
- Locate the list of web services modules that are accessible through JMS transport.
- Type the JMS URL fragment in the URL fragment field. Enter a URL fragment that is a prefix to the initial URL part that is obtained by examining the deployment information of the Web service. See the usage scenario following this task for more information.
The value that you enter is used to define the location attribute of the port soap:address element within the WSDL file that is published using the application_name_ExtendedWSDLFiles.zip or the application_name_WSDLFiles.zip file on the Publish WSDL zip files panel.
Results
You have a web service that is accessible through the JMS transport and configured with JMS bindings.
Example
Suppose an application called StockQuoteService contains an EJB JAR file that is named StockQuoteEJB, which contains one or more web services that are accessible through the JMS transport.
See the using SOAP over Java Message Service to transport web services information to review the example that defines a queue with the JNDI name of jms/StockQuote_Q, and a connection factory with the JNDI name of jms/StockQuote_CF, for the application.
In this example, specified the following string as the JMS URL prefix within the Provide JMS and EJB endpoint URL information panel:
jms:/queue?destination=jms/StockQuote_Q&connectionFactory=jms/StockQuote_CF
The WSDL publisher uses this partial URL string to produce the actual JMS URL for each port component defined in the module. The targetService=<port_name> string is added to the end of the JMS URL, for example:
jms:/queue?destination=jms/StockQuote_Q&connectionFactory=jms/StockQuote_CF&targetService=getQuote
The published WSDL file is used by clients to invoke the web service.
What to do next
Publish the WSDL files to make the deployed web services application available to clients.
Subtopics
- Provide JMS and EJB endpoint URL information
Use this page to specify Java Message Service (JMS) and EJB endpoint URL fragments for web services accessed through SOAP and Java Message Service (JMS) or directly as enterprise beans. Fragments are used to form complete endpoint addresses included in published WSDL files.
Related tasks
Making deployed web services applications available to clients Work with web services endpoint URL fragment property files Configure endpoint URL information for HTTP bindings Use SOAP over JMS to transport web services Configure endpoint URL information to directly access enterprise beans
IBM proprietary JMS endpoint URL syntax (deprecated) EJB endpoint URL syntax