Some Basic Terms

Application Programming Interface. In this document, reference is made to the Execution API, the HA API, the Registry API, the PCA, and the TimerLib API (which are supplied with HP OpenCall), and an External API (which is supplied by the user).

In a client/server architecture, this is the side that requests a service from the server.

Plug-In Execution API. This is one of the components of the PIC Framework supplied with HP OpenCall.

Finite State Machine.

Fault Tolerant Controller. This is a component of the HP OpenCall platform which provides fault tolerance.

C++ Compiler for Linux.

HA API. This is one of the components of the PIC Framework supplied with HP OpenCall.

Abbreviation for Inter Process Communication.

Means “no operation”. In a user plug-in (shared library) context, NOP is used to indicate that, by default, a method does nothing. If you want the method to perform some operations, then you must customize the method by supplying the code to perform the operations you desire.

Abbreviation for HP OpenCall.

Plug-In Communications API. This is one of the components of the PIC Framework supplied with HP OpenCall.

Plug-In Container/Application Guardian. This is the name of the HP OpenCall feature that supplies the PIC, the PIC Framework, and the associated APIs.

Plug-In Container. This is one of the components of the PIC Framework supplied with HP OpenCall. The role of the PIC is to encapsulate user applications (called user plug-ins) so that they can be managed by the FTC and can communicate with other user plug-ins using the PCA.

This framework is supplied with HP OpenCall. It provides the PIC, the PCA, the Execution API, the HA API, and the Registry API. This framework enables user-written code to benefit from the facilities of HP’s FTC (Fault Tolerant Controller) and to communicate with other user plug-ins using the PCA.

This is a process running on the HP OpenCall platform. The PIC, and the user plug-in (shared library) that it encapsulates, run as a single process. This process is known as the PIC process.

Registry API. This is one of the components of the PIC Framework supplied with HP OpenCall.

In a client/server architecture, this is the side that performs a service for the client.

A set of related messages within the flow of messages exchanged between user plug-in processes.

Timer Library API. This is one of the components of HP OpenCall.

This is user-supplied code encapsulated in a PIC. It enables user-written code to benefit from the facilities of HP’s FTC (Fault Tolerance Controller) and to communicate with another user plug-in using the PCA.

The user plug-in is supplied in the form of a shared library.