WSA not working in 11.5

Posted by zimbru on 21-Jan-2015 02:25

I installed OpenEdge 11.5. After installation I started Progress OpenEdge Management (in a browser:  localhost:9090) and from there I started Tomcat webserver. I expected that Web Services Adapter to start automatically but not.

I used some documentation from older version of OpenEdge where Apache Tomcat is installed separately. I followed the instruction there only the part with configuring WSA:

  1. Copy $DLC\servlets\wsa to <tomcat_InstallDir>\webapps
  2. Modify the <tomcat_InstallDir>\webapps\wsa\WEB-INF\web.xml
    1. Be sure Admin authentication and authorization is commented out
    2. Be sure security is commented out
    3. Turn off “Require Web Service Authorization” this can be done on tomcat
    4. Comment  <security-constraint> ex. <!--  <security-constraint>  … </security-constraint> à
  3. Set webServerAuth=0 at [WSA] in $DLC/properties/ubroker.properties
  4. Change if required wsaURL in $DLC/properties/ubroker.properties in order to point to tomcat wsa (wsaUrl=http://localhost:8080/wsa/wsa1)
  5. Change if required adminAuth=0 in $DLC/properties/ubroker.properties
  6. Restart Tomcat
  7. Test WSA is running

But WSA still not running

In the log I have no errors. I set the logging level to Extended. This is the log:

E:\Progress\wrk11.5\wsa1.wsa.log opened.
[15/01/21@11:08:20.955+0300] P-002716 T-localhost-startStop-1 1 --- --- Logging level set to = 4
[15/01/21@11:08:20.955+0300] P-002716 T-localhost-startStop-1 1 --- --- Log entry types activated: WSADefault,
[15/01/21@11:08:20.962+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Starting WSA adapter wsa1, version 11.5, ID 87ebb8e59bb9c054:-1fa80fc3:14b0b88f89a:-7fff (10620)
[15/01/21@11:08:21.060+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loading the Web Service applications registry
[15/01/21@11:08:21.080+0300] P-002716 T-localhost-startStop-1 3 wsa1 Admin-Provider Initializing Application: default
[15/01/21@11:08:21.082+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0011.xsd
[15/01/21@11:08:21.082+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0010.xsd
[15/01/21@11:08:21.082+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0009.xsd
[15/01/21@11:08:21.083+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0008.xsd
[15/01/21@11:08:21.083+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0007.xsd
[15/01/21@11:08:21.083+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0006.xsd
[15/01/21@11:08:21.083+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0005.xsd
[15/01/21@11:08:21.083+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0004.xsd
[15/01/21@11:08:21.083+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0003.xsd
[15/01/21@11:08:21.083+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0002.xsd
[15/01/21@11:08:21.083+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Loaded XML Schema: E:/Progress/v11.5/properties/schemas/wsad0001.xsd
[15/01/21@11:08:21.290+0300] P-002716 T-localhost-startStop-1 3 wsa1 Admin-Provider Loaded application runtime properties: E:/Progress/v11.5/servers/tomcat/webapps/wsa//wsa1/default.props
[15/01/21@11:08:21.303+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA Loading user role PSCAdmin (10982)
[15/01/21@11:08:21.303+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCAdmin: wsa.wsa1.apps.props read,write (10983)
[15/01/21@11:08:21.303+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCAdmin: wsa.wsa1.apps.defaults read,write (10983)
[15/01/21@11:08:21.303+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCAdmin: wsa.wsa1.apps.enable read,write (10983)
[15/01/21@11:08:21.303+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCAdmin: wsa.wsa1.servlet.services read,write,delete (10983)
[15/01/21@11:08:21.308+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCAdmin: wsa.wsa1.servlet.stats read,write (10983)
[15/01/21@11:08:21.308+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCAdmin: wsa.wsa1.servlet.props read,write (10983)
[15/01/21@11:08:21.308+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCAdmin: wsa.wsa1.apps.stats read,write (10983)
[15/01/21@11:08:21.308+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA Loading user role DEFAULTWSDL (10982)
[15/01/21@11:08:21.310+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role DEFAULTWSDL: wsa.wsa1.wsdl.* read (10983)
[15/01/21@11:08:21.310+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA Loading user role PSCOper (10982)
[15/01/21@11:08:21.310+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCOper: wsa.wsa1.apps.props read (10983)
[15/01/21@11:08:21.310+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCOper: wsa.wsa1.apps.defaults read (10983)
[15/01/21@11:08:21.310+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCOper: wsa.wsa1.apps.enable read (10983)
[15/01/21@11:08:21.310+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCOper: wsa.wsa1.servlet.services read (10983)
[15/01/21@11:08:21.310+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCOper: wsa.wsa1.servlet.stats read (10983)
[15/01/21@11:08:21.311+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCOper: wsa.wsa1.servlet.props read (10983)
[15/01/21@11:08:21.311+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role PSCOper: wsa.wsa1.apps.stats read (10983)
[15/01/21@11:08:21.311+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA Loading user role DEFAULTUSER (10982)
[15/01/21@11:08:21.311+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role DEFAULTUSER: wsa.wsa1.4GL.* execute (10983)
[15/01/21@11:08:21.311+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA Loading user role DEFAULTADMIN (10982)
[15/01/21@11:08:21.311+0300] P-002716 T-localhost-startStop-1 4 wsa1 WSA adding permission to user role DEFAULTADMIN: wsa.wsa1.servlet.services read (10983)
[15/01/21@11:08:21.319+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Initialization parameter: instanceName value: wsa1 (10965)
[15/01/21@11:08:21.319+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Initialization parameter: propertyFileName value: E:\Progress\v11.5/properties/ubroker.properties (10965)
[15/01/21@11:08:21.319+0300] P-002716 T-localhost-startStop-1 3 wsa1 WSA Initialization parameter: InstallDir value: E:\Progress\v11.5 (10965)

I restarted AdminServer, Tomcat web server several times but wsa still not running.

Can anybody help me?

All Replies

Posted by Srinivas Munigala on 21-Jan-2015 02:40

Are you able to access wsa adapter using browser?

eg: http://localhost:8080/wsa/wsa1

It should give the status as below:

WSA Web Services

Status: wsa1: OK: 101            

If not, can you check for the errors in $CATALINA_HOME/logs folder

Posted by zimbru on 21-Jan-2015 03:33

 
I am not able to access the wsa adapter using the browser. It gives me “Web page not available”
 
I checked the log files: catalina.2015-01-21.log and wsa1.wsa.log but no errors found.
 
Are there any other places to look for errors?
 
 
 
[collapse]
From: Srinivas Munigala [mailto:bounce-smunigal@community.progress.com]
Sent: Wednesday, January 21, 2015 10:41 AM
To: TU.OE.General@community.progress.com
Subject: RE: [Technical Users - OE General] WSA not working in 11.5
 
Reply by Srinivas Munigala

Are you able to access wsa adapter using browser?

eg: http://localhost:8080/wsa/wsa1

It should give the status as below:

WSA Web Services

Status: wsa1: OK: 101            

If not, can you check for the errors in $CATALINA_HOME/logs folder

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by Srinivas Munigala on 21-Jan-2015 04:07

Can you check localhost.<date>.log file? does it have any error?

Are you able to access tomcat home page?

Posted by zimbru on 21-Jan-2015 04:40

I checked the file localhost.2015-01-21.log but it’s empty.
 
Yes, I am able to access tomcat home page and I even see the application /wsa in the list of applications.
 
 
 
[collapse]
From: Srinivas Munigala [mailto:bounce-smunigal@community.progress.com]
Sent: Wednesday, January 21, 2015 12:07 PM
To: TU.OE.General@community.progress.com
Subject: RE: [Technical Users - OE General] WSA not working in 11.5
 
Reply by Srinivas Munigala

Can you check localhost.<date>.log file? does it have any error?

Are you able to access tomcat home page?

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by Srinivas Munigala on 21-Jan-2015 05:43

I would like to see your configuration, could you please share following files:

web.xml from $CATALINA_HOME/webapps/wsa/WEB-INF

context.xml from $CATALINA_HOME/conf/

default.props from $CATALINA_HOME/webapps/wsa/wsa1/

wsa1 configuration from ubroker.properties file

Posted by zimbru on 21-Jan-2015 06:18

Sure,
 
Here are the files.
 
web.xml context.xml
 
 
 
Thanx!
 
[collapse]
From: Srinivas Munigala [mailto:bounce-smunigal@community.progress.com]
Sent: Wednesday, January 21, 2015 1:44 PM
To: TU.OE.General@community.progress.com
Subject: RE: [Technical Users - OE General] WSA not working in 11.5
 
Reply by Srinivas Munigala

I would like to see your configuration, could you please share following files:

web.xml from $CATALINA_HOME/webapps/wsa/WEB-INF

context.xml from $CATALINA_HOME/conf/

default.props from $CATALINA_HOME/webapps/wsa/wsa1/

wsa1 configuration from ubroker.properties file

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by Arun Kumar Mohapatra on 21-Jan-2015 06:37

Below are the basic steps need to follow to configure WSA:

Installing WSA servlets into the tomcat containers

------------------------------------------------------------------

Copy paste the directory ${dlc}\servlets\wsa to  tomcat installation’s “webapps” folder

Set the environment variables

---------------------------------------

JAVA_HOME

CATALINA_HOME

Configure the Tomcat server

--------------------------------------

Configure the http port to 8080 or some other.

Disable the security of the wsa by commenting following text from the $TOMCATINSTALL\webapps\wsa\WEB-INF\web.xml

<!--

<security-constraint>

  <web-resource-collection>

     <web-resource-name>wsa1 Admin</web-resource-name>

     <url-pattern>/wsa1/admin/*</url-pattern>

     <http-method>POST</http-method>

  </web-resource-collection>

  <auth-constraint>

     <role-name>PSCAdmin</role-name>

     <role-name>PSCOper</role-name>

  </auth-constraint>

  <user-data-constraint>

     <transport-guarantee>NONE</transport-guarantee>

  </user-data-constraint>

</security-constraint>

-->

Configure the ubroker.properties  file

-------------------------------------------------

Correct the port number in the below property

[WSA.wsa1]

   location=local

   logFile=${wrk}\wsa1.wsa.log

   loggingLevel=2

   enableWsdl=1

   wsaUrl=http://localhost:8980/wsa/wsa1

   adminAuth=0

   adminEnabled=1

  loggingLevel=4

  webAppEnabled=1

  logEntryTypes=WSADefault,DynamicApi,SessionPool,RunProcs,BrokerClient,SOAPProc,WSA,WSAObject

Deploying the WSA service ie. WSM file

-----------------------------------------------------

Start the tomcat server

Check the WSA status as below::

               http://localhost:8080/wsa/wsa1

               http://localhost:8080/wsa/wsa1/wsdl -> display the wsdl deployed

Set the property::

         wsaman -name wsa1 -prop webAppEnabled -value true –setprops

Deploy the WSM service::

                 wsaman -name wsa1 -wsm C:\OpenEdge\WRK\TestService.wsm –deploy

                 This will deploy the service and create a WSDL file which a client can use for connecting to the service

Enable the Service::

                wsaman -name wsa1 -appname TestService enable

Testing the WSA Service

---------------------------------

get the wsdl file for creating the request as below:

         http://localhost:8080/wsa/wsa1/wsdl

This will list all the services deployed and select the service WSDL which we are interested in then copy the uri and  give it to any soap client which will generate the request.

Supply any arguments required for the SOAP request and see the SOAP response.

We usually follow these steps to configure WSA, I hope this will be helpful.

Posted by zimbru on 21-Jan-2015 06:50

I tried to access the wsa in a web browser using the URL:
 
I got the web page:
WSA Web Services
 
Status:wsa1:OK:101
 
So it seems that it is working now. I used a wrong port  before (80 instead of 8980 – the port that tomcat uses).
 
Thank you very much!
 
[collapse]
From: Arun Kumar Mohapatra [mailto:bounce-amohapat@community.progress.com]
Sent: Wednesday, January 21, 2015 2:38 PM
To: TU.OE.General@community.progress.com
Subject: RE: [Technical Users - OE General] WSA not working in 11.5
 
Reply by Arun Kumar Mohapatra

Below are the basic steps need to follow to configure WSA:

Installing WSA servlets into the tomcat containers

------------------------------------------------------------------

Copy paste the directory ${dlc}\servlets\wsa to  tomcat installation’s “webapps” folder

Set the environment variables

---------------------------------------

JAVA_HOME

CATALINA_HOME

Configure the Tomcat server

--------------------------------------

Configure the http port to 8080 or some other.

Disable the security of the wsa by commenting following text from the $TOMCATINSTALL\webapps\wsa\WEB-INF\web.xml

<!--

<security-constraint>

  <web-resource-collection>

     <web-resource-name>wsa1 Admin</web-resource-name>

     <url-pattern>/wsa1/admin/*</url-pattern>

     <http-method>POST</http-method>

  </web-resource-collection>

  <auth-constraint>

     <role-name>PSCAdmin</role-name>

     <role-name>PSCOper</role-name>

  </auth-constraint>

  <user-data-constraint>

     <transport-guarantee>NONE</transport-guarantee>

  </user-data-constraint>

</security-constraint>

-->

Configure the ubroker.properties  file

-------------------------------------------------

Correct the port number in the below property

[WSA.wsa1]

   location=local

   logFile=${wrk}\wsa1.wsa.log

   loggingLevel=2

   enableWsdl=1

   wsaUrl=http://localhost:8980/wsa/wsa1

   adminAuth=0

   adminEnabled=1

  loggingLevel=4

  webAppEnabled=1

  logEntryTypes=WSADefault,DynamicApi,SessionPool,RunProcs,BrokerClient,SOAPProc,WSA,WSAObject

Deploying the WSA service ie. WSM file

-----------------------------------------------------

Start the tomcat server

Check the WSA status as below::

               http://localhost:8080/wsa/wsa1

               http://localhost:8080/wsa/wsa1/wsdl -> display the wsdl deployed

Set the property::

         wsaman -name wsa1 -prop webAppEnabled -value true –setprops

Deploy the WSM service::

                 wsaman -name wsa1 -wsm C:\OpenEdge\WRK\TestService.wsm –deploy

                 This will deploy the service and create a WSDL file which a client can use for connecting to the service

Enable the Service::

                wsaman -name wsa1 -appname TestService enable

Testing the WSA Service

[/collapse]

This thread is closed