Table Of Contents

Previous topic

Monitoring Configuration

Next topic



System Requirements

The agent is supported on the following systems:

  • Red Hat Enterprise Linux™ 3 on x86 and x86_64 [1] [2]
  • Red Hat Enterprise Linux™ 4 on x86 and x86_64 [1]
  • Red Hat Enterprise Linux™ 5 on x86 and x86_64 [1]
  • Debian 6.0 on x86 and x86_64 [1]
  • Ubuntu 10.04LTS on x86 and x86_64 [1]
  • SUSE Linux Enterprise Server™ 11 on x86 and x86_64
  • Solaris™ 9 on SPARC™ [2]
  • Solaris™ 10 on SPARC™, x86 and x86_64 [1]
  • AIX™ 5.3 (TL 07 and up) on Power™
  • Windows™(XP, Server 2003, Vista, 7, Server 2008) 32 and 64 bit


[1](1, 2, 3, 4, 5, 6) On x86_64 the agent still runs as a 32-bit application, the OS needs to have the adequate 32-bit compatible userland support installed.
[2](1, 2) These platforms have reached their end-of-life date as specified by their original vendors and are only supported on a best effort basis. It is possible that not all agent functionality will be available.

AIX Specifics

When using the Oracle monitor on AIX there are some extra requirements on the platform:

  • The system must support 64k pages and load the agent in this configuration. AIX only supports 64k pages from 5300-04 and upwards on a Power5+ CPU with a 64-bit kernel. The experienced sysadmin could try to run with 16M pages which is supported since AIX 5100-02 on Power4 CPUs.
  • The system must be configured not to load shared library text used by the agent in the global loader space. It must be loaded as private text instead.

Windows Specifics

Windows installation is generally very easy and performed using an MSI installer, however the user performing the installation must have full administration rights. In complex, heavily controlled and administered environments the following points should be noted:

  • The user performing the installation should have strong Windows administration skills, preferably someone with an understanding of the specific system administration mechanisms and policies on the customer site.
  • It is important that the user doing the install has full local and domain administration privileges, full control of the Program Files directory and rights to install and run a Windows service.
  • The user doing the install must ensure that if there is a Group Policy Object (GPO) implemented that would stop the Agent service from starting then it must be properly configured; it may be set up to only allow white listed applications.
  • If Active Directory is running, there could be an Active Directory Group Policy that might stop the Agent service from starting.
  • If the Windows Data Execution Prevention (DEP) feature is enabled it will stop all non-trusted services from running. The Agent service must be added to the DEP’s list, or the DEP should be turned off. Note this cannot be done via an installer provided; the implementer must change the DEP settings. Note that group policies can also affect the DEP settings.
  • For DB Monitoring on Windows, the Abilisoft Agent uses Windows ADO. ADO requires that a suitable data service (e.g. via OBDC) is installed and defined and the Agent manifest must be configured with the correct connection string depending on the data service defined.

Installing the Agent (UNIX)

The UNIX installation archive is named:


Make sure you have an archive that matches the platform you want to install to (although the installer will detect a mismatch an tell you).

Unpack the archive as follows:

$ tar -xof asagent_<VERSION>_<ARCH>.tar.gz

Navigate to the directory extracted and invoke the installer:

$ cd asagent_<VERSION>_<ARCH>
$ ./

Run with the --help argument to get details on all its command line options. The installer will automate the installation of MA onto a UNIX system into its default location of /opt/, unless --prefix is used.

Some recommended environment variables are printed after installation, however the --profile option can be used to automatically appended them to /etc/profile. If the profile was updated, by using --profile or manually, make sure it is effective by sourcing it or logging out and in again. Otherwise you could source the setup script in the current shell which will have the same effect:

. /opt/

When not exporting these environment variables in the current shell you can still invoke the installed applications by using the full pathname to their installed binaries.

After installation an init script will be available in:


This init.d script can be automatically installed to /etc/init.d/ and appropriate symbolic links created by using the --initd parameter. This will start the Agent in run-levels 3, 4 and 5 and stop it in all other run-levels.

Refer to the asagent section for details on running the agent.

Installing the Agent (Windows)

The Windows installer is delivered as an MSI package named:


The MSI can be executed by double-clicking the MSI installer icon, via a management service like SMS or running it from the command line as follows:

c:\> msiexec /i asagent_<VERSION>_x86-win32.msi


You can use the /quiet option for an unattended installation

There are many command line installation options, any of the agent’s runtime configuration settings can be defined during the installation procedure. Refer to MSI Command Line Options for details of MSI command line options.

Follow the installation prompts, using the defaults are recommended. The agent will be installed as a Windows service and in general a reboot will not be required.

Once installed you will need to run the agent; refer to the asagent section for details on running the agent.

Windows 64 bit

Note that for installations on 64 bit Windows platforms the default agent installation directory is C:\Program Files (x86)\

Un-installing or Upgrading (UNIX)


Make sure the agent is not running, i.e. execute the command:

$ asagent --stop

If the agent has been using monitoring and runtime configuration in the default location of $AS_HOME/etc then take a backup copy.


It is possible to configure your agent to get runtime and monitoring configuration from a source outside the installation directory. Refer to Using Configuration Outside the Installation Directory for details.

Simply delete the directory /opt/ using the command:

$ rm -rf /opt/


To upgrade asagent, perform the un-installation procedure followed by the installation procedure. Take care to back up any configurations before upgrading.

Un-installing or Upgrading (Windows)


Open the Windows Control Panel navigate to the ‘Add/Remove Programs’ screen. Right-click Abilisoft asagent and select Un-install. The asagent service will be stopped (if running) and the software un-installed.


To upgrade asagent, perform the un-installation procedure followed by the installation procedure. Take care to back up any configurations before upgrading.

Environment Variables

There are two key environment variables that are essential to the operation of the Agent:


This specifies the installed directory of the Agent, by default it is /opt/

On Windows it is not required to have this environment variable set since the registry key HKEY_LOCAL_MACHINE\SOFTWARE\abilisoft\mtm\as_home will be used if present. This key is automatically created during the windows installation by the MSI. The usual value for this variable on windows is C:\Program Files\\asagent.

Using the UNIX Shell

Most UNIX systems will have an sh compatible shell available. As a quick refresher there are several ways in which you can set environment variables using an interactive shell:

$ VAR=value

Will set the variable in the current shell only, which means any process started from the shell will not have this environment variable. To make the variable available to the children of the shell it must be exported:

$ VAR=value
$ export VAR

Lastly it is also possible to set an environment variable for just one child process created by the shell, e.g. using the echo command:

$ VAR=value echo The value is: $VAR

This manual may use any of these techniques in examples, but in each case any technique which sets a variable in the environment of the agent is appropriate.


This directory contains the Agent runtime configuration file asagent.conf. This is a standard INI file format; sections are used for various groups of settings. An example is shown below:

loglevel = DEBUG
manifest_uri =

This configuration mode can also be used on Windows if preferred, however configuration settings are stored in the Registry by default.


Agent log files are written here by default (although one can configure them to be written elsewhere). The current log file has a *.log extension, rolled log files have a *.log.1, *.log.2 etc extensions. The number of rolled logs can be configured.

Man Pages

UNIX man pages are available as well:

maql (1)               command line remote asagent client
asagent.conf (5)       asagent runtime configuration file
asagent (8)            Abilisoft Monitoring Agent