Enterprise Integration, iPaaS and
Enterprise Service Business
Shane Petersen, Technology Architect, TechnologyOne
26 July 2018
Commercial in confidence
Agenda
Enterprise Integration
▪ Ci A Web Services Architecture
▪ Integration Capabilities
iPaaS and ESB
Integration example
Futures
Ci A Web Services Architecture
REST Web services
BPA Forms
Entity Services Ci A Analysers
Business Views
Entities
(TScript)
Enterprise Integration Capabilities
Web
Services
RESTful / JSON
WFS
CMIS
SOAP/XMLPlatform
SAML
SMTP
File
InterfacesCi A
Deep LinkingSFTP
Import / Export
T1 Connect
Attunity sync
iPaaS and ESB
Integration ChallengesTechn
olo
gyO
ne
Ente
rprise S
oftw
are
?
Other Systems
SCADA
Operational
Monitoring
Network
Design
Contractor
Systems
Other Service
Provider
Systems
Drawing
Management
Engineering
Collaboration
Vegetation
Management
Environment
Sust. Mgmt
External
Reporting
• Propagating master records
• 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’
• Increasing number of devices and Apps
• Interface change management
?
iPaaS and ESB
Integration PatternsTechn
olo
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
OneWater example
Use case...
• Inbound: Ci Anywhere web
service to create a Work Order for
SCADA Alarm
▪ Direct call to entity service or
indirect using a forms based web
service (to simplify request)
• Outbound: call to external web
service when a relevant Work
Order is updated
▪ Leverages BPA process
integration to enable further
extension and automation
BPA
Process
Web
Service
External
System
(or iPaaS)
TScript
Wo
rk O
rder
Ent
ity S
ervi
ces
3
2
Outbound
Form
Inbound
1
4
5
Configuration steps …
Inbound Interface:
▪ Create a Form
▪ Add a TScript
▪ Expose a Web Service
1
2
3
Specify
Alarm
Input
Fields
1Add Form
Flag for
Web Service use
Call Create Work Order
Entity Service
Request and Response
Form Steps
2Add TScript
Request Message Payload
Inbound
Endpoint
3Add WS
Configuration steps …
Outbound Interface:
▪ Create a Business Process
▪ Add a TScript
4
5
Call TScript
Set Process
Start
Trigger
4Create
a Simple
Process
Add Step
to Call
Web Service
Outbound Call
to Web Service
Endpoint
Entity &
Process
Integration
5Add TScript
Integration Futures
• OAUTH for CiA Web Services (planned for 2018B)
• Ci A ETL (planned for 2018B)
• Additional Entity Services (each release)
On the roadmap …
Already delivered …
• Trigger ETL processes via Ci A Web Services
• Create ETL step to read Ci A Analysers and
Business Views
• Add TScripts to existing Ci Workflows
• BPA Forms with Classic Ci Workflow
Want more information on this
session?If you would like to find out more information about this
session, request more information here and a member
of the appropriate team will contact you.
26 July 2018
Commercial in confidence