introduction to the iway service manager design and transformation engine michael florkowsi...

Introduction to the iWay Service ManagerDesign and Transformation Engine

Michael FlorkowsiInformation Builders

Copyright 2007, Information Builders. Slide 2

Introduction

What is iWay? iWay Service Manager Components

iWay Service Manager iWay Explorer iWay Transformer iWay Designer

iWay Adapter Factory iWay SM Architecture


What is iWay?


Application Example

iWay Service Manager 5.5 SMiSM Components


iWay Components

iWay Service Manager (iSM) Host for Service-Oriented

Architecture Supports configuring iWay

Adapters of all types J2SE Environment (Server) Supports other iWay

Components iWay Transformer iWay Designer iWay Explorer


iWay Components

iWay Transformer Transforms XML and non-

XML documents into XML and non-XML documents

GUI mapping of source to target formats

Alternative to XSLT Extensible Document Enhancement


iWay Components

iWay Designer Performs complex stateless

process execution Synchronous/Asynchronous


iWay Components

iWay Explorer Allows exploration of EIS via

the adapter Creates XML Schemas for

Request/Response (Service) Creates XML Schemas for

Result (Event) Consistent view of all

Enterprise Systems


An adapter is a software component that exposes an application’s functionality and data to iWay Service Manager using open standards.

XML is the data format for the business level service.

iWay Adapters - What is an Adapter ?


Adapter Environments

iWay Adapters require only a J2SE environment. iWay Adapters are resold in several environments:

BEA WebLogic Server Oracle Fusion SAP Netweaver (XI)

iWay Adapters can be deployed under any J2EE compliant Application Server: JBOSS IBM WebSphere Many others


Adapter ClassesData Adapters: Provide a relational view of

proprietary databases and file systemsApplication Adapters: e.g. SAP, Siebel,

PeopleSoft, JDETransaction Adapters: e.g. CICS, IMS,

TuxedoTechnical Adapters: JMS, FTP, e-mail,

3GL, 4GL, etc.Emulation Adapters: e.g. 3270, 5250eBusiness Adapters: e.g. EDI, SWIFT,

cXML, HIPAA

Data Adapters

Adabas Adabas/C ALLBASE/SQLC-ISAM (Informix)C-ISAM (Microfocus)CA-DatacomCA-IDMS/DBCA-IDMS/SQLCloudscape D-ISAM DB2DB2/400 DBASE DBMS EJBENSCRIBE Essbase Excel Flat Files FOCUS Data Access Foxpro IDS-II ImageSQL IMSInfoManInformixIngresInterplex ISAM KSAM Lotus Notes Microsoft Access

Data Adapters

Microsoft OLAP Services Microsoft SQL ServerMillenniumModel 204MUMPS (Digital Standard MUMPS)NOMADNonStop SQL NucleusOmnidex OpenIngres OraclePROGRESSQSAM Rdb Red BrickRMS SAP BW SAP R/3SQL/DS SUPRASybaseSybase/IQ System 2000 TeradataTOTALTurboIMAGE Unisys DMS 1100/2200 UNISYS DMS IIUniVerseVSAMXML

Application System Adapters

AribaAXIS BaanBroadVisionClarifyCommerce OneHogan Financials i2 TechnologiesJ.D. EdwardsLawsonManugistics Microsoft CRM MySAP.comOracle ApplicationsPeopleSoftSAP ApplicationsSiebelVantiveWalker Interactive

e-Business Adapters

AS1/AS2 Comma-Delimited Files cXML ebXMLEDI-ANSI X12 (American)EDI-EDIFACTFIXFIXMLFlat (positional) Files HIPAAHL7ISO 15022OAG BODStructured Files SWIFTSWIFTMLTransora UCCnetXBRLxCBL

Transaction ProcessingAdapters

Bull TDSBull TP8CICS IMS/TMSoftware AG NaturalTuxedo

Terminal Emulation Adapters

3270 (Mainframe, zSeries)5250 (AS/400, iSeries)

Touchpoint Adapters

Analysis CodesBill of MaterialCatalogsChange QualityChart of AccountsComponent IssuesContainer MoveCustomerInventoryItemItem MaintenanceLocationsOrder ChangesPreliminary InvoicesProduction Order Purchase OrderReceiptsRequisitionReturnsSales OrderSuppliersUsersWork OrderWork Order Status Change

Technology Adapters

Any J2EE Application Server BEA MessageQ BEA WebLogic Application ServerBEA WebLogic IntegrationCC++cc:mail (VIM) COBOLCOMFOCUSFORTRANFTP Fujitsu Interstage HTTP IBM WebSphere Application ServerIBM WebSphere MQ (MQ Series) IBM WebSphere MQ IntegratorInternet Mail (SMTP/MIME) JacORB JavaJMS Lotus Notes (VIM) Microsoft BizTalk ServerMicrosoft Exchange (MAPI)

Technology Adapters

Oracle 9iASOracle 9iAS Integration Oracle AQ Oracle PL/SQLOrbix PascalPOPPythonRDBMS RPGSAP eXchange Infrastructure (XI)SAP Web Application ServerSonic ESB SonicMQ SunONE Application ServerTIBCO JMSTIBCO RendezvousVisibroker

Connector Technologies

.NET ActiveX iWay JCAJDBC™ Microsoft DTSMQSeries ODBC OLE DB SOAP

ADAPTERS

ADAPTERS Data

Application

Touchpoint

Technical

Emulation

eBusiness

Transaction

iWay Adapter Factory300+ Intelligent Adapters


Component with consistent set of XML and Java interfaces for Design Time and Run Time.

Through these Interfaces, iWAF provides: Design Time metadata browsing capability Web Service presentation JCA wrapping capability

iWay Adapters – iWAF (iWay Adapter Framework)


iWay Adapters are divided in 2 classes:

Event adapter, designed to publish information from the application.

Service adapter, designed to consume messages into application.

Adapter Classes


Event Adapters perform 3 functions: Trigger an “event” that occurs inside the running EIS and

extract data about the event from the EIS into the adapter.

Transform event data from the EIS-specific format to an XML document that conforms to the XML schema for the event. The XML schema is based on metadata in the EIS.

Propagate the event.

Adapter Classes - Event Adapters


Event-based integration: real-time, no rekeying and no errors

SAPClient

P.O.P.O.

SAPServer

IMSTransactions

Event detected

Message sent

Systems in sync

iWay Software - Events


Service Adapters perform 3 functions: Process the XML Request into the EIS specific data

format. Invoke the underlying function in the EIS and wait for its

response. Transform the response from the EIS specific data format

to an XML document that conforms to the response XML schema for the service. The response XML schema is based on metadata in the EIS.

Adapter Classes - Service Adapters


Service-based integration: real-time, no rekeying and no errors

Applicationuser

ApplicationServer

SAPServer

Service requested

Service fulfilled

RequestLookup

iWay Software - Service

iWay Service Manager 5.5 SMArchitecture


What is an iWay Channel

Easily configurable constructs for: accessing applications applying transformations (pre-emit & post-emit) receiving or emitting documents

Channels help organize how you design components and then deploy them for execution.


3 Phases of a Channel

Every Channel consists of an Inlet, Route and Outlet


iWay Service Manager -Channels

Users will assemble conduits called Channels easily configurable components for accessing application, applying

transformation, receiving or emitting documents into complete These channels define a complete integration operation: receipt of inputs,

service processing and transmission of outputs using any supported protocol

Channels contain references to Inlets, Routes and Outlets


iWay Service Manager -Inlets

Inlets defines how a message enters the channel.Each channel contains exactly one Inlet. In the Inlet, the message may be decrypted and or preparsed

(turned into XML) and then assigned to a route for further processing.

Each inlet contains a sequence of components defined as follows:

Listener ==> Decryptor ==> Preparser


iWay Service Manager -Listeners

Listeners are components that monitor communication protocols waiting for input documents or messages.

A listener can be defined for the following protocols:

Protocol Name

Description

AQ Oracle AQ queues exchange documents

AS1 AS/1 protocol

AS2 AS/2 protocol

CS3 A TCP port is monitored for traffic in iWay’s CS3 protocol

EMAIL iAM acts as an email client to a designated email system to retrieve messages sent to that system

File A file or subdirectory of files is monitored for documents

FTP Requests and responses are exchanged with an FTP server

FTPD FTP Daemon – iAM operates as an FTP server so that clients can send documents directly to it.

HTTP Receives a request from a browser client, adding a security layer

Internal

JMSQ Java Messaging queues exchange documents

MQ IBM MQSeries queues and queue managers exchange documents

MQJMS


iWay Service Manager -Listeners

Listener Types (Continued)Protocol

NameDescription

MQSI Documents are exchanged with iWay nodes operating in an IBM WMQI message flow

MSMQ

RDBMS Data is automatically retrieved from any JDBC data source table using an SQL query

Relay A special purpose listener is used with WebSphere MQ for remote data access from another instance of iAM working with WMQI

SAP A special-purpose listener receives an Idoc from an SAP R/3 system

Schedule Triggers a custom agent to be executed at a regular interval to perform the required operations

SOAP Receives requests containing Stored Procedure calls using Simple Object Access Protocol (SOAP)

Sonic SonicMQ queues exchange documents

TCP A TCP port is monitored for the arrival of a document

Tibrv Exchanges messages with TIBCO Rendezvous


iWay Service Manager - Routes

A Route is defined as a path the message takes thru the Channel.

Each Channel must make reference to one or more routes. Along each route transformations and business logic are

applied to the message.Routes contain references to Transformers, Processes and Outlets. A Route describes the path that a document takes during its passage through the system. It is the job of the inlet to convert the input message to a process able document.


iWay Service Manager – Outlets

An Outlet determines how a message leaves a Channel. Each Channel contains one or more outlets. In the outlet, the message maybe transformed or encrypted

and finally emitted by the system. It is important to note that each message may pass thru

multiple outlets of a channel.

Outets contain references to Preemitters, Encryptors and Emitters. Once a document has been processed, it must be sent on to one or more designated recipients. This is the job of the outlet. The outlet is responsible for all aspects of preparing the document for emission and then emitting it.


iWay Service Manager – Build/Deploy/Start

Create a Channel Add an Inlet to the Channel.

Create and Add a Listener to the Inlet. Add a Route to the Channel.

Add a Transform to the Route.Add a Process Flow to the Route.

Add an Outlet to the Channel.Build the Channel – create the Channel Archive file.Deploy the Channel to iSM.Start the Channel.


Build a Channel

Building a Channel creates an Archive (.car) file. This file is used to deploy to iSM.


Deploy and Start a Channel

The Channel Archive must be deployed to the iSM ServerThe Channel is started, initiating the Listener Protocol.


Deploying Services To The Runtime

RuntimeEngineRegistry

Deployment: Build from Registry, Deploy to Engine

Business Service Provider

Graphical Workbench

ApplicationExplorer

Designer Transformer Partner

Agreements

iWay Service Manager: Enterprise Service Bus


Example of a Channel

Channel PurchaseOrder

PurchaseOrder Inlet

PurchaseOrder Route

PurchaseOrder Outlet

PurchaseOrder File Listener

PurchaseOrder Process Flow

Default.outlet

PurchaseOrder

PurchaseOrderReq

JDBC Service

PurchaseOrder2

File Emitters


Review

Discuss the iWay Service Manager Understand the architectureExamine the iWay Service Manager components and toolsNext: Demo iSM, Designer, and Transformer

introduction to the iway service manager design and transformation engine michael florkowsi...

Documents

iway components iway

iway components iway

iway service manager

ebusiness adapters

emulation adapters

adapter classes data

tuxedo technical adapters

jde transaction adapters