8.1 Supported Configurations: Sun Solaris 9 on SPARC

Sun Solaris 9 on SPARC with WebLogic Server 8.1

Provides full support for WebLogic Server. WebLogic Workshop, WebLogic Integration, and WebLogic Portal are not supported. See below for Design and Development Tools support.

This section provides the following information:

Related Information

For information about supported database configurations, Web servers, and browsers, plus support for interoperability tools and WebLogic Platform product support information, see WebLogic Platform 8.1 Supported Configurations.
For details about Sun Solaris 9, visit Sun's Solaris Web page at: http://www.sun.com/solaris.
For Sun's support services information site, see http://www.sun.com/service/support. If you have a support contract for the use of Solaris platforms, you may be able to obtain support for general Java issues (for example, SDK problems).
For information on suggested values for some Solaris TCP and VM-related tunable parameters, see WebLogic Server Performance and Tuning.

Configuration Requirements

Table 7-1 Requirements for WebLogic Server 8.1 on Sun Solaris 9 on SPARC

Operating System Version and Patches	Solaris 9
Chip Architecture and Minimum Processor Speed	UltraSPARC (168 MHz)
SDK	Sun Java 2 SDK 1.4.1_02-er (32 bit)	WebLogic Server 8.1 supports Sun Java 2 SDK 1.4.1_02-er and all later service packs of 1.4.1. Supports the Java HotSpot^TM Client and Server VMs.
Design and Development Tools	The WebLogic Workshop IDE is not supported on Sun Solaris systems. Sun Solaris is supported for the production deployment of applications developed in the WebLogic Workshop IDE, and for remote debugging of applications developed in the WebLogic Workshop IDE. Sun Solaris is also supported for the development and production deployment of WebLogic Server applications developed with other tools.
RAM	512 MB required; 1 GB recommended
Performance Pack	Included	`lib/solaris/libmuxer.so`
Node Manager	Included	Native
BEA jDrivers for Oracle	For this Oracle client version:	The following shared libraries are provided:
	Oracle 8.1.7.4	`lib/solaris/oci817_8/libweblogicoci39.so` `lib/solaris/oci817_8/libweblogicoxa39.so`
	Oracle 9.0.1.4	`lib/solaris/oci901_8/libweblogicoci39.so` `lib/solaris/oci901_8/libweblogicoxa39.so`
	Oracle 9.2.0.3	`lib/solaris/oci920_8/libweblogicoci39.so` `lib/solaris/oci920_8/libweblogicoxa39.so`

Known Issues

Issue	Workaround
BEA has discovered that some Solaris JVMs report an incorrect IP number. The reported IP number for the machine is the first number in the `/etc/hosts` file. Unfortunately, the first number in `/etc/hosts` is frequently `127.0.0.1`, the standard loopback network address for the machine. This problem affects licenses, where a license is granted for a specific IP number. This problem also occurs in a cluster in which an HTTP request is passed by a Web server or another WebLogic Server, via the HttpClusterServlet, to a WebLogic Server running on a Solaris machine with this configuration problem. The `127.0.0.1` IP number is carried with the server's response. Subsequent calls to that machine time out because of the incorrect IP number.	To determine whether this problem exists on your Solaris system, run the following command: `java utils.netAddresses` If you see `127.0.0.1` in the output, ask the system administrator to move the computer's network IP address to the beginning of the `/etc/hosts` file.

Issue

Workaround

BEA has discovered that some Solaris JVMs report an incorrect IP number. The reported IP number for the machine is the first number in the /etc/hosts file. Unfortunately, the first number in /etc/hosts is frequently 127.0.0.1, the standard loopback network address for the machine. This problem affects licenses, where a license is granted for a specific IP number.

This problem also occurs in a cluster in which an HTTP request is passed by a Web server or another WebLogic Server, via the HttpClusterServlet, to a WebLogic Server running on a Solaris machine with this configuration problem. The 127.0.0.1 IP number is carried with the server's response. Subsequent calls to that machine time out because of the incorrect IP number.

To determine whether this problem exists on your Solaris system, run the following command:

java utils.netAddresses

If you see 127.0.0.1 in the output, ask the system administrator to move the computer's network IP address to the beginning of the /etc/hosts file.

For more information about known issues with this release, see the WebLogic Server 8.1 Release Notes, available at:

http://download.oracle.com/docs/cd/E13222_01/wls/docs81/notes/index.html