Enable a Web services-enabled EAR file with the endptEnabler command
Before doing this task, you need to assemble a Web services-enabled EJB JAR into an enterprise archive (EAR) file.
The endptEnabler command-line tool adds one or more router modules to the EAR file for each EJB JAR module within the EAR file. A router module provides an endpoint for the Web services in a particular Enterprise JavaBean (EJB) JAR module.
Each router module supports a specific transport such as HTTP or Java Messaging Service (JMS). If there are no EJB JAR modules in the EAR file, it is not necessary to use these tools.
To enable an EAR file with the endptEnabler command...
- Invoke the endptEnabler command from the $WAS_HOME\bin directory. If you are using UNIX, invoke the command from the $WAS_HOME/bin directory.
- Enter the name of the EAR file, when prompted.
- Enter various input values as they are requested by the endptEnabler command. You are prompted for various input values for each Web services-enabled EJB JAR module in the EAR file. Typically, accept the defaults for each prompt. See endptEnabler prompts and commands for more information about endptEnabler command prompts.
An HTTP or JMS router module is added to the EAR file for each Web services-enabled EJB JAR module contained in the EAR file. For HTTP, a context-root is configured for the application so the Web service can be invoked through a URL. The URL used to invoke the Web service ishttp://host[:port]/context-root/services/port-component-name
Deploy the EAR file into WAS.
See AlsoAssembling Web services applications based on Web Services for J2EE