The relay server outbound enabler (RSOE) runs as an Unwired Server process and manages synchronization requests from a relay server.
Connect, transfer, and disconnect activities of the RSOE are driven on
demand by the clients and backend servers. The connections the RSOE facilitates between relay and backend servers are bidirectional. That is, the RSOE, after retrieving information regarding the available relay servers, creates the
up and down channel pairs with each relay server:
- Up channel –
the relay server forwards client requests to the RSOE using the established up channel (either HTTP or HTTPS).
The outbound enabler then relays the client request to the backend Unwired Server component (replication based synchronization or messaging based synchronization).
- Down channel – once the outbound enabler receives the response from the Unwired Server, it forwards the
response back to the relay server. The relay server relays the
response to the client.
As an Unwired Server process, RSOE always starts when Unwired Server starts. Unwired Server monitors the process to ensure it is available -- if for any reason an RSOE fails, Unwired Server restarts it automatically. At this time, the RSOE must be manually restarted.
Note: Sybase recommends that three RSOE processes be added to each synchronization port (RBS and MBS types) you define as part of an Unwired Server farm for a relay server.