Weblogic console mode installation Steps

Oracle Weblogic Server

Weblogic 12c installer can be downloaded from http://www.oracle.com/technetwork/middleware/weblogic/downloads

Both JRockit and WebLogic Server were installed in the console mode option without any graphical interface. Production environments are more restricted, and console mode requires only a terminal; it is faster and does not need an X11 Server.
Generic installer is used to install WebLogic since it is the one that contains the native library for x86-64. The native library is important because it enables the use of a native socket reader that is much faster than the pure Java socket reader. This library enables what is called the performance pack on WebLogic and is mandatory in a production environment. The installation process is very straightforward and only copies the files to their directories.

Please follow below steps for weblogic console mode installation:

1. Create a dedicated user to host and run WebLogic Server 12c in Linux. Log in as the root user and create the user and the group named wls, and define a new password for it:

[[email protected]]# groupadd wls

[[email protected]]# useradd -g wls wls

[[email protected]]# passwd wls

Changing password for user wls.

New UNIX password: <new password>

Retype new UNIX password: <new password>

2. Log in as the wls user and set the correct file permissions:

[[email protected]]$ umask 027

3. Run the JRockit installer in console mode and install JRockit:

[[email protected]]$ ./jrockit-jdk1.6_xxx-linux-x64.bin -mode=console

4. Follow the onscreen instructions and type/oracle/jvm in the Product Installation directory. You can just press Enter for all the other options. JRockit will be installed without the demos and with no source code.

5. Run WebLogic Server 12c Generic Installer in console mode:

[[email protected]]$ /oracle/jvm/bin/java –jar wls1211_generic.jar –mode=console

6. Follow the onscreen instructions and type/oracle/Middleware for the “Middleware Home” = [Enter new value or use default] screen. Press Enter to move forward.

7. Skip the Register for Security Updates screen by typing 3 to navigate to 3|Receive Security Update:[Yes], then type No and then Yes. Press Enter to move forward.

8. Type 1 to select the 1|Typical option on the Install Type screen.

9. The freshly installed /oracle/jvm JDK should be selected. If not, add it by typing 1 for 1|Add Local Jdk.

10. Press Enter to confirm all the other screens.

Please follow below steps for creating the WebLogic domain

The WebLogic domain is the central configuration entity of WebLogic Server. The domain should have at least one WebLogic Server instance with the role of the Administration Server. The Administration Server is the access point used for configuration, deployment, and monitoring. A WebLogic cluster can also be added to the domain. The cluster consists of one or more Managed Servers acting as one single entity. A single webLogic Server installation is not restricted to one WebLogic domain, and more domains can be created using the same installation.

We will create a new WebLogic domain called PROD_DOMAIN with an administration instance (AdminServer) named PROD_AdminServer and a WebLogic cluster PROD_Cluster with the two Managed Servers PROD_Server01 and PROD_Server02. The two machines hosts are called prod01 and prod02.

1. Log in as a wls user on the first machine prod01 and navigate to the following folder:

[[email protected]]$ cd $WL_HOME/common/bin

2. Start WebLogic Configuration Wizard in console mode:

[[email protected]]$ ./config.sh -mode=console

3. Follow the onscreen instructions and type 1, and press Enter to select the Create a new WebLogic domain option on the Welcome screen.

4. Type 1 and press Enter to select the Choose WebLogic Platform components option on the Select Domain Source screen.

5. Press Enter again to continue with the Basic WebLogic Server Domain – [wlserver_12.1] template.

6. On the Edit Domain Information screen, type the domain name PROD_DOMAIN and press Enter twice.

7. Leave /oracle/Middleware/user_projects/domains unchanged on the Select the target domain directory for this domain screen and press Enter.

8. On the Configure Administrator User Name and Password screen, set the WebLogic administrator username and password. Type the username as wlsadmin and type 2 to set the password and 3 to type the password again and confirm it. Press Enter to move forward.

9. The Domain Mode Configuration screen is where you set the production mode. Type 2 and press Enter.

10. The installed JRockit should already be selected as /oracle/jvm on the Java SDK Selection screen. Press Enter to continue.

11. On the Select Optional Configuration screen, type 1 for the Administration Server and 2 for the Managed Servers, clusters, and machines.

12. On the Configure the Administration Server screen, type 1 to set the Administration Server name as PROD_AdminServer. Leave the other options in their default values and press Enter to move to the next screen.

13. Then add the two Managed Server instances on the Configure Managed Servers screen.

14. Type PROD_Server01 to add the first server, then type 2 to modify the listen address to prod01.domain.local. Type 3 to modify the port to 8001, press Enter, and then type 5 to finish this server.

15. Do the same for the second server and type 1 to add, type PROD_Server02 as the name, and type 2 to modify the listen address to prod02.domain.local. Type 3 to modify the port to 8002. Press Enter to continue.

16. Add the cluster on the Configure Clusters screen. Type PROD_Cluster and press Enter to create it. Type 3 and modify the Cluster Address field to prod01.domain. local:8001,prod02.domain.local:8002.

17. The next screen is the Assign Servers to Clusters screen. Type 1 to select PROD_Cluster. Then type 2 to Select All and press Enter. Confirm it by pressing Enter again.

18. Configure the two machines on the Configure Machine screen. Type prod01 and press Enter. Type 2 to change the listen address to prod01.domain.local as well. Type 4 when done.

19. Add the second machine typing 1 and name it as prod02. Press Enter and press Enter again to skip the Unix Machine screen.

20. You will now assign the Managed Servers to their respective machines on the Assign Servers to Machines screen.

21. Type 1.1 to choose prod01 and type 1 and press Enter. Now type 1-2 and press Enter assigning the PROD_AdminServer and PROD_Server01 servers. Press Enter again to return.

22. Type 1.2 to choose prod02, then type 1 and 1 again, and press Enter to finish.

Note: The PROD_DOMAIN domain was created with one the Administration Server named PROD_AdminServer and one cluster PROD_Cluster containing the two Managed Servers PROD_Server01 and PROD_Server02.

Copying the domain files to remote machines using PACK and UNPACK command

A new domain is installed and configured in one machine (prod01). Since the architecture includes another machine (prod02), the domain files now have to be distributed in all the machines of the domain.

Create a new template of the domain using the pack command in the prod01 machine. With the template created in prod01, use the unpack command to distribute the files to the machine prod02 (and to all machines used by the WebLogic cluster).

1. Log in as a wls user on the first machine prod01 and navigate to the folder:

[[email protected]]$ cd $WL_HOME/common/bin

2. Run the following command:

[[email protected]]$ ./pack.sh -domain=$DOMAIN_HOME-template=$WL_HOME/common/templates/domains/PROD_DOMAIN_template.jar -template_name=PROD_DOMAIN –managed=true

A file $WL_HOME/common/templates/domains/PROD_DOMAIN_template.jar will be created.

3. Log in as a wls user on the second machine prod02 and copy the template from prod01 to prod02:

[[email protected]]$ scp [email protected]:$WL_HOME/common/templates/domains/PROD_DOMAIN_template.jar $WL_HOME/common/templates/domains/

4. Run the following commands to unpack the template:

[[email protected]]$ cd $WL_HOME/common/bin

[[email protected]]$ ./unpack.sh -template=$WL_HOME/common/templates/domains/PROD_DOMAIN_template.jar –domain=$DOMAIN_HOME

The unpack command will create the necessary files to host the WebLogic domain PROD_DOMAIN on the prod02 machine based on the template created with the pack command on prod01.

An entry to the PROD_DOMAIN domain will automatically be added to the nodemanager.properties file.

Copying the files manually

1. Log in as a wls user on the machine prod02 and copy the domain from prod01:

[[email protected]]$ mkdir –p $DOMAIN_HOME

Note: DOMAIN_HOME is set to /oracle/Middleware/user_projects/domains/PROD_DOMAIN

[[email protected]]$ scp –rp [email protected]:$DOMAIN_HOME $DOMAIN_HOME/..

2. Edit the nodemanager.domains file:

[[email protected]]$ vi $WL_HOME/common/nodemanager/nodemanager.domains

3. Add the following entry if it doesn’t exist:


Starting the Node Manager

1. Log in as a wls user on the first machine prod01 and navigate to the folder:

[[email protected]]$ cd $WL_HOME/server/bin

2. Start the Node Manager in the background. Since it’s the first time you are starting it, the $WL_HOME/common/nodemanager/nodemanager.properties file will be created.

[[email protected]]$ nohup ./startNodeManager.sh &

[1] <PID>

nohup: appending output to `nohup.out'

3. Do the same on the prod02 machine and on all the machines of the WebLogic domain.

Starting the Administration Server

1. Log in as the wls user on the first machine prod01 and navigate to the folder:

[[email protected]]$ cd $DOMAIN_HOME/bin

2. Start the Administration Server:

[[email protected]]$ ./startWebLogic.sh

3. The server will initiate the startup process and ask for the WebLogic Administrator username and password:

Enter username to boot WebLogic server: wlsadmin

Enter password to boot WebLogic server:

4. Type wlsadmin as the username and the <password> value you previously specified during domain creation.

5. WebLogic Administration Server will start.

The system administrator should also create a boot.properties file to avoid entering the boot username and password in every WebLogic Server startup.

Creating the boot.properties file

Specify a boot.properties file so the Administration Server doesn’t ask for the username and password at startup.

1. Go to the Administration Server root folder:

[[email protected]]$ cd $DOMAIN_HOME/servers/PROD_AdminServer

2. Create and enter a new directory:

[[email protected]]$ mkdir security

[[email protected]]$ cd security

3. Create a new file called boot.properties with wlsadmin as the username and the <password> value you specified:

[[email protected]]$ echo -ne "username=wlsadmin\npassword=<password>" >


[[email protected]]$ cat boot.properties



4. The next time you start WebLogic Administration Server, it will use the credentials from the boot.properties file. The file will also be encrypted:

[[email protected]]$ cat boot.properties



In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.

4 Responses

  1. Jobs says:

    Very nice post. I am getting an error however when I run the following command: java -jar fmw_12. -mode=console
    The error is saying: Invalid arguments : -mode=console
    OS is centos 6.5, I have jdk 1.7 installed, and it is added to my PATH as well. I would appreciate any help you could give me.

    • Ramakanta says:

      Create a weblogic_silent.xml file with below details as given in below URL:


      Run it like

      /usr/java/jdk1.7.0_67/bin/java -jar /fmw_12. -mode=silent -silent_xml=/weblogic_silent.xml

      Or else no need to mention -mode=console , just run java -jar fmw_12.

  2. Chetan K says:


    WL 12c requires us to create a oraInst.loc and point to the inventory pointer location which is how we can install in silent mode which i feel is correct version. Can you please check again.


    ./runInstaller -silent -response /home/Oracle/response/Wl12c.rsp -invPtrLoc /home/Oracle/oraInst.loc

Leave a Reply