Pre-Installation Steps for JBoss, WebLogic, and WebSphere Application Servers with SASŪ 9.2

This page describes the necessary steps that must be performed before running the SAS Deployment Wizard, and before the installation of JBoss, WebLogic, and WebSphere Application Servers with SASŪ 9.2.

Increasing the Per Process Limit on Open File Descriptors

SAS recommendeds increasing the per process limit on the number of open file descriptors to at least 10240 on UNIX platforms. This is required when running Java 5 to allow the opening of class files within the various SAS Web applications. Before modifying any system resource settings, determine the current hard limit for the machine by running ulimit -Hn. The ulimit shell command displays the current limits for a particular system. HP-UX users can also use the command /usr/sbin/kctune -q maxfiles to display the system's open file descriptor limit. You might need to ask your system administrator to increase it if the ulimit command reports the limit to be too low. Changing the limit requires root privilege.

An example where the number of file descriptors needs to be increased:

$> ulimit -Hn

An example where the number of file descriptors does not need to be increased:

$> ulimit -Hn
Note for WebLogic Server users: When the value for open file descriptors is "unlimited," the common WebLogic Server configuration script throttles back that number to 1024. If you are allowing SAS Deployment Wizard to configure your WebLogic Server domain, the SAS wrapper script, sets this value to 10240 before calling Setting the value to 10240 before calling the script prevents the script from throttling the value back further. If you are manually configuring your domain, you can either use the SAS wrapper that is generated for the sample domain as an example, or you can modify this value yourself in <BEA_HOME>/weblogic92/common/bin/

Setting ulimit on Linux

Increasing open file descriptors on Linux is accomplished by changing the /etc/security/limits.conf file and then rebooting the machine. Changing the configuration file requires root privilege.

Add a line to limits.conf that reads:

* - nofile 10240
For more information, see this FAQ entry for details.

Setting ulimit on Sun Solaris

Increasing open file descriptors on Sun Solaris is accomplished by setting rlim_fd_max in the /etc/system file. For more information, see this FAQ entry for details.

Setting ulimit on IBM AIX

Increasing open file descriptor limit on IBM AIX is accomplished by changing the /etc/security/limits file and then rebooting the machine.

Add a line to limits that reads:

nofiles = 10240

Setting ulimit on HP-UX

The tuneable kernel parameter maxfiles_lim is used to set the hard limit for the maximum number of files which can be open per process on HP-UX systems. The HP-UX command kctune can be used to display and modify kernel tuneable parameters. SAS recommends that you use kctune to modify the value of the kernel parameter maxfiles_lim to 10240.

An example of increasing the maximum open file limit on HP-UX using kctune:

# kctune maxfiles_lim=10240

IBM AIX 6.1 Update for Multicast Networking

SAS 9.2 software uses multicast networking in the SAS Remote Services application. IBM has identified that AIX 6.1 systems might require updates to support multicast networking correctly. Review the IBM support note for APAR IZ35571. If necessary, apply the appropriate fix pack from the IBM support Web site for the issue.

A symptom of the problem is an entry in the Web application server log that is similar to the following example:
16:25:16,648 ERROR [SimpleCache] Required entry, '/sas/properties/environment', not found in the cache.
16:25:16,648 ERROR [SimpleCache] Possible causes include: the RemoteServices VM is not started or
16:25:16,648 ERROR [SimpleCache] there is a multicast address/port mismatch; using
16:25:16,648 ERROR [SimpleCache] address=239.nn.nn.nn and port=nnnn.

Note: The previous error message indicates a communication failure between the SAS Remote Services application and SAS Web Infrastructure Platform Applications. Therefore, the multicast networking issue associated with IBM AIX 6.1 is not the only cause of the message.

Installing WebLogic Server on 64-bit Platforms

On platforms that use a single Java Development Kit binary to provide 32-bit and 64-bit modes, make sure that you install WebLogic Server in 64-bit mode with the -d64 parameter. See the following example:

$> java -d64 -jar server922_generic.jar

If WebLogic Server is accidentially installed on 32-bit on a 64-bit platform, then the SAS Deployment Wizard fails to configure WebLogic Server. The error message is NodeManager failed to start..

On 64-bit Windows, if the WebLogic download comes with the .exe and .jar installation files, the .jar file must be used to install WebLogic.

Configuring an Alternative Database for SAS Shared Services

The SAS Shared Services Web application uses a JDBC data source. The default configuration is for the Web application to use a connection to a SAS Table Server. If you prefer to use a different database, then refer to Configuring an Alternative Database for SAS Shared Services.