Service Engines

An OmniCenter service engine is a specialized deployment of an OmniCenter virtual appliance—on an independent server—that is configured to run only particular OmniCenter services (typically, high volume processing services, such as application traffic flow collection). This offloads the work of performing those resource-intensive services from your main OmniCenter to the service engine. This is of value because the use of a service engine to collect and process data for traditionally high volume tasks can dramatically reduce the processing load of the server on which your main OmniCenter is deployed.

Service engines are managed on the Service Engine Administration pages.

To reduce the load on the main OmniCenter server, all data related to a particular service is collected and processed on an appropriately configured service engine. OmniCenter then queries the service engine through a RESTful API to retrieve the processed data for display in its own UI. The connection between an OmniCenter and a service engine is on-demand—from OmniCenter to the service engine—using a secure question and answer framework.

In the event that your main OmniCenter loses communication with any of its connected service engines, those engines will still continue to collect and process data as long as they can still communicate with the devices they monitor. Once communication with your main OmniCenter is restored, it will be updated with the cached data from the service engine.

If you would like to stop using service engines for a particular service, removing all services of that given type from all connected service engines will cause your main OmniCenter to resume providing that service itself.

The following services are available for activation on a service engine (these are outlined more completely below):

  • OmniCenter Log Collector (OLC)
    This service collects and processes log data.
  • OmniCenter Traffic Collector (OTC)
    This service collects and processes network application traffic flows.
  • OmniCenter Remote Poller (ORP)
    This service collects and processes device performance statistics and monitors host and service availability.
  • OmniCenter Remote Collector (ORC)
    This service performs exactly the same services as an OmniCenter Remote Poller (above), but for devices isolated from the main OmniCenter by a firewall. The service engine running the remote collector service is intended to be deployed inside of that security perimeter, where your main OmniCenter typically cannot initiate a connection. In this case, the connection is initiated by the service engine, which “calls home” every 5 minutes to update your main OmniCenter with all of the collected data it has built up in its cache.

To deploy a service engine, see How to Add a Service Engine to OmniCenter.

As your network grows, you can deploy any number of service engines using additional separate servers.

Updated on October 9, 2019

Was this article helpful?

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support

Leave a Reply