XML-SOAP Admin tool

The WebSphere administrative console is available for administering enterprise applications. However, individual Web services are not visible in the administrative console.

The SOAPEarEnabler tool gives you the opportunity to add administrative interfaces to an EAR file. For this purpose, WebSphere Application Server - Express provides a modified version of the Apache SOAP XML Admin interface for each SOAP enabled EAR file. This interface allows you to do the following for each context root:

• List configured services, showing active and stopped services
• Start a service
• Stop a service
• View the Apache SOAP deployment descriptor for a service

http://your_node_name:port/soapsamples/admin/index.html

Note: You must start your WebSphere Application Server - Express instance before you attempt to access the URL.

You cannot use the XML-SOAP Admin tool to add or remove a service. Use the SOAPEarEnabler tool to add or remove services.

Note: To remove a service, you must first start with the original EAR file and then add only the services you want. The SoapEarEnabler tool does not accept a SOAP enabled EAR file as input.

A stopped service is persisted across starts and stops of the application server. Therefore, if you stop a service, it remains stopped until the next time you use the XML-SOAP Admin tool to start it.

You can add the XML-SOAP Admin tool interface to an enterprise application when you SOAP-enable the EAR file using the SOAPEarEnabler Tool. In interactive mode, you are asked whether you want to add the XML-SOAP Admin tool interface. When you reply, yes,the necessary JSP files and bindings are added that allow you to access the XML-SOAP Admin tool interface for the application. The interface is an optional addition because you might not want to expose it in a production environment.