Cisco Systems OL-27172-01 Mobility Aid User Manual


 
19-2
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 19 RDU and DPE Connection Management
RDU Batch Concurrency
RDU Batch Concurrency
In the Cisco BAC system, a provisioning client submits API requests to the RDU in the form of batches
containing single or multiple commands. A command represents an operation that can be performed on
an object in the RDU's database, for example, changing a device's Class of Service. Depending on the
commands contained in the batch, the RDU runs the batch in one of two modes: concurrent or
non-concurrent.
The commands contained within a batch determine the mode it is to be run with. When a batch is
received at the RDU, its commands are checked and the batch is marked with the mode with which it
must be run with. During the execution of a concurrent-mode batch, other concurrent-mode batches are
allowed to be run, in parallel. The majority of batches executed are run in the concurrent mode.
If the batch is marked as non-concurrent, it is executed only when all the currently executing batches are
completed in the RDU. The non-concurrent batch is run alone. After the batch completes running, the
RDU processes the queued batches in the mode that they have been marked.
The reason concurrent and non-concurrent modes exist is to provide higher throughput at the RDU
without losing data integrity. There are only a few commands that cause a batch to run in non-concurrent
mode. They are mainly concerned with system configuration operations that are not called very often.
Non-concurrent Commands
Along with Server Registration, if any of the following commands are present in a batch, it is run in
non-concurrent mode.
Configuration Interface
addLicenseKey
addUser
addCustomPropertyDefinition
addClassOfService
addFile
changeClassOfServiceProperties
changeDPEDefaults
changeExtensionPointSettings
changeRDUDefaults
changeSystemDefaults
changeFileProperties
changeProvGroupProperties
changeUser
deleteClassOfService
deleteFile
deleteLicenseKey
removeCustomPropertyDefinition
replaceFile