Enable an EAR file for Web services with the endptEnabler command

This task explains how to use the endptEnabler command-line tool to enable an enterprise archive (EAR) file for Web services.

Before doing this task, you 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 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 Java Message Service (JMS). If no enterprise bean JAR modules exist in the EAR file, it is not necessary to use these tools.

Enable an EAR file with the endptEnabler command by following the actions listed in the steps for this task section.

1. On the Qshell command line, invoke the endptEnabler script from the /QIBM/ProdData/WebSphere/AppServer/V6/Base/bin directory.

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

3. Enter various input values as requested by the endptEnabler command. You 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. See endptEnabler prompts and commands for more information about endptEnabler command prompts.

ResultAn HTTP or JMS router module is added to the EAR file for each enterprise bean JAR module that is enabled for Web services and contained in the EAR file. 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

What to do next

Related tasks
Assembling Web services applications