Kbase P104074: How to setup and configure a remote Web Services Adapter?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/1/2010 |
|
Status: Verified
GOAL:
How to setup and configure a remote Web Services Adapter?
GOAL:
How to deploy a Web Service using a remote WSA?
GOAL:
How to setup Web Services Adapter with a remote AdminServer?
GOAL:
How to setup WSA with a remote AdminServer?
FACT(s) (Environment):
OpenEdge 10.x
All Supported Operating Systems
FIX:
For the purpose of this Solution, the following configuration will be assumed:
Server A (local server):
OpenEdge 10.0B
Windows 2003
AppServer
Database
Server B (remote server):
Solaris 9
Tomcat 4.1.30
Web Services Adapter (OpenEdge 10.0B)
General:
- Tomcat will be installed with the default settings.
- WSA security will be disabled during the WSA installation process.
- Port 8080 will be specified for Tomcat during the WSA installation process.
- You have already generated your Web Service proxy.
Configuring the WSA on the remote server:
Download and install Tomcat.
Download and install the Web Services Adapter (WSA).
Copy the wsa directory located in <OpenEdge directory>/servlets into the directory <Tomcat directory>/webapps.
So you should have <Tomcat directory>/webapps/wsa .
(Re)-Start Tomcat.
In a browser enter the following URL: :8080/wsa/wsa1">http://<hostname>:8080/wsa/wsa1
The correct response is an HTML page entitled "WSA Web Services" that contains 'status:wsa1:OK".
Note:
The Web Services Adapter (WSA) does not require an AdminServer to be installed locally, but the WSA does need a syntactically correct ubroker.properties file.
An example of a ubroker.properties file from the WSA machine which has no AdminServer:
[WSA.wsa1]
location=remote
logFile=/usr1/OE_101awrk/wsa1.wsa.log
wsaUrl=http://uxtssolar3:80/wsa/wsa1
This example can be defined on the AdminServer machine as well however the location of the logfile would need to be adjusted to a location local to the machine.
Example of a ubroker.properties file of the AdminServer which is remotely monitoring the WSA:
[WSA.wsa1]
location=remote
logFile=c:\temp\wsa1.wsa.log
wsaUrl=http://uxtssolar3:80/wsa/wsa1
Deploying a Web Service from the local server:
If possible remove the existing WSA instance called "wsa1" from Progress Explorer.
Create a new remote WSA instance from Progress Explorer called "wsa1".
Verify the WSA instance by checking the status in Progress Explorer (right-click on the WSA instance / status).
It should show that the WSA is running.
Deploy your Web Service without enabling it (e.g. called wsTest).
Configure the required Web Service properties of the remote server by using the Progress Explorer or by using the WSAMAN utility from a Proenv DOS window, e.g.:
wsaman -name wsa1 -appname wsTest -prop appServiceHost -value <server A> -setprops
Enable your Web Service.
Restart your Tomcat on the remote server and verify that you can now access your Web Service.