Tuesday, May 1, 2018

Ansible automation for WebLogic - Part 2: Unarchive and Copy WebLogic installers

This post is continuous learning "Ansible automation for WebLogic" series. If you are not read the previous post please go through it which will be telling you that Java installation using Ansible. That same play book you can use it for CPU patches. The objective of this post is to use the ansible playbook for unzip the WebLogic installer and run the silent mode installer. As we have explored in the last post unarchive module used for the Java installer which had tar.gz extension.  There are multiple modules in ansible which are very powerful. In this post I would like to share my experiments with the following:

  1. unarchive module
  2. copy module
Unarchive module in Ansible

We can use the unarchive module for Zip files and also for tar.gz files. When we use this module need to provide the src, dest values that is source and destination. This module automatically copies the zip file and unzip it in the remote

The copy module in Ansible
The copy module is works similar to scp in Linux it will copy the specified files in the source to destination. We can copy multiple files to remote machine with_item option. You need to provide the list of filenames that need to copy in the list.

WebLogic response file, OraInv.loc and zip file to remote boxes using ansible modules

Working in preparation of WebLogic development environments, where we need to use the WebLogic quick installer is around 230 megabytes in size. We choose this installer because which is most preferable installer for docker clusters and virtualization implementation environments or cloud environments. After download from the Oracle site, First we need to unzip the installer.

The response file
Now lets create the silent response file for WebLogic.
Response File Version=
INSTALL_TYPE=WebLogic Server

The oraInst.loc file


Lets copy and enhancing the existing playbook file added WebLogic specific installer and silent response file, oraInv.loc files

vi wls_ins_fcp.yml
- hosts: appservers
  remote_user: vagrant
   - name: Unpack archive
        src: /u01/app/software/jdk/jdk-8u172-linux-x64.tar.gz
        dest: /home/vagrant
        remote_src: yes
   - name: WebLogic Software unzip
        src: /u01/app/software/FMW_wls/fmw_12.
        dest: /tmp
   - name: Copy install script and properties
        src: ~/wls-auto/{{ item }}
        dest: /tmp
        mode: "a+r"

Now run the playbook
vagrant@docking ~/wls-auto $ ansible-playbook -i ~/hosts wls_ins_fcp.yml

PLAY [appservers] **************************************************************

TASK [Gathering Facts] *********************************************************
ok: []
ok: []

TASK [Unpack archive] **********************************************************
ok: []
ok: []

TASK [WebLogic Software unzip] *************************************************
changed: []
changed: []

TASK [Copy install script and properties] **************************************
ok: [] => (item=wls_install.rsp)
ok: [] => (item=wls_install.rsp)
ok: [] => (item=oraInst.loc)
ok: [] => (item=oraInst.loc)

PLAY RECAP *********************************************************************             : ok=4    changed=1    unreachable=0    failed=0             : ok=4    changed=1    unreachable=0    failed=0

No two programs will be same each one can differently to achieve the same task. Lets confirm the execution of the above ansible playbook.
WebLogic installer, response file, oraInst.loc file into remote /tmp 

Next we will be work with the above files to install the WebLogic in remote machines using Ansible.

Expecting your feedback  in the comment section to improve ourself to give much better solutions.


  1. Unarchive module
  2. Copy module


  1. Thanks, it's good automation process.. Can possible to write ansible yml file just to run restart weblogic instances?

  2. yes it is possible you just need to use command module.


Blurb about this blog

Blurb about this blog

Essential Middleware Administration takes in-depth look at the fundamental relationship between Middleware and Operating Environment such as Solaris or Linux, HP-UX. Scope of this blog is associated with beginner or an experienced Middleware Team members, Middleware developer, Middleware Architects, you will be able to apply any of these automation scripts which are takeaways, because they are generalized it is like ready to use. Most of the experimented scripts are implemented in production environments.
You have any ideas for Contributing to a Middleware Admin? mail to me wlatechtrainer@gmail.com