This is pretty much identical to a WebLogic 11g installation, but I decided to post separately as this includes details of the PSU appropriate to this WebLogic 12.1.1 installation, a potential gotcha with the H675 patch, and I’m using Oracle JDK 7.
I’m assuming here that the “oracle” user, groups etc. have already been created here. If not, take a look at “Create oracle user and groups” under my Linux installation post here.
I’m using the WebLogic 12gR1 generic package installer (used for all 64-bit JVM installs) to do this installation on Linux 6.4, with Oracle JDK 7 (u21). If you’re using a 32-bit package installer, this will already contain the appropriate JDK.
Oracle JDK 7 install
To install Oracle JDK 7, download the latest version for Linux x86-64 here and then install the RPM as root:
cd /u01/app/oracle/software rpm -ivh jdk-7u21-linux-x64.rpm
NOTE: I tried using WGET to fetch the file, but Oracle want you to accept the license terms before downloading. Supplying a single cookie header with the WGET command failed to work for me too 🙁
Now logged in as oracle again, set your environment and make sure Java is referencing the new JDK path:
export JAVA_HOME=/usr/java/jdk1.7.0_21 export PATH=$JAVA_HOME/bin:$PATH java -version
Before you start the install, it’s worth pointing out that I had issues with the GUI when using X-Sessions from my Windows machine via Xming and PuTTY. It looks like a Java 7 specific issue (as I tried other versions, and Java 6 worked OK), but occasionally the GUI wouldn’t let me type or select things at certain stages. If I ran the installer from the Linux machine directly, or via VNC, it worked as expected though.
Start the WebLogic install
You can download the wls1211_generic.jar file here.
Start up the installer:
cd /u01/app/oracle/software export USER_MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=350m" $JAVA_HOME/bin/java -d64 -Xmx1024m -jar wls1211_generic.jar Extracting 0%.............
NOTE: You need to use the -d64 flag above when using 32/64-bit hybrid JDKs, but I specify it just in case here 😉
Once the GUI starts, respond as follows:
- Choose Middleware Home Directory
- Create a new Middleware Home
- Middleware Home Directory: /u01/app/oracle/middleware
- Accept the warning about the directory not being empty, click Yes
- Register for Security Updates
- Uncheck ‘I wish to receive security updates via My Oracle Support’
- Confirm you wish to bypass this, click Yes
- There is a known bug within the installer at this stage. If you get caught in a loop where you cannot bypass this, leave the box ticked and click Yes and Yes again.
- When the ‘Connection failed’ dialog appears, tick the ‘I wish to remain uninformed…’ box, then Continue and you should then make it to the next screen!
- Choose Install Type
- Choose Products and Components
- Untick the ‘Oracle Coherence’ option (unless you plan to use it)
- JDK Selection
- Local JDK: Oracle 1.7.0_21 (your Oracle JDK 7 installation)
- Choose Product Installation Directories
- WebLogic Server: /u01/app/oracle/middleware/wls_12.1.1
- Installation Summary
- Next to install
- Installation Complete
- Once the installation has finished, remove the tick next to ‘Run Quickstart’
Patch H675 fails to install
If during the installation, you use a Middleware Home (/u01/app/oracle/middleware) which contains an existing WebLogic Home (11g perhaps), then you may hit this error towards the end of the installation:
Just click OK and after the installation has completed, you can either apply the latest PSU mentioned below (which contains this patch), or download patch 13340309 from MOS (currently listed as patch ID ‘TAYS’ as opposed to ‘H675’) and reapply it that way.
Create an environment file with the following (USER_MEM_ARGS parameter is required for Java 7):
vi ~/set_wls12.env # WebLogic 12c environment file export JAVA_HOME=/usr/java/jdk1.7.0_21 export PATH=$JAVA_HOME/bin:$PATH export MW_HOME=/u01/app/oracle/middleware export WLS_HOME=$MW_HOME/wls_12.1.1 export USER_MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=350m"
Set your environment:
Copy the following JAR files as root (as stated in the Using WebLogic Server with JDK 7 document):
export JAVA_HOME=/usr/java/jdk1.7.0_21 export MW_HOME=/u01/app/oracle/middleware mkdir $JAVA_HOME/jre/lib/endorsed cp $MW_HOME/modules/javax.annotation*.jar $JAVA_HOME/jre/lib/endorsed cp $MW_HOME/modules/javax.xml.bind*.jar $JAVA_HOME/jre/lib/endorsed cp $MW_HOME/modules/javax.xml.ws*.jar $JAVA_HOME/jre/lib/endorsed
Apply the latest WebLogic PSU (18.104.22.168.4) – optional
Patch ID: YJCB
Patch No: 16083652
Download the patch from MOS (no OPatch utility required).
Unzip the patch to the cache_dir directory:
cd $MW_HOME/utils/bsu/cache_dir cp /u01/app/oracle/software/p16083652_12110_Generic.zip $MW_HOME/utils/bsu/cache_dir unzip p16083652_12110_Generic.zip
Install the patch using the Smart Update command utility:
cd $MW_HOME/utils/bsu ./bsu.sh -install -patch_download_dir=$MW_HOME/utils/bsu/cache_dir -patchlist=YJCB -prod_dir=$WLS_HOME
…at this point, if you get any patch “mutually exclusive” conflict like I did, take a look at this post.
Restart any WebLogic servers that are running to pick up the PSU changes.
Check the PSU version:
. $WLS_HOME/server/bin/setWLSEnv.sh java weblogic.version|grep PSU
That’s it, WebLogic is installed and patched up-to-date, ready for creation of your domain(s).