Planning Your Installation and Deployment
You can choose from several different approaches for installing and deploying Reflection. Deciding which approach to use is typically based on a variety of factors, including your approved business processes, the scale of the deployment, your deployment tools, and whether you want to customize the installation.
For example, a small-scale deployment might consist of using the Attachmate Installation Program to install Reflection on a few workstations, whereas an enterprise-wide deployment would probably involve extensive customization and testing.
Use one of the following approaches, depending on your requirements.
- Perform a Workstation Installation on each Workstation
Install all of the files for Reflection to a PC hard drive. You might choose this approach if you are installing Reflection on a small number of machines and you do not need to customize the installation. - Perform a Basic Deployment
Perform an administrative installation to copy Reflection files to an administrative installation point. This is also referred to as creating an administrative installation image. Then, using deployment tools, you access these files and create packages that are deployed to workstations. A basic deployment is a good choice when you need to deploy Reflection to a large number of workstations but you do not need to customize the installation. - Perform a Customized Deployment
Perform an administrative installation to copy Reflection files to an administrative installation point (just as you would for a basic deployment). Then, you customize the installation to specify the way it installs, looks, and acts on the end users' computers. Customized deployments can be used to deploy to any number of workstations. In this scenario, you can provide users with customized files. (For example, for some products these files could include workspaces and session documents).
|