Professional Documents
Culture Documents
The W3C Web Services Architecture Working Group defined a Web Services Architecture,
requiring a specific implementation of a "web service." In this a web service has an interface
described in a machine-processable format (specifically WSDL). Other systems interact with
the Web service in a manner prescribed by its description using SOAP (Simple Object Access
Protocol) messages, typically conveyed using HTTP with an XML serialization in
conjunction with other Web-related standards.
Many organizations use multiple software systems for management. Different software
systems often need to exchange data with each other, and a web service is a method of
communication that allows two software systems to exchange this data over the internet. The
software system that requests data is called a service requester, whereas the software system
that would process the request and provide the data is called a service provider.
Different software might be built using different programming languages, and hence there is
a need for a method of data exchange that doesn't depend upon a particular programming
language. Most types of software can, however, interpret XML tags. Thus, web services can
use XML files for data exchange.
Rules for communication between different systems need to be defined, such as:
1
remember, IP address of a website. This allows the website visitors to find and return to a
web page more easily. It also allows advertisers the ability to give a website a memorable
name that visitors will remember and come to, hopefully leading to conversions for the web
page. The domain is the human readable address for a web site. Owning a domain name
involves registering the name you want with an organization called ICANN through a domain
name registrar like XnYnZ.com . For example, if you choose a name like "example.com",
you will have to go to a registrar, pay a registration fee for that name.
An often-used analogy to explain the Domain Name System is that it serves as the phone
book for the Internet by translating human-friendly computer hostnames into IP addresses.
For example, the domain name www.example.com translates to the addresses 93.184.216.119
(IPv4) and 2606:2800:220:6d:26bf:1447:1097:aa7 (IPv6). Unlike a phone book, the DNS can
be quickly updated, allowing a service's location on the network to change without affecting
the end users, who continue to use the same host name. Users take advantage of this when
they use meaningful Uniform Resource Locators (URLs), and e-mail addresses without
having to know how the computer actually locates the services.
The Domain Name System distributes the responsibility of assigning domain names and
mapping those names to IP addresses by designating authoritative name servers for each
domain. Authoritative name servers are assigned to be responsible for their supported
domains, and may delegate authority over subdomains to other name servers. This
mechanism provides distributed and fault tolerant service and was designed to avoid the need
for a single central database.
1.4 IP ADDERSSING
2
IP (INTERNER PROTOCOL) is a 32 bit computer address. It is numerical identification of
computer on network. It is divided in 4 octet each octet contain 8 bit. It has two parts one is
network id and second is host id. We use private IP address in LAN which is reserved by
IANA (INTERNET ASSIGNING NUMBRING AUTHOURTIY) for free of cost usage. The
minimum value (per octet) is 0 and the maximum value is 255. IP address is divided in five
classes:
Table 1: IP Classes
1.5 IP Routing
IP Routing is an umbrella term for the set of protocols that determine the path that data
follows in order to travel across multiple networks from its source to its destination. Data is
routed from its source to its destination through a series of routers, and across multiple
networks. The IP Routing protocols enable routers to build up a forwarding table that
correlates final destinations with next hop addresses.
When an IP packet is to be forwarded, a router uses its forwarding table to determine the next
hop for the packet's destination (based on the destination IP address in the IP packet header),
3
and forwards the packet appropriately. The next router then repeats this process using its own
forwarding table, and so on until the packet reaches its destination. At each stage, the IP
address in the packet header is sufficient information to determine the next hop; no additional
protocol headers are required.
1.6 VLAN
A VLAN (virtual LAN) is a group of end stations with a common set of requirements,
independent of physical location. VLANs have the same attributes as a physical LAN but
allow you to group end stations even if they are not located physically on the same LAN
segment.
VLANs are usually associated with IP subnetworks. For example, all the end stations in a
particular IP subnet belong to the same VLAN. Traffic between VLANs must be routed. LAN
port VLAN membership is assigned manually on an port-by-port basis.
4
1. GOALS OF THE PROJECT
This project will focus on developing services with a client point of view, bringing together
governance, content managers, end users, and service providers to clearly define the service
offerings that support our web presence.
Defining web services in a way that is meaningful to the customer and aligns service
providers to delivery and support
Improving the experience of end-users in accessing campus web services and
obtaining support for incidents and requests
Establishing a web service team to plan and support the lifecycle of web services,
create effective processes, and set expectations for customers and web service
providers
Defining roles and responsibilities across the spectrum of web services
Reliability: The most common thing done with a domain is looking it up. Often this is
automatic, and users are not even aware of it. It happens many billions of times a day.
People want name look ups to be fast and reliable.
Permanence: When people get a domain, they would like it to last forever, or at least
until they say otherwise. Of course, all dispute resolution systems which can take a
domain away are at odds with this goal.
Uniqueness: People want a domain to point precisely at one thing. If I give you my
business card with an E-mail address on it, you and I both want that address to mail to
me, and me alone. You might consider this a subset of reliability.
Cheap and for everybody: People would like the domain name system to be cost-
effective, with minimal cost to both the holders and users of domains, financially and
technically.
No Control: A counter to that goal is that people don't want outside forces running the
system against their wishes. They don't want any one powerful party (that isn't them)
to have too much say or control, with the ability to take away their name unfairly or to
enforce rules they don't desire.
5
2. METHODOLOGY
Virtualization, in computing, refers to the act of creating a virtual (rather than actual)
version of something, including but not limited to a virtual computer hardware platform,
operating system (OS), storage device, or computer network resources.
In hardware virtualization, the host machine is the actual machine on which the virtualization
takes place, and the guest machine is the virtual machine. The words host and guest are used
to distinguish the software that runs on the physical machine from the software that runs on
the virtual machine. The software or firmware that creates a virtual machine on the host
hardware is called a hypervisor or Virtual Machine Manager.
In our project we choose virtualization as our methodology because implementing the actual
project will be too costly (several thousands of dollars) physically. So to test that if our
project is feasible and according to the requirements we will virtualize various hardware
devices and operating systems, this will help us to reduce the cost required to remove various
problems we may face after actual/physical implementation of the project.
6
3.1 Implementation of Project (Overview)
Head Office
VMware
Router 1
(Head Office)
ISP/VLAN
Branch Office
(Similar to Head Office)
ISP
Client 1, … …, Client n
7
3. HARDWARE & SOFTWARE REQUIREMENTS