SHREE VENKATESHWARA

HI-TECH ENGINEERING COLLEGE

GOBI-638 455

NAME OF THE LAB__________________________________________________________

University Register No___________________________________________

Name ___________________________________ Roll No______________________

Branch__________________________________ Batch_______________________

Certified that this is bonafide record of work done by the above student during
the year 20 -20

LAB IN-CHARGE HEAD OF THE DEPARTMENT

Submitted for the practical Examination held on _____________________________________

INTERNAL EXAMINER EXTERNAL EXAMINER

 INDEX

S.N PAGE FACULTY

DATE NAME OF THE EXPERIMENT MARKS
O. NO. SIGNATURE

1 Install Virtualbox/Vmware Workstation

2 Install C Compiler In Virtual Machine

3 Installing And Running The Google App

Engine On Windows
GAE Launcher To Launch The Web
4
Applications

5 Cloud Scenario Using Cloud Sim

Transfer The Files From One Virtual

6
Machine To Another Virtual Machine

7 Launch Virtual Machine Using Trystack

8 Install Hadoop Single Node Cluster

ADDITIONAL EXPERIMENTS

Develop a new Web Service for

9
Calculator

10 Develop new OGSA-compliant Web

Service.
Using Apache Axis develop a Grid
11
Service.
EX.No:1 INSTALL VIRTUALBOX/VMWARE WORKSTATION

Date:

Aim:
Find procedure to Install Virtual box/VMware Workstation with different flavors 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.

Step 2- Download the installer file

It should probably be in the download folder by default, if you have not changed the settings in your
browser. File name should be something like VMware-workstation-full-15.5.1-15018445.exe. This
file name can change depending on the version of the software currently available for download.
But for now, till the next version is available, they will all be VMware Workstation 15 Pro.

Step 3- Locate the downloaded installer file

For demonstration purpose, I have placed the downloaded installer on my desktop. Find the installer
on your system and double click to launch the application.

VMware workstation 15 pro for windows 10 installer file screenshot.

Step 4- User Access Control (UAC) Warning
Now you should see User Access Control (UAC) dialog box. Click yes to continue.

VMware Workstation 12 Pro installer windows 10 UAC screenshot

Initial Splash screen will appear. Wait for the process to complete.

VMware Workstation 15 Installation Splash Screen

Step 5- VMware Workstation Setup wizard
Now you will see VMware Workstation setup wizard dialog box. Click next to continue.
Step 6- End User License Agreement
This time you should see End User License Agreement dialog box. Check “I accept the terms in the
License Agreement” box and press next to continue.

VMware Workstation 15 Installation – End User License Agreement

Step 7- Custom Setup options
Select the folder in which you would like to install the application. There is no harm in leaving the
defaults as it is. Also select Enhanced Keyboard Driver check box.

VMware Workstation 15 Pro installation – select installation folder

Step 8- User Experience Settings
Next you are asked to select “Check for Updates” and “Help improve VMware Workstation Pro”. Do
as
you wish. I normally leave it to defaults that is unchecked.

VMware Workstation 15 Installation – User Experience

Settings

Step 9- Application Shortcuts preference

Next step is to select the place you want the shortcut icons to be placed on your system to launch the
application. Please select both the options, desktop and start menu and click next.

VMware workstation 15 pro installation shortcut selection checkbox screenshot.

Step 10- Installation begins
Now you see the begin installation dialog box. Click install to start the installation process.

Screenshot for VMware Workstation 15 pro installation process.

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
 Step 11- Launch VMware Workstation
After the installation completes, you should see VMware Workstation icon on the desktop. Double
click on it to launch the application.

Step 12- Licence Key

If you see the dialog box asking for licence key, click on trial or enter the licence key. Then what
you have is the VMware Workstation 15 Pro running on your windows 10 desktop. If don’t have
the licence key, you will have 30 days trial.

VMware Workstation 15 Pro home screen

Step 13- At some point if you decide to buy

At some point of time if you decide to buy the License key, you can enter the License key by going
to Help->Enter a License Key
You can enter the 25 character license key in the dialog box shown below and click OK. Now you
have the license version of the software.

Result:

Thus the Virtual Box or VMware is successfully installed on top of windows 7 or 8.

EX.No:2 INSTALL C COMPILER IN VIRTUAL MACHINE

Date:

INSTALLVIRTUALBOX

1. Visithttp://www.virtualbox.org/wiki/downloads
2. Download VirtualBox platform packages for yourOS
3. Open the Installation Package by double clicking

4. Click continue and finish installingVirtualBox

5. When finished installation, close thewindow.

DOWNLOAD LINUX

I.Visit the page http://www.ubuntu.com/download/ubuntu/download

2. Choose the latest version of ubuntu and32-bit and click “startdownload”

CL¦
CK

INSTALL LINUX USING VIRTUALBOX

1. Run VirtualBox by double-clicking theicon
2. Click “New” button on the top leftcorner
3. Click “Continue” on the pop-upwindow
4. TypeVN name,select“Linux” for the OS and choose “Ubuntu” for the version.

5. Choose the amount of memory to allocate (I suggest choosing between 5I2 NB to

I024 NB)
6. Click Continue or Next
7. Choose create a new virtual hard disk
8. Click Continue or Next

9. Choose VDI (VirtualBox DiskImage)

10.Click Continue or Next
11. Choose “DynamicallyAllocated” click continue. This way, the size of yourVirtual Hard Disk will
grow as you use.

12.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
14. Click Create

RUNNING LINUX

1. Choose Ubuntu from left column and click start.

2. Click continue on pop-up window

3. Click the folder icon and choose the ubuntu iso file you downloaded and click continue and start
4. Click Install Ubuntu

5. Check “Download updates” and clickForward

6. Choose “Erase disk and install Ubuntu” and click Forward (Don’t worry, it won’t wipe your computer)

7. Click “Install Now” and wait. Naybe grab asnack.

8.When finished, click Restart and pressEnter.
C PROGRAMMING ON LINUX
I.OpenTerminal(Applications-Accessories-Terminal)

2. Open gedit by typing “gedit &” onterminal

3. Type the following on gedit
#include<stdio.h>
Main()
{
Printf(“Hello World”\n);
}
4.Save this file as “helloworld.c”

C Programming on Linux

5. Type “ls” on Terminal to see all files under currentfolder

6. Confirm that “helloworld.c” is in the currentdirectory. If not,type cd DIRECTORY_PATH to go to the
directory that has“helloworld.c”
7. Type “gcc helloworld.c” to compile, and type “ls” to confirm that a new executable file “a.out” is created
8. Type “./a.out” on Terminal to run theprogram
9. If you see “HelloWorld” on the next line, you just successfully ran your first C program!
10.Try other codes from “A Shotgun Introduction to C” on professor Edwards’s webpage.You can also
find many C programing guides online. (justgoogle it!) Enjoy :)

Result:
Thus the C compiler is created using virtual box and execute Simple Programs are executed
successfully.
EX.No:3 INSTALLING AND RUNNING THE GOOGLE APP
ENGINE ON WINDOWS
Date:

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.

Pre--Requisites: Python 2.5.4

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/

Download and Install

You can download the Google App Engine SDK by going to:

http://code.google.com/appengine/downloads.html

and download the appropriate install package.

Download the Windows installer – the simplest thing is to download it to your Desktop or
another folder that you remember.

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

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:

C:\Documents and Settings\csev\Desktop\apps

And then make a sub--‐folder in within apps called “ae--01--trivial” – the path to this
folder would be:

C:\ Documents and Settings \csev\Desktop\apps\ae--01--trivial

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
Then create a file in the ae--01--trivial folder called index.py with three lines in it:

print 'Content-Type:
text/plain' print ' '
print 'Hello there Chuck'

Then start the GoogleAppEngineLauncher program that can be found under Applications. Use the
File --> Add Existing Application command and navigate into the apps directory and select the ae-
-01--trivial folder. Once you have added the application, select it so that you can control the
application using the launcher.

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.

Watching the Log

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:
Each time you press Refresh in your browser – you can see it retrieving the output with a
GET request.

Dealing With Errors

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:
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.

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.

Shutting Down the Server

To shut down the server, use the Launcher, select your application and press the Stop button.

Result:
Thus the Google App Engine is installed and simple web application is executed successfully.
EX.No:4 GAE LAUNCHER TO LAUNCH THE WEB
APPLICATIONS
Date

Google App Engine is a great way to get started with learning web development. It provides a
bunch of useful features such as sharding, automatic database replication, automatic scaling,
memcache, and so on.

PROCEDURE:

Step 1. Download the basic housekeeping stuff

No matter what platform you build products on, there is always some housekeeping stuff you
need to put in place before you can hit the ground running. And deploying apps within the Google
App Engine is no exception.

1. Download Python 2.7

As of when this article was written, the Google App Engine standard environment supports
Python only upto version 2.7. However, it is only a matter of time before support for Python
3.x is added. You can check the App Engine docs for the latest info.

2. Download Google Cloud SDK

This will allow you to fork apps onto your local machine, make changes (edit and develop the
app), and deploy your app back to the cloud.

3. Set the Python path in the Google App Engine launcher

After downloading the SDK, launch the App Engine launcher, go to Edit -> Preferences and
make sure you set the path for where you installed Python in step 1 above.
Step 2. App Engine sign-up

This is often the most confusing part of the entire setup. Things you should know when you sign-up:

1. Currently, App Engine offers a free trial for one year.

2. The trial includes $300 of credit that can be used during the one year trial period.
3. You will need to add a credit card to sign-up (for verification purposes).
4. You will not be charged during the sign-up process.
5. You will not be charged during the trial period as long as you do not cross the credit limit
offered.

Here are the steps you need to follow to sign-up:

1. Go to the Google Cloud landing page

2. Follow the sign-up process and go to your App Engine dashboard

Most of the hard work is complete after a successful sign-up.

Step 3. Create a new project

The next step is to create a new Python project that you can work on. Follow the screenshots below to
create a new project.

Launch the new project wizard.

Give your app a name and make a note of your project ID.

Hit the create button and Google should take a few minutes to set up all that is necessary for your newly
created app.

Step 4. Fork the app to develop it locally

The next step in the process is to fork the app on your local machine. This will allow you to make
changes to the app locally and deploy it whenever you wish to.

Go to Google App Engine launcher and create a new application.

Enter the project ID of your newly created app. Also, provide the folder (local destination) where you wish to
store the app locally. Make sure you select the Python 2.7 as your runtime engine.

Hit the create button, and you should see your app listed on the window that follows. You should also check that
you now see some files in your local storage (the directory you chose in the screenshot above) after this step.

Step 5. Run the app locally

Before you go ahead and make some changes to the app, it is important to check whether or not you
have executed all the above steps correctly. This can be done by simply running the app locally.

Select the app and hit the run button on the window.

Wait for a few seconds until you can hit the Browse button. Once the Browse button becomes clickable,
click it. This should take you to the browser, and you should see the hello world text appear in your
browser window. Alternatively, you can manually go to the browser and use the port specified to access
the app.
Step 6. Understand the app structure

It is finally time to look at the lines of code which are running this webapp. Open your app folder in the
text editor of your choice. I recommend Sublime text or VS Code. However, feel free to choose the one
you prefer.

Here is a description of the various files.

app.yaml

This file is a basic markup file that stores information (some metadata) about the app. It is important to
note the following crucial parts of the file.

1. application
This is the project ID which you should never change. This is the unique identifier for the app
2. url -> script
This is the homepage for the app. In other words, this file will be rendered in your browser when
you launch the app
3. libraries
This is where you can include external libraries to use within the webapp
main.py

This is the homepage of the app (as discussed above). Note that the hello world text in the browser
window (step 5) is due to the code you see highlighted below.

Step 7. Make your changes and deploy the new app

No hello world app is ever complete without the developer changing the hello world text to something
else just to make sure that everything happening behind the scenes is working as it should.

Go ahead and change the text in the above screenshot to something else.

Save the changes, go to the browser and refresh the page. You should see the page with the text “MEOW”
displayed.
Finally, it is time to deploy your changes to the cloud to make them globally accessible via a URL. Go to the App
Engine launcher, select the app, and hit the Deploy button.

This will ensure your app gets deployed onto Google Cloud. To check whether or not everything worked
just fine, go to the URL below:

https://<yourProjectID>.appspot.com/

You should see the exact same window as above, expect now, it is a URL that is globally accessible.
Step 8. Misc

Congratulations, you’ve finally gotten your first Python webapp deployed on the Google App Engine.
Here are some other points which you may find useful.

1. Jinja 2 is an amazing front end templating library for Python that can do some cool stuff, such as passing
objects form Python to HTML, using for loops, if conditions, and so on directly out of the box
2. Here’s a very useful Udacity course on web development that I have personally found quite resourceful
3. Viewing the logs while running your webapp can be handy to debug and also discover some bugs on the
fly

Result:
Thus the GAE launcher is installed successfully and web application is launched.
EX.No:5 CLOUD SCENARIO USING CLOUD SIM

Date
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: CloudSim.init(num_user, calendar, trace_flag)
6. Data centres are the resource providers in CloudSim; hence, creation of data centres is a
second step. To create Datacenter, you need the DatacenterCharacteristics object that stores the
properties of a data centre such as architecture, OS, list of machines, allocation policy that covers
the time or spaceshared, the time zone and its price:
Datacenter datacenter9883 = new Datacenter(name, characteristics, new
VmAllocationPolicySimple(hostList), s
7. The third step is to create a broker:
DatacenterBroker broker = createBroker();
8. The fourth step is to create one virtual machine unique ID of the VM, userId ID of the VM’s
owner, mips, number Of Pes amount of CPUs, amount of RAM, amount of bandwidth, amount of
storage, virtual machine monitor, and cloudletScheduler policy for cloudlets:
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.
0.0: Broker: Cloud Resource List received with 1 resource(s)
0.0: Broker: Trying to Create VM #0 in Datacenter_0
0.1: 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!

Result:
Thus the Cloud Sim is installed and Scheduling Algorithm is executed Successfully.
EX.No:6 TRANSFER THE FILES FROM ONE VIRTUAL
MACHINE TO ANOTHER VIRTUAL MACHINE
Date:
VirtualBox is a program that allows you to run multiple operating systems (guests) on one computer
(the host computer). You may need to transfer files between the host and the guest. It’s easy to set up
in Windows guests, but tricky in Ubuntu guests

Once you’ve installed the guest additions, enable shared folders by adding a folder from your host
machine in the settings for the guest machine. To do this, first make sure the guest machine is
powered off. Then, select the guest machine in the list on the left of the VirtualBox Manager and
click Settings on the toolbar.

On the Settings dialog box, click Shared Folders in the list of options on the left. On the Shared
Folders screen, click the folder button with the plus sign to add a folder.
On the Add Share dialog box, select Other from the Folder Path drop-down list.

The Browse For Folder dialog box displays. Navigate to the folder you want to share between the
host and the guest, select it, and click OK.
The path to the selected folder is inserted in the Folder Path edit box. The name of the folder
automatically becomes the Folder Name, but you can change this name if you want. If you don’t want
to be able to change items in this folder in the guest machine, select the Read-only check box. To
have the selected folder automatically mounted in the guest machine when you boot it, select the
Auto-mount check box. Click OK once you’ve finished choosing your settings for the shared folder.

The selected folder displays in the Folders List. Click OK to close the dialog bo x.
Now, make sure the guest machine is still selected in the VirtualBox Manager and click Start to boot
it.

Once the guest machine is booted, open Nautilus (File Manager) by clicking the file cabinet on the
Unity bar on the left side of the desktop.

In the Devices list on the left, click Computer and then double-click the Media folder on the right.
You’ll see a folder named similarly to the folder you selected to share on your host machine with
“sf_” added to the beginning of the name.
If you double-click on that folder, the following dialog box displays. This is because there is one
more task to perform before you can access the shared folder.

In addition to users in Ubuntu, there are also groups. When VirtualBox installed the Ubuntu operating
system, it added a group called “vboxsf”. Before you can access any shared folders, you must add
yourself to the vboxsf group. To do this, press Ctrl + Alt + T to open a Terminal window. Type the
following at the prompt, replacing “[username]” with your username, and press Enter.

sudo adduser [username] vboxsf

Type your password when prompted and press Enter again. Messages display as you are being added
to the group and “Done.” displays when the process has been successfully completed.

To close the Terminal window, type “exit” (without the quotes) at the prompt and press Enter

To verify you are in the vboxsf group, you can type “id [username]” (without the quotes, and
replacing “[username]” with your username) at the prompt and press Enter. All the groups of which
the specified user is a member display.
Now, when you access the shared folder in the Media folder as described above, you should see any
files in that exist in that folder on the host machine.

You can edit these files directly in this folder if you DID NOT select the “Read-only” option when
selecting the folder in the Settings. You can also copy files into and out of this folder. If the folder
was set to “Read-only”, you can only copy files from this folder and cannot copy files into it.

Result:
Thus the file is successfully transferred from one virtual machine to another.
EX.No:7 LAUNCH VIRTUAL MACHINE USING TRYSTACK

Date

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

 Overview: What we will do?

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.

Step 1: Create Network

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.

1. Go to Network > Networks and then click Create Network.

2. In Network tab, fill Network Name for example internal and then click Next.
3. In Subnet tab,
1. Fill Network Address with appropriate CIDR, for example
192.168.1.0/24. Use private network CIDR block as the best practice.
2. Select IP Version with appropriate IP version, in this case IPv4.
3. Click Next.
4. In Subnet Details tab, fill DNS Name Servers with 8.8.8.8 (Google
DNS) and then click Create.

Step 2: Create Instance

Now, we will create an instance. The instance is a virtual machine in the cloud,
like AWS EC2. You need the instance to connect to the network that we just
created in the previous step.
1. Go to Compute > Instances and then click Launch Instance.
2. In Details tab,
1. Fill Instance Name, for example Ubuntu 1.
2. Select Flavor, for example m1.medium.
3. Fill Instance Count with 1.
4. Select Instance Boot Source with Boot from Image.
5. Select Image Name with Ubuntu 14.04 amd64 (243.7 MB) if you want install Ubuntu
14.04 in your virtual machine.
3. In Access & Security tab,
1. Click [+] button of Key Pair to import key pair. This key pair is a public and
private key that we will use to connect to the instance from our machine.
2. In Import Key Pair dialog,
1. Fill Key Pair Name with your machine name (for example Edward-Key).
2. Fill Public Key with your SSH public key (usually is in
~/.ssh/id_rsa.pub). See description in Import Key Pair dialog box
for more information. If you are using Windows, you can use
Puttygen to generate key pair.
3. Click Import key pair.
3. In Security Groups, mark/check default.
4. In Networking tab,
1. In Selected Networks, select network that have been created in Step 1, for example internal.
5. Click Launch.
6. If you want to create multiple instances, you can repeat step 1-5. I created
one more instance with instance name Ubuntu 2.

Step 3: Create Router

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.

1. Go to Network > Routers and then click Create Router.

2. Fill Router Name for example router1 and then click Create router.
3. Click on your router name link, for example router1, Router Details page.
4. Click Set Gateway button in upper right:
1. Select External networks with external.
2. Then OK.
5. Click Add Interface button.
1. Select Subnet with the network that you have been created in Step 1.
2. Click Add interface.
6. Go to Network > Network Topology. You will see the network topology. In the
example, there are two network, i.e. external and internal, those are bridged by a
router. There are
instances those are joined to internal network.

Step 4: Configure Floating IP Address

 Floating IP address is public IP address. It makes your instance is accessible from the
internet. When you launch your instance, the instance will have a private network IP, but no
public IP. In OpenStack, the public IPs is collected in a pool and managed by admin (in our
case is TryStack). You need to request a public (floating) IP address to be assigned to your
instance.
1. Go to Compute > Instance.
2. In one of your instances, click More > Associate Floating IP.
3. In IP Address, click Plus [+].
4. Select Pool to external and then click Allocate IP.
5. Click Associate.
6. Now you will get a public IP, e.g. 8.21.28.120, for your instance.

Step 5: Configure Access & Security

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.

Step 6: SSH to Your Instance

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.

Result:
The Virual machine using try stack is launched successfully.
EX.No:8 INSTALL HADOOP SINGLE NODE CLUSTER
Date

Install Hadoop

Step 1: Click here to download the Java 8 Package. Save this file in your home directory.

Step 2: Extract the Java Tar File.

Command: tar -xvf jdk-8u101-linux-i586.tar.gz

Fig: Hadoop Installation – Extracting Java Files

Step 3: Download the Hadoop 2.7.3 Package.

Command: wget https://archive.apache.org/dist/hadoop/core/hadoop-

2.7.3/hadoop- 2.7.3.tar.gz

Step 4: Extract the Hadoop tar File.

Command: tar -xvf hadoop-2.7.3.tar.gz

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

Then, save the bash file and close it.

For applying all these changes to the current Terminal, execute the source command.

Command: source .bashrc

Fig: Hadoop Installation – Refreshing environment variables

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: java -version

Fig: Hadoop Installation – Checking Java Version

Command: hadoop version

 Fig: Hadoop Installation – Checking Hadoop Version

Step 6: Edit the Hadoop Configuration files.

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

1
<?xml version="1.0" encoding="UTF-8"?>
2 <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
3 <configuration>
4 <property>
5 <name>fs.default.name</name>
6 <value>hdfs://localhost:9000</value>
</property>
7 </configuration>
8

Fig: Hadoop Installation – Configuring core-site.xml

Step 8: Edit hdfs-site.xml and edit the property mentioned below

inside
configuration tag:
hdfs-site.xml contains configuration settings of HDFS daemons (i.e. NameNode,
DataNode, Secondary NameNode). It also includes the replication factor and
block size of HDFS.

Command: vi hdfs-site.xml
Step 9: Edit the mapred-site.xml file and edit the property mentioned below
1
2 <?xml version="1.0" encoding="UTF-8"?>
3 <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<configuration>
4 <property>
5 <name>dfs.replication</name>
6 <value>1</value>
7 </property>
8 <property>
<name>dfs.permission</name>
9 <value>false</value>
10 </property>
11 </configuration>
12
inside configuration tag:

mapred-site.xml contains configuration settings of MapReduce application like

number of JVM that can run in parallel, the size of the mapper and the reducer
process, CPU cores available for a process, etc.

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.

Command: cp mapred-site.xml.template mapred-site.xml

Command: vi mapred-site.xml.

1
<?xml version="1.0" encoding="UTF-8"?>
2 <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
3 <configuration>
4 <property>
5 <name>mapreduce.framework.name</name>
6 <value>yarn</value>
</property>
7 </configuration>
8
Step 10: Edit yarn-site.xml and edit the property mentioned below inside
configuration tag:

yarn-site.xml contains configuration settings of ResourceManager and

NodeManager like application memory management size, the operation needed
on program & algorithm, etc.

Command: vi yarn-site.xml

Fig: Hadoop Installation – Configuring yarn-site.xml

1
2
<?xml version="1.0">
3 <configuration>
4 <property>
5 <name>yarn.nodemanager.aux-services</name>
6 <value>mapreduce_shuffle</value>
</property>
7 <property>
8 <name>yarn.nodemanager.auxservices.mapreduce.shuffle.class</
9 name>
1 <value>org.apache.hadoop.mapred.ShuffleHandler</value>
0 </property>
</configuration>
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
Step 12: Go to Hadoop home directory and format the NameNode.

Command: cd

Command: cd hadoop-2.7.3

Command: bin/hadoop namenode -format

Fig: Hadoop Installation – Formatting NameNode

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.

Step 13: Once the NameNode is formatted, go to hadoop-2.7.3/sbin directory and

start all the daemons.

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
The above command is a combination of start-dfs.sh, start-yarn.sh & mr-
jobhistory- daemon.sh

Or you can run all the services individually as below:

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.

Command: ./hadoop-daemon.sh start namenode

Start DataNode:

On startup, a DataNode connects to the Namenode and it responds to the requests from the
Namenode for different operations.

Command: ./hadoop-daemon.sh start datanode

Fig: Hadoop Installation – Starting DataNode

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.

Command: ./yarn-daemon.sh start resourcemanager

Fig: Hadoop Installation – Starting ResourceManager

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.

Command: ./yarn-daemon.sh start nodemanager

 See Batch Details

Fig: Hadoop Installation – Starting NodeManager

Start JobHistoryServer:

JobHistoryServer is responsible for servicing all job history related requests from client.

Command: ./mr-jobhistory-daemon.sh start historyserver

Step 14: To check that all the Hadoop services are up and running, run the below
command.
Command: jps

Fig: Hadoop Installation – Checking Daemons

 Step 15: Now open the Mozilla browser and go
to localhost:50070/dfshealth.html to check the NameNode interface.

Fig: Hadoop Installation – Starting WebUI

Congratulations, you have successfully installed a single node Hadoop cluster

Result:
The Hadoop is successfully installed on a single node cluster.
EX.NO:
DATE Develop a new Web Service for Calculator

Aim:
To develop a new Web Service for Calculator using Globus toolkit.

Algorithm

1. Create new project

2. Select java Empty Web Application
3. Give a name to your project and click ok button
4. Go to Solution Explorer and right click at your project
5. Select Add New Item and select Web Service application
6. Give it name and click ok button

MathService.java:
package gt3tutorial.core.first.impl;
import org.globus.ogsa.impl.ogsi.GridServiceImpl;import
gt3tutorial.core.first.Math.MathPortType; import
java.rmi.RemoteException;
public class MathImpl extends GridServiceImpl implements MathPortType
{
public MathImpl()
{
super("Simple Math Service");
}
public int add(int a, int b) throws
RemoteException
{
return a + b;
}
public int subtract(int a, int b) throws
RemoteException
{
return a - b;
}
public int multiply(int a, int b) throws
RemoteException
{
return a * b;
}
public float divide(int a, int b) throwsRemoteException
{
return a / b;
}}
 OUTPUT:

Result:

Thus the Web Service for Calculator is developed using Globus Toolkit successfully.
EX.NO:
DATE Develop new OGSA-compliant Web Service.

Aim:
To develop new OGSA-compliant Web Service.
Procedure:
 Choose New Project from the main menu.
 Select POM Project from the Maven category.

 Type MavenOSGiCDIProject as the Project name. Click Finish.

 When you click Finish, the IDE creates the POM project and opens the project in the
Projects window.
 Expand the Project Files node in the Projects window and double-click pom.xml to open
the file in the editor.
 The basic POM for the project should be similar to the following.
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance"
xsi:schemaLocation="http://maven.apache.org/POM/4
.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany</groupId>
<artifactId>MavenOSGiCDIProject</artifactId>
<version>1.0-SNAPSHOT</version>

<packaging>pom</packaging>
<properties><project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties></project>
  Modify the parent pom.xml to add the following elements. Save your changes.
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven- 4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany</groupId>
<artifactId>MavenOSGiCDIProject</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>pom</packaging>
<properties><project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<dependencyManagement><dependencies><dependency>
<groupId>org.osgi</groupId>
<artifactId>org.osgi.core</artifactId>
<version>4.2.0</version>
<scope>provided</scope>
</dependency></dependencies></dependencyManagement></project>

Creating the OSGi Bundle Projects

 The Maven category in the New Projects wizard includes an OSGi Bundle
archetype for creating OSGi bundle projects. When you create an OSGi bundle project,
the generated POM declares the org.osgi.core JAR as a dependency and specifies the
maven-bundle-plugin for building the project.
 Creating the MavenHelloServiceApi Interface Bundle
 In this exercise you will use the New Project wizard to create an OSGi bundle
project that will provide a simple interface that will be implemented by other bundles.
After you create the bundle and interface, you will modify the POM to update the
dependency on the org.osgi.core artifact that you specified in the parent POM project.
 Choose File > New Project to open the New Project wizard.
 Choose OSGi Bundle from Maven category. Click Next.
  Type MavenHelloServiceApi for the Project Name.
 Click Browse and select the MavenOSGiCDIProject POM project as the Location. Click
Finish.
 When you click Finish, the IDE creates the bundle project and opens the
project in the Projects window. If you open pom.xml for the MavenHelloServiceApi project
in the editor you can see that the packaging element specifies bundle and that the maven-
bundle-plugin will be used when building the bundle.
<project><modelVersion>4.0.0</modelVersion>
<parent><artifactId>MavenOSGiCDIProject</artifactId>
<groupId>com.mycompany</groupId>
<version>1.0-SNAPSHOT</version></parent>
<groupId>com.mycompany</groupId>
<artifactId>MavenHelloServiceApi</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>bundle</packaging>
<name>MavenHelloServiceApi OSGi Bundle</name>
<properties><project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<dependencies><dependency>
<groupId>org.osgi</groupId>
<artifactId>org.osgi.core</artifactId>
<version>4.3.0</version>
<scope>provided</scope>
</dependency></dependencies>
<build><plugins><plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.3.7</version>
<extensions>true</extensions>
<configuration><instructions>
<Bundle-
Activator>com.mycompany.mavenhelloserviceimpl.Activator</Bundle-
Activator>
<Export-Package />
</instructions></configuration></plugin>
...
</plugins></build>
...
<project>
 You can also see that when you create an OSGi bundle project using the
Maven OSGi Bundle archetype, the IDE added the org.osgi.core artifact as a dependency by
default.
 Right-click the MavenHelloServiceApi project node in the Projects window and choose
Properties.
 Select the Sources category in the Project Properties dialog box.
 Set the Source/Binary Format to 1.6 and confirm that the Encoding is UTF-8. Click OK.
 Right-click Source Packages node in the Projects window and choose New > Java Interface.
 Type Hello for the Class Name.
 Select com.mycompany.mavenhelloserviceapi as the Package. Click Finish.
 Add the following sayHello method to the interface (in bold) and save your changes.
  public interface Hello {
 String sayHello(String name);
}
 Right-click the project node in the Projects window and choose Build.
 After you build the project, if you open the Files window and expand the
project node you can see that MavenHelloServiceApi-1.0-SNAPSHOT.jar is created in the
target folder.


 The maven-bundle-plugin handles the generation of the MANIFEST.MF file
when you build the project. If you open the MANIFEST.MF file in the compiled JAR you
will see that the plugin generated a manifest header that declares the export packages. For
OSGi, all bundles that you want to be exposed and available to other bundles must be listed
in the Export-Package element in MANIFEST.MF.
 Confirm that the MANIFEST.MF contains the Export-Package element (the element shown in
bold in the example below).
 Manifest-Version: 1.0
 Bnd-LastModified: 1395049732676
 Build-Jdk: 1.7.0_45
 Built-By: nb
 Bundle-Activator: com.mycompany.mavenhelloserviceapi.Activator
 Bundle-ManifestVersion: 2
 Bundle-Name: MavenHelloServiceApi OSGi Bundle
 Bundle-SymbolicName: com.mycompany.MavenHelloServiceApi
 Bundle-Version: 1.0.0.SNAPSHOT
 Created-By: Apache Maven Bundle Plugin
 Export-Package:
com.mycompany.mavenhelloserviceapi;uses:="org.osgi.frame
work";version="1.0.0.SNAPSHOT"
 Import-Package: org.osgi.framework;version="[1.6,2)"
 Tool: Bnd-1.50.0
 The OSGi container will read the Export-Package manifest header to
determine the classes in the bundle that can be accessed from outside the bundle. In this
example, the classes in the com.mycompany.mavenhelloserviceapi package are exposed.
 Note. If the MANIFEST.MF does not contain the Export-Package element,
you will need to enable the default plugin behavior for the plugin in the Project Properties
window and rebuild the project. In the Project Properties window, select the Export
Packages category and select the Default maven-bundle-plugin behavior option. You
can use the Export Packages panel of the Project Properties window to explicitly specify
the packages that should be exposed or specify the packages directly in pom.xml.
  Creating the MavenHelloServiceImpl Implementation Bundle
 In this exercise you will create the MavenHelloServiceImpl in the POM
project.
 Choose File > New Project to open the New Project wizard.
 Choose OSGi Bundle from the Maven category. Click Next.
 Type MavenHelloServiceImpl for the Project Name.
 Click Browse and select the MavenOSGiCDIProject POM project as the Location
(if not selected). Click Finish.
 Right-click the project node in the Projects window and choose Properties.
 Select the Sources category in the Project Properties dialog box.
 Set the Source/Binary Format to 1.6 and confirm that the Encoding is UTF-8. Click OK.
 Right-click Source Packages node in the Projects window and choose New > Java Class.
 Type HelloImpl for the Class Name.
 Select com.mycompany.mavenhelloserviceimpl as the Package. Click Finish.
 Type the following (in bold) and save your changes.
 public class HelloImpl implements Hello {
public String sayHello(String name) { return "Hello " + name; }}
 When you implement Hello, the IDE will display an error that you need to
resolve by adding the MavenHelloServiceApi project as a dependency.
 Right-click the Dependencies node of MavenHelloServiceImpl in the Projects
window and choose Add Dependency.
 Click the Open Projects tab in the Add Library dialog.
 Select MavenHelloServiceApi OSGi Bundle. Click Add.


 Right-click in the HelloImpl.java class that is open in the editor and choose Fix
Imports (Alt-Shift- I; □-Shift-I on Mac) to add an import statement for
com.mycompany.mavenhelloserviceapi.Hello. Save your changes.
 Expand the com.mycompany.mavenhelloserviceimpl package and double-click Activator.java
to open the file in the editor.
  The IDE automatically created the Activator.java bundle activator class in your
project. A bundle activator is used to manage the lifecycle of a bundle. The bundle activator
class is declared in the MANIFEST.MF of the bundle and instantiated when the bundle is
started by the container.
 An OSGi bundle does not require a bundle activator class, but you can use the
start() method in the activator class, for example, to initialize services or other resources that
are required by the bundle. In this exercise you will add some lines of code to the class that
will print messages to the Output window. This will make it easier for you to identify when
the bundle starts and stops.
 Modify the start() and stop() methods in the bundle activator class to add the
following lines (in bold).
public class Activator implements BundleActivator {

public void start(BundleContext context) throws Exception {

System.out.println("HelloActivator::start");
context.registerService(Hello.class.getName(), new HelloImpl(), null);
System.out.println("HelloActivator::registration of Hello service
successful"); }

public void stop(BundleContext context) throws Exception {

context.ungetService(context.getServiceReference(Hello.class.getNam
e())); System.out.println("HelloActivator stopped"); } }

 You can see that the bundle activator class imports

org.osgi.framework.BundleActivator and org.osgi.framework.BundleContext. By default
 the generated class contains two methods: start() and stop(). The OSGi framework
invokes the start() and stop() methods to start and to stop the functionality provided
by the bundle. When the bundle is started, the service component provided by the
bundle is registered in the OSGi service registry. After a bundle is registered, other
bundles can use the registry to look up and then use the active services via the bundle
context.
 If you look at the POM for the project you can see the <Bundle-Activator>
element that specifies the bundle activator under the configuration element for the maven-
bundle-plugin.
<plugin><groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.3.7</version><extensions>true</extensions>
<configuration><instructions><Bundle-
Activator>com.mycompany.mavenhelloserviceimpl.Activator</Bu
ndle- Activator></instructions></configuration></plugin>
 When you build the bundle, the plugin will generate a Manifest Header in
the bundle's manifest file in the JAR and specify the Bundle Activator class. The OSGi
runtime looks for the Bundle-Activator header in the manifest file when a bundle is
deployed.
 Fix the import statements in Activator.java to import
com.mycompany.mavenhelloserviceapi.Hello. Save your changes.
 Expand the Dependencies node and confirm that the org.osgi.core artifact is listed as a
dependency.
 Note. Remove any older versions of the artifact that are listed under the Dependencies node
by right-clicking the artifact and choosing Remove Dependency. The only dependencies should be
the MavenHelloServiceApi project and the org.osgi.core artifact.
  Building and Deploying the OSGi Bundles
 In this exercise you will build the OSGi bundles and deploy the bundles to GlassFish.
 Right-click the MavenOSGiCDIProject node in the Projects window and choose Clean and
Build.
 When you build the project the IDE will create the JAR files in the target folder
of each of the projects and also install the snapshot JAR in the local repository. In the Files
window, you can expand the target folder for each of the two bundle projects to see the two
JAR archives (MavenHelloServiceApi-1.0-SNAPSHOT.jar and MavenHelloServiceImpl-1.0-
SNAPSHOT.jar).
 Start the GlassFish server if not already started.
 Copy the MavenHelloServiceApi-1.0-SNAPSHOT.jar to the
glassfish/domains/domain1/autodeploy/bundles/ directory of your GlassFish installation.
 You should see output similar to the following in the GlassFish Server log in the
Output window.
 INFO: Started bundle: file:/glassfish-
4.0/glassfish/domains/domain1/autodeploy/bundles/MavenHelloServiceAp
i-1.0- SNAPSHOT.jar
 Right-click the GlassFish server node in the Services window and choose View
Domain Server Log if the server log is not visible in the Output window.
 Repeat the steps to copy the MavenHelloServiceImpl-1.0-SNAPSHOT.jar to the
autodeploy/bundles directory.
 You should now see output similar to the following in the GlassFish server log.

 INFO: HelloActivator::start
 INFO: HelloActivator::registration of Hello service successful
 INFO: Started bundle: file:/glassfish-
4.0/glassfish/domains/domain1/autodeploy/bundles/MavenHelloServiceImp
l-1.0- SNAPSHOT.jar
 INFO: Started bundle: file:/glassfish-
4.0/glassfish/domains/domain1/autodeploy/bundles/MavenHelloServiceImp
l-1.0- SNAPSHOT.jar

Result
Thus the OGSA-compliant Web Service using Globus Toolkit is developed successfully.
EX.NO: Using Apache Axis develop a Grid Service

DATE

Aim:

To develop a web Service using Apache Axis Webserver

Algorithum:
Create a new project

start by creating a new Java Project called ProvisionDirService.SelectFile > New > Project...and select Java >
Java Project from the selection wizard. Click Next and enter ProvisionDirService in the Project Name textbox.
Accept the remaining project creation defaults by clicking Finish.

Make the project a Tomcat project

The first thing we need to do is to make this project a "Tomcat Project." Doing so enables Tomcat to run from
.class files inside our project as soon as they are compiled by Eclipse (which appens every time they are
saved). Hence, minor changes to the service logic will be reflected in the running service without having to
regenerate or redeploy any GARs. Open the project properties
page shown in Figure 8 (select Properties from the project's pop-up menu), select the Tomcat page, and check
the "Is a Tomcat Project" checkbox.

Add project source to Tomcat source path

Now we need to add the project's source to the Tomcat source path. The last step allows Tomcat to reload any
updates to the implementation. This step allows the live debugger to pull up the fresh source when debugging.
Go to Window > Preferences and select the Tomcat > Source Path page (shown in Figure 9). Select the
checkbox next to our ProvisionDirService project.

Add project source to Tomcat source path

Now we need to add the project's source to the Tomcat source path. The last step allows Tomcat to reload any
updates to the implementation. This step allows the live debugger to pull up the fresh source when debugging.

Go to
Window > Preferences
and select the
Tomcat > Source Path
Select the checkbox next to our
ProvisionDirService
project

Create the GT4 library

To create a user library from the GT4 library directory, use theUser
Libraries...
button. Click
New...
in the User Libraries dialog (see Figure 11) and create a
.

Result
Thus the Apache Axis webserver to develop a Grid Service using Globus Toolkit is
developedsuccessfully.