62 lines
3.4 KiB
HTML
62 lines
3.4 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>XML-SOAP Admin tool</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h6><A NAME="wsspxmat">XML-SOAP Admin tool</A></h6>
|
||
|
|
|
||
|
|
|
||
|
|
<p>The WebSphere administrative console is available for administering enterprise applications. However, individual Web services are not visible in the administrative console.</p>
|
||
|
|
|
||
|
|
<p>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:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>List configured services, showing active and stopped services</li>
|
||
|
|
<li>Start a service</li>
|
||
|
|
<li>Stop a service</li>
|
||
|
|
<li>View the Apache SOAP deployment descriptor for a service</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<strong>Accessing the XML-SOAP Admin tool</strong>
|
||
|
|
|
||
|
|
Access the XML-SOAP Admin tool through a Web browser. For example, to use this interface with the soap samples, type:
|
||
|
|
|
||
|
|
<pre>
|
||
|
|
http://<em>your_node_name</em>:<em>port</em>/soapsamples/admin/index.html
|
||
|
|
</pre>
|
||
|
|
|
||
|
|
where <em>your_node_name</em> is the host name of your WebSphere Application Server - Express instance and <em>port</em> is the port number that corresponds to that instance.
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> You must start your WebSphere Application Server - Express instance before you attempt to access the URL.</p>
|
||
|
|
|
||
|
|
<p>You cannot use the XML-SOAP Admin tool to add or remove a service. Use the SOAPEarEnabler tool to add or remove services.</p>
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> 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.</p>
|
||
|
|
|
||
|
|
<p>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.</p>
|
||
|
|
|
||
|
|
<p>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.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<!--<p><strong>Updating an existing SOAP enabled Enterprise Application</strong></p>
|
||
|
|
|
||
|
|
<p>Use the Application Assembly Tool to update the contents and configuration of an enterprise application. For example, to secure the XML-SOAP Admin tool interface for a particular EAR file, use the AAT to secure the resource. However, you cannot use the AAT to add or remove a Web service.</p>
|
||
|
|
|
||
|
|
<p>To add or remove a service to the XML-SOAP Admin tool, start with the original EAR file and run the enabling process again.</p>
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> The SOAP Ear Enabler tool saves a backup copy of the EAR file.</p>-->
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|