In SAS Digital Marketing, you can use the double bess.war architecture. This architecture consists of one external bess instance, sited outside of your firewall and acting as a proxy server, and another instance inside your network.

In a double bess.war architecture, the external bess_proxy configuration files are not created correctly. This problem occurs during the configuration process at installation and also as part of the hot-fix application process.

To work around this problem, once the bess_proxy has been configured or re-configured, locate the bess_proxy.ear in your SAS-configuration-directory\Lev1\Web\Staging\ staging directory. Locate the application.xml file in bess_proxy.ear\META-INF\ file. Using a suitable text editor, modify the application.xml file, replacing the incorrect web-uri reference to bess.war with the correct reference bess_proxy.war, as detailed below:

Operating System and Release Information