BookmarkSubscribeRSS Feed
Fluorite | Level 6

I have next to no experience with complex SAS installation's administration, but need to research the use of a stored processes and the SAS Stored Process Web Application to potentially migrate a SAS/IntrNet-based [fully functioning, mature production] application to this setup.


So I have set up the much more complicated SAS environment needed. During the setup I have chosen to not configure and deploy the SAS Web Server product since I prefer to use my existing Apache Web Server setup (our client wishes to use Apache as well). The instructions state that I should "deploy the sas-environment.xml file located in [configurationpath]\sas-environment.xml to an HTTP server within your computing environment." 


I have not clue how to do that. Can you let me know how to perform this deployment using the xml file?


Also it seems that some sort of SAS Web Server is actually deployed (even though the configuration guidelines after install do not state that) on port 8080, i.e., if I type http://[mycomputer]:8080/SASStoredProcess gets me to the stored process examples. Can somebody either tell me or point me to the right resource that tells me where HTML, CSS and JavaScript files to, so they can be served as content by the SAS Web Server? This would at least allow me to continue some testing.


SAS/IntrNet is a piece of cake compared to this setup 🙂


Thank you for any pointers, 


Super User

The SAS webserver is just an adapted variant of apache 2.2. You can easily use the binary with a different config.

I have it installed and use it for the SAS services (port 7980, started from the SAS install user), and in a second instance as the main server (port 80, started from root and using user nobody)

The web application server is also just an adapted tomcat.

Rhodochrosite | Level 12



There is just one important issue I would like to point out to you. SUPPORT!!

If you decide to deviate from using the Standard Installation & Configuration setup recommended by SAS Institute, then you are most likely


- Not be able to easily apply future Hotfixes that touches the Web-Tier components, including the SAS Web Server, and other SAS components/modules

- Not be able to easily follow documented instructions related to Starting/Stopping the Services, Custom Branding, ...etc

- Not be able to easily follow SAS Tech Support guidance, or even allow SAS Tech Support to replicate your issues in order to help you with resolution(s)


This is just an advice from fellow SAS/Admin, the decision is ultimately yours,



Amethyst | Level 16

Hello @beate,


I would consider carefully the recommendation by @AhmedAl_Attar. A good one.


Additionally to this recommendation, some information:


  • If I understand you well, you are deploying SAS 9.4
  • 9.4 deploys a minimum of a SAS Web Server (aka Apache) and a SAS Web Application Server (at least)
  • If you do, while the SAS Web Application Server will listen on port 8080 (as you said, you will have a SAS Web Server, normally running on port 80 (http) or 443 (https), or if you are on Linux, they would be most likely 7980 (http) or 8443 (https). 
  • This SAS Web Server will be your Content Server, and every static file can be copied to your Config/Levx/Web/WebServer/htdocs folder, and the config you have on your existing Apache server, I am pretty sure you can replicate it on the SAS Web server configuration files on Config/Levx/Web/WebServer/conf folder. If you have trouble integrating your modification, please ask the support of SAS Technical Support and/or an experienced Apache admin.
  • Finally, you would be happy to read that SAS actually support the integration of external Web Servers acting as Reverse Proxies


Hope that this helps.


Kind regards.


Fluorite | Level 6

Thank you all for your responses. As you can tell, I am not a SAS administrator, so your advice is much appreciated!


I have been able to figure out how to set things up, so I can develop Stored Process based Web Apps using the recommended SAS setup (i.e., the SAS Web Server), but at the same time retain my preferred setup for the SAS/IntrNet clients I am supporting. There is so much documentation out there, and a lot of it is completely irrelevant, so it takes some time to dig through and find the bits that are important. Thank you again!

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 4 in conversation