e-governance Other Government Central Government Business State Citizen

Transcription

1 5th International Conference on e-governance e-governance Technology Perspectives December 28, 2007 WELCOME S. Ramakrishnan

2 e-governance e-governance is the use of IT to support government operation, engage citizen and provide public services. G2G G2B Other Government G2C Central Government G2G G2B Business G2C Citizen State

3 Participants of e-governance e Framework Delivery Service Request Channel Service Seekers Encoded Request Service Access Standard Service Provider Provider Government Request Standard Standard Services Request Request * -Source: Intel

4 Paradigm shift e-governance From Technological perspective there is a paradigm shift from Closed Source/proprietary/shrink wrapped Software Towards Service-Oriented applications with Strong Inclusion of the Community ( the user) New paradigm follows Open Source (interaction) methodology. Open Standards are the foundation for Software as commodity and for a inclusive egovernance applications. From software as Artefact to Software as a Service India have the opportunity to build up an open and robust infrastructure based on Open Systems, Open Standard, share the knowledge available in the OS community for further development.

5 Interoperability Tools Technological tools required for inclusive egovernance application development Generic Interoperability Framework for egovernance Open Standards and Open Source Solutions Integration of disjointed legacy systems (XML Technologies) SaaS realized through EA, SOA and Web Services. Localization Language Tools

6 SOA Framework Development using OpenStandards and OpenSource Tools OASIS, W3C, WS-I, WS-BPEL XML, SOAP, WSDL Consistent Meta-data Open Standards Open Development Platform Open Source Runtimes Eclipse, Mono, Netbeans Consistent implementation and validation environment ObjectWeb, Apache Consistent execution environment Open Source ESB Open ESB, Mule ServiceMix, Petals Celtix, ChainBuilder, Apache Synapse

7 Technology evolution of e-governancee

8 e-government Interoperability e-government Interoperability is the ability of two or more diverse government information and communications technology (ICT) systems or components to meaningfully and seamlessly exchange information and use the information that has been exchanged. It can be realized with Open Standards Architecture EA and SOA

9 Enterprise level Interoperability * -Source: Intel

10 Interoperability results when components are able to work together to complete a process. Open Standards, by helping to define component interfaces, increases interoperability. This leads to simpler, repeateable and quicker integration efforts Eric Sliman According to Bruce Perens Open Standard is more than just a specification, and that the principles underlying the standard and the practice of offering and operating the standard are what make the standard open. The Principles are Availability Scalability Reusability Openness Maximize end-user choice Open Standards

11 Recommendations W3C Standards Unicode RFC (IETF) (HTML, XML, SVG, XFORMS, DOM,CSS) STD (IETF) OASIS (SOA, XML) Standards (ISO) ECMA (JavaScript) Names, Number (IANA)

12 Current Implementation Problems Isolated Applications across the department Independently designed and operated legacy systems across the department were developed without consideration of any future need for information sharing or reuse which they lack openness, coordination and interoperability. Solution Service Oriented Architecture

13 Building e-governance e Applications Architecture Idea about how to structure your app, possibly shared through natural language documentation and structured methods, like UML (MVC, Enterprise Architecture) Selection of Security Framework, Hardware, Database Essentials, License Methodology Other Features Security, Server Database Building web Application Framework an implementation of an architecture that someone can use as the basis for a working application (Struts, Ruby on Rails, Django) Solution for recursively occurred Problem Certain Languages conducive to the development of app. Frameworks larger communities Web Languages (Python JSP) Design Patterns

14 Traditional Web Applications

15 Dynamic Web Application Framework

16 Web Service is Platform-independent computational entity, Defined Published Classified Discovered dynamically assembled for developing massively distributed, interoperable, evolvable systems and applications[1] Web Services as the enabling Technology preferred Implementing Technology for SOA

17 Service Oriented Architecture First proposed by Gartner analysts Roy W. Schulte and Yefim V. Natis. They specified SOA as a style of multitier computing that helps organizations share logic and data among multiple applications and usage modes. Service Oriented Architecture(SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. - SOA Reference Model (OASIS) Service Oriented Architecture Frame work enables the Government process and Procedures to achieve total integrated governance between G2G, G2B, G2C and C2C.

18 SOA Benefits Reuse the ability to encapsulate and expose coarse grained business functions as services Loose-coupling ensuring that service consumers are sufficiently abstracted from the physical implementation of a service Identification and categorization (discoverability) making sure that potential consumers can find the services they need

19 The 7 steps to SOA are: Deployment of SOA 1. Create/Expose Services 2. Register Services 3. Secure Services 4. Manage (monitor) Services 5. Mediate and Virtualize Services 6. Govern the SOA 7. Integrate Services (ESB)

20 ESB An enterprise service bus generally provides an abstraction layer on top of an Enterprise Messaging System which allows integration architects to exploit the value of messaging without writing code. ESBs are an implementation of SOA ESBs are based on message-oriented middleware The base functions of an ESB should be individually addressable and usable

21 Role of ESB in SOA Infrastructure External/Internal Service Requestors Business Process Management SOA Infrastructure ENTERPRISE SERVICE BUS (Routing, Transformation, Mediation etc) Business Service Directory External/Internal Service Providers

22 Business Integration and Standards Application to Application (A2A) Business to Business (B2B) Business Process Management (BPM) Many architectures, Technologies and Vendors. Standards JSR 208 Service Component Architecture (SCA), Service Data Objects (SDO)

23 e-governance applications with Enterprise Service Bus Finance Dept Personnel Dept Enterprise Service Bus Data Connector Connector Connector Connector Connector Data Domain Dept Data Purchase Dept Data ENTERPRISE SERVICE BUS Data Stores Dept Scalability To handle large number of Services Separates changes in the Integration logic Routing Transformation Protocol Changing Facilitates management Message monitoring, Auditing Enables enterprise wide service reuse by registry integration

24 Case Study: National Service Delivery Gateway National Service Delivery Gateway is like a post office or telephone exchange which electronically allowed to route the business messages originate by service seeker using service access provider infrastructure and fulfilled by back office service provider. National Service Delivery Gateway makes MANY-TO-MANY connection possible through MANY-TO-ONE connections. National Service Delivery Gateway would promote inter-operability among autonomous and heterogeneous systems MANY-TO-MANY (N 2 N)/2 = 15 MANY-TO-ONE N = 6 Gateway

25 National Service Delivery Gateway Mission To bring interoperability among autonomous and heterogeneous systems (application and data) in service delivery by standardized interfacing, messaging, and routing switch Objectives To evolve Gateway messaging standards and build at least one government owned Central Gateway based on these standards. Act as a catalyst in enabling the building of Standards based e-governance applications with Gateway as the middleware. Enable integration across Centre, State or Local Governments there by enabling Integrated Service Delivery (ISD) and sharing of data across departments & various front-end service access providers in a secure manner. De-link the back-end departments/service Providers (SP) from the front-end Service Access Providers. This would simplify the view of the external world to the departments at one end and encourage competition at the front-end. Independent service providers will be able to provide services with varying levels of complexity, cost and service quality levels.

26 Business Driver/Issues Enables interoperability among heterogeneous environments through standards-based messaging Enables integration across Centre, State or Local Governments through a hierarchy of Gateways Acts as a National e-services Directory enables introduction of Single-Sign-On Facilitates delivery of joined-up services of various departments with certainty and speed

27 Business Context Diagram National Services Directory Payment Gateway Certifying Authority Issues PKI Digital Certificate during user provisioning and provide online infrastructure for verification Sending Service Message with attachment to the NSDG for its fulfillment, retrieving message Service Access Provider Submit Service Request, receive service request outcome. To pay the transaction charges online for service delivery Resolving the Service Routing Path for unlisted services at NSDG gateway Route Service Request Message, Receive Response Message National Service Department Delivery Gateway of Transport Exposing the web services, route service request, send service response for fulfillment of service request received from the Service Access Provider Other Gateway User registration, System Administration, Database Administration, Business Transaction Monitoring System Administrator Service Seeker Service provider

28 Stakeholders Service Seekers Citizen, Business, Govt. Dept. approaches a Service Access Provider to access a services Provide information for service access Service provider Provides one/more back office services Host services with NSDG Service Access Provider Provides service access to service seekers Registers with NSDG for sending messages Register with service providers to offer services Provides an interaction point for service seekers National Service Delivery Gateway A point of integration between service seekers and service provider A mechanism to build transparency for service request and its fulfillment A separation of concerns of service seekers and a service provider A standardized, secured reliable conduit of message transfer between service seekers and service providers A single point of access for common services. Back office Services The actual realization of a govt. services Accessed by service access providers Has specific access policies Requires business specific messages to be sent Responds with service response

29 Actors User Service Seeker Service Access Provider Service Provider National Services Directory Back-office Service NSDG Administrator

30 Enterprise view Network Channels Service Seeker Citizens Businesses Service Access Provider Delivery Channels NSDG Service Provider Govt Depts Centre States Govt Services Local Authorities Core Services Autonomous Bodies Delivery Channels Messaging, Audit Logging, Transaction Management, Gateway Services Directory, Inter-Gateway Messaging, National Services Directory Common Services SAP/SP Registration & Authentication Services

31 Architecture Overview Diagram of NSDG MPLS WAN Network Http/Https National Service Directory Http/Https PKI Digital Signature Interface Http/Https Payment Gateway Interface Clients Application/Mediation Services Resource Managers Service Access Provider /Service Provider Access via Browser Browser Service Seeker Access Channel Browser NSDG Protocol Connector (MQ Client/Server) Internet Service Access Provider Presentation Layer+ Business logic Services Web services directory UDDI Http/Https Http/Https/ JMS/MQ Public & Pvt. N/Ws Protocol Firewall Extranet Firewall Load Balancer Invoke Services using IIS Interface Received Msg (SOAP with IIP header using IIS specification) Reverse Proxy Server Authenticate Message using IIP Header XML Accelerator ( Validate & Auth. Msg, GUID gen.) Domain Firewall Static Content Web+ Portal Server Content Delivery Directory & Security Services (LDAP+PKI Key) User Profiles IIS Interface MQ for JMS Support Locate Service Application Services Application Logic Reporting Engine Gateway Service Registry and Repository Authorization Enterprise Service Bus (Message Routing by Dynamic Binding) Audit Logs Security Management System Management Application Data Application Database Services Web Service Directory IIS Interface Extranet Firewall NSDG Protocol Connector (MQ Server/Client) Appl. Specific Connector Service Interpretator Layer Service Interpretator Layer Native Interface Layer Appl. Specific Connector Native Interface Layer Service Application Existing Application Universal Layer

32 Standards Proposed for Gateway Interoperability Interface Specifications (IIS) Interoperability Interface Protocols (IIP) Specification doesn't cover asynchronous message support.

33 Interoperability Interface Protocol The Interoperability Interface Protocol defines the interaction between Service Access Provider implementations, the Service implementations and the Gateway. The protocol provides a mechanism for submitting documents destined for the services of public sector organizations and an acknowledgement-polling scheme for subsequently querying the status of the message as it passes through the Gateway.

34 Conclusion From Technological perspective there is a paradigm shift from Closed Source/proprietary/shrink wrapped Software Towards Service-Oriented applications with Strong Inclusion of the Community ( the user) New paradigm follows Open Source (interaction) methodology. Open Standards are the foundation for Software as commodity and for a inclusive egovernance applications. From software as Artefact to Software as a Service India have the opportunity to build up an open and robust infrastructure based on Open Systems, Open Standard, share the knowledge available in the OS community for further development.

35 THANK YOU