Communication and Optimizing the OTM Integration Interface

2

ExternalSystemExternalSystem OTMOTM

Transmission

Transmission Ack/Transaction AckAssigned Transmission Number

Transmission Report

INBOUND

Handshake and Exchanging Pleasantries: Optimizing the Integration Interface

(based on the AckSpec element in the Transmission)

3

OTMOTM ExternalSystemExternalSystem

Transmission

Transmission Ack/Transaction Ack

Transmission Report

OUTBOUND


There are 4 primary xml documents defined:

1. Transmission: Primary document for both inbound and outboundprocesses. Each transmission contains mulitple transactions

2. TransmissionAck: Response message representing the receiptof the Transmission. Contains the assigned ReferenceTransmission number and an error if the Transmission was notcorrectly received.

3. TransmissionReport: This summarizes the errors detected whenthe transmission was processed. This is optional and only sent ifthe Transmission it is specified in the AckSpec element.

4. TransactionAck: Used inbound into OTM as anacknowledgement of Transactions posted outbound from thesystem.


Methods to post data to OTM:

1. HTTPOST2. Web Services3. Oracle Advanced Queueing (OAQ)4. Direct XML Insert5. Manual Upload


6

ExternalSystemExternalSystem

1: Authentication2: Splits Transactions3: Posts Transaction

Ack – Synchronous4: Validates Contents5: Pre-persist Event

Agents Triggered6: Persist Transactions7: Post-persist Event

Agents Triggered8: Posts Transmission

Report -Asynchronous

OTM





Report -Asynchronous

OTM

Transmission


Transmission Report

INBOUND



AckSpec:

Determines if a Transmission Report is sent:• ERROR = Flag to indicate to send the Transmission Report only

if there is an error• YES = Flag to indicate to always send the Transmission Report• NO = Flag to indicate not to send the Transmission Report

Property Setting:glog.integration.Transmission.Report=on error


8

1: Authentication2: Validates Contents3: Pre-persist EventTransmission Agents Triggered4: Persist Transactions5: Post-persist Event AgentsTriggered6. Transmission Object

1: Authentication2: Validates Contents3: Pre-persist EventTransmission Agents Triggered4: Persist Transactions5: Post-persist Event AgentsTriggered6. Transmission Object

External SystemExternal System

Transmission


Transmission Report

OUTBOUND



Triggers to Send Data Outbound:

• Agent Workflow• Workflow Notification• Process Manager – Send or Resend• Drop Down Actions from various Managers


Processing Outbound:

• Internal Java object classes populated• Converted to XML string• XSL Transformations are applied if configured• XML is then persisted in the I_TRANSMISSION table• External System utilized to post the XML• Status of the Transmission is updated


Transmission Inbound:


AckSpec element:

Specifies how the Transmission Report needs to be posted byOTM:


Communication Method InformationEMAIL EmailAddress, SmtpHost or

ContactGidHTTPPOST ServletURLQUEUE ContactGid

AckOption: YES, NO or ERROR

AckSpec element:


14

ExternalSystemExternalSystem





Report -Synchronous

OTM





Report -Synchronous

OTM

Transmission


Transmission Report

INBOUND





Message Class:InformationWarningError

Properties to modify TransmissionAck:


Property Value Description

glog.integration.servlet.TransmissionStageError.elementName

StackTrace Used to send theStackTrace instead ofthe TransmissionAck

glog.integration.servlet.TransmissionStageError.includeTransmissionText

true The full transmissionis posted back whenTrue

TransmissionReport element:


Communication and Optimizing the OTM Integration Interface

Technology

Transcript of Communication and Optimizing the OTM Integration Interface