Skip Headers
Oracle® Business Transaction Management Installation Guide
12.1.0.3

E37016-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

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

11 Installing Observer Libraries on Oracle Enterprise Gateway

This chapter provides instructions for installing and uninstalling observer libraries into Oracle Enterprise Gateway 11.1.1.6.

The Observer Distribution File

The Business Transaction Management observers are distributed by way of ZIP files. Each ZIP file contains one type of observer that is suitable for installation into a particular application server. The ZIP file suitable for installing an observer into an Enterprise Gateway server is BTMObserver_OEG_11.1.1.6_OEG_*.zip.

Note:

In the actual ZIP file, the asterisk (*) is replaced with the observer version number.

Installing Observer Libraries on Enterprise Gateway 11.1.1.6

  1. Locate the observer distribution ZIP file that is appropriate for your version of Enterprise Gateway.

  2. Shut down your Enterprise Gateway server.

  3. Unpack the observer ZIP file into a temporary directory, referred to henceforth as observer_temp.

    Unpacking the ZIP file creates three directories named config, lib, and scripts.

  4. Copy all of the JAR files located in the lib to OEG_HOME/ext/lib, where OEG_HOME is your Enterprise Gateway server's home directory (the top-level installation directory).

    Note:

    By default, the observer looks in the lib directory for its libraries. For information on overriding this default location, see Overriding the Default Location of Observer Libraries.
  5. Ensure that the user account running Enterprise Gateway has at least the following privileges:

    • read permission on the nanoagent/config and nanoagent/lib directories (on UNIX-like systems traverse permission is also required)

    • read permission on all JAR files in the lib directory

  6. Open OEG_HOME/system/conf/jvm.xml in a text editor and make the following changes inside the <JVMSettings> element:

    1. Add the following line as the first child of the <JVMSettings> element:

      <SystemProperty name="AP_NANO_CONFIG_URL" value="http://host-name:port-number/btmmonitor/agent/agent/"/>
      

      Replace host-name:port-number with the host name and port number of the monitor you want to associate with your observer.

    2. Locate this line:

      <ClassPath name="$VDISTDIR/system/lib/system/iaik_jce.jar"/>
      

      and then add this line just before it:

      <ClassPath name="$VDISTDIR/ext/lib/orawsdl_1.0.0.jar"/>
      
  7. Restart your Enterprise Gateway server.

  8. Publish the interceptor module to finish the installation of the observer as follows:

    1. Open the observer_temp/scripts/publishLoadableModule.py script file in a text editor.

    2. Set the defUsername and defPassword variables using the credentials of an Enterprise Gateway administrator's account (the user name of the default administrator account is admin), for example:

      defUserName = "admin"
      defPassword = "mypassword"
      
    3. Set the defServer variable to the base URL of the Enterprise Gateway server, for example:

      defServer = "http://myOegHost:8090"
      

      Do not add a trailing slash (/) to this URL.

    4. Save and close the script file.

    5. Run the script, for example:

      On Windows systems, run:

      %OEG_HOME%/Win32/bin/jython.bat publishLoadableModule.py
      

      On UNIX-like systems, run:

      $OEG_HOME/posix/bin/jython publishLoadableModule.py
      
  9. Ensure that the user under which your Enterprise Gateway server is running has permission to write to the observer's error log directory.

    By default, the observer's error log directory is OEG_HOME. For information about configuring error logging, see Chapter 14, "Logging Observer Errors and Debugging Information."

  10. Ensure that the monitor to which your observer forwards messages has an Observer Communication policy applied to it.

    For information on applying an Observer Communication policy, see Applying an Observer Communication Policy.

Uninstalling Observer Libraries from Enterprise Gateway 11.1.1.6

This section describes how to uninstall observer libraries from an Enterprise Gateway 11.1.1.6 server.

  1. Remove the observer interceptor module from your Enterprise Gateway server as follows:

    1. Open the observer_temp/scripts/removeLoadableModule.py script file in a text editor.

      Note:

      If observer_temp no longer exists, refer to Installing Observer Libraries on Enterprise Gateway 11.1.1.6 for information about recreating it.
    2. Set the defUsername and defPassword variables using the credentials of an Enterprise Gateway administrator's account (the user name of the default administrator account is admin), for example:

      defUserName = "admin"
      defPassword = "mypassword"
      
    3. Set the defServer variable to the base URL of the Enterprise Gateway server, for example:

      defServer = "http://myOegHost:8090"
      

      Do not add a trailing slash (/) to this URL.

    4. Save and close the script file.

    5. Run the script, for example:

      On Windows systems, run:

      %OEG_HOME%/Win32/bin/jython.bat removeLoadableModule.py
      

      On UNIX-like systems, run:

      $OEG_HOME/posix/bin/jython removeLoadableModule.py
      
  2. Shut down your Enterprise Gateway server.

  3. Remove all of the observer-related JAR files located in OEG_HOME/ext/lib.

    All of the observer-related JAR names are prefixed with “ap-” except for the following:

    orahttp_client_1.0.0.jar
    orawsdl_1.0.0.jar
    xstream-1.2.2.jar 
    

    Note:

    Take care not to remove JAR files that are being shared with another module.
  4. Open OEG_HOME/system/conf/jvm.xml in a text editor and remove any and all observer-related elements from inside the <JVMSettings> element, including the following:

    <SystemProperty name="AP_NANO_CONFIG_URL" value="http://host-name:port-number/btmmonitor/agent/agent/"/>
    
    <ClassPath name="$VDISTDIR/ext/lib/orawsdl_1.0.0.jar"/>
    

    Also remove all <VMArg> elements whose name attribute begins with the following string:

    -Dcom.amberpoint
    
  5. Save and close the jvm.xml file.

  6. Restart your Enterprise Gateway server.