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.

• EIS to Unwired Server – can communicate only via the DCN feature. DCN uses HTTP or HTTPS and all requests are also authenticated via the DCN User role. Sybase discourages the use of HTTP for DCN because credentials could be intercepted by network sniffers in HTTP. To secure the channel:

  • The EIS developer uses HTTPS to construct and send DCN requests to the listener.

  • No action is required if the default configuration is used. If you want to create a custom DCN security profile in SCC, you must manage the certificates, then uses Sybase Control Center to configure a new HTTPS listener.
    Note: If you are connecting with Online Data Proxy or DOE-C, then each type of connection requires it's own security profile, and the DCN listener profile should not be used in this case.
• Unwired Server to EIS – Unwired Server can perform operation replays. The manner in which those replays are communicated depends on the EIS and whether or not the administrator secures this channel in Sybase Control Center:
  • REST/SOAP uses BASIC authorized over HTTP or HTTPS.
  • REST/SOAP for SAP® uses BASIC/SSO2/X.509 authentication over HTTP or HTTPS.
  • JCo for SAP uses one of username/password, SSO2 tokens, or X.509 over SNC.
  • JDBCࡊ uses driver specific mechanisms to encrypt traffic. Review your JDBC driver documentation to learn how to configure this.

  For each of these EIS communication channels, you must configure the secure protocol. Otherwise, the user's credentials can potentially be exposed network sniffers. Once you have configured the secure channel, always ensure that EIS server certificates are imported into the Unwired Server truststore to allow this communication.