Completing the Pre-migration Checklists

Later, during the installation and migration step, the SAS Deployment Wizard prompts you for account credentials used to run SAS 9.1.3 (including third-party software) and for ports for SAS servers that are new to SAS 9.2. Complete the following checklists and have them ready to refer to when you run the SAS Deployment Wizard.

• external user account checklist

• new server ports checklist

Complete the following checklist to use later, during the installation and migration step, when the SAS Deployment Wizard prompts you for account credentials. For migration purposes, you must have the same operating system accounts that you had in SAS 9.1.3.

Also, make sure that you review important information in the topic, Important Notes on User Accounts and Authentication.

Note:   This checklist assumes that you are migrating to SAS 9.2 using the same machines that you used to run SAS 9.1.3. If you are using new machines, then you need to make sure that the SAS 9.1.3 operating system accounts, groups, and user and group permissions are set up properly. For more information, see "Setting Up Required Users and Groups" in the SAS 9.1.3 Intelligence Platform: Installation Guide, available at http://support.sas.com/913administration.  

Consider the following items when working with user accounts during the migration process:

• Identities must be unique. You cannot reassign an existing system identity that is associated with a metadata persona in either the SAS 9.1.3 or SAS 9.2 configuration. For example, if the operating system user account sasguest is associated in metadata with the SAS Guest persona in your SAS 9.1.3 system, you cannot also associate sasguest in SAS 9.2 with the SAS Anonymous Web User.

• On UNIX systems, the SAS Deployment Wizard requires that you supply the root password during configuration. Certain SAS products and features use functionality that requires SAS to check user ID authentication and file access authorizations. This in turn necessitates that certain files within your SAS installation have setuid permissions and be owned by root.

• The SAS automated migration tools detect machine name changes for the metadata server during the migration process and automatically changes host name domains in all logins and for the necessary file permissions.

  For example, if the metadata server host name changed from "myhost" to "mynewhost," then all domain logins that are qualified with "myhost" are automatically changed to "mynewhost." (The tools change "myhost\sasadm" and "myhost\sastrust" to "mynewhost\sasadm" and "mynewhost\sastrust.")

• The SAS automated migration tools do not automatically change the following:

  • required external user account IDs

    (For example, changing "myhost\ebiadmin" to "myhost\sasadm" or changing "ebiadmin" to "sasadm."

    You must specify these new external accounts when prompted for them in the deployment wizard in order to change the SAS metadata. To change the file permissions, use the temp scripts.

    For more information, see Permission Considerations when User Accounts or Groups Change.

  • required operating system group (UNIX only)

    (For example, changing the primary group of the SAS Installer user from "sas913" to "sas."

    To change the file permissions that involve group membership, use the temp scripts. (There are no SAS metadata changes required when you change an operating system user group.)

    For more information, see Permission Considerations when User Accounts or Groups Change.

• If your UNIX system uses an authentication method other than /etc/passwd or /etc/shadow, then you must configure authentication before you begin your SAS software deployment, or SAS 9.2 will not function properly. For more information, see the Configuration Guide for SAS 9.2 Foundation for UNIX Environments available at http://support.sas.com/installcenter.

• The SAS Anonymous Web User is used to grant clients access to applicable SAS Web Infrastructure Platform applications such as SAS BI Web Services and the Stored Process Web Application.

• The SAS Deployment Wizard prompts you for a SAS Spawned Server account. The user ID and password that you supply are assigned as the launch credentials for a new SAS 9.2 server, the pooled workspace server, and stored in the metadata as follows:

  • If you supply a user ID that already exists in metadata, the migrated password in that login is overwritten with the password that you supply.

    For more information, see Password Policies in the SAS Intelligence Platform: Installation and Configuration Guide.

  • If you supply a user ID that doesn't already exist in metadata, the credentials that you supply are stored in a new login on the Accounts tab of the SAS General Servers group.

    For more information, see Launch Credentials in the SAS Intelligence Platform: Security Administration Guide.

• The migration process doesn't change any existing launch credential assignments. For example, if the SAS 9.1.3 stored process server has a login (for example, spsrv) as its designated launch credential, that assignment is preserved. If the spsrv account isn't valid on the SAS 9.2 machine, the stored process server won't work in the SAS 9.2 environment (until you change that server's launch credential).

Complete the following checklist to use later, during the installation and migration step, when the SAS Deployment Wizard prompts you for ports to designate for the new SAS 9.2 servers. The deployment wizard uses the same ports when migrating the SAS 9.1.3 servers.

Note:   This checklist assumes that you are migrating to SAS 9.2 using the same machines that you used to run SAS 9.1.3. (You can change these port assignments in SAS 9.2 with the Port Remap utility. For more information, see Change Ports and Host Names Used By SAS Products.) If you are using new machines, then you need to make sure that the same ports that you designated for your SAS 9.1.3 servers are available on the new machines. For more information, see "Designating Ports" in the SAS 9.1.3 Intelligence Platform: Installation Guide available at http://support.sas.com/913administration.  

The following table lists new servers that have been introduced in SAS 9.2:

After migration, you will need to reschedule all of your SAS flows. (See Reschedule Flows.) To do this you will need to know the user ID under which each flow is scheduled to run.

Follow these steps to determine the user ID associated with scheduled flows:

1. Log on to Platform Flow Manager.

2. Select the user ID tab.

3. For each user ID, note the flows associated with it.

The SAS automated migration tools ship with scripts that are used to assign the proper permissions to files and directories under the SAS configuration directory. If you are using required operating system user accounts and group names in SAS 9.2 that are different from the ones on your SAS 9.1.3 system, then you must make sure that the permissions reflect these changes.

During configuration, the SAS Deployment Wizard invokes the levconfig extension (a part of the migration package) which converts certain temporary files into corresponding permission script files (*.bat and *.sh files). The deployment wizard persists these permission script files in the SAS 9.2 configuration directory (under Levn/Temp) and then invokes them during configuration.

You have to do one of the following procedures:

• Before running the SAS Deployment Wizard, do the following:

  Replace occurrences of a SAS 9.1.3 external user account (for example, "ebiadmin") with the SAS 9.2 external user account (for example, "sasadm") in the *.tmp files in the levconfig\levconfig1 directory of the migration package (for example, /smu_package/host1.example.com/levconfig/levconfig1).

• Or, after running the SAS Deployment Wizard, do the following:

  Replace occurrences of a SAS 9.1.3 required external account with the SAS 9.2 required external account in the permission scripts residing in SAS 9.2-configuration-directoryLevn/Temp, and rerun these scripts.

Copyright © 2009 by SAS Institute Inc., Cary, NC, USA. All rights reserved.