2.5 Upgrading the ZENworks Orchestrator Agents and Clients

It is likely that you have installed ZENworks Orchestrator Agents and Orchestrator Clients on machines other than where the ZENworks Orchestrator Server components were installed. This section includes information that helps you to walk through the upgrade of those agents and clients.

NOTE:To perform a mass upgrade of ZENworks Orchestrator Agents we recommend that you use a reputable application software distribution method to upgrade to the newer versions that ship with PlateSpin Orchestrate 2.0. For example, you can use ZENworks Linux Management to distribute new agents and clients to Linux servers.

For more information, see Section 2.7, Running the Upgrade Configuration on an Enterprise Scale.

2.5.1 Checking the Current Version of the Orchestrator Agent

Before you upgrade the ZENworks Orchestrator Agent packages from an earlier version to the current PlateSpin Orchestrate version, you should check which packages of the older Orchestrator version need to be upgraded and which non-Novell packages are included in the product packages.

To do this, change to the directory where the current version of the Orchestrator .iso was extracted, then run the following command:

rpm -qa | grep 'novell-zen'

We recommend that you record the results of this command so that you can compare it with the results of a similar task following the upgrade (see

2.5.2 Backing Up the Orchestrator Agent Prior to Upgrading

As with the installation of any software, it is always a wise precaution to back up a working copy of ZENworks Orchestrator 1.3 Agent directories before you install the newer version, such as PlateSpin Orchestrate 2.0. To back up the old version, copy the /var/opt/novell/zenworks/zos/agent directory.

2.5.3 Automatically Upgrading the Orchestrate Agent from the Orchestrate Development Client

The PlateSpin Orchestrate Development Client includes a feature that lets you automatically upgrade older Orchestrate Agents on resources (virtual or physical) that connect to the Orchestrate Server.

If your grid includes older (that is, older than version 2.0.2) Resource objects, their Orchestrate Agents cannot connect to a recently upgraded Orchestrate Server. This is shown when the Resource Registration icon in the Resource Monitor of the Orchestrate Development Client displays a “flag up” status.

When you click the Resource Registration icon, the Resource Registration Monitor dialog box displays all of the older resource objects attempting to connect.The Upgrade option is also available in the dialog box. You can select this option, along with all of the older agents that you want to upgrade.

When you use this automatic upgrade method, only the agent rpm (that is, the zw_zos_agent pattern) is upgraded, but other Orchestrate components that might be present on the resource machine are not upgraded. These include the following components (listed by pattern names):

  • zw_zos_clients

  • zw_mon_agent

  • zw_vm_builder

To separately upgrade these components, you need to use the YaST upgrade from the product ISO (see Upgrading ZENworks Orchestrator Agent Packages Using YaST) or the rug upgrade method (for each component) from the bash prompt (Upgrading ZENworks Orchestrator Agent Packages Using the rug Command).

2.5.4 Using the Product ISO to Upgrade Agents and Clients on a SLES 10 SP1 Machine

This section includes information about upgrading the agent and client packages on the product ISO.

Upgrading ZENworks Orchestrator Agent Packages Using YaST

Use the following procedure if you want to use YaST, a graphical user interface, to upgrade the ZENworks Orchestrator packages to PlateSpin Orchestrate packages. If you want to use the command line to upgrade, see Upgrading ZENworks Orchestrator Agent Packages Using the rug Command.

  1. Download the appropriate PlateSpin Orchestrate 2.0.2 ISO (32-bit or 64-bit for SLES 10 or SLES 11), then prepare it for installation:

  2. Upgrade ZENworks Orchestrator Agent software packages:

    1. Log in to the target SLES server as root, then open YaST2.

    2. In YaST2, open the Filter drop-down menu, then select Installation Sources to display the install patterns available on the PlateSpin Orchestrate installation media.

      Component packages already installed to the server are checked.

    3. Right-click on any of the installed package names, click All in This List > Update if newer version available.

    4. Click Accept to install the upgraded packages.

      After the server RPMs are upgraded, the program runs a script that does the following:

      • Stops job activity on the existing agent

      • Backs up the existing agent data to a retrievable format

      • Upgrades the RPMs for the selected PlateSpin Orchestrate patterns

      WARNING:The preceding steps have been tested and validated in YaST. Using other methods to update packages in YaST have not proven successful.

    5. Run the configuration program on the machine where the agents or clients are installed. You have two options for running the script:

Upgrading ZENworks Orchestrator Agent Packages Using the rug Command

Use the following procedure if you want to use YaST, a graphical user interface, to upgrade the ZENworks Orchestrator packages. If you want to use the GUI Configuration Wizard to upgrade, see Upgrading ZENworks Orchestrator Agent Packages Using YaST.

  1. Download the appropriate PlateSpin Orchestrate 2.0 ISO (32-bit or 64-bit), then prepare it for installation:

    • (Optional) Burn a DVD of the ISO image, mount the DVD, then extract the contents of the .iso folder to the local file system of the server.

    • (Optional) Extract the contents of the .iso folder to the local file system of the server.

  2. At the command line, change to the directory where the Orchestrator .iso folder was extracted, then run the commands to upgrade ZENworks Orchestrator:

    1. Run the following command:

      rug sa -t zypp "http://<ip_address_of_local_server>/<directory_location_of_iso_files>"

      NOTE:If you have chosen not to extract the files and you want to use the .iso image to upgrade, use the following command in this step:

      rug sa -t zypp "iso:///?iso=$ISO_FILE_NAME&url=dir:///$PATH_TO_ISO/"

      For example, for the ISO located at /root/Desktop/PlateSpin_Orchestrate-2.0.2.x86_64.iso, you could use this command:

      rug sa -t zypp "iso:///?iso=PlateSpin_Orchestrate-2.0.2.x86_64.iso&url=dir:///root/Desktop/"

      NOTE:If you are using an ftp server, extract the contents of the .iso to a folder, use the following command:

      "ftp://<ip_address_of_local _server>/<directory_location_of_iso_files>"

    2. Run the following command:

      rug sub platespin

    3. Run the following command:

      rug up -y

  3. Configure the PlateSpin Orchestrate Agent. You can use one of two information gathering methods to perform the configuration:

Checking the Upgraded Orchestrate Agent

After you upgrade the ZENworks Orchestrator 1.3 packages to PlateSpin Orchestrate 2.0.2, you should check the upgraded software packages to confirm that all of the earlier versions of the product components are now updated and which of the non-Novell packages have been updated.

To do this, change to the directory where the PlateSpin Orchestrate 2.0.2 .iso was extracted, then run the following command:

rpm -qa | grep 'novell-zen'

Compare the results of this command with the results you had with the check you performed before the upgrade (see Section 2.5.1, Checking the Current Version of the Orchestrator Agent). If some of the components have not been upgraded from the earlier version, the incompatibility between the components could cause unexpected behavior.

Configuring the Upgraded Agent Packages

You can use one of two information gathering methods to configure upgraded PlateSpin Orchestrate packages:

Running the Product Configuration Script to Upgrade Agents

If you decided to use the product configuration script to upgrade ZENworks Orchestrator Agents and Clients referred to Step 2.e,

  1. Make sure you are logged in as root to run the configuration script.

  2. Run the script, as follows:

    /opt/novell/zenworks/orch/bin/config

    When the script runs, the following information is initially displayed:

    Welcome to PlateSpin Orchestrate.

This program will configure PlateSpin Orchestrate 2.0

Select whether this is a new install or an upgrade

i) install
u) upgrade
- - - - - -

Selection [install]:

  3. Enter u to select the option to upgrade to PlateSpin Orchestrate.

    The following information is displayed:

    Select products to upgrade

 #   selected  Item
 1)     no     PlateSpin Orchestrate Monitoring Service (not installed)
 2)     no     PlateSpin Orchestrate Server (not installed)
 3)    yes     PlateSpin Orchestrate Agent
 4)     no     PlateSpin Orchestrate VM Builder (not installed)

Select from the following:
  1 - 4)  toggle selection status
       a)  all
       n)  none
       f)  finished making selections
       q)  quit -- exit the program
Selection [finish]:

  4. Toggle the items in the list that you want to upgrade to yes.

  5. Enter f to finish the selection and begin the configuration.

  6. Enter y or n to view or bypass a summary information screen of the configuration you have completed. If you chose to view the summary, you can proceed with the upgrade (by entering yes) or abort the upgrade (by entering no).

Running the GUI Configuration Wizard to Upgrade Agents

If you decided to upgrade ZENworks Orchestrator Agents and Clients to PlateSpin Orchestrate Agents using the GUI Configuration Wizard referred to in Step 2.e,

  1. Run the script for the PlateSpin Orchestrate Configuration Wizard as follows:

    /opt/novell/zenworks/orch/bin/guiconfig

    The GUI Configuration Wizard launches.

    IMPORTANT:If you only have a keyboard to navigate through the pages of the GUI Configuration Wizard, use the Tab key to shift the focus to a control you want to use (for example, a Next button), then press the spacebar to activate that control.

  2. Click Next to display the license agreement.

  3. Accept the agreement, then click Next to display the PlateSpin Orchestrate Configuration Selection page.

  4. Select Upgrade, then click Next to display the PlateSpin Orchestrate components page.

    This page lists the components that are available for configuration (already installed). By default, all previously installed components are selected for configuration.

  5. Select all the agent components you want to upgrade, then click Next to display the Configuration Summary page of the configuration wizard.

  6. Commit the configuration.

    1. (Optional) Click Next to apply the configuration settings.

    2. Deselect the Configure now check box so that the wizard can write the configuration file to /etc/opt/novell/novell_zenworks_orch_install.conf without starting Orchestrator or applying the configuration settings.

      NOTE:You can use this .conf file to start the Orchestrator Agent and apply the settings either manually or with an installation script. Use the following command to run the configuration:

      /opt/novell/zenworks/orch/bin/config -rs

  7. Click Next to display a message asking whether you want to overwrite the .conf response file.

  8. To upgrade, you need to overwrite the existing file. When prompted, click Yes to overwrite the file and display the configuration page.

  9. Click Finish to dismiss the configuration wizard.

  10. Click Next to begin the upgrade configuration for the ZENworks Orchestrator Service to the PlateSpin Orchestrate Service.

    When the configuration is complete, the Finish page of the configuration wizard is displayed.

2.5.5 Using the ISO to Upgrade the Orchestrator Agent and Clients on Red Hat Enterprise Linux 4 Machines

Use the following procedure if you want to use the Add-on method to install just the Orchestrate Agent and the PlateSpin Orchestrate Monitoring Agent to a Red Hat Enterprise Linux (RHEL) 4 machine.

  1. Shut down the Orchestrator Console on the machine where you intend to install the new PlateSpin Orchestrate Development Client.

  2. Download the appropriate PlateSpin Orchestrate Server ISO (32-bit or 64-bit) to an accessible network location.

  3. Mount the PlateSpin Orchestrate ISO as a loopback device as in the following example:

    mount -o loop PlateSpin_Orchestrate-2.0.2.x86_64.iso /mnt

    This mounts the ISO in the /mnt folder.

  4. Navigate to the directory path where the RHEL 4 packages reside. For example:

    cd /mnt/RHEL4

    There are five packages in the /RHEL4 directory (the list below is for a 64-bit ISO):

    • novell-zenworks-monitor-gmond-3.0.4-50.x86_64.rpm
    • novell-zenworks-orch-config-2.0.2-141.noarch.rpm
    • novell-zenworks-orch-config-gui-2.0.2-57039.noarch.rpm
    • novell-zenworks-zos-agent-2.0.2-57039.i586.rpm
    • novell-zenworks-zos-java-1.5.0_sun_update17-0.x86_64.rpm

  5. Use the rpm command to install the packages:

    rpm -Uvh *.rpm

    If you encounter an issue regarding missing dependencies, you can use the up2date command to download and install those. For example, if you were missing libcaplso or libcap.so.1, you would run the following:

    up2date --solvedeps=libcp.so,libcap.so.1

  6. (Optional) Increase the heap size that the JVM handles to enable the Orchestrate Development Client to manage a large number of objects.

    1. Open the zoc bash shell script at /opt/novell/zenworks/zos/server/bin.

    2. Inside the script, find the following line where the JVM parameters are defined:

      JVMARGS="-Xmx256m -Xms256m -Xmn64m -XX:NewSize=64m -XX:MaxNewSize=64m"

      The -Xmx argument specifies the maximum heap size for the JVM*. Increasing the heap size prevents a JVM out of memory condition.

    3. Change the value in the -Xmx argument from 256 MB to 512 MB.

    4. Save the script.

NOTE:Upgraded agent and client software does not require you to execute the configuration script on RHEL 5 machines.

2.5.6 Using the ISO to Upgrade the Orchestrator Agent on Red Hat Enterprise Linux 5 Machines

Use the following procedure if you want to use the Add-on method to upgrade the Orchestrator Console to a PlateSpin Orchestrate Development Client running on a Red Hat Enterprise Linux (RHEL) 5 machine.

  1. Shut down the Orchestrator Console on the machine where you intend to install the new Orchestrate Development Client.

  2. Download the appropriate PlateSpin Orchestrate ISO (32-bit or 64-bit) to an accessible network location.

  3. Mount the PlateSpin Orchestrate ISO as a loopback device as in the following example:

    mount -o loop PlateSpin_Orchestrate-2.0.2.x86_64.iso /mnt

    This mounts the ISO in the /mnt folder.

  4. Navigate to the directory path where the RHEL 5 packages reside. For example:

    cd /mnt/RHEL5

    There are five packages in the /RHEL5 directory:

    • novell-zenworks-monitor-gmond-3.0.4-50.x86_64.rpm
    • novell-zenworks-orch-config-2.0.2-141.noarch.rpm
    • novell-zenworks-orch-config-gui-2.0.2-57039.noarch.rpm
    • novell-zenworks-zos-agent-2.0.2-57039.i586.rpm
    • novell-zenworks-zos-java-1.5.0_sun_update17-0.x86_64.rpm

  5. Use the rpm command to install the packages:

    rpm -Uvh *.rpm

    If you encounter an issue regarding missing dependencies, you can use the up2date command to download and install those. For example, if you were missing libcaplso or libcap.so.1, you would run the following:

    up2date --solvedeps=libcp.so,libcap.so.1

  6. (Optional) Increase the heap size that the JVM handles to enable the console to manage a large number of objects.

    1. Open the zoc bash shell script at /opt/novell/zenworks/zos/server/bin.

    2. Inside the script, find the following line where the JVM parameters are defined:

      JVMARGS="-Xmx256m -Xms256m -Xmn64m -XX:NewSize=64m -XX:MaxNewSize=64m"

      The -Xmx argument specifies the maximum heap size for the JVM. Increasing the heap size prevents a JVM out of memory condition.

    3. Change the value in the -Xmx argument from 256MB to 512MB.

    4. Save the script.

NOTE:Upgraded agent and client software does not require you to execute the configuration script on RHEL 5 machines.

2.5.7 Using the ISO to Upgrade the Orchestrator Agent or the Orchestrator Clients on Windows Machines

The PlateSpin Orchestrate Agent and the PlateSpin Orchestrate Development Client are supported on Windows* 2003 and Windows XP. To upgrade, we recommend that you use the methods native to the OS to uninstall an older agent or client from the machine, then install the new 2.0 release of the Orchestrate Agent or the Orchestrate Development Client.

Use the following steps to download the PlateSpin Orchestrate component you want to install:

  1. Download the appropriate PlateSpin Orchestrate 2.0.2 ISO (32-bit or 64-bit) to an accessible network location.

  2. Create a DVD from the ISO or use a tool that will mount the ISO.

  3. Navigate to the directory path where the Windows packages (Windows 2003 or Windows XP) reside.

  4. Double-click the appropriate file (.exe) to launch an installation and configuration wizard for the console.

2.5.8 Using the Administrator Information Page to Upgrade the Agents and Clients

The Administrator Information Page page includes installers for the PlateSpin Orchestrate 2.0 Agents and Clients for Windows and various Linux/UNIX machines (see Installing the Orchestrate Agent from the Administrator Information Page in the PlateSpin Orchestrate 2.0 Installation and Configuration Guide). The page has no facility for upgrading an agent or client.

To upgrade, we recommend that you use the methods native to the OS to uninstall an older agent or client from the machine, then install the new 2.0 release of the Orchestrate Agent or Orchestrate Development Client.