2010 11 10 avks omnibus core overview (2)

8/10/2019 2010 11 10 AVKS OMNIBus Core Overview (2)

1/46

Netcool/OMNIBus Core Overview

2009 IBM CorporationNetcool/OMNIBus Core Overview


Venkat M. [email protected]


2/46


2009 IBM Corporation2 Netcool/OMNIBus Core Overview

Agenda

What is Netcool/OMNIbus

Basic Architecture/Components

Object Server

Probs

Gateways Administrator GUI Tool

Event List (Desktop)

Web GUI

Basic Failover

SQL Interface

Import/Export Utility Process Agent (PA)

Server Editor

Proxy Server

Deployment Steps

Supported Platforms

Basic Failover

Multi-tiered Architecture

OMNIbus Automations

Triggers

Procedures

ObjectServer SQL

Troubleshooting

OMNIbus Probe Architecture

OMNIbus Gateways Architecture

Additional Information/References

Questions


3/46



Product Overview - What is Netcool/OMNIbus

It is a SLM system that collects enterprise-wide event information from awide variety of IT and network resources in real time.

Presents a consolidated view of this information to operators andadministrators for monitoring and management.

Tracks alerts/events in a high-performance, in-memory database, andpresents information of interest to specific users via filters and views.

Provides automation functions that can perform intelligent processing ofalerts.

Alerts (Events) information can then be:

Assigned to operators

Passed to helpdesk systems Logged in a database

Replicated to remote OMNIbus system for consolidation/failover/HA

Used to trigger automatic responses to certain events


4/46



Netcool/OMNIbus - Basic Architecture


5/46



Netcool/OMNIbus - Components

ObjectServer

Probes

Gateways

DesktopEvent List

Administration tools

The Web GUI Server

Gateway Target(s)

RDBMS

HelpDesk/CRM/Etc.


6/46



Netcool/OMNIbusObject Server

Provides the in-memorydatabase which is the core

Event information is forwarded tothe ObjectServer from

Probes, Gateways, etc. Event information is stored and

managed in database tables

Events are displayed in DesktopEvent Lists

or Active Event List (AEL) inthe Web GUI

Provides Automations


7/46



Netcool/OMNIbusProbes

Probes connect to an eventsource and

Detects/Acquires event data

Forwards the data to ObjectServer asevents/alerts

Probes use the logic specified ina rules file to map event elements to OS

fields/columns of alerts.status

Each probe is uniquely designed to acquire event data from a specific

source

Probes can acquire data from Sources like Network Devices,

Databases, Log Files


8/46



Netcool/OMNIbus - Gateways

Gateways enable exchange of eventsbetween ObjectServer to

Applications, Databases,Helpdesk, etc.

ObjectServer Gateways to replicate

events with backup ObjectServer for failover

Application gateways integratebusiness functions.

Eg. Reporting/Archiving, AutoTrouble Ticketing, etc.

Transfer of events once configured istransparent to operators


9/46



Netcool/OMNIbusAdministrator GUI Tool

OMNIbus Administrator is agraphical tool

OMNIbus Administrator can beused to

Configure and ManageObjectServers

Configure process control(PAs)

Started via

$OMNIHOME/bin/nco_config

Netcool Suite > Administrator


10/46



Netcool/OMNIbus -Administrator GUI Tool

Use Administrator to configure thefollowing ObjectServer objects:

Users, groups, roles, and restriction filters

Event list menus, Tools and prompts

Trigger groups/triggers/Procedures User-defined signals

Event list alert severity colors

Conversions, Classes, Column Visuals

ObjectServer DB, Files, and properties

Channels for AEN

Note most of the functions are available viaCLI or SQL interface


11/46



Netcool/OMNIbusEvent List (Desktop)

The desktop is an integratedsuite of graphical tools used to

View and manage events

Configure how eventinformation is presented

Event information is delivered ina format that you can use to

Quickly determine theavailability of ITresources/Services

Most of the features of thedesktop are also available in theWeb GUI component


12/46


13/46



Netcool/OMNIbusWeb GUI

The Web GUI is a Web-based applicationthat

Processes network events from oneor more data sources

Presents the event data to users invarious graphical formats

The Web GUI contains most features ofthe /OMNIbus native desktop environment.

The Web GUI uses a client-serverarchitecture.

The Web GUI server runs inside TivoliIntegrated Portal (TIP)

Clients connect to TIP to access the WebGUI.

The Web GUI can be configured forintegrations with other Tivoli products.


14/46




Web GUI main components:

Active Event List (AEL) A Java applet functionally similar to native

desktop

Lightweight Event List (LEL) A dynamic HTML event list that provides the

data filtering, data sorting, and information drill-down capabilities of the AEL without the eventmanagement tools

Table View A static HTML event list in the form of a table

showing a defined set of alerts.

Event Dashboard Presents the alert information as a series of

monitor boxes, from which you can open AELs.

Maps Administrators can use maps to design visual

representations of a network and to createinteractive graphical views networkperformance.

Chart rendering component Administrators can create charts that present

high-level information to users in a number ofgraphical formats including bar charts and piecharts.


15/46





16/46



Netcool/OMNIbusSQL Interface

SQL interactive interface

Connect to an ObjectServer, anduse you to

SQL cmds. for defining andmanipulating database objects.

SQL cmds. to interact with, andcontrol, the objectServer

Enables tasks such as creating anew database table or stoppingthe ObjectServer

Available via Admin. GUI or CLI

Use nco_sql on UNIX, isql onWindows or nco_config


17/46



Netcool/OMNIbusImport/Export Utility

Utility or Tool (nco_confpack):

Export and Importconfigurations to deployduplicate systems

Extract a subset ofconfiguration items fromObjectServers and importthem into otherObjectServers

Save ObjectServerconfiguration data forbackup/restore purposes


18/46



Netcool/OMNIbusProcess Agent (PA)

PA performs two primary tasks:

It runs external procedures that arespecified in automations.

It manages local and remoteprocesses.

PA is used to configure remote processes

in order to simplify the management ofOMNIbus components

ObjectServers, probes, andgateways.

The process control system consists of:

Process agents installed on each hostfor managing processes

A set of command-line utilities thatprovide an interface to processmanagement

N t l/OMNIB C O i


19/46



Netcool/OMNIbusServer Editor

Server Editor used tomaintain communicationinformation for the OMINbuscomponents

Interfaces files

The desktop client and clientcomponents connects to theObjectServer using the portdefined by the interfaces filefor communications.

N t l/OMNIB C O i


20/46



Netcool/OMNIbusServer Editor

Use the Server Editor to

Create and modifycommunication details(interfaces file)

Test server activity (nco_ping)

Configure virtual server forfailover pair (primary/backkup)

To start the Server Editor

On Windows Click Start Programs Netcool Suite System Utilities Servers Editor

$NCHOME/omnibus/bin/nco_xigen at Unix cmd. prompt

N t l/OMNIB C O i


21/46



Netcool/OMNIbusProxy Server

Usually alerts are forwardeddirectly to the ObjectServer.

When a large number of probesand desktops connects directly tothe ObjectServer, there can be a

negative impact on performance.

Proxy server can reduce thenumber of probe connections

Multiple probe connectionsmade to the proxy server are

multiplexed and forwardedthrough a single connectionto the ObjectServer.

Netcool/OMNIB s Core O er ie


22/46



Netcool/OMNIbus - Deployment Steps

Step 1: Access software and Productdocumentation

From Passport Advantage, XL, etc.

Step 2: Evaluate H/W and S/W systemrequired

See Planning information

Step 3: Review the base architecture Step 4: Install the non-Web components of

Tivoli Netcool/OMNIbus

Step 5: Create an ObjectServer databasefor use

Step 6: Install the probe and gatewaycomponents

Download and install the requiredprobe and gateway components



23/46



Netcool/OMNIbus - Deployment Steps

Step 7: Set up the connections betweenserver components

Define and generate the interface fileusing the Server Editor

Step 8: Install and configure the Web GUIcomponent (optoinal)

Before installing the Web GUIcomponent, start the ObjectServer.

Step 9: Configure process agents(optional) to manage processes

Step 10: Install additional desktop clients(optional)

On additional user workstations, ifrequired.



24/46



Netcool/OMNIbusSupported Platforms

Tivoli Netcool/OMNIbus is supportedon various versions of UNIX, Linux,and Windows.

aix5 - AIX systems

hpux11 - HP-UX PA-RISC-based

systems hpux11hpia - HP-UX Integrity-

based systems

linux2x86 - Red Hat Linux andSUSE systems

linux2s390 - Linux for System z

solaris2 - Solaris systems

win32 - Windows systems



25/46



Netcool/OMNIbusStarting/Stopping ObjectServer

To start an ObjectServer as aprocess, enter the followingcommand:

nco_pa_start -process ObjectServer

Use the nco_objserv commandto start the ObjectServermanually.

$NCHOME/omnibus/bin/nco_objserv[ -name servername ]

To stop an ObjectServer as aprocess, enter the followingcommand:

nco_pa_stop -process ObjectServer

Use the SQL interactive interfaceconnects to ObjectServer. Whenthe SQL prompt is displayed,enter the following commands:

1> alter system shutdown;

2> go



26/46



Netcool/OMNIbusBasic Failover

The virtual ObjectServer isconfigured using

Primary/Backup failover pair

Desktops, gateways, and probes

are connected to the failover pair If the primary object server fails,

Clients switch to the backupautomatically

When the primary object server

is available again, Clients reconnect

automatically to it (Fallback)



27/46



Netcool/OMNIbusMulti-tiered Architecture

The standard multitieredarchitecture ( 3-Tire )

Collection

Aggregation Display

ObjectServers and associatedObjectServer Gateways



28/46



Netcool/OMNIbus - Automations

Processes alerts withoutrequiring an operator to takeaction

For example,

Generic_Clear Trigger

Deduplication Trigger

Netcool/OMNIbus includes anumber of standardautomations

Include Triggers, Signals, andExternal Procedures



29/46



Netcool/OMNIbus -Automations

Triggers automatically perform a triggeraction or fire

when the ObjectServer detects anincident (DB change) associated witha trigger

Triggers can can run in response tochanges

SQL commands

Call procedures

Signals are alsopart of the automationsubsystem

Signals can have triggers attached

ObjectServer can automaticallyrespond to signals are raised

Procedures are executable programs thatare created to perform common operations



30/46



Netcool/OMNIbus Automations - Triggers

Trigger Types

Database triggers

Pre/Post database action

Delete/Insert/Reinsert/Update

Signal triggers Signal triggers fire when a

system or user-defined signalis raised

Temporal triggers

Temporal triggers fire based

on a specified frequency

For example, delete_clear



31/46



Netcool/OMNIbus Automations - Procedures

A procedure is an executable object thatcan be called to perform commonoperations.

The types of procedures are as follows:

SQL procedures, which manipulatedata in an ObjectServer database

For example, SQL procedure thatgenerates a report on the total numberof alerts received (and deduplicated) fora given node

External procedures, which run anexecutable file on a local or remotesystem

For example, external procedure calls aprogram called nco_mail, which sendse-mail about unacknowledged criticalalerts.



32/46


Netcool/OMNIbus - ObjectServer SQL

ObjectServer SQL commands include:

DDL cmds. to create, alter, and drop DBobjects

DML cmds. to query and manipulate data inexisting database objects

System cmds. to alter the configuration of

an ObjectServer

SQL interactive interface to connects to anObjectServer and run SQL commands.

UNIX nco_sql -server servername -user username; Windows isql -Sservername -U username

nco_sql -server OS1 -username

myuser -password mypass 1> select * from alerts.status; 2> go



33/46


Netcool/OMNIbus - ObjectServer Troubleshooting

Check Environment variables

$NCHOME, and $OMNIHOME

Check nco process

PA, pseaf | grep nco

Check Port Usage

netstat -na | grep 4100 Check th e interface fi le

Servers Editor (nco_xigen)

Check DEBUG logs

MessageLevel DEBUG

Check DB Size (number of events)

select count(*) from alerts.status; Check ObjectServer profile

Enable Profiling



34/46


Additional Information/References

IBM Tivoli Netcool/OMNIbusdocumentation

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp

IBM Redbooks

Certification Guide Series: IBM TivoliNetcool/Webtop V2.0 Implementation

Best Practices for IBM Tivoli EnterpriseConsole to Netcool/OMNIbus Upgrade

Integration Guide for IBM TivoliNetcool/OMNIbus, IBM Tivoli Network

Manager, and IBM Tivoli NetcoolConfiguration Manager

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsphttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsphttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsphttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp


35/46


Netcool/OMNIbus - Probe Architecture

The function of a probe is to acquireinformation from an event source andforward it to the ObjectServer.

Probes use tokens and elements, andapply rules, to transform event sourcedata into a format that the ObjectServercan recognize.

1. Event data is generated by the probetarget.

2. The probe acquires the event data andprocesses it based on a rules file. Theprobe then forwards the processed datato the ObjectServer as an alert.

3. The ObjectServer stores and managesalerts, which can be displayed in theevent list, and optionally forwarded to oneor more gateways.



36/46


Netcool/OMNIbus - Probe Architecture

1. The probe breaks the raw event data intotokens.

2. The probe then parses these tokens intoelements and processes the elementsaccording to the rules in the rules file.

Elements are identified in the rulesfile by the $ symbol. For example,

$Node.3. Elements are used to assign values to

ObjectServer fields.

Elements are indicated by the @symbol.

4. Fields make up the alerts that areforwarded to the ObjectServer, and arestored/managed in the alerts.status table.

5. The Identifier field is derived or generatedby the rules file and is used fordeduplication.



37/46


Netcool/OMNIbus - Probes

Universal Probes, for

example,

SNMP probe - nco_p_mttrapd

Log File Probe - nco_p_glf

ODBC Probe - nco_p_odbc

Specific Probes, fore

example,

Tivoli EIF Probe nco_p_tivoli_eif

Cisco PIX Probe - nco_p_pix

Microsoft SCOM Probe -nco-p-scom2007



38/46


Netcool/OMNIbus - Probe Types

Probes can be categorized based on howthey acquire events. The types of probesare:

Device

Log file

Database

API

CORBA

Miscellaneous

The probe type is determined by themethod in which the probe detects events.For example,

Probe for Agile ATM Switch Managementdetects events produced by a device, but itgets events from a log file, not directly fromthe switch. So, it is considered as a log file

probe and not a device probe. Probe for Oracle obtains event data from a

database table, and is a database probe.



39/46


Netcool/OMNIbusProbe Components

Netcool/OMNIbus probe usuallyconsists of the following primarycomponents:

an executable file, a properties file,

a rules file, and Optional additional probe specific

components.

The executable file is the core of a

probe. It connects to the event source,processes events, and forwards theevents to the ObjectServer as alerts.

The executable file for the Simnet Probe that runs onLinux is:$OMNIHOME/probes/linux2x86/nco_p_simnet

To start Simnet Probe on UNIX, run thewrapper script :

$OMNIHOME/probes/nco_p_simnet

When the probe starts, it gets theconfiguration information from eventdefinition, properties, and rules file

simnet.def, simnet.props, simnet.rules



40/46


Netcool/OMNIbusGateways



41/46



The preceding figure illustrates how to usegateways for a variety of purposes:

1. Probes send alerts to the localObjectServer.

2. The ObjectServer Gateway replicatesalerts between ObjectServers in afailover configuration.

3. The Helpdesk gateway integrates theNetwork Operations Center (NOC)and the helpdesk by convertingtrouble tickets to alerts, and alerts totrouble tickets.

4. The RDBMS gateway stores criticalalerts in a relational databasemanagement system (RDBMS) sothat you can analyze networkperformance.



42/46



Gateways can send alerts toa variety of targets:

Another ObjectServer (Uni& Bi Gateway)

A database (ODBCGateway)

A helpdesk application(Remedy Gateway)

Other applications or

devices (Flat FileGateway)



43/46



A unidirectional ObjectServerGateway

allows alerts to flow from asource ObjectServer to a

destination ObjectServer

A bidirectional ObjectServerGateway

allows alerts to flow from

both source/destinationObjectServer



44/46



Gateways have reader andwriter components.

Readers extract alerts fromthe ObjectServer.

Writers forward alerts toanother ObjectServer or toother applications.



45/46



Tivoli Netcool/OMNIbus gateways

Gateway for Clarify

Flat File Writer Gateway

Gateway for HP ServiceCenter

ObjectServer Gateway Guide for V7.3.0

ObjectServer Gateway Guide for V7.2.1

ObjectServer Gateway Guide for V7.2

ODBC Gateway Gateway for Oracle

Gateway for Remedy ARS

Gateway for Siebel

SNMP Writer Gateway

Socket Writer Gateway

TCP Echo Utility Gateway

Gateway for Tivoli EIF

Gateway for TSRM Message Bus Integration

Integration with TSRM

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.tivoli.nam.doc/welcome_og.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/clarify/clarify/wip/concept/clargw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/flatfilegw/flatfilegw/wip/concept/flatfilegw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/hpservicecenter/hpservicecenter/wip/concept/hpscgw_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/objectservergw/objectservergw/wip/concept/objsrvgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/objectserver/objectserver/wip/concept/objsrvgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus_gateways.doc/objsrv/concept/objsrvgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/odbc/odbc/wip/concept/odbcgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/oracle/oracle/wip/concept/oraclegw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/remedy/remedy/wip/concept/remgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/siebel/siebel/wip/concept/siebgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/snmpgw/snmpgw/wip/concept/snmpgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/socketgw/socketgw/wip/concept/socketgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tcpeu/xF594402244.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tivoli_eif/tivoli_eif/wip/concept/tveifgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tsrmgw/tsrmgw/wip/concept/tsrmgw_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/xmlintegration/xmlintegration/wip/concept/xmlmisc_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tsrmintegration/tsrmintegration/wip/concept/tsrm_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tsrmintegration/tsrmintegration/wip/concept/tsrm_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tsrmintegration/tsrmintegration/wip/concept/tsrm_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/xmlintegration/xmlintegration/wip/concept/xmlmisc_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/xmlintegration/xmlintegration/wip/concept/xmlmisc_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tsrmgw/tsrmgw/wip/concept/tsrmgw_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tsrmgw/tsrmgw/wip/concept/tsrmgw_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tivoli_eif/tivoli_eif/wip/concept/tveifgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tivoli_eif/tivoli_eif/wip/concept/tveifgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tcpeu/xF594402244.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tcpeu/xF594402244.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/socketgw/socketgw/wip/concept/socketgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/socketgw/socketgw/wip/concept/socketgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/snmpgw/snmpgw/wip/concept/snmpgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/snmpgw/snmpgw/wip/concept/snmpgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/siebel/siebel/wip/concept/siebgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/siebel/siebel/wip/concept/siebgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/remedy/remedy/wip/concept/remgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/remedy/remedy/wip/concept/remgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/oracle/oracle/wip/concept/oraclegw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/oracle/oracle/wip/concept/oraclegw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/odbc/odbc/wip/concept/odbcgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/odbc/odbc/wip/concept/odbcgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus_gateways.doc/objsrv/concept/objsrvgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus_gateways.doc/objsrv/concept/objsrvgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/objectserver/objectserver/wip/concept/objsrvgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/objectserver/objectserver/wip/concept/objsrvgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/objectservergw/objectservergw/wip/concept/objsrvgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/objectservergw/objectservergw/wip/concept/objsrvgw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/hpservicecenter/hpservicecenter/wip/concept/hpscgw_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/hpservicecenter/hpservicecenter/wip/concept/hpscgw_introduction.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/flatfilegw/flatfilegw/wip/concept/flatfilegw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/flatfilegw/flatfilegw/wip/concept/flatfilegw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/clarify/clarify/wip/concept/clargw_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.tivoli.nam.doc/welcome_og.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.tivoli.nam.doc/welcome_og.htm


46/46

Questions

2010 11 10 avks omnibus core overview (2)

Documents