Goal

Reading this article you will be able to perform a WebLogic 12c installation on a development server with a single WebLogic domain mydomain.

Requirements

I assume the installation will be in /opt folder and there is enough space, at least 1Gb

# du -sh /opt/*
0       /opt/java
26M     /opt/JDBC
286M    /opt/jdk1.7.0_71
20K     /opt/lost+found
539M    /opt/weblogic

I also assume Java JDK 1.7 is installed and a symbolic link /opt/java points to the current version, something like

$ ls -l /opt/|grep jdk
lrwxrwxrwx. 1 root     root        11 Nov 19 12:34 java -> jdk1.7.0_71
drwxr-xr-x. 8 root     root      4096 Sep 27 02:14 jdk1.7.0_71

Get files from Apache Ant and Oracle download pages. You will need an Oracle account: available WebLogic download is licensed only for development purpouse. For production environment you will need to purchase a license.

Copy files apache-ant-1.9.4-bin.zip and wls1213_dev.zip to /tmp path on target host, for instance host.example.com and create folders weblogic user will own.

$ sudo su -
# mkdir /opt/weblogic
# chown weblogic /opt/weblogic
# mkdir /opt/weblogic/mydomain

If you want a different location for the domain folder, you should know that it must be a subfolder of a folder the weblogic user can read/write or the domain creation will fail.

Installation

Perform installation with weblogic user. Extract archives

# sudo su - weblogic
$ cd /opt/weblogic
$ unzip /tmp/apache-ant-1.9.4-bin.zip
$ unzip /tmp/wls1213_dev.zip

Edit .bash_profile and add the following lines

export JAVA_HOME=/opt/java
export PATH=$PATH:$JAVA_HOME/bin

export ANT_HOME=/opt/weblogic/apache-ant-1.9.4
export PATH=$PATH:$ANT_HOME/bin

# default is           -Xms256m  -Xmx512m  -XX:CompileThreshold=8000 -XX:PermSize=128m   -XX:MaxPermSize=256m
export USER_MEM_ARGS=" -Xms1024m -Xmx2048m -XX:CompileThreshold=8000 -XX:PermSize=1024m  -XX:MaxPermSize=2048m "

alias start_weblogic='nohup /opt/weblogic/mydomain/bin/startWebLogic.sh > $HOME/start_weblogic.nohup 2>&1 &'
alias stop_weblogic='/opt/weblogic/mydomain/bin/stopWebLogic.sh'

then source it

$ source $HOME/.bash_profile
Note that the USER_MEM_ARGS depends on how many RAM your host has. The configuration above worked for me, but, remember that I am a WebLogic newbie.

Launch WebLogic configure.sh

$ export MW_HOME=/opt/weblogic/wls12130
$ cd $MW_HOME
$ . ./configure.sh

Do you want to configure a new domain?  [y/n]? n

Answer n otherwise it will be created a domain under the MW_HOME which is not recommended (see $MW_HOME/README.txt).

Now it is time to create your WebLogic domain: first load the environment required, then cd into your domain folder and launch domain creation

$ source $MW_HOME/wlserver/server/bin/setWLSEnv.sh
$ cd /opt/weblogic/mydomain
$ $JAVA_HOME/bin/java $JAVA_OPTIONS -Xmx1024m -XX:MaxPermSize=256m weblogic.Server

Would you like the server to create a default configuration and boot?  (y/n): y

Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
For confirmation, please re-enter password required to boot WebLogic server:

where I use the same Unix weblogic credentials for the WebLogic weblogic user.

It will take some time (approx 30 min.)

When you see message

Server state changed to RUNNING

login to http://host.example.com:7001/console with weblogic user credentials.

Finally login with another session as weblogic Unix user and launch

$ stop_weblogic

Then try to start it

$ start_weblogic

Check that it starts RUNNING mode

$ tail -f $HOME/start_weblogic.nohup

Press CTRL-C to exit. Now you can exit your ssh session.

Your WebLogic server is up and running!

Configuration

Follows some extra tip about WebLogic configuration.

Log4j

Create a log4j.xml file, for instance /opt/weblogic/domain/config/log4j.xml, and add this line to your .bash_profile

export LOG4J_CONFIG_FILE=/opt/weblogic/domain/config/log4j.xml