An subscription set is a container for subscriptions. You assign subscription sets to a group so that its members have access to the data and files defined in the subscriptions that are part of the subscription set. The subscriptions that you assign can be JDBC subscriptions, DataPropagator subscriptions, file subscriptions, or custom subscriptions. Each subscription set can contain any number of subscriptions (limited by mobile device storage capacity).
When users start the synchronization user software on the device, they choose which applications to synchronize. This menu of applications is created from the list of subscription sets associated with the user's group. For more information, see Registering the user's device.
To define an subscription set:
Each step is explained further in this section.
After authenticating a user, the Sync Server determines the group that the user belongs to, then queries the administration control database to determine the subscriptions that belong to the subscription set referenced in the request. For this reason, the Sync Server must be able to uniquely identify each subscription set by name.
To identify the subscription set, provide the following information on the Identification page of the Create Subscription set notebook:
Provide a descriptive, unique name for the subscription set from 1 to 18 characters. You might choose a name that maps to the name of an application already used by a particular group, or you might create a new name here. For example, you might choose VNURSE as the name for the subscription set used by all home health care specialists that work at the hospital.
Subscription set names are case-sensitive.
Type up to 128 characters of text that describes this subscription set. For example, you might describe the VNURSE subscription set as "Data and files used by all home health care specialists".
To enable a group of mobile users to access data and files that its members require, associate the subscription set with replication subscriptions that define tables and files as data sources available for replication.
For example, suppose your group of visiting nurses relies on a Palm OS application called vnurse.prc to perform their jobs. The vnurse.prc Palm OS application accesses patient and scheduling information in the PATIENTS and SCHEDULES tables, which reside on a source server. To enable the nurses to use the DB2 Everyplace Sync Server to replicate this data to their user devices, you must define two replication subscriptions:
After defining the subscriptions, associate the subscriptions with a subscription set and then assign that subscription set to the VNURSE group to enable the visiting nurses to replicate the data that they need. When the visiting nurses synchronize their data, they receive the latest copy of the resource file, as well as updates to the PATIENTS and SCHEDULES tables.
You can associate an unlimited number of subscriptions with a subscription set.
To associate subscriptions with the subscription set:
If no subscriptions are displayed in the Available subscriptions list, you will need to create a subscription. You can click Create to open the Create JDBC subscription, Create DataPropagator subscription notebook, Create File subscription notebook, or Create Custom subscription notebook now, or you can create a subscription later and associate a subscription set with it later.
To allow a group to access the DataPropagator and file subscriptions referenced in a subscription set, you must associate the group with the subscription set.
To assign an subscription set to a group:
If no groups are displayed in the Available groups list, you will need to create a group. You can click Create to open the Create Group notebook now, or you can create a group later and associate it with a subscription set later. See Creating a data synchronization group for details on creating a group.