The integration described here is a Propel Service Exchange content pack consisting of Operations Orchestration (OO) flows and an adapter to enable Service Manager (SM) request-to-fulfill (R2F) use cases. The OO flows allow for coordinated management of tasks necessary to manage the R2F use case. The API and Data Transformation parts of the Propel content pack manage interfacing to the underlying system.
Propel aggregates catalog items from endpoint systems, such as SM. When a Propel consumer (end user) orders a catalog item, the work necessary to fulfill this request is accomplished by the Propel Service Exchange/ Service Manager integration. When Service Exchange is notified of the request to order the item (via REST), the SM fulfillment is triggered. A "createOrder" message is injected into the Service Exchange message bus and the underlying SM adapter invokes the necessary APIs to fulfill the order. This communication channel is carried out in reverse (system > bus > SM > Propel Portal) to notify the consumer that the requested item is available.
The Propel Portal provides a single "front door to IT" where multiple services are available. End users no longer need concern themselves with signing-in to the correct shopping portal to order particular types of services. With Propel, user requests can be fulfilled by different endpoint systems, such as HPE Service Manager (SM), Cloud Service Automation (CSA), and Service Anywhere (SAW) in a consistent manner. Propel administrators configure organizations and catalogs to separate catalog offerings into groups, which can be exposed to different end users based on an authentication system such as LDAP or Active Directory. To orchestrate this, the Propel solution uses Propel Service Exchange (SX) to aggregate content from multiple service providers and to integrate the content through a single consumption experience.
Service Exchange is a framework to connect endpoint systems, used to simplify the development and maintenance of integrations in multiproduct (endpoint) environments. Instead of developing numerous point-to-point integrations, developers create an adapter to integrate their product with Propel. The adapter handles requests for end users and other adapters to enable Service Exchange use cases.
Service Exchange utilizes the Canonical Data Model (CDM), which can express objects and actions in a product-agnostic manner. This data model enables otherwise disparate systems to interact, so long as they define how to transform from their local language/APIs to CDM and from CDM back to their local language/APIs. This approach replaces a point-to-point integration pattern and enables point-to-multipoint integrations. This pattern becomes more cost effective and worthwhile with every endpoint that is introduced into the integrated ecosystem.
|Propel Service Exchange|