While I was working on one of my Siebel requirements I realized that my script would become very accurate and less confusing to business if I could script based on Server Name. So I had to access the Server Name using eScript. I thought about this for sometime and after 10 minutes I suddenly realized that it is easy.
I went to Site Map –Server Configuration – Enterprises. The view you would see here is definitely based on some Business Object, Business Component and stored in some table. So went to About View and found that the Enterprise server name is coming from the Business Component “Enterprise Server” and the server name is stored in the field “Enterprise Server”. So all I did was to query this BC and access column. So easy after I realized.
Similarly, it is very easy to access other server parameters that change dynamically depending on the Environment.
Share with me your experience configuring something unusual requirements like this and eventually you figured out. Lets have some fun.
Related posts(Auto Generated):
June 3rd, 2008 at 6:16 pm
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.
June 3rd, 2008 at 10:12 pm
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.
March 3rd, 2009 at 8:19 am
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.