HPE Propel 2.20 integrates with HPE Operations Orchestration (HPE OO) to accommodate general-purpose integrations not supported by targeted integration adapters such as HPE SM, HPE SAW, and HPE CSA. The HPE OO flows allow for coordinated management of the tasks necessary for request-to-fulfill (R2F) use case. The API and Data Transformation parts of the HPE Propel content pack manage interfacing to the underlying system.
When an HPE Propel consumer (end user) orders a catalog item, the work necessary to fulfill this request is accomplished by the HPE Propel Service Exchange/HPE OO integration. When Service Exchange is notified of the request to order the item (via REST), the HPE OO flow for fulfillment is triggered. A "createOrder" message is injected into the Service Exchange message bus and the underlying HPE OO adapter invokes the necessary APIs to fulfill the order. This communication channel is carried out in reverse (system > bus >HPE OO > HPE Propel Portal) to notify the consumer that the requested item is available.
The HPE 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 HPE Propel, user requests can be fulfilled by different endpoint systems, such as HPE Service Manager (HPE SM), HPE Cloud Service Automation (HPE CSA), and HPE Service Anywhere (HPE SAW) in a consistent manner. HPE 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 HPE Propel solution uses HPE 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 HPE 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.
Documentation for this integration can be found using the following links:
|Downloadable Adapter Material|
|Propel Service Exchange|
|Operations Orchestration Platform|
Generated: 6/11/2018 4:50:29 AM