Skip Headers
Oracle® Enterprise Manager IBM Tivoli Netcool/OMNIbus Connector Installation and Configuration Guide
Release 12.1.0.3.0

E36154-06
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

2 Installing the Connector

The Oracle Enterprise Manager Connector Framework requires a web service interface for forwarding event information to IBM Tivoli Netcool/OMNIbus (Netcool/OMNIbus). Since Netcool/OMNIbus does not provide a web services interface, you must install a third-party web service for Netcool/OMNIbus front-end, which is included in the Oracle Enterprise Manager Netcool/OMNIbus installation package.

You can install the web service on a Windows or Unix system that has connectivity to the Netcool/OMNIbus server. In addition to the web service for Netcool/OMNIbus front-end, you must also install a back-end Oracle Agent for Netcool/OMNIbus on the same physical system as the Netcool/OMNIbus server. The Oracle Agent for Netcool/OMNIbus is preconfigured and is also included in the Oracle Enterprise Manager IBM Tivoli Netcool/OMNIbus installation package.

Figure 2-1 shows the communication between the various components of the Netcool/OMNIbus Connector.

Figure 2-1 Connector Communication Between Components

Connector Communication Between Components

The following sections in this chapter discuss these topics:

2.1 Installation Platforms

You can install the web service for IBM Tivoli Netcool/OMNIbus on the following platforms that support Java Development Kit (JDK) 1.6:

  • Microsoft Windows

  • Oracle Solaris

  • HP-UX

  • Linux

You can install the Oracle Agent for IBM Tivoli Netcool/OMNIbus on the following platforms:

  • Microsoft Windows (2000, 2003, 2008, XP)

  • IBM AIX (RS/6000 OS version 5.2+, 5.3, 6.x, and 7.x)

  • Linux RHEL (64-bit) 5.3, 5.4, 5.6

  • Oracle Solaris (8, 9, and 10)

2.2 Prerequisites

Ensure that the following prerequisites have been met before proceeding to the next section.

  • My Oracle Support Preferred Credentials must be set to enable you to download the Connector from the Self Update page of the Enterprise Manager Cloud Control.

    To set the credentials:

    1. From the Setup menu of Enterprise Manager Cloud Control, select My Oracle Support, then select Set Credentials.

    2. Enter the user name and password information, then click Apply.

    3. From Setup menu, select Extensibilty, then Self Update.

    4. From the Self Update page, click Check Updates to schedule a job to collect the metadata for the connector.

    See Also:

    "Using Self Update to Download Oracle Products" section of the Enterprise Manager Cloud Administration Guide for more details.
  • An IBM Tivoli Netcool/OMNIbus user account must be set up that the web service for Netcool/OMNIbus can use to access the Object Server database. The account must have read permission to the alerts.status, alerts.details, and alerts.journal database tables.

  • An unzip utility must be available on the system where the Oracle Agent for Netcool/OMNIbus is to be installed.

  • A Netcool/OMNIbus Process Agent must be installed on the system where the Oracle Agent for Netcool/OMNIbus is to be installed. Oracle recommends installing the Oracle Agent for Netcool/OMNIbus on the Object Server system.

  • The Netcool/OMNIbus connector requires a Netcool/OMNIbus TEC EIF Probe to insert events into IBM Tivoli Netcool/OMNIbus. This probe can be a single standalone master or a master/slave pair. At a minimum, a master Netcool/OMNIbus TEC EIF Probe must be installed on a system that has connectivity to the Object Server system.

2.3 Installing the Connector in Enterprise Manager

The Netcool/OMNIbus connector is not included out-of-box, so you need to download it from the Oracle Enterprise Manager store. All connectors in the store are available for download via the Self Update page of Enterprise Manager Cloud Control.

Notes:

To download and install (apply) the connector:

  1. From the Setup menu, select Extensibility, then select Self Update.

  2. Click the Management Connector link in the Type column.

    The IBM Tivoli Netcool/OMNIbus connector appears in the list with a status of Available.

  3. Click on IBM Tivoli Netcool/OMNIbus connector to select it, then click Download.

    The Schedule Download window appears, where you can determine when the download should be performed.

  4. Click Select to download immediately.

    If you want to schedule the download for a later time, specify the date and time when the download should occur, and click Select. You will need to return and finish the remainder of this procedure after the scheduled download date and time.

  5. If necessary, refresh the screen until the status of the connector changes to Downloaded.

  6. Click on the IBM Tivoli Netcool/OMNIbus connector to select it, and then click Apply.

    After you respond to the prompt to confirm the operation, a page appears that indicates the request has been submitted.

  7. Refresh the screen until the status of the connector changes from Apply Scheduled to Applied.

See Also:

"Using Self Update to Download Oracle Products" section of the Enterprise Manager Cloud Administration Guide for detailed information and diagnostic procedures.

2.3.1 Installing the Connector if Enterprise Manager is in "Offline" Mode

Under certain circumstances, such as in high security environments, an active Internet connection between Enterprise Manager and the Enterprise Manager Update Store may not be available. In such situations, Enterprise Manager can be set to install the connector in an "offline" mode.

The installation process still requires that a computer exist at your site that has Internet access, as a connection to the Enterprise Manager Update Store is still required to obtain the necessary files. The files that you download to this computer can then be transferred to a computer behind your firewall.

To install the connector if Enterprise Manager is in "offline" mode:

  1. From the system that you will ultimately deploy the connector, set Enterprise Manager Cloud Control to Offline Mode:

    1. From the Setup menu, select Provisioning and Patching, then select Offline Patching.

    2. In the Online and Offline Settings page, select Offline.

  2. From the Setup menu, select Extensibility, then select Self Update.

  3. On the Self Update page, click Check Updates. A message appears with the following URL to an Oracle site from where the updates catalog file can be downloaded:

    https://updates.oracle.com/Orion/Download/download_patch/p9348486_112000_Generic.zip
    
  4. From an Internet-enabled computer, download the catalog file using the aforementioned URL.

  5. Copy the downloaded catalog file to the OMS host or the Management Agent host where you plan to import the connector.

  6. Import the catalog file to Enterprise Manager:

    • If the catalog file is on the OMS host:

      emcli import_update_catalog -file="file" -omslocal
      

      Where:

      • -file: is the direct path to the connector archive (*.zip).

      • -omslocal: indicates that the path mentioned in the -file option is directly accessible to the Enterprise Manager server

    • If the catalog file is on a different host:

      emcli import_update_catalog -file="file" -host="hostname" [-credential_set_name="setname"] | -credential_name="name" -credential_owner="owner"
      

    Example 2-1 shows a sample for importing the catalog archive.

  7. On the Self Update page, in the table, click Management Connectors.

  8. On the Connector Updates page, select the imported update that is available for download. Click Download.

    A message appears with a URL to an Oracle site from where the update can be downloaded.

  9. From a computer that is connected to the internet, download the update using the aforementioned URL.

  10. Copy the downloaded file to the OMS host or the Management Agent host where you plan to deploy the connector.

  11. To import the downloaded connector archive into Enterprise Manager, run the following command:

    emcli import_update -file=”<path to *.zip file>” -omslocal
    

    Where:

    • -file: is the direct path to the connector archive (*.zip).

    • -omslocal: indicates that the path mentioned in the -file option is directly accessible to the Enterprise Manager server

Example 2-1 Sample for Importing Catalog Archive

emcli import_update_catalog -file="/u01/common/p9348486_112000_Generic.zip"  -omslocal

Imports the master catalog file p9348486_112000_Generic.zip. The file must exist
on the OMS host. In a multiple OMS setup, the request can be processed by any
OMS, so the file should be accessible from the OMS processing the request. This
means that the file must be kept on a shared location that is accessible from all
the OMS instances.

emcli import_update_catalog -file="/u01/common/p9348486_112000_Generic.zip" -host="host1.example.com" -credential_set_name="HostCredsNormal"
 
Imports the master catalog file p9348486_112000_Generic.zip that is present on 
the host host1.example.com. The host must be a managed host target in Enterprise
Manager, and the Management Agent on this host must be up and running. The
preferred unprivileged credentials for host host1.example.com are used to retrieve
the remote file.

2.3.2 Exporting the Installation Files

The agent and web service installation files are included in the Self Update archive that was installed in Installing the Connector in Enterprise Manager.

To export the installation files:

  1. Determine the command required to export the adapter installation file. To do this, perform the following steps:

    1. From the Setup menu, select Extensibility, then Self Update.

    2. Click on the Management Connector link in the Type column.

    3. Click on the IBM Tivoli Netcool/OMNIbus connector to select it, then select Export from the Actions list.

      A pop-up window similar to the example shown in Figure 2-2 appears with the command required to export the file.

      Figure 2-2 Export Command Example

      Export Command Example
  2. Open a command window on the Enterprise Manager host system and navigate to a temporary directory where you can copy the file.

  3. Log into EM CLI using the following command:

    emcli login -username=<Enterprise Manager Super Administrator log in>
    

    You will be asked to provide the password information.

    You must execute EM CLI from the OMS server system. See the Oracle Enterprise Manager Command Line Interface for information about setting up EM CLI.

  4. Run the EM CLI export_update command from your system, changing <dirname> to the full path of the temporary directory.

    This action creates a zip file. The file name is comprised of the ID value you specify in the export_update command with a .zip extension. In the example command in Figure 2-2, the zip file name would be:

    1208A7C0D8913455B18D12F65ABCA8A0.zip
    
  5. Extract the installation files from the zip file using the following command:

    unzip *.zip archives/*
    

2.4 Installing the Web Service for Netcool/OMNIbus Front-End

The web service for Netcool/OMNIbus acts as a front-end for all data flowing into and out of Netcool/OMNIbus. Oracle Enterprise Manager posts calls to the web service whenever it needs to create or update an alert or get new or updated alerts from Netcool/OMNIbus.

You can install the web service for Netcool/OMNIbus on any Unix or Windows system that runs the Oracle JDK 1.6 and has connectivity to the Netcool/OMNIbus server and the Oracle Enterprise Manager OMS (Oracle Management Service).

2.5 Web Service for Netcool/OMNIbus on Unix

The following sections explain how to install and then subsequently run the Web Service on a Unix platform:

2.5.1 Prerequisites

The following prerequisites must be met before proceeding to the next section:

  • Oracle Java Development Kit (JDK) version 6 Update 11 or higher is installed.

  • JAVA_HOME environment variable is set to the JDK installation directory.

2.5.2 Installing the Web Service on Unix

To install the web service on a Unix platform, perform the following steps:

  1. Create a directory where you want to install the web service.

  2. Copy the OMNIbus_webservices_adapter.jar file from the Management Server host system to the web service installation directory. The file is located in the archives directory that was extracted in Exporting the Installation Files.

  3. Open a command prompt window and change the working directory to the web service installation directory.

  4. Enter the following command to extract the web services components from the web services .jar file:

    jar xvf OMNIbus_webservices_adapter.jar
    

    Note:

    If the system where the web service for Netcool/OMNIbus is being installed does not have the JDK installed, you cannot extract the jar file contents. You need to copy the .jar file to a system that has the installed JDK and transfer the files after they have been extracted.

    This creates the adapters directory that contains the installation files.

  5. Enter the following command to change the working directory:

    cd adapters/endpoints/omnibus
    
  6. Enter the following command to run the installation script:

    sh ./install.sh
    
  7. When the script prompts whether you want to use HTTPS:

    • If you specify Y, then the web service is set up to use HTTPS port number 8443.

    • If you specify N, then the web service is set up to use HTTP port number 8080.

  8. When the script prompts for the user name of the web service, enter a user name that must be provided to access the web service for Netcool/OMNIbus.

    The user name can be any value and is not associated with any specific OS or Netcool/OMNIbus account. Make a note of this value and supply it when configuring the Netcool/OMNIbus connector in Enterprise Manager.

  9. When the script prompts for the password of the web service, enter the password that must be provided to access the web service for Netcool/OMNIbus.

    The password can be any value and is not associated with any specific OS or Netcool/OMNIbus account. Note this value and supply it when configuring the Netcool/OMNIbus connector in Enterprise Manager.

  10. When the script prompts for the username to access the Object Server database, enter the username of an account that has read access to the alerts.status, alerts.details, and alerts.journals database tables.

  11. When the script prompts for the password to access the Object Server database, enter the password for the account specified in the previous step.

  12. When the script prompts for the host name of the Object Server system, enter the host name or IP address of the system where the Object Server is installed. You will not be allowed to specify a host name of localhost, because the web service will fail when attempting to connect to the Object Server database.

  13. When the script prompts for the Object Server database port number, enter the port number to use when connecting to the Object Server database. The default port number is 4100. To determine the port number used by your system, start the Netcool/OMNIbus Administrator and open the Object Servers window. The port number for the Object Server is listed on this window.

  14. The web service can be configured to attempt to connect to a backup Object Server database if there are problems connecting to the primary Object Server database. You are prompted to specify whether you want to configure the web service to connect to a backup Object Server instance. If you answer N to the prompt, skip to step 17.

  15. When the script prompts for the host name of the backup Object Server system, enter the host name or IP address of the system where the backup Object Server is installed. You are not allowed to specify a host name of localhost, because the web service will fail when attempting to connect to the Object Server database.

  16. When the script prompts for the backup Object Server database port number, enter the port number to use when connecting to the backup Object Server database. The default port number is 4100. To determine the port number used by your system, start the Netcool/OMNIbus Administrator and open the Object Servers window. The port number for the Object Server is listed on this window.

  17. When the script prompts for the master EIF probe host name, enter the host name or IP address of the system where the master TEC EIF probe is installed.

  18. When the script prompts for the master EIF probe port number, enter the port number to use when connecting to the master TEC EIF probe. The port number is defined in the PortNumber property in the tivoli_eif.props file. The file is located in the EIF probe installation directory.

  19. The web service can be configured to also send events to a slave EIF probe when sending events to the master EIF probe. You will be prompted to specify whether you want to configure the web service to send events to a slave EIF probe. If you answer N to the prompt, skip to step 22.

  20. When the script prompts for the slave EIF probe host name, enter the host name or IP address of the system where the slave TEC EIF probe is installed.

  21. When the script prompts for the slave EIF probe port number, enter the port number to use when connecting to the slave TEC EIF probe. The port number is defined in the PortNumber property in the tivoli_eif.props file. The file is located in the EIF probe installation directory.

  22. After the script displays the message "Netcool/OMNIbus Adapter Install Complete," press Enter to complete the installation.

  23. Copy additional required jar files as specified in Copying the Required .jar Files

  24. If the web service was configured to run using the HTTPS protocol, you must set up SSL as specified in Section 6.1, "Configure Oracle Enterprise Manager to Use SSL."

  25. Delete the OMNIbus_webservices_adapter.jar file from the installation directory.

The web service framework is now installed and ready to start.

2.5.3 Running the Web Service on Unix

To run the web service for Netcool/OMNIbus framework commands listed with the following tasks, first change the working directory to ...

adapters/bin

... in the installation directory.

  • Start: ./service.sh start

  • Shut Down: ./service.sh stop

  • Restart: ./service.sh restart

  • Check Status: ./service.sh status

2.5.4 Testing the Web Service on Unix

Perform the following steps to verify that the web service for Netcool/OMNIbus is functional.

  1. Open a terminal and change the working directory to the adapters/bin directory in the installation directory.

  2. Run the test script:

    ./testAdapter.sh
    
  3. When the utility prompts for the web service password, enter the password you specified for the web service for Netcool/OMNIbus in step 9 of Installing the Web Service on Unix.

If the test completes successfully, the last line the utility displays is "Test completed successfully."

2.5.5 Copying the Required .jar Files

The web service for Netcool/OMNIbus requires you to copy the following .jar files in the Web Services installation directory to the lib/adapters directory:

  • log.jar — Used by the EIF probe

  • evd.jar — Used by the EIF probe

  • jconn4.jar — Sybase JDBC driver file

To copy the appropriate .jar files, complete the following steps:

  1. From the Object Server system, access the following directory:

    $OMNIHOME/java/jars
    
  2. Copy the log.jar and evd.jar files to the lib/adapters directory in the web service installation directory.

  3. Access the following URL to download the Sybase JDBC driver file:

    http://downloads.sybase.com/swd/summary.do?client=support&baseprod=63
    
  4. Create an account, which is required to download the driver. After you have created an account, select All from the drop-down list next to "Display" and "in all months" next to "platforms."

  5. Click Go to get a list of drivers available for download.

  6. Select latest version 7 release of jConnect for JDBC and download.

  7. Extract the contents of the .tgz file into a temporary directory.

  8. Navigate to the jConnect installation directory for the appropriate platform:

    ebfxxxxx/unix/Disk1/InstData
    

    Where xxxxx is the version of the jar file.

  9. Run the setup executable to install jConnect.

  10. Navigate to the jConnect-7_0/classes directory in the jConnect installation directory.

  11. Copy the jconn4.jar file to the lib/adapters directory.

Note:

If version 7 of the jConnect is not available for download, you can download the latest version available. With each major version release, the name of the jconn jar file changes; so, the name of the jar file will likely be different.

Whenever the jar file name changes, a configuration change must be made to the OMNIbus Web Service. Listed below are the steps required to make the configuration change to the Web Service:

  1. Navigate to the conf directory of the Web Service installation directory.

  2. Open the framework.properties file in a text editor.

  3. Change the omnibus.sql.driver property to the path of the SybDriver class in the jconn jar file that was downloaded. For example:

    If the jar file is named jconn5.jar, then the path should be:

    com.sybase.jdbc5.jdbc.SybDriver 
    

    If the jar file is named jconn6.jar, then the path should be:

    com.sybase.jdbc6.jdbc.SybDriver.
    

    If there are any problems using those paths, you can use the jar utility to determine the correct path to the SybDriver class as shown below

    jar tvf /path/to/jconnx.jar | grep SybDriver
    
  4. Save the update to the framework.properties file.

  5. Restart the OMNIbus Web Service.

2.5.6 Uninstalling the Web Service on Unix

To uninstall the web service on Unix:

  1. Run the service.sh status command to determine whether the web service is running.

  2. If the web service is running, run the service.sh stop command to stop the web service and verify it completes successfully.

  3. Delete all files in the installation directory.

2.6 Web Service for Netcool/OMNIbus on Windows

The following sections explain how to install and then subsequently run the web service for Netcool/OMNIbus on a Windows platform:

2.6.1 Prerequisites

The following prerequisites must be met before proceeding to the next section.

  • Oracle Java Development Kit (JDK) version 6 Update 11 or higher is installed.

  • JAVA_HOME environment variable is set to the JDK installation directory.

  • Zip utility, such as WinZip, is installed for unzipping a zip file.

2.6.2 Installing the Web Service on Windows

To install the web service on a Windows platform, perform the following steps:

  1. Create a directory where you want to install the web service.

  2. Copy the OMNIbus_webservices_adapter.jar file from the Management Server host system to the web service installation directory. The file is located in the archives directory that was extracted in Exporting the Installation Files

  3. Open a command prompt window and change the working directory to the web service installation directory.

  4. Enter the following command to extract the web services components from the web services .jar file:

    jar xvf OMNIbus_webservices_adapter.jar
    

    Note:

    If the system where the web service for Netcool/OMNIbus is being installed does not have the JDK installed, you cannot extract the jar file contents. You need to copy the jar file to a system that has the installed JDK and transfer the files after they have been extracted.

    This creates the adapters directory that contains the installation files.

  5. Enter the following command to change the working directory as follows:

    cd adapters\endpoints\omnibus
    
  6. Enter the following command to run the installation script:

    install.bat
    
  7. When the script prompts whether you want to use HTTPS:

    • If you specify Y, then the web service is set up to use HTTPS port number 8443.

    • If you specify N, then the web service is set up to use HTTP port number 8080.

  8. When the script prompts for the user name of the web service, enter a user name that must be provided to access the web service for Netcool/OMNIbus.

    The user name can be any value and is not associated with any specific OS or Netcool/OMNIbus account. Note this value and supply it when configuring the Netcool/OMNIbus connector in Enterprise Manager.

  9. When the script prompts for the password of the web service, enter the password that must be provided to access the web service for Netcool/OMNIbus.

    The password can be any value and is not associated with any specific OS or Netcool/OMNIbus account. Note this value and supply it when configuring the Netcool/OMNIbus connector in Enterprise Manager.

  10. When the script prompts for the username to access the Object Server database, enter the username of an account that has read access to the alerts.status, alerts.details, and alerts.journals database tables.

  11. When the script prompts for the password to access the Object Server database, enter the password for the account specified in the previous step.

  12. When the script prompts for the host name of the Object Server system, enter the host name or IP address of the system where the Object Server is installed. You will not be allowed to specify a host name of localhost, because the web service will fail when attempting to connect to the Object Server database.

  13. When the script prompts for the Object Server database port number, enter the port number to use when connecting to the Object Server database. The default port number is 4100. To determine the port number used by your system, start the Netcool/OMNIbus Administrator and open the Object Servers window. The port number for the Object Server is listed on this window.

  14. The web service can be configured to attempt to connect to a backup Object Server database if there are problems connecting to the primary Object Server database. You will be prompted to specify whether you want to configure the web service to connect to a backup Object Server instance. If you answer N to the prompt, skip to step 17.

  15. When the script prompts for the host name of the backup Object Server system, enter the host name or IP address of the system where the backup Object Server is installed. You will not be allowed to specify a hostname of localhost, because the web service will fail when attempting to connect to the Object Server database.

  16. When the script prompts for the backup Object Server database port number, enter the port number to use when connecting to the backup Object Server database. The default port number is 4100. To determine the port number used by your system, start the Netcool/OMNIbus Administrator and open the Object Servers window. The port number for the Object Server is listed on this window.

  17. When the script prompts for the master EIF probe hostname, enter the host name or IP address of the system where the master TEC EIF probe is installed.

  18. When the script prompts for the master EIF probe port number, enter the port number to use when connecting to the master TEC EIF probe. The port number is defined in the PortNumber property in the tivoli_eif.props file. The file is located in the EIF probe installation directory.

  19. You can also configure the web service to also send events to a slave EIF probe when sending events to the master EIF probe. You will be prompted to specify whether you want to configure the web service to send events to a slave EIF probe. If you answer N to the prompt, skip to step 22.

  20. When the script prompts for the slave EIF probe hostname, enter the host name or IP address of the system where the slave TEC EIF probe is installed.

  21. When the script prompts for the slave EIF probe port number, enter the port number to use when connecting to the slave TEC EIF probe. The port number is defined in the PortNumber property in the tivoli_eif.props file. The file is located in the EIF probe installation directory.

  22. After the script displays the message "Netcool/OMNIbus Adapter Install Complete," click Enter to complete the installation.

  23. Copy additional required jar files as specified in Copying the Required .jar Files

  24. If the web service was configured to run using the HTTPS protocol, you must set up SSL as specified in Section 6.1, "Configure Oracle Enterprise Manager to Use SSL."

  25. Delete the OMNIbus_webservices_adapter.jar file from the installation directory.

The web service framework is now installed and ready to start.

2.6.2.1 Running the Web Service as a Windows Service (Optional)

Optionally, if you want the web service to run as a Windows service, perform the following steps:

  1. Change the working directory to the adapters\bin directory in the installation directory.

  2. Enter the following command to install the web service as a Windows service:

    service.bat install
    

2.6.3 Running the Web Service on Windows

You can run the web service either as a standalone service or Windows service.

Running as a Standalone Service

To start the web service for Netcool/OMNIbus framework when set up as a standalone application (not set up to run as a Windows service):

  1. Change the working directory to the adapters\bin directory in the installation directory.

  2. Run the following command:

    startAdapters.bat
    

To shut down the web service Netcool/OMNIbus framework, close the window where you started the web service.

Running as a Windows Service

To start the web service for Netcool/OMNIbus framework when set up to run as a Windows service, enter the following command:

net start iWaveAdapters

To shut down the web service Netcool/OMNIbus framework, enter the following command:

net stop iWaveAdapters

2.6.4 Testing the Web Service on Windows

Perform the following steps to verify that the web service for Netcool/OMNIbus is functional.

  1. Open a terminal and change the working directory to the adapters\bin directory in the installation directory.

  2. Enter the following command to run the test script:

    .\testAdapter.bat
    
  3. When the utility prompts for the web service password, enter the password you specified for the web service for Netcool/OMNIbus in step 9 of Installing the Web Service on Windows.

If the test completes successfully, the last line the utility displays is "Test completed successfully."

2.6.5 Copying the Required .jar Files

The web service for Netcool/OMNIbus requires you to copy the following .jar files in the Web Services installation directory to the lib/adapters directory:

  • log.jar — Used by the EIF probe

  • evd.jar — Used by the EIF probe

  • jconn4.jar — Sybase JDBC driver file

To copy the appropriate .jar files, complete the following steps:

  1. From the Object Server system, access the following directory:

    %OMNIHOME%\java\jars
    
  2. Copy the log.jar and evd.jar files to the lib\adapters directory in the web service installation directory.

  3. Access the following URL to download the Sybase JDBC driver file:

    http://downloads.sybase.com/swd/summary.do?client=support&baseprod=63
    
  4. Create an account, which is required to download the driver. After you have created an account, select All from the drop-down list next to "Display" and "in all months" next to "platforms."

  5. Click Go to get a list of drivers available for download.

  6. Select latest version 7 release of jConnect for JDBC and download.

  7. Extract the contents of the .tgz file into a temporary directory.

  8. Navigate to the jConnect installation directory for the appropriate platform:

    ebfxxxxx\windows\Disk1\InstData
    

    Where xxxxx is the version of the jar file.

  9. Run the setup executable to install jConnect.

  10. Navigate to the jConnect-7_0\classes directory in the jConnect installation directory.

  11. Copy the jconn4.jar file to the lib/adapters directory.

Note:

If version 7 of the jConnect is not available for download, you can download the latest version available. With each major version release, the name of the jconn jar file changes; so, the name of the jar file will likely be different.

Whenever the jar file name changes, a configuration change must be made to the OMNIbus Web Service. Listed below are the steps required to make the configuration change to the Web Service:

  1. Navigate to the conf directory of the Web Service installation directory.

  2. Open the framework.properties file in a text editor.

  3. Change the omnibus.sql.driver property to the path of the SybDriver class in the jconn jar file that was downloaded. For example:

    If the jar file is named jconn3.jar, then the path should be:

    com.sybase.jdbc3.jdbc.SybDriver
    

    If the jar file is named jconn4.jar, then the path should be:

    com.sybase.jdbc4.jdbc.SybDriver
    
  4. Save the update to the framework.properties file.

  5. Restart the OMNIbus Web Service.

2.6.6 Uninstalling the Web Service on Windows

To uninstall the web service on Windows:

  1. Determine if the web service is installed as a Windows service:

    • If the web service is installed as a Windows service, perform the following steps:

      1. Determine if the web service is running.

      2. If the web service is running, run the service.bat stop command to stop the web service and verify it completes successfully.

      3. Run the service.bat uninstall command to remove it as a Windows service and verify it completes successfully.

    • If the web service is not installed as a Windows service, perform the following steps:

      1. Determine if the web service is running.

      2. If the web service is running, stop the web service by closing the Java window.

  2. Delete all files in the installation directory.

2.7 Installing the Oracle Agent for Netcool/OMNIbus

The Oracle Agent for Netcool/OMNIbus is invoked by an Object Server external procedure to send event information to the web service for Netcool/OMNIbus.

Note:

The IBM Tivoli Netcool/OMNIbus Process Control/Process Agent must first be installed on the system where the Agent is to be installed. Oracle recommends installing the Oracle Agent for Netcool/OMNIbus on the Object Server system.

To install the Oracle Agent for Netcool/OMNIbus, perform the following steps:

  1. Create a directory where you want to install the Oracle Agent for Netcool/OMNIbus.

  2. Determine the name of the installation file based on the OS platform where the agent is being installed.

    The platforms and associated installation files are as follows:

    • Windows — OMNIbusAgentWindows.zip

    • AIX — OMNIbusAgentAIX.tar.gz

    • Linux — OMNIbusAgentLinux.tar.gz

    • Oracle Solaris — OMNIbusAgentSolaris.tar.gz

  3. Transfer the appropriate installation file from the Management Server host system to the Agent installation directory. The file is located in the archives directory that was extracted in Exporting the Installation Files.

  4. Extract the files from the zip archive. This creates the agent directory that contains the installation files.

  5. Change the working directory to the agent directory.

  6. Run the setup script to configure the agent.

    The file name depends on the platform. If the platform is Windows, the setup script is named Setup.cmd. For all other platforms, the setup script is named setup.sh and should be called using the following command:

    sh ./setup.sh
    
  7. When the script prompts for the web service host name, enter the host name or IP address where the web service for Netcool/OMNIbus is installed.

  8. When the script prompts for the web service port, enter the port number the web service for Netcool/OMNIbus uses to receive transactions from the Agent.

    The default port number of 8080 will be used most of the time and will even be used if the adapter is configured to use HTTPS. The only time the default port number will not be used is when the default port is changed as specified in the Changing the Web Service Port (8080) section in Appendix A. If you are unsure of what port number to use, perform the following steps to determine the port number to use:

    1. At the system where the web service is installed, navigate to the adapters/conf directory.

    2. Open the framework.properties file in a text editor and search for the notification.url property.

    3. Whatever port number is specified in the notification.url property is the port number you should specify.

  9. When the script prompts for the user ID to specify when creating event journal entries in Netcool/OMNIbus, enter the user ID of a user that has permission to add journal entries. If no value is specified, the user ID will default to 0 (root). The value specified must be an integer value and will not work properly if a different value is entered.

    The script generates the necessary configuration files and places them in the Agent directory. The Agent is now installed, but you need to make some modifications in Netcool/OMNIbus for everything to function properly.

  10. Perform the steps in Modifying Netcool/OMNIbus to complete the setup.

2.7.1 Uninstalling the Oracle Agent for Netcool/OMNIbus

To uninstall the Oracle Agent for Netcool/OMNIbus:

  1. If the agent is being permanently deleted, the OMNIbus server modifications must be backed out as specified in Uninstalling Modifications to Netcool/OMNIbus.

  2. Delete all files in the installation directory.

Note:

If the Oracle Agent for Netcool/OMNIbus is being replaced, the database external procedures that call the agent will fail until the replacement agent has been installed in the same location.

2.8 Modifying Netcool/OMNIbus

The procedures in the following sections enable you to configure Netcool/OMNIbus to work with the installed Oracle Agent and web service components:

2.8.1 Configuring the Object Server Database

Perform the following steps to run the configuration script that sets up the Netcool/OMNIbus Object Server database to work with the installed Oracle Agent and web service components.

  1. If the Oracle Agent for Netcool/OMNIbus was NOT installed on the primary Object Server system, copy the configure_oracle_webservice.sql file from the system where the Oracle Agent for Netcool/OMNIbus was installed to the system where the primary Object Server is installed.

  2. Run the SQL script using the appropriate command listed below based on the applicable platform:

    Unix:

    $OMNIBUSHOME/bin/nco_sql -S <objserver> -U <username> -P <password>
    < <script_directory>/configure_oracle_webservice.sql
    

    Windows:

    "%OMNIBUSHOME%\bin\isql" -S <objserver> -U <username> -P <password>
    -i <script_directory>\configure_oracle_webservice.sql
    

    When entering the commands, provide the following information:

    • objserver — Object Server name

    • username — User name that will be used when connecting to the database. The account must have permission to create tables, triggers, and procedures in the Object Server database.

    • password — Password associated with the user name

    • script_directory — Directory where the configure_oracle_webservice.sql file is located. If the Oracle Agent for Netcool/OMNIbus was installed on the primary Object Server system, this will be the Oracle Agent for Netcool/OMNIbus installation directory. Otherwise, it will be the directory where the file was copied.

2.8.2 Configuring the TEC EIF Probe

You need to manually change the set up of the TEC EIF probe configuration to accept alerts from the web service for Netcool/OMNIbus. You must modify the existing EIF probe rules file to include an Oracle-supplied rules file.

Note:

If the probes are configured to operate in a master/slave pair, these changes are required for each probe.

To install the new rules file, perform the following steps:

  1. Shut down the EIF probe.

  2. Access the EIF probe installation directory.

  3. Make a back-up copy of the existing tivoli_eif.rules file.

  4. Copy the oracle_eif.rules file from the system where the Oracle Agent for Netcool/OMNIbus was installed to the EIF probe install directory.

  5. Modify the tivoli_eif.rules file as follows:

    1. Insert the following statements before any other executable statements:

      defaultAlerts = registertarget("<PRIMARY>", "<BACKUP>", "alerts.status")
      OracleAlerts = registertarget("<PRIMARY>", "<BACKUP>", "custom.oracle_status")
      
    2. Replace <PRIMARY> with the name of the primary object server.

    3. Replace <BACKUP> with the name of the back-up server. If a back-up is not configured, replace it with an empty string so that the back-up server is "".

    4. In the location where the tivoli_eif_tpc.rules and tivoli_eif_tsm.rules files are included, add an include statement for the oracle_eif.rules file.

    5. Save the tivoli_eif.rules file.

  6. Make sure the Inactivity parameter for the tivoli_eif.props file is set to 0.

  7. Restart the EIF probe.

Note:

After installing the EIF Probe, at a minimum, you need to edit the tivoli_eif.props file and set the correct Netcool/OMNIbus server name. The file can be found in the following locations:

For UNIX:

%OMNIHOME%/probes/<platform>/tivoli_eif.prop

For Windows:

%OMNIHOME%\probes\<platform>\tivoli_eif.prop

Where:

<platform> is the actual platform name (such as win32).

Refer to the IBM Netcool/OMNIbus Installation and Deployment Guide for more information on configuring the EIF Probe:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=%2Fcom.ibm.tivoli.namomnibus.doc%2Fwelcome_ob.htm

2.8.3 Change Deduplication Trigger Priority

The oracle_alert_reinserted trigger in the primary_only group must run first in order to function properly. To ensure the trigger runs first, the priority of the deduplication trigger in the default_triggers group must be changed from 1 to 2.The trigger priority can modified using the Netcool/OMNIbus Administrator application.

Note:

On some older versions of Netcool/OMNIbus, this trigger does not exist. If the trigger does not exist in your system, then no changes are required in this section.

2.8.4 Uninstalling Modifications to Netcool/OMNIbus

To uninstall modification made to Netcool/OMNIbus:

Revert Deduplication Trigger Priority

Change the priority of the deduplication trigger in the default_triggers group back to 1. The trigger priority can modified using the Netcool/OMNIbus Administrator application.

Revert TEC EIF Probe Configuration

Perform the following to revert the TEC EIF probe configuration back to its original settings:

  1. Shut down the EIF probe.

  2. Access the EIF probe installation directory.

  3. Replace the tivoli_eif.rules file with the backup copy of the file that was created during installation.

  4. Delete the oracle_eif.rules file from the EIF probe install directory.

  5. Restart the EIF probe.

Revert the Object Server Database Configuration

Perform the following steps to uninstall the customizations made to the Netcool/OMNIbus Object Server database during installation:

  1. If the Oracle Agent for Netcool/OMNIbus was NOT installed on the primary Object Server system, copy the uninstall_oracle_webservice.sql file from the system where the Oracle Agent for Netcool/OMNIbus was installed to the system where the primary Object Server is installed.

  2. Run the SQL script using the appropriate command listed below based on the applicable platform:

    • Unix:

      $OMNIBUSHOME/bin/nco_sql -S <objserver> -U <username> -P <password> <script_directory>/uninstall_oracle_webservice.sql
      
    • Windows:

      "%OMNIBUSHOME%\bin\isql" -S <objserver> -U <username> -P <password> -i <script_directory>\uninstall_oracle_webservice.sql
      

    When entering the commands, provide the following information:

    • objserver — Object Server name

    • username — User name that will be used when connecting to the database. The account must have permission to delete tables, triggers, and procedures from the Object Server database.

    • password — Password associated with the user name

    • script_directory — Directory where the uninstall_oracle_webservice.sql file is located. If the Oracle Agent for Netcool/OMNIbus was installed on the primary Object Server system, this will be the Oracle Agent for Netcool/OMNIbus installation directory. Otherwise it will be the directory where the file was copied.

2.9 Uninstalling the Connector

To uninstall the connector, you must first delete all defined instances of the connector, then you must delete the connector from the Self Update page.

  1. From the Setup menu, select Extensibility, then Management Connectors.

  2. Select an instance of the connector you want to delete, then click Delete.

  3. On the Confirmation page, click Yes.

  4. Repeat steps 2 and 3 until all instances of the connector have been deleted.

  5. From the Setup menu, select Extensibility, then Self Update.

  6. Click on the Management Connector link in the Type column. A list of updates appears for Management Connectors.

  7. Click on the connector you want to delete, select Actions, then select Delete. The Delete Update window appears.

  8. Click Delete to delete the connector. A pop-up confirmation window appears.

  9. Click OK to confirm and delete the connector.