You can deploy Web services that are contained in J2EE archive files by deploying the archive file, including:
EJB Jar files – can contain J2EE 1.4 EJB Web services.
WAR Files – can contain J2EE 1.4 Web application (servlet based) Web services.
EAR files – can contain EJB Jar files or WAR files that contain J2EE 1.4 Web services.
A Web service within one of these archive files is defined by a combination of the webservices.xml file, WSDL file, and jaxrpcmapping file. The webservices.xml file defines the location of the WSDL file and jaxrpcmapping file, and which EJB/servlet is used to define the Web service. Additional information about the webservices.xml file can be obtained from it’s XSD, as described by these Web sites:
You can deploy Web service clients as part of an EJB, Web
application, or application client. These are defined by a service-ref tag
in the ejb-jar.xml, web.xml or application-client.xml file. Web
Service clients can be deployed with full WSDL, partial WSDL, or
no WSDL as defined in the J2EE 1.4 Web Services specification. If
you deploy with partial or no WSDL, additional information must
be given on deployment for port name, binding and location address.
See “Deploying with a partial WSDL”.
Deploy your J2EE Web service from the command line.
Go to the bin subdirectory of your EAServer installation.
Use the deploy command (EAServer_home/bin/deploy.bat Windows deploy.sh Unix) to deploy the EJB Web service. See “Deploying Web services from the command line”
Deploying J2EE Web services