1816/2020 Configuration Guidelines and Details Configuration Guidelines and Details for "desktop-10" 9, Operating System Services Scheduling Server 10. SAS Visual Analytics 42, SAS Web Infrastructure Platform Scheduling Services 28, Obtaining Additional Information Warnings and Notices The following issues occurred during the automated portion of your configuration and must be addressed before proceeding. ‘+ Some of the clients in your environment may need access to the SAS/GRAPH Java applets to view graphical output generated by SAS processes. If so, add the APPLETLOC option to the sasv9_usermods.cig file located in each SAS Application Server context directory specifying the location to be used in generating graphical output. APPLETLOC should point to a network accessible copy of the SAS/GRAPH Java applets. Since your deployment includes the SAS Web Infrastructure Platform, the applets can be made available via: -APPLETLOC="ht tp://web-server:port/sasweb/graph™ The web server portis typically 80 on Windows deployments and 7980 on other deployments. Deployments that do not use a web server can point directly to the SAS Web Application Server, which typically uses port 8080. NOTE: Do not add this line to the sasv9_usermods.efg file until the SAS middle lier is configured. After updating the file, restart the object spawner and validate your Workspace, Pooled Workspace, and the Stored Process servers again, + You indicated that security policies could be modified by the SAS Deployment Wizard, As a result, the user DESKTOP- 10\sasdemo was granted the local security policy Log on as a batch job (SeBatchLogonRight). This policy allows a {le:13C:/SASIConfighLev3:Documents/instructons.himl 4311516/2020 Configuration Guidelines and Details User to be logged on by means of a batch-queue facility and is required when this account is used with SASApp - Workspace Server. The policy will take effect the next time DESKTOP-10\sasdemo authenticates against the operating system. Therefore, if DESKTOP-10\sasdemo is currently logged on to the system, a reboot will be needed for this policy to take effect. + SAS Web Applications are being protected by a security iter that prevents linking from unauthorized hosts. The security iter is customizable. For further information on customizing this fier, refer to the SAS 9.4 Intelligence Platform: Middle-Tier Administration Guide, found at |http:/support sas com/documentation/onlinedoc/inteliplatformlindex html + The following SAS Environment Manager Agents need to be manually restarted. ‘© The SAS Deployment Agent is not running on the host desktop-10, Use the following command to restart the SAS Environment Manager Agent on this host: :\SAS\ConFig\Lev3\Web\SASEnvironmentHanager\agent-5.8.0-EE\bin\hq-agent.bat restart SAS Management Console SAS Management Console is required to complete many of the following steps, Shortcut Programs > SAS > SAS Management Console 9.4 UserID SAS Administrator user 1D Password Enter the password you created in the SAS Deployment Wizard, SAS Application Servers SASMeta - Metadata Server Host machine Port 8563 ‘CASAS\Config\Lev3\Logs Log For more details about the inital logging configuration and how to modify it, see "Administering Logging for directory SAS Servers" in the SAS Intoligence Platform: System Administration Guide at hfpu/support sas, com/@4administration, ion Windows service type SAS [Config-Lev3] SASMeta - Metadata Server Shortcuts Programs > SAS > Configuration > Config - Lev3 desktop-10 Exect Notes: + The metadata server is configured to perform unassisted metadata server backups. The backups are performed every day at 1 am. except on Sunday and stored in the "C:\SAS\Config\Lev3\SASMeta\MetadataServeriBackups" directory, Backups are retained for seven days. To lear about the metadata server backup facilty, see "Backing Up and Recovering the SAS Metadata Server" in the SAS Intelligence Platform: System Administration Guide at ‘ntte:/support.sas.com/@4administration. + The metadata server is configured to send an alert e-mail message to rian.magpantay@gmail.com in the event of a system, backup, or recovery failure. You can test that the alert-email notification subsystem is configured propery by ‘opening the Properties sheet for the active metadata server in the SAS Management Console Metadata Manager and sending a test message. If the system is configured properly, you will receive a test e-mail from SASMeta - Metadata Server Config - Lev3 . If you want to change your alert e-mail options, see the section fl: 11C:/SASIConfigiLev3:Documents/instructons.himl 21811516/2020 Configuration Guidelines and Details "Managing Alert E-mail Options for the SAS Metadata Server" in the chapter "Metadata Server Configuration Tasks" of the SAS intelligence Platform: System Administration Guide at htt SASApp - Connect Server Host machine Port 7553 CASAS\Config\Lev3\Logs Log For more details about the intial logging configuration and how to modify it, see "Administering Logging for directory SAS Servers" in the SAS Intelligence Platform: System Administration Guide at httpd/support.sas.com/94administration. desktop-10 In the SAS Management Console, on the Plug-ins tab, select, Expand SASApp. Expand SASApp - Logical Connect Server, Highlight the SASApp - Connect Server. Right mouse click this server and select Validate (you can enter DESKTOP-10\sasdemo or the SAS ‘Spawned Servers account for the user ID), You should see a Validation Successful message. to expand the Server Manager node. Validation steps NOTE: To successfully validate a CONNECT server, the associated spawner must be configured with option Signon Scripts Allowed set to Yes. SASApp - Stored Process Server Host machine desktop-10 Port 8603 Log directory C:\SAS\Config\Lev3\Logs 1. In the SAS Management Console, on the Plug-ins tab, select, node. Validation 2. Expand SASApp. steps 3. Highlight the SASApp - Logical Stored Process Server. 4, Right mouse click this server and select Validate. You should see a Validation Successful message. lo expand the Server Manager SASApp - Workspace Server Host machine Port 8593 CASAS\Config\Leva\Logs Log For more details about the initial logging configuration and how to modify it, see "Administering Logging for directory SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http:support.sas.com/administration, desktop-10 4, In the SAS Management Console, on the Plug-ins tab, select 2, Expand SASApp. 3, Highlight the SASApp - Logical Workspace Server. 4, Right mouse click this server and select Validate (you can enter DESKTOP-10\sasdemo or the SAS ‘Spawned Servers account for the user ID). You should see a Validation Successful message. to expand the Server Manager node. Validation steps {l:11C:/SASIConfighLev3:Documents/instructons hil st1516/2020 Configuration Guidelines and Details Notes: + The CASAS\Config\Lev3\Logs directory is intended to serve as a placeholder for workspace server logs, Workspace server logs may be directed to this directory in the event that your SAS or IT administrator enables logging, The following default attrbutes are associated with the Logs directory: © Universal read, write or execute access is disabled for the directory in order to comply with default installation security requirements ‘© Execution of a workspace server does not populate the Logs directory ‘© The Logs directory serves as a placeholder should you enable logging for workspace servers. Enabling workspace server logging should be carefully considered, due to the proliferation of workspace server logs, as well as the requirement to grant universal write access to the Logs directory, To enable workspace server logging, perform the following steps: ‘© Enable read, write and execute access to the Logs directory ‘© Modify the workspace server logconfig.xml to enable the desired levels of logging © Alternatively, enable the logconfig trace.xmI logging file to capture workspace server diagnostic logging SASApp - Pooled Workspace Server Host machine desktop-10 Port 8703 4, In the SAS Management Console, on the Plug-ins tab, select node. Validation 2. Expand SASApp. steps 3. Highlight the SASApp «Logical Pooled Workspace Server, 4, Right mouse is server and select Validate. You should see a Validation Successful message. 1o expand the Server Manager SASApp - SAS DATA Step Batch Server Host machine desktop-10 CASAS\Config\Lev3iLogs, Log For more details about the inital logging configuration and how to modify it, see "Administering Logging for directory SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http:/support.sas.com/administration Validation 1. Select this link: C:\SAS\Config\Lev3\SASApp\BatchServerisasbatch,bat steps 2 I SAS starts successfully, the DATA step batch server has been validated. SAS Spawners Object Spawner Host maciian desktop-10 Port 8583 CASASIConfig\LevaiLogs Log For more details about the initial logging configuration and how to modify it, see "Administering Logging for diractory SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/administration. {l:f1C:/SASIConfighLev3:Dacuments/instructons.hml 4611516/2020 Execution type Shorteuts Configuration Guidelines and Details Windows service SAS [Config-Lev3] Object Spawner Programs > SAS > Configuration > Config - Lev3 Connect Spawner Host machine Port Log directory Execution type Shortcuts desktop-10 7543 CASAS\Confg\Leva\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS intelligence Platform: System Administration Guide at hitp:/support.sas.com/94administration Windows service SAS [Config-Lev3] Connect Spawner Programs > SAS > Configuration > Config - Lev3 SAS/SHARE Server Host machine Port Log directory Execution type Shortcuts desktop-10 8553 ‘CASAS\ConfiglLevaiLogs For more details about the intial logging configuration and how to modify it, see "Administering Logging for SAS Servers' in the SAS intelligence Platform: System Administration Guide at hitp//support sas com/94administration Windows service SAS [Config-Lev3] Share Server Programs > SAS > Configuration > Config - Lev3 SAS Web Infrastructure Platform Data Server Host machine Port Log directory Execution type desktop-10 9434 CASAS\Config\Levailogs For more details about the inital logging configuration and how to modify it, soe "SAS Web Infrastructure Platform Data Server" in the SAS intelligence Platform: Middle-Tier Administration Guide at htpl/support sas com/S4administration Windows service SAS [Config-Lev3] Web Infrastructure Platform Data Server Solution Data Servers SAS Decision Manager Common Data Server {l:11C:/SASIConfighLev3:Documents/instructons.himl 51311516/2020 Configuration Guidelines and Details Host desktop-10 machine Port 10484 CASAS\Config\LevaiLogs Log For more details about the initial logging configuration and how to modify it, see "SAS Web Infrastructure directory Platform Data Server" in the SAS Intelligence Platform: Middle-Tier Administration Guide at hhttp:/support.sas.com/@4administration Execution Windows Service Type SAS [Config-Lev3] Decision Manager Com Data Svr Cfg SAS Risk Common Data Server Configuration Host machine Port 10504 ‘CASAS\Config\Lev3iLogs For more details about configuration, see "SAS Web Infrastructure Platform Data Server’ in the SAS Intelligence Platform: System Administration Guide at hip:/isupport,sas.com/94administration, desktop-10 Log directory Execution Windows service type SAS [Config-Lev3] SAS Risk Common Data Server SAS Risk Governance Framework Data Server Database type Host machine Port 10524 CASASIConfiglLevaiLogs Log To administer logging, edit fle directory _C:\SAS\Config\Lev3iRiskGovernanceFrameworkDataServeridatalpostgresql.conf. For more information about SAS Risk Governance Framework Data Server desktop-10 Execution Windows service type SAS [Config-Lev3] Risk Gov Frwk Data Server SAS Deployment Tester Server H machi © dosktop-10 Port 10023 Execution Windows service type SAS [Config-Lev3] Deployment Tester Server Shortcuts Programs > SAS > Configuration > Config - Lev3 Validation steps _1. In SAS Management Console, on the Plug-ins tab, select "+" to expand the Application Management node. 2. Select "+" to expand Deployment Tester 3, Highlight the host machine: desktop-10 {l:11C:/SASIConfighLev3:Documents/nstructons.himl 61311516/2020 Configuration Guidelines and Details 4, Right mouse click and select Run All Test Suites. 5, Select "#" to expand the Results. 6. Validate the results for each test suite. All tests should pass. If you are prompted for credentials, select the "Help" button in the Credentials dialog box to display the accounts that can be used for each test suite. Notes: + Deployment Tester Server is used to run tests on SAS products and servers to validate functionality and proper operation. The Deployment Tester Server in conjunction with the Deployment Tester SASMC plug-in allows for tests to be executed on remote systems from a single SASMC instance, + When you are done validating your deployment with SAS Deployment Tester, the Deployment Tester Server can safely be shut down without affecting the rest of your SAS deployment, Deployment Tester Server is a stand-alone server, independent of the rest of SAS, that can be started and used periodically to verify the health of your SAS deployment. You should consider verifying the health of your SAS deployment after initial installation, after applying maintenance and hot fixes, or when you make any other significant changes to the deployment. + More detailed information on validating your SAS deployment with Deployment Tester can be found in the "Using the Deployment Tester" section of the SAS 9.4 Intelligence Platform: System Administration Guide, which is available at hhtto:l/support sas, com/@4administration, Operating System Services Scheduling Server Host machine Port 8453 desktop-10 bog Gy directory CASAS\Config\Lev3iLo 4. In the SAS Management Console, on the Plug-ins tab, select, Validation 2. Highlight Operating System Services - desktop-10. steps 3. Right mouse click this server and select Validate (you can enter DESKTOP-10\sasdemo or the SAS ‘Spawned Servers account for the user ID). You should see a Validation Successful message. to expand the Server Manager node. SAS Visual Analytics SAS Visual Analytics Administration To provide access to SAS Visual Analytics, see the topic "Adding Users" in the SAS Visual Analytics: Administration Guide. For a brief validation sequence, see "Validate Your SAS Visual Analytics Deployment” in the SAS Visual Analytics: Installation and Configuration Guide (Non-distributed SAS LASR) ‘Administrative documentation for SAS Visual Analytics is available from hhttp:/support sas com/documentation/onlinedoc/valindex htm! SAS Visual Analytics High-Performance Configurat SAS Visual Analytics Data Provider Non-distributed LASR Autoload To schedule autoloading, run Scheduling "C:\SAS\Config\Lev3\Applications\SASVisualAnalytics\VisualAnalyticsAdministrator\schedule.bat" program, fle: 11C:/SASIConfighLev3:Documents/nstructons.himl 71311516/2020 Configuration Guidelines and Details which will then run periodically every "15" minutes. To unschedule, run *C:\SAS\Config\Lev3\Applications\SAS VisualAnalytics|VisualAnalyticsAdministratoriunschedule. bat" For more details about autoloading, see "Autoload" in the SAS Visual Analytics: Administration Guide at hitto://support sas. com/documentation/onlinedoc/valindex htm! Autoload log C:ASAS\Config\Lev3\Applications\SASVisualAnalytics\VisualAnalyticsAdministratorLogs directory SAS Information Retrieval Studio SAS Information Retrieval Studio for SAS Host machine desktop-10 Server Admin Port 10653 Proxy Server Port 10663 Proxy Server Admin Port 10673 Proxy Server Web Admin Port 10683 Pipeline Server Port 10893 Pipeline Server Admin Port 10703 jpeline Server Web Admin Port 10713 Index Builder Port 10723 Query Server Port 10733 Query Statistics Server Port 10743 Query Statistics Server UDP Port 10743 Crawler Admin Port 10753 Query Web Server Port 10763 Windows service Execution tye sas (Config-Lev3] Information Retrieval Studio SAS Web Infrastructure Platform Scheduling Services Log directory C:\SAS\Config\Lev3\WebiLogs JES Java Batch Server Name Workflow Java Batch Server 'SASApp - JES Java Batch Server" Name = "SASApp - Workflow Java Batch Server" Configuration Directory Deployment Directory "CASAS\Config\Lev3\Web\Applications\SASWIPSchedulingServices9.4" Configuration 'SAS\ConfiglLevalWIPSchedBatch Validation steps JES Java Batch Server In SAS Management Console, on the Plug-ins tab, select Select "+" to expand SASApp. Select "#" to expand the SASApp - Logical SAS Java Batch Server. Verify the existence of the java batch server(s) referenced above. +" to expand the Server Manager node, {l:11C:/SASIConfigiLev3:Documents/instructons.himl ast1516/2020 Configuration Guidelines and Details 5, Right mouse click this server and select Properties. 6. Click the Options tab, 7. Validate that the command line and arguments are appropriate for this java batch server. Workflow Java Batch Server In SAS Management Console, on the Plug-ins tab, select “* to expand the Server Manager node. Select "+" to expand SASApp. Select “+" to expand the SASApp - Logical SAS Java Batch Server. . Verify the existence of the java batch server(s) referenced above. 5. Right mouse click this server and select Properties . Click the Options tab. . Validate that the command line and arguments are appropriate for this java batch server. Nogeene servicetrigger.ini file 1. The file servicetrigger ini may need to be modified. This fle is located in the install folder C:\Program Files\SASHome3\SASWeblnfrastructurePlatformSchedulingServicesl9.4. 2. The following default settings for Java command line options appear in this file: java.net preferlPv4Stack=true and java.net preferIPv6Addresses=false. 3, Ifthe system is configured to use IPV6, these values must be changed to: java.net preferlPv4Stack=false and java.net preferlPv6Addresses=true. Scheduling Services - Cache Locator Host Machine Port Log directory Configuration Configuration Directory desktop-10 41417 CASAS\Config\Lev3\Web\gemfirelinstances\ins 41417 ‘C:\SAS\Config\Lev3\Weblgemfrelinstances\ins_41417" Windows Service Execution fYP¢ | Sas (Config-Lev3] Cache Locator on port 41417 1. Check the status of the running locator process using Validation steps Windows Service : SAS [Config-Lev3] Cache Locator on port 41417 2, Validate that the locator process is started Scheduling Services - DIP JobRunner Host Mac! e Log directory Configuration Execution type Validation steps desktop-10 CASAS \Config\Lev3\Web\ApplicationsiSASWIPSchedulingServices9.4\dip Configuration Directory = "C:\SAS\ConfighLeva\Web\Applications\SASWIPSchedulingServices9.4\dip" Windows Service SAS [Config-Lev3] DIP JobRunner 1. Check the status of the DIP JobRunner process by running C:SAS\Config\Lev3\Web\Applications\SASWIPSchedulingServices9.4\dip\DIPJobRunnerService,bat status 2, Validate that the server is stopped. SAS Business Rules Manager Server Configuration Working | C:\SAS\Config\Lev3\Applications\SASBusinessRulesManagen3.2\ area created {le:11C:/SASIConfighLev3:Dacuments/instructons.himl ast1516/2020 Configuration Guidelines and Details for application SAS High-Performance Risk SAS High-Performance Risk Server Configuration SAS High- Performance Risk C:\SAS\Config\Lev3\AppDatalSASHighPerformanceRisk Root Directory Workspace Server SASApp - Logical Workspace Server You can access the latest documentation for SAS High-Performance Risk Server Configuration at hitp/support.sas,com/documantaion/oninedoc/norsklindax.himl withthe following access key: Documentation + Access Key: Man@93r15k The following database has been created in the SAS Risk Common Data Server. ‘+ Database Namo: RiskTrans = Host: desktop-10 + Port: 10504 + User 1D: riskuser Application Databases SAS Risk Work Group Server Configuration ‘SAS Risk Work Group Root C:\SAS\ConfigiLevatAppDatalSASRiskWorkGroup Directory You can access the latest documentation for SAS Risk Werk Group at with the following access key: Documentation + Access Key: Man@93r15k SAS Risk Management SAS Risk Dimensions Server You can access the latest documentation for SAS Risk Dimensions at http:/support.sas.com/documentation/anlinedoc/hprisidindex.htm! with the following access key: Documentation + Access Key: Man@93r15k SAS Infrastructure for Risk Management Server Configuration Content and After SAS Infrastructure for Risk Management has been configured successfully, you can download Documentation content specific to your environment as detailed in the SAS Infrastructure for Risk Management: {l:11C:/SASIConfighLev3:Dacuments/instructons hl 10911516/2020 Configuration Guidelines and Details ‘Administrators Guide. The SAS Infrastructure for Risk Management: Administrator's Guide can be downloaded at hti:/support sas.com/documentation/prod-piirm/ with the following access key: + Access key: INFRStructr SAS Risk Governance Framework SAS isk Governance Framework Server Operational files and directories for SAS Risk Governance Framework 7.4 are in CASAS\Config\Lev3\AppData\SASRiskGovernanceFramework and in licalions\SASRiskGovernanceFrameworkServer Configuration Directory LASR Reload Library | “brary name is rafroad. ‘The memory provided to standard Workspace Server sessions must be increased to allow LASR load jobs to run successfully + Inthe SAS Management Console, expand the Server Manager plug-in. Expand SASApp and expand SASApp - Logical Workspace Server. Right click on SASApp - Workspace Server and and select Properties from the drop-down menu Select the Options tab Within the Command text box, add the following argument to the command that launches the Workspace Server: -memsize 4G Verity |! Workspace |! ServerMemory |! Setting Note that the value specified for -memsize should be the largest value allowed in your environment, subject to the specifications of the SAS Tier machine and IT policy. Four gigabytes (4G) is the minimum recommended value. SAS Risk Govemance Framework 7.4 requires the additional deployment of a solution content Documentation | package. For the URL and access key for the solution documentation, contact the SAS Installation Representative at your site or contact SAS Technical Suppor, SAS k Governance Framework Admi SAS Risk Governance Framework 7.4 requires the additional deployment of a solution content package. Documentation For the URL and access key forthe solution documentation, contact the SAS Installation Representative at your site or contact SAS Technical Suppor. Configuration Operational files and directories are in Directory C:\SAS\Config\l ev3\Applications\SASRiskGovernanceFrameworkAdministrativeTools After the middie tier is installed and configured, complete the SAS Risk Govemance Framework post instareoatsaltn take as daveb Inne SAS Pk GovomanceFramenar haan and tation Conrguaton Guide Forno URC an acoss ey forthe clio docoentatn ona SAS Installation Representative at your site or contact SAS Technical Support. SAS Risk Governance Framework LASR Configuration LASR Server Risk Gov Frwk LASR Analytic Server fle: f1C:/SASiConfighLev3:Documents/instructons hm 1111516/2020 Configuration Guidelines and Details LASR Library RGF LASR LASR Library Libref_ RGFLASR SAS Risk Governance Framework Mid-Tier LASR Configuration = Group RGF Data Administrators was added to role Visual Analytics: Administration Add Groups to Roles + Group RGF Data Administrators was added to role Visual Analytics: Date Building + Group RGF Users was added to role Visual Analytics: Data Building SAS Model Implementation Platform SAS Model Implementation Platform Server Configuration The following database has been created: + Database Type: SAS Risk Common Data Server Application» Database Name: ModimpTrans Databases + Host: desktop-10 + Port: 10504 + User 1D: modimpdbuser You can access the latest version of the SAS Model Implementation Platform documentation at Mip1@ttrm SAS Risk Model Editor SAS Risk Model Editor Server Configuration The following database has been created in the SAS Risk Common Data Server: Database Name: ModEdTrans Host: desktop-10 Port: 10504 User ID: modeddbuser Application Database Remote Services The Remote Services process is not used by SAS applications and solutions beginning with SAS 9.4. Itis configured, but not running by default. If you want to deploy a custom application into this SAS 9.4 environment that previously used Remote Services, contact Technical Support for more information. SAS Environment Manager Configuration SAS Environment Manager Name desktop-10 {l:13C:/SASiConfigiLev3:Documents/instructons.himl 208116/2020 Contiguration Guidelines and Details SAS Environment Manager Port Name 7082 SAS Environment Manager Secure Port Name 7445 SAS Environment Manager Home Dir ¢1SAS\ConfiglLevaiWeb\SASEnvironmentManagerserer-5.8.0- SAS Environment Manager Administrator Name sasadm@saspw ‘SAS Environment Manager Admi trator Email Roda rian. magpantay@gmail.com SAS Environment Manager Database Type PostgreSQL SAS Environment Manager Database Server desktop-10 ‘SAS Environment Manager Database Server Port Name 454 SAS Environment Manager Database Server Name _EVManager SAS Environment Manager Web Console _hiipiliiesklop-10:7082/ C:\SAS\Config\Lev3iWeb\SASEnvironmentManageriserver-5.8.0- Log directory ESjne Starting and Stopping SAS Environment Manager You can start and stop your SAS Environment Manager use the Service Control Manager (Control Panel->Services). Service Name: SAS [Config-Lev3] SAS Environment Manager You can also manually start and stop SAS Environment Manager with the following commands. To start SAS Environment Manager, enter ce C:\SAs\ConFig\Lov3\Web\SASEnvironmentManager\server-5.8.0-E£\bin he-server.bat start To stop SAS Environment Manager, enter ha-server.bat stop Note: that the first time the SAS Environment Manager starts up it may take several minutes to initialize, Subsequent startups will be much faster. PostgreSQL Configuration Manual Steps Use the following steps to manually configure PostgreSQL inventory configuration properties in the SAS Environment Manager system. Log on to the SAS Environment Manager Web Console. Click ‘Browse’ under Resources List all servers by clicking ‘Servers’ Click one of the server name including PostgreSQL (for example, abc.com PostgreSQL 9.x localhost:9432}. You need to do the following steps for all server names including PostgreSQL, Go to the configuration page by clicking the Configure Server button in the Tools Menu. Note: The Configure Server button is only available contextually when a PostgreSQL server has been selected. 6. Supply values for the following properties, postgresql.host Host name of the PostgreSQL server. Listening port of the PostgreSQL. server.(You can find it from the path or command of the Windows. postgresql.port service Web Infrastructure Platform Data Server’, it should be a number after -p'. Default value: 9432) {le:11C:/SASIConfighLev3:Documents/instructons hm 130811516/2020 Configuration Guidelines and Details postgresql.user Username of the PostgreSQL server (Default user: dbmsowner) postgresql.pass Password for the specified user. Full path to the data file (Usually the path is SSASConfig/LevN/WebinfrastructurePlatformDataServeridata) ‘Windows service name of the PostgreSQL server (Default name: SAS [Config-LevN] Web Infrastructure Platform Data Server) postgresql.pgdata service_name Restarting SAS Environment Manager Agent The SAS Deployment Agent is not running on the host desktop-10. Use the following command to restart the SAS Environment Manager Agent on this hast: C:\SAS\Config\Lev3\Web\SASEnvironmentNanager\agent-5.8.0-2E\bin\hg-agent.bat restart SAS Environment Manager Agent Configuration SAS Environment Manager Agent Home Dir C:\SAS\Config\Lev\WebISASEnvironmentManager\agent-5.8.0-EE SAS Environment Manager Agent Host Name desktop-10 SAS Environment Manager Agent Port 2146 Log directory _C:\SAS\Config\Lev3\Web\SASEnvironmentManageriagent-5.8.0-EE\log Starting and Stopping SAS Environment Manager Agent ‘You can start and stop your SAS Environment Manager Agent use the Service Control Manager (Control Panel->Services). Service Name: SAS [Config-Lev3] SAS Environnent Manager Agent You can also manually start and stop SAS Environment Manager Agent with the following commands. To start SAS Environment Manager Agent, enter ce C:\SAs\conFig\Levs\Web\SASEnvironmentHanager\agent: hg-agent.bat start ee\bin To stop SAS Environment Manager Agent, enter ha-agent.bat stop To restart SAS Environment Manager Agent, enter ha-agent.bat restart The “restart” command will force the agent to contact the SAS Environment Manager and then save the connection settings to the agent’s C:\SAS\Config\Lev3\Web\SASEnvironmentManageragent-5.8.0-EE\data directory. To run SAS Environment Manager Agent setup, you must run command line under a command prompt (On Windows 7 or above, if above commands retum error, open a command prompt in the Run as administrator mode, then run above commands again SAS Environment Manager Enablement Kit Server {l:11C:/SASIConfighLev3:Documents/instructons hil 1411516/2020 Configuration Guidelines and Details Quick Start Guide For information on initializing SAS Environment Manager Enablement Kit Server, see CASAS\Config\L ev3\Web\SASEnvironmentManagerier framework\SAS_Environment_Manager_Service_Architecture_Quickstart.paf. For the most up-to-date information, including hints and tips, troubleshooting, and additional kits, see |http/support sas com/software/products/sev/index html. SAS Web Server Configuration Vendor SAS Web Server Name SAS Web Server Version 10.04 Installation Directory C:\Program Files\SASHomeS\SASWebServeri9.4 Instance Directory _C:\SAS\Config\Lev3\Web\WebServer Host deskiop-10 HTTP Port 81 HTTPS Port 444 Server Administrator Email Address _rian.magpantay@gmail.com Server Home Page hitp:idesktop-10:81 Configuring SAS Web Server You have configured SAS Web Server as part of your deployment. The server is configured as a load-balancing web server for SAS Web Application Server. ‘SAS Web Server Configuration Scripting Tools The SAS Web Server configuration scripting tool is generated during SAS Deployment Wizard configuration. This too! allows you to manually execute configuration steps through a command line interface. You performed an automated configuration. The tool can restore or reconfigure each resource exactly as it was configured during the SAS Deployment Wizard configuration steps. The scripting tool is located in the directory C:\SAS\Config\Lev3\Web\Scripts\WebServer. It is possible to make changes to your configuration by modifying property files and rerunning steps using the configuration tool Detailed instructions for the configuration framework can be found in the SAS intelligence Platform: Midale-Tier Administration Guide. ‘Summary of Automated Configuration Steps You have chosen auto configuration of SAS Web Server. The following list contains a summary of configuration actions the SAS Deployment Wizard has already performed: 4. The installation paths found in the scripts and configuration files located in the installed image have been updated. 2, An instance of the web server has been created 3, A service has been installed for starting and stopping the web application server. 4, A custom SAS configuration file has been created. This configuration fle is updated when new application servers and applications are added. Starting and Stopping Servers 1, Enable execution of powershell scripts: {l:11C:/SASIConfighLev3:Documents/instructons hil 15011516/2020 Configuration Guidelines and Details The script used to install the service and start the server is written in Windows PowerShell 2.0. If necessary, enable Windows PowerShell for script processing; by default, script processing is disabled. 1, Start PowerShell from the Start Menu as an Administrator by opening Start > All Programs > Accessories > Windows PowerShell, then right-clicking on Windows PowerShell and selecting Run as Administrator. A PowerShell window starts. 2. Check the current PowerShell setting by executing the following command: PS prompt» Get-ExecutionPoticy Ifthe command returns Restricted, it means that PowerShell is not yet enabled. Enable it to allow local script processing at a minimum by executing the following command: PS prompt» Set-ExecutionPolicy RenoteSigned 2. Install the service for starting and stopping the web application server: The service is already installed during an automated configuration. To install the service enter: cd C:\SAS\Config\Leva\web \kebserver\bin powershell .\httpdectl.pst install 3, Start the server: powershell .\httpdctl.psi start 4, Stopping the server: powershell .\httpdctl.pst stop Log Files There are potentially three log files generated by the server and when any of them reaches a size of 50 megabytes, itis saved and a new log file of that type is started. Log files are placed in the directory C:ASAS\Config\Lev3lWeb\WebServerilogs. Each log file includes a datestamp as part ofthe file name. These logs are not removed and should be periodically cleaned up to recover disk space. The following list describes the three different log flles that can be generated: + access_YYYY_MM_DD-HH-MM.log - plain text http requests » error_YYYY_NIM_DD-HH-MM.log « server error log * ss|_request_YYYY_MM_DD-HH-MM.log - secure requests, (only when SSL is configured) Web Application Server SAS Web Application Server Vendor | SAS Application Server Name | SAS Web Application Server Version | 9.44 ‘SAS Web Application Server Home Dir | C:\Program Files\SASHome3\SASWebApplicationServen9.4 Java Home | C:\Program Files\SASHome3\SASPrivateJavaRuntimeEnvironment\9.4\jre Configuring Your SAS Web Application Server When the SAS Deployment Wizard installs and configures your SAS software, it provides the option to configure a SAS Web Application Server configuration and to deploy SAS web applications. {l:11C:/SASIConfighLev3:Documents/instructons hil 16911516/2020 Configuration Guidelines and Details ‘basic SAS Web Application Server configuration has been created for you that uses SAS authentication and connections that are not secure. This configuration should support a small number of users. If you need to set up a more sophisticated topology such as web server authentication or single sign-on, see the SAS Intelligence Platform: Security Admit Guide. For reverse proxy server and secure socket connections, see the SAS Intelligence Platform: Middle-Tier ‘Administration Guide. ‘SAS Web Application Server Configuration Scripting Tools ‘ASAS Web Application Server configuration scripting tool is generated during a SAS Deployment Wizard configuration. This tool allows you to manually execute configuration steps through a command line interface. if you performed a manual configuration, you can execute the scripting tool to create the server configuration and to configure resources that are equivalent to what would have been built during a SAS configuration if you had performed an automated configuration. If you Performed an automated configuration, the tool can reconfigure each resource exactly as it was configured during the SAS. Configuration step. ‘You can execute the individual steps and make changes to your configuration by modifying the following property files. C:\SAS\ConFig\Lev3\web\Scripts\ApaServer\props\appserver properties C:\SAS\Config\Levs\web\Scripts\apaServer\props\credentials. properties You can rerun the scripting tool to redeploy or reconfigure web applications to SAS Web Application Server, or SAS Web Server. (C:\SAS\ConFig\Levs\neb\Seripts\ApsServer\appsrvcontig.cnd -2 You can use the scripting too! to stop, start, or restart all configured servers including SAS Web Application Server, SAS JMS. Broker, SAS Cache Locator, or SAS Web Server. :\SAS\Config\Lev3\Web\Seripts\ApaServer\appsrvconfig.cmd stop C:\SAS\ConFig\Levs\web\Scripts\aposerver\appsrvcontig.cnd start CC2\SAS\Config\Lev3\heb\Scripts\ApaServer\appsrvconfig.cnd restart You have chosen auto configuration of the SAS Web Application Server. The following list is a summary of configuration actions the SAS Deployment Wizard has already performed: Configuring SAS Web Application Server Instance(s) Host machine | desktop-10 Port |8081, 8443, Server Name | SASServert CASAS\Config\Lev3\Web\WebAppServer'SASServert_t Log directory | C:\SAS\Config\L ev3\Web\WebAppServeriSASServert_1Nogs Clusterable Web Applications ‘SASWebinfrastructurePlatformServices9.4 ‘SASWebinfrastructurePlatformApplications9.4 ‘SASWIPAdmin9.4 ‘SASWIPResources9.4 ‘SASStoredProcess9.4 ‘SASWorkflow9.4 ‘SASContentServer9.4 ‘SASPrincipalServices9.4 ‘SASIdentityServices9.4 ‘SASAuthorizationServices9.4 ‘SASTemplateEditor9.4 ‘SASPermissionManager9.4 ‘SASFlexThemes4.7M2 ‘SASThemeDesigner4. 7M2ForFlex ‘SASThemes9.4 ‘SASDeploymentBackup9.4 ‘SASBackupManager9.4 {le:11C:/SASIConfighLev3:Documents/instructons hm 178116/2020 I Configuration Guidelines and Details Non-clusterable Web Applications. Windows Service SAS [Config-Lev3] SASServer!_1 - WebAppServer Validation steps Check the status of the running Web Application Server Windows Service : SAS [Config-Lev3] SASServert_1 - WebAppServer Host machine desktop-10 Port 9081, 9443 ‘Server Name ‘SASServertt Configuration directory CASAS\Config\Lev3\Web\WebAppServer'SASServert1_1 Log directory CASAS\ConfigiLev3\Web\WebAppServer'SASServert1_i\logs. Clusterable Web Applications ‘SASRiskWorkGroup ‘SASRiskScenarioManager ‘SASHighPerformanceRisk ‘SASModellmpPitfrmMidTier ‘SASRiskModelEditor Non-clusterable Web Applications Windows Service ‘SAS [Config-Lev3] SASServert1_1 - WebAppServer Validation steps Check the status of the running Web Application Server Windows Service : SAS [Config-Lev3] SASServer1_1 - WebAppServer Host machine desktop-10 Port 9181, 9543 ‘Server Name ‘SASServer12 Configuration directory CASAS\Contig\Lev3\Web\WebAppServerISASServer12_1 Log directory ‘CASAS\Config\Leva\Web\WebAppServer'SASServert2_t\logs Clusterable Web Applications ‘SearchinterfacetoSASContent3.6 ‘SASVisualAnalyticsHub7.4 ‘SASVisualAnalyticsServices7 4 ‘SASVisualAnalyticsDesigner7.4 ‘SASVisualAnalyticsGraphBuilder7.4 ‘SASVisualAnalyticsViewer7 4 ‘SASVisualAnalyticsAdministrator7.4 SASVisualDataBuilder7.4 Non-clusterable Web Applications Windows Service ‘SAS [Config-Lev3] SASServer!2_1 - WebAppServer Validation steps Check the status of the running Web Application Server, Windows Service : SAS [Config-Lev3] SASSer Host machine desktop-10 Port 9281, 9643 ‘Server Name SASServer13 Configuration directory CASAS\Contig\Lev3iWeb\WebAppServeSASServer13_1 Log directory CASAS\Contig\Leva\Web\WebAppServerISASServer13_t\logs Clusterable Web Applications {le:11C:/SASIConfighLev3:Documents/instructons hm + SASDataManagement 189116/2020 Configuration Guidelines and Details Non-clusterable Web Applications Windows Service SAS [Config-Lev3] SASServer!3_1 - WebAppServer Validation steps (Check the status of the running Web Application Server, Windows Service : SAS [Config-Lev3] SASServer13_1- WebAppServer Host machine desktop-10 Port 8181, 8543 ‘Server Name SASServer2 Configuration directory C:AASAS\ConfigiLev3\Web\WebAppServeriSASServer2_1 Log directory CASAS\Config\LevaiWeb\WebAppServen'SASServer2_t\logs Clusterable Web Apy ions ‘SASEnvironmentMgrMidTier2.5 ‘SASSecurityAdminModule2.3 SASLineage3.2 SASWebDoc9.4 ‘SASEnvironmentMgrLibraryMod2.1 ‘SASServerModule2.1 ‘SASUserModule2.2 ‘SASStudioMidTier3,71 Non-clusterable Web Applications Windows Service SAS [Config-Lev3] SASServer2_1 - WebAppServer Validation steps ‘Check the status of the running Web Application Server Windows Service : SAS [Config-Lev3] SASServer?_1- WebAppServer Host machine desktop-10 Port 8681, 9043 ‘Server Name SASServer7 Configuration directory CASAS\Config\LevalWeb\WebAppServeriSASServer7_1 Log directory C:AASAS\ContigiLev3iWeb\WebAppServeriSASServer7_t\logs Clusterable Web Applications + SASDocisionManagerCommon3.2 ‘+ SASWorkflowAdministrator1 4 + SASBusinessRulesWebManager3.2, Non-clusterable Web Applications Windows Service SAS [Config-Lev3] SASServer?_1 - WebAppServer Validation steps ‘Check the status of the running Web Application Server Windows Service : SAS [Config-Lev3] SASServer7_1- WebAppServer Host machine desktop-10 Port 8781, 9143 ‘Server Name SASServer8 Configuration directory C:AASAS\Contig\LevaiWeb\WebAppServeriSASServer8_1 Log directory CASAS\ConfigiL eva\Web\WebAppServeriSASServer8_1\logs Clusterable Web Applications + SASIRM. + SASIRMServer + SASRiskGovernanceFramework {le:11C:/SASIConfighLev3:Documents/instructons hm 1918119672020 Configraton Guceines and Detals Non-clusterable Web Applications | Windows Service |SAS [Confg-L.ev3] SASServer_1- WebAppServer ‘Check the status of the running Web Application Server Validation steps Windows Service : SAS [Config-Lev3] SASServer8_1 - WebAppServer Configuring SAS JMS Broker The SAS Deployment Wizard installs and configures SAS JMS broker as a standalone server in SAS 9.4. Host machine | desktop-10 Port |61618 IMX Port | 11101 Configuration directory | C:\SAS\Config\Lev3\Weblactivema, Log directory | C:ASAS\Config\Leva\Web\activema\data Windows Service | SAS [Config-Lev3] JMS Broker on port 61618 (Check the status of the running JMS broker Windows Service : SAS [Config-Lev3] JMS Broker on port 61618 Validation steps SAS Web Applications SAS Themes Validation SAS Themes are used by SAS theme-enabled web applications. If you go to the logon screen for the Portal or steps Web Report Studio and see images then SAS Themes are working properly. SAS Environment Manager Mid-Tier + CASASIConfigllevaiWeb\Logs\SASServer?_1\SASEnvironmentMgrMidTier2.6.log Log file For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS Infeligence Platform: Middle-Tier Administration Guide at hnteusuppari.sas,com/94administration, SAS Security Administration Module Note This module is part of SAS Environment Manager * CASAS\Config\L ev3\WebiLogsiSASServer?_1\SASSecurityAdminModule?,3.log Log fil For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications” in the SAS Intelligence Platform: Middle-Tier Administration Guide at http:/support sas.com/94administration. SAS Environment Manager User Module Note This module is part of SAS Environment Manager {l:11C:/SASIConfighLev3:Documents/instructons.himl 201311516/2020 Configuration Guidelines and Details + CASAS\Config\Leva\Web\LogsiSASServer?_1\SASUserModule?.2.log Log file For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS Intelligence Platform: Middle-Tier Administration Guide at http:/support sas.com/24administration. SAS Environment Manager Library Module Note This module is part of SAS Environment Manager Log 'e For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS Intelligence Platform: Middle-Tier Administration Guide at htfpul/supportsas,com/@4administration, SAS Environment Manager Server Module Note This module is part of SAS Environment Manager » C:ASAS\Config\Lev3\WeblL ogsiSASServer?_1\SASServerModule?.1.log Log fil For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications” in the SAS Intelligence Platform: Middle-Tier Administration Guide at http:Jsupport sas.com/94administration. SAS Web Infrastructure Platform Log directory C:\SAS\Config\Lev3\Web\Logs\SASServer’_1\ 4. Access the Comment Service. Validation steps 2. Log in using the DESKTOP-10\sasdemo credentials provided during configuration. 3, Verify that you can add a comment. URL _hitp://desktop-10:81/SASStudio + CASAS\Config\L eva\Webil og: 1ver2_1\SASStudioMidTi Log file For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS intelligence Platform: Middle-Tier Administration Guide at httpilsupport sas.com/24administration. Validation _1, Access the URL provided above. steps 2. Login using the DESKTOP. 10\sasdemo credentials provided during configuration. {l:11C:/SASIConfighLev3:Documents/instructons hil 2113411516/2020 Configuration Guidelines and Details Notes: * Ifyou have a CAS server deployed and would like to configure SAS Studio to connect by default, you can set the CASHOST and CASPORT options in a SAS autoexec file, This can be done on a per user basis by using the "Edit ‘Autoexec File" menu item on the application options menu in SAS Studio, This can also be done for all users by adding itto the autoexec for the SAS workspace server. For SAS Studio Mid-Tier, this can be added to the autoexec_usermods.sas file for your deployment (for example Config\Lev1\SASApp\WorkspaceServer\appserver_autoexec_usermods.sas for Windows or config/Lev1/SASApp/WorkspaceServeriautoexec._usermods.sas for Unix). SAS Content Server Logfile C:\SAS\Config\Lev3\Web\Logs\SASServeri_1\SASContentServer9.4.log In the SAS Management Console, on the Plug-ins tab, select node. Highlight the SAS Content Server. Right mouse click this server and select Validate. Log in using valid credentials for an unrestricted user defined in the SAS Metadata Server. You should see a Validation Successful message. [o expand the Server Manager Validation steps OREN SAS Stored Process Web Application URL _hitp:/desktop-10:81/SASStoredProcessido Log file C:\SAS\Config\Lev3iWeb\Logs\SASServert_1!SASStoredProcess9.4.log 1, Access the URL provided above. 2. Log in using the DESKTOP-10\sasdemo credentials provided during configuration. Validation > ON the Welcome page, click the "Sample: Server Test” link to access the custom input form for this stops sample stored process. 4, Select an output format and ODS style or accept the default values, and click the "Display SAS Output” button. 5. The output from the stored process is a simple message that the server processed the request. SAS Web Administration Console URL htt 0:81/SASAdmin Logfile C:ASAS\Config\Lev3\Web\Logs\SASServert_1\SASAdmin9.4.log Jideskt ‘Access the URL provided above. Log in using the sasadm@saspw credentials provided during configuration. On the main page, expand the “Environment Management" folder in the tree and select the “Users” node. \erify that "sasadm” appears in the "System Users" section in the right frame. Click the checkbox in the far right column of the "sasadm* row. Click the menu icon directly above the checkbox and select "Send E-mail" Enter your email address in the "To:" field and click "Send", 3. Verify that you received the email. Validation steps SAS Visual Analytics Services Service SAS Visual Analytics Transport Service {l:11C:/SASIConfighLev3:Documents/instructons.himl 221311516/2020 Configuration Guidelines and Details Log fi For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications” in the SAS Intelligence Platform: Middle-Tier Administration Guide at http:l/support.sas.com/94administration, Notes: + The SAS Anonymous Web User has been configured for your environment. Currently SAS Visual Analytics Services does not have Guest Access enabled. For more information on how to support Guest Access, see the topic "Supporting Guest Access" in the SAS Visual Analytics: Administration Guide available at ittp:/support.sas.com/documentatian/onlinedoc/va/index him! + The following URLs have been added to the configuration property 'sas.web.cdps.knownHosts’ on the SAS Application Infrastructure node: © http://opnsta.sas.com/ © htipy/opnstb.sas.com/ © httpy/opnste-sas.com/ SAS Visual Analytics Hub URL _hitp://desktop-10:61/SASVisualAnalyticsHub + C:SAS\Config\l ev3\WeblLogs\SASServer12_1\SASVisualAnalyticsHub7.4.log Log file For more details about how to modify your log format and to see what logging entails, see “Administering Logging for SAS Web Applications" in the SAS /ntelligence Platform: Middle-Tier Administration Guide at _http:support.sas.com/94administration Validation _1. Access the URL provided above. steps 2. Login using the DESKTOP-10\sasdemo credentials provided during configuration Notes: + The SAS Anonymous Web User has been configured for your environment. Currently SAS Home does not have Guest ‘Access enabled. For more information on how to support Guest Access, see the topic “Supporting Guest Access" in the SAS Visual Analytics: Administration Guide available at http//support.sas.com/documentation/onlinedoc/va/index,him|. SAS Visual Analytics Designer URL tt Log file For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS /ntelligence Platform: Middle-Tier Administration Guide at htfp:l/support.sas.com/@4administration. For a brief validation sequence, see "Validate Your SAS Visual Analytics Deployment” in the SAS Visual ation Analytics: Installation and Configuration Guide (Non-distnbuted SAS LASR) available at StePS _tip:/support.sas.com/documentation/onlinedocivalindex.him| {le:11C:/SASIConfigiLev3:Dacuments/instructons.himl 231311516/2020 Configuration Guidelines and Details SAS Visual Anal URL _http://desktop-10:81/SASVisualAnalytics Viewer + C:ASAS\Config\L ev3\Web\LogsiSASServert2_t\SASVisualAnalyticsViewer7.4.lo9 Log file For more details about haw to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS intelligence Platform: Middle-Tier Administration Guide at http:support.sas.com/94administration For a brief validation sequence, see "Validate Your SAS Visual Analytics Deployment” in the SAS Visual On Analytics: Installation and Configuration Guide (Non-cdistributed SAS LASR) available at StePS _ttp:/support sas.com/documentation/onlinedoc/va/index.htm| Validation Notes: + The SAS Anonymous Web User has been configured for your environment. Currently SAS Visual Analytics Report Viewer does not have Guest Access enabled, For more information on how to support Guest Access, see the topic "Supporting Guest Access" in the SAS Visual Analytics: Administration Guide available at nttp:/support.sas.com/documentation/onlinedociva/index,him|. SAS Visual Data Builder URL _http://desktop-10:81/SASVisualDataBuilder + CASAS\Config\Lev3\WebiLogs\SASServert2_1\SASVisualDataBuilder7.4.log Log directory For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS /ntelligence Platform: Middle-Tier Administration Guide at htlp:l/support.sas.com/@4administration. Validation F0"@ brief validation sequence, see "Validate Your SAS Visual Analytics Doployment" in the SAS Visual Tape Analytics: Installation and Configuration Guide (Non-distnbuted SAS LASR) available at StePS _tip:/support sas.com/documentation/onlinedocivalindex.him! SAS Visual Analyt 's Graph Builder + C:ASAS\Config\L ev3\Web\LogsiSASServer!2_1\SASVisualAnalyticsGraphBuilder7.4,log Log file For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS Intelligence Platform: Middle-Tier Administration Guide at htlp:support.sas.com/94administration. For a brief validation sequence, see "Validate Your SAS Visual Analytics Deployment” in the SAS Visual On Analytics: Installation and Configuration Guide (Non-distnbuted SAS LASR) available at StePS _nttp:/support sas.com/documentation/onlinedoc/va/index.htm| Validation {l:11C:/SASIConfighLev3:Documents/instructons hil 241311516/2020 Configuration Guidelines and Details SAS Visual Anal URL _http://desktop-10:81/SASVisualAnalyticsAdministrator + CASAS\Config\L ev3\Web\Logs\SASServer12_ 1\SASVisualAnalyticsAdministrator7.4.log Lea directory For more details about how to modify your log format and to see what logging entails, see “Administering Logging for SAS Web Applications" in the SAS intelligence Platform: Middle-Tier Administration Guide at http:support.sas.com/94administration For a brief validation sequence, see "Validate Your SAS Visual Analytics Deployment” in the SAS Visual On Analytics: Installation and Configuration Guide (Non-distnbuted SAS LASR) available at StePS _http:/support sas.com/documentation/onlinedoc/va/index.htm| Validation SAS Flex Application Themes SAS Flex Application Themes are used by SAS web applications that are displayed with the Adobe Flash Player. If these applications correctly display colors, graphics, and fonts, then the SAS Flex Application Themes have been successfully installed, Validation steps Validation SAS Theme Designer for Flex is accessible from htip://desktop-10:81/SASThemeDesignerForFlex. steps In order to use this application, you must be a member of the role "Theme Designer for Flex: Administration’. SAS Risk Scenario Manager URL _ httos//desktop-10:81/SASRiskScenarioManager ‘+ CASAS\Config\Lev3\Web\Logs\SASServert1_1\SASRiskScenarioManageriog Log file For more details about how to modity your ly format and to see what logging entals, see "Administering Logging for SAS Web Applications” inthe SAS Intligence Platform: Midle-Tier Administration Guide at htfd/sunportsas.com/Sdadministration 1. Access the URL provided above Validation 2, Loain using the DESKTOP-10\sasdemo credentials provided during configuration. aidation The web application will open, steps 4 This verifies that the product is properly configured 5. Logout of the application and close your browser window. ‘The folowing database has been created * Database Type: SAS Risk Common Data Server Application Database Namo: ScenNgr Databases + Host: dosktop-10 Port: 10504 User ID: scenmngrdbuser SAS Data Management Console URL hitpi/desktop-10:81/SASDataManagement Log file {le:11C:/SASIConfighLev3:Documents/nstructons.himl 251311516/2020 Configuration Guidelines and Details \Leva\WeblLogs\SASServer13_1\SASDataManagement.log For more details about how to modify your log format and to see what logging entails, see “Administering Logging for SAS Web Applications" in the SAS intelligence Platform: Middle-Tier Administration Guide at http:/support.sas.com/94administration. Make sure to add the SAS First User or a valid user to the following SAS Data Management user group which is automatically created for you: Data Management Executives. This will give the user view capabilities only. Validation For instructions about adding SAS users to a group, see "Adjust Group or Role Membership". steps 4. Access the URL provided above. 2. Login using the DESKTOP-10\sasdemo credentials provided during configuration, SAS Lineage Mid-Tier URL http//desktop-10:81/SASLineage + CASAS\Config\l ev3\WeblLogs\SASServer?_1\SASLineageS.2.log Log file For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS intelligence Platform: Middle-Tier Administration Guide at _http:support.sas.com/94administration, Validation _1, Access the URL provided above. steps 2. Login using the DESKTOP-10\sasdemo credentials provided during configuration Search Interface to SAS Content URL _hitpu/desktop-10:81/SASSearchService + CASASIConfi \Lev3lWeb\Logs\SASServer12_11SASSearchService.log Log file For more details about how to modify your log format and to see what logging entails, see “Administering Logging for SAS Web Applications" in the SAS intelligence Platform: Middle-Tier Administration Guide at http:/support.sas.com/94administration. 1, Access the sample URL, http/desktop~ 2. Log in using valid credentials defined in the SAS Metadata Server. 3, Verify that a list of XML/JSON links is displayed in the browser or downloaded as a file. Ifa file is Validation downloaded, open it in a text editor to verify that a list of resources/inks is retumied, steps 4, If you are testing Search through some client application (e.g. SAS Visual Analytics Hub) and if Search Interface to SAS Content has been installed in a separate installation, please restart the Web Application Server having dependent Web Applications (e.g. SAS Visual Analytics Hub) to ensure they register the presence of newly added web application. Notes: + For instructions about integrating Search Interface to SAS Content 3.6 with internet browsers and other search engines, refer to the document Integrating Search Interface to SAS Content 3.6, at |htlp:supportsas.com/documentationvinstallcenter/94/index htm! {l:11C:/SASIConfighLev3:Documents/instructons hil 261311516/2020 SAS Documentation URL SAS Content Server Log File Validation steps Configuration Guidelines and Details isk Governance Framework Mid-Ti SAS Risk Governance Framework 7.4 requires the additional deployment of a solution content package. For the URL and access key for the solution documentation, contact the SAS Installation Representative at your site or contact SAS Technical Support ttpsideskt. 0:8 1/SASRiskGovernanceF ramework nttplldesktop-10:81/SASContentServer/repository/default C:ASAS\Config\l ev3iWeb\Logs\SASServer8_1\SASRiskGovernanceFrameworkMidTier log 4, Access the URL provided above. 2. Login using the DESKTOP-10\sasrgfad credentials provided during configuration, 3, SAS Risk Governance Framework display expectations: © For a deployment with no SAS Risk Governance Framework content packages (solutions) loaded, itis acceptable to see a message stating You must install at least one solution to start using SAS Risk Governance Framework. © For a deployment with one content package (solution) loaded, you will see an initial screen Whose title will be the name of the content package (solution) loaded. © For a deployment with more than one content packaged (solution) loaded, you will be presented with a dialog titled Choose a Solution, which allows you to choose which solution to sign in to. SAS Deployment Backup and Recovery Tool Purpose and Scope Log directory Configuration + The SAS Deployment Backup and Recovery Tool synchronizes the backup and recovery of SAS. metadata, the SAS Content Server repository, and the databases that are managed by the SAS Web Infrastructure Platform Data Server or SAS Solution Data Servers. The SAS Deployment, Backup and Recovery Tool does not backup all files in a SAS deployment. The SAS Deployment Backup and Recovery Tool does not backup all files in the SAS configuration directory. No files in the SAS installation directory are backed up. The SAS Deployment Backup and Recovery Tool does not take the place of operating system and file system backups. + Performing regular backups of the SAS system is an important part of administering the SAS 9.4 Intelligence Platform configuration. Backups taken by the SAS Deployment Backup and Recovery ‘Tool should be synchronized with operating system and file system backups to ensure that files and content can be restored to the same point in time. For more information, see "Best Practices for Backing Up and Restoring Your SAS Content” in the SAS intelligence Platform: System Administration Guide at http://support sas.com/94administration, + Backups can only be used in recovering the SAS deployment for which they are created. A backup from one SAS deployment cannot be used to recover another SAS deployment, Recovery using SAS Backup Manager is not supported. Recovery of data must be invoked using the command line Utilities provided by SAS Deployment Backup and Recovery Tool. For more information, see the SAS Intelligence Platform: System Administration Guide at hitp/support,sas.comy/94administration. + CASAS\Config\Lev3\Web\Logs\SASServert_1\SASDeploymentBackup9.4.log + A central vault location was not specified during installation and configuration. Backups will be stored in a local vault, * For each tier the path for the local vault is: SAS-configuration-directory/Lev /Backup/Vault + Backups are retained for 30 days and purged automatically after this period. + The SAS Deployment Backup and Recovery Tool is configured to run scheduled backup each Sunday at 1:00 a.m. local time, + See “About the Deployment Backup and Recovery Too!" in the see the SAS Intelligence Platform: ‘System Administration Guide at http:J/support.sas.com/94administration fl: 11C:/SASIConfighLev3:Documents/instructons hil 27st1516/2020 Configuration Guidelines and Details to learn what is and is not backed up by the SAS Deployment Backup and Recovery Tool and for information about modifying the backup configuration |. Launch the SAS Environment Manager Web Console 2. Lag in using the sasadm@saspw credentials you specified during configuration. . Click Administration in the menu bar to open the SAS Environment Manager Administration. |. Open the SAS Backup Manager by clicking the Side Menu icon in the SAS Environment Manager Validation banner and select SAS Backup Manager. The SAS Backup Manager appears. steps Note: The SAS Backup Manager might take several minutes to load as it discovers the assets that, are available for backup in the deployment. 5. In the SAS Backup Manager, click Start Backup. 6. Verify that the backup completes successfully Note + For more information about the SAS Deployment Backup Tool, see the SAS Intelligence Platform: System Administration Guide at hito://support sas. com/24administration + Best practices for backing up and restoring your SAS content can be found in the SAS intelligence Platform: System Administration Guide at hitp://support sas, com/24administration, SAS High-Performance Risk Mid-Tier URL _hitp//desktop-10:81/SASHighPerformanceRisk + C:ASAS\Config\L ev3\WebiL ogsiSASServert1_1\SASHighPerformanceRisk.log Log file For more detals about howto modiy your log format and to see what ogging ental, see “Administering Logging for SAS Web Applications" in the SAS intelligence Platform: Middle-Tier Administration Guide at http://support.sas.com/94administration. 4, Access the URL provided above 2 Login using the DESKTOP. 0\eaademo credentials provided during configuration, Validation oe: you receive an error message that you donot belong o any risk wrk groups, navigate to _http:/support.sas.com/documentation/onlinedoc/hpriskindex html, select your version of SAS High- Performance Risk from the available tabs, and open the link to SAS Risk Dimensions and SAS High Performance Risk documentation with the access key Man@93r15k. SAS Risk Work Group Mid-Tier URL. https/desktop-10:81/SASRiskWorkGrouplrest! + CASAS\Config\L ev3\WebiLogs\SASServer!1_1\SASRiskWorkGroup.log Log file ee’ For more details about how to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS Intelligence Platform: Middle-Tier Administration Guide at hitp:l/support.sas.com/94acministration. Validation steps 1. Access SAS Risk Work Group using the URL above. 2, Sign in using the DESKTOP-10\sasdemo credentials provided during configuration. 3, The response will be JSON that starts with: ("version":, "links". If you either directly see this string in the browser, or the browser prompts you to open or save a JSON file that contains this {l:11C:/SASIConfigiLev3:Documents/instructons.himl 201311516/2020 Configuration Guidelines and Details string, then SAS Risk Work Group is functional 4, With some web browsers, you may see XML displayed in the browser. It will have the same elements as the JSON version but formatted as XML elements. This result also indicates that SAS Risk Work Group is functional. 5, Sign out, if necessary, and close your browser. The latest documentation for SAS Risk Work Group can be found at hitps:/documentation sas.com/? docsetld=riskwg&docsetTargetttlepage,htm&docsetVersion=4.1 with the following access key: Documentation + Access Key: Man@93r15k SAS Infrastructure for Risk Management Mid-Tier URL _http:/desktop-10:81/SASIRM ‘+ C:ASAS\Config\Lev3\Web\Logs\SASServer8_1\SASIRM.log + CASAS\Confi \Lev3iWeb\Logs\SASServer8_11SASIRMServerlog Log file For more details about how to modify your log format and to see what logging entails, see “Administering Logging for SAS Web Applications" in the SAS intelligence Platform: Middle-Tier Administration Guide at nttp:lsupport.sas.com/24administration. 1, Access the URL provided above. Validation 2. Login using the DESKTOP-10\sasdemo credentials provided during configuration. steps 3. If you were able to login, then SAS IRM is properly installed and configured. 4, Logout. SAS Model Implementation Platform Mid-Tier URL _htlp:/desktop-10:81/SASModellmplementationPlatform + CASAS\Config\Lev3\WebiLogs\SASServert1_1\SASModellmpPitfrmMidTier.log Log file For more details about how to modify your log format and to see what logging entails, soo "Administering Logging for SAS Web Applications” in the SAS Intelligence Platform: Middle-Tior Administration Guide at http:/support.sas.com/94administration, Validation _4. Access the URL provided above. steps 2. Login using the DESKTOP. 10\sasdemo credentials provided during configuration. You can access the latest version of the SAS Model Implementation Platform documentation at Documentation Mip1@ttrm SAS Risk Model Editor Mid-Tier URL. hitpi/desktop-10:81/SASRiskModelEditor Log file + C:SAS\Config\L ev3\Web\Logs\SASServer!1_1\SASRiskModelEditor.log {le:11C:/SASIConfighLev3:Documents/nstructons.himl 200311516/2020 Configuration Guidelines and Details For more details about haw to modify your log format and to see what logging entails, see "Administering Logging for SAS Web Applications" in the SAS intelligence Platform: Middle-Tier Administration Guide at _http:support.sas.com/94administration. 41. Access the URL provided above. 2. Login using the DESKTOP-10\sasdemo credentials provided during configuration, SAS Deci jon Manager Common Mid-Tier for De n Manager Host | desktop-10 + CASAS\Config\Lev3\WeblLogs\SASServer7_1\SASDecMgrShell3.2.10g Logfiles | | CiSAS\Gonfig\Lev3lWebiL ogs\SASServer?_1\SASDecMgrGommon3.2.log SAS Business Rules Manager Web URL Log file ‘The SAS Deployment Wizard (SDW) does not create application users by default. The SAS. Administrator must create users in the SAS Management Console with the appropriate group and role permissions. If the sasdemo user already oxists, you can add the user to one or more of the user groups in SAS Management Console. For information about how to configure users, groups and roles, see the SAS Business Rules Manager 3.2: Administrator's Guide Pre-validation steps Perform the quick start tutorial in the Getting Started section of the SAS Business Rules Manager 3.2: Validation User's Guide to validate your installation steps Note: If you have completed the validation steps for SAS Decision Manager, then you do not need to complete any additional validation steps for SAS Business Rules Manager. For more information, see the SAS Business Rules Manager 3.2: Administrator's Guide. All of the Documentation documentation is available atthe following URL: hitei/sunnor.sas,com/documantaton/oniin SAS Help Viewer for Midtier Applications URL _ httpu/desktop-10:81/SASWebDoc Validation Use the URL above and examine the list of product documentation. If there were any errors configuring the ‘steps help content, they will be reportedilisted on this page. Web Application Custom Content Ifyou wish to add custom content into SAS web applications, refer to the "Web Application Custom Content" section of the SAS Intelligence Platform: Middle-Tier Administration Guide located at hitp://supporl.sas.com/administration SAS Metadata Bridges The SAS Metadata Import or Export function of SAS Management Console and SAS Data Integration Studio will prompt for the location of a SAS license file, Therefore, a valid SAS license file must be accessible from the client machine. The license file may be available in the sid_files directory at the root of your SAS Software Depot or it may be included with your SAS Software Order E-mail. Ifit is with your SAS Software Order E-mail, then you should follow the instructions included in that e- mail for where and how to store your SAS license fil. fle: 11C:/SASIConfighLev3:Documents/instructons.himl 300311516/2020 Configuration Guidelines and Details Obtaining Additional Information Additional SAS Intelligence Platform documentation is available from the SAS 9.4 administration documentation web site. There may be additional configuration steps required for your SAS Foundation software. Consult the SAS Foundation Configuration instructions available for your operating system for product-specific post-installation steps. The configuration instructions are available from the SAS Install Center web sit. Backing Up Your SAS Deployment The SAS system now includes a Deployment Backup utlty that can back up the following components of your SAS deployment: + the metadata server * selected data and configuration directories on any SAS server tier * the SAS Content Server repository * any SAS Web infrastructure Data Server databases + custom directories configured for your site If the Deployment Backup utility is configured on your system, it will automatically run every Sunday at 1 a.m. The automatic backup schedule can be changed or disabled. For more information, see "Using the Deployment Backup and Recovery Too!” in the SAS Intelligence Platform: System Administration Guide at htlorl/support.sas.com/94administration, Caution: Regular backups of your SAS system are crucial to ensuring the health of your SAS 9.4 Intelligence Platform configuration. Itis recommended that you schedule regular system backups to occur just after the SAS metadata or deployment backups so that each system backup includes a timely backup of your SAS components. For more information, see "Best Practices for Backing Up and Restoring Your SAS Content" in the SAS Intelligence Platform: System Administration Guide at http/support.sas.com/94administration. Copyright © 2018, SAS Institute Inc., Cary, NC, USA. All Rights Reserved {l:11C:/SASIConfighLev3:Documents/instructons hil 31131