Configure the ICCP Adapter by updating the
$NMS_HOME/etc/system.dat file to include the ICCP Adapter as a system service. There are three 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 ICCP Adapter. Search for IccpAdapter and make sure those lines are uncommented. You must restart the system services in order for the ICCP Adapter to be properly monitored by SMService.
Below is an example of the program section in the system.dat file:
The command line for the ICCP Adapter provides the following options:
The IccpAdapter.prm file is used to configure the operation of the Oracle Utilities Network Management System ICCP Adapter. The default location for this file is the same as where the IccpAdapter binary is located (
i.e.,
$CES_HOME/bin) but it is generally configured to be in a different location by using the
-prm_path <IccpAdapter.prm path>
command line option. Lines in this file beginning with a ";" (semi-colon) are comments. Lines beginning with a "[" (left bracket) are block identifiers (markers). Fields marked as <Required> must be configured for proper operation and are generally site specific. See the IccpAdapter.prm.template file in the standard
$CES_HOME/templates directory for an example IccpAdapter configuration file.
|
|
|
|
|
|
|
|
|
Used for generic configuration of program.
|
|
|
|
|
The IP address(es) of the LiveData Server hostname(s) to connect to. It could be a blank separated list of IP address of several LiveData Servers. In case a failure of connection was detected by the ICCP Adapter with the current LiveData Server, it will traverse the ServerHostname list for the next LiveData Server to connect to.
|
|
|
|
|
Blank separated list of TCP/IP port numbers that the ICCP Adapter will use for a connection attempt to a LiveData Server. Parallel to the ServerHostname, it could be a list of port numbers to use to connect to the corresponding LiveData server in ServerHostname. In case there was a failure of connection with the current LiveData Server, it would proceed to the next entry - in parallel with the next ServerHostname entry. 5002 is typical.
|
|
|
|
|
Time in seconds between periodic transfers of non-time critical data.
|
|
|
|
|
The maximum number of status updates to be sent to DDService at one time.
|
|
|
|
|
Identification number assigned to the SCADA in Oracle Utilities Network Management System with which the ICCP Adapter is communicating.
|
|
|
|
|
Dead band for analog value updates. It is the required percent change from the last reported value to trigger an update.
|
|
|
|
|
Boolean value indicating use of the ANALOG_MEASUREMENTS table.
|
|
|
|
|
Boolean value indicating use of the DIGITAL_MEASUREMENTS table.
|
|
|
|
|
Configurable duration of delay to wait after the LiveData Server instances failed in succession.
|
|
|
|
|
Boolean value indicating use of the controls table for Block 5 functionality.
|
QualityCodeUseOnAssociationTimeOut
|
|
|
|
Quality code that will be sent to DDService when the communication with LD server is lost. A valid QualityCode must be specified if this option is used.
|
|
|
|
|
Normally the adapter will accept and process a stop high level message. This option disables this feature. When this feature is enabled, the adapter will disregard a stop high level message.
|
|
|
|
|
Normally the adapter will process a COV update (one or more open and close sequences within a scan cycle - normally indicating one or more momentaries) and send it to DDService. This option disables this feature.
|
|
|
|
|
The number of VCCs (Virtual Control Centers) that are configured in the LiveData Server.
|
IgnoreCritInterSysServFail
|
|
|
|
Normally the adapter will stop if SMSserivce reports a critical service failure and not restart until services are recovered. This option disables this feature.
|
|
|
|
|
This parameter sets the quality codes that prevent switches from being operated. There is no effect on non-switch statuses.
|
|
|
|
|
If set to true, this will enable Iccp Adapter to interpret data discrete values as three-bit phase encoded statuses. [e.g., A = ‘001’, B = ‘010’, C = ‘100’, etc.]
|
|
|
|
|
If set to 1, then this will set the pseudo flag for the switch entry to be sent to DDService. Generates pseudo (advisory) alarms for ICCP reported device ops rather than actually operating the switches in the Oracle Utilities Network Management System model.
|
|
|
|
|
Number of seconds to wait when attempting to connect ICCP Adapter to the LiveData server. If no connection is received, it will move to the next available LiveData server (if configured). Generally leave as the default.
|
|
|
|
|
Detach the IccpAdapter internal thread that is reading the incoming RTP data stream from Isis. Generally leave as the default.
|
|
|
|
|
Detach the IccpAdapter internal thread that is writing the outgoing RTP data stream from Isis. Generally leave as the default
|
|
|
|
|
Detach the IccpAdapter internal thread that is sending outgoing RTP data stream heartbeat requests from Isis. Generally leave as the default
|
|
|
|
|
E.g., [VCC1]. Provides additional information for each VCC (Virtual Control Center).
|
|
|
|
|
RTP address in LiveData Server for watching and controlling this VCCs association status
|
|
|
|
|
RTP address in LiveData Server for controlling the use of configured ICCP transfer sets
|
|
|
|
|
The total number of transfer sets that are available for use in the VCC. Number must be a multiple of 16.
|
|
|
|
|
The name of the ICCP Association.
|
|
|
|
|
Seconds allowed for restart before the association is considered failed.
|
|
|
|
|
Seconds allowed to restart transferset before the restart is considered failed and no additional restart attempts will be made.
|
TransferSetFailCountReset
|
|
|
|
The number of fail count to be exhausted before marking the transfer set as not alive.
|
|
|
|
|
Maximum number of restart for transfer set.
|
|
|
|
|
Transfer set control mask for the transfer set to be sent to LiveData Server. One T/F flag for each TransferSet. String length must be a multiple of 16.
Example with one TransferSet enabled: "FTTTTTTTTTTTTTTT"
|
|
|
|
|
Assign an Oracle Utilities Network Management System quality to ICCP Validity Quality values
|
|
|
|
|
The value is valid. This is the default (normal) value should virtually always be 0.
|
|
|
|
|
Previous data value has been held over. Interpretation is local.
|
|
|
|
|
Data value is questionable. Interpretation is local.
|
|
|
|
|
|
|
|
|
|
Assign an Oracle Utilities Network Management System quality to ICCP Current Source Quality values.
|
|
|
|
|
Value was received from a telemetered site. This is the default (normal) value should virtually always be 0.
|
|
|
|
|
Value was calculated based on other data.
|
|
|
|
|
Value was entered manually.
|
|
|
|
|
Value was estimated (State Estimator, etc.).
|
|
|
|
|
Assign an Oracle Utilities Network Management System quality to ICCP Normal Value Quality values.
|
|
|
|
|
The point value is that which has been configured as normal for the point. This is the default (normal) value should virtually always be 0.
|
|
|
|
|
The point value is not that which has been configured as normal for the point.
|
|
|
|
|
Assign an Oracle Utilities Network Management System quality to ICCP Timestamp Quality values
|
|
|
|
|
Current value of the TimeStamp attribute contains the time stamp of when the value was last changed. This is the default (normal) value should virtually always be 0.
|
|
|
|
|
Current value of the TimeStamp attribute contains the time stamp other than when the value was last changed.
|
|
|
|
|
Assign an Oracle Utilties Network Management System quality to the non-open/close statuses that can be returned in the two-bit ICCP status field. ICCP "open" is generally (1) and "closed" is (2).
|
|
|
|
|
Quality code to set if the two bit ICCP switch status is reported as "between" (0).
|
|
|
|
|
Quality code to set if the two bit ICCP switch status is reported as "invalid" (3).
|
The IccpAdapter.prm file enables ICCP quality codes to be translated into Oracle Utilities Network Management System quality codes. In the simplest (and default) configuration, all of the ICCP quality codes (except the
Between and
Invalid SwitchStatusQuality codes, which need to be defined to ensure proper operation) are assigned to the 'normal' Oracle Utilities Network Management System quality code (0).
Values of 0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024 may not be assigned as codes for new qualities because they are already defined and used within Oracle Utilities Network Management System. The ‘normal’ Oracle Utilities Network Management System quality code is 0.
The adapter reads the IccpAdapter.prm file only during startup. If the quality code is added when the adapter is running, you must restart the adapter in order for it to recognize the new quality code.
The ICCP Adapter can be dynamically controlled from Oracle Utilities Network Management System by using high-level messages. They can be used any time while running the Oracle Utilities Network Management System ICCP Adapter. The following high-level messages can be used:
Use IccpAdapterService with high-level messages for the Oracle Utilities Network Management System ICCP Adapter. For example: