e-GOVERNANCE
for
ENHANCE SERVICE DELIVERY
TRANSFER KNOWLEDGE, DEVELOP AND IMPLEMENT QUICK WIN PILOT E-SERVICES
(SERVICE ORIENTED ARCHITECTURE (SOA) -BASED BUSINESS PROCESS MANAGEMENT (BPM))
June 2nd to 21st 2012
AMMAN- JORDAN
DAY 1
PRESENT BY:
Agenda
Time
9:00
Topic
Opening & Agenda
9:30
E-Government Enterprise Architecture Reference Model
10:00
11:00
11:30
12:20
1:10
1:30
2:30
4:00
4:15
5:15
E-Government Architecture Framework
Coffee Break
E-Government Technical Architecture
Service Oriented Architecture
SOA Governance & Maturity Model
Lunch Break
Oracle SOA Suite (1)
Coffee Break
Oracle SOA Suite (2)
Q&A + Discussion
E-Government Enterprise Architecture
Reference Model
‫معمارية المؤسسات للحكومة اإللكترونية‬
‫النموذج المرجعي‬
Introduction
The purpose of the reference architecture model is to
provide the government agencies with adequate reference
material in order to:
– Support government agencies that want to develop
their enterprise architecture
– Provide the entities with guidelines that allow them
to hook up with the central architecture
‫– دعم الجهات الحكومية التي ترغب في تطوير البنية المعمارية ألعمالها‬
‫– تزويد الجهات الحكومية بمبادئ توجيهية لربطها مع معمارية الحكومة‬
‫اإللكترونية المركزية‬
‫المزايا ‪Advantages‬‬
‫‪‬‬
‫‪‬‬
‫‪‬‬
‫‪‬‬
‫‪Align IT infrastructure and process with enterprise strategy and goals‬‬
‫‪Supplement the existing e-government strategy and project management‬‬
‫‪‬‬
‫‪‬‬
‫‪methodology with EA Standards & Guidelines‬‬
‫‪EA sets the standards for informed technical management decisions‬‬
‫‪EA Promotes "interoperability" among entities‬‬
‫‪‬‬
‫‪‬‬
‫مواءمة البنية التحتية التقنية وعمليات األعمال مع إستراتيجية المؤسسة وأهدافها‬
‫تكملة إستراتيجية الحكومة اإللكترونية القائمة ومنهجية إدارة المشاريع مع معايير ومبادئ هيكلية المؤسسة‬
‫هيكلية المؤسسة تضع معايير تساعد اإلدارة الفنية على اتخاذ قرارات مستنيرة‬
‫هيكلية المؤسسة تشجع على ”التخاطب البيني“ بين الكيانات الحكومية‬
Components ‫المكونات‬
•
Business Architecture: Identify business
processes and supporting organizational structure.
Help in achieving the business model
•
Application Architecture : the architecture of
applications that support the business processes
•
Technology Architecture : addressing the
infrastructure that supports the applications
•
Data Architecture : addressing the information
that supports the applications
Enterprise Architecture (EA) Framework
• EA Framework is a tool for systematically documenting the
enterprise architecture.
• EA framework provide the tools and artifacts needed for
documenting the architecture.
• It also has a Technical Reference Model or TRM, that can be
referred to for creating the architecture.
• Based on TOGAF or ZACHMAN. TOGAF is more popular
• TOGAF: The Open Group Architecture Framework
E-Gov Challenges
• Need to transform e-government strategy and vision
into concrete business and IT solutions.
• Interoperability Issues among entities.
• Lack of reuse of functionality (Re-inventing the
wheel).
• Lack of e-service maturity at some entities.
• Limited funding for e-government related activities at
entities.
• Limited technical skill sets at entities.
• Duplicate data ownership.
Technical Architecture
Entity Reference
Model
Infrastructure
Governmental Entities
Integration
Entity Architecture
Delivery
E-Services
Applications
Middle ware
Software
Access
Infrastructure
E-Government
E-Services
Integration
Middle ware
Access
Applications
Software
Governance
Software
Governance
Applications
Interoperability
Framework
Delivery
E-Services
Central Architecture
Governance
Entity Architecture
Interoperability
Framework
Entity Reference
Model
Infrastructure
Governmental Entities
Components ‫المكونات‬
•
Central Architecture & Building Blocks – Architecture for
“common services” such as “Payment Gateway” provided by egovernment program that all entities can use.
•
Entity Reference Architecture – Provide a process that entities
can adopt to integrate with central building blocks. Additionally It
provides direction for entities to create there own information
technology architecture using the “FEAF” Framework.
•
Interoperability Framework – This framework provide technical
standards to streamline interoperability. It provides data standards to
create unique standardized XML data dictionaries for common data
elements across all entities. This will help in removing any confusion
regarding the data ownership, type, relationship or structure.
•
Governance – The frameworks and architectures described above
are subject to the EGAF Governance process, that will ensure that
the EGAF remain relevant over time.
e-Government
Architecture Framework
‫إطار الهيكلة‬
‫الحكومة االلكترونية‬
Framework Overview
Business
Perspective
Application
Perspective
Information
Perspective
Technology
Perspective
Conceptual
Level
Business
model
Service
catalogue
Information
model
Technology
platform
Logical
Level
Process
model
Application
architecture
model
Logical data
model
Technical
architecture
model
Operational
Level
Workflow
model
Application
design
model
Physical data
model
Infrastructure
model
Business Model
Description
The business model describes
the core and support activities an
organization performs.
Purpose
The business model supports
process and service orientation
of eGovernment activities
Example model
Process Model
Description
The process model describes
processes within and between
organisations.
Purpose
The process model supports processand service orientation, as well as
business process improvement and
re-engineering
Example model
Workflow Model
Description
The workflow model describes process
and workflow on a detailed level.
Purpose
The workflow model supports
implementation of defined processes
using selected technology.
Example model
Service Catalogue
Description
The service catalogue provides a highlevel overview of business services
and e-services.
Purpose
The service catalogue makes services
visible and/or available to internal and
external users.
Example model
Application Architecture
Description
The application architecture describes
application components that supports
business services and e-services.
Validate against
Purpose
The application architecture provides
a vehicle to connect and integrate
services and technology
Example model
Application Design
Description
The application design describes
implementation of applications.
Validate against
Purpose
The application design supports
implementation of specific applications
and/or application integration.
Example model
Information Model
Description
The information model describes the
core concepts related to a specific
area or organisational unit.
Purpose
The information model provides a
shared vocabulary for a specific
area or organisational unit.
Example model
Logical Model
Description
The logical data model provides a
description of information elements
and their relations
Purpose
The logical data model provides a
vehicle for creating a shared definition
of a specified area or organisational
unit.
Example model
Physical Data Model
Description
The physical data model provides a
detailed and technology-specific
definition of data elements and their
relations.
Purpose
The physical data model supports
implementation of the data model,
using a specific technology
Example model
Technology Platform Model
Description
The technology platform model
gives a high-level view of the
technology platform, including all
platform components.
Purpose
The technology platform model
provide the organisation with a highlevel understanding of the technology
platform.
Example model
Technology Architecture Model
Description
The technical architecture model
describes the components and
interactions between the components
in the technology platform.
Purpose
The technical architecture models
provide a detailed view of a certain
area or organisational unit.
Example model
Infrastructure Model
Description
The infrastructure model details the
technical components of the solution.
Purpose
The infrastucture model provides
documentation as well as blueprints
for ICT systems.
Example model
‫أساسيات البيانات الموحدة‬
‫‪Master Data Essentials‬‬
‫األشخاص‬
‫شهادة الجنسية‬
‫البطاقة الشخصية‬
‫البطاقة التموينية‬
‫بطاقة السكن‬
‫المؤسسات‬
‫الحكومة‬
‫اإللكترونية‬
‫العناوين‬
‫‪GIS‬‬
‫الرقم الوطني الموحد‬
‫المركبات‬
‫العقارات‬
‫‪E-Government‬‬
‫‪Technical Architecture‬‬
‫المعمارية التقنية‬
‫للحكومة اإللكترونية‬
Overview
‫نظرة عامة‬
• Customer/citizen Centric ‫تتمحور حول المواطن‬
• All services centered around customer
needs. ‫جميع الخدمات تتمحور حول تلبية احتياجات‬
‫العمالء‬
• Stakeholders ‫األطراف‬:
–
–
–
–
E-Government ‫الحكومة اإللكترونية‬
Governmental Entities ‫الجهات الحكومية‬
Businesses ‫قطاع األعمال‬
Customers / Citizens ‫المواطنون‬
• Multiple Access & Delivery Channels:
:‫قنوات إيصال و تواصل متعددة‬
–
–
–
–
–
Traditional ‫التقليدية‬
Web ‫الويب‬
Call Center ‫مركز خدمات على الهاتف‬
Mobile ‫الجوال‬
SMS ‫رسائل الجوال‬
Architecture
‫المعمارية‬
• Central Enterprise Service Bus – ESB
• Provides:
– Transformation
– Mapping
– Rounting
• Provides Central Services such as
Identity Management, Payment
Gateway
• Orchestrates Business Processes
• Acts a central mediator for:
– Customer / Government Interactions
– Business / Government Interactions
– Government / Government Interactions
High Level Integration Architecture
‫معمارية الترابط‬
Integration & Canonical Data Model
‫الترابط و نموذج البيانات القياسي‬
Gov Entity 1
Gov Entity 5
Gov Entity 4
Gov Entity 2
Gov Entity 3
Integration & Canonical Data Model
‫الترابط و نموذج البيانات القياسي‬
Gov Entity 1
Adapter
Canonical
Message
Gov Entity 2
Gov Entity 3
Adapter
Adapter
Canonical
Message
Gov Entity 4
Adapter
Canonical
Message
Enterprise Service Bus
Business Process Engine
Shared Services
Gov Entity 5
Adapter
Canonical
Message
Canonical
Message
E-Service Categories
‫فئات الخدمات‬
• Vertical Services (‫)خدمات عامودية‬:
Self-Contained end to end service provided by a governmental entity
• Cross Organization Services (‫)خدمات عابرة للجهات الحكومية‬:
A service which requires the involvement of several government entities in order to
be delivered.
• Composite Services (‫)خدمات مركبة‬:
A service which flows across multiple government entities. Process across multiple
entities.
• Shared Services (‫)خدمات مشتركة‬:
shared services are defined as the ‘’enablers’’, providing technology-based
functionality that are central to the provision of vertical and cross-organizational
services such as: SMS Gateway, Authentication, Payment Gateway, etc.
E-Gov Portal & Delivery Channels
‫بوابة الحكومة االلكترونية و قنوات اإليصال‬
Kiosk
PC
Home
Mobile
Access
Other
Access
Access
Layer
PC
Business
Internet
Data
Conversion
Authentication
Audit &
Management
Messaging
Transaction
Engine
Payment
Services
Secure Government Network
Department A
Department X
Gateway/Portal Layer
Portal and Content Management
SOA
Service Oriented Architecture
‫الموجهة‬
‫معمارية الخدمات‬
َّ
Service Oriented Architecture – ‫معمارية الخدمات الموجَّ هة‬
Service-Oriented Architecture (SOA) is a set of principles
and methodologies for designing and developing software
in the form of interoperable services. These services are
well-defined business functionalities that are built as
software components that can be reused for different
purposes.
‫) هي مجموعة من مبادئ تصميم األنظمة‬SOA( ‫معمارية الخدمات الموجَّ هة‬
‫ يقدم النظام‬.‫تستخدم في مجال الحوسبة أثناء مراحل تطوير األنظمة واندماجها‬
‫الذي يستخدم هذه البنية وظائفه على هيئة حزمة من الخدمات المتعاونة التي يمكن‬
.‫استخدامها من قبل أنظمة مختلفة من مجاالت تجارية متعددة‬
What is a Service
A Service is generally defined as:
A functionality provided as a modular piece of software,
with a well defined interface contract. Service can be
accessed by a service consumer by invoking the service
interface.
‫ يتم‬.‫وظيفة مقدمة من خالل وحدات برمجية ذات عقد واجهة ربط واضح المعالم‬
.‫التواصل مع الخدمة من قبل المستهلكين من خالل استدعاء واجهة ربط الخدمة‬
Service Attributes – ‫سمات الخدمة‬
• A service must have a well defined interface.
• A service is “loosely coupled”, in that sense changes made to the
implementation of the service require no changes from the consumer.
• A service is modular and independent from other services.
• A service is a reusable unit.
‫الخدمة تحتوي على عقد واجهة ربط واضح المعالم‬
‫ بمعنى أنه أي تغييرات في تطبيق الخدمة ال يتطلب تغييرات‬،‫الخدمة تقترن مع مثيالتها بشكل متباعد‬
.‫من المستهلك بفضل عقد الترابط‬
‫الخدمة هي وحدة مستقلة عن غيرها من الخدمات‬
‫الخدمة هي وحدة قابلة إلعادة االستخدام‬
•
•
•
•
Service Interface / Contract
BLACK BOX
‫ عقد الخدمة‬/ ‫واجهة‬
SERVICE INTERFACE
BACKEND APPLICATIONS
SERVICE A
SERVICE
CONSUMER
Mainframes
SERVICE PRODUCER
BACKEND APPLICATIONS
SERVICE B
LOOSE COUPLING
SERVICE
CONSUMER
Mainframes
SERVICE PRODUCER
INDEPENDENT
REUSABLE
Service Interface / Contract
‫ عقد الخدمة‬/ ‫واجهة‬
A service interface is a contract that establishes the identity of
the service and the rules of the service invocation. Listed
below are details typically presented in a service interface.
–
–
–
–
Request Data Message
Response Data Message
Exception Conditions
Metadata to identify the function and purpose of the service
‫ تحتوي واجهة الخدمة‬.‫واجهة الخدمة هو العقد الذي يحدد هوية وقواعد طلب الخدمة‬
:‫على‬
‫بيانات رسالة الطلب‬
‫بيانات رسالة االستجابة‬
‫شروط االستثناءات‬
‫معلومات عن وظائف الخدمة والغرض منها‬
–
–
–
–
Advantages of SOA ‫مزايا معمارية الخدمات‬
‫الموجَّ هة‬
•
•
•
•
Adapt applications to changing technologies.
Easily integrate applications with other systems.
Leverage existing investments in legacy applications.
Quickly and easily create a business process from existing services.
‫تكييف التطبيقات مع التكنولوجيات المتغيرة‬
‫تسهل التكامل مع األنظمة األخرى‬
‫يتيح إمكانية التخاطب البيني للتطبيقات القديمة بدون تكاليف إضافية‬
‫خلق عمليات أعمال بسرعة و بسهولة من الخدمات المتاحة‬
•
•
•
•
•
SOA Principles
•
•
•
•
•
‫مبادئ معمارية الخدمات الموجَّ هة‬
Software that enables the services must be modular.
The software modules must be distributable.
Software developers must write or generate interface metadata that specifies
an explicit contract so that another developer can find and use the service (this
helps enable loose coupling).
The service interface must be separate from the implementation (code and
data) of the service provider module .
Service providers must be shareable — that is, designed and deployed in a
manner that allows them to be invoked successively by disparate consumers.
‫يجب أن تكون البرمجيات مبنية بشكل وحدات‬
‫يجب أن تكون البرمجيات قابلة للتوزيع على عدة خوادم‬
‫يجب على مطوري البرمجيات كتابة أو توليد بيانات واجهة الخدمة لتحديد عقد واضح بحيث يمكن العثور عليه‬
.)‫من قبل مطور آخر واستخدام الخدمة (وهذا يساعد على تمكين اقتران فضفاض‬
.‫يجب أن تكون واجهة الخدمة منفصلة عن البرمجية المنفذة لمزود الخدمة‬
‫ أي أن تصمم وتنشر على نحو يسمح للمستهلكين طلب الخدمة على التوالي في‬.‫يجب أن تكون الخدمات تشاركية‬
.‫آن واحد‬
•
•
•
•
•
‫‪SOA Governance & Maturity Model‬‬
‫الموجهة و نموذج النضج‬
‫حوكمة معمارية الخدمات‬
‫َّ‬
SOA Governance ‫حوكمة معمارية الخدمات الموجَّ هة‬
Specifying the decision rights and accountability framework to encourage
desirable behavior in the use of IT.
SOA Maturity Model ‫نموذج النضج‬
Oracle SOA Suite
Oracle SOA Suite
Oracle SOA Suite Components














JDeveloper
Oracle Service Bus
Oracle Mediator
Oracle Adapters
Metadata Service Repository
Oracle Policy Manager
Oracle Business Rules
Oracle BPEL
Human Workflow
Oracle Business Activity Monitoring – BAM
Oracle Complex Event Processing
Oracle User Messaging Service
Oracle B2B
Oracle Enterprise Manager
JDeveloper

Integrated Development
Environment – IDE

Uniform Integrated set of
Tools for:




Developers,
Architects,
Business Analysts
Others

Visual Interaction

Declarative Tools

Minimize Coding

Rapid Deployment
Oracle ESB: An ESB Moves Data
Oracle ESB: Facilitates Service Invocation
Oracle ESB: Component Architecture
Components





Integrated Designer
Rich Monitor Console
JCA Adapters
Routing Services
Meta Data Repository
Features





Content Based Routing
Enterprise Messaging
Native XML & WebServices
Multi Transport Fabric
SCA & SDO
Usage Patterns





Point to Point
Canonical Model
Store & Forward
Request/Response
External Services
Oracle Mediator

Route:
Determines the service
component to which to
send the messages.

Validate:
Provides support for
validating the incoming
messages

Filter:
filters part of a payload
message to extract
specific information

Transformation:
transforms document
data from one XML
schema to another
Oracle Adapters



Open Standards
Rapid Development
Standard Adapters:


SOA & JCA Adapters
ERP Adapters: EBS, Siebel, SAP, etc
Metadata Service Repository
•
•
•
•
•
•
Business Events
Rulesets for use by Oracle Business Rules
XSLT files for Oracle Service Bus and Oracle Mediator
XSD XML schema files for Oracle BPEL Process Manager
WSDL files
Metadata files for Complex Event Processing.
Oracle Policy Manager

Global security and Auditing
Policies

Standard Mechanism for
Signing Messages

Encryption

Authentication

Role-Based Access Control

Collects Monitoring Statistics
Oracle Business Rules

Agile rule maintenance
by business analysts
not programmer

Enable dynamic
decisions at runtime

separating rule logic
from underlying
application code

Automate:




Policies
Constraints
Computations
Reasoning
Oracle BPEL Process Manager

Assembling discrete
services into end-to-end
process flows

Radically reducing the
cost and complexity of
process integration

Orchestrate synchronous
and asynchronous
services

Declarative Process
Definition

Isolate Process from
involved parties (partner
links)
Human Workflow





Human interactions with processes, including assignment and routing of tasks to
the correct users or groups.
Deadlines, escalations, notifications, and other features required for ensuring the
timely performance of a task (human task activity).
Presentation of tasks to end users through a variety of mechanisms such as work
lists.
Organization, filtering, prioritization, and other features required for end users to
productively perform their tasks.
Reports, reassignments, load balancing, and other features required by
supervisors and business owners to manage the performance of tasks.
Oracle Business Activity Monitoring - BAM

Monitor Business
Processes and Services
in real-time

Analyze events as they
occur by correlating
events, identifying trends
as they emerge, and
alerting users to
bottlenecks, exceptions,
and solutions to business
problems

Act on current conditions
with event-driven alerts,
real-time dashboards,
BPEL processes, and
Web services integration,
enabling quick changes or
corrective action to
business processes
Oracle Complex Event Processing

An Advance SOA
Feature

Works on Data Streams
such as sensors, stock
ticker, etc.

Context Creation

Filtering

Correlation and
Aggregation

Pattern Matching

Complex Event Sinks
Oracle User Messaging Service
• Provides services to sending out messages from applications to
devices
• Routes incoming messages from devices to applications.
• Supports: Email, IM, SMS, Text, Voice, etc.
Oracle B2B





Document Management: Provides multiple document standards, such as definitions, validation,
translation, identification, correlation, batching, routing, code lists, and envelope generation.
Trading Partner Management: Provides capabilities to manage trading partner profiles and
agreements.
Profiles: Provides trading partners details, such as identifications, contacts, users, delivery
channels, supported documents, and security.
Agreements: Enables agreement between trading partners for a specific interaction.
System Management: Provides features to monitor and manage the environment.
Oracle Enterprise Manager



Configure, monitor, and manage your SOA composite application during run time from
Oracle Enterprise Manager FMW Control Console.
The SOA Infrastructure provides you with access to all deployed SOA composite
applications, service engines, service components, business events, and other
elements.
Provides a wide variety of administrative and performance data for the SOA
components, composite applications, and composite instances within the SOA
infrastructure
Thank You!