Enable endpoints for a Web service-enabled EAR file with an assembly tool

This task explains how to enable an enterprise archive (EAR) file that has been assembled with all the required artifacts for Web services. The artifacts are assembled into a JAR file in the previous task.

 

Before you begin

Before doing this task, we need to Assemble an enterprise bean JAR file into an EAR file.

We can assemble the EAR file with assembly tools that are provided with WebSphere Application Server.

Before use the assembly tool, configure the assembly tool.

 

Overview

This task is one of the steps required to develop and implement a Web service.

We can add one or more router modules to your Web services-enabled application. The EAR file is the Web services-enabled application.

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 Java Message Service (JMS). If no Web services-enabled enterprise bean JAR modules exist in the EAR file, it is not necessary to use these tools. To enable end points for a Web service-enabled EAR file, follow the steps provided in this task section.

 

Procedure

  1. Start an assembly tool. The assembly tools, Application Server Toolkit (AST) and Rational Web Developer, provide a graphical interface for developing code artifacts, assembling the code artifacts into various archives (modules) and configuring related J2EE V1.2, 1.3 or 1.4 compliant deployment descriptors.

  2. Right-click the EJB project to enable.

  3. Click Web Services > Endpoint Enabler.

  4. Specify the transport and router module names in the corresponding fields.

  5. Click OK.

 

Result

You have added an HTTP or JMS router module to the EAR file for each enterprise bean JAR module contained in the EAR file. For HTTP, a context-root is configured for the application so that the Web services 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

 

What to do next

Now that the EAR file has been enabled, one can deploy the EAR file into WebSphere Application Server.


 

Related Tasks


Assembling Web services applications