1. Jake Freivald Director iWay Software
March 25, 2017
Service Oriented Architecture
SOA: Not Just
The Missing Link?
Web Services
Jake Freivald
Director
iWay Software
Norman Manley
Vice President
Service Oriented Architecture is often confused with Enterprise Application Integration (EAI) and thus with Brokers, SOA is much more. EAI came originally from the IT side an its role was to make application cooperate with each other, later BPM was added and workflow to ensure that the applications also did something useful for the Business. SOA is the completion of that model and its message is Business Value, to provide business value the back-office systems need to work with business processes not just data – and to do that you need an adapter framewrok aas well as a broker.
March 25, 2017
Copyright © 2004 iWay Software 1

2. World leader in connecting information assets Over 2000 customers
SOA – The Missing Link? iWay Software - An Information Builders Company
World leader in connecting information assets
Over 2000 customers
Over 6000 servers
Adapter Suite for integration
iWay’s parent company, Information Builders, has excelled at helping organizations meet their information delivery needs for over 25 years. IB is “the Mother ship” and its $300+ million in revenue provide substantial financial backing and stability for iWay – making a iWay a secure vendor to partner with.
Today Information Builders is ranked among the top 50 software companies worldwide. Headquartered in New York City, we were recently given the honor of being the largest software company in Silicon Alley.
We are installed in 90 percent of the Fortune 100 companies and 80 percent of the Fortune In terms of who uses our software It is a who’s who of the largest and most innovative companies in the world:
Information Builders’ products are installed in 8 of the top ten telecommunications companies including Lucent, At&T, and Qwest.
We are installed at the top automobile manufacturers including General Motors, Ford, Volkswagen, Toyota, and Nissan.
Information Builders also represents the second largest software install at Microsoft, right behind SAP con-current users a day are leveraging a combination of our business intelligence and enterprise integration solutions to deliver reports, load pivot tables, and seamlessly access SAP R/3 and SQL Server.

3. SOA – The Missing Link? Where are we coming from?
The Monolithic Structure
CICS gateway
ORB
Message
Screen scrape
RPC
Down- load
file
Sockets
Message queue
APPC
Trans-
action
This is the way most back-office systems look today, whilst we have installed a lot of ERP and CRM packages in recent years many of our important systems are still data processing systems, they were not built to work the way the Business works and they are difficult and costly to replace.

4. SOA – The Missing Link? What is the Value Proposition?
SOA promises seamless collaboration of multiple information systems without regard for the nature of the technology or the incompatibilities that may exist between systems.
The SOA model is built to allow disparate systems to work together irrespective of what database system they use and what type of hardware they run on. The key words here are business process after 30 years of trying to make the user work the way the IT department found convenient we must now adapt our back-end systems to meet the needs of the business and we must do it quickly and cost effectively.

5. SOA – The Missing Link? What does the Business want?
The Business processes transactions – Contracts, Orders, Deliveries, Invoices, Payments etc.
They don’t want to wait a year while IT re-writes the mainframe invoicing system which has worked fine for the last 10 years.
They want to provide better Customer Service at lower cost
The Business needs to be agile – changing the service they offer to meet market demands
The Business wants to do just that – Business, but they don’t think in terms of which system they need, is it SAP or Peoplesoft? And does it run on the mainframe or on the NT server? The Business needs to answer customer queries, place orders and sign-up new customers, they also need to be able to add new services, quickly to compete and they don’t need IT telling them that it will take a year to set up the invoicing for the new “product suite” they want to introduce!

6. SOA – The Missing Link? One Adapter Layer for All Projects
By employing an adapter layer between the front-office systems that the Business uses and the back-office systems we can create a flexible layer between the two – and simply by adding new adapters or modifying existing ones business processes can be added or altered without changing either the front or back office systems
SOAP
JCA
JDBC
JMS MQ
ODBC
OLE DB WS WS
Application
Database
eBusiness
Legacy
Technology
API
API

7. SOA – The Missing Link? So what do we achieve?
Agile business systems can be created utilizing the information technologies companies already have in place, since no business can afford the time and expense of ripping out, replacing or rewriting every incompatible technology that impedes business agility.
Agility at low cost is the aim, it is both too time consuming and expensive to alter the back-end systems every time we wish to add a new process.

8. SOA – The Missing Link? What does the Business want?
Back Office Systems
Web
Portal
Order
Entry
Pay
Bill
Send
Goods
Swift
Adapter
Oracle
Peoplesoft
SAP
The users continue their attempts to learn more about what is going on in the business – both in terms of reporting or Business Intelligence and in terms of offering new services to both their customers and their suppliers.

9. SOA – The Missing Link? 250+ Intelligent Adapters
Adapter Classes
Data Adapters: Provide a relational view of proprietary databases and file systems
Application Adapters: e.g. SAP, Siebel, PeopleSoft, JDE
eBusiness Adapters: e.g. EDI, SWIFT, cXML, HIPAA
Transaction Adapters: e.g. CICS, IMS, Tuxedo
Emulation Adapters: e.g. 3270, 5250
Touchpoint Adapters: e.g. Bill of Materials, Chart of Accounts, Purchase Order, Sales Order, Work Order & more
Program Adapters: e.g. 3GL, 4GL, etc. A D P T E R S
Data
Application
Touchpoint
Program
Emulation
eBusiness
Transaction
Application System Adapters
Ariba
AXIS
Baan
BroadVision
Clarify
Commerce One
Hogan Financials
i2 Technologies
J.D. Edwards
Lawson
Manugistics
Microsoft CRM
MySAP.com
Oracle Applications
PeopleSoft
SAP Applications
Siebel
Vantive
Walker Interactive
e-Business Adapters
AS1/AS2
Comma-Delimited Files
cXML
ebXML
EDI-ANSI X12 (American)
EDI-EDIFACT
FIX
FIXML
Flat (positional) Files
HIPAA
HL7
ISO 15022
OAG BOD
Structured Files
SWIFT
SWIFTML
Transora
UCCnet
XBRL
xCBL
Data Adapters
Adabas
Adabas/C
ALLBASE/SQL
C-ISAM (Informix)
C-ISAM (Microfocus)
CA-Datacom
CA-IDMS/DB
CA-IDMS/SQL
Cloudscape
D-ISAM
DB2
DB2/400
DBASE
DBMS
EJB
ENSCRIBE
Essbase
Excel
Flat Files
FOCUS Data Access
Foxpro
IDS-II
ImageSQL
IMS
InfoMan
Informix
Ingres
Interplex
ISAM
KSAM
Lotus Notes
Microsoft Access
Microsoft OLAP Services
Microsoft SQL Server
Millennium
Model 204
MUMPS (Digital Standard MUMPS)
NOMAD
NonStop SQL
Nucleus
Omnidex
OpenIngres
Oracle
PROGRESS
QSAM
Rdb
Red Brick
RMS
SAP BW
SAP R/3
SQL/DS
SUPRA
Sybase
Sybase/IQ
System 2000
Teradata
TOTAL
TurboIMAGE
Unisys DMS 1100/2200
UNISYS DMS II
UniVerse
VSAM
XML
Transaction Processing
Adapters
Bull TDS
Bull TP8
CICS
IMS/TM
Software AG Natural
Tuxedo
Terminal Emulation Adapters
3270 (Mainframe, zSeries)
5250 (AS/400, iSeries)
Touchpoint Adapters
Analysis Codes
Bill of Material
Catalogs
Change Quality
Chart of Accounts
Component Issues
Container Move
Customer
Inventory
Item
Item Maintenance
Locations
Order Changes
Preliminary Invoices
Production Order
Purchase Order
Receipts
Requisition
Returns
Sales Order
Suppliers
Users
Work Order
Work Order Status Change
Technology Adapters
Any J2EE Application Server
BEA MessageQ
BEA WebLogic Application Server
BEA WebLogic Integration C
C++
cc:mail (VIM)
COBOL
COM
FOCUS
FORTRAN
FTP
Fujitsu Interstage
HTTP
IBM WebSphere Application Server
IBM WebSphere MQ (MQ Series)
IBM WebSphere MQ Integrator
Internet Mail (SMTP/MIME)
JacORB
Java
JMS
Lotus Notes (VIM)
Microsoft BizTalk Server
Microsoft Exchange (MAPI)
Oracle 9iAS
Oracle 9iAS Integration
Oracle AQ
Oracle PL/SQL
Orbix
Pascal
POP
Python
RDBMS
RPG
SAP eXchange Infrastructure (XI)
SAP Web Application Server
Sonic ESB
SonicMQ
SunONE Application Server
TIBCO JMS
TIBCO Rendezvous
Visibroker
Connector Technologies
.NET
ActiveX
iWay
JCA
JDBC™
Microsoft DTS
MQSeries
ODBC
OLE DB
SOAP
Access to your information assets can be broken down into groups or classes of adapters. Listed on this slide, are:
Data Adapters – which provide a relational view of any relational or non-relational data structures like DB2, Oracle, SQL Server, VSAM, IDMS, ADABAS, flat files, MUMPS and so much more.
Application Adapters provide transaction level access to the most popular ERP, CRM, and SCM packages like SAP, PeopleSoft, Siebel, and more.
Transaction Adapters provide fast and efficient access to TP environments like CICS, IMS/TM and Tuxedo.
Program Adapters allow organizations to leverage their existing libraries of custom written programs in COBOL, PL1, SQL RPCs and more.
Emulation Adapters deliver easy access to legacy green screen applications through screen-scraping technologies for 3270, 5250 and VT100 based applications.
e-Business Adapters represent the latest investment of research and development dollars from iWay Software. iWay’s new Adapter Factory has pumped out e-Business transaction adapters like SWIFT and FIX for the finance arena, HIPAA for healthcare industry, and Covisant for the Automotive industry.
No other EAI vendor can sole source as many adapters over more adapter classes as iWay Software. In fact, there isn’t even a vendor in the adapter business that can provide the coverage of iWay.
So how does everyone else bridge the gap between what iWay delivers and what they don’t?? Well, they ship an SDK – or software development kit. Hey, if you have to build your own access, test it and maintain it That’s not integration assembly. Your back into a integration solution steeped in custom development.

10. SOA – The Missing Link? Expect more from the adapter Layer
iWay Adapter Manager
Pre-processing
Client
Application
Template
selection
Transform
Agent
Listener (TCP,
SOAP, SAP XI,
JMS, MQ, etc.)
Transform
Agent
Transform
Agent
Adapters deal with the so called “fine-grained” processes, all the validations and transformations that are required bys a specific back-end system should be executed in the “fine-grained” adapter layer, the “business rules” which apply to all transactions and the routing of which processes are handled where are “coarse-grained” and should be handled by the broker layer.
Post-processing
Target
resource
One transformation template is selected based on the name of the first tag in the XML request document

11. SOA – The Missing Link? Universal Adaptive Framework
Here is the big picture of how iWay adapters provide plug-n-play connectivity to vital information sources. We call this big picture the iWay Universal Adapter Framework.
Mouse click 1 – The Universal Adapter Framework begins with iWay’s seven classes of adapters, which we discussed earlier. Here we introduce a bit more granularity, exposing capabilities like error handling and security, and validation, translation and transformation. Error handling, quite simply, is the process of communicating back to the calling application with error code and message reporting as revealed by the connected information asset. iWay adapters respect the O/S and information source security layers, passing credentials collected from the calling application to the operating system, data management and application security layers for proper user authentication. Exits are provided for implementing custom routines.
Validation, translation, and transformation may be process and adapter specific capabilities. Validation for example, is exemplified by the automatic parsing of a HIPAA claims document and the subsequent rejection of the record if a required field (e.g. claim date) is not populated. iWay vertical EDI adapters provide built-in validation where a public specification is available. Transformation is inherent for any information source reply set returned to a Web service. In this case, the reply must be transformed into XML to constitute a valid Web service message payload. Other forms of transformation, such as edit masking, date manipulation and other forms of message enrichment can be applied by invoking rules composed in iWay’s XML Transformation Workbench as an extension of the iWay adapter. For translation, the simplest example would be the EBCIDIC/ASCII character set conversion that is required when exchanging data between mainframe and non-mainframe computing environments.
Mouse click 2 – Metadata generation is a key differentiator for iWay. iWay provides several utilities to generate the metadata that defines each information asset. Metadata can be generated by reading the catalog of a relational DBMS, by interrogating a packaged application for it’s list of RPC’s via the iWay Application Explorer, by running COBOL FD’s thru a translator, or even by keying structure definitions by hand in our file tool. Once generated, the metadata becomes available to each client process thru the adapter that the client is conversing with. So important to note here, is the representation of metadata in XML form versus SQL form. This because the classic client/server approach stills needs a relational view (table/column view) of the world, while the newest generation of tools requires an XML view (XML structure file view) of information resources.
Mouse click 3 – Finally, we can add into the picture, packaged and custom applications, IT app dev and DW tools, desktop and business intelligence tools, application and web servers In general, anything needs connection to your information assets. The calling application, process or tool is configured for a certain type of connection and network protocol to communicate to an iWay Adapter. iWay supports many different connectivity options, from ODBC and JDBC, to JCA, to a variety of messaging systems, to SOAP for Web services-based integration. Further, iWay supplies architecturally sound plug-ins for popular integration tools like BEA, IBM MQSI, MS BizTalk Server and more. The plug-ins provide a direct connection to iWay adapters, greatly extending the inherent reach and range of the host product.
The path described from a connector thru to the data is known as an iWay Service Channel. The Service Channel represents a reusable pathway to the information asset described. For instance, once your VSAM parts table is described thru an iWay ODBC connector, it is available to any ODBC client. Introducing some more iWay terminology, any procedure or routine called through an iWay Service Channel and via Web Services, is known as an iWay Business Service (IBS).
Over 250+ Connectors and Adapters for integrating legacy databases and applications
Real time, transaction based integration

12. SOA – The Missing Link? EDIFACT/AS2 Adapter in a SAP XI Environment
The Adaptive Framework and the Broker at Philips Lighting
Fine-Grained and Coarse-Grained Services
Coarse-Grained
Fine-Grained
An example of SOA from Philips Lighting, the customers, on the right hand side, in this case Walmart, Auchan and Carrefour communicate with their supplier (Philips) only in terms of electronic documents either in an EDI format (in this case EDIFACT) or a XML format, all orders, queries, invoicing etc between these parties is done in this way. No paper and no people are involved. This is a requirement of doing business with these companies and as a supplier you either comply, as Philips has done, or they buy their goods elsewhere. In this case the fine-grained validation, i.e. the validation specific to matters such as security, message format etc is done by the iWay EDIFACT/AS2 adapter, only when the incoming message has been validated is it passed to the SAP broker, where credit checks and other “business” rules are carried out before the message which has now been changed to an SAP IDOC is passed on to SAP R3 for processing. Some of the messages have not yet been implemented in SAP XI for Philips own internal reasons and they are passed by the iWay adapter to a different broker, in this case Mercator, which then communicates with SAP. Processing these business transaction this way was implemented in a matter of days, setting up the architecture took longer but now that it’s there extra process can be added simply and quickly.

13. SOA – The Missing Link? Summary
The Business needs to be agile – offer new services quickly to meet market demands
SOA is about business, not just another IT solution.
Re-use of existing systems is not only possible – it’s relatively simple
You need an adaptive framework to access your existing systems
Be wary of “Adapter Development Kits”

14. Thank You !