third user is granted access, and so forth. Of course, whenever any user's time out period expires,
his/her request is rejected immediately.
• If the third user sets a time out period longer than the second user and the second user's time out
period expires before the first user releases the transaction, the second user's request is dropped
from the queue. The third user subsequently moves up in the queue. Thus, if the first user releases
the transaction before the third user's time out has expired, the third user is granted access.
Request Queue Management
If multiple command requests are issued simultaneously, each request is queued and processed in
the order it was received. The user is not required to wait for a response from one command before
issuing another.
Incoming requests, whether multiple requests from a single user or requests from multiple users, are
not prioritized. Multiple requests from a single user are handled on a first-in, first-out basis. Simply
put, requests are answered in the order in which they are received. Servicing of requests from multiple
users is dependent upon traffic in the data network.
Interface Configuration and Installation
In addition to this manual, additional information concerning PDBI installation, configuration and
integration with the network operator's information system is provided in the EPAP Administration
Manual.
Transparency of Redundant Systems
The network operator is responsible for provisioning to only one PDBA. Once the active PDB is
provisioned, the system automatically passes down the data to the active and standby RTDBs on that
EAGLE 5 ISS. At the same time, the data is also passed, asynchronously, to the standby PDB and
subsequently to the mated RTDBs on the mated EAGLE 5 ISS. Provisioning of redundant systems,
therefore, is transparent to the user.
When the active PDBA becomes unavailable, the standby PDBA does not automatically switch to
active. The PDBA client must send a switchover command to tell the standby PDBA to become active.
Logs
Several logs are available to the user, including a Command Log, which contains a trace of the
commands sent to the PDBA, and an Error Log, which contains a trace of all errors encountered during
provisioning, in addition to several other options.
Crash Recovery
If a crash occurs while a transaction is in process and does not cause database corruption, the database
remains in the state before the crash after the reboot.
In the event of a catastrophic failure or corruption of a database, several options exist for reloading
the data. For more information, refer to the EPAP Administration Manual.
30
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual
To Next Page
Loading...
