With LSF9, Lawson delivers pfserv.cfg to start pfserv in this order: pfserv.start.order rmi em bpm sch However PF documentation shows this order: startpfem startpfbpm startpfrmi startpfsch What I'm finding is that the documented order is correct, and that the delivered pfserv.cfg is incorrect. In particular, if EM is started after RMI, it brings RMI down in some cases. Has anyone experienced this?
John,
I have not run into this issue yet. So far the default startup order has worked for me. I've seen issues where the pfserv stop all or even stopping individually does not actually stop the servers and then the restart then fails. I use a combination of netstat and lsof to ensure that everything is actually down.
In addition, I've had issues where processflow starts with the enviroment which is before WAS. Given that the first step in most flows is to interact with Lawson in some fashion (Data/Drill/Transaction request) this causes the flow to fail. i typically change the value in service.cfg so that pflow doesn't startup automatically. Careful though... when you apply a patch from lawson it re-enables the processflow services..
thanks
Jason Beard
617-548-5568
jabeard3@gmail.com