Architecture

Fulfillment Subscriber Inventory comprises of a server providing external interfaces and processing inventory entities and a UI client that access the server.

The following diagram represents Fulfillment Subscriber Inventory architecture:

  • Services and Operations
    The interfaces are organized into services that include related operations. The following interfaces are exposed for any client to invoke the services related to the framework. These services can be invoked over two different channels: SOAP over HTTP and SOAP over JMS.
  • Integration Channels
    To provide maximum flexibility for exposing services to the enterprise, service implementation is separated from the interface. This allows services to be invoked from different transport mechanisms. The following transports are supported:
  • Security Header
    This SOAP header element has to be sent along with all operations (except Authenticate) in the request. The header contains a WS-Security JSON Web Token returned in the authenticate response.