Integration: The road more commonly travelled. Steve Scheepmaker - - PowerPoint PPT Presentation

integration the road more commonly travelled
SMART_READER_LITE
LIVE PREVIEW

Integration: The road more commonly travelled. Steve Scheepmaker - - PowerPoint PPT Presentation

Integration: The road more commonly travelled. Steve Scheepmaker Manager, Information Technology Township of Langley A lighthearted presentation covering the following topics: What is Integration? What should you consider? What are some


slide-1
SLIDE 1

Integration: The road more commonly travelled.

Steve Scheepmaker Manager, Information Technology Township of Langley

slide-2
SLIDE 2

A lighthearted presentation covering the following topics:

  • What is Integration?
  • What should you consider?
  • What are some of the options?
  • Examples
slide-3
SLIDE 3

“What is Integration?”

slide-4
SLIDE 4

“Integration is a process of combining or accumulating.”

(WikiPedia)

slide-5
SLIDE 5

“To form, coordinate, or blend into a functioning or unified whole.”

(Webster’s)

slide-6
SLIDE 6

Integration is becoming more and more mainstream…. … actually, there is (and should be) an expectation to have “touch points” available for integration purposes.

slide-7
SLIDE 7

In GIS, integration generally involves meshing together spatial and/or attribute data into a homogeneous dataset.

slide-8
SLIDE 8

As GIS becomes a core component of the enterprise landscape, the need to integrate GIS with other “traditional” enterprise applications is becoming much more common.

slide-9
SLIDE 9

“So I want to integrate, now what?”

slide-10
SLIDE 10

“What are you trying to do?”

  • Business Process Integration
  • Data Integration
  • Something else?
slide-11
SLIDE 11

“What do you need?”

  • One way
  • Bi‐directional
  • Aggregation
slide-12
SLIDE 12

“What other factors do I need to consider?”

  • Latency
  • Performance
  • Data structure/quantity
  • Transaction load
slide-13
SLIDE 13

“One Source”

slide-14
SLIDE 14

The “One Source” philosophy states:

“We must provide efficient access to information while attempting to consolidate and eliminate data redundancy and duplication whenever possible.”

slide-15
SLIDE 15

At the Township of Langley, the “One Source” philosophy is helping drive our integration needs and requirements.

slide-16
SLIDE 16

“What are my options?”

  • “Duct tape and rubber bands”
  • RDBMS
  • Application integration
  • Enterprise integration
slide-17
SLIDE 17

“Duct tape and rubber bands”

Do whatever it takes...

slide-18
SLIDE 18

As long as you have:

  • A full pack of bubble gum
  • Swiss army knife
  • A license of Access and/or Excel

You can make anything happen!

slide-19
SLIDE 19

RDBMS

Leverage capabilities of the RDBMS to perform integration at the data level.

slide-20
SLIDE 20

RDBMS ‐ Example Requirement:

  • 1. Leverage property information stored

within the Land Management System inside the GIS system.

  • 2. Minimize duplication if possible
slide-21
SLIDE 21

RDBMS ‐ Example Solution: Perform a “join” at the database level to aggregate information stored in the GIS and the land management system.

slide-22
SLIDE 22

RDBMS ‐ Example

Solution:

slide-23
SLIDE 23

RDBMS ‐ Example

Solution:

slide-24
SLIDE 24

Application Integration

Leverage capabilities of a particular application or development environment to integrate at the application level.

slide-25
SLIDE 25

Application Integration ‐ Challenges

Application “A” Application “B”

One challenge is the inherent system boundaries… …as long as the vendor has provided the “touch point”

slide-26
SLIDE 26

Application Integration ‐ Options

Many options provided by the operating system for Inter‐process Communication (IPC):

  • COM
  • Windows messaging
  • DDE
  • Etc.

… All are accessible using a number of development environments

slide-27
SLIDE 27

Application Integration ‐ Example Requirement:

  • 1. Utilize GIS functionality within the Land

Management System

  • 2. Leverage existing web‐mapping tool to

minimize the need for end‐user training

slide-28
SLIDE 28

Application Integration ‐ Example Solution: Leverage application level integration touch‐points to integrate existing web‐ mapping tool with the Land Management System.

slide-29
SLIDE 29

Application Integration ‐ Example Solution:

slide-30
SLIDE 30

Application Integration ‐ Example Solution:

slide-31
SLIDE 31

Application Integration ‐ Example What’s happening under the hood?

  • Windows messaging
  • HTTP POST
  • Database operations
slide-32
SLIDE 32

Enterprise Integration

Leverage inherent capabilities of a enterprise architecture or middleware to perform required integration.

slide-33
SLIDE 33

Enterprise Integration ‐ Explanation Lengthy and complicated topic… … if you thought we had too many acronyms and confusing terminology before…

slide-34
SLIDE 34

Enterprise Integration ‐ Explanation ESB

Federated Mediated

SOAP Queue SOA

Messaging

Synchronous

Asynchronous

REST

Middleware

Yikes!!

slide-35
SLIDE 35

Enterprise Integration ‐ Explanation

Holy SOAP Batman! I can’t access my WSDL, the ESB does not want to respond and it appears that my Middleware might have failed!

slide-36
SLIDE 36

Enterprise Integration ‐ Explanation

You are freaking me out Robin! WSDL, ESB and your Middleware – do I need to drive you to the doctor?

slide-37
SLIDE 37

Enterprise Integration ‐ Explanation In a nutshell:

  • There is a real paradigm shift occurring in

how we view the enterprise; integrating systems is a requirement.

  • GIS will play even a more important role on

the enterprise landscape in the years to come.

slide-38
SLIDE 38

Enterprise Integration ‐ Explanation Just one of the many new advancements helping enable enterprise integration… Service‐Orientated Architecture (SOA): SOA establishes an architecture from which applications expose methods (building blocks) for other enterprise applications.

slide-39
SLIDE 39

Enterprise Integration ‐ Options Other integration options available:

  • BizTalk
  • SQL Server Integration Services (SSIS)
  • Vendor specific (Web services, etc.)
  • Too many to list!
slide-40
SLIDE 40

Enterprise Integration ‐ Example Requirement: Implement integration between the following systems: ‐ Municipal business license database ‐ Regional land inventory database ‐ Motor vehicles database ‐ Police mainframe

slide-41
SLIDE 41

Horatio says: “Integration is cool!”

slide-42
SLIDE 42

Enterprise Integration ‐ Example

“By correlating all owners of dog grooming businesses that recently

  • btained a class 4 drivers license we

determined that the killer has brown hair and lives in a 2 bedroom condo within two kilometers of a freeway onramp – now only if we had a GIS…”

slide-43
SLIDE 43

Enterprise Integration ‐ Example Requirement: Need to access images in catalog system directly inside other corporate systems

slide-44
SLIDE 44

Enterprise Integration ‐ Example Solution: Encapsulate business logic for image search inside of a web service and leverage that functionality in other enterprise applications.

slide-45
SLIDE 45

Enterprise Integration ‐ Example Solution:

…/_WsLglPlan.asmx

[GetLegalPlansByNumber(string)]

Image Catalog Web Mapping SharePoint

slide-46
SLIDE 46

Enterprise Integration ‐ Example

…/_WsLglPlan.asmx

[GetLegalPlansByNumber(string)]

slide-47
SLIDE 47

In Summary:

  • Technology is continuing to evolve.
  • Integration is becoming a requirement.
  • GIS vendors are helping with this.
  • Plan your integrations carefully.
  • Try to think modular/ think big picture.
  • We are only just beginning…
slide-48
SLIDE 48

Thanks!