Post-Installation Steps for JBoss, WebLogic and WebSphere Application Servers with SAS^® 9.3

SAS middle-tier applications make use of JGroups software and the 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. Multi-homed machines usually have more than one address because they have more than one network interface controller (NIC) 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 the method InetAddress.getLocalHost().getHostName() as the bind address for use by JGroups. If the two bind values do not match, that is, 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 does not function correctly.

To force JBoss and JGroups to use the same bind address, you need to add the following JVM option both to the JBoss application server and to SAS Remote Services:

In this option, ip-address should be replaced with an actual IP address, as shown in the following examples:

• -Djgroups.bind_addr=10.10.10.1
• -Djgroups.bind_addr=localhost

For details about setting this option for JBoss and SAS Remote Services, see SAS Note 35086. See also System Properties Supported by JGroups (2.4 and higher).

SAS recommends that you use the HPjconfig tool to verify that the values of your tunable kernel parameters are optimal for WebLogic and JBoss. For more information about HPjconfig, see HPjconfig Downloads and Documentation.

If you configure your system with a large base_pagesize parameter using the Tunable Base Page Size feature that is provided in HP-UX 11i v3, you should read the Hewlett-Packard document, Tunable Base Size Page.

When you automatically configure 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 manually configure your managed servers.

When you manually configure SAS web applications, there are no strict requirements as to how the web applications can be distributed. A more detailed discussion about tuning the performance of your middle-tier topology is available in SAS 9.3 Web Applications: Tuning for Performance and Scalability.