What's new in this release

Tivoli Netcool/OMNIbus V8.1 provides new features and enhancements that focus on the following areas: ease of deployment, integration, interoperation, performance, scalability, and high availability.

Summary of new features

This description of the new features and enhancements is also available in the Release Notes®.

Server components

Items that are preceded by a fix pack graphical cue (for example, Resolved from fix pack 1) indicate a function or feature that is only available in the specified fix pack and later fix packs. The function or feature is not present in the base version of the product.

Initial Configuration Wizard
The Initial Configuration Wizard (nco_icw) automates some initial configuration tasks, such as creating ObjectServers and gateways. The wizard presents a series of panes in which you can create the common components of a Tivoli Netcool/OMNIbus installation for one or more computers. When your configuration is complete, it is saved to a deployment descriptor file. You can apply the deployment descriptor file on any computer where the wizard is installed.
More information: Initial configuration wizard
Multitenancy
Tivoli Netcool/OMNIbus supports multitenant configurations where events for multiple organizations or departments are stored in a single ObjectServer. Restriction filters can be used to ensure that a user sees only those events that are owned by their organization or department
More information: Multitenancy
Reloading multiple probe rules files
A sample SQL procedure named reloadrules_allprobes is provided in the $OMNIHOME/extensions/roi directory. The procedure can be used to request multiple probes that have their HTTP interface enabled to reload their rules files. The status of each reload is written to a probe management log file. This facility is useful when you change the rules files for several probes and you want to implement all the changes at the same time.
More information: Reloading multiple probe rules files
Probe registration
Probe registration is supported by default in a multi-tiered deployment. When a probe connects to the ObjectServer, it registers information about itself in the registry.probes table. The V8.1 of the table is persistent as opposed to the virtual table in V7.4.
New command line utility nco_rules_util
A new command line utility nco_rules_util is available to analyze rules files and list all of the included files, as well as calculate a checksum for a rules file and/or its combined set of included files.
Improved functionality: probe command port SSL configuration
The configuration of the SSL certificate for a probe command port has been made consistent with the configuration of an SSL certificate for the ObjectServer.
Support on 64-bit operating systems
64-bit support has been extended to AIX® in the V8.1 release for Tivoli Netcool/OMNIbus server components. Every native application that is shipped with the server components is now a 64-bit application. Compatibility with previous, 32-bit applications is provided. All clients from previous versions can connect to a 64-bit ObjectServer. A 32-bit event list can display events that are in a 64-bit V8.1 ObjectServer. A 64-bit JRE is shipped. New directories are provided for binary files, libraries, and modules. These directories are listed in the following table, with the equivalent directories for a 32-bit Tivoli Netcool/OMNIbus system.
Table 1. 64-bit directories and 32-bit directories for Tivoli Netcool/OMNIbus binary files, libraries, and modules
64-bit directory 32-bit directory
$NCHOME/platform/arch/bin64 $NCHOME/platform/arch/bin
$NCHOME/platform/arch/lib64 $NCHOME/platform/arch/lib
$NCHOME/platform/arch/module64 $NCHOME/platform/arch/module
$NCHOME/omnibus/platform/arch/bin64 $NCHOME/omnibus/platform/arch/bin
$NCHOME/omnibus/platform/arch/lib64 $NCHOME/omnibus/platform/arch/lib
$NCHOME/omnibus/platform/arch/module64 $NCHOME/omnibus/platform/arch/module
$NCHOME/omnibus/platform/arch/probes64 $NCHOME/omnibus/platform/arch/probes
64-bit probe binary files are installed into $NCHOME/omnibus/platform/arch/probes64. A 64-bit JRE is installed into $NCHOME/platform/arch/jre_1.6.7.
Note: any does not provide 32-bit operating system libraries for Linux® x86_64 operating systems. Probes and gateways, and other products such as IBM Tivoli Network Manager IP Edition, might need 32-bit libraries. Before you install such components or products, ensure that the required 32-bit libraries are on the operating system.
On 64-bit operating systems, the ObjectServer can become greater in size than the process limit for 32-bit applications. Database sizes are the same for 64-bit as 32-bit. The performance of Tivoli Netcool/OMNIbus V8.1 on 64-bit operating systems is comparable to the performance of the product in V7.3.1, on 32-bit operating systems.
Reports for Tivoli® Common Reporting
A set of event reports that can be viewed in IBM® Tivoli Common Reporting is provided. These reports are based on the reports that were released previously on the IBM Integrated Service Management Library website. The reports display information about the events in the ObjectServer in various graphical formats. Examples of the information you can display include the number of events by severity and day, over a date range, for particular criteria. You can also display the entities, probes, locations, and so on, that generated the most events over a defined period. Use the reports to identify which parts of your network require attention or remedial action, or to monitor the response times of network operators to events. The reports are supported by the Tivoli Netcool/OMNIbus Gateway Configuration Scripts (Reporter Mode), Tivoli Common Reporting V2.1 or later, a relational database, and the Gateway for JDBC.
More information: Importing event summary reports into Tivoli Common Reporting and Tivoli Common Reporting reports for Tivoli Netcool/OMNIbus.
Resolved from fix pack 1DisableDetails property for probes
A new property, DisableDetails is added to probe properties files. When the property is set to 1, probes omit alert details, that is INSERT statements to the alerts.details table, when alerts are sent to the ObjectServer. Equivalent command-line options are also added.
More information: Common probe properties and command-line options.
Resolved from fix pack 1Process agent enhancements
The following command-line options are added to the process agent daemon, nco_pad, that replace existing command-line options. The replaced command-line options are deprecated. The following table lists the new options and shows which deprecated options they replace.
Table 2. New process agent command-line options and deprecated equivalents
New command-line option Deprecated command-line option
-maxlogfilesize -logsize
-messagelevel -debug
-messagelog -logfile
Support for properties files is added to the process agent. Equivalent properties are provided for all command-line options. A default properties file is in $OMNIHOME/etc/nco_pa.props. In the file, all properties are disabled by default. Instead of entering multiple options when you run the nco_pad command, use the new single -propsfile command-line to enforce the settings that are specified in the file.
Restriction: The following properties do not support environment variables in paths: ConfigFile, PropsFile, RedirectFile, and TicketDir. If you define a path for these properties that contains an environment variable, the property does not work as expected. The following example does not work:
ConfigFile: '$OMNIHOME/etc/nco_pa.conf'
Instead, use a path like the following example:
ConfigFile: '/opt/IBM/tivoli/netcool/omnibus/etc/nco_pa.conf'
More information: Process agent properties and command-line options.
Resolved from fix pack 2Support on Red Hat® Enterprise Linux 7 and SUSE Linux Enterprise Server 12 operating systems
Operating system support has been extended to Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12 in the V8.1 fix pack 2 release of Tivoli Netcool/OMNIbus.
More information: Supported operating systems.
Resolved from fix pack 2New scala_itnm_configuration.sql file in $NCHOME/omnibus/extensions
The scala_itnm_configuration.sql file supports integrations between Tivoli Netcool/OMNIbus, IBM Operations Analytics - Log Analyzer, and Network Manager when the Network Manager Insight® Pack is used. The file needs to be run using the nco_sql utility (which is used for applying SQL files to the ObjectServer), as follows:

./nco_sql -user root -password <myp4ss> -server NCOMS < /opt/IBM/tivoli/netcool/omnibus/extensions/update81to81fp2.sql

More information: http://www-01.ibm.com/support/knowledgecenter/SSTPTP_1.3.0/com.ibm.netcool_ops.doc_1.3.0/soc/topo_search/task/soc_ts_configuretoposearch.html.

Resolved from fix pack 2New ParentIdentifier column in ObjectServer alerts.status table
The ParentIdentifier column is required for the Event Analytics component to work. It is used to correlate events in parent-child relationships, which can be viewed in the Event Viewer.
More information: alerts.status table.
Resolved from fix pack 4Device counter extension
The device counter extension provides a utility to automatically track the number of unique end points from which Tivoli Netcool/OMNIbus receives events.
More information: Enabling the device counter extension.
Resolved from fix pack 4Scope-based event grouping updates
The following enhancements were added to the scope-based event grouping extension:
  • Support for multitiered environments
  • Ability to specify the QuietPeriod in the event
  • Template Probe rules and IBM Tivoli Netcool/Impact policy to help users implement custom scope-based event grouping
More information: Enabling scope-based event grouping.
Resolved from fix pack 4 Probe store-and-forward supports ObjectServer schema changes
In Fix Pack 4 and later, the probe store-and-forward mode can handle certain changes between the ObjectServer schema and the data stored in the store-and-forward file.
More information: Store-and-forward mode for probes.
Resolved from fix pack 4SNMP data type conversion functions added
The following SNMP conversion functions were added to the Tivoli Netcool/OMNIbus Probes library:
  • decimaltoascii
  • decimaltohex
  • hextimetostring
  • hextoascii
  • hextodecimal
More information: SNMP conversion functions.
Resolved from fix pack 4String expressions can now be used for regular expressions in rules files
The ability to use string expressions as regular expressions in the extract(), regmatch(), and regreplace() functions was added. Previous levels only allowed the use of string literals for regular expressions.
More information:
Resolved from fix pack 5Increased trigger CodeBlock size
The size of the trigger CodeBlock has been increased to 32768 bytes (32 KB). The related error message when the limit is exceeded has also been added.
More information: catalog.triggers table and E-OBX-102-016.
Resolved from fix pack 5Automated housekeeping tasks
Several useful housekeeping tasks have been automated using triggers to help with common optimization tasks that would otherwise need to be run manually.
More information: Automating housekeeping tasks.
Resolved from fix pack 7ObjectServer can check for user name in password
You can set the ObjectServer to reject passwords that contain user names. By default, the ObjectServer permits passwords to contain user names. The PasswordFormat property includes the contains username field which can be changed to set up checking for user names in passwords.
More information: Configuring the ObjectServer for user authentication and ObjectServer properties and command-line options.
Resolved from fix pack 7Scope-based event grouping
  • Updating scope-based event grouping.
To avail of the most current scope-based event grouping functions, you can update scope-based event grouping configurations.
More information: Updating scope-based event grouping.
  • Modifying behavior of the grouping function.
Scope-based event grouping includes configurable properties that allow for the modification of the behavior of the grouping function and also the appearance of the synthetic containment events.
More information: Scope-based event grouping properties.
Resolved from fix pack 8Scope-based event grouping
This fix-pack adds the following functions to scope-based event grouping automation.
The scope-based event grouping automation is now extended to also clear childless synthetic parents created by the analytics-based event grouping.
The scope-based event grouping is now updated to allow a user to modify the ScopeIDParent summary text in relation to the number of affected subgroups present. Previously it was hardcoded to say X sites affected. Customers use different things to subgroup by, which are not necessarily sites. This additional property allows users to specify the label, other than site. The new property is called SEGScopeIDSitesAffectedLabel and has a default value of site.
The scope-based event grouping automation creates journal entries with the underlying children events' details in them. Previously it did this function only for synthetic parent events created for scope-based event grouping. This function is now extended to also perform the same journaling function for the synthetic parent events created by the analytics-based event grouping.
The following two properties control whether OwnerUID and OwnerGID propagate from parent events to child events, or not.
  • SEGPropagateOwnerUID
  • SEGPropagateOwnerGID
A 0 means that it does not, and a 1 means that it does. This enhancement adds a third value. A value of 2 for SEGPropagateOwnerUID means that it propagates only OwnerUID if the child event is not owned by anyone, the child has an OwnerUID of 65534 (Nobody). Similarly, a value of 2 for SEGPropagateOwnerGID means that it propagates only OwnerGID if the child event is not owned by any group, the child has an OwnerGID of 0 (Public). This function also applies to any groups created by the Event Analytics based event grouping.
Resolved from fp 9This fix pack is an accumulative fix pack release and addresses some APARs and internally found issues.
When you download the fix pack from IBM Fix Central, you get details about the content in the fix pack.
Resolved from fix pack 10Ability to define array, table & registertarget statements anywhere in a probe rules file
Array, table & registertarget definitions are no longer restricted to the beginning of a probe rules file. Now, you can add these definitions, where it is appropriate to do so. For example, an array can be defined in the middle of a block of rule processing statements, immediately before use. Also, it is now possible for a file that contains a definition to be included multiple times in the set of rules that are read by a probe. For more information about probe rules files, see the 'Probe and Gateway' documentation.
Increased limit in the MIB Manager utility to generate SNMP traps.
As you complete steps in the Generating SNMP traps topic, in the Number of Traps field, you can specify the number of traps that can be generated.
Function introduced in Fix Pack 12Audit SQL that is submitted by users in specified groups.
To do audit trail of all SQL commands from prescribed user groups, use the new properties that are delivered with this fix-pack.
More information: Defining and following an audit trail.
Function introduced in Fix Pack 12SSL/TLS certificate sharing.
Two or more Tivoli Netcool/OMNIbus processes can share a certificate by using a new property.
More information: Sharing certificates.
Function introduced in Fix Pack 12SSL/TLS certificate validation accepts host name and domain name in common name attribute.
With nc_gskcmd or iKeyman, it is now possible to use a fully qualified domain name or wildcard domain name as the common name attribute value.
More information: Requesting a server certificate from a CA.
Resolved from fix pack 15Disable ciphers per SSL/TLS protocol.
In response to security vulnerabilities, you can disable specific ciphers per SSL/TLS protocol.
More information: Disabling SSL/TLS ciphers per protocol..
Resolved from fix pack 15Probe restart after column drop in alerts.status.
With Tivoli Netcool/OMNIbus v8.1. Fix Pack 8 or later, probes now are resilient to field drops on alerts.status, and no longer require a restart or removal of SAF files.
More information: DROP COLUMN.
Resolved from fix pack 16Fix Pack 16 is an accumulative fix pack release and addresses some APARs and internally found issues.
When you download the fix pack from IBM Fix Central, you get details about the content in the fix pack.
Resolved from fix pack 17Fix Pack 17. Support for conversions for time (UTC) fields has been added.
For a specific time field with a value such as 0 a conversion text such as Unknown or Not Set could be defined via the alerts.conversions table. Conversions for time/UTC fields are now also supported by the Administrator GUI.
More information: Creating and editing conversions and Display of UTC (time) fields.
Resolved from fix pack 17Fix Pack 17. Scope-based grouping enhancements.

If you have entitlement to Tivoli Netcool/OMNIbus as part of Netcool® Operations Insight, you can apply Netcool Operations Insight Related Event grouping to scope-based grouping groups to create super groups. The scope-based grouping automation’s now support the automatic propagation of the child event details to the super parent journal, so that the super parent will have all the underlying child event details, when ticketed.

The scope based grouping automation's roll up multiple child events into single journal entries in the parent event.

More information: About scope-based event grouping.
Resolved from fix pack 17Fix Pack 17. Tivoli Netcool/OMNIbus v8.1 Fix pack 17 uses Java™ 8.
In Tivoli Netcool/OMNIbus v8.1 Fix-Pack 17, the Java version is updated from Java 7 to Java 8.
More information: JRE requirements and Configuring the JRE for FIPS 140–2.
Functionality delivered in fix pack 26 Fix Pack 26 is an accumulative fix pack release and addresses some APARs and internally found issues.
In Tivoli Netcool/OMNIbus v8.1 Fix pack 26, the following components are updated:
  • libxml2 is updated to version 2.9.11.
  • JRE for Tivoli Netcool/OMNIbus v8.1.0 is updated to IBM JRE 8.0 SR6 FP30 on Solaris systems and IBM JRE 8.0 SR6 FP31 on AIX, Linux, zLinux, and Microsoft Windows systems.
  • IBM JDBC driver is updated to jConnect for JDBC 6.05 - IBM Netcool Build 8.1.0.26-JCON_V8.1.0_1.
In Tivoli Netcool/OMNIbus v8.1 Fix pack 26, the database schema, gateway maps, and table replication definitions for Web GUI and Dashboard Application Services Hub configuration data are provided. This is to facilitate the option of using an ObjectServer failover pair for Web GUI and Dashboard Application Services Hub high availability (HA).
Functionality delivered in fix pack 27 Fix Pack 27 is an accumulative fix pack release.
In Tivoli Netcool/OMNIbus v8.1 Fix pack 27, the following components are updated:
Functionality delivered in fix pack 28 Fix Pack 28 is an accumulative fix pack release.
In Tivoli Netcool/OMNIbus v8.1 Fix pack 28, the following components are updated:
Functionality delivered in fix pack 29 Fix Pack 29 is an accumulative fix pack release.
Fix Pack 29 is an accumulative fix pack release and addresses some APARs and internally found issues. Details about APAR fixes are listed in the README that accompanies a downloaded installation.
  • No new features are added in Fix Pack 29.
  • Support is added to run Tivoli Netcool/OMNIbus 8.1.0 on AIX 7.3.
  • The JRE for Tivoli Netcool/OMNIbus 8.1.0 is updated to the following fix pack levels:
    • IBM JRE 8.0 SR7 FP5 on Solaris systems.
    • IBM JRE 8.0 SR7 FP6 on AIX, Linux, Linux for System z and Microsoft Windows systems.
  • The Jetty libraries, included in the MIB Manager component, are updated to Jetty 9.3.29.
Functionality delivered in fix pack 30 Fix Pack 30 is an accumulative fix pack release.
Fix Pack 30 is an accumulative fix pack release and addresses some defects and internally found issues. Details about fixed defects are listed in the README that accompanies a downloaded installation.

For the full list of updates and fixes, refer to the fix pack README: https://www.ibm.com/support/pages/node/6600029

Functionality delivered in fix pack 31 Fix Pack 31 is an accumulative fix pack release.
Fix Pack 31 is an accumulative fix pack release and addresses some defects and internally found issues. Details about fixed defects are listed in the README that accompanies a downloaded installation.
  • The JRE bundled with Tivoli Netcool/OMNIbus V8.1.0 is updated to the following versions on specific platforms.
    • IBM JRE 8.0 SR8 on Solaris systems.
    • IBM JRE 8.0 SR8 FP5 on AIX, Linux, Linux on zSystems, and Microsoft Windows systems.
  • The version of libxml2 included in Tivoli Netcool/OMNIbus 8.1.0 is updated to version 2.10.3.
  • The ICU data library is updated to version 55.1.3, to support the restoration of Daylight Saving Time in Egypt, plus all other time zone rule changes through to April 2023. The complete list of changes are listed in Known Issue DT206838.
  • No new features are included.

For the full list of updates and fixes, refer to the fix pack README: https://www.ibm.com/support/pages/node/6600029

Functionality delivered in fix pack 32 Fix Pack 32 is an accumulative fix pack release.
Fix Pack 32 is an accumulative fix pack release and addresses some defects and internally found issues. Details about fixed defects are listed in the README that accompanies a downloaded installation.
  • The JRE bundled with Tivoli Netcool/OMNIbus V8.1.0 is updated to IBM JRE 8.0 SR8 FP20.
  • The GSKit version is upgraded to GSKit 8.0.55.24. This upgrade addresses potential security issues and adds support for TLS 1.3. For more information about enabling TLS 1.3 support in Tivoli Netcool/OMNIbus, see Enabling TLS 1.3 support.

For the full list of updates and fixes, refer to the fix pack README: https://www.ibm.com/support/pages/node/7005023

Functionality delivered in fix pack 33 Fix Pack 33 is an accumulative fix pack release.
Fix Pack 33 is an accumulative fix pack release and addresses some defects and internally found issues. Details about fixed defects are listed in the README that accompanies a downloaded installation.
  • The JRE bundled with Tivoli Netcool/OMNIbus V8.1.0 is updated to IBM JRE 8.0 SR8 FP30.

For the full list of updates and fixes, refer to the fix pack README: https://www.ibm.com/support/pages/node/7106820

Web GUI component

Items that are preceded by a fix pack graphical cue (for example, Web GUI component Resolved from fix pack 1) indicate a function or feature that is only available in the specified fix pack and later fix packs. The function or feature is not present in the base version of the product.

Jazz® for Service Management (Jazz SM)
For information about supported versions of Jazz SM and Dashboard Application Services Hub, see Web GUI installation prerequisites.
Event search
Event search uses the search and analysis capability of IBM Operations Analytics - Log Analysis to provide insight into Tivoli Netcool/OMNIbus events. Operations Analytics - Log Analysis is installed independently of the Web GUI component. When the Operations Analytics - Log Analysis feature is selected at installation time you will be asked to provide your Operations Analytics - Log Analysis system information. If the Operations Analytics - Log Analysis host provided does not exist a warning message will be displayed but the installation of the Web GUI will continue and Operations Analytics - Log Analysis can be installed at a later time.
Event search requires the following components:
  • IBM Operations Analytics - Log Analysis V1.2 (or later)
  • IBM Tivoli Netcool/OMNIbus Web GUI V8.1 (or later fix packs)
More information: http://www.ibm.com/support/knowledgecenter/en/SSTPTP_1.4.0.3/com.ibm.netcool_ops.doc/soc/event_search/concept/soc_es_overview.html.
Resolved from fix pack 5 In V8.1 releases prior to fix pack 5, you can perform an historical event search using right-click tools in the Event Viewer. These tools launch out into an external IBM Operations Analytics - Log Analysis server, and run a search using parameters related to the selected event. With V8.1 fix pack 5, a new integrated event search feature allows you to perform historical event searches from within Web GUI itself. For more information, see Integrated event search.
Tools on non-Java applet Event Viewer
You can run SQL tools, CGI tools, and Script tools from the Event Viewer without any browser plugin requirement.
Command tools do not appear on the Event Viewer tools menu by default, and do require a browser plugin to run. A custom Web GUI Tool Launch plugin is available to execute command tools from the Event Viewer.
For information on how to install the custom plugin: Configuring command tools
Note: Where possible, the use of server side tools is recommended over command tools due to the browser plugin requirement.
New UI to configure Data Sources in Web GUI
You can use the Data Sources page to create a new data source, modify or copy an existing data source, or delete a data source. Care should be taken when modifying or deleting existing data sources that are already in use, since this could affect the functionality for current users.
More information: Creating or modifying data sources
System Health Dashboard
The Netcool Health dashboard is a Web GUI dashboard that displays Tivoli Netcool/OMNIbus self-monitoring data. The dashboard is divided into three panels to display status gauges for ObjectServer health, status gauges for client and application health, and self-monitoring event details. When you select a gauge in the Tivoli Netcool/OMNIbus ObjectServer Health or Netcool Client and Application Health panels, the associated self-monitoring events are displayed in the Status Events panel.
More information: Netcool Health dashboard
Defining prompts and metrics
You can use new pages to configure metrics and tool prompts. Metrics are the measurements used to determine a quantifiable value from tables or properties in the ObjectServer. Metrics determine the data that is displayed on gauges. Prompts are included in tools and are displayed as dialog boxes that require input from operators after tools are executed.
More information: Defining prompts and Defining metrics
New Metrics data set in the Web GUI data provider
You can populate Dashboard Application Services Hub gauge widgets with the value of a Web GUI metric. For a specified Web GUI metric, relevant data is retrieved from the data source to calculate and provide the metric value.
More information: The Web GUI data provider
Resolved from fix pack 1Enhanced browser support
Support is added for the Safari browser.
More information: Web GUI browsers, JREs, and mobile devices.
Resolved from fix pack 1Enhanced default view in event lists
A new default view is provided for the Event Viewer and Active Event List, which includes the FirstOccurrence field. This enhancement make it easier to use the integration with the IBM SmartCloud® Analytics - Log Analysis product. The event data queries that run when you run the event management tools are calculated from the value of the FirstOccurrence field. To add the FirstOccurrence field to views, copy the view that is in WEBGUI_HOME/etc/default, use the View Builder, or the WAAPI client.
More information: http://www-01.ibm.com/support/knowledgecenter/SSTPTP_1.2.0/com.ibm.netcool_ops.doc_1.2.0/soc/event_search/reference/soc_es_ael_tools.html.
Resolved from fix pack 1Support for IBM SmartCloud Analytics - Log Analysis V1.2.0.3 and later
The scala.version property is added to the WEBGUI_HOME/etc/server.init file. This property specifies which version of the Support for IBM SmartCloud Analytics product is used in your environment. Because of differences in the search syntax that are used in V1.2.0.3 and previous versions of the product, you need to explicitly state which version is used so that the syntax of search queries is correct. In V1.3, the product is renamed to IBM Operations Analytics - Log Analysis
More information: server.init properties.
Resolved from fix pack 1Creating a watch list
You can move selected alerts to temporary watch lists based on one or more alert fields. A watch list map displays a user's own watch lists and any associated with groups that a user belongs to.
More information: Creating a watch list and Managing events in the Event Viewer.
Resolved from fix pack 1Filtering events by keywords
In the event list, type any text string in the toolbar text box and the event list is filtered accordingly.
More information: Managing events in the Event Viewer.
Resolved from fix pack 2Enhanced functionality in the Event Viewer
New features are provided for monitoring and managing events in the Event Viewer. The Event Viewer portlet can be configured to display events from more than one data source in the same event list. You can apply a different view from the drop-down list of views on the toolbar, add a journal entry for an event, or display the full set of data for multiple events, as well as other enhancements.
More information: Managing events in the Event Viewer and Setting Event Viewer widget preferences.
Resolved from fix pack 3Creating quick filters in the Event Viewer
You can use quick filters as a fast way of displaying events that match a selected criteria. For example, you can quickly display only those events that occurred at the same time as, or before, a selected event. A Quick Filter Builder lets you create customized quick filters. Any filters that are applied to the Event Viewer are displayed as buttons on a filter strip above the event list. Creating multiple quick filters does not replace any filters applied, but are combined with them, so that only events matching all of the quick filter conditions are shown.
More information: Creating quick filters.
Resolved from fix pack 3Workspace preferences in the Event Viewer
You can customize style, layout, and localization preferences in the Event Viewer. The preferences window is accessed via the button on the menu bar or the SHIFT-P keyboard shortcut.
More information: Setting the appearance and behavior of the Event Viewer.
Resolved from fix pack 3Event Viewer status bar
An enhanced status bar in the Event Viewer provides access to current status and to context information for the events including an interactive refresh timer. You can enable the status bar in the Event Viewer widget preferences.
More information: Setting Event Viewer widget preferences.
Resolved from fix pack 3Event Viewer toolbar configuration
Show and hide individual elements of the Event Viewer toolbar, as well as the whole toolbar itself, when configuring the Event Viewer widget.
More information: Setting Event Viewer widget preferences.
Resolved from fix pack 3Define access criteria for new tools based on fields other than class
You can build access criteria conditions when creating a tool by selecting the field options against which the tool can be run. Corresponding value options and comparator operators can also be applied.
More information: Defining tools.
Resolved from fix pack 3Keyboard shortcuts in the Event Viewer
Use keyboard shortcuts to access menu items and execute tools in the Event Viewer.
More information: Managing events in the Event Viewer.
Resolved from fix pack 4New Web GUI installation prerequisites
Installation Manager V1.8.2.1 or later is required before V8.1 fix pack 4 installation. Installation Manager V1.8.3.0 is packaged with refresh installers.
IBM WebSphere® SDK Java Technology Edition V7.0.x is now required for Web GUI V8.1 fix pack 4.
More information: Web GUI installation prerequisites.
Resolved from fix pack 4Change the order of columns in the Event Viewer or lock columns to the grid.
You can drag columns to a new position in the Event Viewer or perform custom sorting within columns. These features must be enabled in Console Settings > User Preferences for Tivoli Netcool/OMNIbus Web GUI > Event List Configuration. You can also lock columns that you want to always display when you scroll horizontally. This setting is in Event Viewer > workspace preferences.
More information: Managing events in the Event Viewer and Setting the appearance and behavior of the Event Viewer.
Resolved from fix pack 4Enable notifications for alerts in the Event Viewer
You can enable flashing, pop-up messages, or sound alerts as notifications in the Event Viewer. In Workspace Preferences, select Enable Notifications in addition to your preferred notification method.
More information: Setting the appearance and behavior of the Event Viewer.
Resolved from fix pack 4Web GUI maps without Java applets
Web GUI maps can now be displayed without Java applets by setting a new portlet preference called Rendering Options.
More information: Setting preferences for the Map portlet.
Resolved from fix pack 5Integrated event search
The integrated event search feature between Tivoli Netcool/OMNIbus Web GUI and IBM Operations Analytics - Log Analysis requires a Netcool Operations Insight license. When the event search with Operations Analytics - Log Analysis feature is installed and enabled (scala.integratedsearch.enabled=true), an Event Search tab is visible when the event information window is opened. With integrated event search you can quickly determine if a particular event is a recurring problem, without having to launch out into the external Operations Analytics - Log Analysis system. Additionally, you can find out if a particular node or type of event has an underlying problem that is causing noise in your environment. Web GUI queries the Operations Analytics - Log Analysis system to run the historical event query, and then renders the results in a chart within the Web GUI interface.
The following properties have been added to the WEBGUI_HOME/etc/server.init file: scala.integratedsearch.enabled, scala.password, and scala.user.
For more information and prerequisites, see: Integrated event search and Event Search charts. For more information about the new server.init properties, see: server.init properties.
Some additional steps must be performed to enable the Event Search tab in the Event Viewer event information window. For more information, see Configuring an SSL connection to IBM Operations Analytics - Log Analysis and Encrypting scala.password in server.init properties.
Resolved from fix pack 5Enhancement to non-Java map
The non-Java (lightweight) map has been enhanced to provide support for monitor boxes (histogram and lavalamp styles). These have been updated with a new look and feel, and allow for the customization of displayed attributes. The lightweight map can also be displayed using Smartpage commands (Maplet and FilterPage), in addition to being launched by direct URL.
More information: Setting preferences for the Map portlet and SmartPage command reference.
Resolved from fix pack 6Web GUI Event Dashboard in lightweight mode
The existing Event Dashboard uses a Java applet when viewing the dashboard, and also when an administrator is editing the dashboard widget preferences. The new lightweight feature allows operators to view a dashboard, and administrators to create and edit a dashboard without the need for Java applets. Lightweight mode is enabled via settings in the Web GUI server.init file (dashboard.edit.render.mode and dashboard.render.mode).
More information: Visualizing event information on Event Dashboards and Setting Event Dashboard widget preferences and defaults.
Resolved from fix pack 6IBM Design Language theme support for Web GUI visualizations
The following visualizations in Web GUI now support the IBM Design Language theme in Dashboard Application Services Hub:
  • Event Viewer
  • Lightweight Event Dashboard
  • Lightweight Map
Resolved from fix pack 7This fix pack is an accumulative fix pack release and addresses some APARs and internally found issues.
When you download the fix pack from IBM Fix Central, you get details about the content in the fix pack.
Function delivered in wb fp8This fix pack is an accumulative fix pack release and addresses some APARs and internally found issues.
When you download the fix pack from IBM Fix Central, you get details about the content in the fix pack.
Event Viewer performance improvement with the Dashboard Application Services Hub CURI runtime environment.
For optimal performance with the Dashboard Application Services Hub CURI runtime environment, configure gzip compression.
More information: Managing events in the Event Viewer
Configure number of events per request in the Event Viewer.
This configuration allows more events to be stored in the Event Viewer and lowers the number of requests that need to be made to retrieve new data.
More information: Setting the appearance and behavior of the Event Viewer, scroll to Configure Event Table preferences.
Start Map Editor with Java Webstart.
Use Java Webstart to start Map Editor as applet support is being deprecated by browsers. This new function runs Map Editor outside the browser.
More information: server.init properties, scroll to the map.editor.mode property.
Usability improvement in the Filter Builder GUI, within the basic filter tab.
When Administrators use the Filter Builder in basic mode, they can choose from the drop-down list of auto populated values.
More information: Creating and editing filters in basic mode.
Start local tools in the Event Viewer.
Due to growing security concerns over plug-ins and the end of support for NPAPI plug-ins in Firefox browsers, Fix Pack 9 replaces the Web GUI Tool Launch plug-in with new function that allows users to download a tool command file and run it manually.
More information: Starting command tools.
Function delivered in wg fp10Link custom help pages to the Web GUI widgets.
The Web GUI administrator can configure a Web GUI widget to link to a custom help page.
More information: Configuring custom help for Web GUI widgets.
Function delivered in wg fp13Enable client side event handling in the Event Viewer
By default, the client has a small subset of events locally. This default setup means that any operations which require more event data (scrolling, filtering, sorting), can require time consuming calls to the server. If you want to reduce the load on your web browser you can either configure the new parameter eventviewer.data.provider.mode within WEBGUI_HOME/etc/server.init, or you can enable the Event Viewer widget preference Use CURI mode for events.
More information: server.init properties and Setting Event Viewer widget preferences
Function delivered in wg fp13Web GUI to ObjectServer connectivity can use TLS
You can enable TLS without a requirement for FIPS. To enable TLS, go to the WEBGUI_HOME/etc/server.init initialization file and update the webtop.ssl.protocol property.
More information: server.init properties
Function delivered in wg fp13To change ObjectServer password setting in Web GUI use a public REST API.
This password setting applies to the Web GUI to ObjectServer connection, in the event feed context.
More information: Example JSON payloads
Function delivered in wg fp13Ability for non-admin users to delete group filters.
To grant a user permission to edit group filters, go to the WEBGUI_HOME/etc/server.init initialization file and update the value for the users.group.filter.mode property.
More information: Filter Builder overview
Functionality delivered in fix pack 14Relationship configuration allows the events to be aggregated across multiple databases.
Events in the Event Viewer can be aggregated across all the data sources.
More information: Defining event relationships
Functionality delivered in fix pack 14Managing events in the Event Viewer has new functions.
In the Event Viewer you can copy a cell and you can use clickable links in a cell
More information: Managing events in the Event Viewer
Functionality delivered in fix pack 35WebSphere Application Server 9.0.5
WebSphere Application Server 8.5.5 is not supported in this Fix Pack. You cannot upgrade directly from WebSphere Application Server 8.5.5 to version 9.0.5. Instead, you can migrate your data from one WebSphere Application Server installation to another.
More information: Migrating from WebSphere Application Server 8.5.5 to WebSphere Application Server 9.0.5