InfoCenter Home > 6.6.0.10: SoapEarEnabler toolThe SoapEarEnabler tool is a Java application that enables a set of SOAP services within an Enterprise Application Archive (EAR). The SoapEarEnabler guides you through the required steps to enable one or more services within an application. The SoapEarEnabler tool makes a backup copy of your original EAR in the event you need to remove or add services at a later time. After you enable web services, you must install the EAR in WebSphere Application Server. You will be prompted as to whether you wish to add the adminsitration client to the EAR. This is a Web-based client that will allow to list all active services for a specific context from a browser window. With this interface, you can stop and start existing services. You might choose to not add this interface for security reasons, or you might want to secure the interface before making a service available. For more information on securing resources, see article Securing SOAP services. Before invoking SoapEarEnabler, first create an 4.8.2.1: Apache SOAP deployment descriptor for each service to be enabled. Invoke the SOAP EAR enabler tool from the WebSphere Application Server bin directory using the command, SoapEarEnabler on the Windows platform or SoapEarEnabler.sh on UNIX platforms. The tool operates in two modes: Specify all required command line arguments to use the tool in silent mode.
Interactive modeThe SoapEarEnabler tool prompts you for all required information. The following dialog is an example of using the tool in interactive mode.
Silent ModeIn silent mode, supply the arguments in the same order as for the interactive prompts.
The following example describes how to to use the tool in silent mode:
Silent Mode examplesThe following is an example of deploying
one ejb as a non-secured service: soapearenabler soap.ear 1 d:\xml-soap\java\samples\ejbadder\deploymentdescriptor.xml y adderservice-ejb.jar 1 samples.jar n /soap The following is an example of deploying one ejb as a non-secured service, and one java class as a secured service: soapearenabler soap.ear 2 d:\xml-soap\java\samples\ejbadder\deploymentdescriptor.xml y adderservice-ejb.jar 1 samples.jar n d:\xml-soap\java\samples\stockquote\deploymentdescriptor.xml n 1 samples.jar y /soap /soap-sec The following is an example of deploying 2 java classes as non-secured services: soapearenabler soap.ear 2 d:\xml-soap\java\samples\stockquote\deploymentdescriptor.xml n 1 samples.jar n d:\xml-soap\java\samples\addressbook\deploymentdescriptor.xml n 1 samples.jar n /soap The line breaks in the above examples have been modified for this documentation. Typically, commands are issued on a single line. |
| ||||
|