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. If you are migrating to the same machine and you will be using the same port numbers in both environments, stop all of the servers in the source environment before starting the SAS Deployment Wizard.

3. 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

4. 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.)

If you are migrating to the same machine as the source environment, respond to the prompts as follows:

Table A1.1 SAS Deployment Wizard Responses for Migrating to the Same Machine

Wizard Page

How to Respond When Migrating to the Same Machine (Shared SASHome, Different Level Number)

Select Deployment Task Select Install SAS software.

Wizard Page

How to Respond When Migrating to the Same Machine (Shared SASHome, Different Level Number)

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 is created with the level number that you specify.

Local Machine Name Enter the fully qualified host name and short host name for the machine.

Migration Information Select Perform migration, and then navigate to the highest-level directory of the migration package that you created during pre-migration tasks.

Note: Do not select this option when you are installing additional metadata server nodes or additional middle tier nodes.

Remap Ports To specify 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 bold indicate a potential port conflict.

If the source and the target environments will both be operational at the same time, then it is important to specify new port numbers for each server in the target environment. If only one environment will be operational at a time, then the two environments can share the same port numbers.

External Account: Installer As a best practice, specify the same SAS 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.

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

Wizard Page

How to Respond When Migrating to the Same Machine (Shared SASHome, Different Level Number)

If the source and the target environments will both be operational at the same time, then it is important to specify new port numbers for each component in the target environment. If only one environment will be operational at a time, then the two environments can share the same port numbers.

SAS Web Infrastructure Platform Scheduling Services

Configuration Dependencies SAS Visual Analytics Configuration Dependencies

If SASMeta is selected, then you must select a different server context. In SAS 9.4, the SASMeta server context no longer includes a workspace server or a batch server.

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.

If you are migrating to a different machine, respond to the prompts as follows:

Table A1.2 SAS Deployment Wizard Responses for Migrating to a Different Machine

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).

Wizard Page

How to Respond When Migrating to a Different Machine (Same or Different Level Number)

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.

Local Machine Name Enter the fully qualified host name and short host name for the machine.

Migration Information Select Perform migration, and then navigate to the highest-level directory of the migration package that you created during pre-migration tasks.

Note: Do not select this option when you are installing additional metadata server nodes or additional middle tier nodes.

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 bold indicate a potential port conflict.

External Account: Installer As a best practice, specify the same SAS 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 Web Infrastructure Platform Scheduling Services

Configuration Dependencies SAS Visual Analytics Configuration Dependencies

If SASMeta is selected, then you must select a different server context. In SAS 9.4, the SASMeta server context no longer includes a workspace server or a batch server.

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.

5. When the wizard is finished, read the warnings and notices that appear in Instructions.html.

6. On Windows systems, check to ensure that a unique set of Windows services has been created for the new environment. If you migrated to the same machine, a separate set of services should appear for each level (for example, Lev1 and Lev2).

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