---

This screen displays current information about the Repository selected on the Application Desktop, and allows you to change the configuration information. Carefully review the information on this screen before you make any changes.

• Repository ID - This is a display field and may not be changed. This Repository identifier is the "key" associated with all configuration information for this repository.
• Repository Server - This is a display field and may not be changed. This field displays if the repository is installed on a remote server (see Maintain Servers).
• Repository Type - This is a display field and may not be changed.
• Description - This is the Repository's descriptive name that displays on WSD screens.
• User List - determines whether the list of users for this Repository is Shared with TeamWSD, or Private and maintained uniquely for this Repository.
  • If set as Shared, the user list will be shared by all other Shared Repositories
  • If set as Private, the repository can only be accessed by someone whose User Name is in the private user database associated with this repository. This may be the "initial user" designated when this repository was created or any other User Name added via the Add New User function from within this repository.

    Note: When a TeamWSD user tries to access this Repository using the [GO TO REPOSITORY] function on the TeamWSD Application Desktop screen, the user must provide a username/password that is valid for the user list associated with this Repository.

• Working Directory - The Working Directory is the root directory under which the directories and documents for this repository are maintained. It is used to construct URLs to access your documents.
  Warning: If you change the value assign to Working Directory, you may also have to change the value assigned to Template Directory, if you want users to be able to edit the template documents using the copy of WSD that manages this Repository.
• Program Directory - The directory into which the copy of WSD that manages this repository is installed. This field is display only.
• Program URL - The URL to access the installed WSD program that controls the data in this Repository. If you change the value in this field you may have to make corresponding changes to one or more of your web server's configuration files depending on which server you are using.

  If the new value you enter includes a script alias/URL prefix for a directory above the TeamWSD directory, you will not have to make any additional web server control file modifications to allow access to this Repository. If you are using specific script aliases to access each installed copy of WSD, you will have to make appropriate changes to your server configuration files. The nature of these changes will vary between servers.

  Note: Because of the administrative burden of managing large numbers of Script Aliases, we recommend against assigning them directly to WSD Program Directories. Instead, you should create a script alias for the TeamWSD parent directory or any of the parent directories above the TeamWSD installation directory.

  The following examples show some script alias alternatives for TeamWSD installed on a Microsoft Windows server. The ".exe" program extension shown does not apply to UNIX servers. For our examples we are using a domain of "mycompany.com" with TeamWSD installed in the "/servers/users/programs/teamwsd" directory:

  • for ScriptAlias: /parent1/ referencing directory: /servers/users/programs/ Program URL: /parent1/<Repository-ID>/wsd.exe
  • for ScriptAlias: /parent2/ referencing directory: /servers/users/Program URL: /parent2/programs/<Repository-ID>/wsd.exe
  • for ScriptAlias: /parent3/ referencing directory: /servers/Program URL: /parent3/users/programs/<Repository-ID>/wsd.exe
  Using any of the alternatives listed above eliminates the need to assign specific script aliases to access individual copies of WSD.
• Support Directory - This is the directory where all of the support files used by WSD are stored. The default value at the time a new repository is created is the same "wsd-support" directory used by TeamWSD itself. The support directory must be located under the Document Root directory and the specified path is relative to the Document Root directory. You should not change this value unless you want this repository to have its own versions of the support files.
  Warning: Do not include the Document Root directory as part of the entry value for this field!
• Request Directory (not available for WSD Express or WSD Lite) - This is the directory used to store request files while they are being processed by WSD.
• Version Directory (not available for WSD Express or WSD Lite) - This is the directory where version history files are stored. All prior versions are maintained as "deltas" in the mastr copies so that WSD users can revert a document back to any prior version. Note: Althought WSD Express provides a version history, it's Version Directory is built-in to that application.
• Template Directory (not available for WSD or WSD Lite) - This is the directory where Page Layout Templates are stored.
• Default Edit Online Image Directory (not available for WSD or WSD Lite) - The default directory for the images to be used by the WYSIWYG Online Editor when  creating or editing a document located in the directory.
• Dynamic Content Preview Directory - The directory where requests that reference dynamic content from your third-party software (i.e., Cold Fusion or active server pages) are temporarily stored during view and preview within WSD.
• Activity Log File - This is the file that contains a log of all WSD activity for this Repository. The log entries include the date and time of the activity, the username of the user who performed the activity and a brief description of the activity.
  Note: To prevent direct access to the file by a web browser, this file should be placed in or under the web server's cgi-bin directory.
• URL Prefix - Some installations, specifically many Internet Service Provider (ISP) installations, place the Document Root directory under a User Home Directory as a method of separating access to each user's web content from that of other users. To access files in that home directory, a URL Prefix (such as "/~username" or "/username") is sometimes required at the beginning of every URL. Because WSD generates URLs to access its support files while it is managing the content in the designated repository, this field should be set to any URL Prefix (without a trailing "/") needed to access documents under this User's Home Directory. If no URL Prefix is needed, this field should be left blank.
• Error Log File (not available for WSD Express or WSD Lite) - this file is used to log all errors that occur in WSD. Log entries include date/time of error, username, and a brief description of the error.
• SQL Journal File (not available for WSD Express or WSD Lite) - the file used to log all database updates made by WSD. Entries include date/time of database update and the sull SQL command that made the update.  This journal file can be used, along with a backup of the WSD database, to restore the database up to the very last update.
• Database Name (not available for WSD Express or WSD Lite) - this is the name of the existing SQL data base. All WSD document, request, user, and configuration information is stored in this database.
• Database Host (not available for WSD Express or WSD Lite)  - if the SQL database engine is on a different machine than the web server, this is the hostname of that machine.
• Database Port (not available for WSD Express or WSD Lite)  - if you use a MySQL database engine that is configured to use a different port than the default, that port must be specified in this field.
• Database User Name (not available for WSD Express or WSD Lite) - if you are using an SQL database server that requires a validated login, this is the name of the user authorized to access the database.
• Database User Password (not available for WSD Express or WSD Lite)  - this is the password associated with the Database User Name.
• Administration E-mail Address (not available for WSD Express or WSD Lite) - this is the e-mail address of the WSD Administrator. This address is displayed by WSD as the contact address if a database error occurs.
• File Permissions for new files: (UNIX only) - if you are not using CGIWrap or an equivalent utility, and you want to be able to update files in the Working Directory outside of WSD, click the appropriate Read and Write checkboxes to assign permissions as follows:
  • Owner - assign UID Read and/or Write file permissions to the owner User ID (UID).
  • Group - assign GID Read and/or Write file permissions to the owner Group ID (GID).
  • Other - assign Read and/or Write file permissions to all other users who are not the owner of the UID or GID.
• Server Root Directory and Document Root Directory - These fields are displayed at the end of this screen, and may be changed for Virtual Host-based repositories only. The default values are derived from configuration information defined for the Virtual Host (Hostname or IP Address) specified on the (previous) Create New Repository screen. For Apache web servers, TeamWSD interrogates the hosting server to get Document Root information.
  • Server Root Directory - This value is used as the filename prefix when you do not provide fully-qualified pathnames for the Program Directory, Access Control File, Password File, or Activity Log File fields on this screen.
  • Document Root Directory - This directory forms the path prefix for the Working Directory and Template Directory fields on this screen if you do not type in fully-qualified pathnames for these fields.

FUNCTION BUTTONS:

[UPDATE]	Updates the configuration information and displays the Application Desktop screen.
[USER ADMINISTRATION]	Displays the Repository's User Administration screen.
[MAINTAIN USERS]	If the User List is "Shared" (see radio button), displays the TeamWSD Maintain Users screen.
[CHECK PERMISSIONS]	Displays the TeamWSD Repository Permissions Check report.
[CANCEL]	Returns to the Application Desktop screen without changing the configuration.

5714-B Industry Lane, Frederick, Maryland 21704 USA Phone: +1 301.682.8885 E-mail: info@cyberteams.com  http://www.cyberteams.com CyberTeams and WebSite Director are registered United States trademarks of CyberTeams, Inc.  Copyright 2001 CyberTeams, Inc., Maryland, USA All rights reserved