Primary Netcool/OMNIbus ObjectServer configmap
This topic explains the structure of the configmap for the primary IBM®
Tivoli®
Netcool®/OMNIbus ObjectServer
pod, ncoprimary
, and lists the
data elements that can be configured with this configmap. Edit this configmap to customize, and add
custom automations and triggers to, the primary Netcool/OMNIbus ObjectServer.
Contents
The following table lists the data elements that are contained in the primary Netcool/OMNIbus ObjectServer configmap:
Data elements | Description | More information |
---|---|---|
agg-p-props-append |
Properties that are specified in this data element are appended to the end of the Netcool/OMNIbus ObjectServer properties file on pod restart. | Netcool/OMNIbus 8.1 documentation: Using the ObjectServer properties and command-line options |
agg-p-sql-extensions |
Use this element to add a new SQL extension, such as a trigger or an automation, to the Netcool/OMNIbus ObjectServer on pod restart. | Netcool/OMNIbus 8.1 documentation: ObjectServer SQL |
Examples of each of the data elements in this configmap are provided.
Data element: agg-p-props-append
The following data element appends a
MessageLevel: 'debug'
property to the
.props
file of the Primary
ObjectServer.agg-p-props-append: |
MessageLevel: 'debug'
Data element: agg-p-sql-extensions
The following data element adds a custom database that contains a single table to the primary
Netcool/OMNIbus
ObjectServer.
agg-p-sql-extensions: |
-- create a custom db
create database mydb;
go
-- create a custom table
create table mydb.mytable persistent
(
col1 incr primary key,
col2 varchar(255)
);
go