These integrations will be available for download from Xtreme Leverage on 30th November.    Netcool Knowledge Library (NcKL) Enhanced Probe Rules V3.7 Multiplatform English  Netcool/OMNIbus Gateway Configuration Scripts (Audit Mode : nco-g-audit-scripts 2_0) Netcool/OMNIbus Gateway Configuration Scripts (Reporter Mode : nco-g-reporter-scripts 4_0) Netcool/OMNIbus Gateway Interactive Command Tool (nco-g-icmd 1_0) Netcool/OMNIbus Gateway Java Support Package (libngjava 5_0) Netcool/OMNIbus Gateway NGtkTK Support Package (libngtktk 4_0)... [More]

Tags:  netcool nckl gateway tivoli probe omnibus

Enrichment event can be defined as event that contained network entity and topology information. In general, there are several event fields that are required in order for event enrichment between OMNIbus and IBM Tivoli Network Manager (ITNM) to take place. These existing OMNIbus object server field can be easily populated in the probe rules file. Therefore, the ingredients (object server fields) for this recipe are as listed in section below. Ingredients @LocalNodeAlias @NmosEventMap @LocalPriObj @LocalRootObj @RemoteNodeAlias The ingredients... [More]

Tags:  tivoli omnibus rules probe netcool event-enrichment integration itnm

From OMNIbus Web GUI 7.3.1 fix pack 4 onwards, when configuring a map, you can choose the target action for active elements on the map such that it will update an AEL portlet which is placed on the same TIP page as the map itself. This could be used so that when an active element on the map (such as a button, image, or monitor box) is clicked, the AEL which is visible on the same page will be updated to display the events for the corresponding filter of the clicked item. However, for older releases of Web GUI these options are not available. In... [More]

Tags:  frameset web map ael gui omnibus frame page

I am pleased to announce the publication of a new Tivoli Netcool/OMNIbus best practices document:   Upgrading Tivoli Netcool/OMNIbus 7.x in Production Environments Best Practices   The purpose of this document is to be a supplementary reference to anyone upgrading Tivoli Netcool/OMNIbus 7.x in a production environment.  Upgrading in a production environment is different to any other sort of environment because the focus on data preservation is of paramount importance - as is the need to minimise any outages.  Upgrades in production systems have... [More]

Tags:  upgrading netcool omnibus tivoli

The ObjectServer writes performance information to log files. These logs can give information the time spent running SQL queries, identify which clients are using excessive resources and show CPU usage of individual triggers. In my experience it's often useful to get a high level picture before diving into details. One way of encouraging yourself to look at the overview before delving into details is to generate a graph of key performance indicators over time and focus on areas of interest highlighted by the graph. In this blog I will describe... [More]

Tags:  omnibus objectserver

  1) Use Process Explorer from Sysinternals to open current running process. Download link:  http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx 2) Double-click on the probe name (Example: nco_p_wineventlog). 3) Check the .NET version from .NET Assemblies tab.     Note: - The first three versions of the CLR are specified by "v1.0.3705", "v1.1.4322", and "v2.0.50727". - The .NET Framework version 3.0 and 3.5 use version 2.0.50727 of the CLR. - Beginning with the .NET Framework version 4, only the major and... [More]

Tags:  probe-integrations .net omnibus

Tivoli Netcool OMNIbus Probes with dependency on Microsoft .Net Framework may have a minimum level of .Net version to run. To check what version of .Net installed on the machine, follow steps below: 1) Run command "regedit" from console to open Registry Editor 2) Look for HKEY_LOCAL_MACHINE\Microsoft\NET Framework Setup\NDP 3) All installed .NET Framework versions are listed under NDP drop-down list Example: Screenshot from my workstation (I have .Net v3.5 SP1 installed): Reference for each Microsoft .Net version numbers: ... [More]

Tags:  omnibus .net probe-integrations microsoft

For an OMNIbus Web GUI server that services requests for lots of users there may be a need to increase the Java heap size that is allocated for the server. However, it should be noted that for 32-bit processes there is an upper limit for the amount of memory that can be used: 4GB. This cannot be changed and is in force even if your server has a 64-bit processor, 64-bit Operating System and more than 4GB memory. This limit has some knock-on effects to the amount of heap that can practically be allocated.   The memory used by the Web GUI server... [More]

Tags:  webgui omnibus java webtop

When working with various OMNIbus integrations it is quite often that they are run with the “-version” argument to obtain the version information. However there is another universal integration argument that is not very well known called “dumpprops”. The output of this  argument  provides a full list of all the specific integration arguments and values, along with any of the generic integration arguments and values that are provided by the version of OMNIbus used. The values shown in the output are those that would be used when the... [More]

Tags:  omnibus gateway integrations probe

Explore 2 methods to capture probe raw file and replay the file.   For further info, refer to the following link :  How to turn ON probe raw capture file and replay the file

Tags:  raw stdin omnibus troubleshooting itnm capture

The Netcool/OMNIbus information center at http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc_7.3.1/omnibus/wip/welcome.htm has been updated with new and improved documentation. Both the HTML documentation and the PDF guides, which you can download at  http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc_7.3.1/omnibus/wip/common/reference/omn_ref_PDFbooks.html now feature: Web GUI LDAP Troubleshooting A extensive new section has been added that describes common problems... [More]

Tags:  information-center omnibus documentation

Core dumps in UNIX are important to analyze the memory state of a specific probe during a crash. It is used as debugging aid to investigate the reason behind the crash (memory leak, segmentation faults, etc) and where does the crash occur in probe source codes.   NOTE:  Users need to request probe binary which built with Debug mode turned ON from OMNIbus Integrations L3 Support for a meaningful dump analysis.    SMC Wiki link:... [More]

Tags:  probe-integrations dumps omnibus

Valgrind is a debugging tool that can be used by OMNIbus users to detect probes memory leak and error thrown by glibc. Due to limited platform support, this tool can only be used if probe runs on Linux machine.   This tool is most useful if the issue on user environment is hardly reproduced on other environment (example: L2 Support env), because it run probe binary as normal execution. Users are also not required to produce core files to have the backtrace log. Therefore, users do not need to wait memory leak until probe crash to have the core... [More]

Tags:  valgrind omnibus probe-integrations

Why need to enforce which .NET version to use? Some issues on Microsoft .NET Framework API are impacting probe which require forcing of using specific .NET version as a workaround. Examples: 1)   Defect in .NET 3.5 causes probe to misbehave in East-Asian locale when event data volume reaches 2GB. Users of East-Asian languages must either enable UTF-8 mode in this probe or upgrade .NET Framework in probe machine to version 4.0. 2)   The design of .NET Framework 4.0 to use strict rendering may cause probe fail to retrieve EventDescription if... [More]

Tags:  omnibus probe-integrations microsoft