8.1 Supported Configurations: Sun Solaris 10 on SPARC
Sun Solaris 10 on SPARC with 8.1 SP6
BEA also supports WebLogic Integration 8.5 SP6 on this configuration.
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 the appropriate Supported Configurations document:
- For details about Sun Solaris 10, 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 about suggested values for some Solaris TCP and VM-related tunable parameters, see WebLogic Server Performance and Tuning.
Configuration Requirements
Table 1-1 Requirements for 8.1 SP6 on Sun Solaris 10 on SPARC
Operating System Version and Patches
|
Sun Solaris 10
|
Chip Architecture and Minimum Processor Speed
|
UltraSPARC (168 MHz)
|
SDK
|
|
Design and Development Tools
|
The WebLogic Workshop IDE and WebLogic Integration Format Builder are 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 9.2.0.4 and later patch sets
|
|
Known Issues
Issues When Using the Azul Virtual Machine
- The Azul Virtual Machine supports only Type 4 JDBC drivers.
- To enable native I/O, specify the following flag on the
java
command line when starting WebLogic Server:
-XX:+WL81NativeIO
- The default number of open file descriptors allocated for the JDK may be insufficient for the Azul Virtual Machine.
In most circumstances the number of open file descriptors allocated, in the proxy machine, for the SDK should be at least three times the number of file descriptors allocated for BEA JRockit. If you are going to run file-intensive operations, be sure to allocate seven to eight times the existing value for the number of open file descriptors in the proxy machine. If no value has been set, set the value to 8192.
To change the specified number of open file descriptors, enter the ulimit -n
command. For example, if the number of file descriptors allocated for BEA JRockit is 1024, raise that number to 8192 by entering the following command:
ulimit -n 8192
Note: Keep in mind that the BEA WebLogic jDriver has been deprecated in WebLogic Platform 8.1. BEA does not support the use of the WebLogic jDriver with WebLogic Server 8.1 SP6 with the Azul Virtual Machine.
Related Information
Download, Installation, and Configuration Instructions
To install WebLogic Platform on your Solaris 10 system, follow the instructions provided in Installing BEA WebLogic Platform:
http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/index.html
Note: If you want to use the Solaris Zones feature, you must implement a few configuration requirements during the installation of WebLogic Platform. Therefore, if you plan to use this feature, read the instructions in Configuring Your WebLogic Platform Installation for Multi-Zone Operation before launching the installer.
Configuring Your WebLogic Platform Installation for Multi-Zone Operation
WebLogic Platform can be run in multiple zones of a Solaris 10 system, as long as the product is installed and configured to accommodate the Solaris Zones feature. To prepare your WebLogic Platform installation to accommodate Solaris Zones, complete the following procedure:
- During the installation of WebLogic Platform, specify a directory to which all zones will have access.
Note: BEA strongly recommends this step so you can avoid installing WebLogic Platform in the default root file system. If WebLogic Platform is installed in the default root, all zones will require write access to root and such widespread write access is not recommended.
- Define a separate WebLogic Platform or WebLogic Server domain for each zone so that the log files for each zone can go to a different location. If you choose, you can also configure a cluster to work across multiple zones as long as you provide read, write, and execute permissions to the domain directory to all the local zones participating in the cluster. For more information, see "Overview of WebLogic Server Domains" in Configuring and Managing WebLogic Server:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/adminguide/overview_domain.html
Service Migration on Solaris Zones
The following WebLogic Server migratable services are not supported on Solaris Zones:
- Activating JTA as a migratable service
- Deploying a JMS server on a migratable target