Secure Unwired 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 deployed to the DMZ (recommended). Alternatively, you can use a third reverse proxy or load balancers. However, in most Unwired Platform deployments, a Relay Server is the first line of defense to the platform by acting as a proxy for the device, and facilitating interactions with Unwired Servers installed on the corporate LAN.
Unwired Server and Device Push Notifications
Sometimes Unwired 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.
Unwired Server and Data Tier Communications
Unwired Server uses two synchronization databases for its data tier: one for replication and one for messaging. It also connects to a cluster, monitor, and domain log database.
Unwired Server and Sybase Control Center Communications
There are two different communication streams used to communicate with the Sybase Control Center administration tool: one for communications with the Sybase Control Center web console, and one for the communications with the Sybase Control Center X.X Windows service.
Unwired Server and EIS Communications
Secure communication between Unwired Server and any supported back-end depends on the direction of the interaction between these components.