Table Of Contents
This document describes the CORBA adapter (CAD). CAD provides a machine-to-machine interface (MMI) over Common Object Request Broker Architecture (CORBA). This architecture is defined by the Object Management Group (OMG) organization.
The the CAD interface provides a provisioning method for the Cisco BTS 10200 Softswitch product that parallels the Command Line Interface (CLI) adapter in capabilities. CAD provides an abstraction of the Cisco BTS 10200 Softswitch in a consistent, object-oriented model. Discussion of the actual object model for this interface is not within the scope of this document.
The Cisco BTS 10200 Softswitch Command Line Interface Reference Guide is the definitive source for token descriptions (parameters) and their values, as used in the CORBA interface.
Note This document describes CORBA using OpenORB. If you are using Visibroker, use the Cisco BTS 10200 Softswitch Release 3.2, 3.3, 3.5 Programmers Specification.
This document is designed for intermediate and advanced CORBA programmers. It presumes an intermediate or higher level of CORBA programming familiarity.
The CORBA Adapter (CAD) uses the OpenORB 1.3.1 interface to develop and deploy distributed object-based applications, as defined in the CORBA specification 2.4.
The XML interface is abstracted from CORBA itself. The OpenORB package uses the Internet Inter-ORB Protocol (IIOP) using either the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP) for connections. Narrowing on the NameService also produces the BTS10200 objects. Narrowing is covered in great detail in the coding examples in the Cisco BTS 10200 Softswitch SDK package. This is bundled with the Cisco BTS 10200 Softswitch application.
Creating separate application-level connections or objects requires some object pooling and numerous logins to obtain valid login keys for every instance of the BTS10200 object. Examples are available in the bundled SDK package.
Batch Data Retrieval (Paging)
Batch data retrieval (paging) is available using the CLI show command. The use of paging is required for viewing large data sets, but the initial request to set up paging impacts performance. Subsequent requests against the same paged data are faster because the data is cached for quick retrieval. This applies to a specific session (key) and that any other command executed against that session flushes any cached data. All requested paged data must be contiguous for optimal performance.
Note For the limit token, in any single show, CORBA automatically limits paging to 500 rows.
Connections and Transactions
CORBA supports up to 50 simultaneous sessions. A session is any valid login to the CORBA interface. CORBA also supports 20 concurrent transactions. A transaction is any specific request; for example, show or change.
Each login session allocates its own specific set of resources much like an individual CLI. These sessions are audited for idle activity. If the session is not active (executes a command) within a 10 minute period, then the session is declared idle, removed from the interface, and all resources are closed.
Note The idle time has changed from previous releases. The older default was 30 minutes; it is now 10 minutes. Idle time is configurable through the bts.properties file of the CIS application. This properties file is located on the Cisco BTS 10200 Softswitch in the /opt/BTScis/etc directory.
Note Modification of the bts.properties file should not be attempted without Cisco TAC support or supervision.