The routine can pass throughHttp://www.sybase.com/files/Technical_Documents/PanoramaRevGuide.zipDownload
In this document, SQL Anywhere 11 may appear elsewhere as SQL Anywhere Panorama.
Transfer Server
The transfer server easily integrates with existing firewall configurations and policies, making communication between mobile devices and mobile middleware servers easier. It also provides support mechanisms for load balancing and fault tolerance environments of mobile middleware servers. The transfer server creates a general communication architecture that communicates with mobile devices and between MobiLink, Afaria, and OneBridge.
Transfer Server Architecture
The transfer server is implemented through a set of web extensions, so a web server is required to run. The transfer server needs to start the connection between the LAN in the enterprise and the transfer server from the LAN in the enterprise.
The transfer server contains two web extensions: client extension and server extension. Client extension processes client requests that run applications on mobile devices. Server extension processing represents the requests sent from the backend server. The external starter-RSOE-runs on the same computer as the background server. The main function is to initialize an external connection to the transfer server on the background server. Each backend server has an external initiator.
On Windows, the web server we support is IIS 6. Because the Transfer Server is a web extension running on the web server, all communications are completed through HTTP (S), and you can easily integrate with existing enterprise firewall configurations and policies. The connection from the enterprise LAN to the transfer server is initialized through the enterprise LAN, which provides a safer deployment environment because the inner connection from DMZ to the enterprise LAN is not required.