Table of Contents
Advertisement
T H E
C O N C E P T
B E H I N D
T H E
O P E R A ™
C O N T R O L
C E N T E R
2 The Concept Behind the OPERA™ Control
Center
The OPERA™ Control Center consists of two modules which access the
remote controlled OPERA™ systems through remote procedure calls. The
first module is the graphical user interface (GUI), which is used to create
and edit entries in the
. From the command database
command database
the system creates some control files which are handed over to the
. The dispatcher module does the real work and takes
dispatcher module
care of the allocation of all required resources before a test call is issued. It
locks the interfaces which are required for a test call and keeps them locked
throughout the test call. This will effectively block all other commands and
also manual access (e.g. the use of OptiCall™) to theses resources.
Commands which require such a locked resource will be delayed until the
resources are free again. Due to this locking mechanism there may be
several OPERA™ Control Centers and OptiCall™ applications active on the
network.
In order to keep the maintenance of the system easy, there are two different
tables used to form the command database. One contains the description of
the available resources on the network ("Phonebook", see Section 3.2) and
another one consists of the actual test commands ("Commands", see Section
3.3). The first table is used to assign an alias name for each combination of
an OPERA™ system, the chosen interface and the associated telephone
number. The second table then uses these alias names to define the
originator and the terminator of the test calls. This means if the name of a
system or just the telephone number changes, it is not required to adapt the
entire command schedule (the relevant interface may be used a hundred
times there), instead just the single database entry which defines the alias
name of the relevant interface has to be modified.
2
Advertisement
Table of Contents
