Scribd
Upload
222 views26 pages

Lev1 SASInstructions

instructions

Uploaded by

Rian Mags
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
222 views26 pages

Lev1 SASInstructions

instructions

Uploaded by

Rian Mags
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 26
‘7/2020 Configuration Guidelines and Detals =_ a8 Configuration Guidelines and Details for “desktop-10' Overview Warnings and Notices Solulon Data Servers SASISHARE Server ‘SAS Add-on for SAP. ‘SAS Deployment Tester Server Remole Services ‘SAS Environment Nanager Configuration ‘SAS Environment Vanager Agent Configuration SAS Environment Manager Enablement Kit Server Server Configuration Warnings and Notices The folowing issues occured during the automated portion of your eonfguraton and must be addressed before proceeding + Some of the aliens in your environment may need access to the SAS/GRAPH Java applels ta view graphical output generated by SAS procasses. I ¢0, add tho APPLETLOC option to the sasv9_usormads cf fle locates in each SAS Application Server context directory Spectving the location fo be used in generating graphical output. APPLETLOC should point to a network accessible copy of the SASIGRAPH lava applets. ‘Since your deployment includes the SAS Web Infrastructure Platform, the applets can be made available vie: ‘app erioce"tetp:/eb-server:port/saeweh/eraph ‘The web server ports typically 8 on Windows deployments and 7980 on other deployments. Deployments that donot use a web server can point directly ta the SAS Web Application Server, which typically uses port 8080. NOTE: Do not add this line tothe sasv@_usermods.cg fle untl the SAS middle tie is configured. After updating the fle, restart the object spawner and validate your Workspace, Pooled Workspace, and the Stored Process servers again You indicated that securty policies could be modified by the SAS Deployment Wizard. As a result the user DESKTOP-10\sasdemo was granted the local securty policy Log on as a batch job (SeBatchL ogonRight) This policy allows @ user lo be logged on by means of @batch- {Queue facity and is requted when this account is used with SASApp - Workspace Server. ‘The policy wil take effect the nex! ime DESKTOP-1O\sasdemo authenticates against the operating system. Therefore, f DESKTOP- ‘0isasdemo is currently logged onto the system, a reboot will be needed for this palcy to take effect, + SAS Web Applications are being protected by a secur fitr that prevents linking from unauthorized hosts. The security filer is customizable For further information on customizing this fter, refer to "Whitelist of Websites and Methods Allowed to Link to SAS Web Applications" in the ‘SAS 9.4 Inteligence Platform: Midle-Tier Administration Guide, found in the SAS 94 Ineligence Plationm: Midde-Tier Adminsiralion Guide SAS Management Console ‘SAS Managemen! Console is requied to complete mary of the foloing steps Shortcut Programs > SAS > SAS Management Console 9.4 UserID SAS Administrator user ID {le 11C:/SASIConfigiLev'iDocuments/instructons.himl 108 ‘7/2020 Configuration Guidelines and Details Password Enter the password you croatod in the SAS Doploymont Wizard SAS Application Servers ‘SASMeta - Metadata Server Host machine Port 8561 dosktop-10 CASAS\ConfiolLevtLogs For mors details about fe intial logging configuration and how to marily, see “Administering Logging for SAS Servers” in the SAS Inteligence Platform: System Administration Guide a hiplsugoot. sas.com/tdadminisiraion. Execution Windows service type SAS [Confg-Levt] SASMeta - Metadata Server Shortcuts Programs > SAS > Configuration > Config -Levt Log directory + The metadata server is configured to perform unassisted metadata server backups. The backups are performed every day at 1 a.m. except an ‘Sunday and stored in the "C:\SASIConfighLev \SASMeta\MetadalaSorver\Backups” directory. Backups are retained for seven days, To learn about the metadata server backup facility, see “Backing Up and Recovering the SAS Metadata Server" in the SAS Inteligence Platform: System Administration Guide at hitp:Isupport.sas.con/S4administration. + Tho metadata servers configured to send an alot e-mail massage to [email protected] in the avant of a system, backup, or rocovory falls. You can test that tho alor-omral notification subsystem is conf gured property by opening tho Proportis shoot forthe active ‘metadata server in the SAS Management Console Metadata Manager and sending atest message. I the system is configured properly, you vill receive a tast e-mail fom SASMeta - Metadata Server Contig - Levt . Ifyou want lo change your alert e-mal ‘options, see tho section "Managing Alert E-mall Options forthe SAS Metadata Server" inthe chapter "Metadata Sorver Configuration Tasks" of the SAS Inteligence Platform: Systom Administration Guid at bitgisuppor.sas.com/Sdadministration. ‘SASApp - Connect Server Host machine Port 7551 CASAS\Cantigl evo For more details about the inital logging configuration and how to modly it, see “Administering Logging for SAS Servers" in the SAS. Intoligence Platform: Systom Administration Guide at biasugoont sas. com/Séadministalion. esktop-10 Log directory +. In the SAS Management Console, on the Plugsins tab, select “+” to expand the Server Manager node. 2 Expand SASAp 3. Expand SASApp - Logical Connect Server. Validation 4. Highlight the SASApp - Connect Server ‘stops 5. Right mouse cick this server and select Validate (you can enter DESKTOP-10\sasdemo or the SAS Spawned Servers account forthe user ID). You should see a Validation Successful message. NOTE: To succosstuly validate a CONNECT sorver, the associated spawner must be configured with option Signon Serpts Allowed sotto Yes. ‘SASApp - Stored Process Server, Host machine desktop-10 Port #601 Log directory CASAS\Confa Abo 4. In the SAS Management Console, on the Plugs tab, select "+" to expand the Server Manager node. 2 Expand SASApp. 43. Highlight the SASApp - Logical Stored Process Server. 4, Right mouse clck his server and select Validate, You should see a Validation Successful message Validation steps ‘SASApp - Workspace Server {le:13C:/SASIConfigiLev'iDocuments/instructons.himl 218 ‘7/2020 Configuration Guidelines and Details Host desktop-10 machine Port 8591 CASAS\Confi\Levil iecktt Paria aoas abate intl gang coniguaton an how mye Adrian ogg fr SAS Sern fe SAS irectory intelligence Platform: System Administration Guide at http:l/support.sas.com/admin’stration. ‘tno SAS Maragomont Const on he Pans by, select oxpandthe Sores Manager noe taion 5 Figugh ihe SAGAGD Log! Worapace Saver, 4 Right mouse click this sorvor and select Valdato (you can ontor DESKTOP-10\sasdomo or tho SAS Spawned Servers account ‘forthe user ID). You should see 8 Validation Successful message. Notes: + The C:\SASIConfgi evt\Logs directory is intended to serve as a placeholder for workspace server logs. Workspace server logs may be rected to ths directory in te event thal your SAS of IT administrator enables logging. The following default atfribules are associated withthe Logs directory Universal read, rite or execute access is disabled for the directory inorder to comply with default installation security requirements © Execution of a workspace server doss not populate the Logs rectory © The Logs drectory sorves asa 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 asthe requirement te grant universal write access to the Logs directory. To enable workspace server logging, perform the following steps: ® Enable read, wtte and execute access Io the Logs directory © Modify the workspace server logconfig.xml to enable the desired levels of logging ® Allematively, enable the logcontigtrace-xm logging fle to capture workspace server diagnostic logging ‘SASApp - Pooled Workspace Server Host machine desktop-10 Port 8701 1. Inthe SAS Management Console, on te Plugins tab, select“ to expand the Server Manager node. 2 Expand SASApp. 3 Highlight the SASApp - Logical Pooled Workspace Server. 4 Right mouse click this server and eelect Validate, You should see a Validation Successful message ‘SASApp - SAS DATA Step Batch Server Host maciost cesktop-10 CASAS\ConfigLovt\Logs For more detalls about the ital logging configuration and how to modly it, see “Administering Logging for SAS Servers" in the SAS. Inteligence Platform: System Administration Guide at iiplisupnarl sas comladmin stration, Log directory Validation 1. Select ths link: CASAS\Confo\L ev! SASAna ‘steps 2, IF SAS starts successfully, the DATA step batch server has been validated. SAS Spawners Object Spawner Host mach ost desktop-10 Port 8581 CASASIConfigLevitLogs For more details about the inal logging configuration and how to molly it, see “Administering Logging for SAS Servers” in the SAS Inteligence Platform: System Administration Guide at htpilsugnor.sas.comladministration. Execution Windows service type SAS [Config-Lovt] Object Spawner Log directory fle: f1C:/SASIConfigiLev'iDocuments/instrucvons.hml 316 ‘7/2020 Configuration Guidelines and Details ‘Shortcuts | Programs > SAS > Configuration > Config- Levt Connect Spawner Host maces! dosktop-10 Port Log directory For more details about ine intial logging configuration and how to modify it, soe "Administering Logging for SAS Servers" in the SAS. Inteligence Platform: System Administration Guide at htpuisunpor sas.com/Sdacminisration Execution Windows service ‘type SAS [Confg-Levt] Connect Spawner Shortcuts Programs > SAS > Configuration > Config - Lev SAS/SHARE Server Host machine Port 8551 CASASIConfilLevilk For more details about the intial logging configuration and how to modify t, see “Administering Logging for SAS Servers" in the SAS Inteligence Platform: System Administration Guide at iipsunpor sas com/Séacminisiration. desktop-10 Log directory Execution Windows service type SAS [Confg-Levt] Share Server Shorteuts Programs > SAS > Configuration > Config - Levt SAS Web Infrastructure Platform Data Server Host machine Port 9432 CASAS\ConfiolLevtLogs For more details about tne inital logging configuration ane how to modify it, see "SAS Web Infrastructure Platform Data Server in the ‘SAS Inoligence Platform: Middle-Tier Administration Guide al ii J/eunoor. sas com/%éadmninitralon dosktop-10 Log directory Execution Windows service type SAS [Confg-Levt] Web Infrastructure Platform Data Server Solution Data Servers ‘SAS Advanced Analytics Common Data Server Host mach st desktop-10 Port 10432 CASAS\ConfolLevtiLogs For more details about the intial logging configuration and how to modify it, s8e "SAS Web Inftastructure Patform Data Server in the ‘SAS Inteligence Platform: System Administration Guide at itplisuapor sas com SMadminstration, Log directory Execution Windows service ‘ype SAS [Confg-Lovt] Advanced Analytics Common Data Server ‘SAS Decision Manager Common Data Server Host machine Port 10482 dosktop-10 {le:f1C:/SASIConfighLev"iDocuments/instructons hil 428 ‘7/2020 Configuration Guidelines and Details Log |CASAS\ConfgiLevti directory For more details about te inital logging configuration ang haw to modlly i, see “SAS Web Infrastructure Patform Data Server" in the ‘SAS Intoligence Platform: Middlo-Tier Administration Guide at hijp/sungor sas. com4administraon. Execution Windows Service ‘Type SAS [Confg-Levt] Decision Manager Com Data Svr Cig ‘SAS Forecast Analyst Workbench Data Server Host mack ost desktop-10 Port 10030 CASASIConf Log e the recth For more detals about te inal logging configuration an how to modty i see "SAS Web nrastruture Platform Data Server inthe ‘SAS Inteligence Platform: System Administration Guide at bpdlsunport sas com/4administaton Execution Windows service ‘ype SAS [Config-Lav't] Forecast Analyst Workbench Data Server SAS Add-on for SAP The SAS Add-on for SAP is used withthe SASIACCESS Interface to RV3 product. For complete information about insaling and configuring the SAS ‘Add-on for SAP. please refer to the Post-lnstallation Instructions for SASIACCESS 4.4 Interface to RI3, avaliable from install Center ( tpitsupport sas, com/documentalioninetaleanter/en/krSeg/66652/PDFidefauliconfig.a) SAS Deployment Tester Server Host machine desktop-10 Port 10021 Execution Windows service type SAS [Config-Levt} Deployment Tester Server Shortcuts Programs > SAS > Configuration > Config - Lev? 1. In SAS Management Console, on the Plug-ins tab, 2 Select *+* to expand Deployment Testor 3, Highlight the host machine: deskiop-10 Validation 4. Rignt mouse click and select Run All Test Suites. 6 6 1cl"#" to expand the Application Management node. ‘steps 5, Select “+” to expand the Resuls Validate the results for each test suite. Al tests should pass, It you are prompted for credentials, select the for each test sue elp" button inthe Credentials dalog box to display the accounts that can be used + Deployment Tester Server is used to run tests on SAS products and servers to validate functionality and proper operation. The Deployment Taster Sarvarin conjunction with the Deployment Tester SASMC plug-in allows for tosis to bo executed on remote systoms 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 isa stand-alone server, dependent of tne rest of SAS, thal can be Slared and used periodically to vorty the health of your SAS deployment. You should consider verying the health of your SAS deployment fer inal installation, aftr applying maintonance and hot Fixes, of when you make any other significant changes tothe deployment. + More detailed information on valdating your SAS deployment with Deployment Tester can be found in tha "Using the Deployment Tester” section of the SAS 8.4 Intligence Pratform: System Administration Guide, which is avaiable at hlin./sunoor sas com/Sadminisalion. Operating System Services Scheduling Server Host mach st desktop-10 Port 8451 rectory CASASIConfolLevtiLogs Validation 1. Inthe SAS Management Console, on the Plug-ins ab, select "+" to expand the Server Manager node. {le:13C:/SASIConfigiLev'iDocuments/instructons.himl 5128 ‘7/2020 Configuration Guidelines and Details steps 2. Highlight Operating System Services - desktop-10. 3. Right mouse click this sorver and select Validate (you can enter DESKTOP-10\sasdema or the SAS Spawned Servers account for the user ID), You should see a Validation Successful message. SAS Visual Analytics SAS Visual Analytics Administration To provide access to SAS Visual Analytics, sa the topic “Adding Users" in the SAS Visual Analytics: Administration Guide. Fora brief validation sequence, see "Validate Your SAS Visual Analytics Deployment” in the SAS Visual Analytics: Installation and Configuration Guide (Non-distibulod SAS LAS) ‘Administrative documantation for SAS Visual Analytics is available from hit:/support.sas.comidocut SAS Visual Analytics High-Performance Configuration ‘SAS Visual Analytics Non-lstibuted LASR Data Provider ‘To schedule autoloading, run *C:\SAS\ConfiglLov \Applcations\SASVisualAnalytics\VisvalAnalyticsAdminstratorschedule bat” program, which wil then run periodically every "15° minutes. To unschadule, run Autoload "CiSAS\Confgl-ev \Applications\SASVieualAnalyticeVisualAnalyties Administraoriunschadule bat ‘Scheduling For more details about autoloading, see "Autoload" in the SAS Visual Analytics: Administration Guide at hipisupport sae comicecumentation/ontinedoclvalindex him! ‘Autoload iog joad 08 C:SAS\Config\Lev1\Applcatons\SASVisualAnalyticsVisalAnalyiesAdminstratorLogs SAS Information Retrieval Studio ‘SAS Information Retrieval Studio for SAS Host machine desktop-10 Server Admin Port 10551 Proxy Server Port 10861 Proxy Sorver Admin Port 10871 Proxy Server Web Admin Port 10681 Pipeline Server Port 10691 Server Admin Port 10701 Pipeline Server Web Admin Port 19711 Index Builder Port 10721 Query Server Port 10731 Query Statistics Server Port 10741 ‘Query Statistics Server UDP Port 10741 Crawler Admin Port 10751 ‘Query Web Server Port 10761 Windows service Execution ype EAS Confgrevil Infomation Retioval Susi SAS Web Infrastructure Platform Scheduling Services Log directory CASAS\ConfolleviiWenlLogs JES Java Batch Namo = "SASApp - JES Java Batch Sever" ‘Server fle: 13C:/SASIConfigiLev'iDocuments/instructons.himl 626 ‘7/2020 Configuration Guidelines and Details Worktiow Java Batch Ser Namo = "SASApp - Workflow Java Batch Server" ‘Configuration Directory = "C\SAS\ConfighLev'\Web\Applcations'SASWIPSchedulingServcess.£* Configuration Deployment Directory = "C:\SAS\ConfigiLevihWIPScheaBatch JES Java Batch Server in SAS Management Console, onthe Plugins tab, selec "so expand the Server Manager node, Select" lo expand SASApp, Select "+" lo expand the SASApp - Logical SAS Java Balch Server. Verify the existence ofthe java batch server(s) referenced above. Right mouse cick tis server and select Properties, Click the Options tab Validate thal the command line and arguments are appropriate fr ths java batch server. Workflow Java Batch Server In SAS Management Consolo, onthe Plug-ins tab, select ‘Select "to expand SASApp. ‘Select "+ to expand the SASApp - Logical SAS Java Batch Server. Verify the existence ofthe java batch server(s) referenced above. Right mouse cick this server and select Properties. lick the Options tab Validate thal tho command line and arguments are appropriate for this java batch server. 10 expand the Server Manager node. Validation steps servicetrigger.ini fils 1. The fl servicevigger ini may need to be modified. This file i tocated inthe instal folder C:\Program Files\SASHome\SASWeblntrastructurePlatformSchedulingServices\9, ‘The following default settings for Java command line options appear inthis file: java net. preferlPvaStack=irue and java.net preferlPvéAddressesfalse. IT the system is configured to use IPV6, these values must be changed to: java.net prferIPv4Stack=false and java.net preferlPvEAddresses=tre, ‘Scheduling Services - Cache Locator Host Machine desktop-10 Port 41415 Log directory C:\SAS\ConfiglLeviWebigemfioinstancesins 41415, Configuration Configuration Directory = "C:\SAS\ConfighLoviWebigemfirelnstancestins_41415" Windows Servico SAS [Confg-Levt] Cache Locator on port 41415 Execution type 4. Check the status ofthe running locator process using lation steps" Windows Service : SAS [Config-.ev1] Cache Locator on port 41415, 2. Validate that th locator process is started ‘Scheduling Services - DIP JobRunner Host Machine desktop-10 Log directory C:\SAS\Confic\Lev1iWeb\Agpicatons\SASWIPSchedulingServines® didip Configuration Configuration Directory = "C:\SAS\ConfighLevilWeb\Applications\SASWIPSchedulingServices9.4iip™ Windows Service Execution type SAS [Confg-Lev1] DIP JobRunner 4. Check the status of the DIP JobRunner process by running Validation steps" C:\SASIConfigiLevtWeb\Applications|SASWIPSchedulingServices9 4\dip\DIPUobRunnerServce.bat status 2, Validate thatthe serveris stopped. SAS Forecast Analyst Workbench ‘SAS Forecast Analyst Workbench Server Configuration fle: 11C:/SASIConfigiLev'iDocuments/instructons hl 18 ‘7/2020 Administrative Guide Notes Configuration Guidelines and Details Please execute the post instalation instructions in the SAS Forecast Analyst Workbench 6.3 Administrator's Guide User name: FAWDOG (case-sensiive); Password: UserDoc (case-sensitive) + Note thatthe SAS Demo User has been assigned the ID, DESKTOP-10\sasdemo, and assigned sufficient authorizations to assist you in validating this product and, perhaps, others. This includes the ably to run ETL jobs for this product. You may consider deleting ths user to Increase the security of your instalation after your validation efforts complete. ‘SAS Forecast Analyst Workbench Mid-Tier LASR Configuration Configuration Notes: The following SAS Forecast Analyst Workbench user groups were added tothe "Visual Analytics Data Administrators" group, + Forecast Analyst Administration Users 1 Forecast Analyst Analysis Users + Forecast Analyst Workbench ETL User ‘The following SAS Forecast Analyst Workbench user groups were added tothe "Visual Data Builder Administrators” group. Forecast Analyst Administration Users Forecast Analyst Analysis Users Forecast Analyst Planning Users Forecast Analyst Workbench ETL Users SAS Business Rules Manager Server Configuration Working area created for | C:SAS\ConfglL evt\Applicaions\SASBusinessRulesManagen3.2 application Remote Services The Remote Services pracess snot used by SAS applications and solutions beginning with SAS 9.4 IIs configured, but nat running by default If you want to deploy a custom application into this SAS 8.4 environment that previously used Remote Services, contact Technical Support for more information SAS Environment Manager Configuration SAS Environment Manager Name ‘SAS Environment Manager Port Name ‘SAS Environment Manager Secure Port Name SAS Environment Manager Home Dir 'SAS Environment Manager Administrator Name ‘SAS Environment Manager Administrator Email Address ‘SAS Environment Manager Database Type ‘SAS Environment Manager Database Server ‘SAS Environment Manager Database Server Port Name ‘SAS Environment Manager Database Server Name ‘SAS Environment Manager Web Console Log directory 19 SAS Environment Manager éosktop-10 7080 reas C:ASAS\ConfigLev1\Web\SASEnvironmentManagerserver-5.8.0-EE sasadm@saspw rian magpanta PostgreSQL dosktop-10 932 EVManager itmuldesktone 10.7080 C:ASAS\ConfigLev1iWeb\SASEnvironmentManagerserver-5.8.0-EEogs You can start and stop your SAS Environment Manager use the Service Control Manager (Control Panel->Services) Service Name! fle: 11C:/SASIConfigiLev'iDocuments/instructons hl ans. ‘772020 Configuration Guidelines and Details SAS [Conftg-Levt] Sts Environment Monsger ‘You can also manually start and stop SAS Environment Manager withthe following commands. To start SAS Environment Manager, entor To stop SAS Environment Manager, enter Note: thatthe fist time the SAS Environment Manager star's up it ay take several minutes to iniaize. 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 Cnsale. Click Browse’ under Resources List all severs by cing Servers Click one of the server name including PostgreSQL. (for example, abe.com PostgreSQL. 9.x acalhost:9432), You need tao the following steps forall server names including PostgreSQL Go tothe configuration page by clicking the Configure Server bution in the Tools Menu. Note: The Configure Server button is only avalable contextually when a PostgreSQL server has been selected, ‘Supply values forthe following properties. postgresqlhost Host name of the PostgreSQL server. Pe sae ste sa naga asmmersette Worse eb nas Windows service name of the PostgreSQL server (Default name: SAS [Config-LevN] Wob Infrastructure Platform Data Server) SAS Environment Manager Agent Configuration ‘SAS Environment Manager Agent Home Dir _C:\SAS\ConfigLevtiWebiSASEnvironmentManageriagent-5.8.0-EE ‘SAS Environment Manager Agent Host Name _desktop-10 ‘SAS Environment Manager Agent Port 2144 Log directory C:\SAS\Config\Lev1\WablSASEnvironmentManagertagent-5.8.0-EEllog 19 SAS Environment Manager Agent ‘You can start and stop your SAS Environment Manager Agent use the Service Control Manager (Control Panel->Services). Service Name: ‘As (Contig-Levt] SAS Enviroment Manager Agent You can also manually stat and stop SAS Enviranment Manager Agent withthe following commands. To start SAS Environment Manager Agent, enter C2 \Se8\contip\Leva\en\SeStavicennentanager agent-5.8.0 Ta stop SAS Environment Manager Agent, enter To restart SAS Environment Manager Agent, enter Tha “estan” command wil force the agent to contact the SAS Envizonmont Manager and then save the connection settings to the agant’s CASASIConfiglLov"\WWeb\SASEnvironmentManageriagant-5.8.0-FEWdata directory fle: 11C:/SASIConfigiLev'iDocuments/instructons hl 96. ‘i772020 Configuration Guidelines and Details To run SAS Environment Manager Agent setup, you must run command ine under a command prompt (On Windows 7 or above, if above commands retum error, open a command prompt in he Run as administrator mode, then run above commands again SAS Environment Manager Enablement Kit Server Quick Start Guide For information on intalzing SAS Environment Manager Enablement Kt Server, see C:\SAS\ConfigiLev1lWeb\SASEnvironmentManagerom- framework'SAS_Envionment_Manager_Service_Architecute_Quickstat pat For the most up-to-date informaton, including hints and tps, troubleshooting, and addtional kts, see iteilsupport sas com/sotwarelproducte/sewindex. il, SAS Web Server Configuration Vendor SAS Web Server Name SAS Web Server Version 10.16 Installation Directory C:\Program Files\SASHome\SASWebServer9.4 Instance Directory _C\SAS\ConfglLeviiWebiWebServer Host desktop-10 HTTP Port 62 HTTPS Port 445, ‘Server Administrator Emall Address ran [email protected] Server Home Page nilpilideskioo.10.82 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. ‘Tne SAS Web Server configuration scripting tools generated during SAS Deployment Wizard configuration. Ths tool allows you to manually execute configuration steps through a command line interface. You performed an automated configuration. The tool can resiore or reconfigure each resource fexacly as it was confgured during the SAS Deployment Wzard configuration steps, The Sexpting tol is located inthe directory CASASIConfiglLev'iWebiScrpis|WebServer, Itis possible to make changes to your configuration by modifying property les and rerunning steps using the configuration too Detaled instructions forthe configuration framework can be found in the SAS intelligence Platform: Midle-Tier Administration Guide. ‘Summary of Automated Configuration Steps ‘You have chosen auto configuration of SAS Web Server. The following Ist contains @ summary of configuration actions the SAS Deployment Wizard has already performed 41. The installation paths found in the scripts ané configuration files located in 2. Aninstance ofthe web server has been created 3. A service has been installed fr starting and stopping the web application server. 4, A custom SAS configuration file has been created. This configuration file's updated when new application servers and applications are added 2 installed image have been updated. ‘Starting and Stopping Servers 4. Enable execution of powershell scrips: ‘The script used to install the service ané stat the servers writen in Windows PowerShell 2.0. If necessary, enable Windows PowerShell for script processing; by defaul, script processing is cisadled 4. Start PowerShell from the Start Menu as an Administrator by opening Start » All Programs > Accessories > Windows PowerShell then Fight-clieking on Windows Powershell and selecting Run as Acministrator.A PowerShell window stats 2. Chack the current PowerShell selling by executing the following command fle: 11C:/SASIConfigiLev'iDocuments/instructons hl 1028 i772020 Configuration Guidelines and Details Ps pronpt> Get-ExecuttonFalicy Irthe command retums Resticted, it means that PowerShell is nol yet enabled. Enable ito allow local script processing at a minimum by ‘executing the following command: 2 Install the service fr starting and stopping the web application server: ‘The service is already installed during an automated configuration. To instal he service enter: @ €:\Sas\Contsp\Leva\ueb weaserveriain povershell -\httpacel-951 snstall 43, Star the server: powerahell \Httpdetl pet 4. Stopping the server: poworshell \hetpactl.p6t stop Log Filos There are potential three log fles generated by the server and when any of them reaches a size of 50 megabytes, i ls saved and a now log fle of that type is started. Logfiles are placed in the directory C:\SAS\Confoll ey‘\WeblWVenServeriogs. Each log fle includes a catestamp as part of the fla name. Thase logs are not removed and should be perioicaly cleaned up to recover disk space. The folowing list describes the lea diferent log fles that can be generated + accoss_YYYY_MM_DD-HH-MM og - plain ext hit requests + error. YYYY_Nfld_DD-HH.Miiog server errr log {881 /equest_YYV¥_MM_DD-HH-MM og - secure requests, (only when SSL is configured) Web Application Server ‘SAS Web Application Server Vendor [SAS ‘Application Server Name | SAS Web Application Server Version [945 'SAS Web Application Server Home Dir | C:\Program Fles\SASHomelSASWebApplicationServen 4 ‘Java Home | C:\Program Fies\SASHomelSASPrivateJavaRuntmeEnvironmenti9ljre Configuring Your SAS Web Applicat n Server When the SAS Deployment Wizard installs and configures your SAS software, i provides the option to configure a SAS Web Application Server configuration and to deploy SAS web apalications, ‘Abasic SAS Web Application Server configuration has been created for you that uses SAS authentication and connections that are not secure. This Configuration should suppor a small numberof user. If you need to set up @ more sophisticated topology such as web server authentication or Single sign-on, see the SAS Intel ‘Administration Guide, For reverse proxy server and secure socket connections, see the SAS infoligonco Plallom: Middle: Tier Administration Guido. ‘SAS Web Application Server Configuration Scripting Tools ASAS Web Application Server configuration scripting tools generated during a SAS Deployment Wizard configuration, This too! allows you to manually execute configuration steps through a command line interface, Ifyou performed a manual configuration, you can execute the serpting too! to create the server configuration and to configure resources that are equivalent to what would have been built curing a SAS configuration f you nad performed an automated configuration. Ifyou performed an automated configuration, the tool ean reconfigure each resource exacly as it was Configured during the SAS configuration step. ‘You can execute the individual stops and make changes to your configuration by maalfying the folowing property es. EASAS\Contse\tens\web\Serspee\appserver\prope\ceadenesnit propertios ‘You can rerun the scripting tool to redeploy or reconfigure web applications to SAS Web Application Server, or SAS Web Server. fle: 11C:/SASIConfigiLev'iDocuments/instructons hl 118 ‘i772020 Configuration Guidelines and Details sis \cantag\Levatweb\Sertpte eprserven You can use the scripting tol to stop, stat, or restart all conigured servers including SAS Web Application Server, SAS JMS Broker, SAS Cache Locator, or SAS Web Server. :\sas\cantsp\Leeatueb\Sersptseppserver\appervcantig-crd stop ESas\Cantag\Lerawweb\Serspts apsserver\appsrveontig-end start EASAS\Centig\leva\web\Serapts\apeserver\appsrvconeipsced 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 Applic tion Server Instance(s) Host machine [deskiop-10 Port |8082, 8443, Server Name |SASServer! Configuration directory | C:\SASIConfgiLevT\WeblWebAppServeriSASServert_ Log directory | C:\SAS\ConfigiLevt\Web\WebAppServeriSASServert_tNlogs ‘SASWeblnfrastructurePlatformServices9.4 ‘SASWeblnfrastucturePlalformApplicalions9.4 'SASWIPAGMin9.4 SASWIPResources9.4 ‘SASStoreeProcess9.4 ‘SASWorkllow®.4 ‘SASContentServer9.4 ‘SASPrincipalServices9.4 ‘SASIdentiyServices94 ‘SASAuthorizationServices9.4 SASTemplateEcHtor9 4 'SASPermissionManager9.4 ‘SASFlexThemesd.7M3 ‘SASThemeDesignerd. 7M3ForFlex ‘SASThemes9.4. ‘SASDeploymentBackup9.4 ‘SASBackupManager®.4 CClusterable Web Applications Non-clusterable Web Applications Windows Service [SAS [Config-Lov!] SASSorvort_1 « WobAppSorvor ‘Check the status ofthe running Web Application Server Validation stePs Windows Service : SAS [Config-Lev!] SASServer'_1 - WebAppServer Host machine [deskiop-10 Port | 9082, 9443, ‘Server Name |SASSorvertt Configuration directory | C:\SAS\ConfigiLevt\WablWabAppServeriSASServertt_t Log directory | C:\SAS\ConfigiLevT\WeblWebAppServeriSASServerit_Nogs ‘SASEntorprisoMiner15.1, ‘SASForecastServert5.1 ‘SASContextualAnalysie15.+ ‘SASModelManagert4.2 ‘SASTextAnalyticsAPI15.1 'SASTewAnalyticsServices15.1 ‘SASTimeSeriesStudioMidTier15.1 CClusterable Wob Applications Non-clusterable Web Applications Windows Service |SAS [Confg-Lev'] SASSorvert1_1 - WebAppServer| ‘Check the staius of he running Web Application Server Windows Service : SAS [Config.Levt] SASServerit_1- WebAppServer Host machine |deskiop-10 Port 9182, 9643 Server Name |SASServer2 Validation steps {le:11C:/SASiConfigiLev'iDacuments/instructons Nm 1208 ‘1772020 Configuration Guidelines and Details Configuration directory (CASAS\ConfighLeviiWebiWebAppServer'SASServert2_1 Log directory (CASASIConfigL eviWeb\WebAppServeriSASServert2_Nogs Clusterable Web Applications ‘SearchinterfacstoSASContent3.6 ‘SASVisualAnalytiesHub7 4 ‘SASVisualAnalyticsServices? 4 'SASVisualAnalyticsExplorer7 4 'SASVisualAnalyticsDesigner7 4 ‘SASVisualAnalytesGraphBullder?.4 'SASVisualAnalyticsViewer? 4 ‘SASVisualAnalytcsAdminisrator7.4 ‘SASVisualDalaBulldr?-4 Non-clusterable Web Applications Windows Service ‘SAS [Config-Lev'] SASServert2_1 - WebAppServer Validation steps ‘Check the status ofthe running Web Application Server Windows Sorvice : SAS [Config.Levt] SASServertZ_1 - We Host machine deskiop-10 Port 9282, 9643 ‘Server Name ‘SASServeri3 Configuration directory ‘CASAS\Configl ev WebWebAppServer'SASServert3_t Log directory [CASAS\Configh ev ihWeb\WebAppServer'SASSenvert3_Nogs CClusterable Web Applications + SASDataManagement + SASMicroAnalyicService2.5 Non-clusterable Web Applications Windows Service ‘SAS [Config-Lev1] SASServer13_1 - WebAppServer Validation steps ‘Check the status ofthe running Web Application Server Windows Service : SAS [Config.Lev!] SASServer3_1 = WebApoServer Host machine deskiop-10 Port 3182, 8543 ‘SASServer? Configuration directory (CASAS\ConfiglL ov Web\WabAppServer'SASSorver2_1 Log directory (CASAS\Configh ov tWeb\WebAppServer'SASServer2_Nlogs CClusterable Web Applications ‘SASEnvironmentNigrMidTier2.5 'SASSecurityAdminNodule2 3 SASLIneage3.2 'SASWebDoC8.4 ‘SASEnvironmentNMgrLibraryMod2.1 ‘SASServerModule2.1 + SASUsorMedule2.2 + SASSIudioMidTe3. 8 Non-clusterable Web Applications Windows Service ‘SAS [Config-Lev1] SASServer2_1 - WebAppServer Check the status of the running Web Application Server Valdation $tePS Windows Service : SAS [Config-Lev!] SASServer2_1 - WebAppServer Host machine |deskiop-10 Port |a682, 9043, Server Name |SASServer7 Configuration directory | C:\SAS\ConfigiLevWeblWebAppServeriSASServer7_t Log directory |C:\SAS\ConfigiLov!\WabiWobAppSarvor'SASSorver7_‘Nlogs CGlusterable Web Applications + SASDecisionManagerCommon3.2 + SASBusinossRulesWebManager32 {le:13C:/SASIConfighLev'iDocuments/instructons.himl 1328 si772020 Configuration Guidelines and Details Non-clusterable Web Applications | ‘Windows Service |SAS [Confg-Lev'] SASServer7_1 - WebdAppServer ‘Check the status ofthe running Web Application Server Validation steP® Windows Service : SAS [Config-Lev!] SASServer?_1 - WebAppServer Host machine [deskiop-10 Port 8782, 9143, Server Name |SASServers Configuration directory |C:\SAS\ConfgiLevt\WebiWebAppServeriSASServer®_t Log directory | C:\SAS\ConfigiLevt\Wab\WabAppServeriSASServer8_t\logs CClusterable Web Applications | + SASForecastAnalystWorkbenchS.3 Non-clusterable Web Applications Windows Service |SAS [Confg-Lev'] SASServer@_1 - WebAppServer ‘Check the status ofthe running Web Application Server: Validation $t@P$ Windows Service : SAS [Config-Lev!] SASSorvor@_1 - WebAppServor Configuring SAS JMS Broker ‘The SAS Deployment Wizard installs and configutes SAS JMS broker as a standalone server in SAS 8.4. Host machine | desktop-10 Port | 61616 IMX Port | 11099 Configuration directory | CASAS\ConfiglLeviiWeblacivemg Log directory | C\SAS\GonfigiLevTlWeblactivemaidata Windows Service | SAS [Confg-Levt] JMS Broker on port 1616 eck the slau ofthe running JMS broker ‘Windows Service : SAS [Config-Levt] JMS Broker on port 61616 Validation steps SAS Web Applications SAS Themes Validation SAS Themes are used by SAS theme-enabled web applications. Ifyou goto the logon screen forthe Portal ar Web Report Studio ‘steps and see mages then SAS Themes are working properly. SAS Environment Manager Mid-Tier + CASASIConfolLaviWebiLogs\SASServar?_1\SASEnvronmentMarMigTir2.og Log ‘ile For more detas about how to modi your ag format and to ee what logging etal, see “Administering Logging for SAS Web Applications” inthe SAS Itligenco Platform: Middlo-Ter Administration Guide at hifalssiapon. ss com 4admin stalin SAS Security Administration Module Note This module is part of SAS Environment Manager + CASASIConfolLevi\Webll ogs\SASServer?_11SASSecuriyAdminModule?.3 log Log file For more details about how to modity your log frat and fo see whet logging entails, see “Administering Logging for SAS Web Applications” in the SAS intelgence Platform: Midae-Trr Administration Guide at hig lisupparl sas, com/94administaion fle: 11C:/SASIConfigiLev'iDocuments/instructons hl 1408 ‘i772020 Configuration Guidelines and Details SAS Environment Manager User Module Note This module is part of SAS Environment Manager + CASAS\ConfgiLovt\WeblLogs\SASServer? 11SASUserModule2 2.109 Log file For more details about how to modty your lag format and to see what logging entails, see “Administering Logging for SAS Web Applications” in he SAS inteligence Platform: Midale-Trer Administration Guide at hip lisupoart sas, com/S4administration, SAS Environment Manager Library Module Note This module is part of SAS Environment Menager dog” “ssSiconflLauiiebi ogsISASSunvar? 1SASEnironmentMd bran Mad? tog og file For more details about how to modty your log format and to see what logging entails, see “Administering Logging for SAS Web Applications" in the SAS Ineligence Platform: Middle-Tler Administration Gulde ath risas.com/S4administration SAS Environment Manager Server Module [Note This module s part of SAS Environment Manager + CASAS\GonfollevilWebil gsiSASServer? 11SASServerModule2.{ log Log file For more details about how to modty your log format and to see what logging entails, se0 “Administering Logging or SAS Web Applications" in the SAS Inteligence Platform: Middle-Tler Administration Gurde at hii. suppor sas.com/Gasdministration ‘SAS Web Infrastructure Platform Log directory C:ASAS\GonfilLev1iWebWLogs\SASServer ti 4. Access the Comment Service fation steps 2, Log inusing the DESKTOP. 1O'sasdemo credentials provided during confguraton 3. Verify that you ean adda comment SAS Studio Mid-Tier URL | Http idoskton-10:82/SASStudio + CASASIConflLevilWeblLogs\SASServer?_11SASStusioMidTier3.8 log Log file For more details about tow to madly your lag format and ta see what logging entails, see “Administering Logging for SAS Web Applications" inthe SAS inteligence Platform: Midle-Tier Administration Guide at ia Jsupoart sas. com/S4administalon Validation 1. Access the URL provided above. ‘steps 2. Login using the DESKTOP-TO\sasdema credentials provided during configuration Notes: + Ifyou have a CAS server deployed and would lke to configure SAS Stuclo to connect by default, you can set the CASHOST and CASPORT ‘options in @ SAS autoexec file. This can be done on a per user basis by using the "Est Autoexec File” menu item on the application options ‘menu in SAS Studio. This can also be dane for all users by adding ito the autoexec forthe SAS workspace server. For SAS Studie Mid- Ter, this can be adaad tothe autoexee_usermods.sas fle for your deployment (for example Confgl.ev \SASApplWorkspaceServeriappserver_autoexec_usermods sas for Windows or configlLav/SASAppWerkspaceServeriauloexec_asermods. Sas fo” Unk). SAS Content Server {le:f1C:/SASIConfigiLev'iDacuments/instructons.himl 1528 1772020 Configuration Guidelines and Details Log fle | CASAS\ConfigL ev iWeblLogs\SASServert_TISASContentServerd4 log Inthe SAS Management Console, on the Plug-ins tab, selec "s" to expand the Server Manager node. Highlight the SAS Content Server Fight mouse click this sarver and select Validate Login using valid credentials for an unrestricted user defined in the SAS Metadata Serve. 1 2 Validation steps. 3 4 5, You should see a Validation Successful message, SAS Stored Process Web Application URL tio dasktop-10:82/SASStoredPracessida Log fle CASAS\ConfiglLovilWeblLogsiSASSenvert 1\SASStoredProcess9.4.og 4. Access the URL provided above. 2. Lag in using the DESKTOP- Oisasdemo credentials provided during configuration. Validation steps 3. On the Welcome page, click the "Sample: Server Tes" link to access the custom input form for this sample stored process. 4. Select an output format and ODS siyle or accept the default values, and cick the "Display SAS Output” button. 5. The output from the stored process is @ simple massage thal the server processed the request. SAS Web Administration Console URL bitodideskton-A0A2/SASAdmin Log file C:iSAS\ConfiolLevilWebil ogs\SASSanert 1\SASAdmin® 40g 4. Access the URL provided above. 2 Log in using the sasadm@saspw credentials provided during configuration, 3. On tne main page, select the “Users” node. 4. Verify that "sasad" appears inthe “System Users" section inthe right frame. lation steps SAS Visual Analytics Services Service SAS Visual Analytics Transport Service + CASAS\ConfolLevt\Webilogs\SASServer12_1$ASVisualAnalyicsTransport7 log + CASASIConfoiLevtiWobiLogsiSASServert2" NSASLASRAuthorzation” 40g For more details about how to modify your log format and to see what logging entails, s00 "Administering Logging for SAS Web Applications” in the SAS intelligence Platform: Midle-Tier Adminisraion Guide a ip supnor\ sas. com/S4adm nisraion, Notes: ‘+ The SAS Anonymous Web User has been configured for your environment, Currently SAS Visual Analytics Services does not have Guest ‘Access enabled. For mare information on how to support Guest Access, see the lope "Supporting Guest Accass" in the SAS Visual Analytics: ‘Administration Guido avalabe at hitp'support sas com/documentaionionlinedocivalindex html + The following URLs have been added tothe configuration property ‘sas.web.caps knownFiosts' on the SAS Application Infrastructure node: ® hitpopnsta.sas.com! © hitpslopnstb sas com! © httpslopnst.sas.com! SAS Visual Analytics Hub URL _bilodideskton-10:82/SASVievatAnal lesHub + CASAS\Configll evt\Webll agsiSASServert?._11SASVisualAnalytesHub7 4 log Log file For more details about tow te mody your lag format and to see what logging entails, see “Administering Logging or SAS Web Applications” inthe SAS infellgence Platform: Midale-Tier Administration Guide at iia lisypport sas com/94administallon Validation ‘steps 1. Access the URL provided above. 2 Login using the DESKTOP-1O\easdemo credentials provided during configuration {le:11C:/SASIConfigiLev'iDocuments/instructons.himl 1628 sr772020 Configuration Guidelines and Details Notes: + The SAS Anonymous Web User has been configured for your environment, Currently SAS Home does not have Guest Access enabled. For ‘more infermation on how to support Guest Access, see the topic “Supporting Guest Access" in the SAS Visual Analytics: Administration Guide avaliable at http support sas.com/socumertaton/ontinedoclvalindex hil SAS Visual Analytics Explorer For more details about how to modly your lag format and to see what logging entails, see “Administering Logging for SAS Web Applications" inthe SAS inteligence Platform: Midale-Tr Administration Guide at ia Jsupoart sas com/S4administalon. Validation For a brat validation sequence, see “Validate Your SAS Visual Analytics Deployment*in the SAS Visual Analytics: Installation and ‘steps Configuration Guide (Non-dlsirbuted SAS LAS) avallable a bipJeupport sas comidacumentalion/aninedaeWvalindx hin. SAS Visual Analytics Designer URL btindlidaskton-10:82/SASVisualAnalyticsDesigner + CASASIGonfollevilWobllogsiSASServert2 1\SASVisualAnalytcsDesioner7 40g 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” inthe SAS Infeligence Platform: Middle Administration Guide at his lisupnart sas com/94administration. Validation For a bret validation sequence, see "Validate Your SAS Visual Analytics Deployment” in the SAS Visual Analytics: Installation and ‘steps Configuration Guide (Non-dstrbuted SAS LASR) avaliable at hitp/unport sax com/documentation/oninedoc!valind him SAS Visual Analytics Viewer URL http ldosktop-10:82/SA8VisualAnalyties CASAS\ConfiglL ev1iWeb\Lo Log file For more details about how to modly your lag format and to see what logging entails, see “Administering Logging for SAS Web Applications” inthe SAS infoligence Platform: Midale-Tier Administration Guide at iia lisupport sas, com/94administatlon Validation For a bref validation sequence, see “Validate Your SAS Visual Analytics Deployment*in the SAS Visual Analytics: Installation and ‘steps Configuration Guide (Non-dsirbutod SAS LAS) avallable at lp Jeupport sas com/dacumentallon/onlinedaeivalindax hin. Notes: + The SAS Anonymous Web User has been configured for your environment. Currently SAS Visual Analytics Repot Viewer does nat have Guest ‘Access enabled. For more information on how ta support Guest Access, see the topic "Supporting Guest Access" in the SAS Visual Analytics: ‘Administration Guide available at hitplsupport sas comidocumentalion/oninedocivalinex hil SAS Visual Data Builder URL bt iNdesktop-10:82/SASVisualDataBullder + CASASIConfolLevilWeblLagsiSASServert?._ 1\SASVisualDataBullder74.og Log directory For more details about how to modly your log format and to see what logging entails, see “Administering Logging for SAS Web “Applications” inthe SAS infelgence Platform: Midale-Tiar Administration Guide at hia isupparl sas com/94administalion Validation Fora brie validation sequence, see “Validate Your SAS Visual Analytics Deployment” in te SAS Visual Analytics: Installation and {le:13C:/SASIConfigiLev'iDocuments/instructons hm 1728 1772020 Configuration Guidelines and Details ‘steps Configuration Guide (Non-dstrbuted SAS LASR) available at hitplisunport ss com/documentation/oninedocivalindsx him SAS Visual Analytics Graph Builder + CASASIConfiglLevilWeblLogs\SASServert2_1\SASVisualAnalyticsGraphBulder7.4 log Log file For more details about tow to modly your lag format and to see what logging entails, see “Administering Logging or SAS Web Applications" inthe SAS inteligence Platform: Middle-Ter Administration Guide at ia Jsupoart sas com/S4administralon Validation For a bref validation sequence, see “Validate Your SAS Visual Analytics Deployment” in the SAS Visual Analytics: Installation and ‘steps Configuration Guide (Non-dsirbuted SAS LASR) avallable a lp Jauport sas com/dacsumentallon/alinedaeWvalind hin. SAS Visual Analytics Administrator URL btigslidaskton-10:82/SASV'sualAnaycsAdministrator + CASASIConfgiLevt\WebiLogs\SASServert2.\SASVisualAnalytesAdminitrator Jog Log directory For more details about how to modly your log format and to see what logging ental, st Applications” inthe SAS Infellgence Platform: Midle-Tler Administration Guide at hts “Administering Logging for SAS Web upnort sas.com/Sdadminisvation Validation For a bret validation sequence, see “Validate Your SAS Visual Analytics Deployment” in the SAS Visual Analytics: Installation and ‘steps Configuration Guide (Non-dlsirbuted SAS LASR) avaliable at hitp/support sas. com/documentation/oninedativalindex him SAS Flex Application Themes Validation SAS Flox Application Themes are used by SAS web applications that are displayed with the Adobe Flash Player. I these applications ‘stops correctly display coors, graphics, and fonts, then the SAS Flex Application Themes have beon successful installed, Validation SAS Theme Designer for Flex is accessible from ho teskto0s ia ‘stops In order to use this application, you must be a member ofthe role "Theme Designer for Flex: Administration” ‘SAS Micro Analytic Service Rest API Web hiiJideskton-10:82/SASMicroAna)ticServicaltost! ‘Service Note: This nk wil take you fo 8 page with a “Status 401 - Full authentication is required to access this resource error’, The fink is URL here for your reference so that you can incorporate into applications that will access the SAS Micro Analytic Servce rest interface. ISASSewerI3 TNSASWicroAnalyleService? 510g Log te ISASSorvert3_11SASMicroAnalylieServiceCore? 5.log For more details about how to modly your lag format and to see what logging entails, see “Administering Logging for SAS Web ‘Applications” inthe SAS intoligence Platform: Milo. Tir Administration Guide at hia lisupoart sas, com/a4adminisvalion The following steps must be performed on every Middle Tier Node machine where SAS Micro Analytic Service Rest API has been seployed on an AIX operating system. 1. Create the following symbolic inks: ® libdiic-1.4.80 > libdtic-1 4.8 Pree 2 libdtssye-1.3.90 > Ibdissys-1 3.0 Example: {ed /Wab/WebAppServer/SASServer!3_#/sas_webapps/sas.microanalyeservice.warWEB-INFIibiloadib Ins ibofle-1.4.alibdfic-1 4.30 In 5 Mbatesys-1.3. libatssys-1.3.50 2, Restart the SASServer' web application server. Validation ‘steps 1. Verify the following JVM options inthe system environment es, fle: 11C:/SASIConfigiLev'iDocuments/instructons hl 1828 sr772020 Configuration Guidelines and Details ¢ Java maximum thread stack size: -Xss512k ® (AIK Only) Native operating systom thread stack size: -Xmso8 12k ‘Windows system environment fe locations: ® \WebiWVebAppServeriSASServer!3_#iconfwrapper.cont © /WebiWebAppServer!SASSorvert3_#ibin/setenv sh 2, Aocess the following Web Service URL: hlloi/desktog-10:82'SASMicroAnalyicServiceiindex you encounter problems accessing the URL, please review the logs Isted under the Log ile section, Notes: + Ifyou have specified the locaton ofthe Python executable, the path must be the same on all machines where the SAS Micro Analytic Service Rest API wil be deployed + For more information, See the SAS Micro Analytic Services 2.5: Programming and Administration Guide available at bitousunpor s2s.com/documentatiolnvad.pimas. ‘SAS Data Management Console URL itp idaskton-10:82/SASDataManagement + CASASIConfolLevi\WebiL ogsiSASServert3._1\SASDataManagementlog Log file For more details about how te modify your log format and to see what logging entails, see “Administering Logging or SAS Web Applications” inthe SAS Infeligence Platform: Midale-Tr Administration Guide at iia lisupport sas com/94administaion Make sure to ad the SAS First User ora valid user to the following SAS Data Management user group which is automaticaly created for you: Data Management Executives. This wil give the user view capabilies only. For instuctions about adding SAS users to a Validation group, soe "Adjusl Group of Role Memborshi. stops 4. Access the URL provided above. 2 Login using the DESKTOP-1O\sasdemo credentials provided during configuration SAS Lineage Mid-Tier 10:82/SAS\ ineage + CASASIConfiolLevilWeblL ogsiSASServer?_11SASLineage3 2.09 For more details about how to mody your log format and fo see what logging entails, see “Administering Logging or SAS Web “Applications” inthe SAS intellgence Platform: Midale-Tier Administration Guide at Nipisupport sas com/94administaion 1. Access the URL. provided above. 2. Login using the DESKTOP-10\sasdema credentials provided during configuration ‘Search Interface to SAS Content URL biipilidaskton-10.82/SASSearchService + CASASIConfiiLovilWeblLogsISASServerl2_ 1\SASSearchService log Log file 1. Access the sample URL, hio:/desktop-10:62/SASSearchServiceirest 2 Log in using valid credentials defined in the SAS Metadata Server. 3. Very that a Ist of XMLLJSON links is cisplayed in the browser or downloaded as a file If fle is downloaded, open it in text ist of resourceslinks is returned, {le:11C:/SASIConfigiLev'iDocuments/instructons.himl 1928 1772020 Notes: Configuration Guidelines and Details 4, ityou are testing Search through some client application (e.g. SAS Visual Analytics Hub) and if Search Interface to SAS Content has been installed ina separate instalation, please restart the Web Application Server having dependent Web Appiations (e.g SAS Visual Analytics Hub) to ensure they register the presence of newly added wed application, + For instructions about integrating Search Interface to SAS Content 3.8 with internet browsers and other search engines, refer tothe document Integrating Search Interface to SAS Content 3.6, 8 isuppor sas. comidocumentalioninstalcenter!94/ndex him ‘SAS Deployment Backup and Recovery Tool Purpose and ‘Scope Log directory Configuration Validation stops 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 les ina SAS deployment. The SAS. Deployment Backup and Recovery Too! does not backup al files inthe SAS configuration directory. No files in the SAS installation directory are backed up. The SAS Deplayment Backup and Recovery Tool does not take the place of aperating system and fle system backups. Performing regular backups ofthe SAS system is an important part of administering the SAS 9.4 Inteligence Platform configuration. Backups taken by the SAS Deployment Backup and Recovery Too! should be synchronized wih operating system and fle system backups to ensure tha fles 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 Inteligence Platform: System Administration Guide at bia lisuppor sas.com9dadministration. 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 isnot supported. Recovery of data must be invoked using the command tne utties provided by SAS Deployment Backup and Recovery Too For more information, see tha SAS Intoligence Platoon: System Administration Guido at hfted/supgan sas com/Sdadminisvation + CASAS\Confgl evt\Webll gsiSASServert_1\SASDeploymentBackup9.4 log + A central vault location was not specified during installation and configuration. Backups will be stored ina local vaut + For each ter the path for the local vaults: SAS-confguration-directoy/Lev'Backup/Vault + Backups are retained for 30 days and purged automatically after this perod, + Te SAS Deployment Backup ana Recovery Tools configured to run scheduled backup each Sunday at 1:00 a.m, local tine. + S00 "About tho Doployment Backup and Recovery Toot in the soe tho SAS Inteligence Platform: System Administration Guide at hit Isupportsas.comS4zdministation to learn what s and is not backed up by the SAS Deploymar ‘madfying the backup configuration Backup and Recovery Too! and fr information about Launch the SAS Environment Manager Web Console LLagin using he sasacm@saspw credentals you spectied during configuration Click Administration in tie menu bar to open the SAS Envonment Manager Administration. Open the SAS Backup Manager by clicking the Side Menu icon in the SAS Environment Manager banner and select SAS Backup Manager, The SAS Sackup Manager appears, Note: The SAS Backup Manager might take several minutes to load asi discovers the assets that are available for backup inthe deployment. Inthe SAS Backup Manager, click Start Backup. Vorty thatthe backup complates succossfuly + For more information about the SAS Deployment Backup Tool, see the SAS Infligence Platform: System Adminstration Guide al bits port sas. com/ administration. + Best practices for oacking up and restoring your SAS content can be found in the SAS Inteligence Platform: System Administration Guide at hllpU/support sas.comSdadministation, ‘SAS Forecast Analyst Workbench URL _httpildeskiog-10:821SASForacastanalysiWorkbench Log ft {le:13C:/SASIConfigiLev'iDocuments/instructons.himl + CASASIConfojl evtlWeblLogsiSASServerS_1iSASForecastAnalystWorkbench5.3.log For mare details about how to malty your log format and to see what logging entails, see Logging for SAS Web Appl sr772020 Configuration Guidelines and Details In the "SAS 9.4 Intelligence Platform: Middle-Tier Administration Guide” under Adminstration Documentation at the SAS. 1. Access SAS Forecast Analyst Workbench Mid-Ter using the URL, above. 2. Sign in using the DESKTOP 1O\sasdemo credentials provided during configuration Validation 3 Te web application wil open. You wil most likely see an error message related tothe database, i inal jobs are not ‘Maps __exeeted, Instructions for executing the required jobs may be found inthe referenced documentation, Closing the eror tlalog results in an automate sign out 4. Ifyou were able to signin, even withthe error message, the web application is correct installed and configured. 5. Sign out, if necessary, and close your browser. ‘Administrator's Refer lo the SAS Forecast Analyst Workbench Mid-Tor Administrato’s Guide for more configuration information. ‘Guide Username: FAWDOG (case-sensitive). Password: UserDoc (case-sensitive), + The SAS Demo User has been assigned the ID, DESKTOP-10\sasdemo, and assigned sufficient authorizations to assist you in validating this product and, perhaps, others. You may consider deleting this user fo increase the security of your installalion after your validation efforts complete SAS Decision Manager ‘URL | Mledidesidon-10:8215ASDecisionManagar httndesikton10:82/SAS DecisionManager/DecisionBuller Logfiles | + ciSAS\GonfollevtlWebil ogs\SASServer7_1\SASDecMgrShall.2log ‘The SAS Deployment Wizard (SDW) does not create application users by default The SAS Administrator must create users in Pre-validation | the SAS Management Console withthe appropriate group and role pormissions. Ifthe sasdemo user already exists, you can ‘stops | add tho user to one or mora ofthe user groups in SAS Management Consale. For information about how to configure users, {70UpS and roles, see the SAS Decision Manager 3.2: Administrators Guid. Perform the quick slat tuloral in te Gelling Started section of the SAS Decision Manager 2.2: User's Guide to validate your Validation | installation, ‘stops | Note: The quick start tutorial includes stops to validate functionaliy for SAS Decision Manager, Decision Builder, SAS Mode! Manager, and SAS Business Rules Manager. ‘SAS Decision Manager includes the functonality of SAS Decsion Manager, SAS Model Manager, and SAS Business Rules Documentation | Manager. For more information, see the SAS Decision Manager 3.2: Administrator's Guide. Al of the documentation is available al the following URL: hitoJ/support sas. comidocu ‘SAS Decision Manager Common Mid-Tier for Decision Manager Host | dosktop-10 Logfiles | + SASAS\GonfollavtiWebll ops\SASServer7_1SASDacMorShalls 209 + CASAS\ConfolLevilWebiLogsiSASServer?_NSASDecMgrComman3.2 log ‘SAS Model Manager Mid-Tier ‘URL [htlo:J/desitop-10:82/SASDecisionManager Log Mle | CSAS\Configl avilWebil ogsiSASServer!t_TSASModaManagarié.2 ag The SAS Deploymant Wizard (SDW) does not create application users by default The SAS Adminstator must create users in reevalidation | the SAS Management Console withthe appropriate group and role permissions. Ifthe sasdemo usor already exists, you can ‘stops | add the user to one or more ofthe user groups in SAS Management Console. For information about how fo configure users, r0UpS and roles, see tha SAS Model Manager 14.2: Adminisirator's Gulde. Perform the quickstart tuloral in te Geting Stared section of the SAS Model Manager 14.2: User's Guide to valiate your Validation | installation. steps | Note: If you have completed the vadation steps for SAS Decision Manager, then you do not need to complete any additonal validation stops for SAS Model Manager. For more information, see the SAS Model Manager 14.2: Administrators Guide. Allofthe documentation fs available at the following URL: hito:!suppor sas.com/documentatonioniinadacimadelmgth Documentation Notes: fle: 11C:/SASIConfigiLev'iDocuments/instructons hl 21128 ‘i772020 Configuration Guidelines and Details + When restarting the middle-ter server: °° SAS Madel Manager has a dependency on the SAS Conlant Server which provides the interface to DAV that is needed by SAS Model Manager. The SAS Content Server runs as a web application and might be running on a diferent instance ofthe application server than ‘SAS Model Manager. In most cases the star-up ofthe applications is handled properly but if you experience a problem where the DAV Contents not yet available just ensure that SASServer! Is up and running before staring SASServer1! (which is where the SAS Modal Manager WAR files are deployed in a mull-server environment) » You can check to see whether the SAS Content Server is up and running by licking on this link hitpdideskton. $0:89/SASCanteniServeridircontens, sq and logging in withthe SAS Adminstrator user ID and password, + For more information about configuring environments, creating user accounts and general SAS Model Manager administration, see the SAS Modo! Manager 14.2: Administrators Guide. SAS Business Rules Manager Web URL _hiipsideskiop-10:82/SASDecisionManager Logfile CASAS\Cont Tha SAS Deployment Wizard (SOW) doos not create application users by dofaul. The SAS Administrator must croato users in Prewalidation the SAS Management Console with the appropriate group and role permissions. Ifthe sasdemo user already exists, you can ‘steps add the user fo one of more of the user groups in SAS Management Console. For information abaut haw to configure users, ‘groups and roles, see the SAS Business Rules Manager 3.2: Administrators Guide, Perform the quick start tutorial in the Geting Stated section of the SAS Businoss Rules Manager 8.2: User's Guido to validate Validation your installation. ‘stops Note: If you have completed the validation steps for SAS Decision Manager, then you do not need to complete ary additonal Validation slaps for SAS Business Rules Manager. For more information, see the SAS Business Rules Manager 3.2: Administrator's Guide. Alo te documentation is avaliable at Documentation ine folowing URL: binJ/supnort sas comidocumentationfonlinedoetbmy Web Application Custom Content Ifyou wish to add custom conten ino SAS web applications, refer to the ‘Web Application Custom Content” section af the SAS Intaligence Platform: Middle-Tier Administration Guide located at hip /sunaort sas canvadminisilon Analytics SAS Forecast Server ‘SAS Forecast Server Host desktop-10, ‘Access to SAS Forecast Studio tasks by SAS Add-in for Microsoft Office and SAS Entorprise Gul Enabled Repotts are not enabled for environments that are created during a new deployment or a migration. For more information about report configuration including how to deploy the sample reports, see the SAS Forecast Server 15.1: Administrators Guide at bin/support.sas,com/cocumentation/onlinadoct Report administration Use the folowing credentials to access the secure documentation pages + User name: sas. 1 Password: doe + Name: Default °° Description: Forecast Server Default Environment «© Workspace Server: SASApp - Logical Workspace Server Default Environment. ‘© Content Location: C:\SASiConfilL ev \ApaDatalSASForecastSorvertS.1 + The Content Location refers toa path on the server ir. This path must exist on the server tier before SAS Forecast Sorvers used. Soe the Configure Foracasting Environments on the SAS Servar nates below for instructions to create the directory or foloer structure Validation steps + Verity that the SAS Forecast Server status page can be accessed successfully from htpilideskioo: 0 orecastServerSialue. fle: 13C:/SASIConfigiLev'iDocuments/instructons.himl 22128 sr772020 Configuration Guidelines and Details +The SAS Forecast Studio client application can be used to perform additonal validation. To use this application, you must og into SAS Forecast Sludio as a user wih an appropriate role. The available tasks depend on the user’ role Perform the following stops: 1. Complete the configuration instructions under the "Notes" below. 2 Launch the SAS Forecast Studio client by clicking on the Launch link on the SAS Forecast Server status page. 3. When the SAS Foracast Studio login dialog box appears, verify that you can successfully log in Note: If there are any validation errors, check the fllowing logs: 1. SAS Forecast Server applications log flo, SASForecastSarvert5. 1109 2. SAS Web Application Server Wab Application Server’ log fle generated during the configuration of ‘server't. Refer to the Web Application Server's configuration instructions forthe location of these logs. Notes: Configure SAS Forecast Studio Users and Roles: + Create user and product administrator accounts. 1. Create the operating system accounts for the Forecast Server users and administrator. 2. Assaciata the above accounts with metadata identties in SAS Management Console, ‘+ Assign the appropriate roles to the Forecast Server users and administrator accounts Configure Forecasting Environments on the SAS Server: + For anvironmants that were created during configuration or migration: 4. Create the content location onthe appropriate workspace server for each configured environment, 2. Set file system permissions 0 thatthe SAS Forecast Studio users have full access tothe content location ofthe environment. Additional Information: + For more information about the previous tasks and forthe most current installation and configuration information, see the SAS Forecast Server 15:1: Administrator's Guide at ito/sunport sas com/documentalion/oninedooforecast SAS Enterprise Miner Mid-Tier Host machine desktop-10:82 ‘Administrator's Additonal information useful in administering SAS Enterprise Miner can be found inthe SAS Enterprise Miner 16.1 Online Guide documents at hiin//supnor.sas.com 'documentajon/onlinedoc/minevindex him. Post The SAS Administrator must create operating system accounts for the Enterprise Miner users and create metadata identities Installation associated wi those accounts in SAS Management Console, The users must have permissions to open projects on the SAS ‘Steps Application Server used for data mining ‘of more details about how to mocify your log format and to see what logging entails, view the SAS 9.4 Logging Administration and Programming Gu Log ft + Please see the "Very the Installation” documentation at lp /isupport sas.com/dacumentation/caen/amag/69529/H TML defaulviewar htmip0x2xch3muASen0zBrutcoehogt htm, Verily thatthe SAS Enterprise Miner Mi-Tier status page can be accessed successfully from hilnildeskion= SO:BNSASEnterpriselfinerdWS/Stalus, + ifyou experience an “Unable fo Launch the Application” error when connecting Io the SAS Enterprise Miner Server via the browser, please reference hil /supparl sas comfan/47/311 him + default sas-environmentxm is enable for validation through the SAS Enterprise Miner Java Web Start Cent. Launch ‘he SAS Enterprise Miner Java Web Start Client clicking on the Launch link onthe status page To specily and configure your site's custom sas-environmant xml file, sve “Create a SAS Environment File in SAS Enterprise Miner 15.1 ‘Administration and Configuration and Configuring the SAS Envronmont File in SAS 8.4 Inteligence Platform: Middlo-Tier ‘Administration Guide, Fourth Eaftion.” This is avaliable at hips l/ga.documen socselld-emag&docsetTargat=n1j'Stanahbjbin m&b407pb6ihimBdocsel Verso Validation ‘steps: 6, 1locale-en, Note: If there are any validation arors, check te lg file mentioned above. Notes: Ploase rfer to the SAS Enterprise Miner Administration and Configuration guide to: Define SAS Enterprise Miner Users and Roles + Configure SAS Enterprise Miner sas-envronments.xnl on the SAS Server fle: 11C:/SASIConfigiLev'iDocuments/instructons hl 23128 i772020 Configuration Guidelines and Details SAS Text Miner Client ‘Administrator's | Adéitonal information useful in administering SAS Text Miner can be found in the SAS Text Miner 15.1 Online documents at Guide hipu/sun midacumentation/onlinedociixtminerindex Him| ‘The post.nstallation step for Text Miner is needed on Windows servers forthe ‘htmfter macro. No post installation step is. needed for ttrfitr on Unix servers. Enable the XCMD Option ‘SAS Text Miner inluges & macro called %-TMFILTER. When running on Windows, the ~xcme option must be setin any SAS Session sat up la run the macro, For mast desktop installations of SAS, this option wil already be set and 2

You might also like