Introduction

There are business scenarios in which the application needs to jump from one system to another, or the application requires information from a remote system.

For example:

  • an application wants to call a transaction from a remote system
  • an application wants to navigate to a Web Dynpro application that is located on a remote system
  • an application wants to execute an Object-Based Navigation (OBN) or intent-based navigation (IBN) targeting a remote system
  • an application needs to read data from a remote system
  • an application wants to generate a URL that would be available outside the corporate network and needs to point to a Web dispatcher
  • an application wants to call an OData service from a remote system

In most cases, when there is a need to communicate or navigate to a remote system, the application can use RFC destination names, defined in SM59 as ABAP Connection (Connection type 3). However, in some cases, the information provided in the RFC destination is not enough to resolve a request (for example, the application wants to navigate to a Web Dynpro application using HTTPS), and runtime additionally requires the HTTP destination for the remote system.

The following article covers only ABAP-based use-cases and is targeted at application developers and system administrators working with NetWeaver Business Client (NWBC) and Fiori Launchpad.

Supported Shells

The resolution of the remote system configuration and the processing of cross-app (cross-system) navigation is handled by the shell that hosts the application.

The following shells need remote system configurations and must be able to handle cross-system navigation:

NWBC for Desktop NWBC for HTML Fiori Launchpad

/wp-content/uploads/2015/06/nwbc_677185.png

Remote targets used in:

  • Index page and navigation menu links, exposing application to remote systems
  • OBN targets
  • Quick launch, collecting links from navigation menu

/wp-content/uploads/2015/06/nwbc_html_677194.png

Same as for NWBC for Desktop

/wp-content/uploads/2015/06/flp_677198.png

Remote targets used:

  • When navigating with tiles that point to Web GUI/ Web Dynpro applications defined in ABAP Report Launchpad (LPD_CUST)
  • When passing Data Origin for SAP Fiori applications via sap-system parameter

 

Use-Cases

To refer to remote systems, you can use the SM59 name (RFC Destination Name) or System Alias – the normalized/base form of the SM59 Destination Name(see below).

There are several places and services in which the System Alias can be used, as described in the following list:

  • Transaction PFCG. The attribute, Target System, of the navigation menu entry. This indicates that the application shall be called by the remote system that is specified by the System Alias./wp-content/uploads/2015/06/sm59_pfcg_677211.png

 

  • Transaction LPD_CUST. The mandatory parameter, System Alias, in the Change Launchpad Role screen. The application shall call the remote system that is specified by the System Alias. The System Alias can be resolved by the ABAP runtime (NWBC) or by Portal runtime./wp-content/uploads/2015/06/sm59_lpd_cust_677212.png

 

  • Fiori Launchpad Designer. System alias can be used in a configuration of the Target Mappings in Fiori Launchpad Designer, for such application types as Transaction, URL or WebDynpro, to define application and data origin (SAP Fiori App using LPD_CUST allows a definition of system alias in LPD_CUST, see case above). The system alias can be entered in dedicated field System Alias or as default parameter sap-system in Parameters section (passing of the alias using sap-system parameter has priority over definition in the dedicated field)./wp-content/uploads/2015/06/sm59_flpd_942955.png
  • As a dynamic parameter, SYSTEM, when navigating by OBN (PFCG-based) or resolving the Report Launchpad (LPD_CUST) link. Passed as a URL parameter that overwrites customized values defined in LPD_CUST or in PFCG ( …?sap-client=001&sap-language=EN&SYSTEM=ERP1 ).
  • As a dynamic parameter, sap-system, passed within intent (intent-based navigation in Fiori Launchpad -> … #SalesOrder-display? sap-system=ERP1). The parameter overwrites the System Alias parameter defined in LPD_CUST.
  • As a parameter for System Alias Repository API web service implemented for NWBC 5.0.

Naming Convention

SM59 does not allow you to create several destinations with the same name even if the connection types are different. The trick for referencing several destinations by the same name is to have multiple SM59 entries with the same base name and an extension (_RFC, _HTTP, _HTTPS) attached to it to distinguish between the different types of connections.

For example, if the system name is XYZ, the different destination names should be the following:

  • SM59 name-resolving sequence for SAP GUI aliases: XYZ_RFC,XYZ
  • SM59 name-resolving sequence for HTTP aliases: XYZ_HTTPS, XYZ_HTTP, XYZ

Using this approach, it is possible to reference multiple connections by passing the base name only. Using the example above, it would be XYZ. The following name extensions (suffixes) can be used:

  • _HTTP (XYZ_HTTP) – to define HTTP connection settings. Can be applied for connection types G and H.
  • _HTTPS (XYZ_HTTPS) – to define HTTPS connection settings. Can be applied for connection types G and H.
  • _RFC (XYZ_RFC) – to define RFC / SAP GUI connections. Can be used for connection type 3.
  • _BOE (XYZ_BOE) – to define additional HTTP connection when used ABAP Launchpad Crystal Reports links. Can be defined as the connection of types G and H.

For connection types RFC (3) and HTTP (H, G), the name extension can be omitted (base name equal to SM59 destination name) and the runtime will still resolve the connection data properly. This fallback allows you to reuse existing definitions without extra configuration. Be aware, if you have a destination of type H/G with name equal to the base name, it will be picked for all HTTP based connections (_HTTP, _HTTPS, and _BOE). Of course, you can still overwrite fallbacks with an explicitly defined destination with extension.

NOTE

Destination names in SM59, and in tools using SM59 aliases, are case-sensitive. The recommended way is to use UPPER case names and to type suffixes in all consumption points.

The technical destination names NONE, LOCAL, etc. are resolved as the local system, that is, the application is located on the same system as the runtime.

 

Referencing by System ID and Client

From UI Add-On SP09 onwards, it is also possible to reference a system not only by logical aliasing but also by system ID and client. The use-case could be the generation of the callback location by the service called remotely: the remote service does not know the name of his system used by the caller, and can only provide its own system ID and client.

If referencing by system ID is required, the following syntax must be used:

sid(SYSTEMID[.CLIENT]) for example : sid(U00.111) or sid(U00)

The syntax is case-sensitive. sid definitions may be used in the following cases:

  • PFCG -> Target System field
  • LPD_CUST -> System Alias field
  • SYSTEM -> URL parameter for OBN/LPD_CUST link resolving (… ?SYSTEM=sid(U00.111)…)
  • sap-system -> intent parameter in Fiori Launchpad ( …#SalesOrder-display?sap-system=sid(U00.111)…)

The system-resolving logic is as follows:

  1. Look up SM59 destinations with the explicit match, that is, with the system alias equal to string sid(SYSID.CLIENT).
  2. If this is not found, parse sid string into System ID and Client
  3. Search in SM59 for RFC destination associated with given SYSID with specified client (or without, if not provided)
  4. Detect base name of system alias from RFC destination name (use as is, or remove _RFC name extension)
  5. Collect system data using system alias

To enable the SM59 destination to be searchable by SID + client notation, the Load Balancing setting of the corresponding RFC destination must be set to Yes, and the target system settings must be properly maintained.

Because the repository (SM59) can have more than one destination pointing to the same SYSID + client, the first matching value is returned.

 

Which Connection Types to Maintain?

Different SM59 destination types are used for supporting different application technologies. It is recommended to always maintain all 3 connection types (_RFC, _HTTP, _HTTPS) even if you do not need them currently. This ensures stable resolution even if your application technology should change in the future.

Destination Type Remarks
RFC (3) Necessary for supporting navigation using RFC protocol or native application embedding. If you would like to use native SAP GUI, the _RFC connection must be maintained.
HTTP (H) Necessary for supporting HTTP-based communication, e.g. all Web-browser-based application technologies such as Web Dynpro, SAP UI5, BSP, Portal, etc. If you want to use one of the mentioned app technologies, the _HTTP connection must be defined.
HTTPS (H) Necessary for supporting secure HTTP communication. The requirements are as for HTTP.

 

RFC Connection Definition

When maintaining the RFC connection, you can either select Load Balancing or provide direct settings (= Load Balancing OFF + Target Host address). Having Load Balancing switched off in the RFC connection definition ensures that your connection can be used for all versions of NWBC for Desktop and all versions of the NWBC server runtime. If you want to implement load balancing using the RFC connection setting, you need to run NWBC 5.0 together with the server runtime for SAP NetWeaver User Interface Services on User Interface Add-On 1.0 for SAP NetWeaver SPS 09 or SAP NetWeaver 7.4 with software component SAP_UI SPS08.

Referencing by System ID and Client is only supported if RFC Load Balancing is enabled.

Technical Settings (Load Balancing) Technical Settings (Direct)
/wp-content/uploads/2015/06/sm59_rdf_technical_settings_lb_677213.png

  • Settings for load balancing can be taken from corresponding SAP Logon system connection. See below for more details.
/wp-content/uploads/2015/06/sm59_rdf_technical_settings_no_lb_677214.png

  • Target Host can be taken from SM51 host
  • Instance No. can be taken from SAP Logon connection definition. See below for more details.
Login & Security Logon & Security (SNC)
/wp-content/uploads/2015/06/sm59_rfc_logon_security_701184.png

  • Leave Language empty if you want to use the language from the calling application
  • A generic user is not yet supported, so you cannot hard code a user and password here
  • Ensure that the Client that you have defined in all connection types is the same. If Client is not specified, Client of calling Application will be added
  • Set SSL to Active if you want to use Single Sign-On; you need to define SNC settings first.
/wp-content/uploads/2015/06/sm59_rfc_logon_security_snc_701185.png

  • SNC settings can be taken from the corresponding SAP Logon connection. Partners correspond to SNC name, QoP corresponds to security settings.

 

HTTP Connection Definition

Technical Settings Logon & Security
/wp-content/uploads/2015/06/sm59_http_techical_settings_701198.png

  • HTTP host and port can be found in transaction SICF of the corresponding system
  • You can use Path Prefix to define a fixed prefix path for ALL your web addresses. For example, if you work only with UI5: /sap/bc/ui5_ui5/
/wp-content/uploads/2015/06/sm59_http_logon_security_701199.png

  • Leave Language empty if you want to use the language of the calling application
  • Generic user is not yet supported, so you cannot hard code a user and password here
  • Ensure that the Client that you have defined in all connection types is the same. If Client is not specified, Client of calling application will be added
  • For HTTP connection, SSL must be set to Inactive

 

HTTPS Connection Definition

Technical Settings Logon & Security
/wp-content/uploads/2015/06/sm59_https_technical_settings_701200.png

  • HTTPS host and port can be found in transaction SICF of the corresponding system
  • You can use Path Prefix to define a fixed prefix path for ALL your web addresses. For example, if you work only
    with UI5: /sap/bc/ui5_ui5/
/wp-content/uploads/2015/06/sm59_https_logon_security_701201.png

  • Leave Language empty if you want to use the language from the calling application
  • Generic user is not yet supported, so you cannot hard code a user and password here
  • Ensure that the Client that you have defined in all connection types is the same. If Client is not specified, Client of calling application will be added
  • For HTTPS connection, SSL must be set to Active. Ensure that you have entered HTTPS Port in the Service No. field on the Technical Settings tab.

 

NOTE
If you maintain backend server destinations for Fiori Launchpad DO NOT fill Path Prefix (leave it empty). It will lead to an error when trying to access WebDynpro Applications or WebGUI transactions, while NWBC URL would be formed using Path Prefix instead of default NWBC handler path. NWBC for HTML used for starting non SAP UI5 applications on backend systems.

 

How to Find System Settings

HTTP Hosts and Ports

  • In the remote system, call transaction SICF -> F8
  • On the application toolbar, press the button Host and Port Information
SICF transaction Host and Port information
/wp-content/uploads/2015/06/sicf_host_port_701203.png /wp-content/uploads/2015/06/sicf_host_port_list_701208.png

 

RFC Load-Balancing Data

Data for configuring the RFC destination can be found in the properties of the corresponding connection defined in SAP Logon (or in NWBC 5.0 System Selector):

  • Load-balancing settings can be found on the Connection tab of the SAP Logon connection
  • SSO settings can be found on the Network tab.
SAP Logon System Settings (Connection) SAP Logon System Settings (Network)
/wp-content/uploads/2015/06/sm59_rfc_load_balancing_701210.png /wp-content/uploads/2015/06/sm59_rfc_snc_701211.png
NWBC 5.0 System Selector SM51 Server List
NWBC50SAPGUIconnection.png /wp-content/uploads/2015/06/sm51_701213.png

 

System Alias not Resolved?

If runtime is unable to determine the system configuration provided by the system alias, it will use the local system (relative path to the application) and will pass the unresolved system alias parameter (SYSTEM or sap-system) for further processing by the application. If a system alias that is dynamically passed (as a URL or Intent hash parameter) is resolved, the URL/Intent parameter is deleted from the parameter list and is not forwarded to the application.

If the application refers to a remote target using System Alias, it normally tries to point to the origin of the target. There are two types of origin:

  • Data Origin: Points to the location of data used/consumed by the target application, and indicates the location from where the data shall be loaded. For SAP UI5 applications, this will be a backend system implementing OData services.
  • Application Origin: Points to the location of the application sources, and indicates the location from where the application itself shall be loaded. For SAP UI5 applications, it is the front-end server.

The Application Origin may be the same as the Data Origin; examples of this are SAP GUI and Web Dynpro applications. For SAP UI5 applications, the SAP GUI, Web Dynpro, or URL system alias that is passed for resolution with the sap-system parameter is treated as Data Origin in all cases. It should not be used for any other purpose. It is not yet possible to explicitly pass the application origin. Instead, the Fiori Launchpad resolves the Application Origin based on the most likely default:

  • SAP UI5 application: FLP origin (front-end server) is assumed to also be the application origin.
  • SAP GUI, Web Dynpro, and URL: System Alias(data origin) is assumed to also be the application origin.

System Alias Mapping

In some cases, it makes sense to use indirection in system alias assignments and be able to redirect several system aliases to another one. There are several ways how such system alias mapping can be done:

  • PFCG If you assign system aliases to applications in PFCG, you can use database table SSM_RFC (can be called using dedicated maintenance view transaction SM30_SSM_RFC)./wp-content/uploads/2015/06/pfcg_ssm_rfc_946094.pngSSM_RFC is client independent and you cannot configure any client dependent system alias mappings.
    Recursive mappings are not supported.
    The SSM_RFC table is available from “stone age”, so can be used mostly on any SAP_BASIS release./wp-content/uploads/2015/06/sm30_ssm_rfc_946095.png
  • ABAP Report Launchpad (LPD_CUST).From SAP_BASIS 730 you can configure system alias mapping in ABAP Report Launchpad. The mapping is Launchpad role/instance and client dependent. There is no way to globally remap system aliases for all Launchpad instances and you can only map system aliases used in selected Launchpad./wp-content/uploads/2015/06/lpd_mapping_946096.png
  • Fiori and NWBC.With UI Add-on V2 there is new functionality available, that allows you to configure system alias mapping for all use cases running within UI2 NWBC (NetWeaver Business Client for UI Add-on) and Fiori Launchpad (PFCG, LPD_CUST, Fiori Launchpad Designer). The mapping can be defined in DB table /UI2/SYSALIASMAP (or using maintenance view /UI2/V_ALIASMAP in transaction SM30)./wp-content/uploads/2015/06/sm30_aliasmap_946097.pngThe mapping allows you to define global or client dependent mapping (for global, client field shall be left empty). Client dependent definition has priority over global definition./wp-content/uploads/2015/06/ui2_sys_alias_map_946098.png

 

NOTE
Please note, that not all system alias mappings are easily trackable by all frameworks and it may happen, that some settings are cached and not revoked after changing of mappings. So it is recommended to run invalidation reports, after changes (transaction SE38):

  • NWBC_DELETE_MENU_CACHE (when using any of SAP_BASIS delivered NetWeaver Business Client)
  • /UI2/NWBC_DELETE_MENU_CACHE (when using UI Add-on delivered NetWeaver Business Client)
  • /UI2/INVALIDATE_CLIENT_CACHES (when using Fiori Launchpad)
  • /UI2/INVALIDATE_GLOBAL_CACHES (when using Fiori Launchpad)

Configuring “silent” system login

After properly maintaining of the system aliases and verifying that navigation between your host and remote systems works, comes next question: how to configure “silent” login of a user during navigation, without the need to enter the login and password.

And here I am not the best expert 😉 . But I will try to provide here some information, which may help and lead you to the right direction.

HTTP connection

If the user navigates to a Web-based application, it is enough if there is established Single Sign-on and the user has client certificate installed. Login to remote system performed by the browser using installed client certificates. If one wants to log in with a user for which no client certificate installed – manual login procedure is required (and browser shall be configured to always show client certificate popup).

RFC connection

If the user navigates to a native application (SAP GUI for Windows), in addition to configuring Single Sign-on, extra configuration is necessary.

First, it needs to use a client, supporting the transfer of the login data from the host system to a remote system, for example, NetWeaver Business Client (NWBC). Details about setting up authentication using NWBC can be found here: Authentication and Single Sign-On with NWBC.

Second, you need to setup your systems in such way, that they allow transfer of login data from a host system to a remote system.

If this is going about an ABAP-based landscape, details can be found here: Using Logon Tickets with AS ABAP.

Basically, the configuration consists of two parts:

At the end, there shall be also trusted relationship between both servers established and that can be done in different ways, as described here (using transactions SSO2 or STRUST).

Existing documentation

Required SAP Notes

Requirements

  • UI Add-On SP09 (support of sid format and load-balancing in NWBC 5.0)
  • To integrate content from other systems by using the property Target System in PFCG, users need display authorization for SM59 in the back end. (NWBC 5.0)
To report this post you need to login first.

21 Comments

You must be Logged on to comment or reply to a post.

  1. Sathish Kumar

    This is a very detailed and informative blog. One of our RFC destinations was named _HTTP and it never worked. I debugged to figure out that something interesting was happening. And googled it, came across your blog to understand the same.

    Thanks.

    (0) 
    1. Alexey Arseniev Post author

      Hello Satish,

      thanks for the feedback. If you will have questions, you can ask them here directly –  I will try to help. Central place for debugging will be class /UI2/CL_SYS_ALIAS_MANAGER=>RESOLVE if you are using UI Addon (NWBC with logon URL /ui2/nwbc or Fiori Launchpad) and CL_URL=>RESOLVE_SM59_ALIAS in case of SAP_BASIS versioon of NWBC (NWBC logon URL /nwbc – without ui2).

      Best regards,

      Alexey.

      RESOLVE_SM59_ALIAS

      (0) 
      1. Emanuel Affatati

        Hi Alexey,

        I am trying to debug the system alias resolve but the breakpoint is not stopping when working with transactions.

        Yes it is stopping in the case of web dynpros.

        Do you have any idea?

        S/4 Hana on premise 1511 FP02.

        Best Regards,

        Emanuel

        (0) 
        1. Alexey Arseniev Post author

          Hi Emanuel,

          from some FLP version (do not ask which 🙂 ), the resolving logic was partially moved from server side to client side: so, the client gets all assigned system alias data on initial load and then use it when actual navigation is triggered, without backend resolving the request. But this is done not for all target types: it is an explanation why your breakpoint does not stop.

          Potentially, any request may be cached on client side, so always track HTTP REST request is actually sent => Chrome + F12 == Development Tools + Network Tab.

          Closer to the issue:

          – to see all “resolved” system alias, check response to request /sap/bc/ui2/start_up?so=*&action=*… (second one, without tm-compact=true parameter). In aggregation “systemAliases” you will see all assigned systems and how they are maintained, with host, URLs etc

          – to get called on ABAP side, when the list is requested put breakpoint as before in /UI2/CL_SYS_ALIAS_MANAGER=>RESOLVE. It would be called for each alias.

          – if you are not called -> it is cached. Can be client side, but also can be server side. In both cases you are out 😉 To get called in standard, you need have a change in SM59, in assigned systems or call both INVALIDATE reports (see in blog above). But easier, just call mentioned request start_up?so=*&action=*… directly => right mouse click on request, Open link in new tab, BUT remove parameter sap-cache-id (it is a trigger for using cache).

          BR, Alexey.

          (0) 
  2. Matt Harding

    Hi Alexey,


    Thanks for pointing out /UI2/V_ALIASMAP in UI Add On 2.0 – Was exactly what I needed for all the Target Mappings in FLP.


    Plus good to see all of this summed up in one place.


    Cheers,

    Matt

    (0) 
    1. Alexey Arseniev Post author

      Hi Matt,

      I am glad to help. I will try to update the blog, as far as I find something new fitting or will be questions requiring clarifications.

      And thanks for the feedback!

      Best regards,

      Alexey.

      (0) 
  3. Rainer Betrich

    Hi Alexey,

    great stuff – really, really helpful.

    BTW: Note 2318483 hasn`t been released. Could you please trigger that.

    Best regards,

    Rainer

    (0) 
    1. Alexey Arseniev Post author

      Hi Rainer,

      already released once more 😉

      It was needed to update unit test code in correction. It was not working in all releases.

      And thanks for feedback!

      Best regards,

      Alexey.

      (0) 
      1. Daniel Leal

        Thank you for the excellent information, Alexey.

        Regarding Note 2318483 (version 2), it appears it has a problem regarding SAP_UI 750. We are experiencing exactly the problem described by the Note in a S4/HANA 1511 FPS01 system with SAP_UI SAPK-75001INSAPUI Support Pack installed.

        Although the Note lists SAP_UI 750 in the Validity section and states it has been delivered in the SP SAPK-75005INSAPUI, SNOTE states the Note cannot be installed. Indeed looking at the correction instructions for SAP_UI 750, they list as valid SPs:

        Correction 6609 – SAPK-20004INUI700-SAPK-20004INUI700

        Correction 6781 – SAPK-20003INUI700-SAPK-20003INUI700

        Correction 6782 – SAPK-20002INUI700-SAPK-20002INUI700

        Correction 9422 – SAPK-20002INUI700-SAPK-20004INUI700


        It appears there are no reference for SAP_UI 750.

        Can you please take a look into this and let me know if I am missing something?

        Regards,

        Daniel Leal

        After posting this entry, I noticed the following validity ranges reported by SNOTE (previously I looked directly into the Note):

        Correction 6609: SAPK-75004INSAPUI – SAPK-75004INSAPUI

        Correction 6781: SAPK-75003INSAPUI – SAPK-75003INSAPUI

        Correction 6782: SAPK-75002INSAPUI – SAPK-75002INSAPUI

        Correction 9422: SAPK-75002INSAPUI – SAPK-75004INSAPUI

        I can see why SNOTE says the Note cannot be implemented, as we have SAPK-75001INSAPUI (This is SAP CAL build).

        Any suggestions on hos to fix this problem for SP 1?

        Thanks,

        Daniel

        (0) 
        1. Alexey Arseniev Post author

          Hi Daniel,

          yes, with SAP_UI 750 SP1 it will be difficult, because I have not done the correction for it… I may add it in next days, if you will not upgrade 😉

          Best regards,

          Alexey.

          (0) 
          1. Daniel Leal

            Excellent news, Alexey.  We do intend to use this version for another 3 months or so. If we could have this issue addressed it certainly would be a plus.  It also may benefit other customers using the SAP CAL S/4HANA 1511 Solution.

            Appreciate your follow-up on this matter.

            Best regards,

            Daniel Leal

            (0) 
              1. Daniel Leal

                Thank you, Alexey.  I was able to download and implement the new version of the Note, along with the pre-requisite. Unfortunately we are still experiencing the same error message.

                This is a snippet of the components in the S/4HANA system:

                S4Components.png

                Notes were implemented:

                S4NoteImplm.png

                Error displayed when executing selected Fiori apps:

                S4Error.png

                For your reference, this is not critical as if we acknowledge the error, the application appears to work correctly, but I thought I should share this result.

                Thank you again,

                Daniel Leal

                (0) 
                1. Alexey Arseniev Post author

                  Hello Daniel,

                  it is rather complex to find out the reason, only by screenshots 🙂

                  I would suggest:

                  – check that you also have note 2279202 installed

                  – check that your RFC connection (for example S4PRC_RFC) is properly defined. Do not use there explicit application server, but enable Load Balancing (there is a bug still on NWBC 6.0 client side, that prevents starting SAP GUI if a host in RFC connection different from the one in HTTP connection and the bug will be only fixed in PL5 of the client).

                  – if still does not help, create a message for component CA-UI2-INT-BE – we will check.

                  Best regards,

                  Alexey.

                  (0) 
  4. Jerry Chiang

    Hi Alexey,

    Thanks for the great sharing!

    We have a central hub deployment setup for S/4HANA with SAP webdispatcher, but we are having issue with all the transactional Fiori app, it always get loaded in the frontend system which obviously do not have the ERP t-code like ME51N, etc.

    The app should be directed to the ERP backend system via the Alias if I understand it correctly, and I have created the RFC XXX_HTTP as per your guide and maintain it in the Alias field in the t-code LPD_CUST.

    However, the app is still getting loaded in the frontend, is there something to do with the webdispatcher? Do I have to redirect some URL to the ERP backend?

    Hope you could help me on this, thanks!

    Regards,

    Jerry Chiang

    (0) 
    1. Alexey Arseniev Post author

      Hello Jerry,

      I do not think the issue related to WebDispatcher. This most likely a configuration error in alias definition. FLP falls back on the current system if alias can not be resolved.

      Please check:

      • You have properly defined all destinations EXAMPLE_BACKEND_RFC (type 3), EXAMPLE_BACKEND_HTTP (type H), EXAMPLE_BACKEND_HTTP (type H). Configuration details see above in the article.
      • In LPD_CUST you have EXAMPLE_BACKEND defined (without a suffix)
      • The target system is not overwritten dynamically (may happen if navigation triggered from within the application, not relevant for apps started by direct click on tile)
      • You are changing correct LPD_CUST instance. It may happen that user has ambiguous target mappings assigned (different targets and same intent) and you are changing the wrong definition.
      • Run invalidation reports mentioned in article, to be sure that all is up to date (normally shall work and without it, but who knows 😉 )
      • You have all notes mentioned in article applied.

      If will not help, create a message and we will check remotely 😉

      BR, Alexey.

      (0) 
  5. Santosh SA

    Hi Alexey,

    Great blog.

    A question regarding RFC connections of type H (HTTP) setup from one ABAP system to another.

    In SM59, RFC connections of type H have no ability to specify load balancing, so does that mean if the target host defined in SM59 then all load using that RFC will only ever run on that host?  Is there any ability to perfom message server load balancing of those connections?

    If not, I assume the only option is to use webdispatcher (or similar) as target for the RFC connection, which then performs load balancing acorss target ABAP system.

     

    (0) 
    1. Alexey Arseniev Post author

      Hello Santosh,

       

      sorry for such long delay with the response – with a change of the SCN platform, I do not get any more a notification mail, if a new comment posted :(. Just noticed it accidentally.

      For native connections (WinGUI)  the load balancing is supported, while you can define it in RFC connection (_RFC, type 3). Load Balancing On + system ID + message server + logon group.

      For HTTP connections (_HTTP/HTTPS, type H/G), so WebGUI and WebDynpro, host address you fill, shall be WebDispatcher / Load Balancer address. So, as you mentioned.

      BR, Alexey.

      (0) 

Leave a Reply