A Study of Design and Implementation on SOA Governance: A Service
Oriented Monitoring and Alarming Perspective
Kuang-Yu Peng
Shao-Chen Lui
Ming-Tsung Chen
Chunghwa Telecom,Taipei, R.O.C.
{ rolandpeng, boboki, kanebo}@cht.com.tw
Abstract
Integrating enterprise IT infrastructure and
providing services to the public, SOA (Service
Oriented Architecture) has been become the main
stream in the field of IT domain. For example, Web
Services as well as JMS (Java Message Service) are
techniques commonly applied in SOA. In order to make
sure that all services on the SOA platform are stably
served, SOA Governance has become more important
in terms of applying SOA to enterprise. But for various
particular governance requirements, it is not an easy
task to perform the role of governance well.
This document will describe the basic concept of
SOA, maturity model, and explore the enterprise
solution of integrating applications and management
of SOA. Then introduce how the evolution of CHT
(Chunghwa Telecom) toward SOA Governance and the
major functions of a practical governance system
named SOBUS (Service Oriented Bus) which is
developed by SOA Governance Evolution Project in
CHT.
1. Introduction
NGOSS (New Generation Operations Systems and
Software) Project initiated recently by Chunghwa
Telecom has been claimed to fulfill standardized
guidelines by TeleManagement Forum. When applying
techniques in NGOSS TNA (Technology Neutral
Architecture), the architecture of NGOSS project
should be neutral and flexible. SOA is perfectly
satisfying such requirements. SaaS (Software as a
Service) is currently quite an appealing way to provide
application service. Customers are charged by the time
of usage under the SaaS-based application. With the
growing of SOA, the extremely flexible and agile
architecture makes such a sales way more feasible and
more attractive to customers. However, another
important issue was led up while the enterprise owning
the convenience of the services. Who should take
charge of the stability of services? SOA Governance is
the key to solve this issue. When SOA was led in the
enterprise, SOA Governance must be in progress as
well.
Until now, SOA Governance is not a well-defined
term of tasks. In general, “Governance” means how to
coordinate and how to cooperate heterogeneous
services under the specified rules. According to the
definition of IBM [6], Governance is the establishment
of :1) Chains of responsibility to empower people. 2)
Measurement to gauge effectiveness. 3) Policies to
guide the organization to meet its goals. 4) Control
mechanisms to ensure compliance. 5) Communication
to keep all required parties informed. On the other
hand, the key activities of SOA Governance mentioned
at WIKIPEDIA [1] are those : 1) Managing the
portfolio of services. 2) Managing the service lifecycle.
3) Using policies to restrict behavior. 4) Monitoring
performance of services.
The major subjects of SOA Governance are to
retain the high reliability of services status, record how
many services are available to serve on the platform
and make sure all of the services operating within an
acceptable service level. Based on those requirements
mentioned above, the SOA Governance Evolution
Project in CHT was established to tackle all the issues
and then SOBUS (Service Oriented Bus) was
developed to assist the governance tasks.
This article introduces the experience of how we
promote CHT toward SOA Governance and briefly
describes the major functions of SOBUS developed by
Telecommunication Laboratories, including the
monitoring of web services and message services and
data analysis of services performance.
2. The SOA maturity model
2008 IEEE International Symposium on Service-Oriented System Engineering
978-0-7695-3499-2/08 $25.00 © 2008 IEEE
DOI 10.1109/SOSE.2008.26
215
Authorized licensed use limited to: SOUTHWEST JIAOTONG UNIVERSITY. Downloaded on September 19, 2009 at 04:28 from IEEE Xplore. Restrictions apply.