---

This screen allows you to configure the WebSite Director (WSD) file, directory and user information for the new Repository. The fields that you will see on this screen depend on the Repository Type. The following fields display the Repository information entered on the previous screen: ID, Server, Type, Description, Working Directory. Only the Working Directory name may be changed on this screen.

Warning: If you change the value assigned to Working Directory, you may also have to change the value assigned to Template Directory (for WSD Pro and WSD Express users only) to allow users to use WSD to edit the repository's template documents.The information you provide in the fields below will be assigned to the WSD module installed to manage this repository. The default directory and file information displayed in these fields is based on the information you provided on the Create Repository screen and the default replacement variables set on the System Defaults screen. After you complete the information on this screen, click [CREATE] to complete creation of the Repository and return to the Main screen. Click [CANCEL] to return to the Application Desktop screen without creating the new Repository.

• Program Directory - The directory into which WSD will be installed.
  • If you did not define a virtual host, the default will be based on the values set on the System Defaults screen.
  • If you defined a virtual host, the information entered on the Configure Virtual Host screen dipslays.
    Warning: If you change this default value, review the default values for Program URL, Access Control File, and Activity Log File to make sure those references are still accurate. Change them where necessary.
• Program URL - The URL to access the installed WSD module that controls the data in this Repository. If you have defined 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.

  Because of the administrative burden of managing large numbers of Script Aliases, we recommend against assigning them directly to WSD Program Directories. Instead, we recommend you 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 NT 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 top-level directory where all of the support files used by WSD are stored. The default is the same "wsd-support" directory used by TeamWSD. The support directory must be located under the Document Root directory and the specified path is relative to the Document Root directory. You should change the default value only when you want a specific 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 (not available for WSD Lite) - 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
• Access Control File  - This is the file that controls user access to WSD. To properly control access to the copy of WSD that will be installed for this repository, it should be in the same directory as, or in one of the parent directories of, the Program Directory specified on this screen. Possible values for this field are:
  • Servers other than the Netscape Server: usually .htaccess
  • Netscape Server: .htaccess, .nsconfig, or blank

    Warning: If you do not place this file in the Program Directory, or one of the Program Directory's parent directories, anyone who can construct a valid URL for accessing this copy of WSD will be able to access this repository without being prompted for a username/password!

    Note: If the Secure Working Directory option is turned on (see below), a copy of this file will be placed in the Working Directory.

• Password File - This is the file that contains the user names and passwords for users validated to access the WSD executable that will manage this repository.
  Note: To prevent direct access to the password file by a web browser, this file should be placed in or under the web server's cgi-bin directory.
• 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.
• Initial User - this is the username assigned to the initial user who is validated to use WSD to manipulate the data in this repository.
  • If you assigned the User List as Private on the previous screen, this field will be blank. You must type in the username of the User initally responsible for maintaining this Repository.
  • If you assigned the User List as Shared on the previous screen, this field will contain your User Name and user ID. A drop-down list contains of all users defined for TeamWSD. You may use the drop-down list to change this assignment to any other TeamWSD user defined within the user database.

    Note: The initial user you assign on this screen is also given all permissions to administer the data repository: User Administration, Repository Administration and System Administration.

• Initial Password and Confirm Password - These fields only display if you have assigned the User List as Private on the previous screen. You must type in the password that will be used by the initial user responsible for maintaining this Repository.
• Proxy User and Password (Microsoft Internet Information Server) - If your Microsoft Internet Information Server is configured to allow anonymous access, leave these fields blank. If it is not configured to allow anonymous access, you must enter a valid Windows NT Server username and password for the Proxy User for WSD to use when logging in.
• 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.
• The following three fields apply to UNIX servers using Virtual Domains. For specific help in setting up TeamWSD for Virtual Domains, please call CyberTeams Support at 301.829.6144.
  • Repository Owner UID: (UNIX only) - the UNIX server's filesystem User ID (UID). This is userid of the owner of the repositories created via TeamWSD.
  • Repository Owner GID: (UNIX only) - the UNIX server's filesystem Group ID (GID). This is the default groupid for the owner of the repositories created via TeamWSD.
  • 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 Read and/or Write file permissions to the repository owner's UID displayed above.
    • Group - assign Read and/or Write file permissions to the repository owner's GID displayed above.
    • Other - assign Read and/or Write file permissions to all other users who are not the UID or GID owner. 
• Virtual Host Information - The displayed default values are derived from configuration information defined for the Virtual Host (Hostname or IP Address) on the Configure Virtual Host screen.
  • Server Root Directory - This value is used as the filename prefix when you do not provide fully-qualified pathnames for the Access Control File, Password File, or Activity Log File fields on this screen. If you defined a virtual host, the information entered on the Configure Virtual Host screen displays in this field.
  • 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. If you defined a virtual host, the information entered on the Configure Virtual Host screen displays in this field.

Warning: The new User Data Repository will not be created if any of the files TeamWSD attempts to install for the new repository already exist within the Program Directory.

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