The application I work with uses a tier configuration of ECP application servers over a Cache mirrored database pair. The reboot of this tier is handled automatically by Cache classes that break down the reboot into three phases. Special Linux accounts are called from the classes via secure shell to handle reboot commands and Cache. The primary database mirror member handles phase one, basically shutdown process on application servers and then passes control to the backup member to do phase two. During phase two, the backup member reboots the primary and returns control back to the original primary for phase three. During phase three the backup member is rebooted, once completed all application servers are rebooted. What used to take 45 minutes manually is now done in 16 minutes by Cache
Markus,
The application I work with uses a tier configuration of ECP application servers over a Cache mirrored database pair. The reboot of this tier is handled automatically by Cache classes that break down the reboot into three phases. Special Linux accounts are called from the classes via secure shell to handle reboot commands and Cache. The primary database mirror member handles phase one, basically shutdown process on application servers and then passes control to the backup member to do phase two. During phase two, the backup member reboots the primary and returns control back to the original primary for phase three. During phase three the backup member is rebooted, once completed all application servers are rebooted. What used to take 45 minutes manually is now done in 16 minutes by Cache
Donnie