Overview of the rolling upgrade procedure
Learn about the steps of a rolling upgrade procedure.
You must perform the following actions to complete a rolling upgrade procedure. These steps are detailed in the following topics.
- Stop management operations while you apply the rolling upgrade procedure. No management operation, such as uploading a new application version or a new adapter, must be performed during a rolling upgrade.
- Duplicate the application server environment and install the fix pack IBM MobileFirst Platform Foundation v6.3.0.x in that duplicated environment, for example in a new cluster. You must use the existing administration database, MobileFirst runtime database, and MobileFirst reports database.
- Start a server in the duplicated environment.
- Direct some of the new HTTP sessions to the new servers and drain the servers of the previous installation so they do not receive new HTTP sessions.
MPF uses session affinity and locally stores data about the state of sessions in a server. When routing traffic to the new cluster, existing sessions must continue to be routed to the old server with which they started.
- When the old servers are all drained and there is no longer any active session, and the new MobileFirst Server is confirmed to work correctly, shut down the old servers. If required, uninstall the old IBM MobileFirst Platform Foundation version from those servers.
- When the old environment is shut down, we can authorize management operations again.
Parent topic: Rolling upgrade procedure to apply a fix pack to MPF v6.3.0