Configuring endpoint URL information for EJB and JMS bindings with the wsadmin tool

WebSphere Application Server supports the use of the Java Message Service (JMS) API to transport Web services requests, as well as directly accessing Enterprise JavaBeans (EJB), as an alternative to using the HTTP transport.

 

Overview

Deploy the Web service into WebSphere Application Server.

 

Overview

You can use the wsadmin tool to configure Java Message Service (JMS) and Enterprise JavaBeans (EJB) URL fragments for published Web Services Description Language (WSDL) files by using the WebServicesPublishWSDLInfo command.

Configuring 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.

You can use Jacl or Jython scripts, but this task assumes you are that you are using Jacl. For more information about using scripting see Deploying and managing using scripting.

To configure endpoint URL information for EJB and JMS bindings with the wsadmin tool:

1. Launch a scripting command.

2. At the wsadmin command prompt, enter the command syntax. You can use install, installInteractive, edit or editInteractive options. The following example provides the correct syntax form:

   $AdminApp install app_Name {-WebServicesPublishWSDLInfo { 
   {<module_name><protocol><URL_endpoint_information>} {<module_name><protocol> 
   <URL_endpoint_information>}}

   The syntax shows multiple modules and URL endpoints because you can edit multiple URL fragments.where:

   • app_name is the application name

   • module_name is the module name

   • protocol identifies the access method, for example, JMS or EJB

   • URL_endpoint_information is the URL fragment information
   See EJB endpoint URL syntax and Java Message Service endpoint URL syntax for more information on specifying URL endpoint information.

3. Save the configuration changes with the $AdminConfig save command.

 

Results

You have a Web service that is accessible through the JMS transport and configured with JMS bindings, or a Web service that is configured to directly access an EJB with EJB bindings.

 

Example

-WebServicesPublishWSDLInfo

wsadmin "$AdminApp editInteractive MultiprotocolServer {-WebServicesPublishWSDLInfo{
{Inventory.jar JMS jms:/topic?destination=jms/NewsGroupTopic&connectionFactory=jms/NewsGroupTCF}
{Supplier.jar EJB jndiProviderURL=someValue } 
{Inventory.jar EJB jndiProviderURL=someInventoryValue}}}"

 

What to do next

Publish WSDL files.

---

Using the Java Message Service API to transport Web services requests
Using WSDL EJB bindings to invoke enterprise beans from a Web services client

EJB endpoint URL syntax
Java Messaging Service endpoint URL syntax
    

 

---