Oracle WebLogic 12c (12.1.2.0.0) with Vagrant

With special help from Oracle Red Samurai Edwin Biemond, here are the steps on creating an Oracle WebLogic 12c domain with Vagrant on a Windows machine acting as the host.

Edwin Biemond provided unparalleled support and his Puppet scripts are first rate. He can be found on github at https://github.com/biemond

Getting Oracle WebLogic 12c Version 12.1.2.0.0 stood up in under 10 Minutes*

What you need to download to get the environment stood up.

KIT REQUIRED:

Download and install the latest Version of VirtualBox:

http://www.virtualbox.org

Download and install Vagrantup:

http://www.vagrantup.com

Download and Install Git for Windows:

https://help.github.com/articles/set-up-git

For Provisioning Oracle WebLogic:

Download JDK7 u40

http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html

Make sure you rename the jdk to jdk-7u40-linux-x64.tar.gz from jdk-7u40-linux-x64.gz

JDK7 Changes of Note as of 10/15/2013

Oracle released a new version of the JDK 1.7u45. This has been reflected and tested in the site.pp file. If you have an older JDK you will need to modify site.pp only. The JDK7 Puppet module does not need to be modified.

site.pp is located in c:\….\vagrant-wls12c-centos64\puppet\manifests\site.pp

Download Oracle WebLogic 12c version 12.1.2.0.0

http://www.oracle.com/technetwork/middleware/downloads/index-087510.html

Optional Tools:

PuTTy Terminal / PuTTy Key Generator

http://www.chiark.greenend.org.uk/~sgtatham/putty/

MacOS Users:

This was originally developed on MacOS and then ported for Windows users.

 

* Truth in Advertising Statement:

On the initial ‘vagrant up’ run, you will need to download the centos64.box on the initial run from dopbox. This can take more then 10 minutes, but at least I warned you.

 

The rest of the work has been done for you…have fun.

Getting Oracle WebLogic 12c Version 12.1.2.0.0 stood up in under 10 Minutes*

Vagrant – Google Chrome

vagrantup.com

Vagrant - Google Chrome

Vagrant – Downloads – Google Chrome

Vagrant - Downloads - Google Chrome

Vagrant – Downloads – Google Chrome

Vagrant - Downloads - Google Chrome

Open File – Security Warning

Open File - Security Warning

Vagrant Setup

Vagrant Setup

Vagrant Setup

Vagrant Setup

Vagrant Setup

Vagrant Setup

Vagrant Setup

Vagrant Setup

GitHub – Google Chrome

GitHub - Google Chrome

Set Up Git · GitHub Help – Google Chrome

Set Up Git · GitHub Help - Google Chrome

matthewbaldwin/vagrant-wls12c-centos64 – Google Chrome

matthewbaldwin/vagrant-wls12c-centos64 - Google Chrome

GitHub you don't need an account…but you can always create one.

If you don’t login then press “Skip Setup” and the repository will be downloaded

GitHub you don't need an account...but you can always create one.

GitHub

GitHub

GitHub

GitHub

Add downloaded wls_121200.jar and jdk-7u40-linux-x64.tar.gz

C:\Users\mbaldwin\Documents\GitHub\vagrant-wls12c-centos64\

Add downloaded wls_121200.jar and jdk-7u40-linux-x64.tar.gz

Once you have synced with GitHub and a quicknote on how they are used

You will have directory structure in the image

Quick Note about VirtualBox shared files between the guest and the host when the virtual machine is booted up.

This directory is being shared with the guest VM. If you modify, delete or add files on the host, the same will happen on the guest and vice versa.

The directory c:\Users\mbaldwin\My Documents\GitHub\vagrant-wls12c-centos64 on the host is mapped to /vagrant on the linux guest. The subdirectories of \vagrant-wls12c-centos64 are also available on the Linux guest and automatically mounted.

Puppet modules and manifests on the host:

c:\Users\mbaldwin\My Documents\GitHub\centos64\puppet\modules (or manifests)

Are shown in the booted linux as

/vagrant/puppet/modules (or manifests)

AND

/etc/puppet/modules-0
/etc/puppet/manifests

 

 

Once you have synced with GitHub and a quicknote on how they are used

GitHub

GitHub

posh~git ~ vagrant-wls12c-centos64 [master]

posh~git ~ vagrant-wls12c-centos64 [master]

posh~git ~ vagrant-wls12c-centos64 [master]

Note that we don’t have a centos64 vagrant box to work with here. We will add this box in the Vagrantfile. This is a onetime operation.

posh~git ~ vagrant-wls12c-centos64 [master]

"vagrant up" posh~git ~ vagrant-wls12c-centos64 [master]

This is downloading the vagrant box specified in the Vagrantfile.

"vagrant up" posh~git ~ vagrant-wls12c-centos64 [master]

posh~git ~ vagrant-wls12c-centos64 [master]

Completed the download and now importing.

posh~git ~ vagrant-wls12c-centos64 [master]

posh~git ~ vagrant-wls12c-centos64 [master]

Booting the vm…based upon the vagrantfile.

posh~git ~ vagrant-wls12c-centos64 [master]

Whole Bunch of output

Whole Bunch of output

Big Pause posh~git ~ centos64 [master]

Just a quick note…this was from my test (Oracle Enterprise Linux) oel64.box. You will get the same pause.

Big Pause posh~git ~ centos64 [master]

Success – posh~git ~ centos64 [master]

Running is nodemanager as a linux service and AdminServer

Success - posh~git ~ centos64 [master]

Oracle WebLogic Server Administration Console – Google Chrome from Host Windows Machine

Since we port forwarded in the Vagantfile we can login from the host machine

login: weblogic/welcome1

Oracle WebLogic Server Administration Console - Google Chrome from Host Windows Machine

WebLogic Console

WebLogic Console

"vagrant ssh" posh~git ~ centos64 [master]

Running vagrant ssh gets you into the machine as user vagrant

"vagrant ssh" posh~git ~ centos64 [master]

login as oracle posh~git ~ centos64 [master]

You can then su -l oracle and have access to the guest.

From here you have all the commandline control you need over this server.

login as oracle posh~git ~ centos64 [master]

"vagrant box list" posh~git ~ vagrant-wls12c-centos64 [master]

Exit out of the ssh to the git command line and you can see that you have the new vagrantbox added to your list. You can use this box as a starter box for your other work.

"vagrant box list" posh~git ~ vagrant-wls12c-centos64 [master]

"vagrant destroy" – posh~git ~ vagrant-wls12c-centos64 [master]

With ‘vagrant destroy’ you then reset the box and when you run ‘vagrant up’ the Puppet scripts will run again.

Little Tip: If you chnage the provision scripts…you just need to run “vagrant provision”

"vagrant destroy"  - posh~git ~ vagrant-wls12c-centos64 [master]

Vagrant Documentation – Getting Started – SSH – For Windows Users

Information on setting up SSH with PuTTY…not really needed if using Git

http://docs-v1.vagrantup.com/v1/docs/getting-started/ssh.html

Vagrant Documentation - Getting Started - SSH - For Windows Users

PuTTY Download Page – Google Chrome

PuTTY Download Page - Google Chrome

PuTTY Key Generator

This procedure would be done after you import the vagrant box

PuTTY Key Generator

Load private key:

This key is generated when you first run vagrant

Load private key:

PuTTY Key Generator

PuTTY Key Generator

PuTTY Key Generator

PuTTY Key Generator

PuTTYgen Warning

PuTTYgen Warning

PuTTygen Save ppk

PuTTygen Save ppk

Save private key on your drive

Save private key on your drive

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

Select private key file

Select private key file

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

PuTTY Configuration

vagrant@vagrantoel64:~

vagrant@vagrantoel64:~
Advertisements

4 thoughts on “Oracle WebLogic 12c (12.1.2.0.0) with Vagrant

  1. […] BTW: All this is possible due to the impressive work Edwin Biemond has done in the last weeks and month (Checkout his powerful puppet modules  here) plus the Vagrant based provisioning script of Matthew Baldwin. (Checkout his recent blog post about that   here). […]

  2. vbatik says:

    Oh yes… I totally agree…Edwin and I have been working very collaboratively…in many ways he is using Vagrant as a test harness around his puppet scripts. Thanks for commenting!

  3. Bill Skaggs says:

    Thanks for the clear steps on setting things up. One note the login is weblogic/weblogic1 for the wls console.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: