IEEM 5352
Download
1 / 49

EDI Standard and Tool - 2 - PowerPoint PPT Presentation


  • 74 Views
  • Uploaded on

IEEM 5352 Enterprise Integration. EDI Standard and Tool - 2. Interchange Envelop ( EDI Document Format). ISA (Interchange Group Start). GS (Functional Group Start). ST (Transaction Set Start). Detailed Segment (with Data Elements). SE (Transaction Set End). GE (Functional Group End).

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' EDI Standard and Tool - 2' - hanley


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

IEEM 5352Enterprise Integration

EDI Standard and Tool - 2


Interchange envelop edi document format
Interchange Envelop(EDI Document Format)

ISA (Interchange Group Start)

GS (Functional Group Start)

ST (Transaction Set Start)

Detailed Segment (with Data Elements)

SE (Transaction Set End)

GE (Functional Group End)

IEA (Interchange Group End)


Transaction set message structure
Transaction Set / Message Structure

ST

Transaction Sets/ Messages

Segments

Composite Elements

Elements

Element Codes


Edi ex tender architecture
EDI EX*tender - Architecture

  • EDI Overview

  • The View from 50,000 ft

  • Client/Server Communication

  • The EX*tender Mailbox

  • Any to Any Translation

  • System Auditing

  • Application Integration


Trading

Partners

SAP

C

O

M

P

A

N

Y

PeopleSoft

Oracle Apps


Trading

Partners

Company

SAP

E

R

P

EDI

Format

PeopleSoft

Oracle Apps


VAN

Trading

Partners

Company

TP-1

E

R

P

EDI

Format

TP-2

TP-3


Ex tender server from 50 000 feet
EX*tender Server from50,000 Feet


Company

EDI EX*tender

T

R

A

N

S

L

A

T

O

R

E

R

P

Inbound

Native

Format

(udf)

EDI

Format

Outbound


VAN

Trading

Partners

Company

xlate

TP-1

T

R

A

N

S

L

A

T

O

R

E

R

P

TP-2

TP-3

xlate


Oracle Apps Environment

EDI EX*tender

T

R

A

N

S

L

A

T

O

R

EDIGateway

(PO)

Outbound

O

R

A

C

L

E

UDF/

FF

EDI

Inbound

(INV)


High level architecture
High Level Architecture

EX*tender

in bound

mbox

server

mgr

server

out bound

com

server


High level architecture1
High Level Architecture

EX*tender

Translator

edi_dbms

Mailbox:

../mbox/TP1/inedi

../mbox/TP2/inedi

../mbox/TP3/inedi

UNIX File System

../db

../script

../log

client

Database


Edi ex tender

EDI EX*tender

Client/Server Communication


Client server communication
Client/Server Communication

  • Allows Server (translator) to be controlled by Client

    • Start and stop the translation engine

    • Change the number of running translator processes

    • Collect performance data

  • Communication via SQL*Net and Oracle DBMS_PIPE

  • Facilitated by UNIX server process (edi_dbms)

  • Edi_dbms services called through PL/SQL API

    • edia - administrative functions (restricted)

    • ediu - user functions (unrestricted)

    • edic - contains functions common to edia and ediu


  • SQL*Net

    Insert Monitor Data

    Oracle RDBMS

    EDI Engine

    IPC

    Delta Monitor

    Monitor Tables

    dbms_alert

    Start/Stop

    Start/Stop

    Client

    Monitor

    Change Number

    of Servers

    OS

    dbms_pipe

    dbms_pipe

    PL/SQL

    API

    Stop Engine

    System Call

    Start Engine

    /TP1

    /inedi

    /inff

    /out

    /TP2

    /inedi

    /inff

    /out

    OS Validations

    File System

    (Mailbox)

    edi_dbms


    Ediu api s
    EDIU API’s

    For details see document: Technical Reference.doc

    • create_mbox - create TP mailbox

    • submit_hostfile - submit file for translation

    • IsEngineRunning - check if translator is running

    • ScriptExists - check if mapping script exists

    • DirectoryExists - check if directory exists

    • create_directory - create directory

    • get_number_of_servers - get number of translators running

    • AnybodyHome - check if edi_dbms is responding

    • get_engine_status - get status of all translator processes

    • FixDM - used if delta monitor ends abnormally


    Edia api s
    EDIA API’s

    For details see document: Technical Reference.doc

    • shutdown - shutdown the translator

    • refresh_dictionary - used when dictionary is added

    • shutdown_audit - shutdown audit process

    • configure - part of setup process

    • adjust_audit_flags - changes audit data written to DB

    • start_engine - starts the translator

    • stop_engine - stops the translator

    • change_number_of_servers - changes the number of server processes

    • start_audit - starts the audit process

    • start_com - starts the outbound device process

    • start_delta_monitor - starts the performance monitor

    • stop_delta_monitor - stops the performance monitor


    Edi ex tender1

    EDI EX*tender

    The Mailbox


    Edi ex tender mailbox
    EDI EX*tender Mailbox

    • Each Trading Partner has a mailbox

    • Implemented as directories in the file system

      • inedi - for edi documents translatation

      • inff - for user defined file (UDF) translation

      • out - default destination for translated documents

    • More than one mailbox root is possible (mbox_aliases)

      • default is $EDIPATH/mbox

    • Mailbox supported by edi_mbox

    • Documents in ../inedi and ../inff are automatically submitted to the translator by edi_mbox

    • Automatic submission controlled by MBOX_SCAN_???

      • see configuration file, $EDIPATH/.edirc

    • Mailbox also interacts with edicopy and ‘scan’ command of console application


    TP1

    /inedi

    /inff

    /out

    Translation

    Engine

    TP2

    /inedi

    /inff

    /out

    TP3

    /inedi

    /inff

    /out

    TP4

    /inedi

    /inff

    /out

    Mailbox Root

    EDI EX*tender

    $EDIPATH/mbox/

    EDI-FF (TP1 to TP3)

    FF-EDI (TP1 to TP3)


    EDI EX*tender

    BUYER

    /inedi

    /inff

    /out

    Oracle

    Apps

    Translation

    Engine

    POO

    EDI

    Gateway

    ASNI

    ASNI

    SELLER

    /inedi

    /inff

    /out

    X.12 850

    Outbound

    Device

    Seller’s

    Organization

    X.12 856

    VAN

    X.12 850


    Edi ex tender mailbox1
    EDI EX*tender Mailbox

    • Which Trading Partner Owns EX*tender?


    Ex tender server
    EX*tender Server

    Any to Any Translation


    EDI EX*tender

    Optional

    Pre-process

    (script)

    Mailbox

    Translate

    (script)

    De-group

    To Mailbox

    Re-group

    Optional

    Post-process

    (script)

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    EDI EX*tender

    edi_manager

    edi_mbox

    edi_server

    To Mailbox

    edi-com

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    EDI EX*tender

    edi-mbox

    edi-mbox

    edi_manager

    edi_server

    mbox1/TP1/inedi

    /inff

    /out

    /TP2/inedi

    /inff

    /out

    ...

    mbox2/TP3/inedi

    /inff

    /out

    ...

    mboxn/TPn/indedi

    /inff

    /out

    To Mailbox

    edi-com

    To Mailbox

    Send to TP

    • Recipient

    Pick up from mailbox


    EDI EX*tender

    edi_manager

    edi_mbox

    edi_server

    To Mailbox

    edi-com

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    EDI EX*tender

    edi-manager

    edi-mbox

    edi_manager

    UDF/FF

    Message Queue

    .

    .

    .

    $$$MSGSTART

    edi_server

    T

    r

    a

    n

    s

    l

    a

    t

    e

    EDI

    To Mailbox

    ST/SE

    or

    edi-com

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    EDI EX*tender

    edi_manager

    edi_mbox

    edi_server

    To Mailbox

    edi-com

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    EDI EX*tender

    edi-mbox

    edi_manager

    edi_server

    UDF/FF Translation

    Memory

    edi_server

    To Mailbox

    EDI

    Message

    Flat File

    Message

    scan script

    map script

    edi-com

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    EDI EX*tender

    edi_manager

    edi_mbox

    edi_server

    To Mailbox

    edi-com

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    EDI EX*tender

    edi-mbox

    edi_manager

    edi_server

    EDI Translation

    Memory

    edi_server

    To Mailbox

    Flat File

    Message

    EDI

    Message

    (Automatic

    memory population)

    map script

    EDI Dictionary

    consulted

    edi-com

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    EDI EX*tender

    edi_manager

    edi_mbox

    edi_server

    To Mailbox

    edi-com

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    EDI EX*tender

    edi_mbox

    edi_manager

    edi_com

    • optional translator component

    • provides event driven and scheduled svc

    • provides communication services

    • used to extend translator capabilities

    • interface to database, email, fax, etc

    edi_server

    To Mailbox

    edi-com

    To Mailbox

    Send to TP

    Recipient

    Pick up from mailbox


    SQL*Net

    /TP1

    /inedi

    /inff

    /out

    /TP2

    /inedi

    /inff

    /out

    edi_mbox

    edi_audit

    edi_mbox

    edi_mbox

    File

    Audit Tables

    edi_logger

    Forms

    Client

    edi_manager

    Setup Tables

    Message Queue

    edi_server

    edi_server

    Monitor Tables

    In Bound

    Asynch

    X.25

    TCP/IP

    Bisynch

    Disk

    edi_com

    Out Bound


    Edi ex tender2

    EDI EX*tender

    System Audit


    Ex tender auditing
    EX*tender Auditing

    • Audit tracks all actions performed by EX*tender

    • All translator processes communicate with edi_logger

    • Each file passing through the translator is assigned a ‘session’ number

    • Each audit record identifies a particular session

      • except for system level audit records which are associated with translator start session

  • Audit records are perodically written to the database by edi_audit

  • During idle times, edi_audit summarizes session activity


  • idle time move

    $EDIPATH/log/edi_answer_log

    $EDIPATH/log/edi_answer_log.old

    edi_mbox

    write

    read

    edi_manager

    Database

    edi_server

    IPC

    insert

    edi_logger

    edi_audit

    edi_audit

    edi_com

    move

    sndevtlog

    parse

    snderrlog

    $EDIPATH/log/edi_answer_log.old.xyz

    * Error: audit needs recovery


    Edi ex tender3

    EDI EX*tender

    Application Integration


    Edi ex tender application integration
    EDI EX*tender Application Integration

    • Implemented by an Outbound Device

    • Outbound Devices are managed by edi_com

    • There are four types of Outbound Devices

      • Scheduled

      • Scheduled, Event Driven

      • Periodic

      • Periodic, Event Driven

  • Outbound Devices are cached by edi_com when EX*tender is started

  • An Outbound Device is an interface to the Operating System via a Shell Script


  • Scheduled outbound device
    Scheduled Outbound Device

    • Similar to UNIX cron process

    • Can specify up to 4 times the device should execute

    • Can specify the period (in days) the device should execute

      • Period = 0 means execute daily

      • Period = 1 means execute every other day

    • When a device is marked as event driven it will execute

      • only if it has been the destination of a translation

    • When a device is not event driven it will

      • unconditionally execute at its scheduled time


    Periodic outbound device
    Periodic Outbound Device

    • Also similar to UNIX cron process

    • Specify a period in days and minutes

    • Device will execute when the period expires

    • When a device is marked as event drivenit will execute

      • only if it has been the destination of a translation

    • When a device is not event driven it will

      • unconditionally execute when the period expires

    • A special case, an event driven periodic device with

      • Period = 0 days, 0 minutes

      • Executes immediately after message is translated

        • Watch out for gotcha!!


    Outbound device specifics
    Outbound Device Specifics

    • An Outbound Device is a UNIX shell script

    • The script must be in $EDIPATH/script

    • The script is named according to the Outbound Device

      • If device is named: 810out then

      • shell script is named: $EDIPATH/script/810out.com

  • Data translated to the device is written to the file:

    • $EDIPATH/tmp/com/810out.lhot

  • When device executes the data file is renamed to:

    • $EDIPATH/tmp/810out.dat

    • This is the file that an event driven device processes


  • Event driven outbound device
    Event Driven Outbound Device

    • For an Outbound Device called 810out

      • Device is executed only if $EDIPATH/tmp/com/810out.lhot exists

      • Messages translated to 810out will be appended to 810out.lhot

      • Just before executing the outbound device

        • 810out.lhot is moved/appended to $EDIPATH/tmp/810out.dat

      • After processing the data file, the outbound device must delete the file to prevent the data from being processed again


    Scheduled outbound device1
    Scheduled Outbound Device

    Unconditionally

    executes daily

    Executes at Midnight

    and 12 noon

    Not Event Driven


    Periodic outbound device1
    Periodic Outbound Device

    Periodic

    Outbound Device

    Executes each time a file

    is translated to this device

    Event Driven


    Outbound device usage in translation
    Outbound Device Usage in Translation

    Executes each time a file

    is translated to this device

    Outbound Device


    Event Driven Outbound Device (810out)

    $EDIPATH/tmp

    $EDIPATH/tmp/com

    1

    810out.dat

    translator

    810out.lhot

    process

    move

    2

    (move)

    4

    3

    edi_com

    $EDIPATH/script/810out.com

    execute

    1.Documents translated to Outbound Device 810out are written to 810out.lhot

    When its time to execute the outbound device:

    2. edi_com moves/appends 810out.lhot to $EDIPATH/tmp/810out.dat

    3. if $EDIPATH/tmp/810out.dat exists then 810out.com is executed by edi_com

    4. 810out.com process the translated data and deletes the file when finished


    ad