Cloud Computing Lab Manual-New
Cloud Computing Lab Manual-New
MCA- SEMESTER-V
Prepared by
Alka Singh
LIST OF EXPERIMENTS:
Course Objective:
To develop web applications in cloud
To learn the design and development process involved in creating a cloud based application
To learn to implement and use parallel programming using Hadoop
Exercises:
1. Install Virtualbox/VMware Workstation with different flavours of linux or windows OS on top
of windows7 or 8.
2. Install a C compiler in the virtual machine created using virtual box and execute Simple
Programs
3. Install Google App Engine. Create hello world app and other simple web applications
using python/java.
4. Use GAE launcher to launch the web applications.
5. Simulate a cloud scenario using CloudSim and run a scheduling algorithm that is not present
in CloudSim.
6. Find a procedure to transfer the files from one virtual machine to another virtual machine.
7. Find a procedure to launch virtual machine using trystack (Online Openstack Demo Version)
8. Install Hadoop single node cluster and run simple applications like wordcount.
CLOUD COMPUTING
Workstation Aim:
Find procedure to Install Virtualbox/VMware Workstation with different flavours of linux or
windows OS on top of windows7 or 8.
PROCEDURE TO INSTALL
Step 1- Download Link
Link for downloading the software is https://www.vmware.com/products/workstation-pro/workstation-
pro-evaluation.html. Download the software for windows. Good thing is that there is no signup
process. Click and download begins. Software is around 541 MB.
Initial Splash screen will appear. Wait for the process to complete.
VMware Workstation 15 Installation Splash Screen
Screenshot for VMware Workstation 15 pro installation begin confirmation dialog box on windows 10.
At the end you will see installation complete dialog box. Click finish and you are done with the
installation process. You may be asked to restart your computer. Click on Yes to restart.
VMware Workstation 15 Installation – Installation Complete
CLICK
Install Linux using Virtual Box
I. Run VirtualBox by double-clicking the icon
2. Click “New” button on the top left corner
MAC PC
Install Linux using Virtual Box
3. Click “Continue” on the pop-up window
4.Type VM name, select “Linux” for the OS and choose
“Ubuntu” for the version.
MAC PC
Install Linux using Virtual Box
5. Choose the amount of memory to allocate (I suggest
choosing between 5I2 MB to I024 MB)
6. Click Continue or Next
MAC PC
Install Linux using Virtual Box
7. Choose create a new virtual hard disk
8. Click Continue or Next
MAC PC
Install Linux using Virtual Box
9. Choose VDI (VirtualBox Disk Image)
I0. Click Continue or Next
MAC PC
Install Linux using Virtual Box
II. Choose “Dynamically Allocated” click continue.
This way, the size of your Virtual Hard Disk will grow as
you use.
MAC PC
Install Linux using Virtual Box
I2. Click the folder icon and choose the ubuntu iso file
you downloaded.
I3. Select the size of the Virtual Disk (I recommend
choosing 8 GB) and click continue
MAC PC
Install Linux using Virtual Box
I4. Click Create
MAC PC
Running Linux
I. Choose Ubuntu from left column and click Start
MAC & PC
Running Linux
2. Click continue on pop-up window
MAC PC
Running Linux
3.Click the folder icon and choose the ubuntu iso file
you downloaded and click continue and start
MAC PC
Running Linux
4. Click Install Ubuntu
Running Linux
4. Check “Download updates” and click Forward
Running Linux
5. Choose “Erase disk and install Ubuntu” and click
Forward (Don’t worry, it won’t wipe your computer)
Running Linux
6. Click “Install Now” and wait. Maybe grab a snack.
7.When finished, click Restart and press Enter.
C Programming on Linux
I. Open Terminal (Applications-Accessories-Terminal)
C Programming on Linux
2. Open gedit by typing “gedit &” on terminal
(You can also use any other Text Editor application)
C Programming on Linux
3.Type the following on gedit
(or any other text editor)
#include<3tdio.h>
main()
{
printf("Hello World\n");
}
This document describes the installation of the Google App Engine Software
Development Kit (SDK) on a Microsoft Windows and running a simple “hello world”
application.
The App Engine SDK allows you to run Google App Engine Applications on your local
computer. It simulates the run-‐time environment of the Google App Engine
infrastructure.
If you don't already have Python 2.5.4 installed in your computer, download and
Install Python 2.5.4 from:
http://www.python.org/download/releases/2.5.4/
You can download the Google App Engine SDK by going to:
http://code.google.com/appengine/downloads.html
1
Double Click on the GoogleApplicationEngine installer.
Click through the installation wizard, and it should install the App Engine. If you do
not have Python 2.5, it will install Python 2.5 as well.
Once the install is complete you can discard the downloaded installer
2
Making your First Application
Now you need to create a simple application. We could use the “+” option to have
the launcher make us an application – but instead we will do it by hand to get a
better sense of what is going on.
Make a folder for your Google App Engine applications. I am going to make the
Folder on my Desktop called “apps” – the path to this folder is:
And then make a sub-‐folder in within apps called “ae-01-trivial” – the path to this
folder would be:
Using a text editor such as JEdit (www.jedit.org), create a file called app.yaml in the
ae-01-trivial folder with the following contents:
application: ae-01-trivial
version: 1
runtime: python
api_version: 1
handlers:
- url: /.*
script: index.py
Note: Please do not copy and paste these lines into your text editor – you might end
up with strange characters – simply type them into your editor.
Then create a file in the ae-01-trivial folder called index.py with three lines in it:
3
Once you have selected your application and press Run. After a few moments your
application will start and the launcher will show a little green icon next to your
application. Then press Browse to open a browser pointing at your application
which is running at http://localhost:8080/
Paste http://localhost:8080 into your browser and you should see your
application as follows:
Just for fun, edit the index.py to change the name “Chuck” to your own name and
press Refresh in the browser to verify your updates.
You can watch the internal log of the actions that the web server is performing when
you are interacting with your application in the browser. Select your application in
the Launcher and press the Logs button to bring up a log window:
4
Each time you press Refresh in your browser – you can see it retrieving the output
with a GET request.
With two files to edit, there are two general categories of errors that you may
encounter. If you make a mistake on the app.yaml file, the App Engine will not start
and your launcher will show a yellow icon near your application:
To get more detail on what is going wrong, take a look at the log for the application:
5
In this instance – the mistake is mis-‐indenting the last line in the app.yaml (line 8).
If you make a syntax error in the index.py file, a Python trace back error will appear
in your browser.
The error you need to see is likely to be the last few lines of the output – in this case
I made a Python syntax error on line one of our one-‐line application.
Reference: http://en.wikipedia.org/wiki/Stack_trace
When you make a mistake in the app.yaml file – you must the fix the mistake and
attempt to start the application again.
6
If you make a mistake in a file like index.py, you can simply fix the file and press
refresh in your browser – there is no need to restart the server.
To shut down the server, use the Launcher, select your application and press the
Stop button.
7
How to use CloudSim in Eclipse
CloudSim is written in Java. The knowledge you need to use CloudSim is basic Java
programming and some basics about cloud computing. Knowledge of programming IDEs such
as Eclipse or NetBeans is also helpful. It is a library and, hence, CloudSim does not have to be
installed. Normally, you can unpack the downloaded package in any directory, add it to the Java
classpath and it is ready to be used. Please verify whether Java is available on your system.
To use CloudSim in Eclipse:
1. Download CloudSim installable files
from https://code.google.com/p/cloudsim/downloads/list and unzip
2. Open Eclipse
3. Create a new Java Project: File -> New
4. Import an unpacked CloudSim project into the new Java Project
5. The first step is to initialise the CloudSim package by initialising the CloudSim library,
as follows:
Vm vm = new Vm(vmid, brokerId, mips, pesNumber, ram, bw, size, vmm, new
CloudletSchedulerTimeShared())
9. Submit the VM list to the broker:
broker.submitVmList(vmlist)
10. Create a cloudlet with length, file size, output size, and utilisation model:
Cloudlet cloudlet = new Cloudlet(id, length, pesNumber, fileSize, outputSize, utilizationModel, utilizationMode
11. Submit the cloudlet list to the broker:
broker.submitCloudletList(cloudletList)
12. Start the simulation:
CloudSim.startSimulation()
Sample Output from the Existing Example:
Starting CloudSimExample1...
Initialising...
Starting CloudSim version 3.0
Datacenter_0 is starting...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>null
Broker is starting...
Entities started.
1.1: Broker: Cloud Resource List received with 1
resource(s) 0.0: Broker: Trying to Create VM #0 in
Datacenter_0
1.2: Broker: VM #0 has been created in Datacenter #2, Host #0
0.1: Broker: Sending cloudlet 0 to VM #0
400.1: Broker: Cloudlet 0 received
400.1: Broker: All Cloudlets executed.
Finishing... 400.1: Broker: Destroying VM #0
Broker is shutting down...
Simulation: No more future events
CloudInformationService: Notify all CloudSim entities for shutting down.
Datacenter_0 is shutting down...
Broker is shutting down...
Simulation completed.
Simulation completed.
========== OUTPUT ==========
Cloudlet ID STATUS Data center ID VM ID Time Start Time Finish Time
0 SUCCESS 2 0 400 0.1 400.1
*****Datacenter:
Datacenter_0***** User id Debt
3 35.6
CloudSimExample1 finished!
1. You can copy few (or more) lines with copy & paste mechanism.
For this you need to share clipboard between host OS and guest OS, installing Guest
Addition on both the virtual machines (probably setting bidirectional and restarting them).
You copy from guest OS in the clipboard that is shared with the host OS.
Then you paste from the host OS to the second guest OS.
2. You can enable drag and drop too with the same method (Click on the machine, settings,
general, advanced, drag and drop: set to bidirectional )
3. You can have common Shared Folders on both virtual machines and use one of the
directory shared as buffer to copy.
Installing Guest Additions you have the possibility to set Shared Folders too. As you put a
file in a shared folder from host OS or from guest OS, is immediately visible to the other.
(Keep in mind that can arise some problems for date/time of the files when there are
different clock settings on the different virtual machines).
If you use the same folder shared on more machines you can exchange files directly
copying them in this folder.
4. You can use usual method to copy files between 2 different computer with client-server
application. (e.g. scp with sshd active for linux, winscp... you can get some info about SSH
servers e.g. here)
You need an active server (sshd) on the receiving machine and a client on the sending
machine. Of course you need to have the authorization setted (via password or, better, via
an automatic authentication method).
Note: many Linux/Ubuntu distribution install sshd by default: you can see if it is running
with pgrep sshd from a shell. You can install with sudo apt-get install openssh-server.
5. You can mount part of the file system of a virtual machine via NFS or SSHFS on the
other, or you can share file and directory with Samba.
You may find interesting the article Sharing files between guest and host without
VirtualBox shared folders with detailed step by step instructions.
You should remember that you are dialling with a little network of machines with different
operative systems, and in particular:
Each virtual machine has its own operative system running on and acts as a
physical machine.
Each virtual machine is an instance of a program owned by an user in the hosting operative
system and should undergo the restrictions of the user in the hosting OS.
E.g Let we say that Hastur and Meow are users of the hosting machine, but they did not
allow each other to see their directories (no read/write/execute authorization). When each of
them run a virtual machine, for the hosting OS those virtual machine are two normal
programs owned by Hastur and Meow and cannot see the private directory of the other user.
This is a restriction due to the hosting OS. It's easy to overcame it: it's enough to give
authorization to read/write/execute to a directory or to chose a different directory in which
both users can read/write/execute.
Windows likes mouse and Linux fingers. :-)
I mean I suggest you to enable Drag & drop to be cosy with the Windows machines and
the Shared folders or to be cosy with Linux.
When you will need to be fast with Linux you will feel the need of ssh-keygen and
to Generate once SSH Keys to copy files on/from a remote machine without writing
password anymore. In this way it functions bash auto-completion remotely too!
OpenStack is an open-source software cloud computing platform. OpenStack is primarily used
for deploying an infrastructure as a service (IaaS) solution like Amazon Web Service (AWS). In
other words, you can make your own AWS by using OpenStack. If you want to try out
OpenStack, TryStack is the easiest and free way to do it.
In order to try OpenStack in TryStack, you must register yourself by joining TryStack Facebook
Group. The acceptance of group needs a couple days because it’s approved manually. After you
have been accepted in the TryStack Group, you can log in TryStack.
TryStack.org Homepage
I assume that you already join to the Facebook Group and login to the dashboard. After you
log in to the TryStack, you will see the Compute Dashboard like:
OpenStack Compute Dashboard
In this post, I will show you how to run an OpenStack instance. The instance will be accessible
through the internet (have a public IP address). The final topology will like:
Network topology
As you see from the image above, the instance will be connected to a local network and the local
network will be connected to internet.
Network? Yes, the network in here is our own local network. So, your instances will be not
mixed up with the others. You can imagine this as your own LAN (Local Area Network) in the
cloud.
I guess you already know what router is. In the step 1, we created our network, but it is isolated.
It doesn’t connect to the internet. To make our network has an internet connection, we need a
router that running as the gateway to the internet.
OpenStack has a feature like a firewall. It can whitelist/blacklist your in/out connection. It is
called Security Group.
1. Go to Compute > Access & Security and then open Security Groups tab.
2. In default row, click Manage Rules.
3. Click Add Rule, choose ALL ICMP rule to enable ping into your instance, and then click Add.
4. Click Add Rule, choose HTTP rule to open HTTP port (port 80), and then click Add.
5. Click Add Rule, choose SSH rule to open SSH port (port 22), and then click Add.
6. You can open other ports by creating new rules.
Now, you can SSH your instances to the floating IP address that you got in the step 4. If you are
using Ubuntu image, the SSH user will be ubuntu.
Install Hadoop
Step 1: Click here to download the Java 8 Package. Save this file in your home
directory.
Step 5: Add the Hadoop and Java paths in the bash file (.bashrc). Open.
bashrc file. Now, add Hadoop and Java Path as shown below.
Command: vi .bashrc
Fig: Hadoop Installation – Setting Environment Variable
For applying all these changes to the current Terminal, execute the source command.
To make sure that Java and Hadoop have been properly installed on your system and can be
accessed through the Terminal, execute the java -version and hadoop version commands.
Command: cd hadoop-2.7.3/etc/hadoop/
Command: ls
All the Hadoop configuration files are located in hadoop-2.7.3/etc/hadoop directory as you
can see in the snapshot below:
Fig: Hadoop Installation – Hadoop Configuration Files
Step 7: Open core-site.xml and edit the property mentioned below inside
configuration tag:
core-site.xml informs Hadoop daemon where NameNode runs in the cluster. It contains
configuration settings of Hadoop core such as I/O settings that are common to HDFS &
MapReduce.
Command: vi core-site.xml
Command: vi hdfs-site.xml
1
2 <?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
3 <configuration>
4 <property>
5 <name>dfs.replication</name>
<value>1</value>
6 </property>
7 <property>
8 <name>dfs.permission</name>
9 <value>false</value>
</property>
10 </configuration>
11
12
Step 9: Edit the mapred-site.xml file and edit the property mentioned below
inside configuration tag:
In some cases, mapred-site.xml file is not available. So, we have to create the mapred- site.xml
file using mapred-site.xml template.
1
<?xml version="1.0" encoding="UTF-8"?>
2 <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
3 <configuration>
4 <property>
<name>mapreduce.framework.name</name>
5 <value>yarn</value>
6 </property>
7 </configuration>
8
Step 10: Edit yarn-site.xml and edit the property mentioned below inside
configuration tag:
Command: vi yarn-site.xml
Fig: Hadoop Installation – Configuring yarn-site.xml
1
2 <?xml version="1.0">
3 <configuration>
4 <property>
<name>yarn.nodemanager.aux-services</name>
5 <value>mapreduce_shuffle</value>
6 </property>
7 <property>
<name>yarn.nodemanager.auxservices.mapreduce.shuffle.class</ name>
8
<value>org.apache.hadoop.mapred.ShuffleHandler</value>
9 </property>
1 </configuration>
0
1
1
Step 11: Edit hadoop-env.sh and add the Java Path as mentioned below:
hadoop-env.sh contains the environment variables that are used in the script to run
Hadoop like Java home path, etc.
Command: vi hadoop–env.sh
Command: cd
Command: cd hadoop-2.7.3
This formats the HDFS via NameNode. This command is only executed for the first time.
Formatting the file system means initializing the directory specified by the dfs.name.dir
variable.
Never format, up and running Hadoop filesystem. You will lose all your data stored in the
HDFS.
Command: cd hadoop-2.7.3/sbin
Either you can start all daemons with a single command or do it individually.
Command: ./start-all.sh
Start NameNode:
The NameNode is the centerpiece of an HDFS file system. It keeps the directory tree of all files
stored in the HDFS and tracks all the file stored across the cluster.
Start
DataNode:
On startup, a DataNode connects to the Namenode and it responds to the requests from the
Namenode for different operations.
Start ResourceManager:
ResourceManager is the master that arbitrates all the available cluster resources and thus helps in
managing the distributed applications running on the YARN system. Its work is to manage
each NodeManagers and the each application’s ApplicationMaster.
Start NodeManager:
The NodeManager in each machine framework is the agent which is responsible for managing
containers, monitoring their resource usage and reporting the same to the ResourceManager.
Start JobHistoryServer:
JobHistoryServer is responsible for servicing all job history related requests from client.
Step 14: To check that all the Hadoop services are up and running, run the below
command.
Command: jps
OBJECTIVE:
To develop a new Web service for Calculator applications.
PROCEDURE:
When you start Globus toolkit container, there will be number of services starts up. The
service for this task will be a simple Math service that can perform basic arithmetic for a
client.
It is possible to start with this interface and create the necessary WSDL file using the standard
Web service tool called Java2WSDL. However, the WSDL file for GT 4 has to include details
of resource properties that are not given explicitly in the interface above. Hence, we will
provide the WSDL file.
GT4services\org\globus\examples\services\core\first\impl\MathService.java.
Deployment Descriptor -- The deployment descriptor gives several different important sets of
information about the service once it is deployed. It is located within the GT4services folder
at:
GT4services\org\globus\examples\services\core\first\deploy-server.wsdd.
When the client is run from the command line, you pass it one argument. The argument is the
URL that specifies where the service resides. The client will create the end point rerference
and incorporate this URL as the address. The end point reference is then used with the
getMathPortTypePort method of a MathServiceAdressingLocator object to obtain a
reference to the Math interface (portType). Then, we can apply the methods available in the
service as though they were local methods Notice that the call to the service (add and subtract
method calls) must be in a “try {} catch(){}” block because a “RemoteException” may be
thrown. The code for the “MathServiceAddressingLocator” is created during the build
process. (Thus you don’t have to write it!)
globus-undeploy-gar org_globus_examples_services_core_first
which should result with the following output:
Undeploying gar...
Deleting /.
.
.
Undeploy successful
6 Adding Functionality to the Math Service
In this final task, you are asked to modify the Math service and associated files so the srvice
supports the multiplication operation. To do this task, you will need to modify:
MathService.java)
Math.wsdl)
The exact changes that are necessary are not given. You are to work them out yourself. You
will need to fully understand the contents of service code and WSDL files and then modify
them accordingly. Appendix A gives an explanation of the important parts of these files. Keep
all file names the same and simply redeploy the service afterwards. You will also need to add
a code to the client code (Client.java) to test the modified service to include multiplication.
Result:
Thus the Develop a new Web Service for Calculator was executed successfully.
2. Develop new OGSA-compliant Web Service
OBJECTIVE:
PROCEDURE:
Writing and deploying a WSRF Web Service is easier than you might think. You just have
to follow five simple steps
To run this program, as a minimum you will be required to have installed the following
prerequisite software
a. Download the latest Axis2 runtime from the above link and extract it. Now we
point Eclipse WTP to downloaded Axis2 Runtime. Open Window -> Preferences
-> Web Services -> Axis2 Emitter
Select the Axis2 Runtime tab and point to the correct Axis2 runtime location.
Alternatively at the Axis2 Preference tab, you can set the default setting that will
come up on the Web Services Creation wizards. For the moment we will accept
the default settings.
b. Click OK.
c. Next we need to create a project with the support of Axis2 features. Open File ->
New -> Other... -> Web -> Dynamic Web Project
Click next
d. Select the name Axis2WSTest as the Dynamic Web project name (you can
specify any name you prefer), and select the configured Tomcat runtime as the
target runtime.
Click next.
e. Select the Axis2 Web service facet
Click Finish.
f. This will create a dynamic Web project in the workbench
g. Import the wtp/Converter.java class into Axis2WSTest/src (be sure to preserve the
package).
Click next.
i. The Web service wizard would be brought up with Web service type set
to Bottom up Java bean Web Service with the service implementation
automatically filled in. Move the service scale to Start service.
j. Click on the Web Service runtime link to select the Axis2 runtime.
Click OK.
k. Ensure that the correct server and service project are selected as displayed below.
Click next.
l. This page is the service.xml selection page. if you have a custom services.xml,
you can include that by clicking the Browse button. For the moment, just leave it
at the default.
Click next.
m. This page is the Start Server page. It will be displayed if the server has not
been started. Click on the Start Server button. This will start the server
runtime.
Click next.
n. This page is the Web services publication page, accept the defaults.
Click Finish.
o. Now, select the Axis2WSTest dynamic Web project, right-click and select Run ->
Run As -> Run on Server to bring up the Axis2 servlet.
Click Next.
p. Make sure you have the Axis2WSTest dynamic Web project on the right-hand
side under the Configured project.
Click Finish.
q. This will deploy the Axis2 server webapp on the configured servlet container
and will display the Axis2 home page. Note that the servlet container will start
up according to the Server configuration files on your workspace.
r. Click on the Services link to view the available services. The newly created
converter Web service will be shown there.
s. Click on the Converter Service link to display the wsdl URL of the newly created
Web service. Copy the URL.
t. Now we'll generate the client for the newly created service by referring the ?wsdl
generated by the Axis2 Server. Open File -> New -> Other... -> Web Services ->
Web ServiceClient
u. Paste the URL that was copied earlier into the service definition field.
v. Click on the Client project hyperlink and enter Axis2WSTestClient as the name
of the client project. Click OK.
Back on the Web Services Client wizard, make sure the Web service runtime is set
to Axis2 and the server is set correctly. Click Next.
Next page is the Client Configuration Page. Accept the defaults and click Finish.
The Clients stubs will be generated to your Dynamic Web project Axis2WSTestClient.
Now we are going to write Java main program to invoke the client stub. Import the
ConverterClient.java file to the workspace into the wtp package in the src folder of
Axis2WSTestClient.
Then select the ConverterClient file, right-click and select Run As -> Java Application.
Here's what you get on the server console:
Another way to test and invoke the service is to select Generate test case to test the
service check box on the Axis2 Client Web Service Configuration Page when going
through the Web Service Client wizard.
If that option is selected, the Axis2 emitter will generate JUnit testcases matching the
WSDL we provide to the client. These JUnit testcases will be generated to a newly added
source directory to the Axis2WSTestClient project called test.
Next thing we need to do is to insert the test case with the valid inputs as the Web
service method arguments. In this case, let's test the
ConverterConverterSOAP11Port_httpTest.java by provide values for Celsius and
Farenheit for the temperature conversion. As an example, replace the generated
TODO statement in each test method to fill in the data with values as:
testfarenheitToCelsius() -> farenheitToCelsius8.setFarenheit(212);
testStartfarenheitToCelsius() -
>farenheitToCelsius8.setFarenheit(212);
testcelsiusToFarenheit() -> celsiusToFarenheit10.setCelsius(100);
testStartcelsiusToFarenheit() ->
celsiusToFarenheit10.setCelsius(100);
Here the testcases were generated to test both the synchronous and asynchronous
clients.
w. After that, select the testcase, right-click, select Run As -> JUnit Test. You will be
able to run the unit test successfully invoking the Web service.
The Web Service wizard orchestrates the end-to-end generation, assembly, deployment,
installation and execution of the Web service and Web service client. Now that your Web
service is running, there are a few interesting things you can do with this WSDL file.
Examples:
You can choose Web Services -> Test with Web Services Explorer to test the
service.
You can choose Web Services -> Publish WSDL file to publish the service to a
public UDDI registry.
RESULT:
Thus the development of a new OGSA-compliant web service was executed successfully.
3.Using Apache Axis develop a Grid Service
OBJECTIVE:
PROCEDURE:
You will need to download and install the following software:
1. Java 2 SDK v1.4.1, http://java.sun.com/j2se/1.4.1/download.html
2. Apache Tomcat v4.124
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.24/bin/jakarta
tomcat4.1.24.exe.
3. XML Security v1.0.4,
http://www.apache.org/dist/xml/security/java-library/xmlsecurity bin1.0.4.zip
4. Axis v1.1, http://ws.apache.org/axis/dist/1_1/axis-1_1.zip
1. Java 2 SDK
• Run the downloaded executable (j2sdk-1_4_1-windows-i586.exe) which will install
the
• SDK in C:\j2sdk1.4.1. Set the JAVA_HOME environment variable to point to
this directory as follows:
• Click on START->CONTROL PANEL->SYSTEM
• Click on the Advanced tab
• Click on the Environment Variables button
• Click on the New… button in the user variable section and enter the details
• Add the Java binaries to your PATH variable in the same way by setting a user
variable called PATH with the value “%PATH%;C:\j2sdk1.4.1\bin”
2. Apache Tomcat
3. XML Security
• Download and unzip
http://www.apache.org/dist/xml/security/javalibrary/xmlsecurity-bin 1_0_4.zip
• Copy xml-sec.jar to C:\axis-1_1\lib\
• Set-up your CLASSPATH environment variable to including the following:
C:\axis1_1\lib\xml-sec.jar;
4. Apache Axis
• Unzip the downloaded Axis archive to C: (this will create a directory C:\axis-1_1).
• Extract the file xmlsec.jar from the downloaded security archive to
C:\axis1_1\webapps\axis\WEB-INF\lib.
• Set-up your CLASSPATH environment variable to including the following:
o The current working directory
o All the AXIS jar files as found in C:\axis-1_1\lib
C:\jakarta-tomcat-4.1.24\common\lib\servlet.jar
• Your CLASSPATH should therefore look something like:
C:\axis-1_1\lib\axis.jar;
C:\axis 1_1\lib\axis-ant.jar;
C:\axis-1_1\lib\commons-discovery.jar;
C:\axis-1_1\lib\commons-logging.jar;
C:\axis-1_1\lib\jaxrpc.jar;
C:\axis-1_1\lib\log4j-1.2.8.jar;
C:\axis-1_1\lib\saaj.jar;
C:\axis-1_1\lib\wsdl4j.jar;
C:\axis-1_1\lib\xercesImpl.jar
C:\axis-1_1\lib\xmlParserAPIs.jar;
C:\jakarta-tomcat-4.1.24\common\lib\servlet.jar
C:\axis-1_1\lib\xml-sec.jar;
• Now tell Tomcat about your Axis web application by creating the file
C:\jakarta- tomcat-4.1.24\webapps\axis.xml with the following content:
<Context path="/axis" docBase="C:\axis-1_1\webapps\axis" debug="0"
privileged="true">
<LoggerclassName="org.apache.catalina.logger.FileLogger"prefix="axis_log."
suffix=".txt" timestamp="false"/>
Deploy one of the sample Web Services to test the system and to create the C:\axis-
1_1\webapps\axis\WEB-INF\server-config.wsdd file. From C:\axis-1_1 issue the
command (on one line):
java org.apache.axis.client.AdminClient
http://localhost:8080/axis/services/AdminService/samples/stock/deploy.wsdd
This should return the following:
.- Processing file samples/stock/deploy.wsdd
.- <Admin>Done processing</Admin>
RESULT:
Thus the development of a Grid Service using Apache Axis is executed successfully.
4. Develop applications using Java or C/C++ Grid APIs
OBJECTIVE:
To develop an applications using Java or C/C++ Grid APIs.
SAMPLE CODE:
import AgentTeamwork.Ateam.*;
import MPJ.*;
public class UserProgAteam extends AteamProg {
private int phase;
public UserProgAteam( Ateam o )
{}
public UserProgAteam( )
{}
// real const
public UserProgAteam( String[] args )
{ phase = 0;
}
// phase recovery
private void userRecovery( ) {
phase = ateam.getSnapshotId( );
}
private void compute( ) {
for ( phase = 0; phase < 10; phase++ ) {
try {
Thread.currentThread( ).sleep( 1000 );
}
catch(InterruptedException e ) {
}
ateam.takeSnapshot( phase );
System.out.println( "UserProgAteam at rank " + MPJ.COMM_WORLD.Rank( ) + " : took a
snapshot " + phase );
}
}
public static void main( String[] args ) {
System.out.println( "UserProgAteam: got started"
); MPJ.Init( args, ateam);
UserProgAteam program = null;
// Timer timer = new Timer(
); if ( ateam.isResumed( ) ) {
program = ( UserProgAteam )
ateam.retrieveLocalVar( "program" );
program.userRecovery( );
}
else
{
program = new UserProgAteam( args );
ateam.registerLocalVar( "program", program );
}
program.compute( );
MPJ.Finalize( );
}
public class UserProgAteam extends AteamProg {
// application body private void compute( )
{ for ( phase = 0; phase < 10; phase++ ) {
try {
Thread.currentThread( ).sleep( 1000 );
}
catch(InterruptedException e ) {
}
ateam.takeSnapshot( phase );
System.out.println ( "UserProgAteam at rank " + MPJ.COMM_WORLD.Rank() + " : took a
snapshot " + phase );
}}
RESULT:
Thus the development of applications using Java or C/C++ Grid APIs is executed successfully
6. Create an word document of your class time table and store locally and on the cloud with doc,and pdf
format . ( use www.zoho.com and docs.google.com)
Steps:
With Google Docs, you can create and edit text documents right in your web browser—no
special software is required. Even better, multiple people can work at the same time, you
can see people’s changes as they make them, and every change is saved automatically.
In Drive, click New > Google Docs > Blank document or From a template.
If you have existing text documents, such as Microsoft® Word® or Adobe®PDF files, you can
import and convert them to Docs.
Go to Drive.
Click New > File Upload and choose a text document from your computer. Supported
files include .doc, .docx, .dot, .html, plain text (.txt), .odt, and .rtf.
Right-click the file you want to convert and select Open with > Google Docs.
Converting your document from another program creates a copy of your original file in Docs
format. You can then edit it in your browser like any other document.
Everyone you shared the document with receives an email with a link to the document.
7. Create a spread sheet which contains employee salary information and calculate gross and
total sal using the formula
DA=10% OF
BASIC HRA=30%
OF BASIC
PF=10% OF BASIC IF
IF BASIC<=1500
NET_SALARY=BASIC_SALARY+DA+HRA-PF
TAX
8. Create your resume in a neat format using google and zoho cloud Programs on PaaS
9. Write a Google app engine program to generat n even numbers and deploy it to google cloud
Steps
Steps:
2. If you have the Google Plugin for Eclipse installed, complete the migrating from GPE procedures.
6. Or from inside Eclipse, select Help > Eclipse Marketplace... and search for Google Cloud.
7. Restart Eclipse when prompted.
App engine Program to generate n even numbers using java servlet application
<!DOCTYPE html>
<head>
</head>
<body>
</form>
</body>
</html>
import java.io.IOException;
import
javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import
javax.servlet.http.HttpServletRequest;
import
javax.servlet.http.HttpServletResponse;
@WebServlet(
name =
"HelloAppEngine",
urlPatterns = {"/hello"}
@Override
response.setContentType("text/plain")
response.setCharacterEncoding("UTF-
8");
int a1=
Integer.parseInt(request.getParameter("n1")); for
if(i%2==0)
response.getWriter().print("\t"+i);
}
Import
java.util.Calendar;
import
java.util.LinkedList;
import gridsim.*;
class Example1
try
int num_user = 0;
Calendar calendar =
Calendar.getInstance(); boolean
trace_flag = true;
String[] exclude_from_file = { "" };
String[] exclude_from_processing = {
"" };
exclude_from_file,
exclude_from_processing, report_name);
GridResource gridResource =
createGridResource();
catch (Exception e)
e.printStackTrace();
System.out.println("Unwanted error
happens");
System.out.println("Starting to create one Grid resource with " + "3 Machines ...");
list");
System.out.println("Creates the 1st Machine that has 4 PEs and " + "stores it into
the
Machine list");
"+
"+
system
resource
ResourceCharacteristics.TIME_SHARED, time_zone,
cost);
System.out.println();
speed
long seed = 11L*13*17*19*23+1;
LinkedList<Integer>(); Weekends.add(new
Integer(Calendar.SATURDAY)); Weekends.add(new
Integer(Calendar.SUNDAY));
LinkedList<Integer>();
GridResource gridRes =
null; try
Weekends, Holidays);
catch (Exception e)
{ e.printStackTrac
e();
}
Output:
11. Program to create one or more Grid users. A Grid user contains one or more Gridlets.
import java.util.*; import gridsim.*;
class Example2
try
{
GridletList list = createGridlet(); System.out.println("Creating " + list.size() + " Gridlets"); ResourceUserList userList =
createGridUser(list);
System.out.println("Creating " + userList.size() + " Grid users"); printGridletList(list);
System.out.println("Finish the example");
}
catch (Exception e)
return list;
}
{
ResourceUserList userList = new ResourceUserList();
return userList;
}
} // end class
12. Program to show how a grid user submits its Gridlets or task to many grid
resource entities
import
java.util.*;
import
gridsim.*;
public class
Test
{
private static final int MIN = 1; // min number of test cases
private static final int MAX = 8; // max number of test cases
/**
* Usage in Unix / Linux:
* javac -classpath $GRIDSIM/gridsim.jar:. Test.java
* java Test [policy: space | time] [test case number: 1 - 8]
*
* For example: java Test space 7 --> running Space-Shared for test case #7
* java Test time 3 --> running Time-Shared for test case #3
*
* The operation of these Test Cases offer are:
* Test Case 1: Submit Gridlets - then wait until all Finish to collect
* Test Case 2: Submit Gridlets - Cancel some of them - Finish
* Test Case 3: Submit Gridlets - Pause some of them - Cancel - Finish
* Test Case 4: Submit Gridlets - Pause - Resume - Cancel - Finish
* Test Case 5: Submit Gridlets - Move some of them - Finish
* Test Case 6: Submit Gridlets - Pause - Move - Finish
* Test Case 7: Submit Gridlets - Pause - Resume - Move - Finish
* Test Case 8: Submit Gridlets - Pause - Resume - Move - Cancel - Finish
*
* NOTE:
* - Test Case 1 is the simplest and Test Case 8 is the most complicated.
*
* - These Test Cases are quite flexible, meaning, you can adjust how big
* these experiments are by increasing/decreasing totalUser, totalPE, etc
* from main() only. You don't need to modify
* any of the Test Case classes.
*
* - Be careful when setting the numbers too high (above 200)
* since you might get Java "Out of Memory" exception.
*
* - For an effective experiment for Gridlet or Job migration, you need to
* have a large number of GridResource entities, say more than 6.
*/
public static void main(String[] args)
{
System.out.println("Starting Test
Cases"); try
{
// Parse the command line
args int policy = 0;
if ( args[0].equals("t") || args[0].equals("time")
) { policy =
ResourceCharacteristics.TIME_SHARED;
}
else if ( args[0].equals("s") ||
args[0].equals("space") ) { policy =
ResourceCharacteristics.SPACE_SHARED;
}
else {
System.out.println("Error -- Invalid allocation policy");
return;
}
////////////////////////////////////////
// First step: Initialize the GridSim package. It should be called
// before creating any entities. We can't run this example without
// initializing GridSim first. We will get run-time exception
// error.
Calendar calendar = Calendar.getInstance();
boolean trace_flag = false; // true means tracing GridSim events
//////////////////////////////////////
// Second step: Creates one or more GridResource objects
int totalResource = 3; // total GridResources for this
experiment int totalMachine = 1; // total Machines for each
GridResource int totalPE = 3; // total PEs for each
Machine createResource(totalResource, totalMachine,
totalPE, baudRate,
peRating, price, policy);
/////////////////////////////////////
// Third step: Creates grid users
int totalGridlet = 4; // total Gridlets for each User
createUser(totalUser, totalGridlet, gridletLength,
baudRate,
testNum);
////////////////////////////////////
// Fourth step: Starts the
simulation
GridSim.startGridSimulation();
}
catch (Exception e)
{
System.out.println("Unwanted errors happen");
System.out.println( e.getMessage() );
System.out.println("Usage: java Test [time | space] [1-
8]");
}
System.out.println("=============== END OF TEST ====================");
}
/**
* Creates many GridResources
*/
public static void createResource(int totalRes, int
totalMachine, int totalPE, double[] baudRate,
int[] peRating, double[] price, int policy)
{
double bandwidth =
0; double cost = 0.0;
// creates a GridResource
createGridResource(name, totalMachine, totalPE,
bandwidth, peRating, policy, cost);
}
}
/**
* Creates many Grid Users
*/
public static void createUser(int totalUser, int
totalGridlet, int[] glLength, double[]
baudRate, int testNum)
{
try
{
double bandwidth =
0; double delay =
0.0;
/**
* A selection of different test cases
*/
private static void createTestCase(String name, double bandwidth,
double delay, int totalGridlet, int[] glLength,
int testNum) throws Exception
{
switch(testNum)
{
case 1:
new TestCase1(name, bandwidth, delay, totalGridlet,
glLength); break;
case 2:
new TestCase2(name, bandwidth, delay, totalGridlet,
glLength); break;
case 3:
new TestCase3(name, bandwidth, delay, totalGridlet,
glLength); break;
case 4:
new TestCase4(name, bandwidth, delay, totalGridlet,
glLength); break;
case 5:
new TestCase5(name, bandwidth, delay, totalGridlet,
glLength); break;
case 6:
new TestCase6(name, bandwidth, delay, totalGridlet,
glLength); break;
case 7:
new TestCase7(name, bandwidth, delay, totalGridlet,
glLength); break;
case 8:
new TestCase8(name, bandwidth, delay, totalGridlet,
glLength); break;
default:
System.out.println("Not a recognized test
case."); break;
}
}
/**
* Creates one Grid resource. A Grid resource contains one or more
* Machines. Similarly, a Machine contains one or more PEs (Processing
* Elements or CPUs).
*/
private static void createGridResource(String name, int
totalMachine, int totalPE, double bandwidth, int[]
peRating,
int policy, double cost)
{
// Here are the steps needed to create a Grid resource:
// 1. We need to create an object of MachineList to store one or more
// Machines
MachineList mList = new MachineList();
int rating = 0;
for (int i = 0; i < totalMachine; i++)
{
// even Machines have different PE rating compare to odd
ones if (i % 2 == 0) {
rating = peRating[0];
}
else {
rating = peRating[1];
}
} // end class
13. Program to show how to create one or more grid users and
submits its Gridlets or task to many grid resource entities
import
java.util.*;
import
gridsim.*;
/**
* You can play around with this class by adjusting few parameters in main()
*/
of test cases
/**
* For example: java Test space 7 --> running Space-Shared for test case #7
* Test Case 1: Submit Gridlets - then wait until all Finish to collect
* NOTE:
* - Test Case 1 is the simplest and Test Case 8 is the most complicated.
* - These Test Cases are quite flexible, meaning, you can adjust how big
*/
System.out.println("Starting Test
Cases"); try
if ( args[0].equals("t") || args[0].equals("time")
) { policy =
ResourceCharacteristics.TIME_SHARED;
}
else if ( args[0].equals("s") ||
args[0].equals("space") ) { policy =
ResourceCharacteristics.SPACE_SHARED;
else {
return;
Integer.parseInt(args[1]);
////////////////////////////////////////
// error.
// statistical measures
String[] exclude_from_file = { "" };
String[] exclude_from_processing = {
"" };
// anything here.
even, odd
4000, 5000};
exclude_from_processing, report_name);
//////////////////////////////////////
totalPE, baudRate,
baudRate,
testNum);
////////////////////////////////////
simulation
GridSim.startGridSimulation();
catch (Exception e)
System.out.println( e.getMessage() );
8]");
/**
int[] peRating,
double[] price, int policy)
double bandwidth =
+)
+ i; if (i % 2 == 0)
bandwidth =
baudRate[0]; cost =
price[0];
else
bandwidth =
baudRate[1]; cost =
price[1];
// creates a GridResource
}
/**
*/
try
double bandwidth =
0; double delay =
0.0;
+ i; if (i % 2 == 0) {
bandwidth =
baudRate[0]; delay =
5.0;
else {
bandwidth = baudRate[1];
}
// creates a Grid user
catch (Exception e) {
// ... ignore
/**
*/
glLength,
switch(testNum)
case 1:
glLength); break;
case 2:
break;
case 3:
break;
case 4:
break;
case 5:
break;
case 6:
break;
case 7:
break;
case 8:
break;
default:
System.out.println("Not a recognized test
case."); break;
/**
* Elements or CPUs).
*/
peRating,
// Machines
int rating = 0;
ones if (i % 2 == 0) {
rating = peRating[0];
}
else {
rating = peRating[1];
operating system
time_zone, cost);
during holiday
// incorporates weekends so the grid resource is on 7 days a
Weekends.add(new Integer(Calendar.SATURDAY));
Weekends.add(new Integer(Calendar.SUNDAY));
try
Weekends, Holidays);
catch (Exception e)
System.out.println("Error in creating
GridResource."); System.out.println(
e.getMessage() );
name); return;
}
} // end class
13. Program to creates one Grid resource with three machines
14. Google app engine program to validate the user use mysql to store user info and deploy on to cloud.
15. Write a Google app engine program to display nth largest no from the given list of numbers and deploy it in
Google cloud
16. Google app engine program to validate user; create a database login(username, password)in mysql and
deploy to cloud