Cloudsync Properties
Page 9 of 17

cloudscape.DataComm.url

Function

Enables or disables the standard JDK URL support for POST messages and thus makes SSL use possible. Cloudscape targets use HTTP POST messages to communicate with the Cloudsync source database for the refresh message and reply.

Cloudscape provides a choice of implementations for the processing of HTTP POST requests for the refresh command.

  • cloudscape.DataComm.url=false is the default if you are not using the servlet API for refresh requests. This implementation uses Java sockets rather than the standard URL support provided by the JDK. No SSL support is not possible.

    This choice was the default in releases prior to 3.0.

  • cloudscape.DataComm.url=true is the default when using the servlet API for refresh requests ( cloudscape.DataComm.listenType=servlet). In fact, this configuration works only when using the servlet API). It uses the standard JDK URL support for post messages. SSL support is possible.

    The optional configuration uses the standard URL support provided by the JDK.

NEW: The default value of this property set to true when using the servlet API for refresh requests is new in Version 3.6.

Setting this property to true allows:

  • Use of SSL (Secure Sockets Layer) for refresh messages.

    This requires that the server framework in which Cloudsync is embedded supports SSL (The Cloudconnector server framework supports SSL.). This also requires that the JVM the target is running in supports SSL or that the target's application includes a package that provides the SSL support. (Netscape Navigator, Microsoft Internet Explorer, JavaSoft Java plugin 1.2.2).

  • Use of Cloudscape synchronization with server frameworks that previously could not with the Cloudscape implementation of HTTP POST due to inconsistencies in the HTTP 1.0 specification for POST messages.

NOTE: When using the optional configuration (standard JDK URL support) targets may still run into JavaSoft bug 4212479, i.e. not having enough memory to send a large refresh message, unless the JVM uses HTTP 1.1 (e.g. Netscape Navigator, Microsoft Internet Explorer). In HTTP 1.1 the complete message is not required to be in memory before sending it.

The server framework may provide an HTTP tracing mechanism to determine if HTTP clients (e.g. Cloudsync targets) are talking HTTP 1.0 or HTTP 1.1. Cloudconnector provides such a facility.

NOTE: This property is valid only for target databases.

Default

false, unless cloudscape.DataComm.listenType is set to servlet, in which case the default is true.

Example

# in cloudscape.properties file at target
cloudscape.DataComm.url=true

CALL PropertyInfo.setDatabaseProperty(
    'cloudscape.DataComm.url', 'true')

CREATE PUBLICATION mypub
...
ADD TARGET DATABASE PROPERTY
    cloudscape.DataComm.url='true'

Scope

Database (publishable)

System

Dynamic or Static

Static. You must restart for the changes to take effect.