Deploying Web services

This task explains how to deploy a Web service into WebSphere Application Server.

To deploy Web services that are based on the Web Services for Java 2 Platform, Enterprise Edition (J2EE) specification, you need an enterprise application, also known as an enterprise archive (EAR) file that is configured and enabled for Web services.

If you have a Web service that was deployed on a previous version of WebSphere Application Server, you might want to run the wsdeploy command 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 application containing Web services by using the wsadmin command, specify the -deployws option. 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 the Web services application is 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:

Start install_root\bin\wsadmin from a command prompt. If you are using Linux or Unix platforms, start install_root/bin/wsadmin.sh.
Enter the $AdminApp install EARfile "-usedefaultbindings -deployws" command at the wsadmin prompt.

ResultYou have a Web service installed into the Application Server.

What to do next

You can confirm that the Web services application was deployed by entering the Web service endpoint URL in a browser, then viewing an informative page. The information page contains the following information:

{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 to the applications.

Sub-topics
wsdeploy command

Searchable topic ID: twbs_deployapp2