Installing SAS 9.2 and Migrating Your SAS Content

Install and Migrate SAS Interactively

Installing and migrating SAS interactively with the SAS Deployment Wizard consists of two main phases:

providing installation information such as the following:
- deployment plan location
- machine type (metadata server machine, server machine, and so on)
- SAS components to be installed on the machine
- valid paths to any required pre-installed, third-party software
providing migration and configuration information such as the following:
- migration package location
- prompting level
- configuration directory name
- required user account credentials

This topic describes some of the more important configuration dialog boxes that you will encounter during the migration and configuration phase of a SAS 9.2 deployment. The type and number of configuration-related dialog boxes that you will see depend on the prompt level that you choose, the SAS tier that you are currently migrating, and the contents of your SAS 9.2 custom order. For information about all SAS Deployment Wizard prompts, see the online Help for the wizard page in question.

To migrate and configure SAS interactively, follow these steps:

Verify that you have performed the earlier required steps outlined in Overview of Installing SAS and Migrating Your Content.

Note: A few pages into the SAS installation, the SAS Deployment Wizard prompt you for paths to the requested third-party software. You must have the necessary third-party software installed on the current machine, or the SAS Deployment Wizard will not let you continue with the installation. In this situation, you will have to end the SAS Deployment Wizard session and install the required third-party software before you can continue.
If you use any garbage collection scripts, temporarily suspend these scripts during SAS Deployment Wizard execution. If any wizard temporary files are deleted during wizard execution, configuration failures can occur.
Ensure that you have the list of required user IDs available. For more information, see Completing the Pre-migration Checklists.
If you are deploying a middle-tier machine, make sure that you have read and understood the information in, Middle-tier Considerations.
Review information about where to source certain SAS content repositories described in the topic, Content Repository Considerations.
Review information about SAS Deployment Wizard configuration prompting levels described in the topic, Interactive Prompting Levels.
If you are deploying SAS on multiple machines, make sure that you are following the process described in Installation Order Rules for Multiple Machine Deployments.
Log on to the machine with a user ID that meets the requirements for the appropriate operating system:
- Windows
  
  Use the same account that was used to deploy SAS 9.1.3. This account must be a member of the Administrators group.
- UNIX
  
  Use the same account that was used to deploy SAS 9.1.3. Do not use root.
- z/OS
  
  Use the same account that was used to deploy SAS 9.1.3.
Make sure that the SAS 9.1.3 servers are not running on the machine on which your are currently migrating.

Note: In situations where you are rerunning the deployment wizard to address configuration errors, make sure that there are no SAS 9.2 servers running. On UNIX and z/OS, you can run the following command: ./sas.servers status. If any SAS 9.2 servers are running, shut them down with the following command: ./sas.servers stop.
- Windows
  
  Use the Windows Services snap-in to stop the SAS 9.1.3 servers. For more information, see your Windows documentation.
- UNIX and z/OS
  
  Use the server scripts to stop the SAS 9.1.3 servers. These scripts reside in the SAS configuration directory under the SAS Application Server directory for the respective server. For example:
  
  /opt/config913/Lev1/SASMain/MetadataServer/MetadataServer.sh -stop
  
  For more information, see the SAS 9.1.3 Intelligence Platform: System Administration Guide.

Start the SAS Deployment Wizard from the highest-level directory in your SAS Software Depot using the command appropriate for your operating system:

Start Up Commands for the SAS Deployment Wizard
Operating System	Command
Windows	setup.exe -record -deploy
UNIX	setup.sh -record -deploy
z/OS	setup.rexx -record -deploy To use a temporary directory other than /tmp, specify -templocation new-temp-dir.

Note: Using the -record -deploy options causes the wizard to create a response file that records the inputs that you supplied. This can be helpful when you want to repeat the deployment on other machines or when troubleshooting a deployment issue. [cautionend]

By default, the deployment wizard writes the response file in the following location:

Windows:

C:\Documents and Settings\current-user\sdwresponse.properties
UNIX and z/OS:

~/sdwresponse.properties

You should see a welcome screen similar to the following:

[SAS Deployment Wizard splash screen]

Select the language that you want the SAS Deployment Wizard to use when it displays text.
Select Install SAS Software.
Select Perform a Planned Deployment, and make sure that Install SAS Software and Configure SAS Software are both checked.
Specify the location (SAS Home) where you want to install SAS.

Note: The deployment wizard prompts you for SAS Home the first time that you run the wizard. On any subsequent sessions on this machine, the wizard uses the previously specified location for SAS Home.
Specify the type of deployment plan you are using:
- customized deployment plan
  
  Choose Specify the full path to a customized deployment plan, and then click Browse to navigate to the plan file.
- standard deployment plan
  
  Choose Select a standard deployment plan, and then choose the appropriate plan in the drop-down list.
  
  For more information, see About Deployment Plans.
Select the machine on which you are installing software, and select the SAS products that you want to install, by doing the following:
1. Select the machine on which you are installing software from the Machine drop-down list.
2. By default, all products displayed will be installed. Deselect any products that you do not want to install.
Specify the location of the SAS installation data file that contains information about the software that you have licensed for the current machine.

CAUTION:
If you do not use the installation data file that supports the products you are planning to install and configure on this machine, you might experience errors later when you are trying to use the products.
Deselect any languages that you do not want SAS to support. By default, SAS attempts to support all languages that your machine's operating system is configured for.

The deployment wizard prompts you to do one of the following:

(z/OS only) No Java Runtime Environment

Select to have the deployment wizard install your software on z/OS without a Java Runtime Environment (JRE).

(UNIX and Windows only) Use the recommended Java Runtime Environment

(Recommended) select to have the deployment wizard install the required JRE on this machine.

On UNIX, specify in the text box where you want the deployment wizard to extract the JRE.

Select an existing Java Runtime Environment

Select to specify the path to a JRE that you have already installed on this machine.

For more information, see http://support.sas.com/resources/thirdpartysupport/v92/jres.html.

(z/OS only) Provide input for the following prompts:

Note: For more information, see the Configuration Guide for SAS 9.2 Foundation for z/OS, available on the SAS Install Center (http://support.sas.com/documentation/installcenter/).
- FTP Batch Generation
  
  Specify the fully qualified host name or IP address of the z/OS mainframe machine on which you are deploying SAS. Also supply a valid user ID and password with which the SAS Deployment Wizard will FTP deployment information to the mainframe machine.
- Specify Jobcard Information
  
  Specify the job account, programmer-name, message class, message level, time, and region values. For more information, consult your z/OS documentation.
- Media Type
  
  Select the check box if installing from cartridge tape media. Leave the check box deselected if you are installing from a DVD or from the Internet.
- Select Installation Action
  
  Choose A - Install a new SAS system.
- Specify New Installation Qualifier
  
  Specify the path where you want to install SAS. You can also choose to require Storage Management Subsystem (SMS) parameters. For more information, consult your z/OS documentation.
- Specify IBM's SMS Parameters
  
  If you chose to require Storage Management Subsystem (SMS) parameters in the previous page, enter them here. For more information, consult your z/OS documentation.
- Specify Parameters
  
  These are all parameters that are used in various DD statements throughout the installation. For more information, consult your IBM JCL documentation.
- Specify Entry Point
  
  Specify the parameters for various ways that SAS can be run with different performance implications. Choose SAS (default ENTRY point) to run the unbundled configuration. Choose SASB to run the bundled configuration. Choose SASLPA to run the bundled configuration with some modules installed in the Link Pack Area (LPA).
- Specify Parameters
  
  Specify additional parameters for DD statements. VOLDISK designates the VOLSER that the installed data sets will go to. For more information, consult your IBM JCL documentation.
- Specify Parameters
  
  Specify parameters used for reblocking the SAS load modules to a library with an optimum block size.
(UNIX only) If your system uses Pluggable Authentication Modules (PAM), select Use PAM Authentication. In addition, you might also need to update your PAM configuration files in order for SAS 9.2 to use PAM authentication. For more information, see the Configuration Guide for SAS 9.2 Foundation for UNIX Environments.

If you are uncertain that this system uses PAM for authentication, contact your system administrator.

Note: Do not select the PAM option if you know that your system uses /etc/password or /etc/shadow authentication.
Review the list of required third-party software that is required for the SAS software that you are installing on the current machine. (The list of third-party software depends on the SAS software that you are installing on the current machine.)
In the pages that immediately follow, be prepared to provide paths to these third-party applications. (The number of pages varies depending on the SAS software you are deploying on the current machine.)

Note: You must provide valid paths to the requested third-party software, or the SAS Deployment Wizard will not let you continue with the installation.

Specify the amount of information to provide the SAS Deployment Wizard for configuring the SAS software you are installing on the current machine. Choose one of the three prompting levels:

Express

displays the minimum number of wizard pages needed to complete the SAS configuration.

Typical

displays the basic set of wizard pages needed to complete the SAS configuration.

Custom

displays all the wizard pages needed to complete the SAS configuration.

Refer to Interactive Prompting Levels for more information about the SAS Deployment Wizard prompting levels.

Specify Configuration Information

Choose a path where the SAS Deployment Wizard will write SAS 9.2 configuration files and logs and the level you want to deploy. (For example, Lev1 = production.) This path should differ from your SAS 9.1.3 configuration path.

Note: The last digit of the default port number reflects the configuration level that you select in the SAS Deployment Wizard. For example, when you select Lev1, the default port for the metadata server is 8561. If you choose another level, such as Lev2, the wizard changes the default port to 8562. During a migration, this setting pertains only to ports for servers that are introduced in SAS 9.2, such as the table server. The deployment wizard will retain the port settings from your SAS 9.1.3 servers. For information about how to change port numbers, see Change Ports Used By SAS Products.

For more information, see Overview of the Configuration Directory Structure in the SAS Intelligence Platform: System Administration Guide.

Note: Although your SAS Home and SAS configuration directories can share the same parent directory, one directory should not reside inside another. Defining the configuration directory under the SAS Home directory, or vice versa, can lead to file permission issues arising from the need to manage installed files differently from site-specific configurations.

On z/OS, the mount point must exist; the SAS Deployment Wizard will create the necessary subdirectories.

If you are deploying the SAS Table Server, then SAS configuration path should be a path local to the machine. The configuration path should not be on an NFS shared disk. If you want to put your configuration path on a shared disk, then you must make sure that you specify a local path for the table server content directory. You can set the content directory on the Table Server Invocation Options page. This page is available only on the custom configuration prompting level.
Select Products to Configure

Migrating via the SAS Deployment Wizard should be performed only once per tier for a deployment. You cannot selectively choose products to migrate. You must migrate all products targeted for the current machine.
Local Machine Name

Enter the complete name of the local host in Fully-qualified Local Host Name. The fully qualified local host name typically takes the form of the local host name plus the domain name server (for example, myserver.example.com). Enter a short host name in Short Local Host Name. The short local host name is the abbreviated, more common method of referring to the host, usually only a single word.
Migration Information

Choose Perform Migration and enter the path to the package that you created with the SAS Migration Utility. This path should be to the top level directory of the migration package (for example: C:\SMU\913_Deployment). (This path should match the value of the SMU.Output.Dir property.)

Note: Migrating via the SAS Deployment Wizard should be performed only once per tier for a deployment. (Also, you cannot selectively choose products to migrate. You must migrate all products targeted for the current machine.) If SAS components are unconfigured for a particular tier, you cannot migrate them a second time by choosing Perform Migration. In this situation, you have to perform a standard, non-migrated configuration using the deployment wizard (unless you want to unconfigure the entire SAS deployment).

CAUTION:
The Perform Migration check box should not be selected when running the SAS Deployment Wizard on any client tiers. The Perform Migration check box should be selected only when there is content available in the SAS Migration Utility package for that machine.
If you are performing a multiple machine deployment, and are migrating a machine other than the metadata server, the wizard prompts you to select the machine to migrate.

Note: If you have already deployed the metadata tier and you have only a total of two tiers, the deployment wizard automatically selects the remaining tier for you.
Provide the remaining migration and configuration information as the wizard prompts you for it.

Note: This topic describes some of the more important pages that you will encounter during the migration and configuration phase of a SAS 9.2 deployment. The options for which the SAS Deployment Wizard prompts you depends on which SAS products are identified in your deployment plan and, in multiple machine deployments, which machine you are currently deploying. For information about all SAS Deployment Wizard prompts, see the online Help for the wizard page in question.
- Authentication Domain
  
  Accept the default value (DefaultAuth), unless the deployment that you are migrating uses a different SAS authentication domain for servers on this machine.
  
  For example, if the metadata server is on Windows and the workspace server is on UNIX, the workspace server might be assigned to a SAS authentication domain named UnixAuth. For more information, see "About Authentication Domains" in the SAS Management Console: Guide to Users and Permissions available at http://support.sas.com/documentation/cdl/en/mcsecug/61708/HTML/default/aboutum.htm.
  
  Note: Authentication domain assignments from the original deployment are always preserved. This prompt affects only new servers that are introduced in the 9.2 environment.
- Windows Options (run as managed scripts or services)
  
  On Windows, choose how to run your SAS servers either by using management scripts or running them as Windows services. If you choose the script option, then the user account that runs the object spawner must meet the following requirements on the object spawner machine:
  - be the administrator or a member of the Windows Administrator's group
  - have the following Windows local user rights:
    - Adjust memory quotas for a process
    - Replace a process level token
- Integrated Windows Authentication
  
  Select to use Integrated Windows authentication (IWA) for workspace servers running on Windows only. IWA supports a single sign-on feature in which a metadata server running on Windows accepts a user's previous authentication to his or her Windows desktop when the user attempts to access a workspace server.
  
  Selecting this page when you are deploying a workspace server on Windows enables the workspace server to use IWA. You also encounter this page when deploying SAS Enterprise Guide and SAS Add-In for Microsoft Office. If you have not chosen IWA for the workspace server, then choosing IWA for these clients has no effect.
  
  For more information, see Integrated Windows Authentication in the SAS Intelligence Platform: Security Administration Guide.
  
  By default, a metadata server running on Windows has IWA turned on by default. For more information, see SSPI System Option in the SAS Intelligence Platform: Application Server Administration Guide.
- SAS Metadata Server
  
  If you have any changes for the metadata server, enter them in this page.
  
  The deployment wizard creates a separate server context (SASMeta) for the metadata server and the other servers required to perform metadata server utility functions, such as backup and promotion. A server context is a SAS IOM server concept that describes how SAS Application Servers manage client requests. A SAS Application Server has an awareness (or context) of how it is being used and makes decisions based on that awareness. The server context name is prepended to all server names defined in the server context. Therefore, we recommend that you not change the logical server or server prefix (SASMeta).
  
  For more information, see Overview of the SAS Metadata Server and Its Initial Configuration in the SAS Intelligence Platform: System Administration Guide.
- Deployment Accounts: Type of Accounts
  
  Select whether to use internal accounts when appropriate. Internal user accounts are accounts known only to SAS and are created and authenticated internally in metadata rather than externally. For more information, see Choose to Use SAS Internal Accounts.
  
  Note: On Windows, whenever the deployment wizard prompts you for an external account, always enter a domain-qualified user account (for example, myDomain\myAccount).
- External Account: Unrestricted Administrator
  
  Enter user ID and password for an account known to the host that will serve as an unrestricted administrator for the purpose of configuring the SAS metadata server. On Windows, enter a domain-qualified user ID. If your SAS 9.2 operating system user account is different from the one you use for SAS 9.1.3, then you must be sure to make the corresponding file permissions changes. For more information, see Permission Considerations when User Accounts or Groups Change.
- External Account: Trusted User
  
  Enter the user ID and password for an account known to the host that will enable the SAS server and spawner components to communicate securely with each other. On Windows, enter a domain-qualified user ID. If your SAS 9.2 operating system user account is different from the one you use for SAS 9.1.3, then you must be sure to make the corresponding file permissions changes. For more information, see Permission Considerations when User Accounts or Groups Change.
- SAS BI Web Services: Authentication Method
  
  Select the method by which users of SAS BI Web Services are authenticated:
  - SAS Authentication is managed by the metadata server.
  - Web Authentication is managed by the Web application server using container-based authentication or a third-party product. Selecting Web authentication has these effects:
    - fully configures Web authentication for .NET BI Web Services.
    - partially configures Web authentication for Java BI Web Services.
      
      For more information, see Securing SAS BI Web Services for Java in the SAS Intelligence Platform: Web Application Administration Guide.
    - has no effect on the BI Web applications (such as SAS Web Report Studio, SAS Web Information Portal, and so on).
      
      You will have to configure Web authentication for these BI Web applications.
    - prevents you from being offered a chance to set up an anonymous Web user (as this is incompatible with Web authentication).
- Anonymous Web Access
  
  When using SAS authentication you can select this option to set up a SAS identity for anonymous access to certain Web services and Web applications that support this feature. Currently, SAS BI Web Services for Java and .NET and the SAS Stored Process Web Application are the only components that support this feature.
  
  For more information, see Using the SAS Anonymous Web User With SAS Authentication in the SAS Intelligence Platform: Web Application Administration Guide.
- External Account: Anonymous Web User
  
  (Optional) Enter the user ID and password for an account to be used to grant clients access to applicable SAS Web Infrastructure Platform applications such as SAS BI Web Services and the Stored Process Web Application. On Windows, enter a domain qualified user ID. When SAS authentication is being used and the user has not preemptively specified credentials, the client will be given access to these Web applications under the anonymous user account.
  
  For more information, see Using the SAS Anonymous Web User With SAS Authentication in the SAS Intelligence Platform: Web Application Administration Guide.
- External account: SAS Spawned Servers Account
  
  Enter the user ID and password for the external account to be used to start the pooled workspace server and the stored process server. On Windows, enter a domain qualified user ID. For migration purposes, you must use the same operating system accounts and passwords that you had in SAS 9.1.3.
  
  For more information, see Important Notes on User Accounts and Authentication.
- Create Common Directories
  
  Select to create common directories for server and spawner logs, user-specific files, and temporary work tables and files.
  
  When you select this option, the deployment wizard creates the specified directory (Logs, Users, and Temp) under the SAS configuration directory.
- Server Encryption
  
  Select the encryption level and algorithm that SAS clients and servers use to connect to the metadata server.
  
  Choose Credentials to encrypt only login credentials. Choose Everything to encrypt all communication with the metadata server.
  
  To specify an encryption algorithm other than SASPROPRIETARY, you must have a license for SAS/SECURE software. The other algorithms are: RC2, RC4, DES, TripleDES, and AES.
  
  For more information, see Encryption Model in the SAS Intelligence Platform: Security Administration Guide.
- Client-side Credentials Policy
  
  Select this option to set the policy to allow users to save their user IDs and passwords in client-side connection profiles on the metadata server for desktop applications. This input sets the value for OMA_SASSEC_LOCAL_PW_SAVE in omaconfig.xml.
  
  For more information, see Reference Information for omaconfig.xml in the SAS Intelligence Platform: System Administration Guide.
- E-mail Server
  
  Enter the port and host name for an SMTP e-mail server that the SAS Metadata Server uses to send e-mail alerts to an administrator if journaling issues arise. The SAS Deployment Wizard also uses this e-mail server as the default for the SAS Application Server to provide e-mail services to various SAS clients. For example, with SAS Data Integration Studio, you can use a Publish to Email transformation to alert users about various data changes. In order for SAS BI Dashboard to send alerts by e-mail to dashboard users and administrators, the port and host name must be configured for the e-mail server.
  
  For more information, see Overview of Adding or Modifying E-Mail Settings for SAS Application Servers in the SAS Intelligence Platform: Application Server Administration Guide.
- SAS Pooled Workspace Server
  
  Enter the name of the logical pooled workspace server and the pooled workspace in metadata. You also need to enter the name of the machine on which the pooled workspace server runs and the port on which the object spawner will listen for client requests to launch pooled workspace servers. The machine name should match the name specified to the object spawner.
  
  The pooled workspace server is a new SAS 9.2 server. For more information, see Overview of Workspace Servers and Stored Process Servers in the SAS Intelligence Platform: System Administration Guide.
- SAS Pooled Workspace Server Dependencies
  
  Make sure that you choose an application server context that exists in the foundation repository, or SAS components dependent on the pooled workspace server (such as SAS BI Dashboard) won't be able to access the server.
- SAS Table Server
  
  Enter the name of the logical table server in metadata. You also need to enter the name of the machine on which the table server runs and the TCP/IP port on which the table server will listen to.
  
  The table server is a new SAS 9.2 server for use with SAS Shared Services. For more information, see the SAS Intelligence Platform: Web Application Administration Guide.
- Metadata Utility SAS DATA Step Batch Server
  
  Enter the various values required to configure a SAS DATA step batch server. The directory fields identify where the deployed SAS program is stored and the name of the deployed SAS DATA step program job. Access to this server is limited to members of the SAS Administrators group, and its use is limited to metadata server backup.
  
  For more information, see Contents of the Metadata Server Subdirectory (SASMeta) in the SAS Intelligence Platform: System Administration Guide.
- Query Cache Library
  
  Enter the physical location on the file system where the SAS library will exist for temporary files used when creating optimized tables for query look-up.
  
  In Query Cache Libref, enter the SAS library reference which SAS will use to refer to the query optimizer SAS library. The name must be eight characters or shorter and should be unique from other librefs used within this repository. Librefs must start with a letter or underscore and contain only letters, numerals, or underscores. The typical installation libref name is wrstemp. The libref will be used in conjunction with the server context name to form the SAS library name for the optimizer library.
  
  Select Enable Query Cache to allow the query optimizer to run. If this selection is not made, then the query optimizer will not attempt to optimize queries and will not create temporary data sets for improving performance during rendering. A typical installation will have this selection turned on. The temporary files created within the query cache library will be visible to anyone with Read permission on the Renderer Optimizer directory, so if you have security concerns with the authorization on this folder you might want to leave the optimizer off.
  
  For more information, see Using the Query Cache in the SAS Intelligence Platform: Web Application Administration Guide.
- Output Management Library
  
  Enter the physical location on the file system where the SAS library will exist for burst set definition tables for reports which will be distributed by e-mail. A burst definition table will contain e-mail addresses, channels, and possibly by group information.
  
  In Output Management Library Libref, enter the SAS library reference that SAS will use to refer to the output management SAS library. The name must be eight characters or shorter and should be unique from other librefs used within this Repository. Librefs must start with a letter or underscore and contain only letters, numerals, or underscores. The typical installation libref name is wrstemp. The libref will be used in conjunction with the server context name to form the SAS library name for the distribution library.
  
  For more information, see Verifying Permissions for the Distribution Library in the SAS Intelligence Platform: Web Application Administration Guide.
- Web Application Server: Automatic Configuration
  
  Select this option for the deployment wizard to automatically build and configure the SAS Web applications as well as configuring a sample Web application server for use with SAS 9.2. (To use this wizard feature, be sure that your Web application server is not running before proceeding. For WebSphere, it is necessary to stop all deployment manager servers, all node agent servers, and all application servers before continuing with your SAS 9.2 deployment.) For more information, see Middle-tier Considerations.
  
  If you choose not to automatically configure your Web application server, you will still be prompted for Web application server information, and deployment stages such as Configure Products, Deploy Web Applications, and Start Web Application Servers will execute to create instructions for manual deployment. When configuration is complete, follow these manual instructions on how to configure your server and deploy your Web applications. If you manually configure WebLogic, a reference domain will be created in your SAS configuration area, but no servers will be started. If you manually configure JBoss, sample start scripts will be created, but not launched.
  
  For more information, go to http://support.sas.com/resources/thirdpartysupport/v92 and search for the product name of your Web application server.
- Web Application Server: Multiple Managed Servers
  
  Select to have the deployment wizard automatically configure multiple managed servers for you using SAS best practices for choosing the server to deploy each application to.
  
  In some situations it might be preferable to split the SAS Web applications across multiple managed servers. This is usually done for performance reasons.
  
  If you chose to manually configure your Web application servers, you will be provided with recommended configuration settings in a generated instructions file (Instructions.html) when the SAS Deployment Wizard completes.
  
  More advanced performance configuration considerations are documented in the SAS Business Intelligence Application Administration Guide, which can be found at http://support.sas.com/92administration.
- Web Application Server: Managed Server
  
  Enter a logical name for your managed server. This name will be displayed in your Web application server administrative console and used in administrative scripting.
  
  In HTTP Port, enter the unsecured port on which the managed server will listen.
  
  In HTTPS Port, enter the SSL port to be assigned to the managed server.
  
  In RMI Port, enter a port using these considerations:
  - WebSphere
    
    This maps to the RMI BOOTSTRAP port. Each server contains an administrative services component and a separate and unique port is required for each Web application server.
  - JBoss
    
    This maps to the default JNDI port. Clients connecting to applications running on JBoss, such as the JBoss shutdown command, would use this port.
  - WebLogic
    
    No RMI port is required for WebLogic.
  In Configured Protocol, select the communication protocol for the administration server: HTTP or HTTPS. Automated configuration through the SAS Deployment Wizard only supports the HTTP protocol. If you perform a manual configuration, you can set up HTTPS.
  In Additional JVM Options, enter any additional Java options that you want the managed server JVM (Java Virtual Machine) to use. These JVM options are tagged onto the end of the managed server's command line. Options that are deployment wizard defaults can be overridden in this way.
  
  For more information, go to http://support.sas.com/resources/thirdpartysupport/v92 and search for the product name of your Web application server.
- SAS Shared Services database properties (not displayed when SAS Table Server is selected)
  
  Enter the host name, fully qualified host name, or IP address for the host where the database is installed. Specify the port that the database server is listening to, and the name of the database that will contain the SAS Shared Services tables.
  
  Choose Automatically create tables and load data to have the deployment wizard automatically create tables and load the selected pre-existing database with initial data.
  
  In the case of MySQL, the Shared Services configuration process will also create a new MySQL database in addition to creating tables and loading data. The new database is named according to the value specified in the Database Name field.
  
  Note: If you are using MySQL, do not specify a pre-existing MySQL database or the configuration will fail. For more information, see "Configuring an Alternative Database for SAS Shared Services" at: http://support.sas.com/resources/thirdpartysupport/v92m3/appservers/SharedServicesAlternativeDatabase.pdf.
  
  For more information, see About SAS Shared Services in the SAS Intelligence Platform: Web Application Administration Guide.
- SAS Shared Services JDBC Properties
  
  Enter the user account and its password for accessing the database used with your SAS Shared Services tables.
  
  If you have selected to automatically configure the SAS Shared Services database, this user account must have the ability to create tables and insert records. If you are not automatically configuring the SAS Shared Services database, this user account must have the ability to insert, update and delete records. The default user account is the SAS Trusted User account (sastrust@saspw). For more information, see About SAS Shared Services in the SAS Intelligence Platform: Web Application Administration Guide.
  
  In Directory containing JDBC driver jars enter the appropriate JDBC driver jars and your selected RDBMS database and version. Inappropriate or additional jar files will cause configuration failures, so just copy the minimum required jars to the JDBC driver jars directory.
- Web Application Server: Automatic Deployment
  
  Select to automatically deploy SAS 9.2 Web applications to the Web application server. For more information, see Middle-tier Considerations.
  
  Regardless of whether you choose to automatically deploy your SAS Web applications, when building Web applications, the wizard also automatically explodes Web application archive files (.EAR files).
  
  If you choose not to automatically deploy SAS Web applications, the deployment wizard writes manual deployment instructions to Instructions.html during the Web application deployment stage, that you will need to complete after the wizard finishes executing. For more information, go to http://support.sas.com/resources/thirdpartysupport/v92 and search for the product name of your Web application server.
  
  Note: The SAS Deployment Wizard does not automatically deploy SAS OnlineDoc for the Web, even when you choose the automatic deployment option. You must manually deploy SAS OnlineDoc for the Web. For more information, see Deploying SAS OnlineDoc Manually for the Web in the SAS Intelligence Platform: Web Application Administration Guide.
- External Account: Web Application Server Administrator
  
  You are prompted for this information if your site uses the WebSphere or WebLogic Web application server. Enter the user ID and password for the administrator account for either the WebSphere Application Server or the WebLogic Server. On Windows, be sure to enter a domain-qualified user ID.
  - For WebSphere, the Web application server administrator user ID is the administrator account specified when WebSphere Admin Security was enabled.
  - For WebLogic, the Web application server administrator user ID is used to configure the WebLogic default security realm. When the deployment wizard automatically configures your Web application server, the wizard uses these credentials to create the administrator account and the WebLogic domain.
    
    If you choose to manually configure your Web application server, you will need to create this administrator account (using the credentials you define here) with the WebLogic administrative tools.
  For more information about configuring Web application servers to support the SAS middle tier, go to http://support.sas.com/resources/thirdpartysupport/v92 and search for "WebSphere" or "WebLogic".
- Web Application Server : Proxy Information
  
  If you are using SAS Information Delivery Portal RSS feeds, then you will have to provide proxy server information. Enter the fully qualified host name for the proxy server and its port that your site uses to access the Internet.
  
  For NonProxy Hosts enter the DNS names of all the machines that should not be accessed through the proxy server. Be sure to include other machines where application servers are configured as part of a common WebLogic Domain or are part of a WebSphere cell. Separate each machine name with a vertical line character (|). Use an asterisk (*) as a wildcard for an entire subnet. For example, *.subnet.com excludes all machines with a DNS name that ends with .subnet.com.
  
  If your site does not allow Internet access on production systems, refer to configuration information available at this SAS Web site: http://support.sas.com/resources/thirdpartysupport/v92. (Search for your Web application server.)
- WebSphere Application Server: Node
  
  In Profile Name, enter a profile name, or accept the default (SAShostname01). The profile name is used for the directory that contains the node agent and the SAS Web application server.
  
  The node agent name is required, but cannot be configured using the deployment wizard.
  
  In Node Name, enter a node name or accept the default (SAShostnameNode). The node name is the WebSphere node that contains one or more of the Web application servers.
  
  In Additional JVM Options, enter any additional Java options that you want the Web application servers to use.
- IP Multicast
  
  Accept these IP multicast settings or enter new ones.
  
  A multicast group communications protocol is used to communicate among middle-tier SAS applications in a single SAS deployment (the set of applications connected to the same metadata server). The combination of multicast IP 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. The defaults are most appropriate for deployments in a firewall-isolated data center environment.
  
  For more information, see Designating Ports and Multicast Addresses in the SAS Intelligence Platform: Installation and Configuration Guide.
- SAS Remote Services Application: JVM
  
  Enter the desired initial heap size for the remote services application using the JVM option format.
  
  In Max JVM Heap Size, enter the desired maximum heap size for the remote services application using the JVM option format.
  
  In Additional JVM Options, enter any additional Java options that you want the Remote Services VM to use. For example, you might want to add -Dmulticast_udp_ip_ttl=1 to restrict multicast traffic to a single subnet based on your network topology.
  
  For more information, go to http://support.sas.com/resources/thirdpartysupport/v92 and search for "SAS 9.2 Web Applications: Tuning for Performance and Scalability".
- SAS Web Report Studio: Scheduling
  
  Choose whether to enable scheduling for SAS Web Report Studio. If Platform Suite for SAS is in your deployment plan, then you have a choice between using Platform Process Manager, provided by Platform Computing, Inc., or SAS In-Process Services.
  
  For more information, see Setting Up Scheduling Using Platform Suite for SAS or Setting Up Scheduling Using SAS In-Process Scheduling in Scheduling in SAS.
- SAS Content Server: Repository Directory
  
  Enter the location on the disk for the actual contents of the content repository.
  
  The content server is a new SAS 9.2 server. For more information, see Administering the SAS Content Server in the SAS Intelligence Platform: System Administration Guide.
- SAS Web Parts for Microsoft SharePoint: Details
  
  We recommend that you accept the defaults.
  
  The Web URL is the address of the web application where the SAS Web Parts solution is deployed.
  
  The Site URL is the site collection where the feature is activated. A web application can have multiple site collections and a site collection can contain multiple sites. In most instances the URLs are the same (a site collection at the root of the web application), but they can also be different.
  
  For more information, contact your site's SharePoint administrator.
  
  The SAS User ID is the metadata identity that you use to implement shared identity mode. For more information, see Configure User Access for SAS Web Parts for Microsoft SharePoint in the SAS Intelligence Platform: Installation and Configuration Guide.
- SAS Information Delivery Portal unchallenged access
  
  When unchallenged access is enabled, users can access the portal and interact with selected content without providing a user ID and password.
  
  Enter a user ID that SAS will use to grant unchallenged access to portal users. (On Windows, make sure to qualify the User ID as appropriate. For example, myDomain\sasguest.)
  
  Deselect Display Search Menu for Unchallenged Access if you want to suppress the search link from displaying in the main portal banner.
  
  Specify what should appear in the portal banner for unchallenged users:
  - logoff
    
    Display the Log Off link.
  - logon
    
    Display the Log On link (which users can click to display the SAS Logon Manager).
  - hide
    
    Hide the Log Off and Log On links.
  For more information, see Enabling Unchallenged Portal Access in SAS Intelligence Platform: Web Application Administration Guide.
When you see the Deployment Summary page, the deployment wizard has finished collecting installation and configuration input. This is the last opportunity to go back and change any information you have provided in previous pages before the wizard begins writing to your system.

Note: Before proceeding with the migration, make sure that the input that you have provided to the deployment wizard is correct. Incorrect user input such as user ID and passwords will cause all or portions of your migration to fail.

Make one of the following choices:
- Click Start to begin installing SAS files and writing the configuration to the current machine.
- Click Back to navigate to earlier wizard pages to change installation and configuration information previously entered.
- Click Cancel to terminate the wizard session. Note that you will lose installation and configuration information previously entered.
  
  Note: If you encounter a situation in which the deployment wizard reports a configuration failure, consult Overview of Troubleshooting Your Initial SAS 9.2 Deployment in the SAS Intelligence Platform: Installation and Configuration Guide.
On UNIX, when you are installing the server tier, you will be prompted to enter the root password. As the message in the installation program explains, 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.

When you see a page similar to the following, the SAS Deployment Wizard is finished:

The deployment wizard has installed, configured, and started SAS processes on your machine.

If you had any errors, you will see a link to ConfigurationErrors.html.
Proceed to the section, Review SAS Deployment Wizard Documents and Reports to examine the SAS Deployment Wizard output to troubleshoot any configuration errors and complete any necessary manual configuration steps.
Click Finish to close the deployment wizard.
For multi-machine deployments, back up your metadata repository and your SAS configuration directory before you run the SAS Deployment Wizard on the next machine called for by your deployment plan. (You do not need to back up machines that contain only SAS 9.2 clients.)
- Make a backup copy of your SAS 9.2 configuration directories by using your site-approved method. Your SAS configuration directories are all the child directories beneath the path that you specified earlier in this procedure on the Specify Configuration Information page.
- Back up your Web application server directories.
- Back up your metadata repository and repository manager on the SAS Metadata Server machine. For more information, see Best Practices for Backing Up and Restoring Your System in the SAS Intelligence Platform: System Administration Guide.
When you are finished completing any manual configuration tasks, and you have made the necessary backups, repeat the steps listed in this topic on each machine defined in your deployment plan.
Be sure to restart any servers that you stopped for purposes of creating a backup.
When you are finished installing and migrating SAS on each machine called for in your deployment plan, proceed to the section entitled, Overview of Performing Post-migration Tasks.

Top of Page