System information

FCD 901 48
Issue R2A, 07.2009
XMP1 Release 5.5 System Description
Load Behavior
Aastra Proprietary Information Page 6-11
SOX stores the original Database values. Before any changes will be saved
to the Database, it is checked whether the Database still contains its original
values. Only in this case, the changes will be executed (Optimistic
Concurrency). Otherwise the action and thus the entire "Save" command
will be rejected.
Each modification of the data of a network element will result in a change of
the configuration ID.
This leads to the following situation:
Parallel configuration works are possible provided that these do not affect
the same network elements and the same units at Network Manager level
(circuits, trunks).
6.2.2.4 Load Behavior
SOX Client requests sent to the SOX Server are implemented
synchronously, i.e. the SOX Client will be blocked until it receives an answer
from the SOX Server (Timeout value can be entered in the configuration
file).
SOX Server messages to the SOX Client are implemented asynchronously
both in the SOX Server and SOX Client. Thus, a slow SOX Client cannot
block the SOX Server. The SOX Server advises all SOX Clients
asynchronously in new, separate threads.
The SOX Server checks at regular intervals whether a SOX Client is still
addressable. If a communication error occurred in the connection to the
SOX Client, the SOX Server will deregister the latter.
6.2.2.5 User Interface
In the "Properties" mask of the Area Node, an overview of all SOX Clients
connected will now be displayed.
The "Security" menu offers the following additional items:
Exclusive Access
Apply for exclusive access
Refresh Permissions:
The authorizations of the User may have been changed in the SOX Server.
This menu item permits the SOX Client to update its User Authorizations.