Enable an EAR file for Web services with the endptEnabler command

Use the endptEnabler command-line tool to enable an EAR file for Enterprise Java Beans (EJB) modules that contain Web services and to specify whether the Web services are exposed using SOAP over JMS or SOAP over HTTP.

Before doing this task, we need to assemble a Web services-enabled enterprise JAR into an EAR file.

The endptEnabler command-line tool adds one or more router modules to the EAR file for each JAX-WS or JAX-RPC based Web service-enabled enterprise bean JAR module within the EAR file. A router module provides an endpoint for the Web services in a particular enterprise bean JAR module.

Each router module supports a specific transport such as HTTP or JMS. An HTTP router module is a Web Archive (WAR) module that provides an HTTP endpoint for each of the Web services contained within a particular enterprise bean JAR module. Likewise, a JMS router module is an enterprise bean JAR module that contains a Message Driven Bean (MDB) that serves as the message listener for requests intended for the Web service endpoints.

If no enterprise bean JAR modules exist in the EAR file, it is not necessary to use this tool.

 

1. Invoke the endptEnabler command from the install_root\bin directory. For operating systems such as Linux, HP-UX, Solaris, AIX or z/OS, invoke the command from the install_root/bin directory.

2. Enter the name of the EAR file, when prompted.

3. Enter various input values as requested by the endptEnabler command. we are prompted for various input values for each enterprise bean JAR module that is enabled for Web services in the EAR file. Typically, you accept the defaults for each prompt. To learn about the properties of this command, see the endptEnabler command documentation.

   1. Specify an HTTP router module to transport the EJB-based Web service. Use the -transport http option to indicate the Web service is available using HTTP. One router module is created for each enterprise bean JAR file that contains either JAX-WS or JAX-RPC Web services.

   2. Specify an JMS router module to transport the EJB-based Web service. Use the -transport jms option to indicate the Web service is available using JMS. One router module is created for each enterprise bean JAR file that contains either JAX-WS or JAX-RPC Web services.

 

Results

An HTTP or JMS router module is added to the EAR file for each enterprise bean JAR module within the EAR file that contains Web services endpoints. For HTTP, a context-root is configured for the application so that the Web service can be invoked through a Web address. The Web address used to invoke the Web service is:

http://host[:port]/<context-root>/services/<port-component-name>

Ensure that you install the HTTP or JMS router module that you generated with the endptEnabler command onto the same target as the Web services enterprise bean JAR files. These HTTP or JMS router modules are included in the Web services application and they need to use the runtime libraries of the application server.

 

Next steps

Deploy the EAR file onto the appserver. An assembled EAR file that is enabled for Web services is required for deployment.

If we are using JMS as a transport for the Web service requests, define the various JMS objects such as queues, topics, or connection factories, that will be used by the application prior to installing the application.

endptEnabler

 

Related tasks

Enable an EAR file for EJB modules that contain Web services
Assemble Web services applications
Use SOAP over Java Message Service to transport Web services