Creating multiple database DOLS subscriptions

A subscription can contain several databases. Although some databases can be optional, others -- like the main database (the one containing the DOLS design elements) -- are required.

• Required databases are those databases necessary for the subscription to work offline. Required databases replicate in full, meaning both the design and data are sent to the user's machine.
• Optional databases replicate as "stubs," meaning only the design is replicated. When you include optional databases in a subscription, you enable users to download the data in the required databases more quickly. Users can then download the optional data later.

Here are a few tips to keep in mind when enabling a multiple database subscription for offline use:

• Identify all the databases in your subscription.
• Identify the main database and copy the DOLS design elements only to the main database. Do not copy the design elements to each database in the subscription.
• Use relative URLs and relative paths to link between databases. Avoid absolute URLs and paths, which do not work offline.

  For example, use /dev/mynsf.nsf as opposed to http://www.servername.com/dev/mynsf.nsf.

• Use wildcards (*) or use a directory when entering values in either the "Required files to replicate" or "Optional files to replicate" fields on the Rules tab of the Offline Subscription Configuration Profile document.

  If you enter explicit file names in either of these fields, you must re-edit the configuration document each time you add or delete files. For example, if the field contains three files -- SalesApp\main.nsf, SalesApp\contacts.nsf, SalesApp\custom.ntf -- you must update the field each time a file is added to the SalesApp\ directory or else that file will not replicate offline to join the rest of the subscription.

  By using wildcards (*) in either of these fields, you specify that all database files or all template files in a given directory are automatically replicated, even files recently added. For example, if you use a wildcard in this way, all NSF files in the SalesApp directory are replicated:

  SalesApp\*.nsf 

  Similarly, to make sure all NTF files in the SalesApp directory are included in the replication, specify the following:

  SalesApp\*.ntf

  By using just the directory, without a wild card, in either of these fields, you specify that all files in the directory, whether NSF or NTF, are replicated, even files recently added, as in this example:

  SalesApp