This task explains how to enable the enterprise archive (EAR) file that you have assembled with artifacts that are necessary to build a Web service. The EAR file is an application that is enabled for Web services.
You need to assemble the Java archive (JAR) file before you can assemble these files into the EAR file, because the enterprise JAR file is an artifact that is required to build the EAR file.
You can add router modules to your application that is enabled for Web services with either the endptEnabler command-line tool with assembly tools provided with WebSphere Application Server. The tool that you choose to use for this task depends on your preference to work with a command-line tool or a graphical user interface.
These tools add one or more router modules to the EAR file for each Web service-enabled EJB module contained in the EAR file. A router module provides an endpoint for the Web service in a particular EJB module.
You should not modify the contents of the EJB module or the Web module that was generated by the WSDL2Java or Java2WSDL command-line tools. If you do, an error occurs during run time. The following is an example of the error that displays:
"Error]- WSWS3142E: Error: Could not find Web services engine.]: javax.servlet.ServletException: WSWS3142E: Error: Could not find Web services engine."
Each router module supports a specific transport such as HTTP or Java Message Service (JMS). If no enterprise bean JAR modules are located in the EAR file, it is not necessary to use these tools.
(dependent on configuration)
Related tasks
Assembling Web services applications
Related reference
endptEnabler command