This week  I was working on a project to implement Single Sign On with EBS R12,  as a first pre-requisite I had to install and configure WebLogic Server.

Here are the steps to install and perform a basic configuration for WebLogic Server.


1. Download Weblogic Server from the following URL:

2. Review documentation to meet the basic hardware and software requirements:


1. I’ve created an operating user “oracle” to own the WebLogic Server, so as a “root” Super User do the following:

#groupadd dba
#useradd -g dba oracle
#mkdir -p /u01/oracle/middleware
#chown -Rh oracle:dba /u01/oracle/middleware
#xhost +

2. Now login as “oracle” and invoke the installer (I’ve downloaded the installer at /u01/dumps) as seen below. Click “Next”

3. Enter the location for Middle Ware Home and click “Next”

4.  Register for Security Updates if you wish to and click “Next”

5. Choose Install Type, I’ve chosen “Custom” and click “Next”

6. Choose “Products and Components”  you wish to use and click “Next”

7. If you have previous JDK/JRockit SDK, you can choose to browse the path, although Oracle recommends that you download the latest JRockit SDK to use with WebLogic. You can download the latest JRockit from:

8.  Choose “Product Installation Directories” and click “Next”

9. Review the Installation Summary and click “Next”

10. Once the installation completes, the “Run QuickStart” is checked. We’ll launch the QuickStart by clicking “Done”

11. Once clicked “Done”, You will be presented with the following which lets you choose 3 Options, We’ll go ahead with the 1st  to proceed with the configuration wizard.


12. Now in the configuration wizard, we’ll choose “Create New WebLogic Domain” and click “Next”

13. Choose the defaults, I’ve also chosen “WebLogic Advanced Web Services Extension” from the following screen, click “Next” to proceed

14.  Now enter the Domain Name and Enter the Domain Location, click “Next” to proceed:

15.  Configure the WebLogic Administrator and Password, click “Next” to proceed.

16. As this is a basic install and for development purposes, I will choose the “Domain Startup Mode” as “Development. Careful consideration should be taken for production deployment. Click “Next” to proceed

17.  Select the Optional Configuration , I’ve selected the following options(we can configure JMS at a later stage):

18.  Configure the Admin Server:

19. Configure the Managed servers and click “Next”

20.  Next screen asks you if you wish to configure cluster, I did not configure any cluster. Click “Next” to proceed.

21. Next Screen is Configure Machines, I’ve not configured any. Click ” Next” to proceed

22. Configure Target Services to Clusters or Servers, review and click “Next” to proceed

23.  Review the Configuration Summary and click “Create”

24.  Click “Done” to finish and close the quickstart screen.

Now that we have installed and configured the WebLogic server, lets start the WebLogic server for the domain we configured. The startup scripts are placed in the user_projects directory for the domain we configured.

25.  Start the WebLogic Server

[oracle@oralin03]$ cd
[oracle@oralin03 ~]$ cd /u01/oracle/middleware/user_projects/domains/
[oracle@oralin03]$ ls
autodeploy            init-info              
bin                   lib                              WseeFileStore
config                security                         WseeFileStoreAdminServer
console-ext           servers  startManagedWebLogic_readme.txt

Now that the WebLogic Server is started lets login to the console

26. In to order login to the console open the web browser , the URL will be of the following format:

http://<hostname&gt;.<domain name>:7001/console

In my case it will be

You will be presented with the following screen:

The user name is “weblogic” and the password is what you configured during the configuration.

27. You will be presented with a neat front page, navigate to check the state of services on the left panel, follow the screenshot:

Thats it folks, the installation and basic configuration of WebLogic Server is complete. Feel free to comment and share your thoughts.

Thanks for reading.


Ever wondered what would you do if  the disk hosting your linux or Windows Operating System crashes? To avoid such unlikely events, backups are always recommended.I ran into a similar requirement for the media server I have at home. I was looking for a backup solution when I wanted to try my hands-on VMware ESXi .

I have CentOS 5 X86_64 installed on my server and after researching for quite sometime I came across a tool which could do my job effortlessly . The tool is called SystemRescueCD. Although this tool provides great amount of features, I will share the one’s which helped me backup and restore the system.

I’ve divided this tutorial in two parts, PART-1 is addressed to backup linux root partition and PART-2 will address on how to restore  your OS in the event of a disk failure or for any reason you’d require to restore your OS. This is just one of many ways to take backup of an OS, you can find the whole list of softwares to suit your needs at

Creation of SysRescueCD or USB

You can create a rescue cd from the ISO, The ISO can be downloaded from here . Alternatively you create a bootable USB stick using theISO(instructions below). I decided to go with the USB bootable stick. Heres the procedure I followed on Windows XP:

1. Mount the SysRescueCD ISO using Magic ISO/PowerISO/Daemon-tools or any emulation software of your choice.
2. Insert the USB and Find the drive letter, in my case its K:
3. Format the USB stick as FAT(NTFS wont work) , please see the screenshot.

4. Copy Files from SysRescueCD to USB stick(K:):

  • Once the USB stick is formatted, copy the files from the SysRescueCD to the root of USB stick.
  • Rename folder isolinux to syslinux in K:
  • Go to K:syslinux folder, rename the file isolinux.cfg to syslinux.cfg

5. Make USB stick(K:) bootable

  • Go to K:bootprog and unzip would change for newer versions of sysrescuecd).
  • Open command prompt and change location to K:bootprogwin32
  • Run the following command to make the USB bootable:
syslinux -ma K:

-m means write mbr

-a means make drive partition active (aka bootable).

  • Your USB stick is now bootable and ready to be used to take backups.

Booting SysRescueCD  using USB

1. Ensure “Removable Devices” is set as the first priority in your bios settings.

2. Shutdown the Linux Host and boot with using the USB bootable stick we created earlier.

3. You will be presented with the following screen:

4. Choose the first option and press return key.

5. Once the boot process is complete, you will be presented with the following screen.

As you can see from the above, you are given many options to connect to this console. Now lets proceed with the backup.

Performing Backup

SysRescueCD gives you majorly two options to backup the file systems.

  • fsarchiver
  • partimage

In this tutorial I will use fsarchiver.

The following is the file system layout, In this scenario I will take a backup of the OS on /backup partition which is a separate hard disk dedicated to take backups.

[root@oralin05 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
7.7G  2.7G  4.6G  37% /
/dev/sda1              99M   12M   82M  13% /boot
tmpfs                 506M     0  506M   0% /dev/shm
/dev/sdb1             7.9G  147M  7.4G   2% /backup
[root@oralin05 ~]#

As you can see /dev/sda holds the root & boot partition and /dev/sdb is used for backups. If you would like to take tape backups, it will be /dev/rmt[n]

1. Mount the directory you would like to take the backup:

root@sysresccd /root % mkdir /backup
root@sysresccd /root % mount /dev/sdb1 /backup
root@sysresccd /root % df -h | grep /backup
/dev/sdb1             7.9G  147M  7.4G   2% /backup
root@sysresccd /root %

2. Backup Master Boot Record(MBR)

root@sysresccd /root % dd if=/dev/sda of=/backup/sda-MBR-backup bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.00573138 s, 89.3 kB/s
root@sysresccd /root %

3. Backup “/boot” and LVM hosting “/” root partition
The following command is used to take the backup:

#fsarchiver -v savefs /backup/backup-sda.fsa /dev/sda1 /dev/mapper/VolGroup00-LogVol00

Deciphering the above command:
-v is verbose
is Save File System
/backup/backup-sda.fsa is the file which holds the backup followed by the partitions we need to backup.

The backup finishes with the following status:

Statistics for filesystem 1
* files successfully processed:....regfiles=104377, directories=11189, symlinks=12825, hardlinks=3975, specials=10
* files with errors:...............regfiles=0, directories=0, symlinks=0, hardlinks=0, specials=0

4. Once backup is complete, you can verify the backup using the following command:

#fsarchiver archinfo /backup/backup-sda.fsa
root@sysresccd /backup % fsarchiver archinfo /backup/backup-sda.fsa
====================== archive information ======================
Archive type:                   filesystems
Filesystems count:              2
Archive id:                     4be3d087
Archive file format:            FsArCh_002
Archive created with:           0.6.8
Archive creation date:          2010-05-14_15-24-41
Archive label:                  &amp;amp;lt;none&amp;amp;gt;
Minimum fsarchiver version:
Compression level:              3 (gzip level 6)
Encryption algorithm:           none

===================== filesystem information ====================
Filesystem id in archive:       0
Filesystem format:              ext3
Filesystem label:               /boot
Filesystem uuid:                3124fbdf-4ae8-4557-9037-45501865b6c8
Original device:                /dev/sda1
Original filesystem size:       98.72 MB (103512064 bytes)
Space used in filesystem:       11.83 MB (12401664 bytes)

===================== filesystem information ====================
Filesystem id in archive:       1
Filesystem format:              ext3
Filesystem label:
Filesystem uuid:                ede651ef-3d19-4d4d-9e65-a2e72672d492
Original device:                /dev/mapper/VolGroup00-LogVol00
Original filesystem size:       7.63 GB (8190885888 bytes)
Space used in filesystem:       2.65 GB (2847793152 bytes)

root@sysresccd /backup %

5. Backup the partition table information, this is required to restore the non-root partitions if you have any on your server.

#sfdisk -d /dev/sda /backup/sda-part-table.sf

This is a text file, you can read the contents of this file.

That concludes the PART-1 of taking the backup of Linux Operating System using SysRescueCD.

I will post the PART-2 shortly …

fsarchiver archinfo /backup/backup-sda.fsa