Neptune DXP Documentation
Neptune DXP - Open Edition · 25.0 MTS

System requirements

The AI Context Hub connects Neptune DXP - Open Edition to an SAP system through Neptune DXP - SAP Edition. The following must be in place, in the order shown, before configuring a data source or ingesting a system.

Neptune DXP - Open Edition

  • Neptune DXP - Open Edition version 25.0 installed:

    Neptune DXP - Open Edition version 25.0 is the release that includes the AI Context Hub. No separate license or license extension is required. Once Neptune DXP - Open Edition version 25.0 is installed, the SAP Data Sources tool is available in Naia Agent Studio in the Cockpit.

  • SAP system connected as a remote system:

    The SAP system is connected as a remote system in the Remote Systems tool (Security tool group). When the system is opened there, it shows an AI Context Hub tab, through which the orchestration engine connects and ingests.

  • Network access to the SAP system opened:

    The Neptune DXP - Open Edition host reaches the SAP system’s HTTP endpoints, so a component ingests rather than failing on connection. For the paths a network or firewall configuration must allow, see SAP connectivity and authorizations.

Connected SAP system

  1. Neptune DXP - SAP Edition version 21 or higher installed:

    This is the platform the orchestration engine connects to and ingests, and it provides the API Designer and API Factory that the later requirements build on.

  2. AI Context Hub API transport imported:

    This transport adds the bridge API the orchestration engine uses to ingest the artifact types and the application component hierarchy and to read business-object metadata, so the system cannot be ingested until it is imported. After import, the bridge API is present in the API Designer.

    The transport is available from the Neptune DXP Portal, under Neptune DXP - SAP Edition → Xtra Add-Ons → Neptune DXP - AI Context Hub.

  3. API Factory access granted:

    The API Factory is deny-by-default, so policies, or entity sets where an API uses entity references, must give the ingestion and runtime identities access to the artifacts they need. When access is complete, a component ingests without a policy error. For what to grant, and how ingestion and runtime access differ, see SAP connectivity and authorizations and the SAP Edition API Factory Policy documentation.

  4. SAP Integration Hub transport imported (optional):

    This transport is needed only for data sources that use SAP Integration Hub APIs. When it is installed and its ICF path active, its APIs appear during ingestion; when it is absent, ingestion skips them and continues with the other sources.

Related topics