In "traditional" AppServer, one can specify a broker owner (i.e. username) that the agent runs under. If not specified, it inherits the user specified for the Admin Server. That property is N/A for PASOE. Is there a way to specify a username for the agent in PASOE?
Jeff Ledbetter Product Architect | Roundtable Software
Hi Marian. My question is for all supported platforms, but especially Linux in this case.
I want to know how to specify the user/owner (like in traditional appserver) when setting up a PASOE instance.
I've never used tcman. I just set it up in OpenEdge Explorer. Are those options available there somewhere that I am overlooking?
Peter Judge I seem to remember that the -U and -G switches are broken.
The -U and -G switches are supposed to set the file ownership. They don't control the user that owns the process. There is not a way provide the user that runs the process from OEE. What "can" do, at least on windows, is register the process as a service, and start the service under a particular user account.
I tried to edit my post and it disappeared, so here it is again (sorry for duplicate if it reappears):
"The -U and -G switches are supposed to set the file ownership."
That is what I am interested in: controlling the ownership of OS files that my PASOE ABL application writes.
In traditional AppServer, setting the broker owner accomplished this. I do not see a way through the OpenEdge Explorer/Management to set a similar value.
I'm not sure if it is available or not because I don't quite know what I am looking for. In the migration guide, the table indicated that there was no matching username property (N/A) hence my original post. I don't know much about Tomcat; I assumed that OpenEdge Management would hide the complexities.
OEE definitely does not have these options during create. They are only available on the command line.
As Paul point out, they do not work (according to this kbase):
Perhaps this is the work-around:
I've never used tcman so I guess this will be an adventure.
if you are using OE Explorer to start the PASOE instance, it will use what ever user started the AdminServer on that same machine.
So stop your AdminServer (proadsv -stop).
Then change to the user you want to run both AdminServer and PASOE instances
Start AdminServer (proadsv -start)
Once started, start PASOE
Hi Roy. Thanks. That would be a valid work-around but not really a solution to what we (or our customers) may need. Going back to my traditional appserver example, one may have their admin server starting as a root but want/need to specify different appserver broker owners for each appserver that is running. For PASOE, it looks like this is something that has to be done via the command line with tcman. We'll have to educate ourselves on using it and see if that is a solution. I was under the impression that one could do everything they need via OEM.