Install and Configure SAS Enterprise Miner

Select Deployment Task. Select Install SAS SoftwareNext.

Specify SAS Home — Choose a file system location to use as the home folder for your SAS software. On Windows systems, the home folder location defaults to C:\Program Files\SASHome. You can use the Browse button to navigate to an alternate location for the SASHome folder. Click Next.

Select Deployment Type — Select Perform a Planned DeploymentInstall SAS SoftwareConfigure SAS Software. Click Next.

Specify Deployment Plan — Choose Select a standard deployment plan and select Enterprise Miner and Text Miner, three machines, JBoss. If your SAS representative provided you with a custom plan file, select Specify the full path to a customized deployment plan. This is the plan.xml file. Typically, the deployment plan is stored in the plan_files folder of the SAS Software Depot. If necessary, click Browse to navigate to your plan.xml file. Click Next.

Specify SAS Installation Data File — This is where you enter the path to your SID file. By default, the SID file is located in the SAS Software Depot, under the sid_files folder. If necessary, click Browse to navigate to this file. Click Next.

Select Language Support — Select the languages to install for the products that are listed. Only those languages that work with your locale are installed. Click Next.

Select Region Settings — This setting enables you to determine the format and display of language, region, and locale-specific information. You can choose to configure SAS as a Unicode server, and force SAS to use the UTF-8 encoding in all data sets, catalogs, and text that is written by SAS. This can be useful if you need to share such files with computers that have different language representations. Click Next.

Select Java Runtime Environment — If you have special requirements for a version of the Java Runtime Environment (JRE), you can choose Select an existing JRE and use the Browse button to navigate to your preferred JRE location. It is recommended that you use the default JRE. Click Next.

Specify SAS Text Analytics Document Conversion Host and Port — If you are installing SAS Enterprise Miner server with SAS Text Miner on a Windows machine, then SAS Document Conversion will be installed automatically on the same Windows machine. The default value for the host name is the name of the machine on which you are installing SAS Enterprise Miner server. The default port number is 7111. If you are installing SAS Enterprise Miner server with SAS Text Analytics on a UNIX machine, enter the host and Port from the Document Conversion installation from SAS Text Miner and the SAS Document Conversion Service. This example uses the default values. Click Next.

Checking System — Finally, the SAS Deployment Wizard checks to make sure the system has enough disk space to perform the installation. In addition, the SAS Deployment Wizard checks to see whether all of the necessary files and folders that it will write are accessible. The installation cannot proceed until access is enabled or granted to any listed files. When the examination of your file system is complete and the number of unwritable files is 0, click Next.

Select Configuration Prompting Level — Select Typical to display the basic set of configuration settings. To accept most defaults and for fewer options, select Express. For more granular configuration options, select Custom. To configure the SAS Enterprise Miner server, the Typical setting is recommended. Click Next.

Specify Configuration Information — This step creates your software’s configuration directory. The SAS Deployment Wizard can allocate up to 10 configuration levels. The default settings create a level-1 configuration. For this example, the default Configuration Directory is C:\SAS\EMTM and the Configuration Level is Lev1. This configuration is saved in C:\SAS\EMTM\Lev1. If you create a level-2 configuration, then the default Windows location is C:\SAS\EMTM\Lev1. Click Next.

Local Machine Name — By default, the Fully-qualified Local Host Name and the Short Local Host Name are filled in. Click Next.

Migration Information — Do one of the following:

Windows Options — This option creates a set of shortcuts that help with the management of the SAS servers that you are about to install. Click Next.

Windows Shortcuts — By default, all users on the machine will have the SAS Server Managements shortcuts available.

Integrated Windows Authentication — Detailed information about single sign-on is available in the SAS 9.3 Intelligence Platform Security Administration Guide. For this example, Use Integrated Windows Authentication is not used. Click Next.

SAS Metadata Server — For this three-machine installation, accept the Host Name and Port defaults. Record the local machine name and port for use in subsequent steps. Click Next.

Deployment Accounts: Types of Accounts — SAS internal accounts are service entities used only for SAS metadata administration. SAS internal accounts are intended to minimize the use of external accounts for SAS internal purposes. For this example, select SAS internal accounts. Click Next.

External Account: Installer — The user ID must be in qualified format, such as domain\userID or machine\userID. For Windows systems, make sure that this account has been given permission to set local security policy in the Pre-Installation tasks. The default account will be your current user ID. Provide the correct password and click Next.

SAS Internal Account: Unrestricted Administrator — This is the administrator for the SAS Metadata server. The password must contain at least six characters. Record and save this password in a safe place. It will be needed in the mid-tier installation instructions. Click Next.

SAS Internal Account: Trusted User — This is a privileged metadata service account that is required to access metadata on behalf of users. The password must contain at least six characters. Click Next.

Deployment Accounts: First User — You want to select this option because it creates a metadata user account for a demonstration user. This account is used to test the deployment. Click Next.

External Account: First User — Enter a valid external user ID. For a Windows account, you must provide the user ID in qualified formation, such as domain\userID or machine\userID. Click Next.

E-mail Server — Enter the host name and port number for the SMTP mail server from which alert messages should be sent to a system administrator. These messages are sent if the metadata server encounters problems. Click Next.

E-mail Address — The Sender E-mail Address is listed in the From field of the e-mail messages that are sent to the system administrator. Click Next. The Recipient E-mail Address specifies where the alert e-mail will be sent. Check the box for E-mail Server Requires Authentication if your e-mail server requires credentials for authentication. The e-mail server user ID and password will be entered on a subsequent page. For this example, this option is not check. Click Next.

SAS Object Spawner — Enter the port number used by the SAS Object Spawner to listen for operator connections. If you choose not to accept the default value, refer to your completed Pre-Installation Checklist for the value that you should enter. Click Next.

SAS Object Spawner: Port Bank — For this example, accept the default values. In deployments that support pooled workspace servers, these ports are used by the SAS Object Spawner as dynamic listening ports for the pooled workspace servers. Click Next.

SAS Application Server: Server Context — Enter the name of the server context for the application server definition. The server context name is prefixed automatically to all server names defined in the server context. 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 of (or context for) how it is being used and makes decisions based on that awareness. The default value of SASApp is recommended for this example. Click Next.

SAS Workspace Server — This is the port where the SAS Object Spawner will listen for client requests to launch workspace servers. If you choose not to accept the default value, refer to your completed Pre-Installation Checklist for the value that you should enter. Click Next.

Metadata Utility Workspace Server — Use of this server is limited to members of the SAS Administrators group. It is used only for metadata server administration tasks such as replication, promotion, and backup. Enter the port where the SAS Object Spawner will listen for client requests to launch the workspace server. If you choose not to accept the default value, refer to your completed Pre-Installation Checklist for the value that you should enter. Click Next.

Metadata Utility SAS/CONNECT Spawner — Access to this server is limited to members of the SAS Administrators group, and its use is limited to metadata server replication. Enter the port number to access the metadata utility SAS/CONNECT Spawner. If you choose not to accept the default value, refer to your completed Pre-Installation Checklist for the value that you should enter. Click Next.

SAS Framework Data Server — Enter the TCP/IP port number that is used by the SAS Web Infrastructure Platform to communicate with the SAS Framework Data server. If you choose not to accept the default value, refer to your completed Pre-Installation Checklist for the value that you should enter. Click Next.

SAS Framework Data Server: Transactional Database Files — This field specifies a local machine path where the database files are kept. The directory path specified here must be on the machine that is hosting the SAS Framework Data server. The directory path cannot be on a network location such as an NFS path or a shared network drive in Windows. Operating system permissions on the path must permit the server process user full control. Click Next.

SAS Data Step Batch Server — Enter the path to the deployment directory from the associated SAS programs. Click Next.

Metadata Utility SAS DATA Step Batch Server — Access to this server is limited to members of the SAS Administrators group. Its use is limited to metadata server backup. Click Next.

Operating System Services Scheduling Server — Enter the port number where the operating system services scheduling server will listen for the associated SAS Workspace Server. If you choose not to accept the default value, refer to your completed Pre-Installation Checklist for the value that you should enter. Click Next.

SAS Deployment Tester Server — The Deployment Tester tests other products, not SAS Enterprise Miner. Some of those other products use JUnit for validation. These products can operate properly without JUnit. However, you will not be able to validate them using the SAS Deployment Tester. If you want to validate other products with the Deployment Tester, enter the location of the JUnit.jar file. The JUnit.jar file is available from the Third Party Software Requirements Web page, located at http://support.sas.com/resources/thirdpartysupport/index.html. If you choose not to accept the default port value, refer to your completed Pre-Installation Checklist for the value that you should enter. Click Next.

IP Multicast Version — Select the IP version that is appropriate for your environment. IPv6 requires the network and all machines that contain SAS products to be IPv6 enabled. For this example, accept the default value of IPv4. Click Next.

IP Multicast — The multicast group communication includes all information needed to bootstrap SAS mid-tier applications. Because this includes sending the SAS environment credentials (such as the sasadm account name and its password), scoping and encryption options are provided. The default values are most appropriate for deployments in a firewall-isolated data center environment. The Deployment Wizard help documentation contains more information about these choices. Click Next.

Deployment Summary — Review the software selected before starting the installation process. If this information is correct, Click Next.

Select Deployment Task — Select Install SAS software. Click Next.

Specify SAS Home — This is where you choose a file system location for the home folder for your SAS software. On a Windows system, this will default to C:\Program Files\SASHome. You can use the Browse button to navigate to an alternate location for your SAS Home. Click Next.

Select Deployment Type — Select Perform a Planned DeploymentInstall SAS SoftwareConfigure SAS Software. Click Next.

Specify Deployment Plan — For this example, select Select a standard deployment planEnterprise Miner and Text Miner, three machines, JBoss. If your SAS representative provided you with a custom plan file, select Specify the full path to a customized deployment plan. You must specify the plan.xml file. Typically, the deployment plan is stored in the plan_files folder of the SAS Software Depot. If necessary, click Browse to navigate to your plan.xml file. Click Next.

Select Deployment Step and Products to Install — The deployment plan determines the products to install and what order they are installed in. In the Deployment Step field, select Step 2: Middle Tier. Click Next.

Specify SAS Installation Data File — This is the path for your SID file. By default, the SID file is located in the SAS Software Depot under the sid_files folder. If necessary, click Browse to navigate to it. Click Next.

Select Region Settings — Specify how you want your SAS Software to format language, region, and locale-specific information. Also, you can configure SAS as a Unicode server, and force SAS to use the UTF-8 encoding in all data sets, catalogs, and text output. This can be useful if you need to share such files with computers that use different language representations. Click Next.

Select Java Runtime Environment — If you have special requirements for a version of the Java Runtime Environment (JRE), use Select an Existing JRE and use the Browse button to navigate to your preferred JRE location. It is recommended that you use the default JRE. Click Next.

Checking System — The SAS Deployment Wizard checks to ensure that the system has enough disk space and that the files and folders it will write are accessible.

Review Required Software — This specifies the third-party software that will be required to continue the installation. In this example, the JBoss Web Application Server was required by the plan file that was chosen previously. You must select the check box for The Web Application Server and the Java Development Kit will be installed on another machine. Click Next.

Specify Software Location — In general, this is the complete file path for the Web Application server or HTTP server that was specified in the preceding dialog box, titled Review Required Software. For this example, enter the path to your JBoss files location. In Windows, that path will resemble C:\Program Files(x86)\EnterprisePlatform-4.3.0.GA_CP08\iboss-as. Click Next.

Specify Software Location — This is the complete file path for the Java Development Kit that was specified in the Review Require Software dialog box. In Windows, that path will resemble C:\Program Files\Java\jdk1.6.0_24. Click Next.

Select Configuration Prompting Level — Select Typical to display the basic set of configuration settings. To accept most defaults and for fewer options, select Express. For more granular configuration options, select Custom. To configure the SAS Enterprise Miner server, the Typical setting is recommended. Click Next.

Specify Configuration Information — This step creates your software configuration directory. The SAS Deployment Wizard can allocate up to 10 configuration levels. The default settings create a level–1 configuration. For this example, the default configuration directory will be C:\SAS\EMTM, and the configuration level will be Lev1. This configuration is saved in C:\SAS\EMTM\Lev1. If you create a level–2 configuration, the default location in Windows systems is C:\SAS\EMTM\Lev2. Click Next.

Local Machine Name — By default, the Fully-Qualified Local Host Name and the Short Local Host Name are given. Click Next.

Migration Information — Do one of the following:

Windows Options — This option creates a set of shortcuts that help with the management of the SAS servers that you are ready to install. Click Next.

Windows Shortcuts — By default, all users on the machine will have the SAS Server Management shortcuts available. Click Next.

Integrated Windows Authentication — Detailed information about single sign-on is available in the SAS 9.3 Intelligence Platform Security Administration Guide. In this example, the box for Use Integrated Windows Authentication is not checked. Click Next.

SAS Metadata Server — Enter theHost Name and Port used for the SAS Metadata Server in the first step of these instructions. Click Next.

Deployment Accounts: Type of Accounts — SAS internal accounts are service entities exclusively used for SAS metadata administration. SAS internal accounts are intended to minimize the use of external accounts for SAS internal purposes. For this example, select Use SAS internal accounts when appropriate. Click Next.

SAS Internal Account: Unrestricted Administrator — This is the administrator for the SAS Metadata server. You must use the same password that was specified in the first step of these instructions. Click Next.

SAS Internal Account: Trusted User — This is a privileged metadata service account required to access metadata on behalf of users. You must use the same password that was specified in the first step of these instructions. Click Next.

Anonymous Web Access — Deselect the option Enable Anonymous Web Access (optional), because it is not required for this example. Click Next.

E-mail Server — Enter the host name and port number for the SMTP mail server that will send messages to the system administrator when the metadata server encounters a problem. Click Next.

E-mail Address — The Sender E-mail Address is the address that is used to send e-mail messages to the system administrator. The Recipient E-mail Address is the address that will receive the server warnings. If your e-mail server requires logon credentials, enable the option E-mail Server Requires Authentication. The e-mail server user ID and password are entered on a subsequent page if you select this option. However, this example does not enable this option. Click Next.

SAS Deployment Tester Server — The Deployment Tester checks others products that use JUnit for validation. Without JUnit, these products can operate properly, but you will not be able to validate them with the Deployment Tester. If you want to validate this installation, enter the location of the JUnit jar file. The JUnit jar file is available from the Third-Party Software Requirements Web page, located at http://support.sas.com/resources/thirdpartysupport/index.html. If you choose not to accept the default port value, refer to your completed Pre-Installation Checklist for the value that you need to enter. Click Next.

SAS Remote Services Application — SAS mid-tier applications use this information to communicate with other SAS applications. For this example, accept the defaults. Click Next.

Event Broker Ports — The SAS Mid-Tier Event Broker listens for both HTTP and administrative events on these ports. Accept the defaults, or refer to your completed Pre-Installation Checklist for the values that you need to enter. Click Next.

Web Application Server: Automatic Configuration — By default, your Web application server will be configured to work with your SAS products. If you forgo automatic configuration of your Web application server, you will still be prompted for Web application server information and deployment stages. 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 you Web applications. For this example, accept the default values. Click Next.

Web Application Server: Scripting Configuration — If enabled, your SAS Configuration will generate a scripting tool and a set of configuration files that can be used for manual application server configuration. By default, this option is not selected. This example uses the default setting. Click Next.

Web Application Server: Managed Server — This is the logical name that will be used for your managed server. For this example, accept the default, SASServer1. Click Next.

Web Application Server: Managed Server Ports — If you choose not to accept the default values, refer to your completed Pre-Installation Checklist for the values that you should enter. For this example, accept the default values. Click Next.

Web Application Server: Automatic Deployment — If you choose not to automatically deploy Web applications, manual deployment instructions will be written to Instructions.html during the Web application deployment stage. For this example, choose to have Web applications automatically deployed to the Web application server. Accept the default values. Click Next.

Web Application Themes — Enter the host name to use when accessing themes. The default value is the name of the host where the configuration is performed. The port number provided here must be the same as the HTTP port of your managed server. If you choose not to accept the default values, refer to your completed Pre-Installation Checklist for the values that you should enter. The Configured Protocol is the communication protocol that is used when you access the installed themes. Accept the default value, which is HTTP Protocol. Click Next.

IP Multicast Version — Select the IP version that is appropriate for your environment. IPv6 requires that your network and all machines that contain SAS products be IPv6 enabled. For this example, IPv4 is selected. Click Next.

SAS Distributed In-Process Scheduling Server — These are the UDP ports and do not conflict with any previous TCP port definitions, such as the metadata server. Accept the default values. Click Next.

SAS Content Server: Repository Directory — The SAS Content Server stores application objects, such as registered SAS Enterprise Miner Model Packages. Enter the location on your disk for the files of this repository. The SAS Content Server will work with a DBMS for persistence. For information about working with a DBMS, see “Administering the SAS Content Server” in SAS Intelligence Platform: Middle-Tier Administration Guide. Accept the default values. Click Next.

SAS Web Infrastructure Platform: Database Type — To accept the recommended database for the SAS Web Infrastructure Platform, click Next.

SAS Web Infrastructure Database JDBC Properties — Specify the user ID and password that are used to access the database that contains your SAS Web Infrastructure Database tables. If you have chosen automatic configuration of a database for the SAS Web Infrastructure Database, this user ID must have the ability to create tables and insert records. If you have not chosen automatic configuration, this user ID must have the ability to create tables, insert records, and delete records. Accept the default values. Click Next.

Select Deployment Task — Select Install SAS Software. Click Next.

Specify SAS Home — Choose a file system location for the home folder for your SAS software. On Windows systems, this will default to C:\Program Files\SASHome. You can use the Browse button to navigate to an alternate location for your SAS Home. Click Next.

Select Deployment Type — Select Perform a Planned DeploymentInstall SAS SoftwareConfigure SAS Software. Click Next.

Specify Deployment Plan — For this example, choose Select a standard deployment planEnterprise Miner and Text Miner, three machines, JBoss. If your SAS representative provided you with a custom plan file, select Specify the full path to a customized deployment plant. This is the plan.xml file. Typically, the deployment plan is stored in the plan_files folder of the SAS Software Depot. If necessary, click Browse to navigate to your plan.xml file. Click Next.

Select Deployment Step and Products to Install — The deployment plan determines which products to install and in what order. In the Deployment Step field, select Step 3: Client. Click Next.

Specify SAS Installation Data File — This is the path to your SID file. By default, the SID file is located in the SAS Software Depot under the sid_files folder. If necessary, click Browse to navigate to this file. Click Next.

Select Language Support — Select the languages that you want to install for the products that are listed. Only those languages that work with your locale are installed. Click Next.

Select Regional Settings — Specify how you want your SAS Software to format and display language, region, and locale-specific information. Also, you can configure SAS as a Unicode server and force SAS to use UTF-8 encoding in all data sets, catalogs, and text output. This can be useful if you need to share these files with computers that use different language representations. Click Next.

Select Java Runtime Environment — If you have special requirements for a version of the Java Runtime Environment (JRE), choose Select an existing JRE and use the Browse button to navigate to your preferred JRE location. It is recommended that you use the default JRE. Click Next.

SAS Environments URL — Enter the URL for the SAS Environment File that you decided on in the Pre-Installation Tasks for SAS Enterprise Miner. This step lets you avoid manually creating and deploying a sas-environment.xml before using SAS Enterprise Miner. The default URL will resemble http://myserver.mynet.mycompany.com:8080/SASLogon/sas-environment.xml. For this example, the network machine name myserver.mynet.mycompany.com would be replaced with the name of the machine that contains the SAS middle tier, installed in Step 2 of these instructions. Click Next.

Checking System — The SAS Deployment Wizard checks to ensure that the system has enough disk space and that all files and folders it needs to write are accessible. The installation cannot proceed until access is granted to any listed files. When the examination of your file system is complete and there are no unwriteable files, click Next.

Select Configuration Prompting Level — Select Typical to display the basic set of configuration settings. To accept most defaults, and for fewer options, select Express. For more granular configuration options, select Custom. To configure the SAS Enterprise Miner server, the Typical setting is recommended. Click Next.

Specify Configuration Information — This step creates your software’s configuration directory. The SAS Deployment Wizard allocates up to 10 configuration levels. The default settings create a level–1 configuration. For this example, the default configuration directory is C:\SAS\EMTM, and the configuration level is Lev1. This configuration is saved in C:\SAS\EMTM\Lev1. If you create a level–2 configuration, it will be saved in C:\SAS\EMTM\Lev2. Click Next.

Local Machine Name — By default, the Fully-Qualified Local Host Name and the Short Local Host Name are provided. Click Next.

Migration Information — Do one of the following:

Integrated Windows Authentication — Detailed information about single sign-on is available in the SAS 9.3 Intelligence Platform Security Administration Guide. In this example, do not select the check box for Use Integrated Windows Authentication. Click Next.

SAS Metadata Server — Enter the host name and port that is used for the SAS Metadata Server, specified in Step 1 of these instructions. Click Next.

Deployment Summary — Review the software selections before starting the installation process. If everything is correct, Click Next.

Deployment Complete — Check all stages of the installation for errors or warnings. Click Next.

Additional Resources — Record these links for future reference. Click Finish.