Cloud Computing Made Easy^®

IBM Websphere Sample

From Cloud Computing Wiki - Kaavo

IBM Websphere Single Server Deployment through IMOD

The Objective of this tutorial is to give the basic idea about application setup on webspehere through IMOD. The per-requisite knowledge for this document is :

Basic knowledge of Websphere architecture.
Automatic Deployment in Websphere
Basic understanding of IMOD

Deployment of Application in Websphere

It is quite easy to deploy application on Websphere through command line or Portal , if you start a IBM cloud server it will automatically bring up the portal on the following url:

http://<ServerIP>:9060/ibm/console

and you can log on to the server and start a new deployment. On the other hand if you log on to the server thorough ssh , it can be as simple as: wsadmin -c "$AdminApp install X:/MyApp.ear" -lang jacl However, this simplicity is deceiving and the preceding example is really just the "Hello World" deployment - a nice demo, but not typical of the real world. In real life you have to automate the deployment, the automation process of Websphere support three types of deployment descriptor :

JACL : which is a tcl type scripting language
Jython : Similar to python
ws_and and ANT script : ANT deployment with xml file and ws_ant tool

We can write our automation by using JACL , jython or ANT. For the simplicity we will use “jacl” script to deploy the

IMOD Deployment for Cloud automation

IMOD supports cloud automation, i.e. IMOD will generate your configuration scripts and run those in boot up process to make your server ready with your application. It will also help you to administrate your server manually or automatically (using autopilot). In this document we will cover up the following things :

Understanding of the basic template with websphere
Setup deployment using jacl script and action scripts
Write action scripts for start and stop server
Idea to setup autopilot and recovery

Configuration of the System Once you deploy you system from example template to your account at IMOD , you have to configure the system, (you can find how to deploy system here). During configuration you have to give some Websphere specific parameter.

WASAdminUser : You have to Websphere admin user name here
WASAdminPassword : You have you webspehere password here , a password should contain at-lease one capital

List of Action for the template

downloadApplication :

Download the application file from user's specific location. In the example, we have downloaded the application from a public location for the sake of simplicity, but in real life you can specify your secured location and credential at the system definition file, i.e. you can always use rsync , git , scp etc. to download your application.

- List of parameter
  - DownloadLink : URL of the repository

- installApplication

InstallApplication will install the application , our script is written by using JACL. Here is the original IBM link for JACL and Jython

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/txml_callappinstall.html

- List of parameters:
  - AppsName : Name of the application file
  - ServerName : Name of the server form the Websphere configuration.

- RunInstallApplication :

This will run the jacl script through wsadmin tool, we have passed the user name and password as parameter.

- -lang : language specification jacl/jython
- -f : jacl/jython script name
- -user : Administrative user name of the Webspehere
- -password : password of the Administrative user

- startApplication :

Very much similar to installApplication script it will start the service. However , this is written in JACL but you can implement Jython as well. List of Parameters:

cell : Name of the base cell
ApplicationName : Name of the application

- runStartApplication :

This script will start the application.

Retrieved from "http://wiki.kaavo.com/index.php/IBM_Websphere_Sample"