SAP Integration Hub

The Hub API Designer provides a unified environment for defining, maintaining, and managing APIs that connect to SAP systems through the SAP Integration Hub framework. It extends Neptune DXP - Open Edition’s existing API management capabilities in the API Designer to cover SAP-integrated use cases, where APIs are stored, transported, and executed directly in your SAP back end.

Deployment environments

The Hub API Designer can be used on SAP systems with or without Neptune DXP - SAP Edition installed and supports the same SAP system versions across on-premise, private cloud, and public cloud deployments. In on-premise and private cloud environments, transports are imported directly and managed locally. In public cloud systems, connectivity and execution are handled through managed runtime services that adhere to SAP’s Clean Core principles. Regardless of the environment, you define and maintain APIs in the same way from within Neptune DXP - Open Edition.

System integration and connectivity

The Hub API Designer can be used in Neptune DXP - Open Edition alone or alongside Neptune DXP - SAP Edition if the latest version of Neptune DXP - SAP Edition is installed. Both editions provide the same interface and share the same underlying data model.

All API definitions are stored in the connected SAP system and moved between systems through the standard SAP transport mechanism across the development, quality, and production deployment stages.

Remote systems

You connect external SAP systems in the Hub API Designer as remote systems that you define with the system type Neptune DXP - SAP Integration Hub in the Remote Systems tool to establish the communication path used by the SAP Integration Hub framework for data exchange. You configure authentication and endpoint details in a system role set as a development environment via the Proxy Authentication tool, upon which you can transport these details forward to other systems.

To maintain user permissions and traceability, Neptune recommends that you use principal propagation to ensure that each API action reflects the actual user identity during design and runtime. See Enabling principal propagation in Neptune DXP - Open Edition.