Show TOC

Creating System Alias for ApplicationsLocate this document in the navigation structure

Use

An SAP system alias is needed as the logical name of a system connection, that is, you specify where the SAP system alias should point to. Depending on the SAP Gateway content scenario and your system landscape you thus set up the system alias. The system alias is the result of the routing for an inbound request on SAP Gateway. It can be a remote or a local system. If that system alias is flagged as a Local GW (Local Gateway) instance, it means that the system that is responsible for processing (managing and storing) the data of an inbound request is the local SAP Gateway instance itself.

For the SAP Fiori system landscape, you need one system alias pointing to the front-end server with the indicator Local GW selected. For each back-end system that you want to use, you need at least one system alias with the software version Default. If you use approvals in a back-end system, you need an additional system alias for task processing within the workflows used in this back-end system.

Note

From SAP NetWeaver 7.4 Support Package 6, you can perform setup tasks for SAP Fiori by using task lists that SAP delivers. A task list groups configuration tasks logically and guides you through the necessary tasks.

For an overview of all task lists and tasks for SAP Fiori, see Configuration Using Task Lists.

The following task lists apply to this step:

  • SAP_GATEWAY_ADD_SYSTEM

  • SAP_GATEWAY_ADD_SYSTEM_ALIAS

Prerequisites

You have defined remote function call (RFC) destinations from the ABAP front-end server to all back-end servers. For more information, see Managing RFC Destinations.

Procedure

  1. In Customizing for SAP NetWeaver, choose Start of the navigation path UI Technologies Next navigation step SAP Fiori Next navigation step Initial Setup Next navigation step Connection Settings (Front-End Server to ABAP Back-End Server) Next navigation step Define SAP System Alias End of the navigation path.

  2. Choose New Entries.

  3. Create the following SAP system aliases:

    • For the front-end server: One SAP system alias with the Local GW indicator selected.

    • For each back-end system: One SAP system alias with the corresponding RFC destination assigned and the software version Default.

    • For each back-end system for which you use approval apps: One additional SAP system alias for task processing with the following parameters:

      • Local GW: Not selected

      • For Local App: Selected

      • Software Version: Select the relevant data provider, such as /IWPGW/BWF.

    For more information about further settings, see the following documentation:

    • For SAP NetWeaver 7.31, see SAP Help Portal at http://help.sap.com/nwgateway20Start of the navigation path Configuration and Deployment Information  Next navigation step Configuration Guide Next navigation step SAP Gateway Configuration Guide Next navigation step SAP Gateway Configuration Next navigation step Connection Settings for SAP Gateway Hub System Next navigation step Connection Settings: SAP Gateway to SAP Systems Next navigation step Creating an SAP System Alias End of the navigation path.

    • For SAP NetWeaver 7.4, see SAP Help Portal at http://help.sap.com/nw74Start of the navigation path Application Help Next navigation step Function-Oriented View Next navigation step SAP Gateway Foundation (SAP_GWFND) Next navigation step SAP Gateway Foundation Configuration Guide Next navigation step SAP Gateway Configuration Next navigation step Connection Settings for the SAP Gateway Hub System Next navigation step Connection Settings: SAP Gateway to SAP Systems Next navigation step Creating an SAP System Alias End of the navigation path.