8.5 Everyplace Synchronization Server


8.5 Everyplace Synchronization Server

Everyplace Synchronization Server is the component provided by WebSphere Everyplace Access for synchronizing data between several types of data repositories and the pervasive devices. It is intended to allow the mobile devices to synchronize personal information data (PIM) and relational database management systems (RDMS) with the back-end repositories.

The Synchronization Server includes adapters for synchronizing with databases such as Lotus Notes, Microsoft Exchange and DB2 or other JDBC-compliant databases.

Synchronization Server uses the Java 2 (J2EE) platform and SyncML V1.0 protocol between the server and the client devices. The devices can use any connection type that can support TCP/IP.

Synchronization Server is a set of servlets that are installed as enterprise applications in WebSphere Application Server. These servlets are as follows .

  • The SyncML servlet handles SyncML requests from pervasive devices.

  • The Relay servlet handles requests from desktops using TrueSync Plus.

  • The DB2 Everyplace Sync Server is the DB2 Everyplace synchronization engine and allows the synchronization with JDBC-compliant databases. The Mobile Devices Administration Center, shown in Figure 8-12, is used to administer users, filters and subscriptions.

    click to expand
    Figure 8-12: The Mobile Devices Administration Center

The adapters provided by Synchronization Server convert data into a common format in order to synchronize it between the back-end repositories and the devices. The adapters provided by Synchronization Server are as follows.

  • Lotus Domino Adapter: provides an interface for the Synchronization Server to access enterprise Lotus Domino databases. Supports e-mail, address book, calendar, to dos and journal data using the standard templates Std50Mail, iNotes5, Std4PersonalAddressBook, Std50Journal, Std6Journal, and custom templates defined in the Mapping Database directory.

  • Microsoft Exchange Adapter: provides an interface for the Synchronization Server to access Microsoft Exchange databases. Supports e-mail, contacts, calendar, tasks and notes synchronization.

  • Relational Database Adapter: uses DB2 Everyplace Sync Server to provide an interface for the Synchronization Server to access DB2 or other JDBC-compliant databases.

8.5.1 Using DB2 Everyplace

Figure 8-13 depicts the relational database synchronization environment for JDBC subscription types.

click to expand
Figure 8-13: DB2 Everyplace synchronization for JDBC subscriptions

The hand-held device sits on the IBM Everyplace Client, which is the unified client. The unified client has a component called Secure Proxy, which is transparent to the user. Secure Proxy handles user authentication and data encryption between the client and the Web Server.

On the server side, IBM HTTP Server handles incoming HTTP requests, and passes those destined for WebSphere Application Server via a plug-in. WebSphere Portal rides on top of the WebSphere Application Server. It provides administration portlets to manage portlets as well as users and groups. User and group information is stored within LDAP.

Also on the server, DB2 Everyplace periodically replicates the back-end databases to mirror databases. DB2 Everyplace Mobile Devices Administration Center or MDAC, together with WebSphere Portal, provides the complete administration functionalities for DB2 Everyplace Sync Server.

DB2 Everyplace is the database engine installed on the mobile device. DB2 Everyplace Sync Server carries out bi-directional synchronization of data between the database on the mobile device and the source database on the server.

For more information about DB2 Everyplace and database synchronization, refer to the IBM Redpaper Relational Database Synchronization in WebSphere Everyplace Access V4.1.1 , REDP3590.

8.5.2 Configuring the DB2 Everyplace Server

The following steps show you how to set up the sample application that is using DB2 Everyplace to interact with the application database in order to collect information on the PDA for the Technician in the field.

  1. Create a mirror database for the application, run the script mirror.bat from the database directory.

  2. Create the SyncGroup with the portal interface. Add the wpsadmin user to the SyncGroup group. Also add all the Technician (tech1, tech2) and Client (client1, client2) users to the group.

  3. Create the DB2e_Technicians group and add the users: tech1, tech2 to the group.

  4. Create the DB2e_Clients group and add the users: client1, client2 to the group.

  5. Start the DB2 Everyplace Mobile Devices Administration Center.

  6. Create a new subscription set, right-click the Subscription Set , then select Create . Set the Name field to HelpDesk , then add the DB2e_technicians group to the subscription set.

    click to expand
    Figure 8-14: Subscription Set

  7. Create a new subscription; right-click Subscriptions , then select: Create -> Table Subscription -> JDBC subscription

  8. Specify the following field for the subscription:

    Name: Customer Service

  9. Switch to the Source tab, the set the following fields:

    Database URL: jdbc:db2:PERPORDB

    User ID: db2admin

    Password and Verify password: password

  10. Switch to the Mirror tab and set the following fields:

    Database URL: jdbc:db2:PERPORMI

    User ID: db2admin

    Password and Verify password: password

  11. Switch to the Subscription sets tab and add the HelpDesk subscription set to this subscription.

  12. Switch back to the Identification tab and click the Define subscription button.

  13. On the Define Replication Subscription panel, click Add then add the following tables to the subscription:

    • DBUSER.CATEGORY

    • DBUSER.DEFECT

    • DBUSER.ORDER

  14. Select the DBUSER.DEFECT item, then click Advanced .

  15. Switch to the Rows tab, then specify the following condition for the Subset of rows for individual users:

     TECHNICIANID=:TECHID 
  16. Close the Replication panel.

  17. Click OK to create the subscription.

    click to expand
    Figure 8-15: Subscription

  18. Select the Groups node, right-click the DB2e-Technicians item and select Edit.. .

  19. Select the Data filter tab, then click Add . Set the Parameter name to TECHID , then click OK . Click OK on the Edit group panel.

    click to expand
    Figure 8-16: Groups

  20. Select the Users node, then right-click tech1 from the list and select Edit.. .

  21. Select TECHID under the Data filter tab, then click Change . Set the User override field to tech1 . Click OK .

  22. Repeat the last two steps for the user tech2.

    click to expand
    Figure 8-17: Users

The database is configured for remote synchronization for pervasive devices.




Patterns. Pervasive Portals
Patterns: Pervasive Portals Patterns for E-Business Series
ISBN: 0738427772
EAN: 2147483647
Year: 2002
Pages: 83
Authors: IBM Redbooks

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net