Enterprise Architecture Deployment Options. Mark Causley Sandy Milliken Sue Martin

Transcription

1

2

3 Enterprise Architecture Deployment Options Mark Causley Sandy Milliken Sue Martin

4 GIS is Being Implemented in Many Settings Organization Business to Business Department Workgroup

5 GIS is Moving to the Enterprise Client/Server Systems Web Services Networks Desktop Tools & Data Professional Productivity Information Management GIS Services... Supporting Standalone to Distributed

6 ArcGIS Family of Software Desktop GIS ArcReader ArcView ArcEditor ArcInfo Server GIS ArcIMS ArcGIS Server ArcSDE Tracking Server Mobile GIS ArcPad ArcGIS Extensions Embedded GIS ArcGIS Engine

7 In this workshop, we will... Look at organizational architecture alternatives: help you think about how you might deploy GIS within the Enterprise Look at each example architecture alternative with respect to: selection of characteristics and associated considerations describe how ESRI s s technology stack fits

8 As you begin Strategic Planning and Requirements Business objectives ser Experience (user environment, usability needs) Functional Requirements What is needed now? How are your needs expected to change?

9 Architecture Considerations Some architecture characteristics to consider Data Management Information Assurance (data integrity, continuity of operations) Security (System, Application, Data) Interoperability (Standards) Infrastructure (Computers & Networks) Performance Scalability Flexibility IT Constraints Deployment (Installation) Operations and Sustainment (Support) Total Cost of Ownership We will use a subset of these describe several architecture options using these criteria

10 Workgroup Standalone or Point-to to-point Embedded GIS ArcGIS Engine Desktop GIS ArcGIS Mobile GIS ArcPad Desktop GIS ArcGIS Desktop GIS ArcGIS File Server

11 Workgroup Standalone or Point-to to-point Data management Individual files, desktop file management- Windows, Arc Catalog File server provides common storage Information assurance (data integrity, COOP) Relies on workflow and desktop tools for data integrity COOP provided by redundancy of workstations Security Facility access ser access at desktop Internet exposure

12 Workgroup Standalone or Point-to to-point Interoperability (Standards) File based- data exchanges Desktop tools for data conversion Infrastructure (Computers & Networks) Few dependencies Workstations may be stand-alone alone or connected Low bandwidth required Performance, Scalability, Flexibility Workstation quantity and capacity Interdependent applications Very flexible (CM issues) This is how many organizations get started with GIS, but quickly encounter challenges as GIS usage increases and matures

13 Department Centralized Data Embedded GIS ArcGIS Engine Desktop GIS ArcGIS Desktop GIS ArcGIS Desktop GIS ArcGIS Mobile GIS ArcPad Data Server Sever GIS ArcSDE

14 Department Centralized Data Data Management RDBMS/spatial data Multi-user user databases Storage capacity Information Assurance (Data integrity, COOP) DBMS resources Workflows COOP must be designed and built in Security DBMS access DBMS risks (vulnerable to attacks)

15 Department Centralized Data Interoperability SQL Shared data Infrastructure (Networks & Communication) Dependence on network Bandwidth Performance, Scalability, Flexibility Processing shared between desktop and server Economy of scale Server based data storage Data model dependencies Client/server balance

16 Department Centralized Applications and Data Citrix Browser Client (Thin) Desktop Citrix Client GIS Arc Reader Embedded Citrix Client GIS Arc Objects (Thin-Thick) Thick) Application Server Citrix Server Server GIS ArcGIS ArcIMS Desktop ArcGIS Server Desktop Citrix Client GIS Arc Map Sever GIS ArcSDE Data Server

17 Department Centralized Applications and Data Data Management RDBMS/spatial data Multi-user user databases Storage capacity Information Assurance (Data integrity, COOP) DBMS resources Standardized Workflows (Potentially( Potentially ) COOP must be designed and built in Security DBMS access DBMS risks (vulnerable to attacks) Application level security

18 Department Centralized Applications and Data Interoperability SQL Shared data Leverage Off Web Services (WFS, WMS, WCS, Arc Native ) Infrastructure (Networks & Communication) Dependence on network increases Bandwidth (improved to client, critical between servers) Performance, Scalability, Flexibility Processing shared between desktop and servers Economy of scale Load balancing Server based data storage Data model dependencies

19 Organization Could be Workgroup Could be Centralized Could also consider SOA approach What is an SOA? What are web services? What is an ESB?

20 Services Oriented Architecture Design methodology to translate a Business Service (function) into a software component that is - standards based, loosely coupled, coarse grained

21 SOA Business functions are defined as services Services can be called in defined sequences to form business processes Sequences can be easily changed Services are independent Location is irrelevant Generalized (to broaden usability) Reusable Standards Compliant

22 SOA Benefits Expose IT resources in an easily consumable fashion Leverage off existing assets (systems/applications) Infrastructure becomes a commodity Faster time to market Reduced cost Risk mitigation Continuous business-process improvement

23 What is a service? A coarse grained software capability intended for use by another application(s).

24 Web Services An application that provides a Web API Web Services enable application-to to- application integration through standard web protocols Supports loosely coupled connections Pervasive Most every system supports the same low level protocols that web services are founded on Works in heterogeneous environments Most every language and platform Standards Based

25 Web Services Components Service XML (Extensible Markup Language) SOAP (Simple Object Access Protocol) Service Description WSDL (Web Services Description Language) Service Discovery DDI (niversal Description, Discovery, and Integration) Service Orchestration BPEL (Business Process Execution Language)

26 Organization SOA Desktop GIS ArcGIS Engine Embedded GIS ArcGIS Engine Browser Mobile GIS ArcPad Service Consumers Web Server Service Discovery Geocode DDI Service Proximity Service Map Service Route Service Notify Employee Get Customer Dispatch Technician Service Orchestration BPEL Engine Service Description WSDL Web Applications Send Help. Dispatch Technician - Get Customer Geocode Proximity Route Notify Employee Adapters Service Providers Internal Data Server GIS ArcSDE Enterprise GIS Applications Server GIS Geocode Service ArcGIS Proximity Server Service Map ArcIMS Service Route Service Other Enterprise Applications CRM Get ERP Customer Notify Employee External External Services Services and and Data Data

27 Enterprise Service Bus According to Gartner, an ESB is standards-based middleware that uses a service-oriented architecture (SOA) and has messaging, intelligent routing, and transformation capabilities. Combines: Message Oriented Middleware ++ Message Transformation Intelligent Routing Distributable Web Services

28 ESB Features Depending on how much $$$ you want to spend an ESB will have Incorporate DDI & BPEL (Or similar service) to build coarse services Error handling & notification Built in Adapters Support Additional Protocols Security

29 Many ESB Options Write ESB Services Mule (open source) Sonic IWay SeeBeyond TIBCO Microsoft Biztalk (SOA-Indigo) WebLogic WebMethods IBM WebSphere SAP Netweaver

30 Who s s on the bus? Java or.net? An ESB provides the common integration fabric that bridges the gap between these two platform technologies Java applications can use JMS to connect into the ESB Applications written using a J2EE EJB server interface with a MessageDrivenBean (MDB).NET applications can interface using ASP.NET and Web Services Enhancements.NET Framework supports SOAP and WSDL natively Any Application could just as easily use SOAP over HTTP or WS-ReliableMessaging

31 Organizational Service Oriented Architecture Data Management Distributed Multi Systems Information Assurance (Data integrity, COOP) Leverage services to automate processes and enforce data integrity Standardized Workflows and flexible COOP dependent upon a larger community Security Multiple security solutions available at the ESB level (LDAP, SSO) System, Application and Data level security

32 Organization Service Oriented Architecture Interoperability Standards based messaging Infrastructure (Networks & Communication) Dependence on network increases Bandwidth critical to success Performance, Scalability, Flexibility Message based transactions have limitations Very flexible and agile Bandwidth! Bandwidth! Bandwidth!

33 Business to Business Federated 4/1/2005

34 Business to Business Federated Data Management Leverage off external resources and partners (ArcWeb( Services) Metadata Information Assurance (Data integrity, COOP) Authoritative data sources Security Authentication between businesses Filtering proprietary and sensitive information Interoperability Agreement between businesses Infrastructure (Networks & Communication) Dependence on national / global network Connectivity is critical Performance, Scalability, Flexibility Leverage partnerships and existing data Relationships are easily changed 4/1/2005

35 How to Decide? Consider Your Organization s s mission and objectives Consider the characteristics of each deployment option Develop as part of your Technology Strategy Evaluate based on your specific needs

36 Identify Information Producers and Consumers GIS Information Themes Business nits Base Map Streets Water lines Sewer System Parcels Zoning Buildings Vegetation tilities Emergency Services se Internal Produce Tax Assessment Water / Waste Water P P Supply Land Records Facilities External Arc Web Services Acme Base Map S S P P? P P P P S Example of Data Themes Produced and Consumed

37 6 R Flexibility Compare Architecture Options Compare Architecture Options Scalability Performance Infrastructure Interoperability Security Information Assurance Data Management Critical Characteristics Potential Architectures Desktop / Point- to-point Centralized Data Centralized Data and Apps Service Oriented Architecture (SOA) Federated

38 Recap ESRI supports a variety of architecture approaches from individual to enterprise Technology is there approach should be business driven

39 For more information Other sessions will cover: Developing an effective GIS Technology Strategy System Design and Configuration Strategies Including sing Citrix Planning an Enterprise Implementation Integrating GIS within the Enterprise Planning an Enterprise Geodatabase Solution Developing Secure ArcGIS Solutions ArcGIS Enterprise Systems: Performance and Scalability Or contact

40 Questions?

41 Thanks for attending! Enjoy the Conference!