9.4 Managing Installation Packages

An installation package is an installation program that is run by the Deployment Service as part of a deployment task. You can perform the following tasks with Installation packages:

  • Install, reinstall, uninstall, or upgrade the AppManager agent.

  • Install, upgrade, or uninstall a module.

To install the AppManager agent, you should select the NetIQ AppManager Agent package and the AppManager for Application packages that correspond to the applications you want the agent to monitor. For example, to install the AppManager agent and Microsoft SQL Server module, you would need the deployment package for the NetIQ AppManager Windows Agent and the AppManager for SQL Server packages. Control Center creates a separate deployment task for each package.

NOTE: The deployment tasks for a module are not created until after you install the AppManager agent and it appears in the Software Inventory list.

You specify whether to install or uninstall agents and modules when you create or modify a deployment rule. Deployment rules can either install or uninstall agents and modules. The same rule cannot install some components and uninstall others.

The installation package consists of an XML file that you might need to check in to Control Center. By default, all packages available with the current release of AppManager are checked in when you install Control Center. If you download a module released later than the AppManager release, check in the XML file included in the download package. For more information, see Section 9.4.3, Checking in Installation Packages.

9.4.1 Viewing Installation Packages

In the Navigation pane, click Deployment and then click Packages to view a list of available packages.

To view the properties of a package, right-click the package you want and click Deployment Package Properties.

9.4.2 Checking for Updated Deployment Packages

Before deploying an installation package, you can check to be sure you have the latest version of the module in the deployment package. This is an easy way to be sure you are deploying only the most recent module software and it can help you avoid needing to upgrade modules later on.

To check for updated deployment packages:

  1. In the Navigation pane, select the Deployment view.

  2. Click Packages.

  3. On the Main tab of the ribbon, click Tasks > Packages View Tasks > Check for Deployment Package Updates. A browser window displays any available module updates for all deployment packages.

  4. Click the download icon to download and install the updated modules you want.

9.4.3 Checking in Installation Packages

If you download and want to deploy a module later than the version included with the AppManager installation kit, check in the module installation package. Before you can check in an installation package, ensure that you have configured the Control Center console with the name of the IIS Server where you have installed the Deployment Web Service.

The name of the Web Depot computer is configured at the time of installation. For more information about configuring the Deployment Web Service, see Section 3.2.3, Deployment Options.

To check in additional packages after installation:

  1. Log on to the Control Center console using an account that is a member of a user group with deployment permissions. For more information about permissions, see the Administrator Guide for AppManager, available on the AppManager Documentation page.

  2. In the Navigation pane, select the Deployment view.

  3. Click Packages.

  4. In the Tasks pane, click Check in Deployment Packages.

  5. Navigate to the folder where you have saved the XML file for the module and select the file.

  6. Click Open. The Deployment Package Check in Status window displays the status of the package check in.