The SAS Digital Marketing sas.conf file might be overwritten when a hot fix is applied. The sas.conf file contains the ProxyPass and ProxyPassReverse BESS access.

When you apply a hot fix, these settings might be overwritten and deleted. As a result, access to the BESS server fails. If you deploy the BESS server on any of the SAS servers (SASServer1-SASServer6), you need to create a separate .conf file to work around this problem. Follow these instructions:

1. On the machine where the BESS server is installed, navigate to your Lev1\Web\WebServer\conf\ directory (for example, D:\opt\sasinside\Config\Lev1\Web\WebServer\conf).
2. Use a suitable text editor (for example, Microsoft Windows TextPad or Notepad) to create a new file named bess.conf in that directory.
3. Add the following entries to the file:
   

   Proxy Pass /bess balancer://my.server.com_SingletonX/bess
   ProxyPassReverse /bess balancer://my.server.com_SingletonX/bess
   
   <Proxy balancer://my.server.com_BessServer>
   BalanceMember
   http://<hostname>:<port>
   </Proxy>

4. Save the file.
5. In the same directory, modify the httpd.conf file and add the following line at the bottom of the file:
   

   Include conf/bess.conf
   

6. Save the file.
7. Restart the SAS^® Web Application Server in order to activate the sas.conf file change.
8. Restart the SAS Web Application Server node into which you deployed bess.war in order to activate the new bess.xml file in Apache Tomcat Catalina.

Operating System and Release Information