×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
These are the steps I am using to start my Sametime Proxy Server on my IBM
i:
STRQSH
cd
/QIBM/UserData/WebSphere/AppServer/v7/SametimeWAS/profiles/STPAppProfile/bin
./startNode
Wait for dollar sign.
./startServer STProxyServer
Wait for dollar sign.
Can I do the following?
CALL QCMD
MD '/Operations'
EDTF '/Operations/StartSametimeProxyServer.sh'
Add the following lines:
cd
/QIBM/UserData/WebSphere/AppServer/v7/SametimeWAS/profiles/STPAppProfile/bin
./startNode
./startServer STProxyServer
F3
And then modify the program listed in DSPSYSVAL QSTRUPPGM and add
STRQSH CMD('/Operations/StartSametimeProxyServer.sh')
at the end?
I'm trying it...
STRQSH CMD('/Operations/StartSametimeProxyServer.sh'
QSH0005-Command ended normally with exit status 0.
I can log in at the url. Guess that's ok.
Is there a concern that the startServer may start before the node is
ready? Looks like it may be possible:
cd
/qibm/userdata/websphere/appserver/v7/sametimewas/profiles/stpappprofile/bin
$
./startNode
CPC1221: Job 039923/QEJBSVR/NODEAGENT submitted to job queue QWASJOBQ in
library QWAS7.
./startServer STProxyServer
CWNATV01I: Application server nodeagent in profile STPAppProfile has
started.
$ CPC1221: Job 039938/QEJBSVR/STPROXYSER submitted to job queue QWASJOBQ
in library QWAS7.
CWNATV01I: Application server STProxyServer in profile STPAppProfile has
started.
$
Notice the $ in front of the second CPC1221? I think that indicates that
startNode finished after the startServer began processing. It seems to
work though.
Rob Berendt
midrange.com
