Forum Discussion
Monitoring Siebel components
Hello, colleagues!
Our F5 LTM balance siebel web-tier. This implementation was done in accordance to deployment guide (http://www.f5.com/pdf/deployment-guides/f5-siebel-dg.pdf). Now, our next step is implementing load balancing for Siebel App-tier.
In deployment guide recommended health monitor for node checking is HTTP GET (GET /siebel/SCbroker HTTP/1.1 \r\nHost: \r\nUser-Agent: \r\nConnection: keep-alive\r\n\r\n) and receive string SCBroker Okay.
In our siebel implementation we have six components and all six components are running on each pool member (eight app pool members):
EAIIVRObjMgr_enu
If some of components are failed on server, health monitor will not react on component failure.
Do you have any experience with monitoring siebel components?
Thank you for reply!
- Holly_W_37599Historic F5 AccountHi V.Sakalkin,
- Holly_W_37599Historic F5 AccountHi V.Sakalkin,
- v_sakalkin_9556Nimbostratus
Hello, Holly,
1). Monitor was configured manually2). Siebel 7.83). If one component is in failed state on app server, server will send string SCbroker okay. And Health monitor will show status UP.So we need to create this type of monitor, which can check status of each component.Standard load balancing method on siebel can monitor components. So now we balance only web-tier.Vladislav
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com