Problem Note 52324: In SAS® Digital Marketing, the range of ports opened between the bess.war server and the SAS® Digital Marketing server needs to be controlled
In SAS Digital Marketing, the range of remote method invocation (RMI) ports opened between the bess.war server and the SAS Digital Marketing server needs to be controlled. The bess.war server uses random ports. This might be unacceptable to customers, particularly when a firewall exists between the servers.
Click the Hot Fix tab in this note to access the hot fix for this issue.
After you apply the hot fix, specify the following properties as command line options of the Java invocation for the bess.war server and the SAS Digital Marketing server, as shown in the following example:
-DCustomSocketFactory=true
-DSocketStart=30000
-DSocketEnd=30500
The range of ports in use should be identical for both servers. Ensure that the range of ports is opened in your firewall. Ensure that the range of ports is a sufficiently high number to allow for the maximum number of concurrent connections that might be required.
Operating System and Release Information
SAS System | SAS Digital Marketing | Microsoft® Windows® for x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows 8 Enterprise 32-bit | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows 8 Enterprise x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows 8 Pro 32-bit | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows 8 Pro x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows 8.1 Enterprise x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows 8.1 Pro | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows 8.1 Pro 32-bit | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows Server 2003 Datacenter Edition | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Enterprise Edition | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 Standard Edition | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2003 for x64 | 6.1_M1 | | 9.3 TS1M2 | |
Microsoft Windows Server 2008 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows Server 2008 R2 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows Server 2008 for x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows Server 2012 Datacenter | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows Server 2012 R2 Datacenter | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows Server 2012 R2 Std | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows Server 2012 Std | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Microsoft Windows XP Professional | 6.1_M1 | | 9.3 TS1M2 | |
Windows 7 Enterprise 32 bit | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Windows 7 Enterprise x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Windows 7 Home Premium 32 bit | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Windows 7 Home Premium x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Windows 7 Professional 32 bit | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Windows 7 Professional x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Windows 7 Ultimate 32 bit | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Windows 7 Ultimate x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Windows Vista | 6.1_M1 | | 9.3 TS1M2 | |
Windows Vista for x64 | 6.1_M1 | | 9.3 TS1M2 | |
64-bit Enabled AIX | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
64-bit Enabled HP-UX | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
64-bit Enabled Solaris | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
HP-UX IPF | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Linux for x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
Solaris for x64 | 6.1_M1 | 6.3 | 9.3 TS1M2 | 9.4 TS1M1 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2014-03-05 16:00:59 |
Date Created: | 2014-02-13 06:49:01 |