System information

FCD 901 48
Issue R2A, 07.2009
XMP1 Release 5.5 System Description
Parallel Configuration
Page 6-10 Proprietary Information Aastra
Database to be used.
In case of a connection of a new SOX Client, the SOX Server defines the
authorization level of the SOX Client User and advises the SOX Client
accordingly.
The SOX Server also checks whether a valid dongle (WIBU-KEY) is
available.
SOX Client functions
The SOX Client checks whether the software version used is compatible
with the one used by the SOX Server.
The SOX Client adapts its user interface to the user authorization level
assigned and communicated by the SOX Server.
The SOX Client performs configuration changes. After these changes have
been saved to the Database, the SOX Server will be advised accordingly.
The SOX Server then informs all other SOX Clients on the changes made.
If a SOX Client is advised that another SOX Client has changed the
Database, it will inform its user and offer him a download of the updated
data from the Database.
To send the configuration to the XMP1 network, the SOX Client will apply
for exclusive access. Then the network element settings will be downloaded
from the Database and converted into network element messages. These
messages will be sent to the SOX Server from where they will be passed on
to the individual network elements.
A software download is executed by the SOX Client. For this purpose, the
latter must first apply for exclusive access. The SOX Client generates
network element messages and sends them to the SOX Server.
6.2.2.3 Parallel Configuration
Using the current implementation, several SOX Clients may be able – under
certain circumstances – to execute configuration work simultaneously.
However, normal cases of application provide only
• one terminal for configuration and several terminals for monitoring
purposes.
The "DataBaseServerMode" setting in the configuration file of the
SOX Server determines whether the SOX Clients snynchronize their write
accesses to the database via the SOX Server.
If the DataBaseServerMode adjusted is "Exclusive", only one SOX Client
will get the configuration authorization (one configuration terminal, several
monitoring terminals). "Exclusive" is the default setting for the
DataBaseServerMode. If this setting is changed over to "Optimistic
Concurrency", several SOX Clients will be able - under certain
circumstances - to execute configuration work simultaneously.
All changes made by a SOX Client will be saved to the Database in one
single transaction, i.e. either all changes or none of them will be saved.