Comments on: How to Access Server Parameters using eScript

By: Binu

Binu — Tue, 03 Mar 2009 08:19:23 +0000

We also had a similar requirement to distinguish between Test and Production environments while some workflows are getting executed.

We coded a custom BS similar to what you have done. During the testing of workflows using BS simulator, every thing went fine. But once the WF’s started executing based the WF policies, monitored by WF Monitoring Agent, the WF’s started failing at the Custom BS step to get the Enterprise Server name and sometimes recovered after few attempts. But in production, this failed all the WF’s monitored by our WF monitoring agent.

Finally we had to change this approach.

By: Sridhar

Sridhar — Tue, 03 Jun 2008 22:12:19 +0000

Mike,
Did you release the memory at the end of the script by nullifying the object variables? I will be surprised if the server still crashed after doing this. Check Tip 11 under this link.

http://siebelguide.com/siebelblogs/2008/05/31/escript-best-practices-part6/

Let me know. Thanks.

By: Mike M. Lin

Mike M. Lin — Tue, 03 Jun 2008 18:16:33 +0000

Be very careful with this one. We are on Siebel 7.7.2.6 and tried querying the Enterprise Server buscomp to get some info during login. Functionally it worked, but there were some serious memory leaks that brought down our development environment just a few hours after each restart.