We use the fllowing approuch:
1. There is bgparam.cfg file which containts some rules about bg routine params and num-treads values:
BGcount 3
uBGcount 10
APWcount 5
2. At the begining we run 1 thread and every minute this thread checks config file and decides what to do:
run 1 more thread or...
It is the same as you return temp-tables or datasets in progress 4gl.
DEFINE temp-table xxx
field
index.
DEFINE OUTPUT PARAMETER table for xxx.
Progress actually uses write-xml statement when send answer through web service.
You have to edit servicename.wsdl file under webapps catalog on Linux.
Find endpoint tag at the end of file, and delete ipaddress or host name. Leave only relative path, not absolute.
you can deploy web servoce directlly on linux server through progress explorer. It is the same as deploying on local server. You do not need to do any changes in files generated by proxygen
we used something like:
RUN src/system/run_oscom.p ("sudo sh -c ""proshut ./db/account.db -C disconnect " + string (work-users1.id-proc) + """"). // for linux server part
_connect table can be used to identify user names already connected to db.
1. we had issues cause some fields had name "today", "now". It is reserved in ABL10. It can be identified by code compilation.
2. In 10.1B and later 64 bit architecture and there some difference in PUT LONG statement.
We used something like:
&IF PROVERSION = '10.1A' &THEN
&Scoped-define...
There are some different tags in different versions of proxy gen. You can try edit wsm file manually before you deploy it.
Easiest way to identify - export existing web service and check tags.
download SoapUI tool and connect to progress web service within it.
Check format for incoming queries and test web service.
I use web service with flex only, not php. Do not think there is a big diffrence.
FOR EACH _Connect NO-LOCK WHERE _Connect-Usr NE ?
AND
(_Connect-Type EQ "REMC" OR _Connect-Type EQ "SELF" or _Connect-Type EQ "0" )
BREAK BY _Connect-Usr:
IF _Connect-PID = ? THEN
NEXT.
IF _Connect-Type EQ "SELF" OR...
-admingroup parameter is list of users, not user's groups.
so you have to just change to
proadsv -start -admingroup root
if you start it under root user
smtpmail returns false if there is any error while sending e-mail.
We use tasks for most background processes. Every task has it's status, which determine what step to do next.
In this paradigm it is easy to repeat failed steps.
+ it gives admin chance to see what tasks still running and make...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.