.This topic describes how Exaquantum/Explorer responds when connections to the Exaquantum server(s) or the network is lost.
Exaquantum/Explorer is a tool that has constant interactions with the Exaquantum server(s), even when it is in Design mode.
When users are viewing key production data in Run mode, it is very important that they are informed immediately if the data they are viewing is no longer being refreshed. This could be due to:
Loss of network connection
Exaquantum servers being shutdown.
The response of Exaquantum/Explorer in its various modes of operation to network connection issues is covered in subsequent sections.
For information on how the Excel Add-in handles connectivity to the Exaquantum server, click on .
Whilst Exaquantum applications (Exaquantum/Explorer and Excel with Exaquantum/Explorer Add-In) are running, the Client PC monitors network connections to the Exaquantum servers by sending a message to the servers every 30 seconds. If after 5 seconds a response has not been received then the Exaquantum applications are notified and users are prompted to take the appropriate action as outlined in this section.
The message from the client is invoked by a timer, therefore the time between when the network was lost and the time at which it was detected by the client could be in the range of 5 to 35 seconds. This is because the network connection could be lost just before or after the message is sent from the client. If the network is lost and then re-established (minimum 5 second loss, maximum 35) the client applications will recover.
If Exaquantum/Explorer is started up when there is no network connection or Exaquantum server available, a pop-up screen appears with option buttons to Retry or Cancel.
Pressing Retry attempts to retry the connection to Exaquantum.
Pressing Cancel abandons the Exaquantum/Explorer session and closes the pop-up.
If the network connection is lost in design or run modes, a pop-up screen appears advising that the network connection with Exaquantum has been lost.
Pressing the OK button on this screen opens another screen prompting you to press option buttons Retry or Cancel.
Pressing Retry attempts to retry the connection to Exaquantum.
Pressing Cancel abandons the Exaquantum/Explorer session and opens a pop-up screen advising you to save any unsaved documents.
Once all document changes are saved (or discarded), the Exaquantum/Explorer session closes.
If the Exaquantum server becomes unavailable or shut down, a pop-up screen appears advising that Exaquantum has shut down.
Pressing the OK button on this screen opens another screen prompting you to press option buttons Retry or Cancel.
Pressing Retry attempts to retry the connection to Exaquantum.
Pressing Cancel abandons the Exaquantum/Explorer session and opens a pop-up screen advising you to save any unsaved documents.
Once all document changes are saved (or discarded), the Exaquantum/Explorer session closes.
At startup in a multi server system, the Client PC will attempt to connect to the Primary Server. If this is unavailable it will attempt to connect to the Secondary Server. If a connection is made to either server, this then becomes the system ‘Master’ server.
If a connection to either the Primary or Secondary Server cannot be made, a pop-up screen appears with option buttons to Retry or Cancel.
Pressing Retry attempts to retry the connections to Exaquantum.
Pressing Cancel abandons the Exaquantum/Explorer session and closes the pop-up.
The Master Server is either the Primary or Secondary Server, depending on which server was available at startup.
If the network connection to the Master Server is lost in design or run modes, a pop-up screen appears advising thet the network connection with Exaquantum has been lost.
Pressing the OK button on this screen opens another screen prompting you to press option buttons Retry or Cancel.
Pressing Retry attempts to retry the connections to the Primary and then the Secondary Exaquantum Servers.
Pressing Cancel abandons the Exaquantum/Explorer session and opens a pop-up screen advising you to save any unsaved documents.
Once all document changes are saved (or discarded), the Exaquantum/Explorer session closes.
If the Exaquantum Master server is unavailable or shut down, a pop-up screen appears advising that Exaquantum has shut down.
Pressing the OK button on this screen opens another screen prompting you to to press option buttons Retry or Cancel.
Pressing Retry attempts to retry the connections to the Primary and then the Secondary Exaquantum Servers.
Pressing Cancel abandons the Exaquantum/Explorer session and opens a pop-up screen advising you to save any unsaved documents.
Once all document changes are saved (or discarded), the Exaquantum/Explorer session closes.
If another server that is part of the multi-server environment (not Master) becomes unavailable whilst the user is designing a new document, then the tree for the related elements in the Data Selector will not be expanded.
If the user is viewing a document in run mode, then the tag values for the unavailable data will default to zero and the quality will become Bad/Unavailable.