PASOE - WebHandler configuration

Posted by oedev on 04-Jan-2019 09:07

Openedge 11.7.4 64 bit on Windows 

I've installed 11.7.4 and created a new PASOE instance (oepas2) and deployed this to my working directory, i.e. C:\PASOE1174WRK\oepas2

I can start the instance (running HTTP on port 80) and access the manager on http://localhost:8080/manager. All good so far.

Next step is that I want to deploy a WebHandler, so created the simplest handler Ping.p and copied the rcode into C:\PASOE1174WRK\oepas2\openedge as that directory appears to be in the propath. 

The issue is that I'm not exactly sure where in the openedge.properties file the handler definition should go. I've added it like this;

[oepas2.ROOT.WEB]
defaultCookieDomain=
wsRoot=/static/webspeed
srvrDebug=1
defaultHandler=OpenEdge.Web.CompatibilityHandler
handler1 = Ping : /ping
adapterEnabled=1
defaultCookiePath=
srvrAppMode=development

Secondly, is that is the correct configuration, what is the URL to access the web handler (based on an instance name of oepas2 running on port 8080).

Thanks.

OpenEdge Development - Forum
Posted by Sanjeva Manchala on 04-Jan-2019 09:22

Hello,
 
Based on the information you have provided, you can access the webhandler using the following URL:
http://localhost:8080/web/ping
 
Below is the sample URL format to access WebHandler service: http://<host>:<port>/<abl-web-app>/web/<handler-uri>
 
Thanks,
Sanjeev

Posted by Simon L. Prinsloo on 04-Jan-2019 09:17

I expect your URL will be http://localhost:8080/web/ping

All Replies

Posted by Simon L. Prinsloo on 04-Jan-2019 09:17

I expect your URL will be http://localhost:8080/web/ping

Posted by Sanjeva Manchala on 04-Jan-2019 09:22

Hello,
 
Based on the information you have provided, you can access the webhandler using the following URL:
 
Below is the sample URL format to access WebHandler service: http://<host>:<port>/<abl-web-app>/web/<handler-uri>
 
Thanks,
Sanjeev

Posted by oedev on 04-Jan-2019 09:31

Thanks both, that appears to work.

Is that the correct method of deploying web handlers, or, similar to REST services should they be deployed via Developer Studio as a war? It appears I', deploying to default ROOT web app when copying directly to the openedge directory?

Posted by Mike Fechner on 04-Jan-2019 09:36

Web handlers are not deployed in a .war file.
 
They are registered to an URL in the openedge.properties file and the r-code must be accessible via any directory or procedure library in the PROPATH.

Posted by oedev on 04-Jan-2019 11:10

From a presentation done by Peter Judge (pugchallenge.org/.../284_web_handlers_deep_dive.pdf) he shows an example where handlers are configured against [mediaresource.SportsApp.WEB] - where does SportsApp come from ?

[mediaresource.SportsApp.WEB]

defaultHandler = OpenEdge.Web.DefaultWebHandler

handler1 = Sports.SchemaHandler : /{resources}/catalog

handler2 = Sports.DataHandler : /{resources}/data/{service}

handler3 = Sports.DataHandler : /{resources}/data/

handler4 = App.DocumentHandler : /forms/{form-name}

handler5 = Sports.SportsHandler : /CustomerSvc/catalog

Posted by Mike Fechner on 04-Jan-2019 11:12

That's an additional ABL web app (besides the ROOT).

knowledgebase.progress.com/.../How-to-create-multiple-ABL-applications-in-one-single-PASOE-instance

This thread is closed