Port Used in SAP

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 29
At a glance
Powered by AI
The document discusses various application servers, ports, and services used in SAP systems. It provides details on default ports and their purposes for different application servers like ABAP, Java, and message servers. It also covers ports and services for SAP NetWeaver.

The main application servers mentioned are ABAP, Java, and message servers. ABAP is used for SAP GUI and RFC communication. Java is used for HTTP, SSL, IIOP, and other protocols. Message servers are used for system information retrieval and internal communication.

Some key ports used for communication between application servers include 3300-3399 for ABAP Gateway, 3200-3299 for the ABAP Dispatcher, and ports starting with 5 for Java servers. Internal ports are also discussed briefly.

Product Port Name Service in Default Range Rule External Fixed Comments

Name etc/Services
Application SAP Dispatcher sapdp<NN> 3200 3200- 32<NN> Yes Yes Used by SAP GUI for Windows and Java.
Server 3299
ABAP
Application Gateway sapgw<NN> 3300 3300- 33<NN> Yes Yes Used for CPIC and RFC communication.
Server 3399
ABAP
Application Gateway secured sapgw<NN>s 4800 4800- 48<NN> Yes Yes SNC secured for CPIC and RFC
Server 4899 communication.
ABAP
Note
There is no related sapdp<NN>s(47<NN>)
port for the SAP Dispatcher.
Application ICM HTTP None 8000 8000- 80<NN> Yes No You can configure to port 80 after
Server 8099 installation.
ABAP
Not active by default.
Application ICM HTTPS None 44300 44300- 443<NN> Yes No Must be configured after installation.
Server 44399
ABAP Not active by default.

Application ICM SMTP None Not 25 None Yes No Must be configured after installation. Only
Server active one instance per host should offer SMTP
ABAP services.
Application HTTP sapctrl<NN> 50013 50013- 5<NN>13 Yes Yes On the SAP Central Services (SCS and
Server 59913 ASCS) instance the default instance is 01
ABAP making the default port 50113.
Application HTTPS sapctrls<NN> 50014 50014- 5<NN>14 Yes Yes On the SAP Central Services (SCS and
Server 59914 ASCS) instance the default instance is 01
ABAP making the default port 50114.
Application Message server sapmsSID 3600 3600- 36<NN> Yes No Relevant only for systems that have been
Server 3699 installed prior to SAP NetWeaver 7.0 with a
ABAP central instance (CI).
You can reassign service names to an
arbitrary value after installation in
/etc/services.
Application Internal message None None None None No No Relevant only for systems that have been
Server server port installed prior to SAP NetWeaver 7.0 with a
ABAP central instance (CI).

Configure the internal message server port


with profile parameter rdisp/msserv_internal.

If this internal port is configured, all


modifying clients like the application servers
have to connect to the internal port.

For more information, see SAP Note


1421005 .
Application Message server None 8100 8100- 81<NN> Yes No Relevant only for systems that have been
Server HTTP 8199 installed prior to SAP NetWeaver 7.0 with a
ABAP central instance (CI).

Can be used to retrieve system information


with HTTP.

Not active by default.


Application Message server None 44400 44400- 444<NN> Yes No Relevant only for systems that have been
Server HTTPS 44499 installed prior to SAP NetWeaver 7.0 with a
ABAP central instance (CI).

Can be used to retrieve system information


with HTTPS.

Not active by default.


Application Dispatcher UDP 3200 3200- 32<NN> No No Only used on local host for signaling
Server 3299 dispatcher. Never seen on the network.
ABAP
Application Gateway UDP 3300 3300- 33<NN> No Yes Only used on local host for signaling
Server 3399 dispatcher. Never seen on the network.
ABAP Disabled by default starting with release SAP
NetWeaver 7.0 (gw/use_udp=1 enables
UDP port).
Application ICM Admin None 65000 0-65000 Detected No No Internal communication. Automatically uses
Server automatically the first free port from 65000 downwards.
ABAP Port accepts connections only from the local
host.
Application HTTP None 50000 50000- 5<NN>00 Yes No None
Server Java 59900
Application HTTP over SSL None 50001 50001- 5<NN>01 Yes No None
Server Java 59901
Application IIOP initial None 50002 50002- 5<NN>02 Yes No None
Server Java context 59902
Application IIOP over SSL None 50003 50003- 5<NN>03 Yes No None
Server Java 59903
Application P4 None 50004 50004- 5<NN>04 Yes No None
Server Java 59904
Application P4 over HTTP None 50005 50005- 5<NN>05 Yes No Relevant only for releases up to and
Server Java tunneling 59905 including SAP NetWeaver 7.0x with Java
Dispatcher
Application P4 over SSL None 50006 50006- 5<NN>06 Yes No None
Server Java 59906
Application IIOP None 50007 50007- 5<NN>07 Yes No None
Server Java 59907
Application Telnet None 50008 50008- 5<NN>08 Yes No None
Server Java 59908
Application JMS None 50010 50010- 5<NN>10 Yes No Relevant only for releases up to and
Server Java 59910 including SAP NetWeaver 7.0x with Java
Dispatcher
Application HTTP sapctrl<NN> 50013 50013- 5<NN>13 Yes Yes On the SAP Central Services (SCS and
Server Java 59913 ASCS) instance the default instance is 01
making the default port 50113.
Application HTTPS sapctrls<NN> 50014 50014- 5<NN>14 Yes Yes On the SAP Central Services (SCS and
Server Java 59914 ASCS) instance the default instance is 01
making the default port 50114.
Application Server join port None 50020 50020- 5<NN>20 + No Yes Server number <x> = 0..15
Server Java 59995 (<x> * 15)
Application Server debug None 50021 50021- 5<NN>21 + No Yes Server number <x> = 0..15
Server Java port 59996 (<x> * 15)
SAP CSDM None 20201 0-65535 None Yes No Central Software deployment manager
Business
Suite
SAP DCOM DCE 135 135 None No Yes Connection to license server.
Business
Suite DCOM uses port 135 for the Service Control
Manager, which allocates a free port for the
application.
SAP Lotus Domino - None 62026 26-65526 <xxx>26 Yes No Instance 1 of 4
Business Connector 1
Suite
SAP Lotus Domino - None 62027 27-65527 <xxx>27 Yes No Instance 2 of 4
Business Connector 2
Suite
SAP Lotus Domino - None 62028 28-65528 <xxx>28 Yes No Instance 3 of 4
Business Connector 3
Suite
SAP Lotus Domino - None 62029 29-65529 <xxx>29 Yes No Instance 4 of 4
Business Connector 4
Suite
SAP Lotus Domino - None 62126 26-65526 <xxx>26 Yes No Instance 1 of 4
Business Proxy 1
Suite
SAP Lotus Domino - None 62127 27-65527 <xxx>27 Yes No Instance 2 of 4
Business Proxy 2
Suite
SAP Lotus Domino - None 62128 28-65528 <xxx>28 Yes No Instance 3 of 4
Business Proxy 3
Suite
SAP Lotus Domino - None 62129 29-65529 <xxx>29 Yes No Instance 4 of 4
Business Proxy 4
Suite
SAP Central Enqueue server sapdp<NN> 3201 3200- 32<NN> No No Provides locking services.
Services 3299
(SCS) Profile parameter name enque/encni/port.

SAP Central Enqueue server None 50116 50116- 5<NN>16 No No Replication of enqueue data for high
Services 59916 availability.
(SCS)
Profile parameter name enque/enci/repl_port
SAP Central Message server sapms<SID> 3601 3600- 36<NN> Yes No Configure the message server port with
Services port 3699 profile parameter rdisp/msserv.
(SCS)
SAP Central Internal message None None 3600- None No No Configure the internal message server port
Services server port 3699 with profile parameter rdisp/msserv_internal.
(SCS)
If this internal port is configured, all
modifying clients like the application servers
must connect to the internal port.
SAP Central HTTP None 8100 8100- 81<NN> Yes No Configure the message server HTTP port
Services 8199 with profile parameter
(SCS) ms/http_port_<n>.

<n> stands for a number between 0 and 9.


Always assign the parameters consecutive
numbers ascending from 0 (withNogaps), so
that they are correctly identified.

Not active by default.


SAP Central HTTPS None 44400 44400- 444<NN> Yes No Configure the message server HTTPS port
Services 44499 with profile parameter
(SCS) ms/https_port_<n>.

<n> stands for a number between 0 and 9.


Always assign the parameters consecutive
numbers ascending from 0 (withNogaps), so
that they are correctly identified.

Not active by default.


SAP Central HTTP sapctrl<NN> 50013 50013- 5<NN>13 Yes Yes On the SAP Central Services (SCS and
Services 59913 ASCS) instance the default instance is 01
(SCS) making the default port 50113.
SAP Central HTTPS sapctrls<NN> 50014 50014- 5<NN>14 Yes Yes On the SAP Central Services (SCS and
Services 59914 ASCS) instance the default instance is 01
(SCS) making the default port 50114.
SAP Central Gateway sapgw<NN> 3301 3300- 33<NN> Yes No Ports used by gateway for CPIC and RFC
Services 3399 communication.
(SCS)
SAP Central Gateway secured sapgw<NN>s 4800 4800- 38<NN> Yes Yes SNC secured for CPIC and RFC
Services 4899 communication.
(SCS)
Note
There isNorelated sapdp<NN>s(47<NN>)
port for the SAP Dispatcher.
SAP SAP ESP Web None 9786 9786 9786 Yes Yes Used to connect ABAP log providers.
Enterprise Service Provider
Threat  REST
Detection
 SOAP
SAP UDP None 5514 0-65535 514 Yes Yes UDP connection for all other providers.
Enterprise
Threat
Detection
SAP TCP None 10514 0-65535 10514 Yes Yes TCP connection for all other providers.
Enterprise
Threat
Detection
SAP TLS None 10443 0-65535 10443 Yes Yes Encrypted connection for all other providers.
Enterprise
Threat Disabled by default.
Detection
SAP HANA etsserver None 30021 30021 3NN21 No Yes Internal port on which the accelerator for
Accelerator SAP ASE listens
for SAP
ASE Any SAP ASE clients that run outside the
SAP HANA system can connect to an
accelerator for SAP ASE host on port 30021
directly.
SAP HANA esserver None 30012 30012 – 3NN12 No Yes Internal port on which dynamic tiering host
Dynamic 39912 listens
Tiering
SAP HANA indexserver None 30015 30015 – 3NN15 Yes Yes Single-container system: SQL/MDX access
Platform 39915 port for standard database access in a single-
container system. Access to this port must be
enabled for all database clients, for example,
applications, application servers, end-user
clients, SAP HANA studio, and SAP HANA
cockpit 2.0.

Multitenant systems: As of SAP HANA 2.0


SPS 01, in a new multitenant system created
with one initial tenant database or an
upgraded single-container system, the first
tenant database is also accessible on port
3xx15.

Note As of SAP HANA 2.0 SPS 01, only


multitenant systems are supported.
SAP HANA indexserver None 30013 30013 – 3NN13 Yes Yes SQL/MDX access port for standard access to
Platform 39913 the system database of a multitenant system.
SAP HANA indexserver None None 30041– 3NN41 – Yes No SQL/MDX access port for standard access to
Platform 39998 3NN98 the tenant databases of a multitenant system.

Port numbers are assigned automatically


from the available port number range
according to availability at the time the
database is created. Administrators can also
explicitly specify which port numbers to use
when they create the tenant database.

The max range may be extended by reserving


the port numbers of further instances.
SAP HANA statisticsserver None 30017 30017 – 3NN17 Yes Yes Applicable only if the statistics server is
Platform 39917 running as a separate service This is only
relevant in single-container systems running
SAP HANA 1.0 SPS 08 or lower.

By default, the statistics server runs


embedded in the index server. For more
information, see SAP Note 2091313 .

Note The statistics server must run as an


embedded service in the system database and
tenant databases of a multitenant system.
SAP HANA HTTP(S) None 30033 30033 – 3NN33 Yes Yes Single port for all SAP HANA XS advanced
Platform 39933 application and services when routing is
done by host names instead of ports
(hostname routing)

Hostname routing is recommended in


production systems.

For more information about configuring


hostname routing, see SAP Note 2245631 .
SAP HANA HTTP(S) None 30032 30032 – 3NN32 Yes Yes In an XSA runtime environment, port used
Platform 39932 for the connection to the xscontroller-
managed Web Dispatcher for purposes of
user authentication if port routing is used
SAP HANA HTTP(S) None 30030 30030 – 3NN30 Yes Yes In an XSA runtime environment, port used
Platform 39930 for the connection to the xscontroller-
managed Web Dispatcher for purposes of
data access if port routing is used
SAP HANA HTTP(S) None None 51000 – 51000 – Yes No In an XSA runtime environment, port range
Platform 51500 51500 used for the connection from the
xscontroller-managed Web Dispatcher to the
xscontroller for access to application
instances if port routing is used
SAP HANA HTTP None 8000 8000 – 80NN Yes No SAP Web Dispatcher as part of the SAP
Platform 8099 HANA installation
SAP HANA HTTPS None 4300 4300 – 43NN Yes No SAP Web Dispatcher as part of the SAP
Platform 4399 HANA installation
SAP HANA daemon None 30000 30000 – 3NN00 No Yes
Platform 39900
SAP HANA nameserver None 30001 30001 – 3NN01 No Yes Internal port of the name server
Platform 39901
In a multitenant system, the name server runs
only in the system database.
SAP HANA preprocessor None 30002 30002 – 3NN02 No Yes Internal port of the preprocessor server
Platform 39902
In a multitenant system, the preprocessor
server runs only in the system database.
SAP HANA indexserver None 30003 30003 – 3NN03 No Yes Single-container system: Internal port of the
Platform 39903 index server in a single-container system
Multitenant system: As of SAP HANA 2.0
SPS 01, in a new multitenant system created
with one initial tenant database or an
upgraded single-container system, the first
tenant database also uses this port. Note As
of SAP HANA 2.0 SPS 01, only multitenant
systems are supported.
SAP HANA indexserver None None 30040 – 3NN40 – No No Internal port range for the index server of
Platform 39997 3NN97 tenant databases in a multitenant system

Port numbers are assigned automatically


from the available port number range
according to availability at the time the
database is created or a service is added.
Administrators can also explicitly specify
which port numbers to use when they create
a tenant database or add a service.

The max range may be extended by reserving


the port numbers of further instances.
SAP HANA indexserver None 30017 30017 – 3NN17 Yes Yes Port for internal SQL access to the system
Platform 39917 database of a multitenant system if SQL
access via external port 3xx13 is restricted.
SAP HANA scriptserver None 30004 30004 – 3NN04 No Yes Internal port of the script server in a single-
Platform 39904 container system
Optional. Not active by default. Note As of
SAP HANA 2.0 SPS 01, single-container
system are no longer supported.
SAP HANA scriptserver None None 30040 – 3NN40 – No No Internal port range for the script server of
Platform 30097 3NN97 tenant databases in a multitenant system

Port numbers are assigned automatically


from the available port number range
according to availability at the time the
database is created or the service is added.
Administrators can also explicitly specify
which port numbers to use when they create
a tenant database or add the service.

The max range may be extended by reserving


the port numbers of further instances.
SAP HANA docstore None None 30040 – 3NN40 – No No Internal port range for the docstore server of
Platform 30097 3NN97 tenant databases in a multitenant system
(available as of SAP HANA 2.0 SPS 01)

Port numbers are assigned automatically


from the available port number range
according to availability at the time the
database is created or the service is added.
Administrators can also explicitly specify
which port numbers to use when they create
a tenant database or add the service.

The max range may be extended by reserving


the port numbers of further instances.
SAP HANA statisticsserver None 30005 30005 – 3NN05 No Yes Internal port of the statistics server in a
Platform 39905 single-container system.

Applicable only if the statistics server is


running as a separate service. This is only
relevant in single-container systems running
SAP HANA 1.0 SPS 08 or lower. By default,
the statistics server runs embedded in the
index server. For more information, see SAP
Note 2091313 .

Note The statistics server must run as an


embedded service in the system database and
tenant databases of a multitenant system.
SAP HANA webdispatcher None 30006 30006 – 3NN06 No Yes Internal port of the web dispatcher
Platform 39906
In a multitenant system, the webdispatcher
service runs in the system database.
SAP HANA xsengine None 30007 30007 – 3NN07 No Yes Internal port of the XS classic server in a
Platform 39907 single-container system Note As of SAP
HANA 2.0 SPS 01, single-container system
are no longer supported.
SAP HANA xsengine None 30008 30008 – 3NN08 No Yes As of SAP HANA 2.0 SPS 01: Internal port
Platform 39908 of the XS classic server in the initial tenant
database of a new multitenant system or an
upgraded single-container system.
SAP HANA xsengine None 30014 30014 – 3NN14 No Yes Internal port of the XS classic server in the
Platform 39914 system database of a multitenant system
The xsengine service runs embedded in the
name server.
SAP HANA xsengine None None 30040 – 3NN40 – No No Internal port range for the XS classic server
Platform 30997 3NN97 running in the tenant databases of a
multitenant system

Port numbers are assigned automatically


from the available port number range
according to availability at the time the
database is created or the service is added.
Administrators can also explicitly specify
which port numbers to use when they create
the tenant database or add the service.

The max range may be extended by reserving


the port numbers of further instances.
SAP HANA xsuaaserver None 30031 30031 – 3NN31 No Yes Only if XS advanced runtime is installed
Platform 39931
Internal port used for the connection from the
client to the xscontroller-managed Web
Dispatcher (platform router) for purposes of
user authentication.

Also applicable for multitenant systems. The


xsuaaserver service runs in the system
database.
SAP HANA xscontroller None 30029 30029 – 3NN29 No Yes Only if XS advanced runtime is installed
Platform 39929
Internal port used for the connection between
the xs execution agent and the xscontroller.

Also applicable for multitenant systems. The


xscontroller service runs in the system
database.
SAP HANA xsexecagent None None Free Free No Yes Only if XS advanced runtime is installed
Platform
Also applicable for multitenant systems. The
xsexecagent service runs in the system
database.
SAP HANA XSA application None None 50000 – No No No Internal port range used in single-host
Platform instances 50999 scenarios for the connection from the
xscontroller-managed Web Dispatcher
(platform router) to the application instances.
SAP HANA XSA application None None 50000 – No No No Internal port range used in multiple-host
Platform instances 50499 scenarios for the connection from the
xscontroller-managed Web Dispatcher
(platform router) to the application instances
SAP HANA compileserver None 30010 30010 – 3NN10 No Yes Internal port of the compile server
Platform 39910
In a multitenant system, the compile server
runs in the system database.
SAP HANA R None 30019 30019 – 3NN19 No Yes Internal port used to connect to Rserve
Platform 39919
Optional. Not active by default.

In a multitenant system, the R server runs in


the system database.
SAP HANA diserver None 30025 30025 – 3NN25 No Yes Internal port used to connect to the SAP
Platform 39925 HANA Deployment Infrastructure (HDI)
server
SAP HANA diserver None None 30047 – 3NN40 – No No Internal port range used to connect to the
Platform 39997 3NN97 HDI servers of tenant databases in a
multitenant system

Port numbers are assigned automatically


from the available port number range
according to availability at the time the
database is created or the service is added.
Administrators can also explicitly specify
which port numbers to use when they create
the tenant database or add the service.

The max range may be extended by reserving


the port numbers of further instances.
SAP HANA indexservers None 30040 30040 – 3NN40 – 99 No No Optional, after n->1 recovery
Platform 39999
SAP HANA nameserver None 30101 30101– 3NX01 No Yes Used for log and data shipping from a
Platform 39901 primary site to a secondary site in a system
replication landscape (single-container
systems)
NX = Instance number plus 1 (01..99)
SAP HANA nameserver None 30102 30102 – 3NX02 No Yes Used for metadata communication between
Platform 39902 sites in a system replication landscape
(single-container systems)

NX = Instance number plus 1 (01..99)

Note As of SAP HANA 2.0 SPS 01, single-


container system are no longer supported.
SAP HANA nameserver None 40001 40001 – 4NN01 No Yes Used for log and data shipping from a
Platform 49901 primary site to a secondary site in a system
replication landscape (multitenant systems)
System DB port number plus 10,000
SAP HANA nameserver None 40002 40002 – 4NN02 No Yes Used for unencrypted metadata
Platform 49902 communication between sites in a system
replication landscape (multitenant systems)
System DB port number plus 10,000
SAP HANA nameserver Noe 40006 40006 – 4NN06 No Yes Used for encrypted metadata communication
Platform 49906 between sites in a system replication
landscape (multitenant systems)
System DB port number plus 10,000
SAP HANA indexserver None 30103 30103 – 3NX03 No Yes Used for log and data shipping from a
Platform 39903 primary site to a secondary site in a system
replication landscape (single-container
systems)
NX = Instance number plus 1 (01..99) Note
As of SAP HANA 2.0 SPS 01, single-
container system are no longer supported.
SAP HANA scriptserver None 30104 30104 – 3NX04 No Yes Used for log and data shipping from a
Platform 39904 primary site to a secondary site in a system
replication landscape (single-container
systems)

NX = Instance number plus 1

(optional) Note As of SAP HANA 2.0 SPS


01, single-container system are no longer
supported.
SAP HANA scriptserver None None 40040 – 4NN40 – 97 No Yes Used for log and data shipping from a
Platform 40097 primary site to a secondary site in a system
replication landscape (multitenant systems)

Tenant port number plus 10,000

(optional)
SAP HANA docstore None None 40040 – 4NN40 – 97 No Yes Used for log and data shipping from a
Platform 40097 primary site to a secondary site in a system
replication landscape (multitenant systems)

Tenant port number plus 10,000

(optional)
SAP HANA statisticsserver None 30105 30105 – 3NX05 No Yes Used for log and data shipping from a
Platform 39905 primary site to a secondary site in a system
replication landscape (single-container
systems)
NX = Instance number plus 1 (01..99)

Applicable only if the statistics server is


running as a separate service. This is only
relevant in single-container systems running
SAP HANA 1.0 SPS 08 or lower. By default,
the statistics server runs embedded in the
index server. For more information, see SAP
Note 2091313 .
SAP HANA xsengine None 30107 30107 – 3NX07 No Yes Used for log and data shipping from a
Platform 39907 primary site to a secondary site in a system
replication landscape (single-container
systems)

NX = Instance number plus 1 (01..99)

Applicable only if the XS classic server is


running
SAP HANA xsengine None 40014 40014 4NN14 No Yes Used for log and data shipping from a
Platform primary site to a secondary site in a system
replication landscape (multitenant systems)

System DB port number plus 10,000

Applicable only if XS classic server is


running in the system database
SAP HANA xsengine None None 40040 – 4NN40 – No Yes Used for log and data shipping from a
Platform 40997 4NN97 primary site to a secondary site in a system
replication landscape (multitenant systems)
Tenant port number plus 10,000

Applicable only if XS classic server is


running in the tenant database
SAP HANA indexservers None 30140 30140 – 3NX40 – 99 No No Used for log and data shipping from a
Platform 39999 primary site to a secondary site in a system
replication landscape (single-container
systems)

NX = Instance number plus 1 (01..99)

(optional, after n->1 recovery) Note As of


SAP HANA 2.0 SPS 01, single-container
system are no longer supported.
SAP HANA SOAP/HTTP None 50013 50013 – 5<NN>13 Yes Instance Agent
Platform 59913
SAP HANA SOAP/HTTPS None 50014 50014 – 5<NN>14 Yes Instance Agent
Platform 59914
SAP HANA SAP Host Agent saphostctrl 1128 1128 1128 Yes Yes None
Platform with
SOAP/HTTP
SAP HANA SAP Host Agent saphostctrls 1129 1129 1129 Yes Yes None
Platform with
SOAP/HTTPS
SAP HANA hdbrss None 30009 30009 – 3<NN>09 Yes Yes SAP Support (hdbrss) Not active by default,
Platform 39909 SAP Note 1058533 .
SAP HANA rdsyncserver None 30027 30027 – 3NN27 No Yes Internal port used by the SAP HANA server
Remote Data 39927 to connect to one or more remote data sync
Sync servers
SAP HANA rdsyncserver None 30028 30028 – 3NN28 Yes Yes Port used by synchronization clients running
Remote Data 39928 outside the SAP HANA system to connect to
Sync a remote data sync host
SAP HANA dpserver None 30011 30011 – 3NN11 No Yes Internal port used by the SAP HANA server
Smart Data 39911 to connect to one or more data provisioning
Integration servers
SAP HANA dpserver None No 30040 – 3NN40- No No Internal port range used by tenant databases
Smart Data 39997 3NN97 of a multitenant system
Integration
Port numbers are assigned automatically
from the available port number range
according to availability at the time the
database is created or the service is added.
Administrators can also explicitly specify
which port numbers to use when they create
the tenant database or add the service.

The max range may be extended by reserving


the port numbers of further instances.
SAP HANA dpserver None 5050 5050 5050 Yes Yes Port used by the data provisioning server to
Smart Data connect to the data provisioning agent using
Integration the TCP/IP protocol.
SAP HANA streamingserver None 30016 30016 – 3NN16 No Yes Internal port used by the SAP HANA server
Smart Data 39916 to connect to one or more smart data
Streaming streaming servers
SAP HANA streamingserver None 30026 30026 – 3NN26 Yes Yes Port used by streaming clients running
Smart Data 39926 outside the SAP HANA system (such as
Streaming custom-built external adapters) to connect to
a streaming node via the XML/RPC protocol
SAP SAP Host Agent saphostctrl 1128 1128 1128 Yes Yes None
NetWeaver with
Services SOAP/HTTP
SAP SAP Host Agent saphostctrls 1129 1129 1129 Yes Yes None
NetWeaver with
Services SOAP/HTTPS
SAP SAP Start sapctrl<NN> 50013 50013- 5<NN>13 Yes Yes On the SAP Central Services (SCS and
NetWeaver Service HTTP 59913 ASCS) instance the default instance is 01
Services making the default port 50113.
SAP SAP Start sapctrls<NN> 50014 50014- 5<NN>14 Yes Yes On the SAP Central Services (SCS and
NetWeaver Service HTTPS 59914 ASCS) instance the default instance is 01
Services making the default port 50114.
SAP SAP Web None None 0-65535 None Yes No Typical port for HTTP is 80. Has to be
NetWeaver Dispatcher - configured
Services HTTP port
SAP SAP Web None None 0-65535 None Yes No Typical port for HTTPS is 443. Has to be
NetWeaver Dispatcher - configured
Services HTTPS port
SAP Content Server None 1090 0-65535 None Yes No SAP Content Server
NetWeaver
Services
SAP Cache Server None 1095 0-65535 None Yes No SAP Content Server
NetWeaver
Services
SAP SAP None 50017 50017- 5<NN>17 No Yes None
NetWeaver Deployment 59917
Services Manager as part
of AS instance
SAP SAP None 50018 50018- 5<NN>18 No Yes None
NetWeaver Deployment 59918
Services Manager as part
of AS instance
SAP SAP None 50019 50019- 5<NN>19 No Yes None
NetWeaver Deployment 59919
Services Manager as part
of AS instance
SAP SL Controller None 50017 50017- 5<NN>17 No Yes None
NetWeaver Administrative 59917
Services communnication
SAP SL Controller None 50018 50018- 5<NN>18 No Yes None
NetWeaver GUI port 59918
Services
SAP SL Controller None 50019 50019- 5<NN>19 No Yes None
NetWeaver HTTP port 59919
Services
SAP SAPinst None 21212 0-65535 Free No No One of two ports for SAP installer.
NetWeaver
Services
SAP SAPinst None 21213 0-65535 Free No No One of two ports for SAP installer.
NetWeaver
Services
SAP SAPinst on IDM None 59975 0-65535 Free No No SAPinst on IBM iSeries needs these
NetWeaver AS400 iSeries additional ports. One of two ports for SAP
Services installer.
SAP SAPinst on IDM None 59976 0-65535 Free No No SAPinst on IBM iSeries needs these
NetWeaver AS400 iSeries additional ports. One of two ports for SAP
Services installer.
SAP SDT HTTP None 4239 0-65535 Free No No Used for communication between Software
NetWeaver server Delivery Tools (SDT) server and the browser
Services on the remote host.
SAP SAPup None 4240 0-65535 Free No No Used for communication between SDT
NetWeaver server and SAPup.
Services
SAP SDT server None 4241 0-65535 Free No No Used for communication between SDT
NetWeaver server and SUM GUI on the remote host.
Services

Multiplexer None 40000 40000- 4<NN>00 None None Internet Graphics Server (IGS) as part of
SAP 49900 application server instance.
NetWeaver
Services
SAP Portwatcher None 40001- 40001- 4<NN>01- None None Internet Graphics Server (IGS) as part of
NetWeaver (Clients) 40079 49979 4<NN>79 application server instance.
Services
SAP HTTP-ports None 40080- 40080- 4<NN>80- None None Internet Graphics Server (IGS) as part of
NetWeaver 40099 49999 4<NN>99 application server instance.
Services
SAP IPC dispatcher None 4363 0-65535 None Yes No Mobile client. Internet Pricing and
NetWeaver Configurator (IPC) for SAP NetWeaver 7.0
Services and SAP CRM 5.0.
SAP IPC dispatcher None 4444 0-65535 None Yes No Mobile client. Internet Pricing and
NetWeaver Configurator (IPC) version 3.0 and 4.0.
Services
SAP IPC data loader None 4445 0-65535 None No No Internet Pricing and Configurator (IPC)
NetWeaver version 3.0 and 4.0.
Services
Not active by default.
SAP IPC server None 9999 0-9999 9999, 9998, No No Counting down from 9999 for each server
NetWeaver … process. Internet Pricing and Configurator
Services (IPC) version 3.0 and 4.0.
SAP Design Time None 50015 50015- 5<NN>15 No No NetWeaver Development Infrastructure
NetWeaver Repository 59915 (NWDI). Relevant for SAP NetWeaver 7.0
Services and higher.
SAP PAW None 1099 0-65535 None Yes No Java RMI Server
NetWeaver Communication
Services Server

SAP PAW None 1089 0-65535 None Yes No None


NetWeaver Communication
Services Servlet
SAP Portal Runtime None 8050 0-65535 None Yes No Default port can collide with Internet
NetWeaver for Microsoft Communication Manager.
Services .NET
SAP Portal server None 8051 0-65535 None Yes No Default port can collide with Internet
NetWeaver node for Portal Communication Manager.
Services Development Kit
.NET
SAP liveCache sql30 7200 0-65535 None Yes No If there are multiple SAP MaxDB instances
NetWeaver on one host, all the instances share the
Services services.
SAP liveCache sql6 7210 0-65535 None Yes No If there are multiple SAP MaxDB instances
NetWeaver on one host, all the instances share the
Services services.
SAP SAP MaxDB sapdni72 7269 0-65535 None Yes No If there are multiple SAP MaxDB instances
NetWeaver on one host, all the instances share the
Services services.
SAP SAP MaxDB sdbnissl76 7270 0-65535 None No No If there are multiple SAP MaxDB instances
NetWeaver on one host, all the instances share the
Services services.
SAP Webtools SDB 7575 0-65535 None No No If there are multiple SAP MaxDB instances
NetWeaver on one host, all the instances share the
Services services.
SAP Master Data None 59950 50050- 5<NN>50 Yes No SAP NetWeaver Master Data Management
NetWeaver Server 59950 (SAP MDM)
Services
SAP Master Data None 59951 50051- 5<NN>51 Yes No SAP NetWeaver Master Data Management
NetWeaver Server HTTPS 59951 (SAP MDM)
Services
SAP Master Data None 59650 50050- 5<NN>50 Yes No SAP NetWeaver Master Data Management
NetWeaver Layout Server 59950 (SAP MDM)
Services
SAP Master Data None 59651 50051- 5<NN>51 Yes No SAP NetWeaver Master Data Management
NetWeaver Layout Server 59951 (SAP MDM)
Services HTTPS
SAP Master Data None 59750 50050- 5<NN>50 Yes No SAP NetWeaver Master Data Management
NetWeaver Import Server 59950 (SAP MDM)
Services
SAP Master Data None 59751 50051- 5<NN>51 Yes No SAP NetWeaver Master Data Management
NetWeaver Import Server 59951 (SAP MDM)
Services HTTPS
SAP Master Data None 59850 50050- 5<NN>50 Yes No SAP NetWeaver Master Data Management
NetWeaver Syndication 59950 (SAP MDM)
Services Server
SAP Master Data None 59851 50051- 5<NN>51 Yes No SAP NetWeaver Master Data Management
NetWeaver Syndication 59951 (SAP MDM)
Services Server HTTPS
SAP SAP NetWeaver None 2000 2000- Port Yes No SAP MDM requires three consecutive ports
NetWeaver Master Data 9997 for each repository.
Services Management
Server
SAP SAP NetWeaver None 2001 2001- Port+1 Yes No SAP MDM requires three consecutive ports
NetWeaver Master Data 9998 for each repository.
Services Management
Server
SAP SAP NetWeaver None 2002 2002- Port+2 Yes No SAP MDM requires three consecutive ports
NetWeaver Master Data 9999 for each repository.
Services Management
Server
SAP JMS/JDBC/File None 8200 0-65535 None Yes No Port used for interactive browser access to
NetWeaver Adapter Server configuration interface.
Services
Adapter does not belong to an SAP
NetWeaver Application Server system. It can
be installed on a host with SAP Process
Integration (SAP PI) server, or standalone.
Usually only one instance needed, because
individual JMS/JDBC and File Adapter
instances live inside one server process.

Default ports for multiple Adapter


Installations on same host: 8201, …

Rules for this adapter not yet implemented.


SAP JMS Adapter None 8210 0-65535 None No No Port for incoming data from SAP Process
NetWeaver Integration (SAP PI) server.
Services
SAP JDBC Adapter None 8220 0-65535 None No No Port for incoming data from SAP Process
NetWeaver Integration (SAP PI) server.
Services
SAP File Adapter None 8230 0-65535 None No No Port for incoming data from SAP Process
NetWeaver Integration (SAP PI) server.
Services
SAP Name server None 30001 30001- 3<NN>01 No No Available for TREX 6.1, TREX 7.0, TREX
NetWeaver 39901 7.1.
Services
SAP Preprocessor None 30002 30002- 3<NN><x>2 No No Multiple servers possible: <x>=server index
NetWeaver 39992 (0..9).
Services
Available for TREX 6.1, TREX 7.0, TREX
7.1.
SAP Index server None 30003 30003- 3<NN>x3 No No Multiple servers possible: x=server index
NetWeaver 39993 (0..9).
Services
Available for TREX 6.1, TREX 7.0, TREX
7.1
SAP Queue server None 30004 30004- 3<NN>x4 No No Multiple servers possible: x=server-index
NetWeaver 39994 (0..9).
Services
Available for TREX 6.1, TREX 7.0, TREX
7.1
SAP HTTP server None 30005 30005- 3<NN>05 No No Available for TREX 6.1, TREX 7.0, TREX
NetWeaver 39905 7.1.
Services
SAP GRMG service None 30006 30006- 3<NN>06 No No Optional. Available as of TREX 7.0.
NetWeaver (Heartbeat) 39906
Services
SAP RFC server None 30007 30007- 3<NN>07 No No Multithreaded RFC server. Available as of
NetWeaver 39907 TREX 7.0.
Services
SAP Cruiser None 30008 30008- 3<NN><x>8 No No Multiple servers possible: <x>=server index
NetWeaver 39908 (0..9). Available as of TREX 7.1.
Services
SAP Alert server None 30011 30011- 3<NN>11 No No Available as of TREX 7.0.
NetWeaver 39911
Services
SAP Backup server None 30017 30011- 3<NN>17 No No Optional. Available as of TREX 7.1.
NetWeaver 39917
Services
SAP Index server None 8351 0-65535 None No No Text Retrieval and Information Extraction
NetWeaver (TREX) 6.0
Services
SAP Queue server None 8352 0-65535 None No No Text Retrieval and Information Extraction
NetWeaver (TREX) 6.0
Services
SAP HTTP server None 8353 0-65535 None No No Text Retrieval and Information Extraction
NetWeaver (TREX) 6.0
Services
SAP Name server None 8355 0-65535 None No No Text Retrieval and Information Extraction
NetWeaver (TREX) 6.0
Services
SAP Preprocessor None 8357 0-65535 None No No Text Retrieval and Information Extraction
NetWeaver (TREX) 6.0
Services
SAP Monitoring None 8366 0-65535 None No No Text Retrieval and Information Extraction
NetWeaver (GRMG) (TREX) 6.0
Services
Availability monitoring in CCMS.
SAP SAProuter None 3299 0-65535 None Yes No None
NetWeaver
Services
SAP niping None 3298 0-65535 None Yes No SAP network test program
NetWeaver
Services
SAP SAPlpd printer 515 0-65535 None Yes No SAP printer spooler
NetWeaver
Services
SAP Secure Local Security None 34443 1024- Defined by No No Internal communication. Can be configured
Login Client Hub 65000 Configuration by the customer to avoid conflicts.
and
Port accepts connections only from local
detected host.
automatically

You might also like