GC 11.1.0.1-Install jdk1.6 0n Linux x86_64 Before Install WLS 10.3.2_1063587.1
Case Study - Installing Grid Control 11.1.0.1 - Installation of jdk1.6 0n Linux x86_64 Before Installing WebLogic Server 10.3.2 (Doc ID 1063587.1)
In this Document
Goal |
Solution |
References |
Applies to:
Enterprise Manager Base Platform - Version 11.1.0.1 to 11.1.0.1 [Release 11.1]
Linux x86-64
Checked for relevance on 12-APR-2013
Goal
Last reviewed August 3, 2010.
The installation of Grid Control 11.1.0.1.0 requires an existing WebLogic Server 10.3.2 installation on Linux x86_64. WLS on this platform is installed from a source that does not contain an embedded jdk, so one must be provided. A example of how to obtain and install this jdk is described below.
A step-by-step description with graphical representation of the installer progress is available here.
For details concerning installation of the required jdk on platforms other than that represented in this example, please see this reference:
Note 1106105.1 Grid Control 11g: Required External Components and Versions for Grid Control 11.1.0.1.0
Solution
A) Prerequisites:
1) WLS 10.3.2 for 64bit platforms is supplied as a generic .jar file: wls1032_generic.jar
The java from jdk 1.6 must be used to install WLS, but this java is not embedded in the WLS stage on the 64bit platforms and must be downloaded and installed separately. Please note that a jdk location (not jre) is sourcing java in this case. The Linux x86_64 example shown here will use this same generic WLS source.
2) The jdk used to install WebLogic Server must be used to operate Grid Control/WLS from this point forward. It should not be updated or upgraded.
3) The jdk installation should be preserved and referenced for future actions, so install in a suitable location for posterity. Oracle recommends that this location be inside an Oracle software location (i.e. .../Middleware) to provide a basic measure of security.
B) Procedure:
1) Installation Source
Download jdk 1.6 from Oracle/Sun for the Linux x86_64.
This resulting file can be used to install the required jdk on Linux x86_64, example:
It can be placed in a directory convenient for later use of the jdk, example:
Refer to the Oracle Enterprise Manager Grid Control Basic Installation Guide 11g Release 1 (11.1.0.1.0) for list of support JDK versions:
==================================
Ensure that you have the following version of JDK installed on the host where you are planning to install Enterprise Manager Grid control.
* Linux Platform (64 Bit): SUN JDK 1.6_18+
(On Linux 32-bit platforms, you need not install JDK because it is packaged by default with Oracle WebLogic Server)
* Solaris Platform: SUN JDK 1.6_18+
* HP-UX Platform: JDK 6.0.05+
* AIX Platform: JDK 1.6.0 SR6
* Microsoft Windows Platform (64 Bit): SUN JDK 1.6_18
==================================
2) Command Format
Execute the extraction and installation with this command as oracle (example):
./jdk-6u18-linux-x64.bin
The resulting jdk will be located in the directory with the .bin file, so locate the .bin file appropriately:
/u02/jdk16/jdk1.6.0_18/
3) License Agreement
The installer will bring up a lengthy License Agreement to review.
A carriage return will be required many times to get to the end of the license terms and the agreement prompt.
At the end of the license terms, enter "yes" in the agreement prompt to extract and install the jdk.
4) Finish Installation
At the end of jdk installation, press "Enter".
A web page will be presented that can be reviewed or dismissed.
5) Installation Results
Back in the command session, the jdk installation is complete and has returned an OS prompt.
Notice the extracted jdk directory in the same location as the stage (example):
/u02/jdk/jdk-6u18-linux-x64.bin
Looking deeper, observe the java that is required is located under the .../jdk1.6.0_18/bin/ directory.
This will be the java used for WebLogic Server installation in support of Grid Control installation on this host.
6) Verification of java version
A simple version verification shows that the jdk is ready for use:
Java versions "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)

來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/17252115/viewspace-1243692/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- before install octave package you must be install gcc-fortranPackageGC
- WLS中Linux與Windows間的環境共享LinuxWindows
- Mysql 5.7.21 install for LinuxMySqlLinux
- linux之--install超時Linux
- 02. Install redis on LinuxRedisLinux
- Install linux mint apt to Ubuntu 18.04 LTSLinuxAPTUbuntu
- Linux下python pip install失敗LinuxPython
- install java javac on kali linux, raspberry piJavaLinux
- Rocky Linux 9.5 x86_64 OVF (sysin) - VMware 虛擬機器模板Linux虛擬機
- WLS + Windows Terminal +Phpstorm + Xdebug 開發環境WindowsPHPORM開發環境
- SQLServer2017_Install_for_CentOS Linux release 7.5SQLServerCentOSLinux
- Oracle Linux 7.1 silent install 19cOracleLinux
- Oracle Linux 7.1 silent install 19C RACOracleLinux
- [CSS] 偽元素和偽類,::before 和 :before 區別CSS
- Linux: Centos7 Cannot find a valid baseurl for repo: base/7/x86_64 解決方案LinuxCentOS
- Full GC (Metadata GC Threshold)GC
- 從CLR GC到CoreCLR GCGC
- linux下使用npm install報EACCES的解決方法LinuxNPM
- Linux安裝Redis 6.0.5 ./install_server.sh報錯LinuxRedisServer
- x86_64系統呼叫過程
- GCGC
- GC.MaxGeneration屬性【GC示例】GC
- go install: no install location for directory outside GOPATHGoIDE
- semantic-ui@2.4.2 install: `gulp install`UI
- 編譯OpenCV——ubuntu x86_64平臺編譯OpenCVUbuntu
- solaries作業系統安裝64位JDK1.6作業系統JDK
- jstat命令檢視jvm的GC情況 (以Linux為例)JSJVMGCLinux
- 偽元素 before 和 after 初探
- css偽元素(before與after)CSS
- pip install 提示:Could not install packages due to an EnvironmentErrorPackageError
- 如何處理錯誤訊息Please install the Linux kernel header filesLinuxHeader
- GC是什麼?為什麼要有GC?GC
- JVM 系列文章之 Full GC 和 Minor GCJVMGC
- install qdrant
- Install clickhouse
- habitat install
- macOS OpenCV報錯:Undefined symbols for architecture x86_64MacOpenCVUndefinedSymbol
- Cannot find a valid baseurl for repo: base/7/x86_64
- jdk1.6升級jdk1.8踩出的神坑JDK