Chapter 2 Installing PowerDesigner
Installing PowerDesigner in Administrative mode
If you are a system administrator and you want to allow users to install and use PowerDesigner from a network machine, you have to use the administrative option of the PowerDesigner Setup program.
When you perform an administrative installation, you should respect the following architecture:
- The server stores PowerDesigner files (executable, dll, and so on) that will be used by client machines. The administrative installation installs a source image of PowerDesigner onto the network that is similar to a source image on the product CD. Users in a workgroup who have access to this administrative image can then install PowerDesigner.
- The client machines do not store any PowerDesigner file but their registry is modified in order to be able to run PowerDesigner. You can install any type of PowerDesigner license on a client machine, from trial to standalone local or served.
Roadmap
- Copy the files on a server using the /a setup command. The server stores the PowerDesigner files that will be executed from the client machines.
- Run an administrative installation on each client machine in order to modify their registry. During installation, PowerDesigner prompts you to provide the path of the server where the PowerDesigner modules are installed. If you provide a path with an incomplete installation, a message is displayed to warn you.
For more information about the stand-alone installation process, see section Installing the stand-alone version of PowerDesigner.
Upgrading an administrative install
If you want to pass the administrative install command to an upgrade package downloaded from the web, you have to use the following syntax:
<name of the executable file.exe> -a <argument>
pdupgrade.exe -a /a
Where -a is used to specify that command </a> is targeted to the executable file within the downloaded package pdupgrade.exe.
Copyright (C) 2006. Sybase Inc. All rights reserved.
|
|