• Embed Doc
  • Copy Link
  • Readcast
  • Collections
  • CommentGo Back
Download
 
Customizing with WebSphere CloudBurst, Part 3:Using script packages for customizing above andbeyond patterns
Skill Level: IntermediateBrian Stelzer(bsstelze@us.ibm.com) Staff Software EngineerIBMXin Peng Liu(xinpengl@cn.ibm.com) Software EngineerIBM04 Nov 2009Because every user scenario is unique, the IBM® WebSphere® CloudBurst™Appliance has built-in features to help you configure and customize your IBMWebSphere Application Server environments. Part 3 of this series describes how tocustomize and enhance your deployed WebSphere Application Server environmentsusing script packages.
Introduction
The IBM WebSphere CloudBurst Appliance is a new IBM hardware appliance thatfacilitates the creation and management of a private cloud environment. WebSphereCloudBurst patterns, which represent topology definitions for repeatabledeployments that can be shared, play a key role in the creation of the private cloud.WebSphere CloudBurst contains several preloaded WebSphere Application Serverpatterns based on industry best practices. Not only does WebSphere CloudBurstprovide these patterns to help you instantly build up virtual systems with differenttopologies, but it also enables you to customize your cloud to suit your businessrequirements.A range of customization techniques are possible. You can:
Using script packages for customizing above and beyond patterns © Copyright IBM Corporation 2009. All rights reserved.Page 1 of 19
 
• Customize the preloaded virtual images and patterns.• Configure the deployed WebSphere Application Server environmentdirectly using the administrative console.• Define your own scripts to configure the deployed environment.These and other techniques were highlighted inPart 1of this series. This articlefocuses on script packages and covers:• The format and composition of a typical script package.• How to upload a script package and manage it in the appliance.• How to associate a script package with a pattern.• How to transfer and run a script package in a virtual system.
Script packages
A script package is designed to customize the behavior of parts within a pattern. Theintention of using script packages is to further enable you to customize yourWebSphere Application Server environment beyond the customization provisionsthat are standard with WebSphere CloudBurst. A typical scenario might be to installa WebSphere Application Server application into a server or cluster environmentrendered by WebSphere CloudBurst, as described inPart 1.A script package is an archive (.zip) file containing artifacts that you want to beexecuted, and artifacts that you want to be executed upon. Script packages can beas simple as a single script file or as complex as containing an entirely new product.The content of a script package is not defined or restricted by WebSphereCloudBurst. The scripts included in a script package define the requirements for thescript package. Figure 1 shows the content of a sample script package.
Figure 1. Typical content of a sample script package
developerWorks® ibm.com/developerWorksUsing script packages for customizing above and beyond patternsPage 2 of 19© Copyright IBM Corporation 2009. All rights reserved.
 
As shown here, the sample script package is formed as a file calledMyLabApplication.zip and is composed of two types of files:•
J2EE™ application EAR file
, which represents an application to beinstalled.•
Executable Jython script files
(with the file extension .jy), which containthe logic to perform the application installation to a single WebSphereApplication Server instance or to a cluster of WebSphere ApplicationServer instances.Patterns are made up of virtual image parts, and each virtual image part gets its ownvirtual machine to run in when it is deployed. A script package is associated with avirtual image part. Upon deployment, the virtual image part becomes a virtualmachine, and the script package associated with the virtual image part getsexecuted on that virtual machine. Associating a script package with a virtual imagepart is as easy as dragging and dropping the script package onto the virtual imagepart.During the deployment process, WebSphere CloudBurst will first create andconfigure a virtual machine for each virtual image part. Once the topology iscompletely configured and running, WebSphere CloudBurst will SSH over as rootcontext to the virtual machine for which the script package is targeted. WebSphereCloudBurst will then proceed to unzip the archive and execute the scripts definedwithin.
ibm.com/developerWorks developerWorks® Using script packages for customizing above and beyond patterns © Copyright IBM Corporation 2009. All rights reserved.Page 3 of 19
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...