cancel
Showing results for 
Search instead for 
Did you mean: 

NWBC generates URL with wrong dispatcher port

Wilbert_Jeuken
Explorer
0 Kudos

Hello all,

When starting a classical transaction from an NWBC Fiori Launchpad session, an URL is generated in which the dispatcher port is cut short to ":32" (the suffix of the instance number is missing). The subsequent call of the SAPgui fails with "Partner <Hostname_FQDN>:32 not reached". When analyzing a verbose NWBC trace, I can see this line:

Try to find connection for the following URL: https://<Hostname_FQDN>:<HTTPS_Port>/sap/bc/gui/sap/its/webgui;~service=32?%7etransaction=VA01&%7enosplash=1&sap-client=<CLIENT>&sap-language=EN&sap-user=<USER>

When calling the same transaction from a browser (Chrome), the requested transaction is started without issues.

Where can I influence the URL generated, or how can I make sure the right URL is constructed?

Accepted Solutions (0)

Answers (1)

Answers (1)

sandra_thimme
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Wilbert,

the WebGUI-URL with all its parameters is needed to start a native GUI-Transaction.

Please check target host and instance number:

Configuration Using RFC Destinations,

Parameters evaluated at runtime:

ABAP Connection Definition.

Regards,

Sandra