IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway: Reference Guide
IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway: Reference Guide
IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway: Reference Guide
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Note: After the gateway has started, you can use the nco_sql command to<br />
manually issue commands. For more information about the nco_sql command, see<br />
the <strong>IBM</strong> <strong>Tivoli</strong> <strong>Netcool</strong>/<strong>OMNIbus</strong> Administration <strong>Guide</strong> (SC23-6371).<br />
Table 8 lists the available startup commands.<br />
Table 8. Startup commands<br />
Command Description Syntax Example<br />
SET PROPERTY Use this command to set the value of a SET PROPERTY SET PROPERTY<br />
property in the properties file.<br />
’string’ TO value ; ’Gate.Reader.Debug’ TO<br />
FALSE ;<br />
GET PROPERTY Use this command to return the value of GET PROPERTY GET PROPERTY<br />
a specified property from the properties<br />
file.<br />
’string’ ;<br />
’Gate.Reader.Debug’ ;<br />
SHOW PROPS Use this command to display the current SHOW PROPS ; SHOW PROPS ;<br />
configuration of the gateway by listing all<br />
properties and their values.<br />
go<br />
GET CONFIG Use this command to display the current<br />
configuration of the gateway by listing all<br />
properties and their values.<br />
Note: GET CONFIG is identical to the<br />
SHOW PROPS command and may be<br />
removed from later versions of the<br />
gateway.<br />
TRANSFER Use this command to initiate a data<br />
transfer operation between tables in two<br />
ObjectServers.<br />
Note: You can use a filter condition to<br />
transfer a partial table. If the target table<br />
does not match the source table, a map<br />
can be specified as part of the transfer<br />
operation. This map must be defined in<br />
the map definition file.<br />
FAILOVER SYNC Use this command to synchronize data<br />
between primary and backup<br />
ObjectServers. The command specifies<br />
which master tables are transferred<br />
during the data transfer operation.<br />
Failover Sync example<br />
GET CONFIG ; GET CONFIG ;<br />
go<br />
TRANSFER FROM<br />
sourcetable TO<br />
targettable [VIA<br />
FILTER filtertext]<br />
[WITH DELETE VIA<br />
delfiltertext]<br />
[USING TRANSFER_MAP<br />
mapname] ;<br />
FAILOVER_SYNC [ ADD<br />
’TABLENAME’ TO |<br />
REMOVE ’TABLENAME’<br />
FROM ] WRITERNAME ;<br />
TRANSFER FROM<br />
’master.names’ TO<br />
’resync.names’ VIA<br />
FILTER ’Name !=<br />
\’nobody\’’ DELETE ;<br />
In this example, all records<br />
with the name nobody are<br />
deleted from the<br />
resync.names table and<br />
replaced with<br />
corresponding records in<br />
the master.names table.<br />
See “Failover Sync<br />
example.”<br />
The following is an example of how to use the FAILOVER SYNC command in the<br />
startup command file:<br />
FAILOVER_SYNC ADD ’master.names’ TO ObjectServerA;<br />
FAILOVER_SYNC ADD ’master.groups’TO ObjectServerA;<br />
FAILOVER_SYNC ADD ’master.members’ TO ObjectServerA;<br />
FAILOVER_SYNC ADD ’master.permissions’ TO ObjectServerA;<br />
FAILOVER_SYNC ADD ’master.profiles’TO ObjectServerA;<br />
FAILOVER_SYNC ADD ’tools.actions’ TO ObjectServerA;<br />
FAILOVER_SYNC ADD ’tools.action_access’ TO ObjectServerA;<br />
FAILOVER_SYNC ADD ’tools.menus’ TO ObjectServerA;<br />
FAILOVER_SYNC ADD ’tools.menu_defs’ TO ObjectServerA;<br />
18 <strong>IBM</strong> <strong>Tivoli</strong> <strong>Netcool</strong>/<strong>OMNIbus</strong> <strong>SNMP</strong> <strong>Writer</strong> <strong>Gateway</strong>: <strong>Reference</strong> <strong>Guide</strong>