Puertos utilizados sap
- 1. TCP/IP Ports Used by SAP Applications Date of issue: 05.10.2006
- 2. SAP AG Neurottstraße 16 69190 Walldorf Copyright Germany T +49/18 05/34 34 24 © Copyright 2006 SAP AG. All rights reserved. F +49/18 05/34 34 20 www.sap.com No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Notices The information contained here in may be changed without prior notice. SAP AG provides this publication "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability or fitness for a particular purpose. SAP AG assumes no responsibility for any errors or omissions in these materials. SAP may make changes in the product and/or programs described in this publication at any time without notice. Trademarks Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corp. in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. J2EE™ is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. All other product and service names mentioned are the trademarks of their respective owners. © SAP AG 2006 2 Network Ports used by SAP
- 3. Contents 1 Introduction ....................................................................................................................... 4 1.1 Status and Version History .......................................................................................... 4 1.2 Who Should Read This Document .............................................................................. 4 1.3 Background Information .............................................................................................. 4 1.4 Source and Feedback ................................................................................................. 4 2 Port Table .......................................................................................................................... 5 2.1 SAP Applications ......................................................................................................... 5 2.2 “Will Not be Used” Ports ............................................................................................ 12 3 Table Description............................................................................................................ 13 4 Details on Selected Servers........................................................................................... 14 4.1 SAP Web AS ............................................................................................................. 14 © SAP AG 2006 3 Network Ports used by SAP
- 4. 1 Introduction This paper provides a comprehensive list of ports used by SAP software. It can be useful for planning and configuring your network infrastructure according to SAP requirements. It can also be used to identify specific SAP network traffic for monitoring, prioritization or security purposes. 1.1 Status and Version History This paper is subject to continuous upgrade. Please check: http://service.sap.com/security for the most recent version. 1.2 Who Should Read This Document Use this paper for planning, monitoring and troubleshooting the networking infrastructure for your SAP systems. It is written for anyone dealing with networking aspects of SAP systems. This includes: System architects Network planners and operators Network providers System integration consultants 1.3 Background Information For a list of reserved ports, see http://www.iana.org/assignments/port-numbers. Server ports must not be used by any other program running on the same host, otherwise the system will not operate correctly. FAQ: Why are there no client ports in this table? Client ports are allocated automatically by the operating system. No SAP software specifies a certain port for the client side of a connection. 1.4 Source and Feedback You can find this document and related ones on technical infrastructure topics in the SAP Service Marketplace at http://service.sap.com/security. If you do not have access to that Web site send email to security@sap.com. Please use this address also for any kind of feedback regarding this document. © SAP AG 2006 4 Network Ports used by SAP
- 5. 2 Port Table The following table list SAP applications and functions listening on a port for incoming network requests. A description of the fields can be found in chapter 3. 2.1 SAP Applications Port Number / External Fixed Service Name Range Service Default Comment (min-max) Rule NetWeaver Application Server ABAP including Internet Connection Manager (ICM) Dispatcher 32NN 3200 3200-3299 SAP Dispatcher, used by SAP GUI for + + Windows and Java sapdpNN sapdp00-sapdp99 Gateway 33NN 3300 3300-3399 SAP gateway, used for CPIC and RFC + + communication sapgwNN sapgw00-sapgw99 ICM HTTP 80NN 8000 Free The usual port for HTTP is 80. You can + configure the system to use port number 80 after installation. ICM HTTPS 443NN Not active Free The port is not configured during installation. The usual port for HTTPS is (convention for + 443. If you want to use HTTPS, you multiple must configure it manually. instances) ICM SMTP 25 Not active 25 The port is not configured during installation. The usual port for SMTP is (no other port + 25. If you want to use SMTP, you must generally supported configure it manually. Only one instance by SMTP) per host should offer SMTP service. Message Server 36NN 3600 Free Only CI (central instance) Service names can be reassigned in + /etc/services to an arbitrary value after sapmsSID sapmsC11 sapms<any SID> installation. Message Server HTTP 81NN 8100 Free Only CI (central instance) + Can be used to retrieve system information via HTTP Message Server 444NN Not active Free Only CI (central instance) The port is not configured during HTTPS (convention for + installation. multiple instances) Purely internal ports Dispatcher 32NN/UDP 3200/UDP 3200-3299/UDP Only used on local host for signaling dispatcher, never seen on the network Gateway 33NN/UDP 3300/UDP 3300-3399/UDP Only used on local host for signaling + gateway, never seen on the network ICM Admin detected 65000 or next 65000 or less Internal communication. Automatically uses the first free port from 65000 automatically free lower downwards. Port accepts connections port only from localhost. © SAP AG 2006 5 Network Ports used by SAP
- 6. Port Number / External Fixed Service Name Range Service Default Comment (min-max) Rule SAP NetWeaver Application Server Java J2EE Dispatcher HTTP 5NN00 + 50000 50000-59900 NN = Instance number (00…99) HTTP over SSL 5NN01 + 50001 50001-59901 IIOP initial context 5NN02 + 50002 50002-59902 IIOP over SSL 5NN03 + 50003 50003-59903 P4 5NN04 + 50004 50004-59904 P4 over HTTP 5NN05 50005 50005-59905 + tunneling P4 over SSL 5NN06 + 50006 50006-59906 IIOP 5NN07 + 50007 50007-59907 Telnet 5NN08 + 50008 50008-59908 JMS 5NN10 + 50010 50010-59910 J2EE Server ( internal ports) Server Join Port 5NN20 + x*5 50020 50020-59995 X = 0, 1, 2, 3, ...15 (number of server) + (server 0) Server Debug Port 5NN21 + x*5 50021 50021-59996 X = 0, 1, 2, 3, ...15 (number of server) + (server 0) Central Services for Java (Separate instance, default instance number 01) Enqueue Server Enqueue Server Port 32NN 3201 Provides locking services for AS Java sapdpNN 3200-3299 NN = Instance number (00…99) enque/encni/port Enq. Replication 33NN 3301 3300-3399 Replication of enqueue data for high availability sapgwNN NN = Instance number (00…99) Releases up to NW2004s enque/encni/repl_port Enq. Replication 5NN16 50116 50016, …, 59916 Replication of enqueue data for high availability NN = Instance number (00…99) enque/encni/repl_port Starting with NW2007 Message Server Message Server Port 36NN 3601 NN = Instance number (00…99) 3600-3699 rdisp/msserv HTTP 81NN + 8101 8100-8199 ms/http_port HTTPS 444NN + Not active 44400-44499 ms/https_port © SAP AG 2006 6 Network Ports used by SAP
- 7. Port Number / External Fixed Service Name Range Service Default Comment (min-max) Rule SAP NetWeaver AS Administrative Services Host Control Service SAPHostControl 1128 (+) 1128 50013-59913 + SAP Landscape Host integration service SAPHostControlS 1129 (+) 1129 50013-59913 + NN = Instance number (00…99) Start Service Start Service 5NN13 50013 NN = Instance number (00…99) + 50013-59913 + HTTP sapctrlNN Start Service 5NN14 50014 NN = Instance number (00…99) + 50014-59914 + HTTPS sapctrlsNN Installation & upgrade tools SDM 5NN17 50017 Software deployment manager Only CI (central Instance) as part of Web AS 5NN18 50018 + NN = Instance number (00…99) instance 5NN19 50019 Only NW04 and NW2004s SL Controller 5NN17 50017 Used for patch and upgrade services 5NN18 50018 *17: Administrator Communication 5NN19 50019 + *18: GUI port *19: http port NN = Instance number (00…99) NW2007 SAPinst 21212 21212 Free 21213 21213 SAPinst on 59975 59975 Free SAPinst on IBM iSeries needs these IBM AS400 iSeries 59976 59976 additional ports. Upgrade Free - Monitoring 4238 4238 - UA-server (HTTP) 4239 4239 - R3up-process 4240 4240 - UA-server 4241 4241 Utilities SAProuter 3299 + 3299 Free SAP Web Dispatcher Free Currently there is no installation procedure for SAP Web Dispatcher. - HTTP port chose freely + Typical port for HTTP is 80. - HTTPS port chose freely Typical port for HTTPS is 443 niping 3298 + 3298 Free SAP network test program SAPlpd 515 515 Free SAP printer spooler + printer RDBMS (Database Systems) MS SQL Chose freely 1433 1024 – 5000 Port can be statically or dynamically + allocated. If dynamic, port 1434/udp is also required. Oracle listener 1527 1527 Free configured in listener.ora and © SAP AG 2006 7 Network Ports used by SAP
- 8. Port Number / External Fixed Service Name Range Service Default Comment (min-max) Rule tnsnames.ora IBM Conflicts with SAP J2EE Engine with instance number 00. DB6 (AIX) 50000 50000 Free See relevant documentation on how to DB2 (OS/400) 4402 / as-edrsql 4402 change this DB6 default port. liveCache (MaxDB) 7200 / sql30 7200 Free In case of multiple MaxDB instances on one host the services are shared by all (formerly know as 7210 / sql6 7210 instances. SAP DB) 7269/sapdni72 + 7269 7270/sdbnissl76 + 7270 7575 / SDB + 7575 Webtools © SAP AG 2006 8 Network Ports used by SAP
- 9. Port Number / External Fixed Service Name Range Service Default Comment (min-max) Rule NWDI (NetWeaver Development Infrastructure) DTR 5NN15 50015 Design Time Repository (NW2004s and later) NN = Instance number (00…99) SAP NetWeaver AS Administrative Services ITS (Internet Transaction Server) AGate 39N0-39NM / 3900 – 390M Free N determined at setup so that range free M = No agates –1 sapavw00_Inst Inst = Name of ITS Instance MM 39N9 / 3909 Free Mapping Manager sapavwmm_Inst IGS (Internet Graphics Server) as part of Web AS instance Multiplexer 4NN00 Portwatcher (Clients) 4NN01-4NN79 HTTP-ports 4NN80-4NN99 XI (SAP Exchange Infrastructure) JMS/JDBC/File 8200 8200 Free Port used for interactive browser access to configuration interface. Adapter Server (8201, … for (Rules for this Adapter does not belong to an SAP Web multiple Adapter adapter not AS system. It can be installed on a host Installations on + yet with XI server, or standalone. same host) implemented) Usually only one instance needed, because individual JMS/JDBC and File Adapter instances live inside one serve process. JMS Adapter Chose freely 8210 Free Port for incoming data from XI server. JDBCAdapter Chose freely 8220 Free Port for incoming data from XI server. File Adapter Chose freely 8230 Free Port for incoming data from XI server. IPC (NW05 and CRM 5.0) (Internet Pricing and Configurator) IPC Dispatcher 4363 + 4363 Free Mobile client IPC Version 3.0 and 4.0 (Internet Pricing and Configurator) IPC Dispatcher 4444 + 4444 Free Mobile client IPC data loader 4445 Not active Free IPC Server 9999, 9998, … 9999 Free Counting down from 9999 for each server process. © SAP AG 2006 9 Network Ports used by SAP
- 10. Port Number / External Fixed Service Name Range Service Default Comment (min-max) Rule TREX (Text Retrieval and Information Extraction) Name Server 3NN01 30001 30001-39901 NN = TREX Instance Pre Processor 3NNx2 30002 30002-39992 multiple servers possible x=server-index (0,1,2,…,9) Index Server 3NNx3 30003 30003-39993 multiple servers possible x=server-index (0,1,2,…,9) Queue Server 3NNx4 30004 30004-39994 multiple servers possible x=server-index (0,1,2,…,9) HTTP Server 3NN05 30005 30005-39905 GRMG service 3NN06 30006 30006-39906 (Heartbeat) MDM (Master Data Management) Admin Console 20003 20003 Fixed Communication between Admin Console + + application and MDM server Server to Server 20004 20004 Fixed Inter Server communication + (master/slave) Admin Console 20005 20005 Fixed Communication between Admin Console + + application and MDM server Import Manager 20006 Communication between MDM Import (+) 20006 Fixed + Manager Service and its clients Syndicator Service 20007 Communication between MDM (+) 20007 Fixed + Syndicator Service and its clients Layout Server 31596, 31597, 31596, Fixed Communication for print publishing 31604 + 31597, 31604 + between MDM Layout Server and its clients Layout Server 31602 31602 Fixed Communication for print publishing Quark Express + + between MDM Layout Server and Quark Express plugin Layout Server 31603 31603 Fixed Communication for print publishing Adobe InDesign + + between MDM Layout Server and Adobe InDesign plugin Layout Server 31596 31596 Fixed Communication for print publishing + + between MDM Layout Server and its clients MDM Server 2000-2002 2000-2002 2000-9997 3 consecutive ports in this range are + required per each repository TREX 6.0 (Text Retrieval and Information Extractio Name Server 8355 8355 Free Pre Processor 8357 8357 Free Index Server 8351 8351 Free Queue Server 8352 8352 Free Http Server 8353 8353 Free Monitoring (GRMG) 8366 8366 Free Availability monitoring in CCMS © SAP AG 2006 10 Network Ports used by SAP
- 11. Port Number / External Fixed Service Name Range Service Default Comment (min-max) Rule Content Server Content Server 1090 + 1090 Free Cache Server 1095 + 1095 Free CRM CSDM 20201 + Free Central Software deployment manager Exchange Groupware 135 / DCE DCOM uses port 135 for the Service Control Manager which allocates a free Connector (DCOM) port for the application. Lotus Domino The range comprises 4 Instances - Connector 62026 – 62029 + 62026–62029 Free xxx26 for instance 1 up to - Proxy 62126 - 62129 62126-62129 Free xxx29 for instance 4. PAW (Performance Assessment Workbench of Knowledge Warehouse) PAW Communication 1099 1099 Free Java RMI Server + Server PAW Servlet Engine 1089 + 1089 Free Business One http Free + 80 Free IIS, configurable port on client side ODBC (e.g. MSSQL) Free 1433 Free Port can be statically or dynamically allocated. If dynamic, port 1434/udp is also required. DCOM 135 / DCE Connection to license server. DCOM uses port 135 for the Service Control Manager which allocates a free port for the application. © SAP AG 2006 11 Network Ports used by SAP
- 12. 2.2 “Will Not be Used” Ports The following ports will not be used by standard SAP applications. They are intended for use with partner or other applications co-running on the same computers as SAP applications. To avoid any possible port number conflicts these additional applications are requested to make use of these “will not be used” ports. Port Number / External Fixed Service Name Range Service Default Comment (min-max) Rule Will Not be Used by SAP 63000 - 65535 These ports will not be used by standard + SAP applications © SAP AG 2006 12 Network Ports used by SAP
- 13. 3 Table Description Service The name or identifier of the network services provided by SAP programs. Port Number / Service Name For each service, we list the port number associated with this service and if existent the rule used to compute port number and service name. Some ports have corresponding entries in /etc/services. If this is the case, we also list the service name. Some services use fixed port numbers, however most use a number that depends on some other value to allow multiple instances of the program running on the same host. Variable name convention (see below for explanation): NN is the instance number of the SAP Web AS instance (e.g. 32NN /sapdpNN means 3200 / sadp00 for instance no. 00) SID is the three letter system ID (e.g. sapmsSID means sapmsC11 for SAP system C11) All ports are TCP ports except where UDP is indicated. UDP is used only for internal communication ON THE SAME HOST, never for communication across a network. Most port numbers are configured by the installation procedure. In this case, the port number listed in the table is the one used by the installation procedure. Sometimes the installation procedure allows changing the port number. In this case, the value is the one presented as a default by the installation procedure. Other ports are not configured by the installation procedure. This is because the corresponding service can be used only after other manual configuration steps that cannot be carried out by the installation procedure. If a port is not automatically configured, this is indicated in the comment. If you want to use the corresponding service, you have to set the port manually. External The most relevant ports are the ones used by programs that connect to the system, for example, SAP GUI or Web browser or other programs that communicate with the system. Those ports are labeled "external" – there are relatively few of them. The other ports are used for internal communication between components of the system. Default The default port numbers are used all defaults presented by the installation procedure are accepted. Range The port range indicates the minimum and maximum port number for this service. Not all numbers in this range may be valid ports for this service. Fixed The column labeled "fix" indicates that SAP does not support changing this port number. If a conflict occurs, chose a different instance number to avoid occupied ports. Comments If appropriate, a brief explanation on the service, the port numbers used or the installation and configuration options. © SAP AG 2006 13 Network Ports used by SAP
- 14. 4 Details on Selected Servers 4.1 SAP Web AS What are a System, an Instance and all that? An SAP Web AS system consists of one or more instances. An instance is a "server" in the sense that a user can connect to every instance individually. An instance typically consists of many running operating system processes that are connected by shared memory, TCP/IP connections on the local host and other means. All instances belonging to the same system are connected to the same RDBMS. A system has a three-letter name, the system identifier (SID). Instances of a system do not have to be configured identically; instead, different instances may offer different services. Some services are unique in a system, i.e. only one instance is configured to offer these services (e.g. Enqueue, Message Server). A system may have an instance called "central instance", which offers many of these unique services. Every instance has a number between 00 and 99, the so-called instance number (abbreviated by InstNr or NN to indicate the numerical value). The installation default is 00. If more than one instance is installed on the same host, they MUST have different InstNr. InstNrs are usually part of the Port numbers to ensure that there is no conflict between instances. An instance uses a number of TCP and UDP ports for internal communication. These ports are usually not configurable and not relevant for the "outside world". They are interesting only in the rare case when a conflict with other software on the same host occurs. The InstNr for an instance can be chosen freely. Different instances belonging to the same system can have different InstNrs. The InstNr is chosen during the installation. Most port numbers depend directly on the InstNr as shown by the table below. Some of the port numbers are merely suggested values that can be overridden during the installation procedure, some are generated automatically but can be changed using configuration tools after the installation as completed and some are fixed in the sense that SAP does not support changing these ports in any way. Web AS Kernel The 80NN, 443NN port convention for HTTP(S) ports of the ICM does not comply with the spirit of the HTTP standard, which specifies port 80 for HTTP. We have chosen this convention to make sure that SAP Web AS is able to start up correctly after installation. For productive servers, especially in the Internet, you should change these values. In the future, the installation procedure will already have an option to change these ports. The port scheme for J2EE server processes implies a maximum of 7 server processes per instance. If this should not be sufficient, the port scheme can easily be modified to allow more server processes. J2EE Engine HTTP communication is handled by ICM, which forwards requests to J2EE engine. Therefore, the HTTP port is used only for internal communication, and the HTTPS port is not used at all. J2EE server handles other protocols, e.g. RMI, directly. Standalone J2EE Engine The J2EE engine can also be installed standalone without the Kernel part of the SAP Web AS. This implies that J2EE Engine now handles HTTP and HTTPS requests directly. © SAP AG 2006 14 Network Ports used by SAP