Cannot deploy web services

[cknaufME]

Hello all,

I'm having an issue deploying web services.

I'm running OpenEdge 10.2B, Apache Server 2.0, and Tomcat 7.0. Apache and Tomcat are connected with mod_jk. I have copied the OE/servlets/wsa file into the Tomcat/webapps directory and Tomcat correctly created the wsa1 folder and inner files. Going to http://localhost:8080/wsa/wsa1 gives me "Status:wsa1:OK:111" and and Tomcat's built-in application manager reports wsa as running.

I am unable to deploy web services through OpenEdge Explorer; the "Deploy" option is greyed out. Querying the adapter through proenv
using

wsaman -i wsa1 -query

returns

Connecting to Progress AdminServer using rmi://localhost:20931/Chimera <8280>
Searching for wsa1 <8288>
Status of Web Services Adapter is Not Running

OpenEdge Explorer also reports wsa1 as not running, but enabled.


I've enabled WSA administration and temporarily disabled authentication


What isn't set up correctly?
Thanks for any help!

 

[Stefan]

10.2B is supported with Java 1.5. Tomcat 7.0 is supported as of Java 1.6.

I had 10.2B running on the openJDK supplied with CentOS 5.5 and everything seemed to work (databases, AppServers, WebSpeed) - I just got jsp errors when doing anything with the web service adapter from within OpenEdge Explorer / Management. Installing Java 1.5, pointing OE 10.2B to use that and installing Tomcat 6.0 got rid of the errors.

Note that I /was/ able to deploy my web services using the command line, but was looking into an issue I had, so decided to fall back to a supported Java version just in case. Java 1.5 did not solve my issue (hyphens in temp-table names) but it did get rid of the OpenEdge Explorer / Management errors when doing things with the WSA.

 

[RealHeavyDude]

It's been a long time since I was fiddling with the WSA - so, just an idea:

If your wsa1 instance servers no other purpose yet then I would try to delete it in the OpenEdge Exploder and create a new instance with the name wsa1 that points to the instance deployed on TomCat. Furthermore in the properties of the was1 instance, especially in the security settings I would turn off "Require WAS Administration Authorization", "Require Web Services Authorization" and "Require WSDL Retrieval Authorization", but, make sure "Enable Web Services" is turned on. You can then, when everything is working, turn the security features back on step by step to see what is breaking it.

Heavy Regards, RealHeavyDude.