0% found this document useful (0 votes)
120 views27 pages

Lev2 SASInstructions

instrucr 2

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
0% found this document useful (0 votes)
120 views27 pages

Lev2 SASInstructions

instrucr 2

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/ 27
1516/2020 Configuration Guidelines and Detals =_ a8 ‘desktop-10 Configuration Guidelines and Details for Overview Warnings and Notices Solulon Data Servers ‘SAS Deployment Tester Server (Operating System Services Scheduling Server 9, SAS Bi Lineage Scheduling Server ‘SAS Visual Anadis 11. SAS Information Retrieval Studio 18. SAS Environment Manager Agent Configuration 46. SAS Enviconment Manager Enablement Kil Server 17, SAS Web Server Configuration Web Appicaion Server 23, Obiaining Additonal Information Warnings and Notices Tre following issues occured tring the automated porion of your coniguation and must be adéessed bear procescng ‘+ Some of the clients in your environment may need access tothe SASIGRAPH Java applets to view graphical outout generated by SAS processes. Iso, add the APPLETLOC option to the sasv9_usermads.clg fle locates in each SAS Application Server context directory Specifying the location fo be used in generating graphical output. APPLETLOC should point to a network accessible copy of the SASIGRAPH sava applets. ‘Since your deployment Includes the SAS Web Infrastructure Platform, the applets can be made avallable via -sopLeTLOce"hetp:/ web serverport/sasweb graph The web server parti typically 80 an 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 ine tothe sasv9_usermods.cg fle untl the SAS midle tie is configured. After updating the fle, restart the object spawner and validate your Workspace, Pooled Workspace, and the Stored Process servars again + You indicated that security policies could be modifed by the SAS Deployment Wizard. As a resul, the user DESKTOP-1O\sasdemo was granted the local security palcy Log en as a batch job (SeBatchLogonRight). Ths policy allows a user lo be logged on by means of abaich- {Queue faclty and is required when tis account is Used with SASApp2 - Workspace Server, ‘The policy will tako effect the next ime DESKTOP-10\sasdomo authenticates against the operating system. Therefore, f DESKTOP- ‘Disssdomo is currently logged onto the system, a reboot will be needed for this policy to take affect. ‘+ SAS Web Applications are being protected by a secu fiter that preven linking from unauthorized hosts. The security iter is customizable. For further information on customizing this filter, refer a the SAS 9.4 Infeligence Platform Middle-Tier Administration Guide, found at lp leuppor.sa8.comidocumentaion/onl SAS Management Console ‘SAS Managemen! Console is required to complete many ofthe folowing stops. Shortcut Programs > SAS > SAS Management Cansole 9.4 UserID SAS Administrator user ID Password Enter the password you created in the SAS Deployment Wizard fle: 11C:/SASIConfighLev2:Dacuments/instructons.hml aor ‘612020 Contguration Guceines and Details SAS Application Servers ‘SASMeta? - Metadata Server Host mactient desktop-10 Port 9562 CASASIConfilLevaiLogs For more details about the inal logging configuration and how to modify it, see “Administering Logging for SAS Servers" in the SAS Inteligence Platform: System Administration Guide al htpulsunpor.sas.com/Sdadministraion. Execution Windows service ‘ype SAS [Config-Lov2] SASMota2 - Metadata Server Shortcuts Programs > SAS > Configuration > Config - Lev2. Log directory Notes: + The metadata server is configured to perform unassisted matadala server backups. The backuns are performed every day at a.m. except an ‘Sunday and stored in the "C:\SASIConfighLev2\SASMetalMetadalaServer\Backups” directory. Backupe are retained for seven days, To learn about the metadata server backup facily, see “Backing Up and Recovering the SAS Metadata Server" in the SAS Inteligence Platform: System ‘Administration Guide at hitplIsupportsas.con/S4adminstration. + The metadata server fs configured to Send an alert e-mail message to rian. [email protected] in the event of a system, backup, or recovery failure. You can test that the aleterral notfication subsystem is configured propetty by opening the Properties sheet for the ace metadata server in the SAS Management Console Metadala Manager and sending a tesi message. I the system is configured properly, you vill receive a tst e-mail rom SASMeta2 - Metadata Server Config - Lev2 . If you wart to change your alert e-mail ‘plions, see the section "Managing Alert E-mail Options forthe SAS Meladala Server" inthe chap "Metadala Server Configuralon Tasks" of the SAS Inteligence Platform: Systom Administration Guid at btgulsugpor.sas.com/sdadministration. ‘SASApp2 - Connect Server Host machine Port 7552 CASASIConfgiLev2iLogs For more details about the initial logging configuration and how to modily it, see “Administering Logging for SAS Servers" in he SAS Inteligence Platform: Systom Administration Guide at bla lisupoart sas. com/Séadministalion. esktop-10 Log directory +. In the SAS Management Console, onthe Plugsins tab, select “+” to expand the Server Manager node. 2. Expand SASApp2 3. Expand SASApp2 - Logical Connect Server Validation 4, Highlight the SASApp? - Connect Server. ‘stops 6. Right mouse cick this server and select Validate (you can enter DESKTOP. 10\sasdomo or the SAS Spawned Servers account Tor the user ID). You should see a Validation Successful message. NOTE: To successtuly validate a CONNECT sorver, the associated spanner must be configured with option Signon Scripts Allowed sotto Yes ‘SASApp2 - OLAP Server Host mmachatt doskop-10 Port 5452 Log CASAS\ConfoLa a dreckgl For more dla abot terial ogaing configuration an hw to mod se “Administering Logging for SAS Severs" n the SAS Inteligence Platform: System Administration Guide a hiplsunpor. sas com/adminisration 1. Inthe SAS Management Console, on the Plug-ins tab, select "+" Lo expand the Server Manager node. Validation 2. Expand SASApp2. stops 3. Highlight the SASApp2 - Logical OLAP Server. 4, Right mouse cick this server and select Validate. You should see a Validation Successful meseage, Execution Windows service type SAS [Config-Lev2] SASApp? - OLAP Server Shortcuts Programs > SAS > Configuraion > Coniig- Lev2 fl: f1C:/SASIConfighLev2:Dacuments/instructons.himl 2n7 1516/2020 Configuration Guidelines and Details ‘SASApp2 - Stored Process Server Host machine dosktop-10 Port 8602 Log directory C:iSAS\Gon‘ilLev2ilogs 1. Inthe SAS Management Console, on the Plugeins tab, select“ to expand the Server Manager node. 2, Expand SASApp2, 3. Highligh the SASAop2 - Logical Slored Process Server. 4 Right mouse click ts server and eoloct Validate, You should see a Validation Successful message ‘SASApp2 - Workspace Server Host machine Port 2592 ‘GASASICanfolLev2iLo9s For more details about the ital logging configuration and how to modily it, see "Administering Logging for SAS Servers" in the SAS. Inteligence Platform: System Administration Guide at hito/su osktop-10 Log directory 1. In the SAS Management Console, onthe Plug-ins tab, select" to expand the Server Manager node. 2 Expand SASApp2 3. Highlight the SASApp2 - Logical Workspace Server. 4. Right mouse click his server and select Validate (you can enter DESKTOP-10\sasdomo ar the SAS Spawned Servers account forthe user ID). You should see a Validation Successful message. + The C:ASAS\ConfgiLev2\Logs directory is intended to serve as a placeholder for workspace server logs. Workspace server logs may be directed to ths directory n te event thal your SAS or IT administalor enables logging. The following defaul atfibules are associated withthe Logs directory: ® Universal read, write or execute access is disabled for the directory in order to comply with default installation secur requirements © Execution of a workspace server does not populate the Logs directory © The Logs directory serves asa placeholder should you enable logging for workspace servers Enabling workspace server logging should be carefuly considered, due to the proliferation of workspace server logs, as well as the requirement te grant universal write access to the Logs drectoy. To enable workspace server logging, perform the folowing sleps: °> Enable read, mite and execute access tothe Logs directory © Modify the workspace server logcontigxml fo enable the desired levels of logging © Altematively, enable the lagcontig race.xm logging file to capture workspace Server dagnesticlogoing SAS BI Report Services Workspace Configuration Name ="SASApp2 -wrstemp" 4. In SAS Management Console, on the Plugsins tab, select the "s" to expand the Data Library Manager node. 2 Select "+" to expand Librares. 3. Seloct the brary listed above. 4. Right mouse click ths Horary and solect Properties. 5. Click the Options tab and locate the path to the library in the Selected itams text box. Query Cache Review the documentation provided to determine it permissions need to be modified for the library or ditectory to which te library Library points 1. For details, view the hp support sas. com/@4administraton and refer to the document called SAS Intelligence Platform 9.4: Web Application Administration Guide. 2 See the section called Improving the Performance of SAS Web Report Studio. 3. This section will contain a Ist of Suggestions for Improving the Performance of SAS Web Report Studio, Goto the information tiled “Using the Query Cache” 4. Refer tothe subsection called Manage Host Access to the Query Cache Directory or information regarding permissions. Distribution | Name = Library "SASApp2 - wrscis” 4. Ip SAS Management Console, on the Plug-ins tab, select the " 2 Select "=" to expand Librares. 3, Select the brary Iisted above. 4, Right mouse click this brary and select Properties, fle: 11C:/SASiConfighLev2:Dacuments/instructons.himl sor to expand the Data Library Manager node. 1516/2020 Configuration Guidelines and Details 5. Click the Options tab and locate the path tothe library in the Selected items text box. Review the documentation provided to determine if permissions need to be madiied forthe library o directory to which the brary points. 1. For details, view the hip support sas.com/S4administraton and refer to the document called SAS Intaligence Platform 9.4: Web Application Administration Guide. 2 See the section called Pre-generated Reports From SAS Web Report Studio. 3, Refer tothe subsection called Verifying Permissions for the Distribution Library for information regarding permissions. In SAS Management Console, onthe Plug-ins tab, select "+" lo expand the Data Library Manager node. Verily the libraries named above are listed under the Data Library Manager. In SAS Management Console, onthe Plug-ins tab, select “+ to expand the Application Management node, Select "+" to expand the Corfiguration Manager Highlight 81 Rep Sve Wispace Config 4.4 Right mouse click and select Properties, Click the Setings tab. Validate the query cache lbrary and the distribution library. They should match the ibrares sted under Data Libravies. Validation SAS BI Report Services ‘CASAS\Conlollav2\Appicatons\SASBIRepontSenvices4 silos Log directory For more detals about how to modify your log format and to see what logging entails, see the SAS Infoligence Platform 9.4: Web ‘Application Administration Guide at i Java Batch Batch Name SASApp2 - BRM Java Batch Configuration Configuration Directory = "G:\SAS\Config\Lev2\Applicalons\SASBIReportServices4.2" Java Batch Server in SAS Management Console, on the Plug-ins tab, select to expand the Server Manager node. 1 2, Select "+" expand SASApp2, 3. Select “+ to expand the SASApp? - Logical SAS Java Batch Server. 4. Voy the existence ofthe java batch server(s) referenced above. 5, Right mouse dick this server ana select Properties, 6. Click the Options tab. 7. Validate the command tne by examining the parameter values and verifying fl locations and the repository name. Local Services Validation 1. In SAS Management Console, onthe Plug-ins tab, select" to expand the Foundation Services Manager node. ‘steps 2, Select "s" to expand the SASBIReportServicesd.4 Local Services Definition. 43. Select “+o expand Core, 4. Very that thare are five services. utputgen ini fi ‘The fle outputgenini may need to be modified. Ths file is locate inthe install folder C:\Program FilesiSASHome2\SASBIRoporServices\4.4 2. The folowing default stings for Java command line options appear inthis file: java.net preferPv4Stack=true and java.net preferiPvéAddresses=fase 3. Ihe system is coniigured to use IPVB, these values must be changed to: java.net. prefelPvaStack=false and java.net preterIPvéAddresses=tue ‘SASApp2 - Pooled Workspace Server Host machine desktop-10 Port 8702 4. In the SAS Management Console, on the Plugins tab, select“ to expand the Server Manager node. 2. Expand SASApp2 3. Highlight the SASApp2 - Logical Pooled Workspace Server. 4 Right mouse click this server and select Validate. You should see a Validation Successful message Validation steps ‘SASApp2 - SAS DATA Step Batch Server Host machost doskton-10 fle: 13C:/SASIConfighLev2:Documents/instructons.himl 407 1516/2020 Configuration Guidelines and Details Log |C:ASAS\CanfigiLev2i directory For more details about the nial logging configuration and how to madi it, see “Administering Logging for SAS Servers" the SAS Intoligence Platform: Systom Administration Guido at hiadisupoort sas con/admin sialon, Validation +, Select hs link: CASAS\Confgileva\SASAnp2\BatchServerisasbatch bat ‘steps 2 If SAS starts successfully, the DATA step batch server has been validate. SAS Spawners Object Spawner2 Host machine Port 9582 CASAS\Confighl evaLogs For more details about te intial logging configuration and how to modify i, see “Administering Logging for SAS Servers” in the SAS Inteligenco Platform: Systom Administration Guide al hipuleunpor. sas.comladminisvalion Execution Windows service type SAS [Config-Lev2] Object Spawner2 ‘Shortcuts Programs > SAS > Configuration > Config - Lev dosktop-10 Log directory Connect Spawner2 Host maces! dosktop-10 Port 7542 Log 2'SASiConfiglLev2iLogs ‘dreckct For moro detals about the ina logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Y Inteligence Platform: System Administration Guide at htpuisunpor sas.com/Sdacminisration. Execution Windows service ‘ype SAS [Config-Lev2] Connect Spawner2 Shortcuts Programs > SAS > Configuration > Canfig - Lev SAS Web Infrastructure Platform Data Server Host machine Port 9433 Log 2'SASiConfiglLev2iLogs directed For more details about te intial logging configuration ane how to mocify it, see "SAS Web Infrastructure Patform Data Server in the Y SAS Intligence Platform: Midale-Tier Administration Guide al iip!/sun20r sa6.com/94acmin stralon dosktop-10 Execution Windows service type SAS [Confg-Lev2] Web Infrastructure Platform Data Server Solution Data Servers ‘SAS Decision Manager Common Data Server Host achat desktop-t0 Port 10483 Log 2'SASiConfiglLevaLogs ‘areckct For more detals about the ina logging configuration and how to modiy it, 866 “SAS Web Infrastructure Platform Data Server in the rectory SAS inteligance Platform: Midale-Tier Administration Guide at htplisugoor sas.canv@4adminsiration, Execution Windows Service fle: 11C:/SASIConfighLev2:Dacuments/instructons.hml 527 1516/2020 Configuration Guidelines and Details ‘Type SAS [Config-Lev2] Decision Manager Com Data Svr Cig SAS Data Remediation Data Server Configuration Data Server Host machine desktop-10 Port 9833, Log directory CASAS\ConfislLev2ilogs Windows service Execution tyPe SAS (Confg-Lev2] DataRemeditionDalaSorver SAS Job Monitor Data Server Host machine desktop-10 Port 9453, Log directory C\SAS\Confi\LevaiLogs Windows service Execution 1YP® SAS [Confg-Lev2] JobMonitorDataServer Visual Process Orchestration Runtime Server SAS Visual Proces Orch tration Runtime Server host desktop-10 ‘SAS Visual Process Orchestration Runtime Server port 21051 Notes: + The Visual Process Orchestration Runtime Server is administered separately from SAS servers. The server is managed by the Windows Service Manager. Stop and Start the SAS Visual Process Orchestration Server using thal interface. One extra action wil be needed. The Server needs to start after the SAS Metadata Server. A post instal step isto setup this dependency. Here is the command followed by an ‘example, The command will need o be run from a MS-DOS promgt, > Command: se config "name of PO Server service’ depend= “name of metadata service" sample: se config "df-POServer-server'" depend= “SAS [Conig-Lev2] SASMeta2 - Metadata Server” SAS Deployment Tester Server Host machine desktop-10 Port 10022 Execution Windows service type SAS [Config-Levz} Deployment Tester Server Shorteuts Programs > SAS > Configuration > Config - Lev2 1. In SAS Management Console, on the Plug-ins tab select" to expand the Apolication Management node, 2. Select “+"to expand Deployment Tester 3. Highlight the hast machine: desktop-10 Validation 4, Right mouse click and select Run All Test Suites. ‘stops 5, Select "#" to expand the Results. 6, Validate the results for each test suit. All tests should pass, Ityou are prompted for credentials, select the “Help” button in the Credentials dialog box to display the accounts that can be used foreach test sue, 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 plugin allows for tess lobe execuled on remote systems from a single 'SASMC instance. + When you are done validating your deployment wth 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 tne rest of SAS, that can be slaled and used periodically to very the health of your SAS deplayment. You should consider verying the heallh of your SAS deployment after inital installation, ater applying maintenance and hotfixes, of when you make any other significant changes to the deployment. {le:f1C:/SASIConfighLev2iDocuments/instructons.himl 6o7 1516/2020 Configuration Guidelines and Details + More detailed information on validating your SAS deployment with Deployment Tester can be found inthe "Using the Deployment Tester” Section of the SAS 9.4 Intligence Pratform: System Administration Guide, which is avalabl at his Operating System Services Scheduling Server Host mactnt desktop-10 Port 9452 Log rect CASAS\Contgev2L 4. Inthe SAS Management Console, on the Plug-ins tab, select "+" Lo expand the Server Manager node. Validation 2. Highlight Operating System Services2 - 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. SAS BI Lineage Scheduling Server Java Batch Name = ‘server *SASApp2-- BIL Java Batch Server" Configuration Configuration Directory = "C:\SASIConfigiLev2\Applcations\SASBILineaged.¢° Java Batch Server in SAS Management Console, on the Plugins tab, select Select "+" to expand SASApD2, ‘Select "+ fo expand the SASApp2 - Logical SAS Java Batch Server Verily the existence ofthe Java batch sever referenced above. Right mouse click this server and select Properties, Click the Options ta Validate the command line. to expand the Server Manager node. Validation ‘stops. _ScanDrivorbat file 4. Verity the existence of the file ScanDriver bat. This file is located in the configuration folder CASASIConfigh ev2\Applications\SASBILineaged 4 ‘Software Component in SAS Management Console, on the Folders tab, select Select "+" to expand the Apalications folder. ‘Select "+" o expand the SAS Bl Lineage Scheduling Server folder. Verily the existence ofthe BI Lineage Sched Svr 4.4 sofware component. (0 expand the System folder. SAS Visual Analytics SAS Visual Analytics Administration To provide access to SAS Visual Analytics, see the topic *Adding Users" in the SAS Visual Anaiytcs: Administration Guid. Fora brief validation sequence, sae "Validate Your SAS Visual Analytics Deployment” inthe SAS Visual Analytis: Installation and Configuration Guide (Non-distibuted SAS LASR) ‘Administrative documentation for SAS Visual Analytics is available from httyisupportsas.comidocumentation/oninedocWvalindax inl SAS Visual Analytics High-Performance Configuration ‘SAS Visual ‘Analytics Nonedistibuted LASR Data Provider Autoload To schedule autoloading, run “C:\SAS\ConfigiLev2\Applications\SASVisualAnalytics\VisualAnalyticsAdministratorschedule.bat” ‘Scheduling program, which wil then run periodically every "15" minutes. To unschedule, run “CASAS\ConfghLev2\ApplicationsiSAS VisualAnalytics\VisualAnalytiesAdministratorunschedule, bat" For more details about autoloading, see "Autoload" in the SAS Visual Analytics: Administration Guido at ‘lavisupnor sas.com/documentaton/onlinedan'vaindax him fle: 13C:/SASIConfighLev2:Documents/instructons.himl m1 1516/2020 Configuration Guidelines and Details ‘Autoload 108 ¢.\sASiConfigl ev2\Applicatons\SASVisualAnalyics\VisualAnalyticsAdminstratorLogs directory SAS Information Retrieval Studio SAS Information Retrieval Studio for SAS Host machine dosktop-10 Server Admin Port 10552 Proxy Server Port 10562 Proxy Server Admin Port 10672 Proxy Server Web Admin Port 10582 Pipet 1e Server Port 10592 Server Admin Port 10702 Pipeline Server Web Admin Port 10712 Indox Bullder Port 10722 Query Server Port 10732 Query Statistics Server Port 10742 Query Statistics Server UDP Port 10742 Crawler Admin Port 10752 ‘Query Web Server Port 10762 Execution type Windows service SAS [Confg-Lev2] Information Retrieval Studio SAS Web Infrastructure Platform Scheduling Services Log directory C\SAS\Confi\LevaiWvebiLogs JES Java Batch ‘Server Workflow Java Batch Server Configuration Validation steps Name = "SASApp2 - JES Java Batch Server" Name "SASApp2 - Workflow Java Batch Server" Configuration Directory = "C:\SAS\ConfigLeva\Web\Applications\SASWIPSchedulingServicesd.4" Deployment Directary = "C\SAS\ConfgiLev2WWIPSchedtatch” JES Java Batch Server in SAS Management Console, on the Phig-ins tab, select" to expand the Server Manager node, Select “+"to expand SASApD2. Select "+" to expand the SASApp2 - Logical SAS Java Batch Server Veni the existence ofthe java batch server(s) referenced above. Right mouse click this server and select Properties. Glick the Options tab. Validate that the command line and arguments are appropriate for ths 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 SASApp2. Select “+o expand the SASApp2 - Logical SAS Java Batch Server \Verfy the existence ofthe Java batch server(s) referenced above. Right mouse click this server and select Properties, Click the Options tab. Validate tnat the command line and arguments are appropriate for this java batch server servicetriggerin file The fle servicetiggerini may need to be modified. This fle is located inthe instal folder C:AProgram FilesiSASHomo2\SASWebinfrastructurPatformSchedulingServicesi 4 “The allowing default settings for Java command ire options appear in this fle: java.net preferlPvaStack=ttue and java.net preferiPvéAddresses-fase. {l:13C:/SASIConfighLev2:Documents/instructons hil anv 1516/2020 Configuration Guidelines and Details 3. the system is configured to use IPVG, these values must be changed fo: java.net. prferlPvaStack java.net proteriPvéAddresses=tus ‘Scheduling Services - Cache Locator Host Machine desktoo-10 Port 41416 Log directory CASASIGonfigll ev2lWeblgemfralinstancosting 41415 Configuration Configuration Directory = "C'\SAS\ConfigLovalWebigemfiralinstancestins_41415" Windows Service Execution type sas (Confg-Lev2] Cache Locator on port 41416 4. Check the status ofthe running locator process using Windows Service : SAS [Config-Lev2] Cache Locator on port 41416 2. Validate thatthe locator process is started Validation steps ‘Scheduling Services - DIP JobRunner Host Machine desktop-10 Log directory C:\SAS\Confi\Lev2lWeb\Aoplicaons\SASWIPSchedulingServices9.Aidip Configuration Configuration Directory = "C:\SAS\Config\LovalWebApplicalions\SASWIPSchedulingServices9.4idip™ Windows Service Execution YP Sas (Confg-Lev2] DIP JobRunner 4. Check the status of the DIP JobRunner pracess by sunning CASAS\ConfigLev2\Wveb\AppicationsiSASWIPSchedulingServices9 4\dpIDIP JobRunnerServce.bat status 2, Validate tnat the serveris sloped, Validation steps Remote Services ‘The Remote Services process isnot used by SAS applications and solutions beginning with SAS 9.4 tis configured, but not running by default, if yeu want te deploy a custom application ina this SAS 9.6 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 Wob Console Log directory Starting and Stopping SAS Environment Manager dosktop-10 7081 8a C:ASAS\Config\LevaiWebiSASEnvironmentManagerserver-§.8.0-EE sasadm@saspw rian. magpantay@gmail com Postgresal esttop-10 933 EvManag llpuldesktop-10:7081/ C:ASAS\ConfigLevaiWebISASEnvironmentManagerserver-5.8.0-EE\logs You can start and stop your SAS Environment Manager use the Service Control Manager (Control Panel->Services). {le:f1C:/SASIConfighLev2iDocuments/instructons.himl oor 1516/2020 Configuration Guidelines and Details Service Name: Sas [Conttg-Lov2] SAS Environment Monsger You can also manually stat and stop SAS Environment Manager with the following commands. To star SAS Environment Manager, enter a C:\SAS\Contig\Lev2\WeD\SASEavirconenManager\senver-5.6.0-26\318 To stop SAS Environment Manager, enter Note: thatthe fist time the SAS Environment Manager stats up it ay take several minutes to itiaize. 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 Envsonment Manager Wab Console Click Browse’ under Resources List all servers by cicing ‘Servers Click one of the server name including PostgreSQL. (for example, abc.com PostgreSQL 9.x ocalhost'9492), You need to do the following steps for all server names including PostgreSQl. Go tothe 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 forthe following properties, postgresqlihost Host name ofthe PostgreSQL server. Listening port ofthe PostgreSQL server {You can find it rom the path or command of the Windows service Web Infrastructure Platform Data Server, t should Be a number after -p. Default value: 9432) postgresqluser Username ofthe PastgreSQL server (Default user: dbmsowner) postgresql.port postgresglpass Password for the speciid user posteresqlpgdata Full path Io the data fle (Usually the path is $SASConfgiLevN/WebInfrastucturePlatformDataServeridata) Windows service name of the PostgreSQL server Default name: SAS [Config-LevN] Web Infrastructure Platform Data service_name Window ‘SAS Job Monitoring Hyperic HQU Plugin 2.2M1 Notes: + Because of diferences in machine startup times, the hyper agent might fal to start, causing configuration errors when attempting to monitor jabs, To fix this, restart the JobMonitorDataServer database service so thatthe Job Monitor components startup without issue. + Ifthe server tors configured before the midtier where SAS Environment Manager is deployed, thore isa chance thatthe Job Monitor hyperic ‘agent might not configure correctly during installation, This is realzed when jobs that are run onthe server are not visible inthe auto-dscovery portlet in SAS Environment Manager. If the auto-discovery portlets not populated with ob information, reset the hyperic agent for Job Monitor by rorunsing the hyperic agent serpt after the installation and configuraton is completed. This action wil nitate communication between Job Monitor and SAS Environment Manager. The scripts located at: C:\SASIConfigh ev2\WebiSASEnvironmentManageragent-5.8.0-E5, nae ‘agent.sh restart SAS Environment Manager Agent Configuration SAS Environment Manager Agent Home Dir C:\SAS\ConfigiLev2\Web\SASEnvironmentManagertagent-.8.0-EE ‘SAS Environment Manager Agent Host Name _desktop-10 ‘SAS Environment Manager Agent Port 2145 Log directory C:\SAS\Config\ev2iWoblSASEnvironmentManageriagent-5.8.0-FEllog 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: {le:f1C:/SASIConfighLev2iDocuments/instructons.himl son? 16/2020 Configuration Guidelines and Details ‘As [Conftg-Lov2] SAS Enviroment Manager Agent ‘You can also manually stat and stop SAS Environment Manager Agent withthe following commands. To start SAS Environment Manager Agent, enter To stop SAS Environment Manager Agent, enter Ta restart SAS Environment Manager Agent, enter ‘The “estar” command wil force the agent to contact the SAS Environment Manager and then save the connection settings to the agent's CISASICanfglLevaiWeb\SASEnviranmentManageriagent-5.&.0-EE\dala dractary To run SAS Environment Manager Agent selup, you must run command ine under a command prompt. (On Windows 7 or above, i above commands return error, open a command prompt in the Run as administrator mode, then run above commands again SAS Environment Manager Enablement Kit Server Quick Start Guide For information on inialzing SAS Environment Manager Enablement Kit Server, see :\SASIConfig\Lev2iWeb|SASEnvironmentManageriom- framework'SAS. Environment. Manager Service_ Architecture Quickstart pa. For the most up-o-date information, including ints and tps, troubleshooting, and addtional kts, see ‘itpulsupport sas. com/sotwarelproducts/sevindex inl. SAS Web Server Configuration Vendor SAS Web Server Name SAS Web Server Version 9.85 lation Directory C:\Program Files\SASHome2\SASWebServer'9.4 Instance Directory | C:\SAS\ConfghLev2\WebilVebServer Host desitop-10 HTTP Port 60 HTTPS Port 443, Insti Server Administrator Emall Address ran [email protected] Sorver Home Page ipiideskion-10:80 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, Ths oa! allows you te manually execute configuration steps through a command line interface. You performed an automated configuration. The tool can resiore or reconfigure each resource ‘xacly as it was configured during the SAS Deployment Wzard configuration steps, The Scripting tol is located inthe rectory CASAS\Config\LevalWeb\Scrpis\WebServer. Itis possible to make changes to your configuration by modifying property les and rerunning steps using the configuration tool Detaled instructions forthe configuration framework can be found inthe SAS inteligence Platform: Midale-Tler Administration Guid. ‘Summary of Automated Configuration Steps You have chosen auto configuration of SAS Web Server. The following list contains @ summary of configuration actions the SAS De has already performed {le:f1C:/SASiConfighLev2:Dacuments/instructons hm ner loymant Wizard 16/2020 Configuration Guidelines and Details 4. The installation paths found in the scripts and configuration files located in the installed image have been updated. 2. Aninstance othe web server has bean created. 3. Aservice has been installed for starting and stopping the web application server. 4 A custom SAS configuration fle has been created. This configuration files updated when new application servers and applications are added Starting and Stopping Servers 4. Enable execution of powershell script: The serpt used t install the service and start the servers writen in Windows PowerShell 2.0. If necessary, enable Windows PowerShell for script processing: by default, script processing le cisadled, 4. 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 stats 2. Check the current PowerShell setting by executing the following command Ps pronpt> Get-ExecutionPalicy Irthe command retums Resticted, it means that PowerShell is not yet enabled. Enable ito allow local script processing at a minimum by ‘executing the follwing command: Ps prompt» Set-ErecutionPolicy fenotesigned 2. Install the service for starting and stopping the web application server The service is already installed during an automated configuration. To instal the service enter: ‘a Cx \SAs\contsp\tewa\ueb\ebserveriain poverahell-\hespeeel 95) Snstall 43. Star the server: Powershell .\httpectl.pet stare 4. Stopping the server: Log Files ‘There are potentially thee log files generated by the server and when any of them reaches a size of 50 megabyles, i fs saved and a new logfile of that type is started. Logfiles are placed in the directory C\SAS\Con(LevaiWebiWepServeiogs. Each ig fle includes a datestamp as par of the fle name. These logs are not removed and should be perioicaly cleaned up to recover disk space. The following list describes the three diferent log files at can be generated + accoss_YYYY_MM_DD-HH-MM og - pain text hip requests + error YVVY_Nlld_DD-HH-MiA og server error log {+ S81 fequest_YYVY_MM_DD-HE-AMiog - 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 Fles\SASHomeZ\SASWebApplicationServer®.4 Java Home | C:\Program FilesiSASHome2\SASPrivateJavaRuntimeEnvironment9 Ayre 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 apalcations AAasic 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 numberof users. Ifyou need to sel up a more sophisticated topology such as web server authentication or single sign-on, see the SAS latligance Piatfomn- Socurly Administration Guide, For reverse proxy server and secure socket connections, see the ‘SAS Infoligence Platform: Middle Tir Administration Guide {le:f1C:/SASIConfighLev2iDocuments/instructons.himl wer 16/2020 Configuration Guidelines and Details ‘SAS Web Application Server Configuration Scripting Tools [A'SAS Web Application Server configuration serpting too! ls generated during a SAS Deployment Wizard configuration. This tool allows you to ‘manually execute configuration stops through a command line interface. Ifyou performed a manual configuration, you can execute the serpting tool ‘create the server corfiguraton and to configure resources that are equivalent to whal would have been buill during a SAS configuration Ifyou had performed an automated configuration. If you performed an automated configuration, the tool can reconfigure each resource exacly as it was Configured during the SAS configuration step. You can execute the individual steps and make changes to your configuration by maaltying the folowing property Mes. :,sts\contsertevz\webiscrtpts\apeserver\props\appserver. properties [EASAS\Canre\teva\web\Serspts\appserver\prope\cracenesa1s propert.as ‘You can rerun the scripting tool to redeploy or reconfigure web applications to SAS Web Application Server, or SAS Web Server. CrASAS\contse\Leva\ued\Scrspte AppServer\appsrucontigucad 2 You can use the scripting tol ta stop, stat, or restart all configured servers including SAS Web Application Server, SAS JMS Brok Locator, or SAS Wed Server, r SAS Cache Cr \sas\contse\ Leva ued\scrspts\Appserver\appsrucontsg.cnd stop E:\SaS\Cantse\Leva\web\serspee\eppserver\appervcontsp cad start ‘CASAS\Conrip\leva\eb\seripts\apeserver\apparveon?ipend restart ‘You have chosen auto configuration of the SAS Web Application Server. The following sts @ summary of configuration actions the SAS Deployment Wizard has already performed: Configuring SAS Web Application Server Instance(s) Host machine [deskiop-10 Port | 8080, 8443, ‘Server Name |SASServer! Configuration directory _|C:\SAS\ConfigiLev2\WeblWebAppServerSASServert_? Log directory | C:\SAS\ConfglLev2\WebiWebAppServeriSASServert_t\logs ‘SASWebln{rastructurePlatformServices9.4 ‘SASWeblnfrasiructurePlatformApplicatons9.4 SASWIPASmind 4 ‘SASWIPResources9.4 ‘SASStoreaProcess9 4 SASWorktow9.4 ‘SASConteniServer9.4 ‘SASPrinclpalServices®.4 SASIdentiyServices9.4 ‘SASAuthorizationServices9.4 ‘SASTemplataEdtor9.4 'SASPormissionManager®.4 ‘SASFlexThemes4.7M2 ‘SASThemeDesignerd, 7M2ForFlex 'SASThemes9.4 ‘SASDeploymentBackup9 4 ‘SASBaackupManager9.4 SASPorald| ‘SASPackageViewerd.¢ SASBIDasnboard4.4 SASBIPortots4.4 Clusterabie Web Applications Non-clusterable Web Applications | + SASBIDashboardEventGend.4 ‘Windows Service |SAS [Confg-Lov2] SASServori_1 - WebAppServer ‘Check the status ofthe running Web Application Server Validation steP© Windows Service : SAS [Corfig-Lev2] SASSorver'_1 - WebAppServer Host machine |deskiop-10 Port 9080, 9443, ‘Server Name |SASServer!t Configuration directory |C:\SAS\ConfigiLev2\Web\WabAppServeriSASServertt_t Log directory | C:\SAS\ConfglLev2iWeb\WebAppServerSASServertt_tNogs {l:f1C:/SASIConfigiLev2:Documents/instructons.himl 1307 16/2020 CClustorable Web Applications Configuration Guidelines and Details + SASEnterpriseMiner14.9 2 SASForecastServeri4.3 + SASModelManagort4.2 + SASTimeSeriesStucioMidTiort4.3, Non-clusterable Web Applications Windows Service ‘SAS [Config-Lev2) SASServertt_1 - WebAppServer Validation steps CCheck the status of the running Web Application Server Windows Service : SAS [Config-Lev2] SASServer!t_1- WebAppServer Host machine doskiop-10 Port 9180, 9543 Server Name SASServert2 Configuration directory ‘CASAS\Contigh. ovaWeb\WebAppServeriSASServert2_1 Log directory (CASASIConfigl evaWeb\WebAppServeriSASServert2_Nogs Clusterable Web Applications ‘SearchinterfacstoSASContent3 6 ‘SASVisualAnalytiesHub7 4 SASVisualAnalytesServices? 4 ‘SASVisualAnalytiosDesigner?.4 ‘SASVisualAnalyticsGraphBuilder7.4 ‘SASVisualAnalytcsViewer? 4 + SASVisualAnalyiosAdminstrator7.4 + SASVisualDalaBulder7.4 Non-clusterable Web Applications Windows Service ‘SAS [Config-Lev2] SASServert2_1 - WebAppServer Validation steps ‘Check the status ofthe running Web Application Server Windows Service : SAS [Config-Lev2] SASServer!2_1 - WebApoServer Host machine doskiop-10 Port 9280, 9643 Server Name SASServert3| Configuration directory ‘CASAS\Contigh ev2\Web\WebAppServer'SASServert3_t Log directory (CASAS\ConfighL evaWeb\WebAppServeriSASServert3_Nogs CClusterable Web Applications + SASDataManagement 2 SASJobMonitorMidTierSve + SASProcessOrchestration + SASDataRemediation + SASTaseManager Non-clusterable Web Applications Windows Service ‘SAS [Config-Lev2] SASServert3_1 - WebAppServer Validation steps ‘Check the status ofthe running Web Application Server Windows Sorvice : SAS [Config-Lov2] SASSorverta_1 - WebAppServer Host machine deskiop-10 Port 8180, 8543 ‘Server Name ‘SASSorver? Configuration directory (CASAS\Config v2Wab\WebAppServeriSASServer2_1 Log directory (CASAS\Config evaWeb\WebAppServer'SASServer?_Niogs (Glusterable Web Applications + SASEnvironmentMgrMidTi¢72 5 + SASSecurityAdminModule2.3 + SASLineages.2 + SASWedDoc8.4 + SASWebReportStudiod.«-SASWebReport2 + SASEnvironmeniMartibraryMod2.1 2 SASServerModule2.1 + SASUserModule2.2 + SASStudioMidTIe3.7 fl: 13C:/SASIConfighLev2:Dacuments/instructons hl s4n7 16/2020 Configuration Guidelines and Details I I Non-clusterable Web Applications Windows Service [SAS [Config-Lev2] SASSorver2_1 - WebAppServer ‘Check the status ofthe running Web Application Server Validation steP= Windows Service : SAS [Corfig-Lev2] SASSorver2_1 - WabAppServer Host machine |deskiop-10 Port | 8680, 8043, Server Name |SASServer? Configuration directory _|C:\SAS\ConfigiLev2\WeblWebAppServerSASServer?_* Log directory | C:\SAS\ConfiglLev2\Web\WebAppServeriSASServer7_t\logs, CClusterable Web Applications | + SASDecislonManagerCommon3.2 Non-clusterable Web Applications Windows Service |SAS [Confg-Lev2] SASServer7_1 - WebAppServer ‘Check the staius ofthe running Web Application Server Windows Service : SAS [Confg-Lev2] SASServer7_1 - WebAppServer Host machine [deskiop-10 Port | 8780, 9143, Validation steps Server Name |SASSorver® Configuration directory | C:\SAS\ConfigiLev2\WeblWebAppServeriSASServer®_t |Log directory | C:\SAS\ConfigiLev2\WebiWebAppServeriSASServer8_‘llogs| CClusterable Web Applications Non-clusterable Web Applications ‘Windows Service |SAS [Confg-Lev2] SASServer®_1 - WedAppServer ‘Check the status ofthe running Web Application Server Windows Service : SAS [Confg-Lev2] SASServer®_1 - WebAppServer Validation steps Configuring SAS JMS Broker The SAS Deployment Wizard installs and configuros SAS JMS brokor as a standalono sorvor in SAS 8.4. Host machine | desktop-10 Port | 61617 “IMX Port | 11100 ‘Configuration directory | C\SAS\ConfiglLevalWeblacivemg Leg directory | C\SAS\GonfigiLevaiWeblactivemaidata Windows Service | SAS [Config-Lev2] JMS Broker on port 81617 ‘Check the status ofthe running JMS broker Windows Service : SAS [Confg-Lev2] JMS Broker on port 61817, 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 Web Report Studio stops and see mages then SAS Themes are working properly. SAS Environment Manager Mid-Tier Lo file + CASAS\Confiev2ebiL agsISASSanver?_ SASF nironmentMrMiTiar2 Slog {le:11C:/SASIConfighLev2:Documents/instructons hm 1827 16/2020 Configuration Guidelines and Details For more details about how to modify your lag format and ta soe what logging entals, soe “Administering Logging for SAS Web Applications” Inthe SAS Intoligence Platform: Middlo-Tler Administration Guido at bite /sigpor. sas com/adadmn station. SAS Security Administration Module Note This module is part of SAS Environment Manager + CASAS\Configll ev7\Webil gsISASServer?_11GASSecurtyAdminodule? 3 log Log file For more details about how to modify your lag format and to see what logging entails, see “Administering Logging for SAS Web Applications” in the SAS inteligence Platform: Middlo-Trer Administration Guide at hig lisupporl sas. com/@4administaion SAS Environment Manager User Module Note This module is part of SAS Environment Manager + CASAS\Configl ev”\Webil galSASServer? 1\GASUserModule? 2 lag Log file For more details about how te modty your lag format and to see what logging entails, see “Administering Logging for SAS Web “Applications” inthe SAS infaligence Plaform: Midae-Tier Administration Guide at Nip lisupparl sas, com/94administaion SAS Environment Manager Library Module Note This module is part of SAS Environment Manager Log 7 isASionfLeuZebiLogsISASSanve?_ 1ISASEnironmentMotL brary Mad? tog 2g file For more details about how to modty your log format and to see whet logging entals, see “Administering Logging for SAS Web “Applications” inthe SAS infeligence Platform: Midale-Tier Administration Guide at Nip lisupparl sas com/@4administraion SAS Environment Manager Server Module Note This module is part of SAS Environment Manager + CASAS\ConfolLev2\WebiLogs\SASServer?_11SASServerModule2.1 log Log file For more details about how te modify your lag format and to see whet logging entails, see “Administering Logging for SAS Web ‘Applictions” in the SAS infellgonce Platform: Midale-Tier Administration Guide at Nig lisupport sas, com/@4admin station SAS Web Infrastructure Platform Log directory |C:\SAS\GonfigLevalWeblLogsiSASSever! 1) 4. Access the Comment Service. Validation steps 2. Lag in using the DESKTOP. 1O\sasdemo credentials provided during configuration 3. Veiify that you can add a comment SAS Studio Mid-Tier URL btiou/deskton-10-80/SASStucio + CASAS\ConfglLev2WoblLogs\SASServer? 11SASStudioMidTier3.7 log Log file For more details about how to modly your lag format and to see what logging entails, se0 “Administering Logging fr SAS Web Applications” inthe SAS infeligence Platform: Midler Administration Guide at hia lisuppart sas. com/S4administation. Validation {l:13C:/SASIConfighLev2:Documents/instructons.himl 1627 16/2020 Configuration Guidelines and Details steps 1. Access the URL provided above. 2. Login using the DESKTOP-1O\sasdema credentials provided during configuration SAS Content Server Log fle | C:SAS\Configl ev2iWebllogs\SASServert_tiSASContentServerd 4.09 4. In the SAS Management Console, on the Plugins tab, select “+” to expand the Server Manager node. 2 Highlight the SAS Content Server 3. Right mouse click this server and select Validate. 4. Lag in using valid credentials for an unrestricted user defined in the SAS Metadata Server. 5, You should see a Validation Successful message, SAS Stored Process Web Application URL biinvideskton=10.80/SASSioredProcessido. Log fle CASAS\ConfigLavalWebil ogs\SASSanert_NSASStoradPracess9.4.o9 4. Access the URL provided above. 2 Lag in using the DESKTOP- 0isasdomo credentials provided during configuration. lidation steps 3. On ine Weleome page, click the “Sample: Server Test” Ink to access the custom input frm fr this sample stored process. 4 Select an output format and ODS style or accopt the default values, and click the "Display SAS Output button, 5, The output from the stored process isa simple message that the server processed the request. SAS Web Administration Console URL tiosidesktop-10:80/SASAdmin Log fle CASAS\ConfigLovalWebiLogs\SASSonert_ NSASAdming 4.109 4. Access the URL provided above. 2 Lag in using the sasadm@saspw credentials provided during configuration, 3. On the main page, expand the “Environment Management” flder inthe tree and select the "Users" node. 4. Verity that sasadm" appears inthe “System Users” section inthe right frame, 5. Click the checkbox in he far rght column of the "sasadm” row. 6. Glick the menu icon directly above the checkbox and select "Send E-mal 7. Ener your ema address in te “To feld and click “Sen 8. Verify that you received the ema Validation steps ‘SAS Web Report Studio ‘GASAS\Confgllev2\Webil ags\SASServer?_1\SASWebRenorStuding 4.SASWebReport2 log Log file For more details about how to modi your lag format and fo see what logging entails, se “Administering Logging for SAS Web Applications” inthe SAS inteligence Plaform: Midale-Ter Administration Guide at iia lisupporl sas, com/@4administalion 1. Access the URL provided above ‘steps 2. Login using valid credentials d ined in the SAS Metadata Server SAS Information Delivery Portal URL httpilldeskton-t080/SASPortal Log fle CiSAS\Confgll eyalWeb)l ogs\SASServert_ NSASPortale 410g Validation ‘steps 1. Access the URL provided above. 2. Login ising the DESKTOP-10\sasdemo credentials provided during configuration, 3. Since the Portal samples were installed, vey that a Home page was created and contains two portlets, My Collections and Bookmarks. 4. Perform a search to very that you have access to SAS content. fle: 11C:/SASIConfighLev2:Dacuments/instructons.himl ser 16/2020 Configuration Guidelines and Details Notes: + The SAS Portlets are located at: C:\SASIConfgl ev7\Web\Applications\SASPorlets4.4\Deployed + lfyour network has 2 proxy server, you must specity te following parameters on the Application Server star-up command so that syndication ‘channels and the URL Display Portlet can access content outside of your network. © -Dhitp.proxyHost=host © -Dhitp praxyPort=port SAS Visual Analytics Services Service SAS Visual Analytics Transport Service + SigAglconisy mctnebLoonsassanert2_ eA nua Ane oem iL.evaWehlLogs GASSeneriZ NGASLASRAuthorzaton? 4 a9 Log fie 1 GigasicontelevanenLes veri lanalyicsHyperink7 4.log For mare d i$ about how ta modify your log format and to see what logging entails, see “Adminstering Logging for SAS Web Applications” inthe SAS intelligence Platform: Midale-Tier Administration Guide at iin isunnart sas cam/s4acdm nisvatian Notes: + The SAS Anonymous Web User has been configured for your environment. Currenly SAS Visual Analytics Services does not have Guest Aczass enable, For mov infomation on how to suppor Guts Access, se he tape “Supporting Guest Access’ ho SAS Visal Analy ‘Administration Guide available at htplisuy «= TheTollng UR have been added tothe coniguraton proper Sas wet caps owes! the SAS Appllation Infrastructure node: ® hitpslopnsia sas.com! © hitpiopnstb sas.com! © hitpsiopnstes2s.com! SAS Visual Analytics Hub URL _htto dosktop-10.80/SASV'sualAnalyesHub CASAS\ConfiglLovalWeblLogs\SASSorvert2_T1SASVisualAnalticsHub7.4.log Log file For more details about how to modly your lag format and to see what logging ental, see “Administering Logging for SAS Web Applications" inthe SAS inteligence Platform: Midle-Tier Administration Guide at tia Jsupoort sas, com/Séadministration Validation +, Access the URL provided above. ‘steps 2, Login using the DESKTOP-10\sasdema 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 ‘mate infermation on how ta support Guest Access, see the topic “Supporting Guest Access" in the SAS Visual Analytics: Admnistralion Guide available at hio/supaor sas.cam/documentaton/onlinedociva/index hin SAS Visual Analytics Designer URL _Htosidesktop-10:80/SASVisvalAnalytesDesigner + GASASIConfgl ev2lWebil gs\SASServert2_1NSASVisualAnalytosDesigner7 4.109 Logfile For more details about how to modty your log format and to see what logging entails, see “Administering Logging or SAS Web Applications” inthe SAS infoligence Platform: Midal-Tior Administration Guide at iia lisupporl sas, com/94administalion Fora brie validation sequence, see "Validate Your SAS Visual Analytics Deployment” in tne SAS Visual Analytics: Installation and Configuration Guide (Non-aistibutod SAS LASR) available at hii: /support sas. comidocumentation/oninedocivaindex hin ‘SAS Visual Analytics Viewer {le:11C:/SASIConfighLev2iDacuments/instructons.himl 1827 16/2020 Configuration Guidelines and Details URL _bifpddeskton-10:80/SASVisualAnalyticsViewer + CASASIConfoll ev2\Webll gsiSASServert2_ 1\SASVisualAnalytiesViewer7 4.log Log fle For more details about how to mody your log format and to see what logging entails, see “Administering Logging or SAS Web Applications” inthe SAS infelgence Plaform: Midale-Tiar Administration Guide at iis lisuppart sas com/@4administration 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) available at hitp/support sos com/documentation/oninedoclvalindex hin + The SAS Anonymous Web User has been configured for your envionment. Currently SAS Visual Analytics Report Viewer does nat have Guest ‘Acoass enabled, For more information on how to support Guest Accass, see the lopie “Supporting Guest Accass” in the SAS Visual Analytics ‘Administration Guide available at hitpisunport sas com/documentallon/onlinedacWvalindx hn, SAS Visual Data Builder URL biiouldesktons10-80/SASVsualDataBuilier CASASIConfiglLevaiWebiLogs\SASSewver!2 TSASVisvalDataBuiler? 410g Log directory For more details about how to modly your lag format and to see what logging ental, see “Administering Logging for SAS Web Applications” inthe SAS infeligence Platform: Midale-Trer Administration Guide attic lsupnartsas,com/S4administation Validation For a bret validation sequence, see “Validate Your SAS Visual Analytics Deployment” in tre SAS Visual Analytics: Installation and ‘stops Configuration Guide (Non-dlstrbuted SAS LASR) available at hte /support sas. comidacumentation/oninedoeWvalindex hin. SAS Visual Analytics Graph Builder URL bit Log file For more details about how te mody your log format and to see what logging entals, see “Administering Logging for SAS Web Applications” inthe SAS infellgence Platform: Midale-Ter Administration Guide at iio lisupporl sas, com/@4administaion For a brie validation sequence, see “Validate Your SAS Visual Analytics Deployment” in tne SAS Visual Analytics: Installation and Coniiguration Guide (Non-aistibuted SAS LASR) available at hil: /support sas. comidocumentation/nlinedoeivaindex hin SAS Visual Analytics Administrator URL btigulidasktons10-80/SASV'svalAna dics Administrator SA cAsAsicontk Log directory For more detalls about how to modly your lag format and to see what logging ental, see “Administering Logging for SAS Web “Applications” inthe SAS inteligence Platform: Midle-Tier Administration Guide at hin lisupoart sas. com/S4administation. Validation For a brie! validaion sequence, see “Validate Your SAS Visual Analytics Deployment" in the SAS Visual Analytics: Installation and ‘steps Configuration Guide (Non-dlstrbuted SAS LASR) available at hip support sas, comidacumentation/oninedatWvalindax, hin, SAS BI Portlets Log file | C:ASAS\Configl ev2lWeb\logs\SASServeri_\SASBIPortets4.4 log Validation steps 4. Login tothe portal. 2. Add the SAS Navigator Portlet to a portal page. {le:13C:/SASIConfighLev2:Documents/instructons hil 1927 16/2020 Configuration Guidelines and Detals 3, Navigate to altferent locations. Notes: + SAS reports must be defined in order to use the SAS Report Poti + SAS stored processes must be defined inorder to use the SAS Stored Process Portlet ‘+ SAS dashboards must be defied in order to use the SAS Bl Dashboard Porte! SAS BI Dashboard URL biipideskton-10:80/SASIDashbaard + CASASIConfigll ev2WeblLogs\SASServert 11SASBIDashboard4.4.log 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: Midale-Ter Administration Guide at ia Jsupoart sas. com/S4administaion +. Grntthe user“SAS Derno User access to SAS BI Dashboard 44 n SAS Management Console, onthe Plugins tab, select the User anager node 2. Right ‘elec "BI Dashboard Administrators" and select Properties. 3: Saloc the "Mombore" ab 4 Double cick on SAS Demo User o add ito the group. 5 Select OK. 8. Arcons the URL proved above 4. Login using the “DESKTOP. 1sasdomo”crodantls provided during configuration 8 Soler Manage Dashboards 8: Select New Indlestor Data 10, Entra nae for the ndeaior Data, and thon select OK. ‘1, Selec Data source. SQL query. Enter tis SOL query selec "fromm sashelp.prdsa Validation 12, Fil > Save, Naviga‘e to Products/BI Dashboard 4 3ModeIConfigs, and salact Save Stops 18. Flle> New> indicator 14. Entra Nome fre indctor,Sooct Display type: Pie Chart. Selact Browse, navigate to th inccator daa just created, and Selec: OK. Seloct OK again. 1 Select Catogoy val: COUNTRY. Select Response value: ACTUAL. 16. Flo > Save. Navigate o ProductsiB\ Dashboard 4 SindicatorDetnitions, and select Save, 17, Flle> New > Dashboard 1, Enter a Nome forthe Dashboard ar select OK. 15, intre Objects pane, navigate to Productslll Deshboard 4/ndicatorDefintions.Orag-- Save, Navigato to Product/Bl Dashboard 4./DashboardConfigs, and solect Save. 3°. View> Goto Dashboard Viewer 22. Very that you have accoss fthis dashboard by adding the Bl Dashboard Porte to a Paral page 23, Documeniation at ilsuaar sas camidacamentaion/onnedaeidashboardindex nls avalabe to assist you. Solect Apply Query Changes, SAS Flex Application Themes Validation SAS Flex Application Themes are used by SAS web applications that are displayed withthe Adobe Flash Player. ifthese applications ‘taps correctly display colors, graphics, and fonts, then the SAS Flex Application Themes have been successfull installed Validation SAS Theme Designer fr Flex is accessible from hiin:/desito0-10:80/SASThameDesignorEorFlex ‘steps In order to use this appleation, you must be a member ofthe role "Theme Designer for Flex: Administration” SAS Visual Process Orchestration URL _hilpddeskton-1 0:80/SASProcessOrchestration + CASAS\Configll ev”\Webil agsiSASServert3._1\SASProcessOrchestration log Log file For more details about ow te mody your lag format and to see what logging entails, see “Administering Logging or SAS Web ‘Appliclions” inthe SAS inteligence Platform: Midalo-Tor Administration Guide at Nis lisypporl sas, com/S4administalion Validation 1. Access the URL provided above. ‘steps 2. Login using he DESKTOP-TO\gasdema credentials provided during configuration {le:f1C:/SASIConfighLev2iDocuments/instructons.himl 20127 16/2020 Configuration Guidelines and Details ‘SAS Data Remediation Mid-Tier URL btigdlidaskton-10-80/SASDataManagement \SASSewert3 1\SASDataRemediation log CASAS\Confi\L evaiWebiLo 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 intelligence Platform: Midle-Tier Administration Guide at tio /supoort sas com/Séadministation Validation 1, Access the URL provided above. ‘steps 2, Login using the DESKTOP-10\sasdema credentials provided during configuration SAS Data Management Console URL bitpideskton-10A0/SASDataManagement 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" in tho SAS inteligence Platform: Midle-Tier Administration Guide at hic Jsupoart sas, com/S4administration. Make suro to add the SAS First Usor ora valid user to the following SAS Data Managomant user group which is automatically created Tor you: Data Managemont Executive. Tris wil give the User view capabilios only For nructions about adding SAS users to a Validation group, see "Adjust Group of Role Membership". ‘stops PS 5. nccess the URL provided above. 2. Login using the DESKTOP-1O\sasdemo credentials provided during configuration ‘SAS Task Manager Mid-Tier URL bt idesktop-10:60/SASTaskManager cAsAsiconfk LevaiWebiLog \SASSerert3_1\GASTaskManae log Log file For more details about how to modly your lag format and to see what logging entails, see “Administering Logging for SAS Web ‘Applictions” inthe SAS infoligonce Platform: Midle-Tror Administration Guide at hia lisupoart sas. com/94administation Validation +, Access the URL provided above. ‘steps 2. Login using the DESKTOP-10\sasdema credentials provided during configuration SAS Lineage Mid-Tier URL bifodidaskton-10:80/SAS! inaage + GASASIConfglLav2\Wabil agsiSASSorver?_{iSASLinaa903 2.09 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 Infelgence Platform: Middle Administration Guide at iis lisuppart sas com/@4administation Validation 1, Access the URL provided above. ‘steps 2 Login using the DESKTOP-TO\sasdema credentials provided during configuration. ‘SAS Job Monitor Mid-Tier Services Logfile + CASAS\Configl ev7\Webil agsiSASServert3._11SAS.JobMonito*MigTierSve log {le:11C:/SASIConfighLev2iDacuments/instructons.himl paar 16/2020 Configuration Guidelines and Details For more details about how to modily your lag format and to see what logging entails, see “Administering Logging for SAS Web Applications" inthe SAS intoligence Platform: Midle-Tor Administration Guide at ia Jsupoart sas. com/Séadministalion +. Login to SAS Environment Manager as sasadm@saspw, Validation 2. On Dashboard, solect your machine, and SAS DM Platform under Auto-Discovery and select Add to inventory. f notin Auto ‘steps Discovery check to see iit has already been added tothe Resource page. 3. Go ta SAS Envizonment Manager and select Analyze then Monitoring Center. ‘Search Interface to SAS Content itp dosktop-10:80/SASSoarchSorvice 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 intoligonce Platform: Midlo-Tior Administration Guide at hia lisupoart sas, com/94administation. 2 Log in using vai credentials defined in the SAS Metadata Server. 3, Very that a ist of XMLUISON links i ciplayed in the browser or downloaded as a file. If fle is downloaded, open it ina text edior to varity thal alist of resourcestins is rtumed. 4. Ifyou are testing Search through some cient application (e.g. SAS Visual Analytics Hub) and if Search Interface fo SAS Content has been installed ina separate instalation, please restart the Web Application Server having dependent Web Applications (e., 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.6 with internet browsers and other search engines, refer tothe document Intograting Search Intorfaco to SAS Contont 36, at hit /sunpot sas comidocumentationiinstalcenter94/ndex him ‘SAS Deployment Backup and Recovery Tool Tho SAS Deployment Backup and Recovery Tool synchronizes the backup and recovery of SAS metadata, the SAS Content Server repotary, ad the databases that are maneged by the SAS Web irvastucture Platform Data Server or SAS Solution Data Severs. Tho SAS Deployment Backup and Rocavery Tool doos not backup all ls in a SAS deployment Tho SAS Deploymont Backup and Recovery Tool dous nt backup all fs in tho SAS cotiguraion dectory. Nols in iho SAS instalation directory are backed Up. The SAS Deployment Backup and Recovery Tool does not ake the place of operating systom and fe system backups. Performing rogur backups ofthe SAS systom isan important part of administering the SAS 8.4 Intaligonce Pltiorm Purpose and” configuration. Backups taken by the SAS Deployment Backup and Recovery Tool shouldbe synchronized with operating ‘Scope _system and filesystem backups to ersure tha les and content can be restored to he same point in time. For mora, information, se "Best Practices for Backing Up and Restoring Your SAS Gontontin tne SAS Ilaligance Platform: Systom ‘Adminstration Guide a itllsinnor sas com/aéadminisialon Backups can onl be used in recovering the SAS deployment for which they are created. A backup ftom one SAS doployment cannot be used to recover anather SAS deployment. Recovery Using SAS Backup Manager fot supported Recovery of dala must be invoked using the command ino vibes provided by SAS Doployment Backup and Recovery Tool For more information, se the SAS Inaligonce Platform: Systom Administration Gude at administration Log directory CASAS\ConfigL evalWebiLogs'SASSevert 1\SASDeplo ‘central vaut location was nat spected dung istaaon and confguraton, Backups wil be stored ina lcal va For eachterthe path forthe local vault: SAS-confguraton-dretoryiLav/Backupault Backups ae retained for 30 days an purge automatealy ater his Baro. “ho SAS Deployment Backup and Recovery Tools configured to run senoduled backup each Sunday a 1:00am. local Configuration ° time * + See "About the Deployment Backup and Recovery Too!” in the see the SAS intelligence Platform: System Administration ute at to: leuppot sas. com9sadminstaton tolean what an snot backed up by te SAS Deployment Backup and Recovery Tool andforinfrmation about mang tne bac configuration Validation ‘steps 1. Launch the SAS Environment Manager Web Console Login using the sasacm@saspw credentals you spectied during configuration {l:11C:/SASIConfighLev2:Documents/instructons.himl 227 16/2020 Configuration Guidelines and Details 3. Click Administration in the menu bar to open the SAS Environment Manager Adminstration. 4, Open the SAS Backup Manager by cicking the Side Menu ican inthe SAS Environment Manager banner and select SAS Backup Manager. Tho SAS Backup Manager appears. Note: The SAS Backup Manager might take several minutes to load asi discovers the assets that are available for backup in the deployment 5. Inthe SAS Backup Manager, click Start Backup, 6. Very thatthe backup completes successful, Notes: + For more information about the SAS Deployment Backup Tool, see the SAS inteligence Platform: System Administration Guide at hilp/Isuppor sas.com9dadministation, + Bes practices for backing up and restoring your SAS content can be found in the SAS Ineligence Platform: System Administration Guide at bitoUsupor.s2s.comadministration, ‘SAS Decision Manager Common Mid-Tier for Decision Manager Host |desktop-10 Log files ‘SAS Model Manager Mid-Tier URL [i Log fi ilop-10:80/SASDesisionManager [CASAS\Gonfigllev2\Webil ogsiSASServertt_1SASModelManageri4 209 The SAS Deployment Wizard (SOW) does not create application users by dafault The SAS Administrator must create users in Pre-validation | the SAS Management Console witn the appropriate group anc role permissions. Ifthe sasdemo user already exists, you can ‘stops | add the user to one or more ofthe user groups in SAS Management Console, For information about how to configure users, 1OUPS and roles, see the SAS Model Manager 14.2: Administrators Gulde. Prom tho quick start tutorial in the Getting Started section of the SAS Modo! Managor 14.2: Usor’s Guido to validate your Validation | installation. steps | Note: If you have completed the valléation stops for SAS Decision Manager, then you do not need to complete any additonal validation steps for SAS Model Manager. For more information, se the SAS Model Manager 14.2: Administrafors Guide. Allof the documentation Is avaliable at the Pocumentation | rofoying UR. hip /éuppor sas com/documertalinlanlinedadmadeln Notes: + When restarting the middeter server: ® SAS Madel Manager has a dependency on the SAS Conlent Server which provides the interface to DAV that is needed by SAS Model Manager. The SAS Content Server runs as a web application ané might be running on a diferent instance ofthe application server than ‘SAS Model Manager. In most cases the star-uo ofthe applications is handled properly bu if you experience a problem where the DAV Contents not yet available just ensure that SASServer! fs up and running before starting SASServer'! (which is where the SAS Modal Manager WAR files are deployed in a mull-server environment) » You can chack to s90 whothor the SAS Content Sorvor is up and running by licking on this link hitpdidaskton. {10:80/SASConteniServercitcontens. 9 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 Mode! Manager 14.2: Administrators Guide. SAS Help Viewer for Midtier Applications URL hiipiideskton-10:80/SASWebDoc fation Use the URL above and examine thelist of product documentation. if ther stops be reportedlisted on tis page. were any erors configuring the help content, they will Web Application Custom Content Ifyou wish to add custom content info SAS web applications, refer tothe "Web Application Custom Content” section of the SAS intaligence Platform: Middlo-Tier Administration Guide located a Hip support sas.com/administation {le:f1C:/SASIConfighLev2iDocuments/instructons.himl 23107 ‘162020 Contguration Guceines and Details 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 Enterprise Guide Enabled Reports 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 14.3: Administrators Guide at hito:/support.sas.com/documentation/anlinedoctforecasl Report administration Use the following credentials to access the secure documentation pages: + User name: sas 1 Password: 00 + Name: Default °° Description: Forecast Server Default Environment © Workspace Server: SASApp2 - Logical Workspace Server Default Environment ‘© Content Location: C:\SASIConfg\L ova\ApaDatalSASForecastServert4.3 + The Content Location refers to @ path on the server ir. This path must exist on the server ter before SAS Forecast Server used. Soe the Configure Forecasting Environments on the SAS Server nates below for instructions to create the directory or folder structure + Verity thatthe SAS Forecast Server status page can be accessed successfully from htpsdaskion- 10:80/SASForecastServerSialus + The SAS Forecast Studio cient application can be used to perform additonal validation. To use this application, you mustlog into SAS Forecast Studio as a user wih an appropriate role, The available tasks depend on the user's role, Perform the folowing steps Validation steps 1. Complete the configuration instructions under the "Notes" below. 2, Launch the SAS Forecast Studio client by clicking on the Launch link onthe SAS Forecast Server status page. 3. When the SAS Foracast Studio login dalog box appears, verify that you can successfully log in Note: If there are any validation errors, check the fllowing logs: 1. SAS Forecast Server application’ log flo, SASForecastServert 3.09, 2. SAS Web Application Server Web Application Server’ log file generated during the configuration of servertt. Refer to the Web Application Server's configuration instructions forthe location ofthese logs, Configure SAS Forecast Studio Users and Roles: + Create user and product administrator accounts. 1. Creal the operating system accounts for the Forecast Server users and administrator. 2. Associate the above accounts with metadata dentles In SAS Management Console. ‘+ Assign the appropriate roles tothe Forecast Server users and administrator accounts Configure Forecasting Environments on the SAS Server: + For environments that were created during configuration or migration 4, Create the content location onthe appropriate workspace server for each confgured environment. 2 Set file system permissions 60 thal the SAS Forecast Studio users have full access tothe cantent location ofthe environment + For more information about the previous tasks and for the most current installation and configuration information, see the SAS Forecast Server 14.3: Administrator's Guide at hitosupportsas.comidocumentalion/oninedonforecast {le:f1C:/SASIConfighLev2iDocuments/instructons.himl 247 16/2020 Configuration Guidelines and Details SAS Enterprise Miner Mid-Tier Host machine desktop-10:80 ‘Administrator's _ Additonal information useful in administering SAS Enterprise Miner can be found inthe SAS Enterprise Miner 14.3 Online ‘Guide documents at htip//supgor sas.comidacumentaton/onlinedociminer/ndex hil Post The SAS Administrator must create operating system accouns for the Enterprise Miner users and create metadata identities Installation associated wih those accounts in SAS Management Console. The users must have permissions to open projects on the SAS ‘Steps Applicaton Server used for data mining ‘SASEnterpriseMiner14.2lo9 "of more details about how to macify yout log format and to see what logging entails, view the SAS 9.4 Logging Administration and Programming Gulde. Log ft + Please see the "Verily the Installation” documentation at bllpu/sunpor sas com/documentaton/adlen/emaql69529/H TMI /defaulWviewer himnOx2xdh ImufSendzBautcoshogt hin, + Verify thal the SAS Enterprise Miner Wid-Tier status page can be accessed successfully from hitau/desktor- SO:B0SASEnterpriseWinerdWS/Salus, + ifyou experience an “Unable fo Launch the Application” error when connecting Io the SAS Enterprise Miner Server via the browser, please reference bilodsut + default sas-environmentxm is enabled for validation through the SAS Enterprise Miner Java Web Star Client, Launch the SAS Enterprise Miner Java Web Slart Clan clicking on the Launch ink on the status page ‘Once this is verifed, you should tum off the default and use the recommended approach of specifying your sites own web server location for obtaining the sas-environment.xm fle. These options are speciied via properties in the SAS. Validation ‘Management Console. steps 1. Invoke SAS Management Console, goto the Plugins tab and expand the tree for Application Management >Configuration Nanager>SAS Application Infrastructure Right clek on the Enterprise Miner Mid-Tier JWS enty and select Properties ‘Once the dialog box is displayed. select the Settings tab Click on Enterprise Miner Java Vieb Start Options Enter your ste specific SAS environment URL value in he SAS environment URL fed Change the Inject default sas-environment. xml propery to false Note: In adition tothe options discussed above, other JWS options are displayed and can be controlled via property settings on this screen Note: If there are any validation eros, check the lag fle mentioned above, Notes: Poase refer to the SAS Enterprise Minor Administration and CorViguration guido to + Define SAS Enterprise Minor Users and Roles + Configure SAS Entorprise Miner sas-environments.xm on the SAS Server SAS Text Miner Client ‘Administrator's Additonal information useful in administering SAS Text Miner can be found inthe SAS Text Miner 14.3 Ontine documents at Guide _hitpu/sunpor.sas.comidocumentationvonlinedac/xminerlindex, hin, Post- The postinstallaton step for Text Miner is needed on Windows servers forthe ttmfter macro. No post.nstallation step is tion needed for Ytmfitr on Unix servers. ‘Steps Enable the XCMD Option ‘SAS Text Miner includes a macro called %cTMFILTER. When running on Windows, the cmd option must be set in any SAS Session setup lo run the macro. For mast desktop installations of SAS, this option wil already be set and %TMFILTER can run locally by default But when cunning the SAS Entorprise Miner Java cient, %STMFILTER wil be run on tha sarver with the SAS session as specified by the Object Spawner. Because the server's configured by defauk ta disallow the -xemd option, the following steps must be taken fo enable this option. Insta XCMD Option ‘The XCMD option, the ability to submit "x" operating system commands from a SAS process, is necessary forthe proper functioning of the %sTMFILTER macro, Because this option fs disabled by default on @ Windows server. is necessary to modify ‘the abject spawmer controls and add the invocation parameter -allowxemd tothe object launch 4. Stop the Object Spawner by stopping the service or canceling the ser 2. Back up then edt ObjectSpawner-bat. The default location for ObjectSpawner-bat Is C:\SAS\iplan name) [Levindbjectspawner. 43. Ect the ObjactSpaver bat fil by adcing the option -llowxcmd betore the 2xmiconfgile option. There is one instance of ‘he -xmicorfifl option in the ObjectSpawnar-bat fe. 4, Save changes. fle: 11€:/SASIConfigiLev2:Documents/instructons.himl 25127 16/2020 Configuration Guidelines and Details 5. insted a8 service, perform stops 6-8, Please note tat this might be necessary you are runing sorts an you sti Tecetve te sare err aftr tying ape 14 6 Ina Command window, go tot Object Spawner rectory your application server drectry or your corigurain, For xem EASAS\pan namef\LevthObjectSpanner 7. Typein sjectopawna remove o remove te existing serves 8 Type in aojectspawn instal fo resnstal he new service 8 Star the Object Spawnerby service star or sorb ‘SAS Time Series Studio Mid Tier SAS Time Series ‘Studio Mid Tier desktop-10 Host + Name: Default Defauit °° Description: Time Series Studio Default Environment Environment © Workspace Server: SASApp? - Logical Workspace Server © Content Location: C\SAS\Config\Lev2\AppDatalSASTimeSerlesStudioMidTiert4.3, + Verity thatthe SAS Time Series Studio Mid Ter status page can be accessed successfully rom biiolidaskton- 10 B0/SASTimeSeriesStusioMioTien/Stalus, + The SAS Time Series Studio clint application can be used to perform addltionsl validation. To use this application, you must log in to SAS Time Series Studio as a user with an appropriate role. The available tasks depend on the user's role, Perform the following steps: 1. Complete the configuration instructions under the "Notes" below. Validation Stops 2 Launch the SAS Time Series Studia clont by cicking on the Launch link on the SAS Time Series Studio Mid Tier status page, 3 When the SAS Time Series Studio login dialog box appears, verfy that you can successful agin. Note: If there are any validation errors, check the following logs: 41. SAS Time Sories Stuclo Mid Tier applications log fle, ‘CASAS Config ev2WebiL ogs\SASServer!t_1\SASTimeSeriesStudioMidTier14.3 og, 2. SAS Web Applicalion Server Web Appiialion Server's log fle generated during the configuration of server. Refer to the Web Application Server's configuration instructions for the location of these logs. Notes: Configure SAS Time Series Studio Users and Roles: + Create user and product administrator accounts. 4. Create the operating system accounts for the Time Series Studio users and administrator. 2. Associate the above accounts with metadata identities in SAS Management Console ‘+ Assign the appropriate roles tothe Time Series Stucio users and administrator accounts. Configure Time Series Studio Environments on the SAS Server: + For anvronments that were created during configuration: 4. Creale the content localion on the appropriate workspace server for each configured environment, 2. Set fle system permissions so thal the SAS Time Series Studio users have full access tothe content lcation ofthe environment Additional Information: + For more information about the previous tasks and forthe most current installation and configuration information, see the SAS Time Series Studio 14.3: Administrator's Guide at hiplsunr imentationoaln SAS Metadata Bridges The SAS Metadata Import or Export function of SAS Management Console and SAS Data Integration Studio wil prompt forthe location of a SAS liconse ile. Therefae, a valid SAS license fle must be accessible from the client machine. The license file may be availabe inte sid_fles directory atthe root of your SAS Software Depot or it may be included witn your SAS Software Order E-mai. fits with your SAS Software Order E-mail then You shoul follow the instructions included in that e-mail for wnere and how fa store your SAS license fle Obtaining Additional Information {le:f1C:/SASIConfighLev2iDocuments/instructons.himl 26127 1516/2020 Configuration Guidelines and Details ‘Additional SAS Inteligence Platform documentation is available from the SAS 9.4 administration documentation web ste, There may be additional configuration steps required for your SAS Foundation software. Consult the SAS Foundation Configuration instructions available for your operating system for praduct-spectic postinstalation steps. The configuration instructions are available fom the SAS Install Center web ste Backing Up Your SAS Deployment ‘The SAS system now includes a Deployment Backup utity that can back up the following components of your SAS deployment: + the metadata server {selected data and configuration directories on any SAS server tor 1 the SAS Content Server repository + any SAS Web Infrastructure Data Server databases + custom directories configured for your ste Ifthe Deployment Backup uit is configured on your system, it wil automatically run every Sunday at 1 a.m. The automatic backup schedule can be changed or disabled. For more information, se “Using the Deployment Backup and Recovery Toot in the SAS Inteligence Platform: System Administration Guide at bilisupot sas com 34adminsiralion, Caution: Regular backups of your SAS system are crucial to ensuring the heath of our SAS 84 Intellgence Platform configuration. tis recommended that you schedule regular system backups to occur jus 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 Inlaligence Platform: System Administration Guide at hislisuppon sas corn/Sdadministation, Copyright © 2017, SAS Insttute Inc., Cary, NC, USA, All Rights Reserved fle: 11C:/SASIConfighLev2:Dacuments/instructons.hml 21

You might also like