TEC 2: SAP S/4HANA Fully-Activated Appliance: Changing the Web Dispatcher Port to 443
This guide shows how customers can change the web disptacher port in the SAP S/4HANA Fully-Activated Appliance from 44301 to 443 eg. if a corporate firewall blocks ports other than 443. Download the DocumentPublic
SAP S/4HANA Fully-
Activated Appliance:
Changing the Web Dispatcher
Port from 44301 to 443
SAP
January 2025
SAP S/4HANA Fully-
Activated Appliance:
Changing the Web Dispatcher
Port from 44301 to 443
SAP
January 2025
2Public
Disclaimer
The following guide outlines how to switch the HTTPS port of the SAP Web Dispatcher from 44301 to 443 in the SAP S/4HANA Fully-Activated
Appliance 1) .
It has been written for use with the SAP S/4HANA 2021 or 2020 Fully-Activated Appliance (all FPS).
It may also work for earlier releases of the appliance, however, you might need to adapt or tweak certain steps.
This document does not describe how to change all places where port numbers are specified in an SAP S/4HANA system.
It solely focuses on providing access to the general Fiori launchpad features so not all features might be fully covered.
In accordance with the recommended use cases of the SAP S/4HANA Fully-Activated Appliance, the procedure outlined in this document is
applicable for scenarios such as sandboxing, proof-of-concept, trial or scoping only.
There is especially no warranty that the procedure is in accordance with the security / network policies of your company or the ones that SAP
recommends in general for its systems.
Please refer to the standard SAP documentation how to change port numbers in systems other than the SAP S/4HANA Fully-Activated Appliance.
Since this document is no official SAP documentation, support for it is provided only via the SAP Community.
1) If you are new to the SAP S/4HANA Fully-Activated Appliance, introductory information can be found here.
Disclaimer
The following guide outlines how to switch the HTTPS port of the SAP Web Dispatcher from 44301 to 443 in the SAP S/4HANA Fully-Activated
Appliance 1) .
It has been written for use with the SAP S/4HANA 2021 or 2020 Fully-Activated Appliance (all FPS).
It may also work for earlier releases of the appliance, however, you might need to adapt or tweak certain steps.
This document does not describe how to change all places where port numbers are specified in an SAP S/4HANA system.
It solely focuses on providing access to the general Fiori launchpad features so not all features might be fully covered.
In accordance with the recommended use cases of the SAP S/4HANA Fully-Activated Appliance, the procedure outlined in this document is
applicable for scenarios such as sandboxing, proof-of-concept, trial or scoping only.
There is especially no warranty that the procedure is in accordance with the security / network policies of your company or the ones that SAP
recommends in general for its systems.
Please refer to the standard SAP documentation how to change port numbers in systems other than the SAP S/4HANA Fully-Activated Appliance.
Since this document is no official SAP documentation, support for it is provided only via the SAP Community.
1) If you are new to the SAP S/4HANA Fully-Activated Appliance, introductory information can be found here.
3Public
Introduction
Introduction
4Public
Motivation
Default setting in the appliance
• The SAP S/4HANA Fully-Activated Appliance by default offers two HTTPS ports for displaying the Fiori Launchpad
• 44301 is the HTTPS port of the web dispatcher. Via this port, the Fiori launchpad and the Web Assistant for integrated help (“?” in right upper
corner) can be used.
• 44300 is the HTTPS port of the ABAP-based ICM. Fiori will also work via this port but the Web Assistant “?” might not be displayed
Potential problem with the default setting
• In some corporate firewalls, the above ports 44301 & 44300 are blocked (e.g. the firewalls only allow the well-known ports <= 1023) and Fiori
can not be reached via the pre-defined HTTPS ports. However, most firewalls allow the use of port 443, or simply speaking omitting the port
parameter in the Fiori URL since a browser interprets an omitted HTTPS port parameter as 443
• Resolution approach
• This guide shows how to change the web dispatcher port from 44301 to 443 so that most firewalls will allow access to the Web Dispatcher (and
hence, the access to the SAP Fiori Launchpad via port 443).
• The “appliance-internal” communication between web dispatcher and ABAP ICM will still run via port 44300 but this won’t affect the connection
through your firewall since the web dispatcher on port 443 is the “proxy” that establishes the allowed handshake through the firewall
• If you need to access the ABAP ICM (or other appliance components via a blocked port), please see the respective SAP standard
documentation how to adapt this
• This resolution approach requires some basic Linux skills and will take ~ 15-30 minutes
Motivation
Default setting in the appliance
• The SAP S/4HANA Fully-Activated Appliance by default offers two HTTPS ports for displaying the Fiori Launchpad
• 44301 is the HTTPS port of the web dispatcher. Via this port, the Fiori launchpad and the Web Assistant for integrated help (“?” in right upper
corner) can be used.
• 44300 is the HTTPS port of the ABAP-based ICM. Fiori will also work via this port but the Web Assistant “?” might not be displayed
Potential problem with the default setting
• In some corporate firewalls, the above ports 44301 & 44300 are blocked (e.g. the firewalls only allow the well-known ports <= 1023) and Fiori
can not be reached via the pre-defined HTTPS ports. However, most firewalls allow the use of port 443, or simply speaking omitting the port
parameter in the Fiori URL since a browser interprets an omitted HTTPS port parameter as 443
• Resolution approach
• This guide shows how to change the web dispatcher port from 44301 to 443 so that most firewalls will allow access to the Web Dispatcher (and
hence, the access to the SAP Fiori Launchpad via port 443).
• The “appliance-internal” communication between web dispatcher and ABAP ICM will still run via port 44300 but this won’t affect the connection
through your firewall since the web dispatcher on port 443 is the “proxy” that establishes the allowed handshake through the firewall
• If you need to access the ABAP ICM (or other appliance components via a blocked port), please see the respective SAP standard
documentation how to adapt this
• This resolution approach requires some basic Linux skills and will take ~ 15-30 minutes
5Public
Constraints & Known Limitations
Known limitations
• Not all appliance features might be fully covered with the change outlined in this document, e.g. if you integrate other
software products with the appliance, the ports 44301 / 44300 might still be maintained somewhere.
If you see logs entries or errors with the mentioning of port 44301 / 44300 after you changed the settings according to this
guide, please check where else the ports need to be adapted.
Slide 14 contains a list of the most relevant places but this list might not be complete.
Constraints & Known Limitations
Known limitations
• Not all appliance features might be fully covered with the change outlined in this document, e.g. if you integrate other
software products with the appliance, the ports 44301 / 44300 might still be maintained somewhere.
If you see logs entries or errors with the mentioning of port 44301 / 44300 after you changed the settings according to this
guide, please check where else the ports need to be adapted.
Slide 14 contains a list of the most relevant places but this list might not be complete.
6Public
Step-by-Step Implementation
Step-by-Step Implementation