Propath question on PASOE win 11.7

Posted by OctavioOlguin on 01-Jun-2019 17:12

I have this setting on openedge.properties (returns inserted at posting time):

[AppServer.Agent]

....
numInitialSessions=5

PROPATH=${DLC}/tty,${DLC}/tty/netlib/OpenEdge.Net.pl,
c:\home\appsch\webapps\ROOT\WEB-INF\openedge\tap,
${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\sch,
${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\dwh,
${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\appserver,
${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\ciateq

....

workDir=${CATALINA_BASE}/work

The testing program is

.....

RUN tap\GetPropath.p on hServer (output pProP).
UPDATE pProP VIEW-AS EDITOR SIZE 75 BY 18.

and this is the position of  GetPropath.p (*.r, in fact) on the server's directory_

I wonder, why it isn't run correctly when using RUN GetPropath.p on hServer , as getpropath.r target file is on "root" of TAP/ and propath explicitly points to c:\home\appsch\webapps\ROOT\WEB-INF\openedge\tap, if I want to run, should use strictly RUN tap\GetPropath.p on hServer...

I'm migrating from Appserver 11.2, and have some big number of files that currently run perfectly (and desktop app since 1997 or so) with the assumption that propath + xplicit(extra path) + "\someprogram.p" would suffice...

on desktop (client networking) i have following instruction on programs..:       run procs\com\com01001.w.   it will run as propath has an entry: c:\tap\ and on disk, this is a valid filename  c:\tap\procs\com\com01001.w...

But apparently, on pasoe, it won't work...

Am I missing other configs?  

TIA

Jorge Olguin

Posted by OctavioOlguin on 03-Jun-2019 14:03

Never mind.....  It didn't run at the time... I did restarted first, instance several times, later equipment,  and yet it didn't run with file not found error....

But today I got to office to get at the problem, and It behaves as intended... sorry.. I don't know what I missed...

Posted by OctavioOlguin on 03-Jun-2019 14:10

Sorry....  Never Mind...

Two days ago, I restarted instances, computer several times, and yet still din't run, as error was (file no found).

Today I came to office to find it works just fine, as intended...

I'm very embarrassed... Sorry for your time

Thanks a lot ...

Posted by OctavioOlguin on 03-Jun-2019 14:14

Sorry for your time..

Coming to office this morning, all works as expected....

At the time I restarted instance several times, even computer.  The error was "GetPropath.p was not found. (293)"

Thanks a lot....

Posted by OctavioOlguin on 03-Jun-2019 22:27

Thanks to my Progress vendor, (Marcela Mtz-SIT consultores) I found that the place where I'd define propath is:

[AppServer.Agent.appsch]    being (appsch) the instance name....

Posted by OctavioOlguin on 03-Jun-2019 22:30

Thanks to my Progress Vendor, (Marcela Martínez-SIT consultores) I found that the place where I'd update propath value is:

[AppServer.Agent.appsch.Propath]

All Replies

Posted by Stefan Drissen on 03-Jun-2019 08:32

1. what do you mean with isn't run correctly - which error do you get?

2. If your propath points to tap and you are running tap/whatever.p then whatever.p (or .r) is expected to be in tap/tap.

Posted by OctavioOlguin on 03-Jun-2019 14:03

Never mind.....  It didn't run at the time... I did restarted first, instance several times, later equipment,  and yet it didn't run with file not found error....

But today I got to office to get at the problem, and It behaves as intended... sorry.. I don't know what I missed...

Posted by OctavioOlguin on 03-Jun-2019 14:10

Sorry....  Never Mind...

Two days ago, I restarted instances, computer several times, and yet still din't run, as error was (file no found).

Today I came to office to find it works just fine, as intended...

I'm very embarrassed... Sorry for your time

Thanks a lot ...

Posted by OctavioOlguin on 03-Jun-2019 14:14

Sorry for your time..

Coming to office this morning, all works as expected....

At the time I restarted instance several times, even computer.  The error was "GetPropath.p was not found. (293)"

Thanks a lot....

Posted by OctavioOlguin on 03-Jun-2019 21:28

Sorry.. I meant:  "procedure GetPropath.p not found. (263)"

but I see know what's wrong with my configuration....

I did following command on a administrator proenv on App directory:

C:\home\appsch>bin\oeprop AppServer.Agent.Propath=C:\home\appsch\openedge,${DLC}/tty,${DLC}/tty/netlib/OpenEdge.Net.pl,C:\home\appsch\webapps\ROOT\WEB-INF\openedge\tap,C:\home\appsch\webapps\ROOT\WEB-INF\openedge\sch,${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\dwh,${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\appserver,${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\ciateq

and restarted service... (restarted server machine)

When run procedure GetPropath.p

DEFINE OUTPUT PARAMETER pProPath AS CHARACTER NO-UNDO.

/* *************************** Main Block *************************** */

pPropath = PROPATH + "~n~nConnected Tap: " + STRING(CONNECTED("TAP")) 
+ "~n~nConnected SCH: " + STRING(CONNECTED("SCH"))
+ "~n~nConnected DWH: " + STRING(CONNECTED("DWH"))
+ "~n~nTempDir: " + SESSION:TEMP-DIRECTORY
+ "~n~n DESDE APPSERVER ".

I get following:

c:\home\appsch\webapps\ROOT\WEB-INF\openedge,c:\home\appsch\openedge,C:\Progress\OpenEdge\tty,C:\Progress\OpenEdge\tty\adecomm.pl,C:\Progress\OpenEdge\tty\adecomp.pl,C:\Progress\OpenEdge\tty\adeedit.pl,C:\Progress\OpenEdge\tty\adeshar.pl,C:\Progress\OpenEdge\tty\OpenEdge.BusinessLogic.pl,C:\Progress\OpenEdge\tty\OpenEdge.Core.pl,C:\Progress\OpenEdge\tty\OpenEdge.ServerAdmin.pl,C:\Progress\OpenEdge\tty\netlib\OpenEdge.Net.pl,C:\Progress\OpenEdge,C:\Progress\OpenEdge\bin

Connected Tap: yes

Connected SCH: yes

Connected DWH: yes

TempDir: c:\t\

DESDE APPSERVER

If you look closely, you'll notice that propaths are diffierent, so  appserver is running some other propath, not the one under [AppServer.Agent]

 I wonder where this Propath came from?  on openedge.properties file there is another propath setting, but it won't match to what I got on runtime.... 

[AppServer.Agent.appsch]

So I'm really confused, as docs mention [AppServer.Agent] as the place to change propath...

Posted by OctavioOlguin on 03-Jun-2019 21:53

This is openedge.properties

##########################################################################
## ##
## Copyright (c) 1998-2014 by Progress Software Corporation ##
## ##
## All rights reserved. No part of this program or document may be ##
## reproduced in any form or by any means without permission in writing ##
## from Progress Software Corporation. ##
## ##
##########################################################################
#
# -------------------- openedge.properties ------------------------------
#
# Property File for the Pacific Application Server for OpenEdge
#
#
# This definition file includes the properties that you can define in
# a Pacific AppServer for OpenEdge.
#
# All information about the properties in this property file may be found
# in the file:
#
# openedge.properties.README.
#
##########################################################################
##
#
# AppServer specific properties
#
[AppServer]
allowRuntimeUpdates=0
applications=appsch
collectMetrics=1
statusEnabled=1

#
# Default properties for Session Manager
#
[AppServer.SessMgr]
agentExecFile=${psc.as.oe.dlc}/bin/_mproapsv
agentListenerTimeout=300000
agentLogEntryTypes=
agentLogFile=
agentLoggingLevel=2
agentLogThreshold=0
agentNumLogFiles=3
agentStartLimit=0
agentStartupParam=-T c:\t -db TAP -H sucahersa3 -S 2500 -U schAS1 -P schAppS1 -db SCH -S 2499 -H sucahersa3 -db DWH -H sucahersa3 -S 2999 -U schAS1 -P schAppS1
connectionWaitTimeout=3000
idleAgentTimeout=300000
idleConnectionTimeout=300000
idleResourceTimeout=0
idleSessionTimeout=300000
ipver=IPv4
maxABLSessionsPerAgent=200
maxAgents=10
maxConnectionsPerAgent=16
numInitialAgents=1
publishDir=${catalina.base}/openedge
requestWaitTimeout=15000
socketTimeout=3000

[AppServer.Agent]
agentMaxPort=62202
agentMinPort=62002
agentShutdownProc=
agentStartupProc=
agentStartupProcParam=
agentTableParam=-n 200
collectStatsData=0
flushStatsData=0
infoVersion=9010
keyAlias=
keyAliasPasswd=
# keyStorePasswd=
keyStorePath=.\keys\
lockAllExtLib=
lockAllNonThreadSafeExtLib=
noSessionCache=0
numInitialSessions=5
PROPATH=C:\home\appsch\openedge,${DLC}/tty,${DLC}/tty/netlib/OpenEdge.Net.pl,C:\home\appsch\webapps\ROOT\WEB-INF\openedge\tap,C:\home\appsch\webapps\ROOT\WEB-INF\openedge\sch,${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\dwh,${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\appserver,${CATALINA_BASE}/webapps\ROOT\WEB-INF\openedge\ciateq
sessionActivateProc=
sessionConnectProc=
sessionDeactivateProc=
sessionDisconnProc=
sessionShutdownProc=
sessionStartupProc=
sessionStartupProcParam=
sessionTimeout=180
sslAlgorithms=
sslEnable=0
usingThreadSafeExtLib=
uuid=
workDir=${CATALINA_BASE}/work

[appsch]
webApps=ROOT

[appsch.ROOT]
allowRuntimeUpdates=0
collectMetrics=1
statusEnabled=0

[appsch.ROOT.APSV]
adapterEnabled=1
enableRequestChunking=1
useHTTPSessions=1

[appsch.ROOT.SOAP]
adapterEnabled=0
adminEnabled=1
adminSoapAction=urn:services-progress-com:wsa-admin:01
debugClients=
wsaUrl=http://${psc.as.host.name}:${psc.as.http.port}/soap
wsdlEnabled=1

[appsch.ROOT.REST]
adapterEnabled=1

[appsch.ROOT.WEB]
adapterEnabled=0
defaultCookieDomain=
defaultCookiePath=
defaultHandler=OpenEdge.Web.DefaultWebHandler
srvrAppMode=production
srvrDebug=0
wsRoot=/static/webspeed

[AppServer.SessMgr.appsch]
agentLogEntryTypes=ASPlumbing,DB.Connects
agentLogFile=${catalina.base}/logs/appsch.agent.log

[AppServer.Agent.appsch]
PROPATH=${CATALINA_BASE}/webapps/ROOT/WEB-INF/openedge,${CATALINA_BASE}/openedge,${DLC}/tty,${DLC}/tty/netlib/OpenEdge.Net.pl
uuid=http://APPSERVER10:8817/appsch

Posted by OctavioOlguin on 03-Jun-2019 22:27

Thanks to my Progress vendor, (Marcela Mtz-SIT consultores) I found that the place where I'd define propath is:

[AppServer.Agent.appsch]    being (appsch) the instance name....

Posted by OctavioOlguin on 03-Jun-2019 22:30

Thanks to my Progress Vendor, (Marcela Martínez-SIT consultores) I found that the place where I'd update propath value is:

[AppServer.Agent.appsch.Propath]

Posted by Roy Ellis on 04-Jun-2019 10:45

I think your issue is your PROPATH and the way you are calling the program.

PROPATH=C:\home\appsch\webapps\ROOT\WEB-INF\openedge\tap (just the important part)

you are calling tap\GetProPath.p

So where we are looking is C:\home\appsch\webapps\ROOT\WEB-INF\openedge\tap\tap\GetProPath.p

Try adding C:\home\appsch\webapps\ROOT\WEB-INF\openedge (without the \tap at the end). Restart PASOE and run the request again.

LMK, Roy

Posted by OctavioOlguin on 04-Jun-2019 12:59

Thanks [mention:30c5058a319047d288fe606ee12c9bbe:e9ed411860ed4f2ba0265705b8793d05] , The issue you point out is correct.

The propath that ends in ....openedge/tap is pointing to the "Root" level of a system module. Beneath this point, there are hundreds of subdirectories, nested and so....  so a program file sitting on tap/procs/ven/ven01001.r,  when called shouldn't include the (TAP) level on the calling, (run tap/procs/ven/...) as indeed, avm would contruct .../openedge/TAP/TAP/procs/ven..

The problem in this case, was that docs point to update the [AppServer.Agen] section on the openedge.properties config file. But this value keeps a relation, (undocumented at first glance of docs) with [AppServer.Agent.<your_instance_name>] which you need to tailor to your need, not the one documented...

Thanks...

This thread is closed