Copyright © Cloud Software Group, Inc. All Rights Reserved

File Sharing

This section discusses using File Sharing as a Revision Control System in the following sections:

•	Preparing for File Sharing on Microsoft Windows

•	Preparing for File Sharing on UNIX

•	Using File Sharing

•	Deleting RCS Projects

Preparing for File Sharing on Microsoft Windows

The project is located on a shared drive accessible by all TIBCO developers.

Make sure all TIBCO developers have read and write access to that drive.

Preparing for File Sharing on UNIX

The project must be located on a mounted drive accessible by all TIBCO developers. You then go through these steps:

1.	Create a Unix group for the TIBCO developers (for example, tibdev).

2.	Create a Unix account for each developer. Each account must have its Primary Group ID set to the group tibdev.

3.	For each account, the umask must be set to 002 to ensure the entire group has write permission on resources (folder and file) in TIBCO Designer projects. Set the umask in the .login or .profile file, as follows:

 

   $ umask 002

Using File Sharing

Allowing multiple users to use file sharing for a project involves these tasks:

Task A Create the Project

1.	Open TIBCO Designer and open the project (which could be a new empty project).

2.	Choose Project > Save > Multi-File Project.

3.	In the dialog that appears:

a.	Supply the root directory for the project (which will become the project name). This directory should be on a drive that can be accessed by all developers that work on the project.

b.	Choose File Sharing from the pop-up.

c.	Supply your username. Other users will see this username as the owner if you lock files in the project

Task B User A Acquires Resource and Makes Changes

The creator of the project or another user can now acquire the lock for the project and, for example, add two folders. Here are the steps:

1.	User A selects the project root folder.

2.	User A chooses Multi-User > Acquire Resource.

That command is also available from the resource’s right-button menu or from the Project menu.

3.	User A drags two Folder resources into the design panel and names each for the user who will work with it.

4.	User A selects the folder for the second user (User B) and chooses Release Resource from the right-button menu.

The folder now appears locked in the TIBCO Designer project panel.

Figure 17 Locked Folders

5.	User A opens the User A folder and adds two resources to it, then selects each resource and chooses Add Resource to RCS from the right-button menu.

User A can make changes to the User A folder (but not to the User B folder).

6.	User A saves the project.

Task C User B Opens Project, Acquires Resource, and Makes Changes

A second user can open the same project and make changes to all folders not currently locked by another user. For this example:

1.	User B opens the project (all project elements are locked).

2.	User B selects the User B folder and chooses Acquire Resource from the right-button menu.

User A released the lock for this folder.

3.	User B can now make changes to User B folder as desired, and save the project.

User B cannot acquire the lock for the project root folder or for the User A folder because both are locked by User A.

Copyright © Cloud Software Group, Inc. All Rights Reserved