• Embed Doc
  • Copy Link
  • Readcast
  • Collections
  • CommentGo Back
Download
 
Mydhili K Nair et al /International Journal on Computer Science and Engineering Vol.1(3), 2009, 248-253248
Generic Web Services: A Step Towards GreenComputing
Mydhili K Nair
Dept.of Information Science & Engg.
 
M S Ramaiah Institute of Technology
Bangalore, Indiamydhili.nair@gmail.com Dr. V. GopalakrishnaIntegra Micro SystemsBangalore, Indiavgopi@integramicro.com
 Abstract
—Software as a Service (SaaS) is a buzzword especiallyin the realm of Cloud Computing. We can reduce the number of applications deployed on the data-centers by using similarapplications hosted by the SaaS providers. Thus,
“reusability” 
of a SaaS is a key-point of focus promoting the same code-base of anapplication serving multiple clients. This reduces the need formore storage space and computational power in the data-centersthus aligning the SaaS architecture to a
“greener” 
computingparadigm. In this paper, we provide a prototype implementationframework, which uses the
 same web service
to
 Register
and
 Report
the results of a backend Network Monitoring (NM) as wellas Weather Monitoring application. We have designed anddeveloped this
“Generic Web Services Framework” 
as well as boththe backend applications. The NM application is done using bothMobile Agents and SNMP and the WM application isimplemented using Temperature Sensors. This paper aims to givea prototype implementation as proof of SaaS maturity levels of ageneric / reusable web service thus orienting towards greencomputing.
 Keywords-Cloud Computing; Network Monitoring ; WebServices; Green Computing;
I.
 
I
NTRODUCTION
Software as a Service (SaaS)
is a model in which a serviceprovider offers an Internet hosted version of their applicationwith the hosting done either in house through a dedicatedserver or at hosting space managed by a third party. Thecustomers of the service vendor access this application overInternet and pays for its utilization on a per-use, per-product orsubscription-basis [7]. An example is a small handicraftbusiness in a remote village in India, which immediately has aglobal presence and immediate access to the global market by just listing its products on a well-known portal such as e-Bay!Thus,
SaaS
enabled by the amalgam of corporate intranetsand the Internet proves to have a great potential to impact oureveryday lives. The
most common implementation
of a
SaaS
 offered over the Internet is as
Web Services
where
‘Services’
 are an implementation of the functionality of a businessenterprise, which can be utilized by users of differentapplications. The logic of the service is
hidden
from theconsumers of the service. In simple terms, services are theend-points of a connection [8]
. ‘Web Services(WS)’
are the setof protocols by which these end connections are made byallowing the services to be
 published 
,
discovered 
and
used 
in atechnology neutral, standard form.The
 five
key benefits of 
Web Services Based 
 
SaaS
are [2]:
•
 
Save money
•
 
Save time
•
 
Focus on business needs of the software rather thanon deployment and maintenance infrastructure.
•
 
Gain immediate access to the latest innovations to thesoftware offered as a service.
•
 
Join a global community using the software as aservice thus gaining instant benchmarking data.Therefore, we leverage on the concept that SaaS is abusiness model, which is proven and will continue to have aglobal impact It is certainly not one of those transientdisruptive technologies that comes and goes is here to staythrough the coming years.Hence, in this paper, we focus on
 optimizing
 
SaaS
design,deployment and maintenance by using
generic / reusable
 
WebServices(WS),
thus aligning business architectures towards
energy efficient green computing
as well as adding a
 sixth key benefit
to
SaaS
described above, namely,
•
 
Save Energy
by reducing storage, computational andprocessing power at the servers where these “
 green”  services
are deployed.In this paper, we depict here the use of 
‘Generic’ WebServices
at the business enterprise, which are not tightlycoupled / tied down to any specific application. This enablesmultiple applications to
‘use’ / ‘consume’
these Web Services.We also present implementation results of usage of 
 two
such
Generic WS
by
 two
 
 completely different
backend monitoringlegacy applications, namely
 Network Monitoring and Weather (specifically Temperature) Monitoring
.The structure of the paper is as follows. Section 2 describesthe overall architecture of our Green Computing Framework.as well as highlights the design of the Generic Web Services.Section 3 presents the implementation results while Section 4focuses on the conclusion and scope of future enhancements toour
Generic Web Services Framework 
.
ISSN : 0975-3397
 
Mydhili K Nair et al /International Journal on Computer Science and Engineering Vol.1(3), 2009, 248-253249II.
 
O
VERALL
A
RCHITECTURE
 
.
 
WeatherMonitoringusing sensors(SunSpot)NetworkMonitoringBackendApplicationNetworkMonitoringDaemonTempMonitoringDaemonRegistrationWSClientTaskSchedulingWSClientReportingWSClientResultReportingWeb ServiceTaskSchedulingWeb ServiceRegistrationWeb ServiceGUI forNetworkMonitoringGUI forWeatherMonitoringAGENT tightly coupled withthe Monitoring BackendENTERPRISE hostingthe Web Services
 
Figure 1. Overall Deployment Diagram of Generic SaaS Framework
 The
generic / reusable web services green computing framework 
, we describe in this paper, consists of three parts:
a)
 
The Backend Monitoring Application
b)
 
Agent Daemon (tightly coupled with backend app)
c)
 
The Enterprise with the Web ServicesThe
shaded blocks
shown in Figure 1 are the reusable webservices for both the backend applications, namely:
•
 
Computer Network Monitoring(NM)
•
 
Weather Monitoring(WM)
 A.
 
 Backend Monitoring Applications
‘Network Monitoring’
 
(NM)
application was developed byus in-house[9]. It uses
SNMP
(
S
imple
 N 
etwork 
 M 
anagement 
 P
rotocol)
as well as
 Mobile Agents
to communicate betweenthe manager and its managed nodes. It adheres to theprinciples of Network Management, namely,
 FCAPS
(
 F
ault,
C 
onfiguration,
 A
ccounting,
 P
erformance, and 
S
ecurity
) and isa fully functional implementation.
 Mobile Agents
are smallpieces of software that migrate from host to host in a network.In our case, they carry instructions to from the manager nodeto interact with the
SNMP MIB
(
 M 
anagement 
 I 
nformation
 B
ase
) at the managed nodes.
‘Weather Monitoring’(WM)
application is an on-goingwork being developed by us for this research work. At thisstage, we have implemented the
Temperature Monitoring
 aspect of monitoring the weather, using
temperature
 
sensors
 called
Sun-Spots
given for academic research from SunMicrosystems. In this paper we show the implementationresults of testing it to communicate with the ReusableEnterprise Web Services. A
Sun-Spot 
kit consists of 
two free-range devices
and
one base-station
. The free-range devices arethose in which we can embed code to sense the temperature.We have used
 J2ME
(
 J 
ava
 2
 
 M 
obile
 E
dition
)
 API 
to embedtemperature
 Midlets
into the free range devices. Itcommunicates using
 Radiogram
 
 Protocol 
with the Base-Station device connected to a computer linked to the Internet.
 B.
 
Software Agent Daemon
Each of the aforementioned backend monitoringapplications has a
Software Agent
tightly coupled with itsimplementation. They act as a
glue[10]
communicating withthe Enterprise as well as the backend application. In our work we have two agents, both implemented as a
daemon processes
.
•
 
The Network Monitoring Agent[10]
•
 
The Temperature Monitoring Agent.
Java Beans
 
Interfaces with the backend NM and WM APIs
 
WorkingMemoyRule BasePatternMatcher
Rule 1
 
Rule 1
 
Rule 1Fact1
 
AgendaExecutionEngine
Drool Rule Engine
Interfaces withEnterprise toregister,and reportresults back toEnterprise.Thus, interfaceswith the
Generic 
Reusable
Registration 
and
Reporting 
Web Services
RegistrationManagerLicensingManagerConfigurationManagerEnterpriseCommunicator
(To get tasks if anyand report results)
Heart Beat Engine of the Agent
 
Figure 2. Architecture of the Agent of Generic SaaS Framework
 As shown in Figure 2, the general design of our SoftwareAgents has
 four 
parts, namely,
•
 
Registration Manager
•
 
Licensing Manager
•
 
Configuration Manager
•
 
Enterprise CommunicatorThe
 Registration Manager
and
 Licensing Manager
 invokes the
 Enterprise
 
Generic Registration and LicensingWS
, to register itself. with a Device ID which is
unique
to theentire enterprise database.The Algorithm described in Figure 3 below, clearlyindicates the steps taken by the Agent’s
 Registration
and
 Licensing Manager 
to ensure that only a valid Agent isallowed to access and utilize the Services offered by theEnterprise. Each Agent comes with a contract expiry datewithin which it can access the Enterprise
SaaS
. The validityof the Agent is determined by this date which also has a
grace period 
, within which the contract needs to be renewed of it hasexpired. These details are checked and maintained by the
Configuration Manager.
The
 Agent 
interacts with the
 Drools Rule Engine
if itsContract Expiry Date is expired, to check the Rule Base andfire the appropriate action. A
 Rule Engine
is made up of rules
ISSN : 0975-3397
 
Mydhili K Nair et al /International Journal on Computer Science and Engineering Vol.1(3), 2009, 248-253250
Figure 3. Algorithm for the Agent Registration and Licensing for SaaS
.which are discrete , as each of them applies to some subset of a potential problem, which needs to be solved.
Figure 4. ‘License.drl’, Sample Rule Base of Java Based Drools[10]
As depicted in Figure 2, the
 Drools Rule Engine
has a
Working Memory
of 
Facts
and a
 Rule Knowledge Base
of Rules.
Facts
are objects (Java Beans) from your applicationthat you insert into the working memory, which the ruleengine can access. A sample
‘
 License.drl’
Rule Base isdepicted in Figure 4. The interaction between the Agent andthe Rule Engine is through Java Beans. Therefore, in our case,the
 LicenseBean
is a
Fact 
. The
Facts
needs to be inserted intothe working memory of the Rule Engine,
before
any of therules are fired [10]. We use the
 JBoss Java based 
 Drools
Rule Engine Version 4.0.
We store the rules in a
.drl file
, a sampleof which is given in Figure 4.
C.
 
The Enterprise Web Serivces
The
 Enterprise
offers
 three Web Services
all of which is a
SaaS
. Out of this
two
of them are the
Generic Web Services
,which we focus in this paper. The Web Services are:
•
 
Registration and Licensing Web Service
•
 
Result Reporting Web Service
•
 
Task Scheduling Web Service
Daemon(here NM or WM)
 
:RegistrationService
:D
 
ataRetrieverFactory
 
: DataRetriever :LicenseManagement
GetContractStatus( )GenerateNewActivationCodeAddorUpdateAssets( )IsAuthentic( )GetAgentDataRetriever( )CheckAuthentication( )Is
AGENT
Present( )MySqlDataRetriever( )ContractStatusNewActivationCode
 
[isAgentPresent=false]<<destroy>>RegisterSystem<<create>>AgentNotFoundExceptionLicensing Exception[isAuthentic=false]alt Is Authentic
:RegistrationStatus
 
alt Agent Not PresentRegisterSystem( )<<create>>
 
Figure 5. Sequence Diagram of the Generic Registration andLicensing Web Serivce
The
 Enterprise Communicator
component of the
Software Agents
, depicted in Figure 2 above, have the client
packagecom.agent.license;importcom.agent.license.LicenseChecker;importcom.agent.license.LicenseAction;
rule
"Contract Expired"
whenlc:LicenseChecker(status==LicenseChecker.EXPIRED)la:LicenseAction()thenlc.setMessage("ContractPeriodExpired,nograceperiod,setnewlicense");//Calltherelevantactionfortherulela.licenseExpiry();lc.setStatus(LicenseChecker.GRACEPERIOD);/*NotifyingtheRuleEnginemodifiedFacts,sothatitcanbere-process*/update(lc);
endrule "License Grace Period"
whenlc:LicenseChecker(status==LicenseChecker.GRACEPERIOD)la:LicenseAction()thenlc.setMessage("ContractPeriodExpired,butwithingraceperiod");//Calltherelevantactionfortherulela.licenseGracePeriod();
end
 
Var
DevID:
Agent’sDeviceIDgivenbytheConfigurationManager.
ContractDate:
LicenseContractExpiryDate
Begin
#ChecksiftheAgentisvalid,registeredwithEnterprise.
If
DevID
ofAgent
= DevID
recordedatEnterprise#CheckiftheContracthasnotexpired
If
not
ContractDate
---Implementation----#AllowtheagenttousetheEnterprise#UpdateEnterprisewiththenewAssetdetailsifany#GeneratesnewactivationcodeandrecordsthesameattheEnterprisetopreventfraud
else
---ImplementationofRuleEngine.
Refer Figure 4.
---#
Controltransfers 
tothe
Drools Rule Engine.
Thisenginechecksifthelicenseiswithinthegraceperiodofthecontract.Ifso,itallowstheAgenttointeractwiththeEnterprise.Ifnot,theAgentisbroughtdown.#ChecksthevalidityoftheAgent
else if DevID
ofAgent
!= DevID
recordedatEnterprise
 #
BringtheAgentdown,notallowingittoaccessEnterprise.
End
ISSN : 0975-3397
of 00

Leave a Comment

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