In Reporting Mode, these are simply the alerts for which the DeletedAt value is null. This selects alerts from the target database that are considered "open". In Reporting Mode, records which do not exist in the database are treated as new entries, and created as INSERTs, while those which already exist added are treated as UPDATEs.īI - As UNI, but the gateway retrieves the set of existing alerts from the target database first. This is the regular resync supported by the old gateways, and processes alerts as if processing IDUC. UNI - Resynchronisation is in one direction only - from OMNIbus to the target database. The JDBC Gateway has 3 modes of synchronisation, set by the parameter in the gateway.props file. It is a good idea to increase thread count if needed to the point where performance is good enough, then stop. Increasing the thread count may place more burden on the target database however and cause throughput to plateau.
The default count of threads (three) provide good concurrency on most target databases. The gateway generally requires little if any tuning to achieve good performance. As a result, no single type of operation acts as a bottleneck. Thus, the throughput can be scaled up by increasing the number of thread pool threads, up to the scalability threshold provided by the target database. To achieve this, the JDBC gateway splits work up into units to be processed by generic thread pool workers (count configurable using a property). The High Performance Oracle Gateway and subsequent gateways introduced bulk data processing. In addition, the gateway architecture previously only allowed individual record updates and inserts. The JDBC Gateway now combines the functionality of both types of gateways in one. Oracle (native/instant client connections) and non-Oracle (via ODBC). The Netcool Database Gateways have historically come in two database flavours:
In Reporter Mode, all the changes to an alert through its lifecycle in the ObjectServer are stored by amending a single record, using the event's ServerName and ServerSerial values as unique record identifiers.
#History of dbschema update#
In Audit Mode, a new record is created in the database for each ObjectServer record insert, update or deletion transferred by the gateway. The Difference between Audit and Reporter Mode In another departure from older practice, the end user is now expected to have a valid database instance and user configured prior to deploying the script. Newer releases of the Reporter Database Schema creation scripts now have a foreign key reference included to facilitate the removal of linked outdated records and feature improved indexing. DB Schema creation scripts for Audit Mode: Oracle, Sybase, MSSQL, DB2, Informix, MySQL.DB Schema creation scripts for Reporter Mode: Oracle, Sybase, MSSQL, DB2, Informix.Each package comes with the respective scripts to create the required supported database schema and the gateway configuration files - i.e: The database schemas – Audit and Reporter – are created using scripts included in the nco-g-jdbc-reporting-scripts and nco-g-jdbc-audit-scripts packages. The Netcool OMNIbus suite offers two database schemas as default historical database repositories – the Audit Schema and the Reporter Schema, with two corresponding modes for the gateway operation itself.
0 kommentar(er)
