DataTree Cloud Services

presenting:

GIS Cloud Services,Custom Search Cloud Services, EGL - Enterprise Address Standardization & Normalization Services

Adriano Freire / Nima Nattaghafreire@firstam.com 715 250 7974

The R & D GroupFirst American DataTree 4 First American Way, Santa Ana, CA 92707 www.datatree.com

DataTree Cloud Services

DataTree Cloud ServicesWe always knew and we’ve prepared for making DocEdgeIII Spatial’s component a reusable plugin and have it relabeled to other internal or external brands brought the R&D Group a creation of a simple, elegant and lightweight solution that can help us expand our “Enterprise Address Standardization & Normalization Services” EGL, and to start enabling several existent “well-known-components” as reusable modules across the enterprise.

Based on this model, or framework, very few modifications are required to be made on existent applications to provide (become a CloudService) or to consume these applications right away. Even though solution is very simple, it relies on state-of-the-art security mechanism to protect the assets of all interested parties.

DocEdgeIII GIS MapSearch, ParcelIQ Batch Upload, and many other, proven useful implementations can become CloudServices almost immediately, and any application can become a consumer and leverage Cloud Services features to our benefit.

If an application has its own deliverables and products, it can definitely benefit when leveraging DataTree’s Enterprise Address Standardization & Normalization Services EGL, Map Searches, Custom Searches+, and Interactive Comparable Searches and deliver its own products - Wait, that’s what DocEdge III will be doing.

Are there bullet points?• Get things developed and to Market faster - Today, our current application development cycle is long and

repetitive - We spend more time creating accessory functions than real feature ones: Every single application we have (and everyone else in the marketplace) has a large overlap of common features: (user management, billing, security, home page, contact us page, chat, customer service, printable view, geographic coverage, open an account, privacy policy, our facebook page)...

• Focus - If DocEdge organic goal is to retrieve documents and property reports, wouldn’t make sense to concentrate, improve, and work on these features full time?

• Simplification - The intercommunication between our components can be defined in a single interface which is used by all applications and resources. The FirstAm.CloudServices.Protocol - a developer1 can prepare it and quickly start using it - (8 to 24) hours range.

• Quality - Simpler, focused, easier to test, easier to maintain, developers, product, and operational groups can focus on the real deal.

• ReUSE - Using a component many times, don’t only save money & time, it makes it better and reliable. Also, what’s ready and in use, it’s already done.

First American DataTree

DataTree Cloud Services Framework

1 Assuming experience with .Net Framework or Similar, Xml Web Services, Internet protocols, and the application to be integrated.

User Authentication WorkflowNormally, one would start scratching her/his head at this point, this actually can be, and normally is, the most complex mechanism of a standard inter-system integration. Marrying two disparate systems security mechanisms, even if they use similar approaches, it’s always complicated.

Most of the integration platforms purpose is to carry on an authenticated user, with hers/his permissions over to the other system, while it establishes a connection between the 2 systems to check for permissions at every checkpoint. The trouble is to translate trust relationships, and layers and several layers of permissions and authorizations.

But sometimes, what’s simple, just passes by unnoticed: we establish the “trust” on the “visiting system” or consumer as a basis premise. If it has the permission to access the feature, it will also have the permission to delegate it to its users. In fact, when the user first sees the Cloud Application link on her/his browser, all the acknowledgment is complete.

The consumer system needs to have a electronic temporal issued security certificate to gain access to the Cloud Services Gateway, and all information is encrypted on the fly.

First American

DataTree Cloud

Services

2. First Am prepares &

sends a Secured Token Request to DataTree Spatial Gateway

1. Use Authenticateswith First Am

3. A identification token

is given back to be attachedto the MapSearch Page Link

4. First American Page is

served by DataTreeCloud Application Pool

with FirstAm Look & Feel

First American DataTree

DataTree Cloud Services Framework

Cloud Services Protocol Class Diagram

The consumer App is required to prepare an AuthorizationRequest object which is the combination of the UserPassCard and the AppFacade ones. The first describes the user, her/his access to features2, how long, the geographic locations they can access, and how many times each can be accessed for. The ladder, defines how the Cloud App looks, and how to handle the user back. Facilities include Key/Pair collections for call back parameters, session ids, etc.

For simplicity and testing, we also have “Unlimited” levels for all types of permissions, and that’s it.

First American DataTree

DataTree Cloud Services Framework

2 Feature is an abstraction that describes “something” a user might want to get access to. It can be a report, a search feature, a layer on the map, or the ability to change something.

Cloud Services Gateway (Service) Class Diagram

To be able to authenticate, receive credentials, temporarily suspend usage, get usage data, report bugs and issues, you will need access to the Cloud Services Gateway Web Services:

These services can be accessed using REST, SOAP, and WCF protocols.

First American DataTree

DataTree Cloud Services Framework

How the consumer Application delivers its Products?3

Using the the GatewayService.ProviderService, a App provider can grant access to products, interfaces, reports, just by defining it compliant to the IFeature interface. This service is the one and only portal to publish them to the Service Directory.

The delivery workflow is described as the following diagram:

CLOUD SERVICES G

ATEWAY

E.A.S.N.S.Enterprise Address

Standartization & Normalization Services

RM

GISCloud

Services

RM

Custom SearchCloud

Services

RM

Comparable SearchInteractive

CloudServices

RM

1. AddressSearch

2.Address is

standardized, normalized& verified

(Including suggestions)

3.Enterprise wide

Address PropertyIdentification

EAID

1.BSpatial Search

4Report/Document

ProductDelivered

2.BGIS Geographic

Data is Converted toEAID

First AmericanDocEdge

TIPsParcelIQ

...

1.CCustom Search

3.BEAID is used to

Retrieve Reports/DocumentsProduct

2.BGIS Geographic

Data is Converted toEAID

First American DataTree

DataTree Cloud Services Framework

3 Preliminary description - Available on Summer 2012

DataTree Cloud Services Deployment Layout

Certificate Server

Public & Private Key Server

Web Services

Client Application/Serverrequests Access Token

Token is used tocompose application

address (url)

App ServersResponse is

loaded with EASNSPropertyID

PropertyIdentification

User orderReports

using GIS

CustomizedApplication

EASNS

Application hasReports, lacks

GIS

User receives Reportfrom Client

Application using EASNS ID

First American DataTree

DataTree Cloud Services Framework

Revision History

Revision History Table

Date Notes

Thursday, December 8, 2011 Creation

First American DataTree

DataTree Cloud Services Framework