Government-Enterprise Ecosystem Gateway (G-EEG) for Seamless e-Government
03 Jan 2007-Vol. 1, pp 101-101
TL;DR: The paper presents some challenges to seamless e-government, and proposes a technical solution - government-enterprise ecosystem gateway (G-EEG) to address them and a number of extensions are described as solutions to the challenges.
Abstract: The paper presents some challenges to seamless e-government, and proposes a technical solution - government-enterprise ecosystem gateway (G-EEG) to address them. G-EEG is a framework through which multi-organizational processes and applications can dynamically build, apply and evolve complex communication structures to asynchronously exchange messages in specific application contexts, e.g. to deliver seamless public services. In addition to basic messaging, G-EEG supports high-level messaging functions through dynamically-enabled horizontal (process-independent) or vertical (process-dependent) extensions. A number of extensions are described as solutions to the challenges for seamless e-government. Currently a research prototype, G-EEG is specified formally and implemented using open standards
Citations
More filters
01 Jan 2004
TL;DR: This chapter introduces web services and explains their role in Microsoft’s vision of the programmable web and removes some of the confusion surrounding technical terms like WSDL, SOAP, and UDDI.
Abstract: Microsoft has promoted ASP.NET’s new web services more than almost any other part of the.NET Framework. But despite their efforts, confusion is still widespread about what a web service is and, more importantly, what it’s meant to accomplish. This chapter introduces web services and explains their role in Microsoft’s vision of the programmable web. Along the way, you’ll learn about the open standards plumbing that allows web services to work and removes some of the confusion surrounding technical terms like WSDL (Web Service Description Language), SOAP, and UDDI (universal description, discovery, and integration).
546 citations
Journal Article•
TL;DR: This paper aims at contrasting the different characteristics of both approaches of information integration and process integration, and concludes with recommendations according to the intended organisational scope of integration.
Abstract: IT managers in administration must decide how to contribute to cross-organisational integration and what strategy and means to choose for achieving interoperability. Comparing the frameworks and guidelines provided by central European and U.S. governmental units, we find information integration and process integration as prominent concepts to guide interoperability efforts, but they seem to point to different directions. This paper aims at contrasting the different characteristics of both approaches and concludes with recommendations according to the intended organisational scope of integration. To be successful in these efforts it is important to understand that (a) interoperability requires a guiding vision of integration, (b) each type of integration points to a different set of interrelated ideas, assumptions and technical means, and (c) integration implies a strategic commitment to explicit forms of cross-organisational cooperation and their implementation.
122 citations
Dissertation•
01 Jan 2012
TL;DR: In this article, a continuous change in how public services are organized and provided is described, and the changes are step-wise and non-linear, influenced by external and internal requirements.
Abstract: Information technology facilitates a continuous change in how public services are organised and provided. Influenced by external and internal requirements, the changes are step-wise and non-linear, ...
17 citations
01 Oct 2012
TL;DR: The need and possibility of Enterprise Architecture concept in the Indian context to achieve the e-Govt interoperability for integration of e-Governance services is analyzed and a framework for this dilemma is proposed to arrive at the maturity level of e -Government in India that is expected in future by GOL.
Abstract: e-Governance initiatives are similar across the world, but in India it will be more complex than in the developed countries due to the multi-tire administrative structure, diversity of culture, and different process management methods in various government departments. Globally most of the Governments are taking efforts for their interoperable e-Government system to provide one stop service to its stakeholders. The solution is e-government interoperability among the administrative structure of a country. One of the ways to get the interoperability in e-Governance systems is to uphold an Enterprise Architecture paradigm across the country. Many of the global tigers have successfully used enterprise architecture frameworks for their e-Govt interoperability. Government of India (GOI) has taken several initiatives to leverage e-Governance in the country with high importance given to citizen-centric service delivery and step forward with various triumphs in the e-Govt interoperability arena. This paper analyzed the need and possibility of Enterprise Architecture concept in the Indian context to achieve the e-Govt interoperability for integration of e-Governance services and we proposed a framework for this dilemma. This framework is helpful to arrive at the maturity level of e-Government in India that is expected in future by GOL.
13 citations
01 Jan 2008
TL;DR: This document describes the implementation of UNUIIST’s research, development, and training projects, its reports, and its publications.
Abstract: This document covers UNU-IIST activities in 2005. It describes the implementation of UNUIIST’s research, development, and training projects, its reports, and its publications.
13 citations
Cites background from "Government-Enterprise Ecosystem Gat..."
...Two publications were obtained during 2006 about the Messaging Infrastructure [1, 2] and one about the Workflow Infrastructure [3]....
[...]
References
More filters
01 Jan 2004
TL;DR: This document defines the Web Services Architecture, which identifies the functional components, defines the relationships among those components, and establishes a set of constraints upon each to effect the desired properties of the overall architecture.
Abstract: This document defines the Web Services Architecture. The architecture identifies the functional components, defines the relationships among those components, and establishes a set of constraints upon each to effect the desired properties of the overall architecture.
1,563 citations
Proceedings Article•
01 Jan 20151,370 citations
Book•
01 Jun 2004
TL;DR: Enterprise Service Bus offers a thorough introduction and overview for systems architects, system integrators, technical project leads, and CTO/CIO level managers who need to understand, assess, and evaluate this new approach to integration.
Abstract: Large IT organizations increasingly face the challenge of integrating various web services, applications, and other technologies into a single network. The solution to finding a meaningful large-scale architecture that is capable of spanning a global enterprise appears to have been met in ESB, or Enterprise Service Bus. Rather than conform to the hub-and-spoke architecture of traditional enterprise application integration products, ESB provides a highly distributed approach to integration, with unique capabilities that allow individual departments or business units to build out their integration projects in incremental, digestible chunks, maintaining their own local control and autonomy, while still being able to connect together each integration project into a larger, more global integration fabric, or grid. Enterprise Service Bus offers a thorough introduction and overview for systems architects, system integrators, technical project leads, and CTO/CIO level managers who need to understand, assess, and evaluate this new approach. Written by Dave Chappell, one of the best known and authoritative voices in the field of enterprise middleware and standards-based integration, the book drills down into the technical details of the major components of ESB, showing how it can utilize an event-driven SOA to bring a variety of enterprise applications and services built on J2EE, .NET, C/C++, and other legacy environments into the reach of the everyday IT professional. With Enterprise Service Bus, readers become well versed in the problems faced by IT organizations today, gaining an understanding of how current technology deficiencies impact business issues. Through the study of real-world use cases and integration patterns drawn from several industries using ESB--including Telcos, financial services, retail, B2B exchanges, energy, manufacturing, and more--the book clearly and coherently outlines the benefits of moving toward this integration strategy. The book also compares ESB to other integration architectures, contrasting their inherent strengths and limitations. If you are charged with understanding, assessing, or implementing an integration architecture, Enterprise Service Bus will provide the straightforward information you need to draw your conclusions about this important disruptive technology.
731 citations
01 Jan 2004
TL;DR: This chapter introduces web services and explains their role in Microsoft’s vision of the programmable web and removes some of the confusion surrounding technical terms like WSDL, SOAP, and UDDI.
Abstract: Microsoft has promoted ASP.NET’s new web services more than almost any other part of the.NET Framework. But despite their efforts, confusion is still widespread about what a web service is and, more importantly, what it’s meant to accomplish. This chapter introduces web services and explains their role in Microsoft’s vision of the programmable web. Along the way, you’ll learn about the open standards plumbing that allows web services to work and removes some of the confusion surrounding technical terms like WSDL (Web Service Description Language), SOAP, and UDDI (universal description, discovery, and integration).
546 citations
"Government-Enterprise Ecosystem Gat..." refers background in this paper
...On a more technical level, Service Oriented Architecture (SOA) [22] has been widely adopted as a solution to both information integration - enabling applications running on different platforms to exchange messages using open standards, and to process integration - service orchestration....
[...]
Book•
[...]
01 Dec 2000
TL;DR: The Java Message Service (JMS) as mentioned in this paper is a standard Java application program interface (API) from Sun Microsystems that supports the formal communication known as "messaging" between computers in a network.
Abstract: From the Publisher:
This book is a thorough introduction to Java Message Service (JMS), the standard Java application program interface (API) from Sun Microsystems that supports the formal communication known as "messaging" between computers in a network. JMS provides a common interface to standard messaging protocols and to special messaging services in support of Java programs. The messages exchange crucial data between computers, rather than between usersinformation such as event notification and service requests. Messaging is often used to coordinate programs in dissimilar systems or written in different programming languages.
Using the JMS interface, a programmer can invoke the messaging services of IBM's MQSeries, Progress Software's SonicMQ, and other popular messaging product vendors. In addition, JMS supports messages that contain serialized Java objects and messages that contain Extensible Markup Language (XML) pages.
Messaging is a powerful new paradigm that makes it easier to uncouple different parts of an enterprise application. Messaging clients work by sending messages to a message server, which is responsible for delivering the messages to their destination. Message delivery is asynchronous, meaning that the client can continue working without waiting for the message to be delivered. The contents of the message can be anything from a simple text string to a serialized Java object or an XML document.
Java Message Service shows how to build applications using the point-to-point and publish-and-subscribe models; how to use features like transactions and durable subscriptions to make an application reliable; and how to use messaging within Enterprise JavaBeans. It also introduces a new EJB type, the MessageDrivenBean, that is part of EJB 2.0, and discusses integration of messaging into J2EE.
About the Authors:
Richard Monson-Haefel is a leading expert in Enterprise Java development. He is the architect of OpenEJB, an open source EJB server, and has consulted as an architect on Enterprise JavaBeans, CORBA, Java RMI, and other distributed computing projects over the past several years. Richard is also the author of O'Reilly's Enterprise JavaBeans.
Dave Chappell is vice president and SonicMQ chief technology evangelist at Progress Software Corp. Dave has over 18 years of industry experience building software tools and infrastructure for application developers, spanning all aspects of R&D, sales, marketing, and support services. Dave has also been published in Network World magazine and has presented technical topics at numerous speaking engagements including JavaOne and XMLOne.
As director of engineering for SonicMQ, Progress Software's award winning JMS Internet Commerce Messaging System, Dave oversaw the design and development of the fastest and most scalable, reliable, and robust implementation of JMS in the marketplace.
Dave has under his belt a broad cross-platform background in designing and developing Internet based middleware and distributed object systems across a wide range of technologies including C++, Java, DCOM, CORBA, and EJB. Dave's experience also includes development of client/server infrastructure, graphical user interfaces, language interpreters, and various utility libraries.
432 citations