After assembling the artifacts required to enable the Web module for Web services into an enterprise archive (EAR) file, you can deploy the EAR file into the application server.
To deploy Java-based Web services, you need an enterprise application, also known as an EAR file that is configured and enabled for Web services.
A Java API for XML-Based Web
Services (JAX-WS) application is packaged as a Web archive (WAR) file or a
WAR module within an Enterprise Archive (EAR) file. A JAX-WS application does
not require additional bindings and deployment descriptors for deployment
whereas a JAX-RPC Web services application requires you to add additional
bindings and deployment descriptors for application deployment. JAX-WS is
much more dynamic, and does not require any of the static data generated by
the deployment step required for deploying JAX-RPC applications.
To install a JAX-WS application, you only need to
install the JAX-WS enabled EAR file. You do not need to use the wsdeploy command.
Use the wsdeploy command only with JAX-RPC
applications that are used with the Feature Pack for Web Services product.
The wsdeploy command is not applicable for JAX-WS applications.
This task is one of the steps in developing and implementing Web services.
You can use either the administrative console or the wsadmin scripting tool to deploy an EAR file. If you are installing an containing Web services by using the wsadmin command, specify the -deployws option for JAX-RPC applications. If you are installing an application containing Web services by using the administrative console, select Deploy WebServices in the Install New Application wizard. For more information about installing applications using the administrative console see Installing a new application.
If your JAX-RPC Web services application was previously deployed with the wsdeploy command, it is not necessary to specify Web services deployment during installation.
The following actions deploy the EAR file with the wsadmin command:{http://webservice.pli.tc.wssvt.ibm.com}RetireWebServices Hello! This is an Axis2 Web service!The first line of this information is variable, depending on your Web service. The URI in the brackets is the namespace and the string following that (in this example, RetireWebServices), is the name of the port used to access the Web service.
The next step you might want to consider is to apply or security for 6.x applications to the applications.
In this information ...Subtopics
| IBM Redbooks, demos, education, and more |