e-GOVERNANCEe-GOVERNANCEfor

ENHANCE SERVICE DELIVERYTRANSFER KNOWLEDGE, DEVELOP AND IMPLEMENT QUICK WIN PILOT

E-SERVICES (SERVICE ORIENTED ARCHITECTURE (SOA) -BASED BUSINESS PROCESS MANAGEMENT

(BPM))

 June 2nd to 21st 2012AMMAN- JORDAN

DAY 1

PRESENT BY:

Agenda

Time Topic9:00 Opening & Agenda

9:30 E-Government Enterprise Architecture Reference Model

10:00 E-Government Architecture Framework11:00 Coffee Break11:30 E-Government Technical Architecture12:20 Service Oriented Architecture1:10 SOA Governance & Maturity Model1:30 Lunch Break2:30 Oracle SOA Suite (1)4:00 Coffee Break4:15 Oracle SOA Suite (2)5:15 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

Infrastructure

Software

Applications

E-Services

Governance

Infrastructure

Software

Applications

E-Services

Governance

Entity ArchitectureEntity Architecture Central Architecture

Delivery

Integration

Middle ware

Access

Delivery

Infrastructure

Software

Applications

E-Services

Governance

Entity ArchitectureEntity Architecture

Integration

Middle ware

Access

Inte

rop

erab

ility

Inte

rop

erab

ility

Fra

mew

ork

Fra

mew

ork

Inte

rop

erab

ility

Inte

rop

erab

ility

Fra

mew

ork

Fra

mew

ork

Entity Reference Model

Entity Reference Model

E-GovernmentGovernmental EntitiesGovernmental Entities Governmental EntitiesGovernmental Entities

Componentsالمكونات

• Central Architecture & Building Blocks – Architecture for “common services” such as “Payment Gateway” provided by e-government 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

Conceptual Level

Logical Level

Operational Level

Business Model

The business model describes

the core and support activities an

organization performs.

Description

The business model supports

process and service orientation

of eGovernment activities

Purpose

Example model

Process Model

The process model describes

processes within and between

organisations.

Description

The process model supports process-

and service orientation, as well as

business process improvement and

re-engineering

Purpose

Example model

Workflow Model

The workflow model describes process

and workflow on a detailed level.

Description

The workflow model supports

implementation of defined processes

using selected technology.

Purpose

Example model

Service Catalogue

The service catalogue provides a high-

level overview of business services

and e-services.

Description

The service catalogue makes services

visible and/or available to internal and

external users.

Purpose

Example model

Application Architecture

The application architecture describes

application components that supports

business services and e-services.

Validate against

Description

The application architecture provides

a vehicle to connect and integrate

services and technology

Purpose

Example model

Application Design

The application design describes

implementation of applications.

Validate against

Description

The application design supports

implementation of specific applications

and/or application integration.

Purpose

Example model

Information Model

The information model describes the

core concepts related to a specific

area or organisational unit.

Description

The information model provides a

shared vocabulary for a specific

area or organisational unit.

Purpose

Example model

Logical Model

The logical data model provides a

description of information elements

and their relations

Description

The logical data model provides a

vehicle for creating a shared definition

of a specified area or organisational

unit.

Purpose

Example model

Physical Data Model

The physical data model provides a detailed and technology-specificdefinition of data elements and their relations.

Description

The physical data model supportsimplementation of the data model, using a specific technology

Purpose

Example model

Technology Platform Model

The technology platform model

gives a high-level view of the

technology platform, including all

platform components.

Description

The technology platform model

provide the organisation with a high-

level understanding of the technology

platform.

Purpose

Example model

Technology Architecture Model

The technical architecture model

describes the components and

interactions between the components

in the technology platform.

Description

The technical architecture models

provide a detailed view of a certain

area or organisational unit.

Purpose

Example model

Infrastructure Model

The infrastructure model details thetechnical components of the solution.

Description

The infrastucture model provides documentation as well as blueprintsfor ICT systems.

Purpose

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

Gov Entity 1 Gov Entity 5Gov Entity 4Gov Entity 2 Gov Entity 3

Enterprise Service Bus

Adapter Adapter Adapter Adapter Adapter

Business Process Engine

Canonical

Message

Canonical

Message

Canonical

Message

Canonical

Message

Canonical

Message

Shared Services

Integration & Canonical Data Modelالقياسي البيانات نموذج و الترابط

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اإليصال قنوات و االلكترونية الحكومة بوابة

PC Business

KioskPC

HomeMobile Access

Other Access

Data Conversion

AuthenticationAudit&

Management

MessagingTransaction

EnginePayment Services

Department XDepartment A

Gatew

ay/Po

rtal Layer

Access

Layer

Portal and Content Management

Internet

Secure Government Network

SOA

Service Oriented Architecture

الموج6هة الخدمات معمارية

Service Oriented Architecture – الخدمات معماريةالموجMهة

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.

الموجMهة ( الخدمات مبادئ )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 / عقد واجهة الخدمة

SERVICE PRODUCER

SERVICE BBACKEND APPLICATIONS

Mainframes

SERVICE PRODUCER

SERVICE ABACKEND APPLICATIONS

Mainframes

BLACK BOX SERVICE INTERFACE

LOOSE COUPLING

REUSABLE

SERVICE CONSUMER

SERVICE CONSUMER

INDEPENDENT

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

. الخدمة طلب وقواعد هوية يحدد الذي العقد هو الخدمة واجهة

: على الخدمة واجهة تحتويالطلب – رسالة بياناتاالستجابة – رسالة بياناتاالستثناءات – شروطمنها – والغرض الخدمة وظائف عن معلومات

Service Interface / Contract / عقد واجهة الخدمة

Advantages of SOA الخدمات معمارية مزايا الموجMهة

• 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 الخدمات معمارية مبادئ الموجMهة

• 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

الموج6هة حوكمة الخدمات و معمارية

النضج نموذج

SOA Governance الخدمات حوكمة معمارية الموجMهة

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!