Step 3: Run the SAS Deployment Wizard and Migrate Your SAS Content

In this step, you run the SAS Deployment Wizard with the migration package as input. The wizard configures the target environment based on the source environment and loads your content to the target environment. Follow these steps:
  1. Log on to the machine with the appropriate user ID. As a best practice, we recommend logging on with the same account that was used to install the source environment. On Windows, the account must be a member of the Administrators group. On UNIX, do not use root.
  2. Go to the highest-level directory in the SAS Software Depot. From that directory, use one of the following commands to start the SAS Deployment Wizard:
    • Windows: setup.exe -record -deploy
    • UNIX: setup.sh -record -deploy
    • z/OS: setup.rexx -record -deploy
  3. As you respond to the SAS Deployment Wizard prompts, follow the guidelines that are provided in the following tables. (These tables list only the pages that pertain to migrations.)
    For detailed instructions for using SAS Deployment Wizard for a migration, see Install and Migrate SAS Interactively in SAS Intelligence Platform: Migration Guide.
    If you are migrating to the same machine as the source environment, respond to the prompts as follows:
    Wizard Page
    How to Respond When Migrating to the Same Machine (Shared SASHome, Different Level Number)
    Select Deployment Task
    Select Install SAS software.
    Select Deployment Type
    Select Perform a Planned Deployment and Configure SAS Software.
    When migrating to the same machine, you do not need to select Install SAS Software, because the software is already installed on the machine.
    Specify Deployment Plan
    Specify the same deployment plan that was used to create the source environment.
    Specify Configuration Prompting Level
    Select the same prompting level that was used to create the source environment (for example, Typical).
    Specify Configuration Information
    Configuration Directory: You can accept the default directory or specify a different directory.
    Configuration Level: Select a level that is different from the level of the source environment. For example, if the source environment is using Lev1, you might want to select Lev2. Under the configuration directory path, a new subdirectory will be created with the level number that you specify. Based on the level number, the SAS Deployment Wizard automatically increments the port numbers for your SAS servers. (See Port Numbering in a Multiple-Level Environment.)
    Local Machine Name
    Enter the fully qualified host name and short host name for the machine.
    Migration Information
    Select Perform migration, and then browse to the highest-level directory of the migration package that you created in Step 2: Perform Pre-migration Tasks.
    Remap Ports
    If you want to specify any port numbers that are different from the defaults, click the Port for Target cell in the appropriate row, and enter the new port number. Port numbers that appear in boldface indicate a potential port conflict. (In some cases, servers such as the SASApp and SASMeta logical workspace servers can share the same port.)
    External Account: Installer
    As a best practice, specify the same installer account that was used to create the source environment.
    External Account: SAS Spawned Servers Account
    If you want, you can specify the same SAS Spawned Servers account that is used by the source environment.
    SAS Framework Data Server: Transactional Database Files
    Edit the path so that it specifies the correct configuration directory (for example, change Lev1 to Lev2).
    Web Application Server: Managed Server
    Enter a managed server name that corresponds to the new environment.
    Web Application Server: Managed Server Ports
    Add 100 or 200 to each port number so that the ports are unique to the new environment. For example, change 8080 to 8180, change 8443 to 8543, and change 1099 to 1199.
    SAS Web Infrastructure Platform Scheduling Services Configuration Dependencies
    Change the SAS Application Server Context from SASMeta to SASApp.
    IP Multicast
    Be sure to modify the multicast settings if you are migrating to the same machine as the source environment. The combination of multicast IPD address and multicast UDP port should be different for each SAS deployment and also different from those used by other multicast applications at your site. See Designating Ports and Multicast Addresses in SAS Intelligence Platform: Installation and Configuration Guide.
    SAS Distributed In-Process Scheduling Server
    Increment each port number so that the ports are unique to the new environment. For example, change 7541 to 7542, and change 7641 to 7642.
    SAS Content Server: Repository Directory
    Repository Directory: Edit the path so that it specifies the correct configuration directory (for example, if you are migrating to Level 2, change Lev1 to Lev2).
    DataFlux Data Management Server
    DataFlux Data Management Server Name: Specify a unique name for this server. For example, if you are creating a development environment, you could add DEV to the end of the server name.
    If you are migrating to a different machine, respond to the prompts as follows:
    Wizard Page
    How to Respond When Migrating to a Different Machine (Same or Different Level Number)
    Select Deployment Task
    Select Install SAS software.
    Select Deployment Type
    Select Perform a Planned Deployment, Install SAS Software, and Configure SAS Software.
    Specify Deployment Plan
    Specify the same deployment plan that was used to create the source environment.
    Specify Configuration Prompting Level
    Select the same prompting level that was used to create the source environment (for example, Typical).
    Specify Configuration Information
    Configuration Directory: You can accept the default directory or specify a different directory.
    Configuration Level: You can use the same level number that is used in the source environment. This option is appropriate if you are creating a mirror of your SAS deployment for disaster recovery purposes, or if you are migrating your deployment to new hardware.
    If you are creating a separate test or development environment, you might want to specify a different level number. If you do so, the SAS Deployment Wizard automatically increments the port numbers for your SAS servers. See Port Numbering in a Multiple-Level Environment.
    Local Machine Name
    Enter the fully qualified host name and short host name for the machine.
    Migration Information
    Select Perform migration, and then browse to the highest-level directory of the migration package that you created in Step 2: Perform Pre-migration Tasks.
    Remap Ports
    If you want to specify any port numbers that are different from the defaults, click the Port for Target cell in the appropriate row, and enter the new port number. Port numbers that appear in boldface indicate a potential port conflict. (In some cases, servers such as the SASApp and SASMeta logical workspace servers can share the same port.)
    External Account: Installer
    As a best practice, specify the same installer account that was used to create the source environment.
    External Account: SAS Spawned Servers Account
    Specify the SAS Spawned Servers account that you created on this machine.
    SAS Framework Data Server: Transactional Database Files
    If you specified a different level number, then edit the path so that it specifies the correct configuration directory (for example, change Lev1 to Lev2).
    Web Application Server: Managed Server
    You can accept the default server name.
    Web Application Server: Managed Server Ports
    You can accept the default ports.
    SAS Web Infrastructure Platform Scheduling Services Configuration Dependencies
    Change the SAS Application Server Context from SASMeta to SASApp.
    IP Multicast
    When migrating to a different machine, it is usually not necessary to modify the multicast settings. See Designating Ports and Multicast Addresses in SAS Intelligence Platform: Installation and Configuration Guide.
    SAS Distributed In-Process Scheduling Server
    You can accept the default port numbers.
    SAS Content Server: Repository Directory
    Repository Directory: If you specified a different level number, then edit the path so that it specifies the correct configuration directory (for example, change Lev1 to Lev2).
    DataFlux Data Management Server
    DataFlux Data Management Server Name: You can accept the default server name.
  4. When the wizard is finished, read the warnings and notices that appear in the instructions.html document.
  5. On Windows systems, check to ensure that a unique set of Windows services has been created for the new environment. A separate set of services should appear for each level (for example, Lev1 and Lev2).

See Also

Installing SAS 9.3 and Migrating Your SAS Content in SAS Intelligence Platform: Migration Guide
Copyright © SAS Institute Inc. All rights reserved.