Upgrading a network deployment environment

Follow these detailed steps to upgrade existing profiles in a network deployment environment.

About this task

When you upgrade from IBM® Business Process Manager Version 8.0.1 in a network deployment environment, some additional steps must be completed. Complete the appropriate steps for your environment.

If minimum downtime is the objective during this upgrade, special precautions should be taken. These precautions are documented separately in the topic "Upgrading clusters with minimum downtime".
The deployment manager must be the highest level in the cell. Upgrade the installation that contains the deployment manager before upgrading the nodes.
In a cluster where Business Process Choreographer is configured, you cannot start cluster members at different version levels at the same time.
- You must stop all members at the older version before starting any of the upgraded members.
- After an upgraded member has been started, you must no longer start ‘old' members.
You must not upgrade more than one installation at a time.
The deployment manager should be up and running when managed nodes are upgraded. This step is necessary because the 8.0.1 installer must connect to the central configuration repository on the deployment manager to make the updates.
Note: The only exception to this rule is for managed nodes that are hosted by the same installation as their deployment manager profile. In this scenario, the managed node configuration is updated as part of the deployment manager profile.
When you apply the refresh pack in a network deployment environment, the connection to the deployment manager requires you to provide a user ID and password because WebSphere administrative security is enabled. The IBM Installation Manager does not prompt for these credentials when you start updating an installation that contains managed profiles. However, depending on your configuration, you might have to enter the credentials in a separate prompt near the end of the upgrade process.
Note: The credential panel displays twice during the upgrade process and has a default time out period of one minute. If you miss this prompt, your security configuration is set up such that a prompt is not displayed, or if you are running the silent installation script, follow the instructions in the "Identifying Profile Update Errors section" of the "Recovering from profile update errors" topic.

For more information on how to configure security for WebSphere administration scripts, which the IBM Business Process Manager scripts depend on, see Configuring security with scripting in the WebSphere® Application Server information center.