The WSA is installed in a JSE as a single Web application that you can instantiate as one or more servlets (WSA instances). Each WSA instance provides a single point of management for one or more deployed SOAP Web services. Thus, to begin working with the WSA in OpenEdge Management or OpenEdge Explorer:
1. Create a new WSA instance if none exists or you need another, and configure it for operation. (The WSA comes installed with one local WSA instance, wsa1.)
2. For a WSA instance where you want to deploy a new SOAP Web service, optionally review and update the default property settings that govern the run-time behavior of new SOAP Web service deployments. You can also adjust these settings for each SOAP Web service individually after you deploy it.
3. If you want to import an existing SOAP Web service, first export the SOAP Web service from the context of the WSA instance where it is currently hosted.
4. Deploy the new SOAP Web service or import the existing SOAP Web service into the context of a WSA instance that you have configured.
5. As you client-test the SOAP Web service, review the WSA instance status and statistics, and update any WSA instance properties as needed. Such changes affect all SOAP Web services deployed to the same WSA instance.
Note: To apply changes to most WSA properties, you must restart the JSE where the WSA is installed. You can make temporary changes to selected WSA properties at run time without restarting the JSE. However, you must update the WSA instance configuration to make these changes permanent.
6. As you client-test the SOAP Web service, review the SOAP Web service status and statistics, and update any SOAP Web service properties as needed. Such changes affect only the selected SOAP Web service. For most of these changes, you must disable the SOAP Web service before you make them, then enable the SOAP Web service afterward to evaluate the effect.
