Encrypting DCN Connections

Developers are responsible for the construction of data change notification (DCN) requests transmitted from the enterprise information server (EIS) . However, an administrator must enable and configure the HTTPS port for DCN connections, when the DCN goes directly to Unwired Server and does not use a relay server.

If you are using a relay server, then you only need to enable HTTPS on the RSOE using the relayserver.protocol property in the relayserver.properties file. See System Administration > Environment Setup > Relay Server Setup and System Administration > System Reference > Configuration Files > Relay Server Configuration Files > Relay Server Properties (relayserver.properties) Configuration File.

Otherwise, for direct DCN connections to Unwired Server, administrators configure a security profile.

  1. In Sybase Control Center for Unwired Platform, expand the server node in the corresponding cluster.
  2. In the left navigation pane, click Server Configuration.
  3. In the right administration pane, click General.
  4. In the Communication Ports subtab, expand Hide secure data change notification ports, and:
    1. Optionally enter a new port number. The default is 8001.
    2. Enable the desired secure ports. If the port value in the Status column is disabled, click the field and select Enabled.
    3. Enter a maximum thread count for each port. The value must be a positive integer. The default is 30.
    4. Select an appropriate security profile for the port by clicking the corresponding profile name in the SSL Security Profile column, and selecting a profile.
  5. If you plan to use a new certificate for this port, create a new certificate, optionally sign it, import it into the Unwired Server keystore (see Configuring Unwired Server Administration Certificates, then use the new 104 Sybase Unwired Platform certificate when creating the security profile. Then, assign the security profile to the appropriate DCN ports.
  6. If necessary, increase the Max Thread default property value.
  7. Save the changes and restart the server.
  8. Repeat on all particpating servers in the cluster