The SIS has the following components and dependences (with links to APIs).

Dependency Description

Rhino SLEE

OpenCloud JAIN SLEE platform.

CGIN Connectivity Pack 3.1

Provides the CGIN APIs, activities, and event types that the IN services use.

IN This is required for SIS-IN only
Component Description

EasySIP resource adaptor type

Provides the EasySIP API, activity, and event types that SIP services use.

SIP This is provided by SIS-SIP only

SIS Common libraries

Provide SIS functionality common to all SIS implementations, including the JMX management API. There is one each for:

SIS Service Composition Selection Extensions resource adaptor types

Provide activity and event types that allow SIS extension components to determine which service composition the SIS should execute for a given initial event. There is one each for:

SIS Interceptor Extension resource adaptor types

Provide activity and event types that:

  • allow SIS extension components to modify signaling parameters in composition service input or output messages

  • allow SLEE services to invoke SIS interceptor components for arbitrary protocol messages.

There is one each for:

SIS Composition Activity Provider resource adaptor type

Provides access to a SIS-managed activity object, related to the underlying network dialog that a service interacts with, through the virtual dialog layer (which the SIS provides, between the network and services, to manage service interaction).

This activity object lets multiple services share state using SLEE-provided features — without the services having to deal with state cleanup on network dialog termination.

Note For a given network dialog, the SIS uses the same activity object to represent service composition selection, interceptor, and composition activities in the SLEE. This means that state can be shared between composition services and SIS extension components if required.

IN This is a SIS feature for IN only

Service Interaction Manager

This component:

  • contains the service-interaction logic of the SIS

  • intelligently manages the delivery of events on a network dialog to multiple services, as well as the responses that it receives from those services

  • is packaged and deployed as a JAIN SLEE resource adaptor, but does not directly provide resource adaption for all resource adaptor types that it implements (a standard SIP or CGIN resource adaptor embedded inside the Service Interaction Manager provides resource adaption functionality for, and implements, the relevant protocol resource adaptor type)

  • injects interaction logic into the events that the embedded resource adaptor passes to it and into the responses that services generate

  • uses relevant protocol resource adaptor type APIs and the SLEE 1.1 specification to interact with the embedded resource adaptor, the SLEE, and composition services.

For IN, the embedded CGIN resource adaptor has two parts:

  • frontend component — a JAIN SLEE resource adaptor (in Java code), implemented according to the SLEE 1.1 specification, to provide functionality defined by the CGIN architecture.

  • backend component — an external TCAP stack which connects to the SS7 network.

See the CGIN documentation for more information on using SS7 networks.

For SIP, the embedded SIP resource adaptor contains the SIP stack and connects directly to the SIP network.
Previous page Next page
SIS Version 3.2