Manual installation of SAP Integration Hub

Before you install SAP Integration Hub, check the System requirements to see if you fulfill the minimum requirements to run SAP Integration Hub and carefully assess what is valid for your system.

Flavors

To support a wide variety of SAP backend system versions and the journey to embrace SAP’s Clean Core principles, SAP Integration Hub can be installed in three flavors, depending on system version and your plan moving forward. The functionality is consistent across these flavors; only ABAP Language Version and API Release state requirements differ.

Version System release Description

Standard

7.31 (SP30)

Supporting the new SAP Integration Hub features in older systems

Cloud

2021 (7.56)

To fully embrace SAP’s Clean Core principles

Combined

2021 (7.56)

To enable older non-Cloud compliant code to run while moving towards adhering to SAP’s Clean Core principles

Perform the following steps to install SAP Integration Hub manually:

1. Import the main installation transport

Prerequisites

  • You have downloaded and unpacked the ZIP installation package for Neptune DXP - SAP Integration Hub from the Neptune DXP Portal.

Procedure

  1. Add the transport to the SAP Transport Management System.

  2. Find the path to the SAP transport directory. Use the SAP transaction AL11.

    In most systems, the transport directory is: /usr/sap/trans.

  3. Upload the K* transport file into the cofiles directory and the R* transport file into the data directory, in one of the following ways:

    1. Use the Upload File dialog in the SAP transaction CG3Z.

    2. Run the function module ARCHIVFILE_CLIENT_TO_SERVER in the SAP transaction SE37.

    3. Move the files at the OS level.

  4. Start the SAP transaction STMS and open the import queue to your system.

  5. Double-click your target system.

  6. Go to Extras → Other Requests → Add.

    Result: The Add Transport Request to Import Queue dialog opens.

  7. Add the transport request to the import queue by locating it in the STMS transport list and import the transport.

  8. Select the Import Request icon.

    Result: The Import Transport Request* dialog opens.

  9. In Target Client*, specify the target client where you are installing Neptune.

  10. In the Options tab, select the checkbox Ignore Predecessor Relations and start the import.

    In previous versions of SAP, the checkbox was called Ignore Invalid Component Version.

    Result: The import of the transport starts. The import runtime varies depending on your system. You can monitor the progress of the import by selecting the row and selecting the Import Monitor icon.

  11. When the import is completed, ignore any warnings associated with the import (code 4/6). If you receive an error (code 8/12), please contact Neptune Support.

2. Set up ICF and HTTP Services

Prerequisites

  • You have downloaded and unpacked the ZIP installation package for Neptune DXP - SAP Integration Hub from the Neptune DXP Portal.

  • You have imported the main transport for SAP Integration Hub.

Procedure

  1. Open the SAP transaction SICF.

    Result: The Define Services screen opens.

  2. Select the Execute icon, retaining the default parameters set in the Define Services screen to go to the Maintain service screen.

  3. Make sure the sap/bc/http node is activated by opening the default_host/sap/bc in the tree and finding the http node there. If it is not activated, right-click it and select the Activate Service option.

  4. When using SAP Integration Hub together with Neptune DXP - SAP Edition (version 24.14.0 or later), you need to activate the /neptune/dxp ICF node in transaction SICF.

  5. In the tree overview of the Maintain service screen, find the /neptune/dxp ICF node, right-click on it, and select the Activate Service option.

  6. When using the classic flavor of SAP Integration Hub together with Neptune DXP - SAP Edition (version 24.14.0 or later), you will need to create an external alias to map incoming HTTP requests starting with the URL path /sap/bc/http/neptune/dxp/ to the /neptune/dxp ICF node in transaction SICF.

  7. On the Maintain service screen in transaction SICF, select the External Aliases button.

    Result: The Maintain external aliases overview screen opens.

  8. Select the top tree node default_host by single-clicking on it.

  9. Press the Create New External Alias icon at the top of the screen.

  10. Enter the exact path /sap/bc/http/neptune/dxp into the input field External Alias. For the description field, you can enter something like Neptune DXP mimic http service.

  11. Navigate to the tab Trg Element to specify which ICF node should be the target for requests reaching /sap/bc/http/neptune/dxp/…​.

  12. In the tree overview, find the /neptune/dxp ICF node and double-click on it.

  13. Save the external alias by pressing the Save icon at the top.

  14. For the Cloud and Combined flavors, the /neptune/dxp HTTP Service needs to be activated.

  15. Open the SAP transaction UCON_HTTP_SERVICES.

    Result: The HTTP Services screen opens.

  16. Enter /NEPTUNE/DXP in the Filter for HTTP Services and click the Search button.

    Result: The /NEPTUNE/DXP HTTP Service should be found.

  17. Select the /NEPTUNE/DXP HTTP Service and click the Activate button.

3. Enable authorization roles for SAP Integration Hub

You can import the standard roles /NEPTUNE/DXP_DEVELOPER and /NEPTUNE/DXP_READ_ONLY either by direct file upload in the SAP transaction PFCG or via transport import. The standard role /NEPTUNE/DXP_DEVELOPER contains all required authorizations for creating and maintaining SAP Integration Hub artifacts, whereas the role /NEPTUNE/DXP_READ_ONLY contains authorization for displaying such artifacts only.

You need to import the roles in new installations and for upgrades where new authorization checks have been introduced.

After you have imported the role into the system, make a copy of the standard roles, make any adjustments you find necessary, generate an authorization profile, and assign it to the corresponding developers and administrators. After importing the transport with the roles, it might be necessary to run the program PFCG_TIME_DEPENDENCY for user master comparison if this is not already scheduled to run as a background job in the target system.

Prerequisites

  • You have downloaded and unpacked the ZIP installation package for SAP Integration Hub from the Neptune DXP Portal.

  • You have imported the main transport for Neptune DXP - SAP Integration Hub.

Procedure

  1. Copy the file _NEPTUNE_DXP_DEVELOPER.SAP located in the Authorization folder of the installation package to your Downloads folder so that it is located outside of the ZIP file.

  2. Go to the SAP transaction PFCG.

    Result: The Role Maintenance screen opens.

  3. From the menu, in Role → Upload, select the file _NEPTUNE_DXP_DEVELOPER.SAP from your Downloads folder.

  4. In the SAP transaction PFCG, open the imported role /NEPTUNE/DXP_DEVELOPER in change mode.

  5. Select the Authorizations tab and select Change Authorization Data.

  6. Select the Generate icon.

  7. In the Assign Profile Name for Generated Authorization Profile dialog, select the Execute icon.

  8. Select Back (F3) to go back to the Change Roles screen and select the User tab.

  9. Enter the users that should have access to do development with SAP Integration Hub.

  10. Select User comparison and perform a full user comparison.

  11. Repeat the corresponding steps also for /NEPTUNE/DXP_READ_ONLY in file _NEPTUNE_DXP_READ_ONLY.SAP as required.

Related topics