Design and Transformation Engine

egyptiannorweiganInternet and Web Development

Oct 31, 2013 (3 years and 5 months ago)

62 views

Introduction to the iWay Service Manager

Design and Transformation Engine

Michael Florkowsi

Information 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





Copyright 2007, Information Builders. Slide
3

What is iWay?

Copyright 2007, Information Builders. Slide
4

Application Example


iWay Service Manager 5.5 SM

iSM Components


Copyright 2007, Information Builders. Slide
6

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


Copyright 2007, Information Builders. Slide
7

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


Copyright 2007, Information Builders. Slide
8

iWay Components


iWay Designer


Performs complex stateless
process execution


Synchronous/Asynchronous

Copyright 2007, Information Builders. Slide
9

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


Copyright 2007, Information Builders. Slide
10



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 ?

Copyright 2007, Information Builders. Slide
11

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


Copyright 2007, Information Builders. Slide
12

Adapter Classes


Data Adapters
:

Provide a relational view
of proprietary databases and file systems


Application Adapters
:

e.g.

SAP, Siebel,
PeopleSoft, JDE


Transaction Adapters
: e.g.

CICS, IMS,
Tuxedo


Technical Adapters
:
JMS, FTP, e
-
mail,

3GL, 4GL, etc.


Emulation Adapters
:

e.g.

3270, 5250


eBusiness Adapters
:

e.g.

EDI, SWIFT,
cXML,

HIPAA

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


Data Adapters


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


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

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)

Technology Adapters


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

A

D

A

P

T

E

R

S

Data

Application

Touchpoint

Technical

Emulation

eBusiness

Transaction

iWay Adapter Factory

300+ Intelligent Adapters

Copyright 2007, Information Builders. Slide
13


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)

Copyright 2007, Information Builders. Slide
14



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

Copyright 2007, Information Builders. Slide
15


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

Copyright 2007, Information Builders. Slide
16

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


SAP

Client

P.O.

P.O.

SAP

Server

IMS

Transactions

Event detected

Message sent

Systems in sync

iWay Software
-

Events



Copyright 2007, Information Builders. Slide
17


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

Copyright 2007, Information Builders. Slide
18

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

Application

user

Application

Server

SAP

Server

Service requested

Service fulfilled

Request

Lookup



iWay Software
-

Service

iWay Service Manager 5.5 SM

Architecture


Copyright 2007, Information Builders. Slide
20

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.

Copyright 2007, Information Builders. Slide
21

3 Phases of a Channel


Every Channel consists of an Inlet, Route and Outlet


Copyright 2007, Information Builders. Slide
22

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


Copyright 2007, Information Builders. Slide
23

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

Copyright 2007, Information Builders. Slide
24

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

Copyright 2007, Information Builders. Slide
25

iWay Service Manager
-
Listeners


Listener Types (Continued)

Protocol
Name

Description

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

Copyright 2007, Information Builders. Slide
26

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.

Copyright 2007, Information Builders. Slide
27

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
.

Copyright 2007, Information Builders. Slide
28

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.

Copyright 2007, Information Builders. Slide
29

Build a Channel


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


Copyright 2007, Information Builders. Slide
30

Deploy and Start a Channel


The Channel Archive must be deployed to the iSM Server


The Channel is started, initiating the Listener Protocol.

Copyright 2007, Information Builders. Slide
31

Deploying Services To The Runtime

Runtime

Engine

Registry

Deployment: Build from Registry, Deploy to Engine

Business Service Provider

Graphical Workbench


Application

Explorer


Designer


Transformer


Partner

Agreements

iWay Service Manager
: Enterprise Service Bus

Copyright 2007, Information Builders. Slide
32

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


Copyright 2007, Information Builders. Slide
33

Review



Discuss the iWay Service Manager


Understand the architecture


Examine the iWay Service Manager components and tools


Next: Demo iSM, Designer, and Transformer