Siebel Analytics Server Administration Guide > Completing Setup and Managing Repository Files > Making Changes in an Analytics Multiuser Development Environment >

Changing Metadata in an Analytics Multiuser Development Environment

After setting up a pointer to the source repository, a developer can check out projects, change metadata, and test the metadata.

During checkout, the Administration Tool performs the following tasks:

• In the developer's local \SiebelAnalytics\Repository directory, the Administration Tool makes a temporary copy of the source repository and writes an entry in the log file for the source repository file ([source repository].rpd.log). The entries in this log file record the time and date when the temporary repository file was created.

  CAUTION:  If a repository with that name already exists in this location, the developer is asked to confirm overwriting the existing repository. If the developer clicks Yes, the existing repository will be immediately overwritten in the background and after the new repository is saved, the source repository file will be automatically deleted.

• In the multiuser directory on the network, the Administration Tool writes an entry in a log file ([source repository].log). The entry in the log file records the time and date when a local repository is created, the names of the projects, the Windows login name of the developer, and the machine name where the local repositories are saved. The following is an example of an entry in the log file:

  ####################### 12/14/2003 6:41:55 PM: Created subset repositories originalDevelopment1.rpd and Development1.rpd based on project(s) Supplier Sales KW2 Login Name: kwolff Computer Name: KWOLFFP4

• In the developer's local \SiebelAnalytics\Repository directory, the Administration Tool saves a local copy of the selected projects in a new repository such as Development1.rpd. The developer uses this copy for metadata changes.

  Additionally, the Administration Tool writes an entry in a log file for the new local repository ([local repository].rpd.log). The entries in this log file record the time and date when a local repository is created and saved.

• In the developer's local \SiebelAnalytics\Repository directory, the Administration Tool saves a second local copy of the new repository, adding Original as the prefix. An example of this local copy might be OriginalDevelopment1.rpd.

  Additionally, the Administration Tool writes an entry in a log file for the copy of the local repository (Original[local repository].rpd.log). The entries in this log file record the time and date when the copy of the local repository is created and saved.

• After the developer saves the new repository file, check out is complete. In the developer's local \SiebelAnalytics\Repository directory, the temporary copy of the source repository is automatically deleted.

CAUTION:  The Administration Tool does not place a lock on the projects in the source repository. Therefore, nothing prevents others from working on the same project. To determine if a project has been checked out, you need to look in the log file in the multiuser directory on the shared network drive.

To check out projects

1. From the Administration Tool menu, choose File > Multi-User Checkout.
2. In the Select repository to extract subset from dialog box, select the source repository and then click Open.

   CAUTION:  If a repository file with that name already exists in this location, a message appears asking if you want to overwrite it. If you click Yes, the file in your local \SiebelAnalytics\Repository directory will be immediately overwritten and after the new repository is saved, the source repository file will be automatically deleted.

3. In the Extract from [name of repository] dialog box, type your user name and password, and then click OK.
4. In the Browse dialog box, select the check boxes for the projects you want to import, and then click OK.
5. In the New Repository dialog box, type a name for the new repository and then click Save.

   After you specify the name of the repository containing the project you want to change, the Administration Tool opens this repository in offline mode.

Changing and Testing Metadata

After making changes to a local repository, the developer can edit the local NQSConfig.ini file, enter the name of the repository as the default repository, and test the edited metadata. For more information about testing the metadata, see Process of Completing the Setup for a Repository File.

NOTE:  DSNs specified in the metadata need to exist on the developer's workstation.