What’s New in the Operations Agent 12.14 Release

by in IT Operations Management

We’re pleased to announce the availability of Operations Agent (OA) 12.14. In this release, we introduced numerous enhancements and optimizations as well as new platform support.

Release Summary

  • New supported operating system versions
  • Network Operation Manager (NOM) integration enhancement
  • OA System Metric Collector resilience
  • BBCUTIL enhancement to show communication security protocol
  • Enhanced documentation
  • Miscellaneous enhancements, fixes and improvements

You will find the release overview in the Operations Agents 12.14 Release notes, from where you navigate through the Operations Agent documentation as desired.

Now let’s talk about new features in more detail.

New Supported Platforms

In this release, we introduced support for the following operating system versions:

  • SLES12 SP5 x64
  • OEL 8 x64
  • CentOS 8 x64
  • CentOS 8.1 x64
  • Debian 10 x64
  • Oracle VM 3.4.6
  • RHEL 8.2 PPCLE
  • RHEL 7.8 x64

For more details on supported platforms and system requirements, check out the latest Operations Bridge support matrices.

NOM Integration Enhancement

In this release, we enhanced the Operations Agent to allow synchronization of all Operations Bridge Manager (OBM) event state changes back to NOM (earlier, it was only possible to synchronize Closed OBM events and you were required to use Operation Connector for the closed event state sync). This enhancement allows you to view event state changes in NOM after the corresponding events (forwarded to OBM) have been updated in OBM.

The following list shows the mapping of lifecycle states of OBM events with the states of the corresponding NNMi incidents:

  • OBM: Open -> Registered
  • OBM: Work on -> In progress
  • OBM: Resolved -> Completed
  • OBM: Close -> Closed

Another improvement to the NOM integration is that you now no longer need to install and configure Operation Connector, which makes the entire setup simpler and faster.

Resilient Monitoring of the Performance Metric Collection

This release introduces a metric collection improvement: earlier, if the oacore metric collection for any collection class stopped, the entire metric collection process had to wait until the problem was resolved. Now, if the metric collection for the FILESYSTEM or DISK classes stops for any reason, the metric collection for those classes is disabled while proceeding with other collection classes. At the same time, the problematic FILESYSTEM or DISK class is being monitored for abnormality and is restarted automatically once the issue is resolved.

Note that if there are problems with the collection classes other than FILESYSTEM and DISK, the entire metric collection process stops until the issue with the affected collection class is fixed. In such a case, you need to manually restart the oacore process.

The resilient monitoring feature is disabled by default. You can activate it by using the COLLECTION_MONITOR configuration variable. For more information, see Configuring the resilient monitoring.

Enhanced bbcutil Command

The bbcutil command (the command that helps you debug a communication server) has been enhanced with the -protocolversion option, which allows you to specify the TLS protocol version to be used for communication.

This new option can help you in troubleshooting problems with the communication server. For more information, see bbcutil.

Miscellaneous Enhancements and Improvements

  • Support for the OA installation from the Agent installation repository in non-default directories on Windows: The new options of the oarepo.ps1 command – -install_dir and - -data_dir – allow you to install OA to custom install and data directories. For more information, see Deploying Operations Agent Using the Agent Installation Repository.
  • Restriction of access to the real-time performance data server: With OA 12.14, real-time performance data server can no longer be accessed remotely from other systems in the environments that run OA (which was the default behavior in earlier OA releases). However, you still have a possibility to explicitly allow access from another systems by adding their hostnames/IP addresses to the authip file. For more information, see Restricting Access.
  • Enhanced OA health monitoring: You can now stop self monitoring of OA health monitoring processes using the -nowatch option of the selfmon_configure.pl script. This option allows you to:
  • Starting from this release, the Operation Agent sends Keep Alive Packets to the server over RPC by default. If you want to enable the ICMP-based packet sending, you can do so by setting the OPC_RPC_ONLY flag to false in the eaagt namespace. Note, however, that the RPC-based approach is firewall-friendly and therefore recommended. For more information, see Config_Variable_Agent.

Documentation Enhancements

In this release, the Troubleshoot section has been enhanced as follows:

  • The troubleshoot content has been standardized by dividing it into Symptom, Cause, and Solution
  • Error messages are now included in the page title for the ease of search

We encourage you to try out our new features and enhancements! For further information on our offerings, visit the Operations Bridge product page, explore our documentation resources and check out our videos and blogs.

If you have feedback or suggestions, don’t hesitate to comment on this article.

Explore full capabilities of Operations Bridge by taking a look at these pages on our Practitioner Portal: Operations Bridge Manager, SiteScope, Operations Connector (OpsCx), Operations Bridge Analytics, Application Performance Management (APM) and Operations Orchestration (OO) documentation!


To get more information on this release and how customers are using Operations Bridge, we are happy to announce the following events:

See all the Micro Focus events worldwide.

Read all our news at the Operations Bridge blog.


Operations Bridge