Aller au contenu principal
Version: v3.6 (Non supportée)

Supervision Options

To configure the supervision options, select the Options... command of the Configuration menu, then, on the displayed dialog box, select the Supervision tab.

Button Data Servers... This button gives access to the list of the DDE and OPC servers that are referred to in the polling list. It allows a list of secondary (redundant) servers to be defined for each referred server (see § 7.2.1 "Secondary DDE Servers"). Button Alias... This button gives access to the definition of alias names for the DDE server and topic names The alias names allow a same name to be used to refer to different servers or topics in redundant configurations (see §7.2.1 "Secondary DDE Servers"). Button OPC Setup... This button gives access to the configuration of the Client and Server OPC interface.

Mediator This group allows the selection of the mediator1 module which will be in charge of the interface with the supervised application. Select in the drop down list the name of the "Mediator" module. By default, there is no mediator selected (choice "-"). To add a mediator to the list, one only have to copy the DDL file of the mediator in the directory of the Alert application, the file name being required to have the format: "M_XXXXXX.DLL, with "XXXXXX" a string identifying the mediator.

  • The Setup button gives access to a dialog box to configure the selected mediator. It is grayed if there is no mediator selected or if the selected mediator does not propose a setup service.
  • The Initialize button commands the reinitialization of the mediator module. It is grayed if there is no mediator selected.
  • The Message processor activation option activates, when checked, a mediator for message processing (message processor). If the message processor is not installed, this option is grayed. When the message p rocessor is active, it can be configured by the command Message processor... in the Configuration menu. Polling parameters
  • The Timeout before start polling value defines the timeout between start -up of the application (with launching of external applicatio ns) and the establishment of the connections with the supervised applications. This timeout allows the completed initialization of external applications to be awaited before soliciting them.
  • The Timeout to restart polling value defines the timeout initiali zed when the connection with an external application is broken before trying to automatically restore it. This timeout will be retriggered until the reestablishment of the connections. If this value is null, there is no automatic reestablishment of the connections.
  • The Timeout on request response value defines the maximum delay for waiting for a response to explicit DDE or OPC requests. These requests are transmitted to all the events to watch, first at the establishment of the connection, then periodically for the events defined with the "periodic request" option. If this timeout is null, requests are done in synchronous mode (blockage while waiting answer).
  • The Polling cycle (Periodic Request) value defines the polling period to read the events set with th e "periodic request" option. At the end of this period, all the events defined with this option are submitted to an explicit DDE or OPC request, to control that the supervised application is still responding.
  • The choice Polling: Always / Only active statio n defines the default polling mode of the station. If the option " Always" is selected, the data servers always establish links with their respective data sources, any is the active status of the station. If the option " Only active station " is selected, t he links are only established when the station is active ("Alert" led in green).
  • The Initial DDE Request on Advise option forces at the connection time an initial request for the DDE type tags declared in polling to recover their current value. This option must be validated if the DDE server of the supervised application does not provide an initial value in return of advise command (the server transmits the value only to the next change).

1 A mediator module is a DLL module which takes charge of the data exchanges between the ALERT software and the supervised application.

It must be invalidated if the DDE server of the supervised application returns incoherent values on an explicit request after starting ADVISE transaction, while the tag value has not been acquired by the server.

  • When the Initial DDE request... option is validated, the Request before Advise option specifies that the DDE request must be performed before the DDE advise.
  • When the Link failure on invalid tag value option is activated, a link failure is set on tags with invalid values despite a successful connection, a bad quality in OPC for example. This parameter can be redefined at the level of each data server and each tag. Server item receiving the event log This option designates an item in an external DDE or OPC server application that will receive the trace of the events logged by ALERT (user login, alarms, acknowledgments ...). This reference can be directly typed or browsed by clicking on the button on the right of the edit field. To disable the event transmission to an external variable, you just have to erase the reference of the defined variable. The events logged by Alert are transmitted to the selected DDE variable under the form: "Event code" <Tab> "Parameters" (See the Event coding table on the following page). Watch Dog item This option defines an item in an external DDE or OPC server application which will be then cyclically written with the value of a counter incremented at each cycle. This item could be tested by the external application to check that its contents changes according to the parameterized cycle, and so control that the alarm manager is still running. This reference can be directly typed or browsed by clicking on the button on the right of the edit field.
  • The Cycle parameter defines the period of the writing cycle of the designated item, in seconds. A null value disables the watch dog processing.
  • The Modulo parameter defines the maximal value of the transmitted counter. When this value is reached, the counter is reset to zero.
  • The Format parameter defines the value which will be written in the designated "watch dog" item. By default the write format contains only the counter value, coded under the form "&C". The format string can include any other numerical or alphanumeric string, and also tab characters that must be coded under the form "&T". To disable the watch dog processing, you just have to eras e the reference of the defined "watch dog" item or to set the write cycle to zero.

Code Parameters Meaning 0 - Application initialization 1 - Application closure 2 <operator> User login 3 <operator> User logout 4 <operator> (<port>:<driver>) Outgoing call for message 5 <operator> (<port>:<driver>) Outgoing call for alarm 6 <operator> Advised operator 7 <operator> Unadvised operator 8 <operator>: <cause> Call failure 9 <alarm message> Alarm 10 <alarm message> / <operator> Alarm acknowledgment 1 11 <alarm message> Alarm reset 12 <operator> / <operator> Call acknowledgment 2 13 <alarm message> Simple event 14 <operator> (<port>) Incoming call 15 <on-call group> Group call succeeded 16 <on-call group> Group call failed 17 <on-call group> (-> <team>) Schedule derogation3 18 <on-call group> End of schedule derogation 19 - System date modified 20 <operator> (<port>) Login from a remote terminal 21 <port> End of communication on a port 22 <port> Port failure (modem) 23 <reference of server or item> Link failure 24 <information> Information message 25 <operator> Operator set off duty 26 <operator> / <substitute> Operator substituted 27 <alarm reference > / <operator> Set of alarm mask 28 <alarm reference> / <operator> Reset of alarm mask 29 <port> Connection established on a port 30 - Alert management deactivation in redundant mode 4 31 - Alert management reactivation in redundant mode 4 32 <operator> End of remote session 33 <error description> Error 34 <operator> Operator set on duty 35 <operator> / <operator> Call denied (negative call acknowledgment) 2 36 Group <G>, team changeover <A> -> <B> / <operator>, max delay <n> minutes Team changeover team A to team B in group G 5 37 Group <G>, team changeover <A> -> <B> Team change over failed team A to team B in group G (timeout expired) 5 38 Group <G>, team <E> / <operator> End on-call time group G team E 39 <operator> -> <status> Change of operator status (availability) Event coding

1 If the acknowledgement is issued from an external application, without identification of operator, the part "/ operator" is omitted. 2 If the call is acknowledged by the called operator himself, the part "/ operator" is omitted. 3 If no team is defined in derogation, the part "(-> team)" is omitted. 4 In redundant mode. 5 If 1st changeover, the part "<A>" is suppressed, if default delay, the part ", max delay..." is suppressed.

To access to the confi guration of the sec ondary DDE servers, select the Options... command of the Configuration menu, then, on the di splayed dialog box, select the Supervision tab. Then click on the Data Servers... button on the top of the page.

This dialog box defines a list of secondary (redundant) servers for each DDE or OPC server referred to in the polling list. In normal time, the DDE and OPC connections are established with the primary servers. In case o f disconnection of a primary server, the connection is automatically reestablished with the first available secondary server in the list of the secondary servers associated with. Primary servers This list displays the list of the DDE and OPC servers which are referred to in the polling list, whether they are on the local station or any network station. The Topic column is used only for DDE servers. The last column displays the number of secondary servers associated with. Secondary servers This list display s the list of secondary DDE and OPC servers associated with the server selected in the list "Primary channels". These servers will be requested, in case of failure of the associated primary server, in accordance with the order defined in the list. Button Add... Click on this button to add a new secondary server in the list of secondary servers associated with the server selected in the list of primary servers. The displayed dialog box allows the selection of a computer (a network station), a server and a topic. Button Edit... Click on this button to modify the definition of the secondary server selected in the list of secondary servers. The displayed dialog box allows the modification of the computer (the network station), the server and the topic.

Button Delete Click on this button to remove the selected secondary server from the list of secondary servers. Buttons and

Use these buttons to respectively move up and down the secondary server selected in the list of secondary servers. The secondary servers are used in accordance with the order defined in the list.

To access to the configuration of the supervision options of the application, select the Options... command of the Configuration menu, then, on the displayed dialog box, select the Supervision tab. Then click on the Alias... button on the top of the page. DDE alias names can be used to replace the server or topic names in a DDE reference name. This allows the same name to be used to reference different servers or topics in redundant configurations.

Server Alias List This list contains the alias names defined for the DDE servers, under the form: <alias name> -> <DDE server> (list of topics attached to the server) Topic Alias List This list contains the alias names defined for the DDE topics, under the form: <alias name> -> <DDE topic> Button Add... Click on this button to create a new server or topic alias (see below). Button Edit... Click on this button to edi t the properties of the alias selected in the server alias list or the

...