The customer must write a client application that uses the PDBI request/response messages to
communicate with the PDBA. Details of the request/response messages appear in PDBI Request/Response
Messages
Socket Based Connection
The PDBI messages are sent across a TCP/IP socket. The client application is responsible for connecting
to the PDBA well-known port and being able to send and receive the defined messages. It is also the
responsibility of the customer’s provisioning system to detect and deal with socket errors. Tekelec
recommends that the TCP ‘keepalive’ interval on the customer’s socket connection be set such that a
socket disconnection problem is promptly detected and reported.
There is a limit to the number of PDBI connections; the default is 16 clients. If an attempt is made to
connect more than the current client limit, a response is returned to the client:
PDBI_TOO_MANY_CONNECTIONS. After the response is returned, the socket is automatically
closed.
Note: Although the default limit is 16 PDBI connections, Tekelec is able to configure and support up
to 128 connections. If you require more than 16 connections, contact Tekelec for information. concurrent
client
String-Based Messages
The PDBI messages (requests and responses) are NULL-terminated strings. This has several benefits.
• It simplifies sending and receiving the messages from any language that has socket capability (for
example, Perl or Java).
• It is easier for the PDBA to support any combination of the G-Flex, G-Port, and INP features at
previous and new levels. Because the messages are not tied to C structures, differences between
previous and new versions of the PDBI calls will not cause possible memory corruption. For
example, if a new parameter is added to the connect(…) command, a client using the previous
version of the command will simply receive a parsing error. The same change in a C structure-based
interface could result in the new C structure being filled in with wrong data.
• It is easier for the PDBA to support any combination of the G-Flex, G-Port, INP, EIR, A-Port, AINPQ
and IGM Migration features at previous and new levels. Because the messages are not tied to C
structures, differences between previous and new versions of the PDBI calls do not cause possible
memory corruption. For example, if a new parameter is added to the connect(…) command, a
client using the previous version of the command simply receives a parsing error. The same change
in a C structure-based interface could result in the new C structure being filled in with wrong data.
• Because the messages are user readable, debugging errors in messages is easier.
• Messages can easily be stored in a request log for review or replay later.
Security
The PDBA maintains a list of IP addresses that are allowed to connect through the PDBI. Any connect
request coming from an IP address that is not in the list is rejected. Each IP address in the list has either
READ or READ/WRITE permission. IP addresses can be added to and removed from the list and
permissions can be modified using the EPAP user interface PDBA menu items (refer to the PDBA
Menu description in the EPAP Administration Manual).
25
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual
To Next Page
Loading...
