Developing custom logic

Voraussetzungen

• Compilation should be performed using JDK1.3 to ensure compatibility with the DB2 Everyplace Sync Server.
• For compilation, the CLASSPATH must include $DSYINSTDIR/Server/lib/dsysvr.jar.
• In order to utilize the custom logic classes implemented, the package(s) in which they reside must be added to the classpath on the server(s) on which they will run. In the event that a mapped class is not located, an error (DSYG013E) will be logged in DSY.LOG, and the affected synchronization or replication will not proceed.

Vorgehensweise

1. Create the custom logic classes

   You can use whatever development environment that you desire to write the Java source files. These classes should be in a package that you create using a naming convention that suites your needs. Since different custom logic may be required for different subscriptions, and possibly even for different tables within the same subscription, care should be taken to ensure uniqueness in the naming convention for the custom logic classes.

   For more information, the custom logic API is located in %DSYINSTDIR%\doc\<lang>\javadoc

   where <lang> is the country code
   

2. Implement the custom logic classes

   You can implement custom logic through the Mobile Devices Administration Center or by utilizing the XML Scripting tool. In both of these implementations, you can enable policy types and add or change custom logic policies.

   The following windows in the Mobile Devices Administration Center have the Custom logic page available:

   • Create JDBC subscription
   • Create DataPropagator subscription
   • Change JDBC subscription
   • Change DataPropagator subscription
   • Advanced upload subscription

Zugehörige Tasks

• Enabling the sample application for custom logic
• Using the custom logic sample application

Zugehörige Konzepte

• Custom logic