Problem: After installation, Listener could not be started, or Service could not be started messages appear.
Explanation: This may indicate your SAP Mobile Platform configuration includes duplicate port numbers. This can happen for a variety of reasons; for example, if an application or service is offline during the installation process, the installer does not detect the reserved port number.
Solution: Change the SAP Mobile Platform component port numbers as needed post-installation, using information in Port Number Reference.
SAP Control Center Could Not be Started
Problem: After installation, SAP Control Center could not be started. The agent bootstrap thread logs error messages in agent.log such as the ones below. In case of a port conflict on the RMI agent port (default 9999) or the Repository DB port (default 3638), the SAP Control Center service startup fails.
RMI Agent:
[Agent Bootstrap Thread] - Failed to start rmi registry.
Messaging:
[Agent Bootstrap Thread] - Messaging provider failed to fully start.
Web Container:
[Agent Bootstrap Thread] - failed....java.net.BindException: Address already in use: JVM_Bind
Repository DB:
[Agent Bootstrap Thread] - Failed to connect to dataserver engine.
Explanation: This error can occur for a variety of reasons; for example, if an application or service is offline during the installation process, the installer does not detect the port number is in use.
Solution: Change the SAP Control Center component port number as needed post-installation, using information in Port Number Reference.
Port Number Reference
Change SAP Mobile Platform component port numbers after installation, if necessary.
Proceed with caution when changing port numbers because the change might impact other configuration files that point to that port. You need to be aware of the default SAP Control Center port numbers so you do not accidentally use these ports when you change SAP Mobile Platform ports. You can change some SAP Control Center default ports, but, in some cases, you should not.
Note: To make SAP Mobile Server port number changes, temporarily stop the other service consuming those ports. Use SAP Control Center to make the changes, then restart SAP Mobile Server.
Note: Port numbers 5701, 5702, and 5011 should be reserved ports.
Port Description Default
Port
Instructions for Changing
Data tier (CDB) server
Port number for the da-ta tier that manages transactions between the enterprise informa-tion system and mobile devices.
5200 Do not change the CDB port.
Management
Default is recommended. No change is required.
HTTP ports HTTP port number on which SAP Mobile
Configure in SAP Control Center by se-lecting Configuration, clicking the Web Container tab and entering a new DCN port or secure DCN port, as required.
See Configuring Web Container Proper-ties in SAP Control Center for SAP Mo-bile Platform online help.
Port Description Default
Configure in SAP Control Center by se-lecting Configuration. In the Compo-nents tab, select Replication or Messag-ing, click Properties and enter a new synchronization port, as required.
Note: If there is a conflict for port 2480 or 2481, SAP Mobile Server will not start, and you cannot use SAP Control Center to modify them. To correct the problem, you must temporarily stop the service that uses the conflicting port, then start SAP Mobile Server.
For replication payloads, see Configuring Replication Subscription Properties in SAP Control Center for SAP Mobile Platform online help.
For messaging payloads, see Configuring Messaging Properties in SAP Control Center for SAP Mobile Platform online help.
Cannot be changed in SAP Control Cen-ter.
Use the SMP_HOME\Servers
\Messaging Server\Bin
\AdminWebServices-Tool.exe command line tool to change the messaging service Web serv-ice port. This tool has built in online help describing how to use the tool. From the command prompt run:
SMP_HOME\Servers\Messag-ing Server\Bin > Admin-WebServicesTool.exe set=<port> restart
Port Description Default numbers of which to be aware, when
• 9999 – default RMI agent port. The port is set in:
SCC_HOME\services\RMI
\service-config.xml
• 2100 – default JMS messaging serv-ice port. The port is set in:
SCC_HOME\services\Mes- saging\service-con-fig.xml
• 3638 – default SAP Control Center repository database port. The default port is set in:
SCC_HOME\services
\SccSADataserver\serv-ice-config.xml
• 8282, 8283 – default Web container ports. The default ports are set in:
SCC_HOME\services\Em-beddedWebContainer
\service-config.xml Before you make any changes to these files, stop SAP Control Center X.X serv-ice. Start the service after you complete the changes. If any of the subsystems fail to start, check the SAP Control Center agent.log for error messages.
Relay server Port numbers on which Relay Server listens for
Change the value for the cluster in SAP Control Center for SAP Mobile Platform.
You can then generate the file and transfer it to the corresponding SAP Mobile Serv-er host.
See Setting Relay Server General Prop-erties in SAP Control Center for SAP Mobile Platform.
Port Description Default
7003 For information on network adapter and port configuration options, see the fol-lowing topics in System Administration
• Configuring Agentry Client-Server Communications
• Agentry Server: [ANGEL Front End]
Configuration Section for internal use by SAP Mobile Platform
Do not use these special port numbers for any purpose. These ports differ from Windows reserved ports (1-1023).
Note: Even if the installer does not detect a conflict at install time, Windows may later use ports in the 1024-64K range for other purposes. Read Microsoft docu-mentation to determine how to reserve SAP Mobile Platform ports. Otherwise, you may experience intermittent prob-lems when starting up platform services due to Windows using these ports for some other purpose at the same time.