Creating a Data Federation Share in Sybase WorkSpace

Set up a link that allows a directory in the local file system to appear in the Data Federation data catalog. Applications (including WorkSpace Data Federation) and users who need the files can then access them through the data catalog without having to know which computer or file system they are located on.

Prerequisites

To create a Sybase Data Federation shared directory, you must connect to the grid domain controller (GDC) as a member of the DataProviders or Administrators group.

Note: Any files or subdirectories to which you do not have read permission will not be included in the shared directory you create in the data catalog.

Follow these steps in WorkSpace Data Federation to share a local directory into your domain’s data catalog.

Connect WorkSpace Data Federation to the GDC of the domain in which you want to create the share. To establish a connection using an existing connection profile, right-click the desired GDC under Grid Domain Controllers in Enterprise Explorer and select Connect. When WorkSpace connects to the GDC, the top-level directories of the domain's data catalog appear under the GDC in Enterprise Explorer.
In Enterprise Explorer, navigate to the data catalog directory in which you want the share to appear as a subdirectory. Sybase recommends that you put Data Federation shares in the /Shares directory of your data catalog.
Right-click the target directory and select Create Data Federation share. The Create Data Federation Share dialog opens.
Complete the dialog as follows.
1. Share name: Enter a name for the Data Federation share service. The name can be up to 32 characters long. A Data Federation directory with this name is placed inside the parent directory you selected. This subdirectory contains the shared data.
2. Grid server: From the pull-down menu, select the Data Federation grid server on which the share will reside. (The shared files need not be located on the same machine as the grid server, but in that case we recommend that you set up a share server local to the shared files.)
3. Share server: If you want the new Data Federation share to use a particular share server, select it from the pull-down menu. If you leave the pull-down menu set to “Local to grid server,” the new share uses the grid server you specified in the Grid server field as its share server. You can configure additional share servers for this share later.
4. Local path on share server: Enter the path to the local directory that you are sharing into the data grid. (This file system should be local to the share server, or to the grid server if you chose “Local to grid server” above.) For example: C:\mySDFshares\testdir
5. Encryption level: From the pull-down menu, choose Clear (encryption is turned off for this Data Federation share) or Encrypted (encryption is turned on). All communication between a Data Federation share and its grid server is encrypted. The encryption level property lets you, the data provider, decide whether your shared data also needs to be encrypted when it travels over the wire. Generally, it’s safe to run shares in clear mode (unencrypted) if your LAN is secure; your proxy server’s encryption protects data integrity over the WAN. In a data grid where traffic travels over the WAN and there is no proxy server, we recommend running shares in encrypted mode.
6. Current owner (optional): To change a Data Federation share’s owner, clickChange Owner and select a new owner from the User/Group Browser. By default, new Data Federation shares are owned by the Administrator user.
7. Description (optional): Enter descriptive information about this Data Federation share.
Click Finish to create the shared directory. The share service processes files at a rate of about 200 files per second, so the creation of a Data Federation share that contains many files can take several minutes. When the process is complete, the system redisplays the data catalog in Enterprise Explorer, showing the new Data Federation share.

Consider configuring the following aspects of your new Data Federation share:

Option	Description
Refresh schedule	The refresh schedule determines how often the Data Federation share rereads its source directory to pick up changes. There is no default refresh schedule.
Share servers	To improve the availability of your shared data, you can add one or more share servers to a Data Federation share.
Permissions	By default, the permissions on a new shared directory are set so that the user who created the share (who is the owner) can read, write, execute, and delete it and its contents; members of the DomainUsers group in the current grid domain can read the share and its contents, but they cannot write, execute, or delete. Users in other domains have no permissions.

Next

For more information on Data Federation shares, including instructions on adding share servers and changing the refresh schedule, see the Data Federation Administration Guide, part of the DI Suite documentation set, which is available on the Sybase Product Manuals Web site at http://sybooks.sybase.com