Skip Headers
Oracle® Business Transaction Management Installation Guide

Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

8 Installing Observers Overview

This chapter describes the procedure for installing Business Transaction Management observers. Installation of observer libraries are covered in separate chapters and are cross referenced from this chapter.

Prerequisite and Preliminary Setup Checklist

General Steps for Installing Observers

  1. Ensure that the assertion secret and encryption key for your observer are set to the same values that are used by the other components of your Business Transaction Management system.

    The components of your Business Transaction Management system use an assertion secret and an encryption key in order to secure communications between themselves. If you have configured your Business Transaction Management server components to use nondefault values for these settings, you must, likewise, configure each JVM or .NET execution environment that hosts observers to use identical values for these settings. For an in-depth explanation of these security settings and how to configure them, see Configuring the Assertion Secret and Encryption Key.

  2. Optional – Configure SSL security on execution platforms that will host observers for the observer-to-monitor transport of observation messages. If you have configured SSL security for any of your monitors, then you must also configure it for the associated observers.

    See Setting up a Secure Socket (SSL) for Observation Messages.

  3. Ensure that an Observer Communication policy is set up.

    See Applying an Observer Communication Policy.

  4. Install the observer libraries and configure them into your application server.

    The procedure for performing this task is specific to the application server and observer type. See the following chapters for detailed instructions:


    This installation guide provides instructions for installing observers that are included as part of release If you want to install an observer from an earlier release, consult the installation guide from that earlier release. In particular, if you want to install the observer for WebLogic 9.2, Oracle Service Bus 10gR3, WebSphere, JBoss, or ASP.NET, consult the installation guide for release All release 12.1.x observers are compatible with the current release.

    For detailed information about a specific observer's compatibility and functionality, refer to the README.txt file located in the observer's nanoagent directory after you expand the observer ZIP file.

  5. Set the AP_NANO_CONFIG_URL Java system property or AmberPoint:NanoConfigUrl Windows key on the application server.

    This property/key associates the observer with the monitor whose URL you specify in the property/key. At startup, the observer retrieves its configuration from the specified monitor and begins sending observations to the monitor. Following is an example of the URL. Edit only the host name and port number:


    Setting this property/key is also explained in the application server-specific instructions for installing the observer libraries.


    If you are using replicated monitors, you must set the host and port portion of the URL to the host and port of your load balancer's HTTP virtual server. For example, if the HTTP virtual server's IP address is, and its port number is 5072, then you would set the URL to:

    For more information about the load balancer's HTTP virtual server, see Configuring Your Load Balancer.

  6. Restart your application server.

Overriding the Default Location of Observer Libraries

This section applies only to Enterprise Gateway and Java application servers (WCF and ASP .NET observer libraries are installed in the GAC).

By default, the observer library is located at AP_NANO_HOME/lib. If you want to place the observer library in a different location, create a Java system property in your server named AP_NANO_CLASSLOADER_BASEDIR and set its value to the location of the library.

The observer uses the following order of precedence to locate its library (from highest to lowest):

  1. the value of the system property AP_NANO_CLASSLOADER_BASEDIR

  2. the value of the deprecated system property apclassloader.basedir

  3. AP_NANO_HOME/lib