OTM Integration Options - otmsig.com€¦ · OTM Integration Options OTM Integration Overview OTM...

1 Copyright © Capgemini 2012. All Rights Reserved

OTM Integration Options


Deepak Khemani ; Rachana Junwa

July 29, 2013



Agenda

Overview of Integration Mechanisms

Integration Scenario

Integration Approach using Oracle Advance Queue

Inbound Integration using Direct XML

Data Queues

Q & A



OTM Integration Overview

OTM uses XML messages to integrate with external applications through several interfaces

OTM Interface Types are classified as Data Load, Transport Flow, Financial and Miscellaneous

OTM XML schema defines the data elements that OTM sends or receives for each type of interface

Integration approach can vary from Manual to Point to Point, to a Hub / bus model using a middleware



OTM Inbound Integration Options

HTTP Post

Provides mechanism to send Inbound Transmission to OTM on the web server using servlet: WMServlet, DirLoadServlet, TransformerServlet

WebService Call

Provides a mechanism to send Inbound Transmission XMLs to OTM via web service to the application: IntXmlService

Direct XML Insert

Inbound Transmission XML are inserted directly into the DB via PL/SQL and are processed using an internal Integration Data Queue

Oracle Advance Queues

Advanced Queuing provides database-integrated message queuing functionality



OTM Outbound Integration Options

HTTP Post

Outbound Transmission are sent to other systems/middleware via configuring the HTTP Post details in OTM external system

WebService Call

Outbound Transmission are sent to other systems/middleware via configuring the WSDL details in OTM external system

FTP

Outbound Transmission are sent to other systems/middleware via configuring the FTP details in OTM external system

Oracle Advance Queues

Advanced Queuing provides database-integrated message queuing functionality



Integration Scenario

ER

P \ L

eg

ac

y A

pp

lica

tio

ns

Tra

din

g P

artn

ers

Inte

gra

tion

Layer

Inte

gra

tion

Layer

ED

I VA

N

Delivery /

Release

Purchase

Order

Location

Master

Trip/

Shipment

Location

Trans

Order

Order

Release

Planned

Shipment

Tender

Offer

Tender

Response

Shipment

Status

Invoice

EDI 204

EDI 990

EDI 214

EDI 210

Master

Data

Order

Management

Shipment

Planning

Shipment

Execution

Visibility

Freight

Settlement



Integration Challenges

Handle real time and batch mode of transactions

Robust and reliable integration mechanism to ensure delivery of transactions

Mechanism to control Volume and Priority of transactions coming into OTM

Manage transaction processing during Middleware and OTM downtime

Exception handling and recovery



Integration using Oracle Advanced Queues

Database message queuing mechanism where producer applications en-queues and consumer applications de-queues messages

Provides a asynchronous mechanism for sending and receiving XML transmissions to/from OTM

Guaranteed message delivery provided by a persistent message queue

Bypasses Web / App layer for message exchange

Retry and data retention time can be setup as per need



Oracle Advanced Queues in OTM

Inbound

Inbound flow requires following queues Inbound Queue XML Topic Queue (XML Stage Queue) Ack Queue Exception Queue Query Reply AQ (For Remote Query transactions).

Database listener needs to be created in order to process the XMLs

Application Server listener/thread needs to be enabled to process the messages in the “XML Topic Queue”

Outbound

Multiple Outbound queues can be created for the outbound interfaces.

Outbound Queues are specified in the External System.



Oracle Advanced Queues in OTM



Exception Handling – Inbound OAQ

Middleware unable to en-queue

Cause: OTM database is down or not reachable

Recovery: Middleware sends notifications

Invalid payload

Cause: XML is invalid

Recovery: Middleware listens to exception queue and sends notification

OTM unable to process messages

Cause: Inbound OAQ listener is down.

Recovery: DBA monitors the AQ listener. Restart inbound listener

Transmissions errors in OTM

Cause: Incorrect master data

Recovery: Agents can be configured to send Transmission failure. Notifications can be dispatched to concerned parties for investigation.



Exception Handling – Outbound OAQ

OTM is unable to en-queue

Cause: OTM Outbound Queue is down

Recovery: Agents can be configured to send Transmission failure notification to concerned parties to investigate and re-start the Queue.

Middleware unable to de-queue

Cause: OTM database is not reachable

Recovery: Consuming middleware or application sends notification



Integration using Direct XML Insert

Inbound XMLs are inserted directly into the DB via PL/SQL

pkg_integration_util package.insert_transmission

Procedure stores XML in Transmission table and returns Transmission number to caller

Process uses OTM Data Queue concept for populating Transaction table data and publishing New XML topic

Direct XML allows the Data Queue name to be passed as an input thus providing the ability to direct XML messages into separately controlled groups

Event priority is also an input in Direct XML signature allowing control of sequencing of events through Data Queue



Exception Handling – Direct XML

Middleware unable to post transactions

Cause: OTM database is down or not reachable

Recovery: Middleware sends notifications

Invalid payload

Cause: XML is invalid

Recovery: The posted transaction would appear as ‘FAILED’ in integration data queues. Within OTM, the transaction would stay in ‘STAGED’ status. Manual Investigation would be required for resolution.

Transmissions errors in OTM

Cause: Incorrect master data

Recovery: Agents can be configured to send Transmission failure notification to concerned parties for investigation.



OTM Data Queues

OTM Data Queues are database resident queues that can be used to control application server workload

Processes for Inbound and Outbound Integration can be configured to use the Data Queues

The mechanism allows configuration of Poller threads that can retrieve a configurable number of events at a configurable time interval

The Executor publishes a New XML topic which is processed as normal in-memory event queues



OTM Data Queues

Transactions hit the application

server in-memory event queues,

creating backlog and competing with

other internal applications server

processes for resources and

process time

Poller threads can be configured

to stage transactions and process

a specific number of transactions

in a particular interval


OTM Integration Options 4

©

Data Queue Definition comprise :

Custom Data Queue Poller

Executor definition can be defined as per the need.

OTM Data Queues Setup



©

Recap

Oracle Advanced Queue and DB XML insert provides database centric mechanism to interface

Choosing between OAQ or Direct XML comes down to volume / performance / tool use

OAQ will have more overhead on the database, but uses a standard Oracle database feature

In either case, Data Queue provides a mechanism to throttle and to have better control on the volume pushed to application server event queues

OTM Integration Options - otmsig.com€¦ · OTM Integration Options OTM Integration Overview OTM...

Documents

Transcript of OTM Integration Options - otmsig.com€¦ · OTM Integration Options OTM Integration Overview OTM...