Enterprise Integration, iPaaS and ESB:

A practical exampleShane Petersen, Technology Architect, TechnologyOne

10-11 May 2018

Commercial in confidence

Agenda

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

Enterprise Integration

▪ CiA Web Services Architecture

▪ Integration Capabilities

iPaaS and ESB

Integration Example

Futures

CiA Web Services Architecture

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

REST Web services

BPA Forms

Entity Services CiA Analysers

Business Views

Entities

(TScript)

Enterprise Integration Capabilities

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

Web

Services

RESTful / JSON

WFS

CMIS

SOAP/XMLPlatform

SAML

SMTP

File

InterfacesCiA

Deep LinkingSFTP

Import / Export

T1 Connect

Attunity sync

iPaaS and ESB

Integration Challenges

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

Technolo

gyO

ne

Ente

rprise S

oftw

are

?

Other Council Systems

Library

CMS

Health Care

Kindergarten &

Child Care

Service Provider

Systems

Aged &

Disability CareImmunisations

Bookings &

Venues

Parking

Programmes &

Activities

• Propagating master records

• Increasing number of devices and Apps

• Supplier & Service provider system integration

• Some complex external interfaces and API’s

• Legacy or bespoke systems integration

• ‘Cloud to cloud’ and ‘cloud to on-premises’

• Interface change management

?

iPaaS and ESB

Integration Patterns

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

Technolo

gyO

ne

Ente

rprise S

oftw

are

iPaaS

(or ESB)

MDM

IoT

Pub/Sub

Complex /

Legacy

Subscriber 1

Ext. 1

Publisher

Subscriber 2

App 1

App 3..n

App 2

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

BPA

Process

Regis

ter

Entity

Web

Services

External

System

(or iPaaS)

TScript

4 S

erv

ices +

1 C

iA A

naly

ser

Outbound

Inbound

1

2

3

4

Name

Entity

OneCouncil Example

Extending the “single view of a customer”

Use Case...

• Store and display data sourced from

multiple systems

• Optionally push updates back to source

• Use Restful web services Integration for

both Inbound and Outbound interfaces

• Leverage BPA Process integration to

enable further extension and automation

External System data sets shown here

Drill-down

for detail

and update

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

Configuration steps …Inbound Interface:

▪ Create a Simple Register

▪ Link the register to the Name entity

▪ Add entity fields

▪ Add fields to the maintenance layout

▪ Publish the register (to create Entity services)

▪ Create a Web Service

▪ Select the system generated Entity Service

▪ Add at least one Role to the web service

▪ Check the Active flag

1

2

Link to the

Name Entity

New

Register

Entity

1Publish / Republish

Request Message Payload

Inbound Endpoint

2Add WS

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

Configuration steps …Outbound Interface:

▪ Create a BPA Process

▪ Set to start when Register entity is updated

▪ Add a TScript Task and Action

▪ Activate the process

▪ Add a new TScript

▪ Add Step to invoke the external Web Service

▪ Map entity data into the request

3

4

Call TScript

Process

Start

Trigger

3

TScript

Step to

Call Web Service

Outbound Call

to Web Service

Endpoint

Entity &

Process

Integration

4

Integration Futures

• OAUTH for CiA Web Services (planned for 2018B)

• CiA ETL (currently in Beta in 2018A)

• Additional Entity Services (each release)

On the roadmap …

Already delivered …

• Trigger ETL processes via CiA Web Services

• Create ETL step to read CiA Analysers and Business Views

• Add TScripts to existing Ci Workflows

• BPA Forms with Classic Ci Workflow

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

Questions?

LOCAL GOVERNMENT

USER GROUP 10 - 11 MAY

Want more information on this

session?

If you would like to find out more information about this session, click

here to complete a request for more information form and a member of

the appropriate team will contact you.

May 2018

Commercial in confidence