® Sync technology (ISync) allows for the use of SSL to connect from the client to the DB2 Everyplace
Sync server, if both client and server are SSL-enabled in a compatible configuration.
Using DB2 Everyplace Java Sync Client for Derby
When using the pure Java
® Apache Derby ISync implementation, there are no ISync-specific SSL configuration steps required. The IBM
Apache Derby Java
ISync provider assumes that the client platform has already been configured to support the SSL outbound connections.
Refer to Configuring SSL for the platform
for more information.
The Apache Derby synchronization codepage configuration isync.encoding values of ASCII
, or UTF8
are not supported when using the DesktopEE Java
runtime environment. The default code page for your client platform is used if the isync.encoding property is not set and functions as expected. If UTF-8 or ASCII encoding must be used, then the Java
5 runtime environment is required.
Using DB2 Everyplace native synchronization
When using the native DB2 Everyplace
native database and synchronization implementation, some operating system-specific tasks are required to prepare the client for synchronization with the DB2 Everyplace
Sync server. Refer to Secure Sockets Layer and DB2 Everyplace mobile devices
in the DB2 Everyplace
These configuration steps can be applied to the device as well as the desktop.
Parent topic: Configuring platform security