SAS middle tier applications make use of JGroups and JBoss Cache for inter-application communication and caching of application properties. The JGroups software uses UDP multicasting as its communications protocol. Using this protocol, the JGroups software must be able to bind to a valid address and port combination. Multihomed machines usually have more than one address (by having more than one NIC, networking card, installed). By default, the JGroups software selects the first non-loopback NIC as its bind address. However, in some cases, the Web application server can select the value of InetAddress.getLocalHost().getHostName() as the bind address for use by JGroups. If the two bind values do not match, the value chosen by JGroups for the SAS Remote Services application and the value chosen by the Web application server for the SAS Web applications, the JGroups communication protocol will not function correctly.
To fix this problem, users can add the following JVM option to force JBoss and JGroups to use the same bind address:
For more information, see System Properties Supported by JGroups (2.4 and higher).
SAS recommends that you use HPjconfig to verify that the values of your tunable kernel parameters are optimal for WebLogic and JBoss. For more information about HPjconfig, see http://www.hp.com/products1/unix/java/java2/HPjconfig/index.html.
If you have configured your system with a large base_pagesize parameter using the Tunable Base Page Size feature provided in HP-UX 11i v3, read the following HP document, http://docs.hp.com/en/14670/ENW-TBPS-TW.pdf. Based on the information in the HP document, SAS recommends that you install and configure Java version 5.0.13 or later.
If your SAS middle tier servers are installed on HP-UX and you want to save SAS Enterprise Guide projects to SAS Folders, you must update the JDK on those middle tier servers to 5.0.14 or later.
When automatically configuring Web application servers for use with SAS applications, the SAS Deployment Wizard provides an option to distribute the SAS Web applications across multiple managed servers. This option is not available in the deployment wizard if you choose to manually configure your managed servers.
When you manually configure the SAS Web applications, there are no strict requirements as to how the Web applications can be distributed. A more detailed discussion about performance tuning your middle tier topology is available at SAS 9.2 Web Applications: Tuning for Performance and Scalability.
Note: For WebLogic Server on HP-UX on Itanium or Sun Solaris on x86-64, the manual instructions that are generated by the SAS Deployment Wizard will instruct you to create two managed servers and will suggest which server to deploy each application to. The recommended split is the same for all operating system platforms and all supported Web application servers. If you want to follow this recommendation for any Web application server, see this sample of the generated instructions for application assignment.