PAS SESSION:SERVER-CONNECTION-ID Value

Posted by Jeff Ledbetter on 11-Oct-2016 09:58

Hi.

When using PAS as a stateless appserver for an ABL application, the server-connection-id contains the following:

"D4ABD9223C4E5AD688B7D40ACC9428DF26D176936884.oepas1"

My question is:

Will the PAS instance name *always* be the 2nd entry in this period-delimited list?

Posted by Peter Judge on 12-Oct-2016 10:48

In curl, add -u tomcat:tomcat  (or whatever's configured; you can see that in OEM/OEE).

All Replies

Posted by Peter Judge on 11-Oct-2016 10:00

Why do you care about that name?
 
Also, it *may* be the ABL application name (which is the same as the instance name by default).

Posted by Jeff Ledbetter on 11-Oct-2016 10:04

I care because I want to display a "friendly name" showing the appserver in use.

Posted by Irfan on 11-Oct-2016 10:16

If I am right, then it is the alias name of the instance and it might dissappear if you enable clustering on that specific PASOE instance.

Posted by Peter Judge on 11-Oct-2016 10:18

OK.
 
The “appserver” in use is a combination of instance (eg http://localhost:8810 or an alias like oepas1  ) and the ABL application name. I don’t believe the instance alias and ABL application names are exposed to clients in the normal but you can get this info via the oemanager REST API (start at  https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/pasoe-admin/list-abl-plication-information.html# ). Note that this requires you to install the oemanager webapp.
 
You should show a combination of those, similarly to how PDSOE does in the Servers view
 
 
 
 

Posted by Jeff Ledbetter on 11-Oct-2016 10:29

For us, this value is set at login and stored in our session table (which all happens on the server) so accessing it via the client isn't really a necessity. We already store the SERVER-CONNECTION-ID and fish out the appserver name for a "traditional" stateless AppServer from this string. I was hoping to do something similar for a PAS server. I don't need this data for establishing a connection, etc. It's just a visual clue to the end-user (and for our tech support).

Posted by Jeff Ledbetter on 12-Oct-2016 09:50

Peter, for funsies I tried what you suggested but received an "unauthorized" response. Is this a small part of a bigger puzzle, or is there some kind of way to pass credentials to the call?

Posted by Peter Judge on 12-Oct-2016 09:52

How  did you ask? you'll need to log in to to access oemanager. The default creds are tomcat/tomcat.

Posted by Jeff Ledbetter on 12-Oct-2016 10:02

I tried using curl (per the example in the doc) as well as my own code (using .Net). How does one log in?

Posted by Peter Judge on 12-Oct-2016 10:48

In curl, add -u tomcat:tomcat  (or whatever's configured; you can see that in OEM/OEE).

Posted by Jeff Ledbetter on 12-Oct-2016 12:09

Ok, that seems to work. Thanks.

Not sure what you mean by "you can see that in OEM/OEE" though.

Posted by Peter Judge on 12-Oct-2016 12:20

There’s a screen somewhere that lets you specify the u/pw used (so it’s not always tomcat/tomcat).

Posted by Jeff Ledbetter on 12-Oct-2016 12:24

Yes, ok, gotcha. I thought you meant some way to see the URI and parameters being passed. :)

This thread is closed