Conjunto de datos por base de datos bibliográfica

For the purposes of this example installation it is assumed that:

• Each user’s Root Drive (%ROOTDRIVE% variable) is mapped to drive letter H:. • The %SYSTEMROOT% environment variable on the Terminal Services server is set

to C:\Wtsrv.

• Required user accounts have been created on the Terminal Services server.

Setting Access Rights

In order to install Developer on a Windows Terminal Services server, you need to have

Administrator access rights to the Terminal Services server. This is required because some Windows system files may be overwritten during installation, and only users with Administration access rights have permission to overwrite system files.

If the Developer installation process attempts to overwrite a system file and detects that you do not have Administrator access rights, an error message will be displayed and the installation process will exit.

Windows operating system access rights are set by the User Manager program. This can be accessed by clicking the Start menu and going to Programs, and then Administrative Tools (Common). If you are unable to set Windows operating system access rights, see the System Administrator for your site.

Note: If the Developer installation process finds system files that need updating, you will

be prompted to reboot your machine before running Developer.

Installing Terminal Services

1. When installing Windows 2000 Server on your Terminal Services server machine, you must install the following components:

• Terminal Services

• Terminal Services Licensing

2. After selecting these components, the Terminal Services Setup screen displays a choice of Terminal Services modes. Select Application Server mode. This mode is recommended for Developer, because it means that client machines can only install programs using the Terminal Services server (using Add/Remove Programs in the Windows Control Panel).

Note: To use Application Server mode, you must install a Terminal Services licensing

server in your domain within 90 days. See your Windows documentation for details. 3. Once the Terminal Services mode has been selected, set the default permissions for

application compatibility. Two options are available:

• Permissions compatible with Windows 2000 users

This option is more secure, but may not be able to run legacy applications such as Windows NT 4.0 and earlier.

• Permissions compatible with Terminal Server 4.0 users

This option is compatible with most legacy applications, but offers reduced security since all clients have full access to the Windows registry and file system locations. This is the default option.

Developer installation will not be affected by this option, so you should select an option based on the number of other legacy programs you are running, and the level of security required.

4. When you have selected your default permissions, continue with the standard Windows 2000 Server installation.

Creating Client Install Disks

Once Terminal Services is installed on the server machine, create installation disks for the client machines. To create the disks:

1. Log in to the Terminal Services server.

2. Select Start, then Programs, Administrative Tools, Terminal Services Client Creator. 3. In the Create Installation Disk(s) dialog box, select Terminal Services for 32-bit

x86 windows. Click OK to finish creating the disks.

Use the created disks to install the Terminal Services Client on your client machines.

Administrator and Developer Server Machine Installation

Ensure you have Windows Administrator privileges for the machine you are installing to, then install the following components:

Component Comments

On the Terminal Services server Administrator installation of Developer to a directory.

See “Using the Administrator Option” on page 3–11.

On the Developer Server Machine

Developer Server See “Installing the Developer Server” on

page 3–16.

Version Control Server (if required) See your Unisys Enterprise Application Developer Version Control Guide.

Repository See “Installing the Developer Repository” on

page 3–19.

On the Security Machine

Developer (required for security) See “Installing Developer on a Client Workstation” on page 3–17.

Note: After installing the Security module, you should set up the necessary access rights for the users who will be using Developer. See your Unisys Enterprise

Application Developer Administration Guide for details.

Developer with Terminal Services Installation and Configuration

To install Developer on the Terminal Services server and configure it for client use: 1. Log in to the Terminal Services server, then select Add/Remove Programs from the

Windows Control Panel.

2. Click Install, then locate and open the Developer installation program (setup.exe) from the directory to which the Administrator installation was copied.

3. In the wizard dialog select the All users begin with common application settings option and click Next to start the Developer installation.

4. Select the Custom Installation Type and click Next.

5. In the Select Components dialog box select only those components users need for a multiuser installation (for example, Developer and Developer Test). When complete, click Next.

If required, the Version Control Client and Builder can be installed later.

Note: De-select Repository as this has been installed as part of the Server machine

installation.

6. Enter the following data in the Installation Configuration dialog box:

• In the Installation Directory field, enter the location on the Terminal Services server where Developer is to be installed. The default is C:\Program

Files\Enterprise Application Developer.

• In the Working Directory field, enter the path to the user’s Root Drive, for example, H:\Program Files\Enterprise Application Developer\Work.

• In the Repository Directory field, specify the path to the Repository relative to the Developer Server machine (that is, the same value entered when you installed the Developer Server). See “Setting up a Multiuser Configuration” on page 5–5 for more details.

7. Select the Multi user mode radio button and specify the Developer Server machine name. Click Next to continue.

8. Answer Yes to The Installation directory does not exist. Do you want the directory to be created? and Yes to The Working directory does not exist. Do you want the directory to be created? Answer No to Creating the Repository.

9. When the installation process is complete, click OK.

10. Return to the Add/Remove Program dialog box and choose Next, then Finish. 11. Restart the Terminal Services server.

Uninstalling Developer with Terminal Services

To uninstall Developer, select Programs from the Start menu, then navigate to the Developer 3.3 program folder and select Uninstall.

Known Issues with Developer with Windows Terminal Services