What is the best practice for applying updates to a Production environment?
Siebel community,
As we prepare for our Siebel upgrade to 2019, I'd like to clarify best practices regarding applying monthly updates.
On Unix-based OSes, the latest updates not only automatically stop Apache and Siebel services, but can also be configured (via the AUTOSTART_SERVICES parameter) to start back up once the update is installed. Ostensibly, this approach greatly minimizes downtime and simplifies the update process, but it does raise some questions.
As a simple example, let's say we are going from 19.2 to 19.3, and our running target environment has:
Server 1: Gateway 1 , AI Server 1
Server 2: Gateway 2, AI Server 1, App Server 1
Server 3: Gateway 3, App Server 2