4.5 Managing Host Packages

4.5.1 Finding Packages on Hosts

You can search through all the hosts to find where a specific package is installed, or find whether the package is installed at all.

  1. On the home page of the console, click Hosts.

  2. In the navigation pane, click Hosts.

  3. In the task pane, click Find Package.

  4. From the Package drop-down list, select or enter the package you are looking for.

    For example: If you are searching for Audit Manager package, enter secaudit in the search field and then click Find.

  5. If you want to find out which hosts do not have this package installed, select the package not installed check box. If you want to find out where the package is installed, deselect the package not installed check box.

  6. Click Find. A list of hosts where the package is installed or not installed is displayed.

  7. Double-click the host name to view its details or click Close to return to the Hosts page.

4.5.2 Updating Packages for a Host

When updated packages are available on your local Package Manager, you can update the packages installed on individual hosts or for all hosts in a domain. The distribution agent performs a number of checks to ensure that the host has enough disk space to extract and install the package. If there is insufficient space, the package is not updated.

  1. On the home page of the console, click Hosts.

  2. In the navigation pane, select either the host or the domain where you want to update the packages.

  3. Click Update Domain Packages or Update Packages in the task pane.

    The console checks for updates on your Package Manager and displays any updated packages available for download.

  4. Select the packages from the list of available packages.

    To select multiple packages, press the Ctrl key and select the packages one at a time, or press the Shift key to select a consecutive list of packages. To select all packages, use Ctrl+A.

    NOTE:The Create Backup option which creates a backup of the currently installed packages is selected by default. Only the last backup is stored. Creating backups requires additional space.

    If necessary, you can use the Rollback Packages option to roll back to the previously backed-up packages.

  5. Click Next to start downloading the selected packages.

  6. Click Finish.

4.5.3 Rolling Back Packages

If you chose to create a backup when updating packages for an individual host or for a domain, you can roll back to the last backup.

Prerequisite

Before you rollback packages from 3.5 to any lower version, you must uninstall the Application SSO Manager (appsso) and Video Processing Module (videoprocessor) packages.

NOTE:When you rollback packages from 3.5 to any lower version, first rollback all the packages except distrib and framework (spf) and lastly rollback distrib and framework (spf) package.

  1. On the home page of the console, click Hosts.

  2. In the navigation pane, select the domain or the host where you want to roll back the packages.

  3. In the task pane, click Rollback Domain Packages or Rollback Packages.

  4. Select the packages from the list of available backed-up packages.

    To select multiple packages, press the Ctrl key and select the packages one at a time, or press the Shift key to select a consecutive list of packages. To select all packages, use Ctrl+A.

  5. Click Next to start rolling back to the previously backed-up packages.

  6. Click Finish.

4.5.4 Committing Packages

When packages are updated and the Create backup option is enabled, a backup of the current package is created and stored in a backup directory in the working package directory. This allows you to roll back to the previous level if the current package does not perform correctly in your environment. (See Rolling Back Packages.)

If the current package does perform correctly in your environment, you can commit the package, which frees up disk space by deleting the files in the backup directory. If your hosts have limited disk space, NetIQ recommends that you commit the packages on all hosts before performing the next update.

  1. On the home page of the console, click Hosts.

  2. In the navigation pane, select the domain or the host where you want to commit packages.

  3. Click Commit Domain Packages or Commit Packages in the task pane.

  4. Select the packages from the list of available packages.

    To select multiple packages, press the Ctrl key and select the packages one at a time, or press the Shift key to select a consecutive list of packages. To select all packages, click the Select all checkbox.

  5. Click Next to start the commit process.

  6. Click Finish.

4.5.5 Registering and Unregistering Packages for a Host

If you want to stop a package from functioning without removing it completely, you can unregister it. You can then register it again later if necessary. Packages are automatically registered when you add them, so you only need to register them if you have previously unregistered them.

Registered packages are shown with a green check mark: .

Unregistered packages are shown with a red exclamation mark: .

To register or unregister a package for a host:

  1. On the home page of the console, click Hosts.

    The navigation pane displays the current hierarchy for your Framework.

  2. In the navigation pane, select the domain where you want to register or unregister packages.

  3. Select the host.

  4. With the host’s packages displayed, select the packages you want to register or unregister.

    To select multiple packages, press the Ctrl key and select the packages one at a time, or press the Shift key to select a consecutive list of packages. To select all packages, use Ctrl+A.

  5. Click Register Package or Unregister Package in the task pane.

    WARNING:Ensure that you are not unregistering an audit manager package or any other package that might cause loss of audit data.

NOTE:The Framework Manager console does not refresh automatically. To check whether your packages have been successfully registered or unregistered, go to another screen and then return to the list of packages.

4.5.6 Installing Packages on a Host

Ensure that the packages have been downloaded to the Framework Package Manager by viewing packages available to deploy. See section Publishing Packages on the Package Manager.

The distribution agent performs a number of checks to ensure that the host has enough disk space to extract and install the package. If there is insufficient space, the package is not installed.

  1. On the home page of the console, click Hosts.

  2. In the navigation pane, click the arrow next to the domain where you want to install the packages.

  3. Select the required host.

  4. In the details pane, click Packages.

  5. In the task pane, click Install Packages.

  6. Select the packages from the list of available packages.

    To select multiple packages, press the Ctrl key and select the packages one at a time, or press the Shift key to select a consecutive list of packages. To select all packages, use Ctrl+A.

  7. Click Next to start installing the selected packages.

  8. Click Finish.

To use a command line option to install packages on hosts, see Package Manager Options.

4.5.7 Uninstalling Packages from a Host

You do not need to uninstall a package to disable it. You can disable it by unregistering the package. See Registering and Unregistering Packages for a Host.

To uninstall a package:

  1. On the home page of the console, click Hosts.

  2. In the navigation pane, click the arrow next to the domain where you want to uninstall packages.

  3. Select the required host.

  4. In the details pane, click Packages. and then select the packages from the list of installed packages.

    To select multiple packages, press the Ctrl key and select the packages one at a time, or press the Shift key to select a consecutive list of packages. To select all packages, click the Select All checkbox.

  5. Click Uninstall Packages in the task pane.

  6. Click Next to start uninstalling the selected packages.

  7. Click Finish.

WARNING:Ensure that you are not uninstalling an audit manager package or any other package that might cause loss of audit data.

To use a command line option to install packages on hosts, see Package Manager Options.

4.5.8 Modifying Audit Settings for the Audit Manager Package

The databases containing audited data from command control (cmndctrl.db) can be placed in an alternative location. The administration audit files (audit.db and audit.ldb) and log.msqs are still stored in the default location /opt/netiq/service/local/audit or C:\Program Files\Netiq\npum\service\local\audit, but these files are relatively small.

To define an alternative location for the audit databases:

  1. On the home page of the console, click Hosts.

  2. In the navigation pane, select the host with the Audit Manager installed.

  3. With the host’s packages displayed, select the Audit Manager (audit) package.

  4. Click Audit Settings in the task pane.

  5. In the Audit Path field, specify the location for the audit databases.

  6. Click Finish.

4.5.9 Configuring SMTP Settings for the Messaging Component Package

The SMTP Settings option allows you to provide details of your e-mail server so reports such as the Compliance Auditor reports and custom command control reports can be automatically e-mailed to the necessary personnel.

To configure the SMTP settings:

  1. On the home page of the console, click Hosts.

  2. Select the host where the Compliance Auditor and Messaging Component are installed.

  3. Click Packages to view details of the packages installed on this host.

  4. Select the Messaging Component (msgagnt).

  5. Click SMTP Settings in the task pane.

  6. Configure the following fields:

    SMTP Host: Specify the IP address of your e-mail server.

    SMTP Port: Specify the port of your e-mail server.

    SMTP Domain: If you are using a Lotus Notes server, specify the name of your SMTP domain.

  7. Click Finish.

4.5.10 Configuring Settings for the dbaudit Package

The Settings option is only displayed when you select the dbaudit package from the Packages page of any host. This is used to configure the credential checkout feature for Oracle and Microsoft SQL Server databases.

For Oracle database, you need to mention the path where Oracle client is installed. For Microsoft SQL Server database, you need to mention the path where the symbolic links are created.

For more information, refer to Configuring Credential Checkout for Oracle Database and Configuring Credential Checkout for Other Databases.