SAS Planning Application 2.0: User s Guide

Transcription

1 SAS Planning Application 2.0: User s Guide

2 Copyright Notice The correct bibliographic citation for this manual is as follows: SAS Institute Inc., SAS Planning Application 2.0: User s Guide, Cary, NC: SAS Institute Inc., SAS Planning Application 2.0: User s Guide Copyright 2016, SAS Institute Inc., Cary, NC, USA. All rights reserved. Printed in the United States of America. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, by any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. Limited permission is granted to store the copyrighted material in your system and display it on terminals, print only the number of copies required for use by those persons responsible for installing and supporting the SAS programming and licensed programs for which this material has been provided, and to modify the material to meet specific installation requirements. The SAS Institute copyright notice must appear on all printed versions of this material or extracts thereof and on the display medium when the material is displayed. Permission is not granted to reproduce or distribute the material except as stated above. U.S. Government Restricted Rights Notice. Use, duplication, or disclosure of the software by the government is subject to restrictions as set forth in FAR Commercial Computer Software-Restricted Rights (June 1987). SAS Institute Inc., SAS Campus Drive, Cary, North Carolina SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are trademarks of their respective companies.

3 Table of Contents Chapter 1 Getting Started... 1 What is a plan file?... 1 How is the plan file used in the software deployment process?... 1 Who uses the planning application?... 1 Chapter 2 Managing Plan Files... 3 Viewing a list of plans you have created... 3 Editing, copying, and deleting a plan... 3 Sample plans... 3 Searching for plans... 4 Uploading plans... 4 Upgrading plans... 4 Chapter 3 Creating a New Plan... 5 Selecting offerings... 5 Defining machines... 5 Distributing components... 7 Machines - Tree view... 8 Machines - Flat view Business rules for certain components Power mode Adding configuration steps Reviewing a plan Printing a plan Saving and sending a plan attachments Validating a plan Chapter 4 Advanced topics SAS Environment Manager and SAS Web Server SAS Visual Analytics and SAS Workspace Server on Windows Migrating DataFlux Authentication Server/SAS Authentication Server Restrictions for SAS Risk Management for Banking Planning delayed deployments of SAS Visual Analytics Administration and Reporting Overview Exceptions to the process Creating the plan SAS Visual Analytics and distributed mode Deploying both 32 bit and 64 bit software on the same machine using a plan file Understanding the Platform Computing Suite for SAS components Page i 12 October 2017

4 Distributing SAS middle-tier components across multiple machines Deploying the metadata server and middle tier on the same machine When to include SAS DATA Step Batch Server in your plan ii

5 Chapter 1 Getting Started What is a plan file? The plan file is an XML-based description of the customer's topology for their SAS system. Similar to an architect's floor plan, the plan file describes the intended final SAS software environment. The plan file contains SAS software as well as third-party software, such as the web application server (prior to SAS 9.3). You must specify the web application server your customer intends to use, even if it's already installed, because the SAS Deployment Wizard configures and deploys the SAS software with options specific to each web server. To learn more about the various SAS components displayed in the Planning Application, go to Install Center (located at and search for the component's name. How is the plan file used in the software deployment process? The plan file is used in the SAS software deployment process to "tell" the SAS Deployment Wizard which software components to install and configure on each machine. You can use one of the standard plans included in the SAS Deployment Wizard, or use a custom plan file you created with the SAS Planning Application. The plan file includes the prerequisite software for each machine in the plan. You must install the prerequisite software before you start deploying the SAS software. The SAS Deployment Wizard prompts for the installation location of all the prerequisites in the plan. For ease of use at deployment time, it is recommended that you list the machines in the plan file in the same order that you will deploy them. The recommended order is: 1. Metadata Server 2. SAS Application Server(s) 3. Remote Services (SAS Foundation Services) Note: Remote Services is no longer a machine purpose after SAS Middle Tier with SAS Web Infrastructure Platform 5. Middle Tier with other web applications (SAS BI Dashboard, SAS Information Delivery Portal, SAS Web Report Studio, etc.) 6. Clients Who uses the planning application? The planning application is used by SAS sales engineers, SAS consultants and approved SAS Partner Program Members. Customers do not use the planning application at this time. Approved users who don't have a SAS address must be added to the database to be able to log in to the application. Send an to planappsupport@sas.com to request that a non-sas user be added to the database. It is up to you to decide when you create your plan, as long as it is done before you begin your SAS software deployment. The recommendation is to create your plan as early as possible so that you can Page 1

6 clarify all technical details with the customer using the printable plan diagrams and the custom preinstallation checklist. For best performance, we recommend that you use a recent version of Internet Explorer 7 or Firefox. Internal SAS users can download these browsers from the following locations: The recommended minimum CPU requirements are: Processor: 2.0GHz or higher Memory: 2GB RAM or higher 2

7 Chapter 2 Managing Plan Files Viewing a list of plans you have created After you log in, the first page of the application is the Select Plans - My Plans tab. This is a table of all the plans you have saved. You can sort the table in various ways by clicking on the headers. Click on the header again to switch between ascending and descending order. To start creating a new plan from scratch, click New Plan in the toolbar. See also Editing, copying, and deleting a plan on page 3 Editing, copying, and deleting a plan To edit, copy or delete a plan, click within the corresponding row in the table. The plan displays in a pop-up window, and the edit, copy and delete links are available at the top and bottom of the pop-up window. You can make a copy of any plan in the system. However, you cannot edit or delete a plan that was created by someone else. See also Sample plans Viewing a list of plans you have created on page 3 Sample plans on page 3 Searching for plans on page 4 Sample plans are listed on the Select Plan - Samples tab. Sample plans are provided as a starting point for some of the more complicated deployment scenarios. You can sort the sample plans in various ways by clicking on the headers. Click on the header again to switch between ascending and descending order. To make a copy of a sample plan, click within the row and a dialog box displays. The option to copy the plan is available at the top and bottom of the dialog box. If you would like to request that a particular sample plan be added to the system, send an to planappsupport@sas.com. See also Editing, copying, and deleting a plan on page 3 Page 3

8 Searching for plans Search is available from the Select Plan - Search tab. Search all the plans in the system by filling in one or more of the following fields: address, customer name, order number, description. You can sort the search results table in various ways by clicking on the headers. Click on the header again to switch between ascending and descending order. To preview a plan you have found, click within the row and a dialog box displays. The option to copy the plan is available at the top and bottom of the dialog box. See also Uploading plans Editing, copying, and deleting a plan on page 3 The upload option is available on the Select Plan - Upload tab. Browse to the plan.xml file location or type in the path, and then click Upload Plan. The plan is displayed. You can then create a copy of this plan or cancel the upload process altogether. Uploads are supported for plans for SAS 9.2 and newer versions of SAS. Upgrading plans To upgrade a plan to a later SAS version or As-of date, first load it into the planning application (by plan edit, copy, or upload as described above), then go to the Select Offerings tab and adjust the SAS Version and As-of date as needed. Because changes take place between versions of SAS and between ship events, you may see a pop-up message that confirms the requested date change. This message is just a reminder that all of the content in your plan file will be updated to the same as of date. This may imply that new components have been added to the offerings in your plan in a subsequent ship event, and that your updated plan file must include these new components. New components will not necessarily be placed automatically. These can be addressed by selecting the Recommended option on the Distribute Components tab or by manually moving products to the appropriate machines on the same tab. 4

9 Chapter 3 Creating a New Plan Selecting offerings To start creating a new plan from scratch, click New Plan located under the Select Plan tab. The fields at the top of this page are optional. If you provide a valid order number and either a valid Tech Support Site Number or Site ID, the customer name is prefilled and the "as of" date is set per the order information. The order number and Tech Support Site Number are both available in your software order and Software Order Information document. The Site ID is being retained for legacy purposes and should only be used by those already familiar with it. Tip: If you select a previously created plan file and then change its as of date, you may see a pop-up message that confirms the requested date change. This message is just a reminder that all of the content in your plan file will be updated to the same as of date. This may imply that new components have been added to the offerings in your plan in a subsequent ship event, and that your updated plan file must include these new components. You must select one or more offerings to include in the plan, and the offerings you choose must match what the customer is ordering. Include the Standalone SAS Metadata Server offering in your plan if you are deploying the metadata server on a separate machine. The following "pseudo-offerings" are available to help you create complex plan files. They are pseudo-offerings because they do not correspond to an actual orderable offering. You must be certain that the customer's order contains the required license for the components you include in the plan file. Choose the SAS Servers and Spawners offering if you want to easily create additional SAS Application Server machines. You must manually drag and drop the desired server configurations onto each additional server machine. Choose the Select Individual Products offering if you want to include typical "add-on" products in your plan, such as SAS/ACCESS products and MVA products. To preview the contents of the offering, click on the offering name. Defining machines Your plan file must contain all the machines that will appear in the SAS software topology. You do not have to include multiple copies of the same machine in the plan, such as an end user client machine. Include one representative machine that contains the desired software components, and at deployment time this template will be reused multiple times for each installation. When defining a machine, the only required fields are Machine Name and Operating System. Machine Name does not have to be the actual name of the machine; instead, it can be a generic name like "Middle Tier". The additional data fields are optional, but they are useful in communicating the SAS environment details with your customer. Page 5

10 Another optional (yet very useful) set of fields is the selection of Machine Purposes. These fields indicate the intended roles the machine will play within the SAS environment. The planning application uses these values to intelligently place the software required by that role on each machine. Furthermore, the different roles limit or expand the specification fields displayed (for example, the fewest specification details are required by client-only machines). Note: Best practice calls for manually defined machines to have the Clients Administrative machine purpose included on them. Manually defined machines are those that are not created and populated automatically by the planning application. The planning application defaults to a standard three machine topology when creating a new plan. You can switch to a one, two, or four machine topology. You can change the options on the standard machines at any time. The icon signifies a standard machine. Beginning with SAS 9.4 if your deployment includes SAS Metadata Server, a metadata server node machine is added by default to your topology. Similarly, if you have software designated for the middle tier, a middle tier node machine will be added to your topology. These two additional machines can be used for clustering and are automatically generated with their required software. They are identified as optional in the plan unless you specifically make them required on this tab. Note: The optional machines are being included by default with every plan that can use them in order to let the user know that clustering is available for SAS 9.4 software. Always including the machines by default also allows the user to add clustered machines after initial deployment of their software without having to create another plan. If you are concerned that seeing the nodes will confuse customers who do not have them initially, you can remove the optional machines in the machine details pane below. You can include as many additional custom machines as you need by clicking Add Machine on the bottom left and specifying the machine name and operating system. The machine. The and icons expand and collapse the machine details. icon signifies a custom For ease of use at deployment time, you should list the machines in the plan file in the same order that you will deploy them. The recommended order is 1. Metadata Server 2. SAS Application Server(s) 6

11 3. Remote Services (SAS Foundation Services) Note: Remote Services is no longer a machine purpose after SAS Middle Tier with SAS Web Infrastructure Platform 5. Middle Tier with other Web applications (SAS BI Dashboard, SAS Information Delivery Portal, SAS Web Report Studio, etc.) 6. Clients The icons to the right of each machine name allow you to change the display order of the machines or remove a machine altogether: Move to top Move up Move down Move to bottom Delete Distributing components To learn more about the various SAS components displayed in the Planning Application, go to the SAS support web site ( and search for the component's name. The Distribute Components tab displays the offerings you have chosen (left side) and the machines you have defined (right side). Use this tab to distribute the offering's included software components across all the machines in the environment. There are two ways to do this: click a button or manually drag and drop components onto a machine. The following buttons allow you to take full advantage of all the business rules and data intelligence built into the application. Selecting Minimum automatically places only the required software components on the machines you have defined. Selecting Recommended automatically places all the required and recommended software components on the machines you have defined. Selecting Maximum places all the required, recommended and optional software components on the machines you have defined. You can also drag and drop components between the Available Software and Machines panes. As you start dragging, the background color changes to light green to indicate valid drop locations. When your cursor approaches a valid drop "zone", the background color changes to a darker green. If the background color does not change, the product cannot be placed in the drop location you have selected, either because business rules do not allow it or because the product is already there. If you try to drop the product in that location, you will receive a warning message explaining why the product has not been placed. 7

12 Regardless of the method you use to place software components on a machine, certain components allow for additional input from you. In the Available Software pane, these components display with a icon and are automatically expanded to display the component that you may choose to include on that machine. The icon indicates that the planning application has selected the default option. When a different choice is made, the question mark will no longer display. If you are content with the default choice, click on the question mark icon to remove it. Required component, can only be installed once Required component, may be installed multiple times Required component, already placed on a machine Required component, additional input may be needed Optional component, can only be installed once Optional component, may be installed multiple times Recommended optional component Optional component, already placed on a machine Additional input may be needed If you click on a product name in the Available Software pane, a window opens that describes the product, whether or not it is required, how many times it can be installed in a deployment, and the hosts on which it is available. If you select the Clear all button above the Machines pane, the software on the machines will return to its original state, that is, to when no software has been assigned to a machine yet. Machines - Tree view The tree view of the Machines pane shows the components on the individual machines in the plan in a hierarchical view. When fully expanded, the tree view shows every reason for every product in the plan. The background color of a component is a quick indicator of its mobility and required status. Background color blue yellow white gray Description component is required in the plan and can be moved from machine to machine component is optional for the plan and can be moved from machine to machine component is required and must be on the machine it is on because of business rules a decision to include the component is available to the user rather than forced by business rules Gray components have check boxes to identify if that component should be included. Selecting the check box includes that component in the plan. If the check box is present and selected and cannot be 8

13 cleared, the component in question has been placed by at least two different reasons, one of which allows a choice and another which does not because of business rules. A component name is bolded when at least one component in that component s expansion can have an action performed on it either a component under it can be moved (blue or yellow) or a decision about its inclusion must be made (gray). A component may appear more than once per machine because it has more than one reason to be included on that machine. If you click on a component name in the tree view, a window opens, similar to the window in the Available Software pane, with information about the component: a description the required status of the component (required or optional) how many times the component can be installed in a deployment the hosts on which the component is available the reason or reasons why the component has been included. For example, if you click on SAS DATA Step Batch Server 9.4, the window might include this information: Required by SAS Visual Analytics Administrator 6.2 on Middle Tier - Microsoft Windows for x64 (WX6) This indicates that SAS Visual Analytics Administrator 6.2 on the middle-tier machine, running on Microsoft Windows for x64 (WX6) requires SAS DATA Step Batch Server 9.4 to be included. Expand a component in the tree view in order to see other components that are included because of a relationship with the component being expanded. Verbs in curly brackets at the beginning of a component name describe the relationship of that component to the component above it in the hierarchy. Look at the following figure as an example. 9

14 In this example, SAS DATA Step Batch Server 9.4 has been expanded to show its dependent components: SAS DATA Step Batch Server 9.4 needs SAS Application Server Context 9.4 in order to be installed. SAS Application Server Context 9.4 contains SAS Deployment Agent 9.4, which in turn requires SAS Remote Deployment Agent Client SAS DATA Step Batch Server 9.4 also requires SAS Intelligence Platform Object Framework 9.4, which in turn requires Java Platform Standard Edition Runtime Environment JAVA 7. When you move a component in the tree view, all of its dependencies go with it. The Planning Application will place the dependent components on the machines where they need to go based on the business rules for the component. Clicking Clear beside the machine name will return the software on that machine to its original state, that is, with no components on that machine at all. Machines - Flat view The flat view of the Machines pane shows a list of the components on each machine so that each component name appears only once on the machine. The flat view is useful for finding an individual component without having to expand all the components available in the tree view. The background color of the components and their reasons for inclusion in the flat view means something slightly different than it does in the tree view. 10

15 Background color white blue yellow Component Description component has at least one nonmovable reason component s reasons are all movable, and the component has at least one required reason component s reasons are all movable, and the component has no required reason Reason Description reason is required and must be on the machine it is on because of business rules reason is required in the plan and can be moved from machine to machine reason is optional for the plan and can be moved from machine to machine White components may include a checkbox, giving the user the option to include the component. If the check box is selected, the component is included in the plan as non-movable with non-movable reasons. When you move a movable component from machine to machine, all of its reasons will follow it. You can also expand a component and drag its movable reasons independently. Note that some nonmovable components have both movable and non-movable reasons. If you drag a movable reason from a non-movable component, when you place that reason, the component associated with it will become movable. If you click a component name in the flat view, a window opens with information about that component: the component name and a parenthetical requirement that it be installed only once per plan, if applicable where the component is currently located in the plan whether the component is installed, configured, or both based on the deployment the hosts on which the component can be used upward relationships, or the reasons why the component is included in the plan downward relationships, or the components included in the plan because of the component you clicked on When you expand a component, the reason or reasons for that component being included are listed beneath it. Clicking Clear beside the machine name will return the software on that machine to its original state, that is, with no components on that machine at all. Business rules for certain components The product data within the application contains a number of business rules that ensure you create valid plans. For example, you can see a business rule in action when you attempt to place a software component on a machine on an unsupported platform. The application prevents you from placing the component on the machine and a message displays informing you as to why this isn't allowed. 11

16 Another way to see the business rules in action is to expand the Machines tree control on the Distribute Components tab after placing software components on a machine. These multilevel data dependencies are hidden by default there is no need for you to worry about them but they are viewable if you want to know what's happening "under the covers". Types of business rules: Dependencies - relationships between software components, both SAS software and thirdparty software (such as Java clients require the JRE on the same machine, or SAS Management Console plug-ins require SAS Management Console on the same machine) Compatibility - you cannot place a software component on an unsupported platform Installation count - if the SAS license allows a limited number of installs then the business rule applies (such as, you can have only one Metadata Server in a plan) Installation order - software components in the plan file are sorted in the correct order for installation and configuration A note about compatibility: If you see an error message about incompatibility, be aware that the incompatibility may only apply to the particular SAS business rules that aid in creating valid plan files. For example, you cannot place two different web application servers in your plan file, and if you try to do so you will see an error about incompatibility. In "the real world", you certainly could install two different web application servers on a machine. Power mode The application contains numerous business rules to ensure that a valid plan file is created every time. However, there may be a situation that requires you to create a plan file without the aid of these business rules. You can do this with power mode. Power mode removes the application's enforcement of installation count restrictions and known compatibilities. However, any product prerequisites or same-machine business rules (such as, a Java client requires JRE on the same machine or a SAS Management Console plug-in requires SAS Management Console on the same machine) cannot be overridden. To use power mode, click Swap into Power Mode located at the bottom of the Distribute Components tab. After a warning message opens, click OK to continue. You can continue using the application as you would normally. Exit power mode by clicking Swap out of Power Mode. Adding configuration steps If you are creating a plan for SAS 9.4 or later, after you have distributed the components, you can use the Configuration Steps tab to create one or more additional configuration steps on any machine with configuration. The primary intent for configuration steps is to support the creation of additional server contexts (past what the planning application automatically does based on the planned content). There are cases where customers want additional server contexts, and previously those had to be manually managed with each additional run of the SAS Deployment Wizard. Now the plan creator can define the contents for each desired server context on the Configuration Steps tab, which means that the person running the SAS Deployment Wizard simply selects a deployment step the manual selection of configured products is no longer necessary since that information is placed in the plan file itself. 12

17 The user should define a label for the added step (which will be shown in the SAS Deployment Wizard), adjust the step order, select the content to be configured, and delete steps. The Planning Application will add these user-defined steps into the plan, placing them after the last programmatically determined step for each machine. Opening the Configuration Steps tab displays a list of the machines that have been defined and have had their components distributed on them. Click Add new step for the machine to which you want to give additional configuration steps. In the Step label field, you should give the step a meaningful name. The list below the Step label consists of the configurable software on that machine. Select the products you want to configure in this new step. You can also use Select all to choose each of the products or Clear all to remove checks from each product. You can also to delete the entire step. When you have finished your selections, click Done to return to the list of machines with configurable software. Repeat the step creation process as often as needed. At the machine list page, you can use the icons described on page 6 to change the order of the steps that have been created, including deleting them. You can also use Edit to open a configuration step and make changes to it. Reviewing a plan The Review Plan tab allows you to see your plan contents in a graphical or text view. The Diagram - Details and Text - Details views display all the components that will be installed and configured on each machine. This view is intended for the person installing the SAS software as well as your customer's IT department. These plan file consumers want to know exactly which SAS software components are installed on each machine. The Diagram - Summary and Text - Summary views display only the software grouping names. This view may be useful for your customer's CIO and business analysts who may not need to understand the nitty-gritty details of the SAS environment. The Deployment Steps view displays the lists of software to be installed and software to be configured for each machine. The following icons are used in the diagrams: Indicates that the machine contains server components. The machine may also contain middle-tier and client components. If you did not use the Software to Install/Configure feature available on the Define Machines tab, then this icon displays by default. Indicates that the machine contains middle-tier components. The machine may also contain client components. Indicates that the machine contains only client components. You can also review the required/optional status of each machine in the plan by clicking Required/Optional Machines in the top right corner of each view. If you choose this option, a Required machines window opens, listing each machine in your plan in one of as many as three categories: machines that are required because they have software that is necessary for the successful deployment of the plan 13

18 machines that are optional because they do not have necessary software machines that are required because the creator of the plan has changed the status from optional to required Any machine listed in the second or third category will also have a button beside its name. If you click that button, that machine will toggle between the second and third categories. Machines in the first category cannot have their required/optional status changed by this dialog. In order to change the status of those machines, you need to return to the Distribute Components tab and remove any required software from them. When you have finished using this dialog, click Close to continue. See also Printing a plan on page 14 Printing a plan You can print a plan by clicking Printable View located at the bottom of each Review Plan tab. This will launch a separate browser window. You may need to set your browser's option to print the background colors, change font size, change page orientation, etc. In the Printable View browser window, Hide Blank Fields suppresses printing of the empty fields in your plan. Show Blank Fields enables printing of the empty fields. You can also print the.htm (Internet Explorer compatible) or.mht (Firefox compatible) attachments. See also Reviewing a plan on page 13 Saving and sending a plan The final step is to save and send your plan file and other attachments via so that you can use them on site when you deploy the customer's SAS software. The Configuration Directory Name is the location in which the SAS Deployment Wizard will install all required start up scripts, configuration options, etc. for the SAS environment. The default name is "Config", so you may wish to change it to something like "EBIserver" or "DIserver" to match your customer's deployment. Plan Name and Plan Description are optional. This plan is a template plan to the following addresses Include STIC variable dictionary spreadsheet Zip the plan delivery files into a single attachment Saves the plan in the system only. If you have a set of plan preferences, machine names, etc. that you like to reuse, you can save a plan as a template for easy access. Prefills with your address, but you can add more. This file is used by the Global STIC Documentation Builder (available to internal SAS users only). All attachments are saved in a single.zip file. Required if you use Outlook Web Access to receive your plan file (XML files are blocked for security purposes). 14

19 Display plan.xml in browser Plan.xml file code displays in a browser window immediately. Note: If you copy and paste the contents of the plan.xml dialog box into a flat file, you must save it using UTF-8 encoding. Failure to do so results in an ISO (Latin-1) encoded file, which the SAS Deployment Wizard may have problems reading. See also attachments on page 15 attachments A number of attachments are included along with the plan.xml file. The stic_var_dictionary.xls and stic_best_practices.html are only included if you choose that option at the Planning Application. checklist.pdf checklist.rtf details_diagram_for_ie7.mht details_diagram.html index.html plan.xml summary_diagram_for_ie7.mht summary_diagram.html deploymentsteps_text.htm InstallationConfigurationDictionary.xlsx stic_best_practices.html Pre-installation checklist in Portable Document Format Pre-installation checklist in Rich Text Format Diagram - Details view of plan file, optimized for Internet Explorer 7 and earlier Diagram - Details view of plan file, optimized for Internet Explorer 8 and later and Firefox Introductory text with links to helpful documentation Plan file that is used by the SAS Deployment Wizard to deploy SAS software Diagram - Summary view of plan file, optimized for Internet Explorer 7 and earlier Diagram - Summary view of plan file, optimized for Internet Explorer 8 and later and Firefox Deployment steps for the plan file Variable dictionary used by the Global STIC Documentation Builder (internal SAS users only) Introductory text for the variable dictionary with links to helpful documentation See also Saving and sending a plan on page 14 15

20 Validating a plan The application continually keeps track of the validity of the plan. The validity status displays in the top right menu area underneath the SAS logo. Displays if the plan is not yet valid. You can click on the "Plan is not valid yet" button to see the reason why the plan isn't valid. Displays if the plan is valid. 16

21 Chapter 4 Advanced topics SAS Environment Manager and SAS Web Server In a deployment where SAS Environment Manager is co-located with a standalone SAS Web Server, the Planning Application will identify a deployment plan as valid, however failures will occur during configuration. Therefore SAS Environment Manager should not be placed on a web server-only tier. SAS Visual Analytics and SAS Workspace Server on Windows When you deploy SAS Visual Analytics or SAS Visual Analytics Administration and Reporting with a solution on a Windows machine with SAS Workspace Server, but put the SAS LASR Analytic Server on a different Windows machine, errors might occur. You might see error messages similar to the ones below when loading data to a SAS LASR Analytic Server machine: ERROR: The LASR Analytic Server on 'host name', port is running on a host platform that is not supported by your SAS client platform. ERROR: Libref VALIBLA is not assigned. ERROR: Error in the LIBNAME statement. This problem does not occur if the SAS LASR Analytic Server is a Linux machine. Take this error condition into account as you create plans with these products on Windows machines. For more information, see Migrating DataFlux Authentication Server/SAS Authentication Server In order to successfully migrate DataFlux Authentication Server content, the target machine must have both DataFlux Authentication Server and Base SAS installed on it. Therefore, if you create a deployment plan for a machine on which you intend to place the DataFlux Authentication Server, ensure that both products are included on the machine in the plan. (To include Base SAS, on the Select Offerings tab, select Select Individual Products, and then on the Distribute Components tab, drag Base SAS from the left pane to the appropriate machine in the right pane.) Restrictions for SAS Risk Management for Banking 3.3 For SAS Risk Management for Banking 3.3, the SAS Risk Management Banking LASR Configuration must be on the same machine as the SAS Visual Analytics LASR Server. Planning delayed deployments of SAS Visual Analytics Administration and Reporting Overview Following the second maintenance release of SAS 9.4, many offerings are packaged with SAS Visual Analytics Administration and Reporting included. SAS Visual Analytics Administration and Reporting works with the LASR analytic servers associated with the offerings to provide a highly visual interface backed by a high-speed analytics platform. However, with a few exceptions noted below, SAS Visual Analytics Administration and Reporting is not a requirement to deploy and use those offerings, so they can be deployed without having access to a LASR analytic server and its highspeed analytics. Page 17

22 There are two primary reasons why a customer may not want to deploy SAS Visual Analytics Administration and Reporting with the initial deployment of an offering. First, the customer may not have a desire or need for the enhanced analytics associated with SAS Visual Analytics Administration and Reporting at the initial deployment. Second, since SAS Visual Analytics Administration and Reporting is available only on 64-bit Linux and Microsoft Windows for x64, the customer may not have the necessary hardware available to deploy it. In either case, except for the offerings noted below, the customer can choose to delay the deployment of SAS Visual Analytics Administration and Reporting for some time after deploying the offering. Exceptions to the process A delayed deployment of SAS Visual Analytics Administration and Reporting should not be planned or performed for the following offerings. These offerings have a technical dependency on SAS Visual Analytics Administration and Reporting, such that not deploying it will cause the offering to not be usable at all. SAS Asset and Liability Management for Banking SAS Capital Planning and Management SAS Credit Assessment Manager SAS Credit Risk for Banking SAS Customer Experience Analytics SAS Financial Management SAS Firmwide Risk for Banking SAS Governance and Compliance Manager SAS Insurance Analytics Architecture SAS Market Risk for Banking SAS Model Implementation Platform SAS Model Risk Management SAS Qualitative Assessment Manager SAS Risk and Finance Workbench SAS Risk Governance Framework SAS Risk Management for Banking SAS Visual Scenario Designer Creating the plan If the offering that you are deploying is not listed in the section above, use the following steps in order to create a plan file for deployments of an offering that include SAS Visual Analytics Administration and Reporting but may delay deploying it. 1. At the Select Offerings tab, if you are working with an existing order, be sure to enter the order number so that the correct software will be included in the plan. 2. Select the offering that you are going to deploy. Note that offering inclusions are automatic. When you select offerings that include SAS Visual Analytics Administration and Reporting, you cannot remove the SAS Visual Analytics Administration and Reporting offering from the plan. 3. On the Define Machines tab, ensure that the SAS Visual Analytics Application Server, SAS Visual Analytics Middle Tier, and Solution LASR Analytic Server purposes are on their own machines or combination of machines. No other purposes should be included on a machine 18

23 that has at least one of those three purposes except for Clients Administrative, which should be included on each machine with any of those purposes. If you are not sure what the topology of the SAS Visual Analytics Administration and Reporting pieces will be when you eventually deploy them, you should consider moving the SAS Visual Analytics Application Server, SAS Visual Analytics Middle Tier, and Solution LASR Analytic Server purposes to a single machine that you can name Delayed VAAR machine. 4. On the Distribute Components tab, distribute the components as you normally would, including the pieces associated with SAS Visual Analytics Administration and Reporting. Do not attempt to remove individual products for SAS Visual Analytics Administration and Reporting, because you might remove pieces that will be needed later. Note: Some SAS Visual Analytics and LASR products will be distributed to the machines that are not going to be delayed, such as the same tier as the Web Infrastructure Platform. This distribution is expected and appropriate. These products will not interfere with anything and are there to ensure that if the SAS Visual Analytics and LASR machines are deployed, the original machines in the deployment have the necessary product set. Do not remove or attempt to move these products. 5. If you decide to delay deployment of SAS Visual Analytics, when you deploy the software using the plan that you ve created, follow the steps in the deployment_steps_text.html, but skip the steps that instruct you to run the SAS Deployment Wizard on the Delayed VAAR Machine. Do not deploy the machines that have any of the three purposes listed in Step 3. This will result in a deployment that includes the offering but none of the SAS Visual Analytics or LASR machines. 6. If you created a plan with a Delayed VAAR machine described in step 3, then, later, if the customer does NOT want to deploy all the remaining SAS Visual Analytics pieces to a single machine, you will have to create a new plan to distribute those purposes and the associated software to the intended deployment topology. If you do create a new plan, be sure to begin by uploading the plan you originally created so that all the pieces will be on the right machines. If the original plan has any pieces that were put in place by moving them manually ( drag and drop ) on the Distribute Components tab, in order to create the updated plan you must first create the new machines and set their purposes on the Define Machines tab. After the machines are created, on the Distribute Components tab, move the SAS Visual Analytics Analytic and Reporting pieces to the new machines manually. If you are sure that the original plan was created by only using the Recommended button on the Distribute Components tab without moving any pieces manually, create the new machines and assign their purposes on the Define Machines tab. Then on the Distribute Components tab, first click Clear for the Delayed VAAR Machine, and then click Recommended to move the SAS Visual Analytics pieces to their new machines. If you are unsure if the original plan was created without moving any of the software on any machine manually, do not use the Recommended button to place the SAS Visual Analytics pieces. After moving the SAS Visual Analytics and Solution LASR Analytics pieces to their new machines, delete the Delayed VAAR Machine. 19

24 For more information about performing the delayed deployment of the SAS Visual Analytics Administration and Reporting and LASR pieces, see SAS Visual Analytics Administration and Reporting: Delayed Deployments Installation Guide, located at default/install.pdf. SAS Visual Analytics and distributed mode Beginning with ship event 14w19, the planning application recognizes that SAS Visual Analytics (or SAS Visual Analytics Administration and Reporting) can be used in non-distributed mode or distributed mode. Non-distributed mode puts the LASR Analytic Server on a server machine. Distributed mode describes a deployment that distributes the work of the LASR Analytic Server across several machines. Note that the use of these modes also applies to offerings that include SAS Visual Analytics, such as SAS High-Performance Anti-Money Laundering. The planning application and its associated documentation cannot distinguish between distributed and non-distributed modes automatically. It can, however, identify when the distributed mode is possible and include information about using it if the deployment calls for it. The planning application accommodates distributed mode in the following ways: The addition of SAS Visual Analytics Server and SAS Visual Analytics Middle Tier to the list of machine purposes on the Define Machines tab. When a machine with the SAS Visual Analytics Server or SAS Visual Analytics Middle Tier purpose is included in a plan, the pre-installation checklist will point to a new document, SAS Visual Analytics: Distributed Environment Deployment Prerequisites. This document is an addendum to the pre-installation checklist applying only to the nodes required for distributed mode. Deploying both 32 bit and 64 bit software on the same machine using a plan file You can deploy both 32 bit and 64 bit SAS software on the same machine using a plan file. However, you must run the SAS Deployment Wizard twice on the machine and you must create separate configuration directories. On the Define Machines tab, create one machine for your 32 bit SAS software and another machine for the 64 bit software. These two logical machines represent a single physical machine. At deployment time, you will run the SAS Deployment Wizard twice on a single physical machine, choosing the appropriate SAS license and matching logical machine each time. You will need to create separate configuration directories for each run of the SAS Deployment Wizard. Understanding the Platform Computing Suite for SAS components If you intend to use the scheduling functionality of Platform Computing Suite for SAS, then you must include Platform Process Manager in your plan file. The Platform LSF component is only required on Grid Node and Grid Client machines (part of Grid Manager offering). Platform Grid Management Service component is only required on Grid Control Server machines (part of Grid Manager offering). 20

25 Distributing SAS middle-tier components across multiple machines The easiest way to create a plan with multiple middle-tier machines is to place copies of the "Middle Tier" group on each machine. Then selectively remove the individual components that you do not want to deploy on the machine. Note that the SAS web applications must have a web application server specified on the machine. You can distribute the various web applications and services across multiple machines. The following is only one example: Middle Tier Machine1 SAS Web Infrastructure Platform Web application server Middle Tier Machine2 SAS BI Dashboard SAS Information Delivery Portal SAS Shared Services SAS Web OLAP Viewer SAS Web Report Studio Web application server Deploying the metadata server and middle tier on the same machine For deployments that include more than one machine, if you want to deploy the metadata server and middle tier on the same machine, you must put them on two separate machines in your plan file (one for metadata server, the other for the middle tier). At one time, best practices allowed the metadata server and middle tier to be in the same configuration directory on the same machine, while the compute tier was on a different machine. However, SAS determined that deploying the middle tier requires that the SAS Application Server already be deployed. Therefore, in this scenario, the metadata server and the middle tier should be split into separate deployment steps and deployed in distinct configuration directories. First deploy the metadata server machine, then deploy the SAS Application Server, and then go back to the first machine to configure the middle tier into a directory other than the one used for the metadata server. The Planning Application will accurately describe the steps to deploy in the order they should be performed. When to include SAS DATA Step Batch Server in your plan If you wish to schedule any SAS Foundation programs, then you should include SAS DATA Step Batch Server in your deployment. For more information about scheduling see the "Scheduling for SAS" documentation, available at from the appropriate version-specific tab at SAS (Enterprise) Data Integration Server deployments which schedule jobs (either via Platform Computing software or Operating System Services Scheduling Server) require SAS DATA Step Batch Server on the SAS Application Server machine. A SAS DATA Step Batch Server is automatically configured by the SAS Deployment Wizard on the same machine as the SAS Metadata Server, regardless of plan file contents for that machine. 21