Before you begin the PlateSpin Orchestrate upgrade process, you need to know the underlying assumptions of the process so that you can better understand how to proceed. The following list details the most important of those assumptions:
To check the installed PlateSpin Orchestrate components for version number, run the following command on a Linux machine where agent, client, or server components are installed.
rpm -qa | grep 'novell-zen'
To check version numbers on a Windows machine, open the
console in Windows and look for the agent or client version number in the programs list.The upgrade to PlateSpin Orchestrate 2.6 must be done for all Orchestrate Servers, Orchestrate Development Cliens, and all Orchestrate Agent components. Running older agents with newer server components or running older Development Clients and interfaces with newer server components (or vice versa) is not supported.
Upgrading a prior release of a 32-bit PlateSpin Orchestrate installation to a newer 64-bit version of PlateSpin Orchestrate is not supported. Similarly, upgrading a prior release of a 64-bit PlateSpin Orchestrate installation to a newer 32-bit version of PlateSpin Orchestrate is not supported.
The PlateSpin Orchestrate Server must be upgraded before Orchestrate Agents are upgraded. The Orchestrate Server operates with older agents running, but older agents cannot communicate with the PlateSpin Orchestrate 2.6 Server. You can upgrade the agents by selecting the Upgrade option on the Resource Registration dialog in the Orchestrate Development Client. For more information, see Walkthrough: Creating a Resource Account
in the PlateSpin Orchestrate 2.6 Installation and Configuration Guide.
NOTE:Upgrading an agent before upgrading the server causes the agent to terminate and to throw the following message:
11.05 06:23:39 : ERROR: Agent software version mismatch. 11.05 06:23:39 : ERROR: Current agent version: 2.6.0 11.05 06:23:39 : ERROR: Server expecting version: 2.5.0 CTRL-C Received. Shutdown node core: perf162 ZOS Agent Terminating: 11.05 06:23:39
After you upgrade the server components, older versions of the PlateSpin Orchestrate Agents, the Development Client, and the VM Client might not work with the newer server components. The Orchestrate Development Client identifies the managed nodes that have non-compatible agents. For more information about component compatibility, see Section 1.2, Compatibility Checking Behavior.
The PlateSpin Orchestrate 2.5 VM Client is not upgraded; it is replaced entirely by the PlateSpin Orchestrate 2.6 VM Client. Any previous version should be uninstalled before installing version 2.6.
Errors can occur during the upgrade process. These errors can be resolved and the upgrade process can be re-run. For more information about how the recovery works, see Section 2.3, Recovering from a Failed PlateSpin Orchestrate Server Upgrade.
After the PlateSpin Orchestrate Server is upgraded and started, rolling back to PlateSpin Orchestrate 2.5 is not supported.
Step-by-step information about the events occurring during the upgrade process is recorded in server.log, located in the /var/opt/novell/zenworks/zos/server/logs directory.
In some situations, the server log might not exist. You can also check the install log at /var/opt/novell/novell_zenworks_orch_install.log for upgrade information.