Try OpenEdge Now
skip to main content
Configuration
Configuring OpenEdge SOAP Web Services : Managing Web Services Adapter (for OpenEdge SOAP Web Services) instances : Creating a new Web Services Adapter (for OpenEdge SOAP Web Services) instance
 

Creating a new Web Services Adapter (for OpenEdge SOAP Web Services) instance

OpenEdge Management and OpenEdge Explorer provide a sample Web Services Adapter (WSA) instance (wsa1). You can edit the wsa1 sample configuration, and you can create new WSA instances.
Note: To complete the creation of a WSA instance after creating it in the management console and before you can deploy SOAP Web services to it, you must update your JSE configuration and edit the WSA's web.xml file. Add a servlet and servlet-mapping element for the instance, then restart your JSE. This creates the root sub-path for the new instance, initializes and runs it. For more information, see OpenEdge Development: Web Services and your JSE documentation.
To create a new WSA instance:
1. From the drop-down for Resources on the management console menu, click New OpenEdge Resource > WebServices Adapter. The WebServices Adapter Configuration page appears.
2. Type the name of the new Web Services Adapter (for OpenEdge SOAP Web Services) in the New Web Services name field.
Note: The Web Services Adapter (for OpenEdge SOAP Web Services) name is case sensitive and can include any character except a period (.) or square brackets ([ ]). The name must be unique among all configured NameServer names.
3. Type the URL in the Url field.
This is a URL that directly addresses the WSA instance on the Internet and serves as the root for other URLs required to access SOAP Web services and other functions of the WSA.
Form the root URL according to the following format:
http://host[:port][/jse-context]/webapp-context/servlet-instance
Where:
*host— The name of the machine where the WSA is installed (Default: localhost).
*port — The HTTP port number on the WSA machine (Default: 80).
*jse-context — The JSE context path name is present only when you have a Web server between your Java Servlet Engine (JSE) and the client application. It specifies the path name that you define in your Web server configuration to send client requests to your JSE.
*webapp-context — The Web application context path name always exists and specifies the path name that you define in your JSE configuration to identify the WSA as a servlet application.
*servlet-instance — The servlet-mapping name for the WSA instance (WSA Web application) specified in OpenEdge-install-dir\servlets\wsa\WEB-INF\web.xml. This is also the name by which the WSA instance appears in the Web Services Adapter folder in the management console.
4. Select the WSA installation location for this instance from these choices:
*local — The WSA is installed on the machine where the selected AdminServer is running.
*remote — The WSA is installed on a network machine that is remote from the selected AdminServer.
5. Click Save. The new WSA instance appears under the Web Services Adapter folder.
You can now configure the properties of the new instance. Note that when you create a new instance, it has a copy of the default configuration. Initially, the instance is enabled only for administration, allowing you to modify its properties and deploy SOAP Web services to it without allowing premature user access to an incomplete configuration.