2. Company Information
Global Information
Headquarters : California, USA
Offices : 11 World wide
Development : Bangalore, India
Founded : 1995
Deployments : 520+ World wide
Global Partner Network
2
3. Typical Business Use Cases
Connecting Applications and Technologies across the Extended Enterprise
Usage Description
SOA Visual, drag-drop-and-configure, unified design/run-time model of business processes and
asynchronous event-flows that implement distributed services immediately without programming.
Messaging Industry-fastest, linearly scalable Java Messaging Service (JMS) with throughput in excess of
95,0001 messages/sec on single server.
Integration Connect disparate applications and systems – independent of language, architecture, data, transport
protocol, and geography – into a networked, intelligently-routed environment with runtime flexibility.
Performance Optimize business process execution by exploiting relevant functionality to enable business your
way vs. application vendor’s way.
Availability Improve application response time and reliability for highly-remote, intermittent bandwidth networks
by de-coupling tightly-integrated, web and client/server application architectures.
1
FioranoMQ Closed benchmark testing as of September 2010.
3
4. Customer Use Cases
Global Innovators Run Fiorano for Enterprise-Wide Performance
Usage Application Customer
SOA Manage cargo logistics for millions DHL Worldwide
packages daily.
Messaging High-speed, high-volume, low-latency Scottrade,
back-office trade clearing and Thomas Weisel,
settlement. George Weiss
Integration/SOA Connect 6,000 US coastal ships into United States Coast Guard
USA Homeland Security network
Performance Optimized SAP order-entry process – United Spirits (Kingfisher)
speed invoice processing time by 80%
Availability No downtime for system access at Schlumberger
remote, offshore oil rigs with unreliable
satellite links.
4
5. Fiorano… Product portfolio…
Fiorano SOA Platform
Fiorano Enterprise Service Bus (Fiorano ESB™)
FioranoMQ® (Messaging Middleware)
Fiorano IDE, Components, Adapters and Tools
5
6. Fiorano Enterprise Service Bus (ESB)
Comprehensive set of prebuilt components / adapters
Extendable component framework and support for Java, C, C++, C#
Support for Standards JCA, JMS, WSDL 1.1, SOAP 1.2 etc
Drag-drop, configure, connect, distribute and execute business logic
Horizontally scalable. Hardware not limiting constraint on performance
No Single Point of Failure
Support for all major transports:
Database File FTP Email HTTP Web services etc
Best Visual Transformation tool
Complete Auditing, Management and Monitoring from a single view
No Programming/XML Configuration
Excellent Technical support with quick turn-around times
Comprehensive Deployment rules and Security
Light Weight Servers
Integrated versioning and support for Source control
Cloud Ready platform
6
7. Centrally Managed, Peer-to-Peer
Architecture
Fiorano Tools
Studio Dashboard
Pop3 SMTP
FileReader /
Writer WebSphere MQ
Database DBProc
Fiorano Enterprise Server (FES)
FTPPut / Get XMLSplitter
Fiorano Peer Server (FPS)
Distributed JMS Bus
Fiorano's architecture is document-centric, event-driven, loosely coupled,
asynchronous and message-based; Choreographed Business Services.
7
8. Fiorano – Value proposition
1. No single point of failure – The technology is based on Peer to Peer architecture
2. Seamless project management and delivery – Provides a single view for both
business and implementation teams
3. Rapid deployment – Requires half the time and half the programmers when
compared to other vendors
4. Ease of use – You can Configure, Connect, Distribute and Execute with minimal
programming
5. No technology or vendor lock-in as it is completely based on standards
6. Flexible and Scalable – Cloud enabled
7. Matured product line – Built ground-up and not evolved through acquisitions
8. No failed implementation – Successful product with effective global support
8
9. Fiorano – Temenos Relationship…
• Scalable architecture – Fiorano ESB is part of the Temenos Enterprise Framework
Architecture (TEFA).
• Rapid development – Temenos T24 inbound and outbound adaptors developed in
less than 3 months.
• Ease of use – Zero coding environment with point and click tools.
• High RoI – Implementation time is more than halved in comparison with an equivalent
integration using IBM, Oracle or Microsoft.
• Seamless integration with 3rd party applications – AML, Risk Management, BI,
Payment Solutions, SWIFT, ISO 8583, ISO 20022, ISO 15022, etc.
• Fiorano ESB will be available for shipment as a packaged offering with T24, Release
13 (scheduled for release in Feb 2013).
• Backward compatibility – Supports T24 Release 9 and upwards.
• Annual subscription based licensing and pricing.
9
10. Key Features
1 Integrate T24 with all other Bank systems
2 Notify external systems of T24 business events
Custom adapters for integration
3 - Outbound adapter for events into T24
- Inbound adapter for events out of T24
4 Participate in enterprise orchestrated value chain
5 Further message routing and transformation via standard ESB
Integration time reduced up to 80% via user tooling
10
11. R12 Technical Architecture
Presentatio
Design
Design
Mobile User
ToolBo
n
Internet Bankin Interfac Event WebServic Workflow
Banking x Design e Design Design
g e
WebServic
e TEMENOS Open Connectivity Framework (TOCF)
Middleware
Synchronous Open Financial Service (OFS)
Integration Framework
access
External
Security Management System
ESB
Designers
Run-Time
Adapters
Middlewar
OFS
e
Asynchronous T24 Banking
access
Account Custom
Program er
Insight (BI) Database Connectivity
Data
OLAP OLTP Design
11
12. R12 Integration Framework – Design Time
1. Fetch Transaction Design Time Source Control
that can trigger event Management
out
4
2. Define Integration
events 2 3
3. Create enrichment
instructions
Events Flows XSD
4. Store integration
project (Event, flows)
into SCM. (optional)
1 5 6
5. Publish the project to
T24 (xsd generation)
6. Get XML schema
(xsd) describing event Service Landscape Event engine
out format
T24 Banking
12
13. R12 Integration Framework – Run Time
1. When the T24
contract / transaction is ESB 3 Routing
committed the relevant
Exit Point is triggered. Transformation
Message constructed in
XML format Fiorano
ESB
JMS RM
2a. The Interface table Adapter Txn 2
can be polled out by
the Event Delivery (R13*)
Service to directly
deliver event to JMS
with 2PC Event Delivery Service 2b
T24 Banking
2b. The Interface table 2a
can be polled out by a
ESB Adapter. To
directly deliver event
3. The routing /
Transaction
transformation stage 1 Exit Point
transforms the event RM
format to match with Txn 1
expected format of the
external service
Database Interface table
13
*plan
14. Thank you
For more information, please visit: www.fiorano.com
Or Contact
Ashraf Imran
+44 0 2070 787 422
ashraf.imran@fiorano.com
14