Secure SAP Mobile Platform component communications
to prevent packet sniffing or data tampering. Different combinations of components
communicate with different protocols and different ports.
Note: As an alternative to reading all the topics on communication security, use Port Number Reference as a quick reference on all ports and information on how to change them.
Device-to-Platform Communications
Depending on your environment, devices typically connect to a Relay Server that is deployed to the DMZ (recommended). Alternatively, you can use a third reverse proxy or load balancers. However, in most SAP Mobile Platform deployments, a Relay Server is the first line of defense to the platform, acting as a proxy for the device, and facilitating interactions with SAP Mobile Platforms installed on the corporate LAN.
SAP Mobile Server and Device Push Notifications
Sometimes SAP Mobile Server must asynchronously notify a device application of changes it should be aware of. The mechanism for transmitting a push notification depends on the device type.
SAP Mobile Server and Data Tier Communications
SAP Mobile Platform uses the Adaptive Server Anywhere (ASA) cache database for its data tier. It also connects to a cluster, monitor, and domain log database.
SAP Mobile Server and SAP Control Center Communications
There are two different communication streams used to communicate with the SAP Control Center administration tool: one for communications with the SAP Control Center Web console, and one for the communications with the SAP Control Center X.X Windows service.
SAP Mobile Server and EIS Communications
Secure communication between SAP Mobile Server and any supported back-end depends on the direction of the interaction between these components.