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.
If you have a JAX-RPC Web service that was deployed on a previous version of WebSphere Application Server, you might want to run the wsdeploy command-line tool so that you can benefit from performance features that have been added to this release.
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
Hi there, this is a 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 security for 5.x applications or security for 6.x applications to the applications.