6.3 AgentUpdate

Use this Knowledge Script to remotely update a 6.0.2 or 6.5 AppManager UNIX agent to version 8.1.0.11, and to update a module on the 8.1.0.11agent computer. To use this Knowledge Script, the AppManager UNIX agent you want to update must run as root.

To update a version 7.5 AppManager UNIX agent to version 8.1.0.11, and to update modules on a version 8.1.0.11 NetIQ UNIX agent, use NetIQ UNIX Agent Manager. For more information, see the UNIX Agent Manager online help.

This Knowledge Script updates the AppManager UNIX agent and any modules on the computer separately. For example, if you have a managed client with the 6.5 version of the AppManager UNIX agent and AppManager for Apache management files, run this Knowledge Scirpt to update the AppManager UNIX agent to version 7.0.1. After you update the agent, configure this Knowledge Script to update the AppManager for Apache module on that computer.

To update the AppManager UNIX agent and preserve the agent’s existing configuration, you must set the INHERITCFG flag in the silent installation file to y. For more information, see AgentUpdate.

This Knowledge Script does not change the user account under which the AppManager UNIX agent runs. To change the AppManager UNIX agent’s account, you must manually run the installation script on the managed client computer.

This Knowledge Script is configured by default to raise an event when:

  • The agent update completes successfully. In this case, the following event message is displayed: “Agent successfully upgraded to version build_number.”

  • The update is in progress but was not completed within the expected 4-minute time period. In this case, the following event message is displayed: “Agent upgrade started. Run this job again to check the status of the upgrade and clean up temporary files.” To verify that the update completed successfully, re-run this Knowledge Script on the managed UNIX client computer.

6.3.1 User Account Requirements for this Script

To run this Knowledge Script, the AppManager UNIX agent you want to upgrade must run as root. If the AppManager UNIX agent runs as a non-root user, you must run the interactive installation script on the local computer to upgrade the AppManager UNIX agent.

6.3.2 Resource Objects

A 6.0.2 or 6.5 AppManager UNIX agent or a module on a 7.0.1 (or earlier) AppManager UNIX agent.

6.3.3 Default Schedule

By default, this script is only run once for each computer.

6.3.4 Setting Parameter Values

Set the following parameters as needed:

Description

How to Set It

Raise event if the update succeeds? (y/n)

Set to y to raise an event indicating the upgrade was successful. If the upgrade fails for any reason, an event is generated regardless of how you set this parameter. The default is y.

Type of installation package (d for directory, t for tar file)

Type d if the installation files are uncompressed and located in a distribution directory. For example, type d if the installation files are located on a mounted CD drive or have been copied to a specific directory. Type t if the installation files are packaged in a tar file. The default is d.

  • If set to “d” for directory, the path you specify for the following parameter needs to point to the fully qualified path of the expanded tarball.

  • If set to “t” for tarball packaging, the path you specify for the following parameter needs to point to the fully qualified file name of the tarball, for example, /home/appmanager/upgradefiles/UnixClient-aix.tar for an AIX upgrade, where “aix" is the operating system on the target computer.

NOTE:Using the tar file requires additional scratch space in the temporary directory you specify on the target computer.

Full path to directory with UNIX agent .tar files

Enter the full path to the AppManager UNIX agent installation .tar file or the extracted contents of the .tar file. Typically the installation package is located on an accessible distribution computer. If you are working with the extracted contents of more than one .tar file, to avoid overwriting installation files you should extract each .tar file into its own shared directory. If the type of installation package is:

  • a .tar file, specify the full path to the .tar file.

  • extracted contents of the .tar file, specify the directory where the netiq_agent_install script is located.

Temporary working directory on the target computer

Specify a directory on the target computer to use as a temporary work space for upgrading the AppManager UNIX agent.

Because the upgrade process creates a backup of your previous installation and verifies the success of the upgrade before removing any temporary files, the file system must have at least 200 MB of disk space available.

The default is /tmp.

Full path to silent configuration file

Enter the full directory path to the silent installation file you’d like to use for the update.

The default is /tmp/silent.ini.

Event severity when job aborts

Set the event severity level, from 1 to 40, to indicate the importance of the event when the job failed to update the agent. The default is 10.

Event severity when update fails

Set the event severity level, from 1 to 40, to indicate the importance of an event when the agent was not successfully updated. The default is 10.

Event severity when update succeeds

Set the event severity level, from 1 to 40, to indicate the importance of the event when the agent has been successfully updated. The default is 20.

Event severity for internal failure

Set the event severity level, from 1 to 40, to indicate the importance of an event if the maximum pool threshold is exceeded. The default is 5.