OTM 5.5 CU4 Startup and Scalability

[ianlo]

Hi everyone,

Now that the startup sequence has been changed for CU4 with Oracle recommending that the Web server be started first then followed by the App, how would this impact the startup sequence for servers under scalability configuration?

Previously, I will always start the primary tier first - app then web and then followed by the secondary tier.

I will always know when the primary web server has started because of the WaitForServer command and can then schedule the start of the secondary App server.

However, now that the sequence has changed, does anyone know what is the correct and recommended sequence of server startup under scalability config?

Thanks!
Ian

[chrisplough]

Re: OTM 5.5 CU4 Startup and Scalability

Ian,

I've been trying to understand the new startup order also - but haven't gotten a definitive answer.

Internally, we have not modified our startup order. The primary reason is that once the OTM web server comes up, integration servers will immediately attempt to post to OTM. If the OTM app server isn't up yet, then these posts will fail, causing other issues.

Hope this helps!

--Chris

[ianlo]

Re: OTM 5.5 CU4 Startup and Scalability

Hi Chris,

Ok thanks for this! I think I will do the same and will boot the app server first.

Thanks!
Ian