To use AppManager for UNIX, you must:
Install the UNIX agent on all the computers you want to manage. Install the agent to a folder, not to the root directory.
If you install the agent to a computer that you will manage using AppManager for Oracle RDBMS on UNIX or Linux Servers, ensure that the account you use to install the agent has access to the Oracle Home directory.
Install the patch to the agent computers that provides the new monitoring features, install UNIX Agent 8.1.0.11 (this is a hotfix) or UNIX Agent 8.1.0.1 with patch 8.1.0.9 or UNIX Agent 8.0 with patch 8.0.0.12, or UNIX Agent 7.5 with patch 7.5.0.14.
Install the Knowledge Scripts by running the module installer .msi on all AppManager repositories that store data for this module.
Install the Help files by running the module installer .msi on all AppManager Control Center and Operator Console computers you will use with this module.
Remotely installing the AppManager for UNIX to your agent computers provides a convenient and uniform method for deploying one or more UNIX agents. You can use the Deployment wizard provided in the UNIX Agent Manager for remote deployment, unless one of the following conditions exist:
Your site standards prohibit your access to root passwords.
Your site standards require a specific software distribution mechanism.
Your site standards prohibit software distribution mechanisms.
You installed UNIX Agent Manager using the options to restrict all communication to FIPS certified encryption algorithms.
For information about installing UNIX Agent Manager, see Section 2.2, Installing and Upgrading UNIX Agent Manager.
To remotely deploy UNIX agent components:
In the File menu of UNIX Agent Manager, click Remote Deployment.
Click the Add Host button and fill in the fields as prompted.
When you are given the option of setting the security level, NetIQ Corporation recommends that you choose Security Level 1 or 2. For more information about security level options, see Section 3.2, Understanding Communication Security Levels.
When you are given the option of communication security settings, do not restrict communication to only Federal Information Processing Standard (FIPS) encrypted algorithms unless you are certain that your environment requires that restriction. If you select that option, UNIX Agent Manager cannot communicate with agents that do not have the same restriction. For more information about FIPS and the other security level options, see Section 3.2, Understanding Communication Security Levels.
When you are given the option to specify the restart method, NetIQ Corporation recommends that you accept the default, rclink. For more information about restart methods, see Section 3.3.4, Restart Methods.
When you are given the option of including additional startup options, you can select from the list of options described in the section Section 3.3.3, Script Options.
Proceed through the wizard to complete the agent installation.
UNIX Agent Manager provides a utility to upgrade existing agents. You cannot use this feature if your UNIX Agent Manager restricts communication to FIPS certified encryption algorithms.
To upgrade UNIX agents using UNIX Agent Manager
Ensure the computer that you want to upgrade is registered in UNIX Agent Manager. You can do this by either importing an existing list that contains the computer using Manage Hosts > Import/Export Host Lists, or by adding the computer using Manage Hosts > Add Host.
Highlight the computer you want to upgrade, and select Manage Hosts > Upgrade Hosts. The left pane displays any options you need to select for your agent.
Scroll to the bottom of the panel and click the Start Upgrade button.
The following procedure guides you through logging on to an agent computer and locally installing all required components on the agent computer.
To install an agent on the local computer:
Log on to an agent computer using an account with super user privileges.
Change directories to product installation package, and then enter the following command to start the install script:
/bin/sh ./install.sh
Proceed through the prompts.
When you are given the option to specify the restart method, NetIQ Corporation recommends that you accept the default, rclink. For more information about restart methods, see Section 3.3.4, Restart Methods.
When you are given the option to configure the agent for use with other products, only select the option if you run NetIQ Secure Configuration Manager, NetIQ Change Guardian, or NetIQ Security Manager to monitor the computer. If you do not use those products, type n instead of accepting the default response of y for those questions.
When you are given the option of setting the security level, NetIQ recommends that you choose Security Level 1 or 2. For more information about security level options, see Section 3.2, Understanding Communication Security Levels.
When you are given the option of including additional startup options, you can select from the list of options described in the section Section 3.3.3, Script Options.
When you finish the installation process, AppManager starts the daemons.
Performing a silent installation allows you to install the UNIX agent without interactively running the installation script. Silent installation uses an installation file that records the information required for completing the installation. Each line in the file is a name=value pair that provides the required information, for example, HOME=/usr/netiq.
If you use the deployment wizard to perform a local installation on one computer, the wizard lets you create a silent installation file based on your choices. A sample installation file, SampleSilentInstallation.cfg, is located on your UNIX agent download package.
The following parameters are available for silent installation for the NetIQ UNIX Agent working with AppManager:
|
Parameter |
Description |
|---|---|
|
CREATE_TARGET_DIR |
Specifies whether you want the install program to create the target installation directory if it does not already exist. Valid entries are y and n. The default is y. |
|
CONTINUE_WITHOUT_PATCHES |
Specifies whether the install program stops or continues when the operating system is not a supported version. Valid entries are y and n. |
|
IQCONNECT_PORT |
Specifies the port that the UNIX agent uses to listen for communications from UNIX Agent Manager. The default is 2620. |
|
IQ_STARTUP |
Specifies restart method for the uagent process. This process is used by the UNIX agent for the AppManager, Security Manager, and Secure Configuration Manager products. For information about the options, see Section 3.3, Starting and Stopping the UNIX Agent. Valid entries are rclink and inittab. The default is rclink. |
|
USE_FIPS_COMMON |
Specifies whether the UNIX agent communicates with UNIX Agent Manager using only FIPS certified encryption algorithms. Only use this option if your environment requires this restriction. Valid entries are 0, meaning that communication is not restricted, and 1, meaning that communication is restricted. |
|
INSTALL_AM |
Specifies whether the UNIX agent works with AppManager. Valid entries are y and n. |
|
OWNER |
Username that runs the UNIX agent. The default is root. |
|
GROUP |
User group of the account that runs the UNIX agent. The default is the primary group of the user to which OWNER is set. |
|
AM_LANG |
Specifies the locale in which the UNIX agent runs. The default is the locale of the user who executes the installation script. This parameter is available for UNIX agent 8.0 and above. |
|
AM_ORACLE_ENABLED |
Specifies whether the UNIX agent works with AppManager for Oracle. Valid entries are y and n. |
|
AM_STARTUP |
The restart method for the nqmagt and agent processes. These processes are specific to AppManager. Valid options are rclink and inittab. For information about the options, see Section 3.3.4, Restart Methods. |
|
ADDITIONAL_STARTUP_OPTIONS |
Any additional startup parameters you want the agent to use when it is restarted. For a list of options, see Section 3.3.3, Script Options. |
|
INHERIT_AM |
For upgrade only. Specifies whether you want to use the previous AppManager-specific configuration information. If you set this parameter to y, you do not need to specify many of the other parameters, such as parameters related to the management server, because the values are inherited from your current configuration. If you set this parameter to n, any running jobs and their current configuration settings are not migrated, and the UNIX agent installation is treated as a new installation. All running jobs no longer run. You must configure and start new jobs. |
|
KEEP_OLD_AM_DIR |
For upgrade only. Specifies whether you want to keep the directory from the previous installation that contains AppManager-specific information. Valid entries are y and n. |
|
PREVIOUS_AM_HOME_MOVED |
For upgrade only. Specifies where you want to move the directory used by the previous installation to keep AppManager-specific information. |
|
INHERIT_AM_DIR |
For upgrade only. Specifies whether you want to use the previous directory that contained AppManager-specific information. If you set this parameter to y, you do not need to specify many of the other parameters, such as parameters related to the management server, because the values are inherited from your current configuration. If you set this parameter to n, any running jobs and their current configuration settings are not migrated, and the UNIX agent installation is treated as a new installation. All running jobs no longer run. You must configure and start new jobs. |
|
AM_MACHINENAME |
Name of the UNIX computer to be displayed in the Operator Console TreeView. The name should be the full hostname for the computer and must be a name or address the management server can resolve for discovery to succeed. |
|
SKIP_DISCOVERY |
Specifies whether you want to install and start the agent without running discovery. Valid entries are y and n. |
|
AM_PRIMARY_MS_ADDRESS |
Name or IP address of the primary management server. If you are upgrading and have set INHERIT_AM_DIR to y, you can leave this setting blank to use the address from the previous installation. For example: tc09k05. |
|
AM_PRIMARY_MS_PORT |
Port on which the AppManager primary management server listens for the UNIX agent. The suggested port is 9001. If you are upgrading and have set INHERIT_AM_DIR to y, you can leave this setting blank to use the address from the previous installation. |
|
AM_PRIMARY_MS_SEC |
Security level for the primary management server. If you are upgrading and have set INHERIT_AM_DIR to y, you can leave this setting blank to use the address from the previous installation. For example, 2. |
|
AM_PRIMARY_MS_KEY |
Location of the public encryption key file for the primary management server. If you are upgrading and have set INHERIT_AM_DIR to y, you can leave this setting blank to use the address from the previous installation. For example, /home/smba/keystore/key_1.key. |
|
AM_SECONDARY_MS_ADDRESS |
Name or IP address of the secondary management server. If you are upgrading and have set INHERIT_AM_DIR to y, you can leave this setting blank to use the address from the previous installation. For example, 10.26.7.184. |
|
AM_SECONDARY_MS_PORT |
Port on which the secondary management server listens for the UNIX agent. If you are upgrading and have set INHERIT_AM_DIR to y, you can leave this setting blank to use the address from the previous installation. The suggested port is 9001. |
|
AM_SECONDARY_MS_SEC |
Security level for the secondary management server. If you are upgrading and have set INHERIT_AM_DIR to y, you can leave this setting blank to use the address from the previous installation. For example, 1. |
|
AM_SECONDARY_MS_KEY |
Location of the public encryption key file for the secondary management server. If you are upgrading and have set INHERIT_AM_DIR to y, you can leave this setting blank to use the address from the previous installation. For example /home/smba/keystore/key_1.key. |
|
USE_FIPS_AM |
Specifies whether the UNIX agent communicates with UNIX Agent Manager using only FIPS certified encryption algorithms. Only use this option if your environment requires this restriction. Valid entries are 0, meaning that communication is not restricted, and 1, meaning that communication is restricted. |
|
KEEP_OLD_AGENT_DIR |
Specifies whether to keep the previous installation directory when you are upgrading from version 7.5 of the UNIX agent. Valid entries are y and n. |
|
OLD_INSTALL_DIR_MOVED |
Specifies the directory where you want the installation program to move the previous installation directory. |
After you have created the installation file, run the silent installation command. For example:
./install.sh Target_Directory -s SilentConfigurationFile.cfg
where Target_Directory is the directory you want to install to, and SilentConfigurationFile is the file name you used to specify the installation options. You can also use the default configuration file, SampleSilentInstallation.cfg.
The script then extracts information from the installation file and installs the agent based on the values you have specified.
NOTE:You must specify the installation filename as an absolute path. By default, SampleSilentInstallation.cfg is located in the UNIX agent install directory.
Access the AM70-UNIX-7.x.x.x.msi module installer from the AM70_UNIX_7.x self-extracting installation package on the AppManager Module Upgrades & Trials page.
You can install the Knowledge Scripts into local or remote AppManager repositories (QDBs). Install these components only once per QDB.
The module installer now installs Knowledge Scripts for each module directly into the QDB instead of installing the scripts in the \AppManager\qdb\kp folder as in previous releases of AppManager.
To install the module on the QDB and AppManager console computers:
On the QDB computer, double-click the module installer .msi file.
Select Install Knowledge Scripts to install the repository components, including the Knowledge Scripts, object types, and SQL stored procedures.
Specify the SQL Server name of the server hosting the QDB and the case-sensitive QDB name.
(Conditional) If you use Control Center 7.x, run the module installer for each QDB attached to Control Center.
(Conditional) If you use Control Center 8.x, run the module installer only for the primary QDB, and Control Center automatically replicates this module to secondary QDBs.
Run the module installer on all console computers to install the Help and console extensions.
(Optional) If you have not discovered UNIX and Linux computers, run the Discovery_UNIX Knowledge Script on all agent computers. For more information, see Section 2.5, Discovering UNIX and Linux Computers.
To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see Section 2.6, Upgrading Knowledge Script Jobs.