HPE Propel integrates with HPE Service Anywhere (HPE SAW) to accomplish request-to-fulfill (R2F) use cases and ticket management. HPE Propel aggregates catalog items from HPE SAW, allowing the consumer (end user) to order HPE SAW catalog items using HPE Propel. Once an order is placed, HPE SAW is used for fulfillment. HPE Propel listens for changes to the fulfillment request (for example, completion or approval) and propagates these changes back to the appropriate HPE Propel. The consumer can also issue a ticket against HPE SAW from the HPE Propel Request Support application. In this case HPE Propel uses the SAW API to create a service request. Other ticket management operations (including List, View Detail, Add Comment or Attachment, and Close) result in corresponding action invocation from HPE SAW.
Each interface is a RESTful API and uses standard web services to implement the APIs.
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.
|Propel Service Exchange|