Tekelec EAGLE 5 - Transaction-Oriented API

4.
The PDBA gets the request message in unencrypted form and sends an unencrypted response to
the SSH client.
5.
The SSH client encrypts the response message and sends it to the SSH port on the CPA machine.
6.
On the CPA machine, the SSH daemon decrypts the message and forwards it to the CPA. The CPA
receives the message unencrypted.
How to Configure the CPA for Connecting to the PDBA
This section describes the parameters that must be defined on a CPA (Customer Provisioning
Application) machine to allow it to connect to the PDBA. The parameters used to configure a CPA
machine for connecting to the PDBA depend on whether SSH tunneling is to be used.
How to Configure the CPA When SSH Tunneling Is Not Used
If SSH tunneling is not to be used, configure the CPA with the following parameters:
• IP address of the PDBA
• PDBA port number 5873
How to Configure the CPA When SSH Tunneling Is Used
If SSH tunneling is to be used, the OpenSSH suite (version 3.6.1 or later) must be installed on the CPA,
the sshd daemon must be running, and the following parameters configured on the CPA machine:
• IP address: either 127.0.0.1 or localhost
• Port number: Use the same port number as is configured through the EPAP GUI (for more
information, refer to the EPAP Administration Manual.)
In addition, provide the following information to the EPAP administrator:
• Port number on the CPA to be used for tunneling (this port number should be the same as the port
number specified on the CPA machine)
• Username and password of the CPA machine
Note: The password is not stored by the EPAP software. It is used only one time for setting up the
SSH tunnel.
Transaction-Oriented API
The PDBI is a transaction-oriented API. This means that all subscription-related commands are sent
within the context of a transaction. Two transaction modes are supported, normal and single.
Normal Transaction Mode
The normal transaction mode is the default method and has two main benefits:
• Many updates can be sent in a large transaction, and written to the database all at once when the
transaction is completed. This results in a much faster rate of updates per second.
• It provides transaction integrity by allowing updates to be aborted or rolled back if there is an
unexpected failure of some kind before the transaction is completed. Updates are not committed
to the database until the end_txn command is issued. If an unexpected failure occurs or if the
transaction is manually aborted, the database is maintained in the state before the start of the
transaction (seer Command Atomicity ).
27
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual