Creating a WSA instance

Try OpenEdge Now

Administration

Web Services Adapter Administration : Managing the Web Services Adapter : Creating one or more WSA instances : Creating a WSA instance

Creating a WSA instance

You use OpenEdge Management or OpenEdge Explorer to create a WSA instance.

To create a WSA instance:

1. Choose one:

From the management console bar, click the Resources tab's dropdown arrow. Choose New OpenEdge Resource-->WebServices Adapter.

Click the Resources tab in the management console menu bar. In the Details frame, click New Resource Monitor. The New Resource Monitor page appears. Click WebServices Adapter.

The WebServices Adapter Configuration page appears.

2. Type the name of the new Web Services Adapter in the New Web Services name field.

Note: The Web Services Adapter 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 Web services and other functions of the WSA.

Form the root URL according to the following format:

http://host[:port][/java-container-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).

java-container-context — The Java container context path name is present only when you have a Web server between your Java container and the client application. It specifies the path name that you define in your Web server configuration to send client requests to your Java container.

webapp-context — The Web application context path name always exists and specifies the path name that you define in your Java container 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.

6. Using the tabbed interface, configure the desired properties.

7. If the WSA instance is remote, perform the following additional steps on the system where the WSA is installed:

a. In the ubroker.properties file, copy and rename the section corresponding to the sample WSA instance provided (wsa1) to a new section—in essence, cloning wsa1's section to a new section.

b. Then, edit the properties in the new WSA instance's section as desired.

8. In the web.xml file, use a text editor (or whatever tool your Java container provides), to copy and rename the section corresponding to the sample WSA instance provided (wsa1) to a new section—in essence, cloning wsa1's section to a new section.

Then, check and perhaps modify, the web.xml items listed in the following table.

Table 17. web.xml file items to check
Check this attribute . . .	Which indicates . . .	And whose default is . . .
<init-param> <param-name> InstallDir <param-value>	The location on disk of the OpenEdge installation directory	C:\Progress\OpenEdge
<init-param> <param-name> instanceName <param-value>	The name of the WSA instance	wsa1
<init-param> <param-name> propertyFileName <param-value>	The location of the ubroker.properties file Note: It need not reside in InstallDir.	C:\Progress\OpenEdge\ properties\ ubroker.properties
<servlet-mapping> <servlet-name>	The name of the WSA servlet	wsa1_servlet
<servlet-mapping> <url-pattern>	The URL pattern of the WSA servlet	/wsa1/*
<security-constraint> <auth-constraint> <role-name>	The role-name of the default WSA administrator	PSCAdmin
<security-constraint> <auth-constraint> <role-name>	The role-name of the default WSA operator	PSCOper
<security-constraint> <user-data-constraint> <transport-guarantee>	The type of connection for accessing WSA administration, WSDL, and Web service applications	CONFIDENTIAL (if you are using SSL)NONE (if you are not using SSL)

Progress Software Corporation recommends that you use names consistently when you name a remote WSA instance and when you edit entries corresponding to the remote WSA instance in the ubroker.properties and web.xml files.