Session 3C: SaaS for Telecommunication
Telecommunication Laboratories Chunghwa Telecom Co.,Ltd.
0..n
0..n
A Study of Design and Implementation on SOA Governance: A Service Oriented Monitoring and Alarming Perspective
0..n
Kuang-Yu Peng Shao-Chen Lui Ming-Tsung Chen December 19, 2008
Outline Introduction. The challenge we faced. The efforts we made: a practical implementation. The effects after our efforts. Conclusion and future work.
22/24 /24
Introduction Why? Change is Constant; both on business and technology. Need a whole new integrated platform in Chunghwa Telecom.
How? New Generation Operations Systems and Software (NGOSS) Service-Oriented Architecture
What? SOA maturity model SOA Governance SOBUS – a management system for governance. A practical system on performing basic SOA Governance in CHT.
33/24 /24
Outline Introduction.
The challenge we faced. The efforts we made. The effects after our efforts. Conclusion and future work.
44/24 /24
The challenge we faced(1/2) Hundreds of OSS/BSS Duplicated Out of date Inflexible
SOA is the best solution, but not easy to implement within enterprise-wide. Web Services, WSDL, UDDI, JMS … Cost, Budget, Time, Human hours …
55/24 /24
The challenge we faced(2/2) How to manage? SOA Governance is not well-defined.
Looking for a suitable SOA management solution. Cost Functionality fit Customize Issue tracking
66/24 /24
Outline Introduction. The challenge we faced.
The efforts we made. The effects after our efforts. Conclusion and future work.
77/24 /24
The efforts we made.(1/11) SOA Maturity Model
Used to evaluate the current state of SOA adoption. A good path toward SOA for the enterprise to follow. Hayward, S. "Positions 2005: Service-Oriented Architecture Adds Flexibility to Business Processes," Gartner, Inc. Feb. 2005.
88/24 /24
The efforts we made.(2/11) Key activities of SOA Governance
Managing the service lifecycle. Monitoring performance of services. Managing the portfolio of services. Using policies to restrict behavior.
99/24 /24
The efforts we made.(3/11) Service Lifecycle Requirements management software
Advantages Asset visibility Services reuse Health monitor Development control
10 /24 10/24
The efforts we made.(4/11) Architecture of the practical governance system (SOBUS) platform monitoring subsystem
system managing subsystem DB Web service monitoring
Report module
Messaging Service monitoring
query notification user
Warning notification Proxy
Service ServiceProxy Proxy
SOA platform
Messaging Service link Backend Web service
client
11 /24 11/24
The efforts we made.(5/11) SOA platform(1)
ESB (Enterprise Service BUS) Support for Web services Workflow management Routing and transforming
12 /24 12/24
The efforts we made.(6/11) SOA platform(2)
EMS (Enterprise Messaging Service) JMS compliant communications Two types of communication models Queue Topic
13 /24 13/24
The efforts we made.(7/11) Platform monitoring
Platform stability Connection response time EMS Server loading CPU Memory File System
14 /24 14/24
The efforts we made.(8/11) Service Monitoring(1)
Web Service monitoring Ping test periodically WSDL test periodically Real-time services status Access time measuring
15 /24 15/24
The efforts we made.(9/11) Service Monitoring(2)
Built-in monitoring and management capabilities EMS monitoring Server health Destinations real-time information Connection resource Client side api-library version
16 /24 16/24
The efforts we made.(10/11) Warning notification
Alarm Email alarm SMS alarm
17 /24 17/24
The efforts we made.(11/11) Services measuring
Leading to continuous business process improvement KPI of services Response time Access frequency
18 /24 18/24
Outline Introduction. The challenge we faced. The efforts we made.
The effects after our efforts. Conclusion and future work.
19 /24 19/24
The effects after our efforts.(1/2) More message transactions
Since Oct. 2007~ Sep. 2008
20 /24 20/24
The effects after our efforts.(2/2) More web service access
More than 2 million average access per month
21 /24 21/24
Outline Introduction. The challenge we faced. The efforts we made. The effects after our efforts.
Conclusion and future work.
22 /24 22/24
Conclusion Future works Service Registry UDDI Version control
Business Process Management (BPM) More reliable and stable Upgrade maturity levels
23 /24 23/24
Q&A
THANKS FOR YOUR LISTENING
24 /24 24/24