Configure the Generic WebSphere MQ Adapter to run as an Oracle Utilities Network Management System service by updating the
$NMS_HOME/etc/system.dat file to include the Generic WebSphere MQ Adapter as a system service. There are 3 main sections where this service needs to be defined: the service, program and instance sections.
See the
$CES_HOME/templates/system.dat.template file for examples of how to configure the Generic WebSphere MQ Adapter. Search for "
mqseriesgateway" in the file and copy those lines to the
$NMS_HOME/etc/system.dat file. Make sure all lines are uncommented so that they are active. See the command line options section below for more details on available options. You must restart the system services in order to the Generic WebSphere MQ Adapter to properly be monitored by SMService.
Note: In setting up
$NMS_HOME/etc/system.dat, it is important to note that the examples above were presented only for illustration purposes. Parameters may differ on an actual project setting. Coordinate with your Project Engineer in setting up your system configuration file. Also, take note that in the example above, it is assumed that the Generic WebSphere MQ Adapter will reside on the same machine where the Oracle Utilities Network Management System environment resides.
|
|
|
|
|
|
|
Enables the adapter to process area summary requests. The specified control zone level will be used to filter the outage list in the area summary. The default control zone level of 3 will be used when none is specified.
|
|
|
|
Specifies how often the interface will save a timestamp which is used for synchronization on restart. The timestamp is used to go back to that timestamp to know how far back to get events on restart.
|
|
|
|
Enables the adapter to process condition data.
|
|
|
|
Enables the adapter to process customer disconnect / reconnect information.
|
|
|
|
Enables the adapter to process trouble calls.
|
|
|
|
Enables the adapter to process crew outage status changes.
|
|
|
|
Enables crew assignments & dispatches to be sent.
|
|
|
|
Indicates mqseriesgateway to use separate DBService.
|
|
|
|
Enables the adapter to process customer outage history information.
|
|
|
|
Enables the adapter to process customer outage status information.
|
|
|
|
Enables the adapter to modify the customer model.
|
|
|
|
Indicates that mqseriesgateway will only parse the customer update xml messages without modifying in the database. This is for performance testing purposes.
|
|
|
|
Enables the adapter to bundle all sql statements for DELETECREATE/CUSTOMER requests to improve speed.
|
|
|
|
Enables the adapter to write to standard output the debug information.
|
|
|
|
Sets the default account type for customer model.
|
|
|
|
Changes the default get queue name.
|
|
|
|
Writes to standard output, the usage of the adapter.
|
|
|
|
Places incidents information in <PostSrsOutput_001> message. This option is not recommended, because it will greatly degrade the performance of the adapter.
|
|
|
|
Includes picklist info in the SRS output message if it exists.
|
|
|
|
This option should be used with the -synchronize option. It will exclude all complete event from the synchronization messages
|
|
|
|
Removes the supply node list from the <PostSrsOutput_001> and <PostSrsOutputStatus_001> messages to improve performance.
|
|
|
|
This command line will disable the JMService supply node recache.
|
|
|
|
Enables outage updates to be sent.
|
|
|
|
Changes the default put queue name.
|
|
|
|
Enables the adapter to process query statements to the Operations Database.
|
|
<string queue manager name>
|
|
Enables the adapter to use the defined queue manager name instead of NMS_MGR.
|
|
|
|
Enables the adapter to recache JMService for the customer model.
|
|
|
|
This specifies when JMService will re-cache customer info in hours. This will override the -recache option.
|
|
|
|
This specifies when JMService will re-cache customer info in minutes. This will override the -recache option.
|
|
|
|
Enables the adapter to send restore messages containing a list of customers who requested a callback of a restored device.
|
|
|
|
Enables the adapter to process sql statements to the Operations Database.
|
|
|
|
Enables the adapter to process outage status (Restored, complete, cancelled).
|
|
<percent affected> <minimum affected> <maximum affected>
|
|
This specifies that the Generic WebSphere MQ Adapter will send an SRSOutput message that contains a callback list of relatively random sampling of customers downstream of the restored device. Default values: percent affected=30%, minimum affected=10, maximum affected=300. Setting the percent affected alone is valid but setting the maximum affected needs all three parameters to be present.
|
|
|
|
Sends synchronization messages when the adapter starts. This is only required to capture outage event update messages for events that were completed while the interface was down.
|
|
|
|
Enables the adapter to process device names instead of supply nodes index or premise identifiers.
|
|
|
|
Enables the adapter to process premise identifiers instead of supply nodes.
|
|
|
|
Indicates that Style Sheet Processing is used, and the literal path the directory that contains the .xsl files for the adapter.
|
The following table lists and describes command line options to support the bulk load for the customer model createSql process.
In
$NMS_HOME/etc/system.dat, include the MQDBService as one of the services. Use the TCDBService entries as examples of how to set this up.