customer case - oracle b2b critical mission hub

Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |

ORACLE SOA/B2BAs a Critical Mission Hub for High Volume Message

Lonneke Dikmans & Bruno Neves Alves


PROGRAM AGENDA

About us

The Use Case

Product Selection

Architecture

Oracle B2B 12c – What’s New

Demo

Conclusion

1

2

3

4

5

2

6

7


Lonneke Dikmans

Consultant and Managing partner at eProseed

Specializing in SOA and BPM

Oracle Ace Director

Bruno Neves Alves

Partner and Technical Director at eProseed UK

Oracle Middleware Consultant

3

ABOUT US


PROGRAM AGENDA

About us

The Use Case

Product Selection

Architecture


Demo

Conclusion

1

2

3

4

5

4

6

7


• Build a cargo hub consolidating 3 legacy solutions for message brokerage

• Interconnect >15.000 Air Cargo Trading Partners

• Process 3 Billion/msg year in multiple formats and protocols

• Reduce time-to-market for customer on-boarding

• Standardization

• Empower of business users to produce document definition rules and mappings

5

THE USE CASE

Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |6

>15.000 trading partners

238 document

types

Market Stand

XML

EDI

Flat Files

Custom

99 envelope

types

476 conversionmappings

8 channel

protocols

SMTP

FTP File

MQ

SOAP

HTTP

TCP

JMS

768 business

rules

3 Billions

B2B messages

year

0message

lost


PROGRAM AGENDA

About us

The Use Case

Product Selection

Architecture


Demo

Conclusion

1

2

3

4

5

7

6

7


10 REASONS . WHY ORACLE B2B

1Pit Stop for Trading Partner,

Document, Channels and

Agreements configuration

2Multiple Document Protocol

Support

4Document Definition Tools

Available

7Multiple Transport Protocols

Support

3Document Translation, Validation

and Construction

6Oracle SOA Suite Native

Integration

10E2E Message Monitoring and

Auditing

8 Self Service Provisioning

5Multiple Envelope Protocols

Support

9 Document Batching and Splitting

Support


WHAT ABOUT ORACLE SOA SUITE – SCA?

• Composite layer for:

– Integration with B2B

– Orchestration

– Routing

– Acknowledge

– Mapping for message normalization

– Enrichment

– Store and forward

– Integration with legacy systems

– Exception Handling

9


PROGRAM AGENDA

About us

The Use Case

Product Selection

Architecture


Demo

Conclusion

1

2

3

4

5

10

6

7


Inbound processing Core processing Outbound Processing

B2B SOA SCA

B2B

ADAPTER

Business Validation

Dynamic RoutingOracle Business Rules

Duplication

Normalization

Acknowledge

Message Deferring

Auditing

E2E Tracking + BAM Monitoring

Rejection

Conversion

B2B

ADAPTER

Document Identification

Document Parsing

Document Validation

Exception Handling

Batching

B2B

Scheduling

Document Construction

Document Validation

Correlation

Trading Partner

IdentificationSMTP

FTP

File

JMS

SOAP

HTTP

TCP

JMS

SMTP

FTP

File

JMS

SOAP

HTTP

TCP

JMS

Batching

Oracle Document Editor

Custom Document Editor

jDeveloper

• Oracle B2B 11g

• Oracle BPEL 11g

• Oracle Mediator 11g

• Oracle Business Rules 11g

• Oracle Business Activity Monitoring 11g

• Oracle Cloud Control 12c


Message Handling

and Routing

Envelope IdentificationValidationand Parsing

EnvelopeConstruction andValidation

MESSAGE PROCESSING

12

DocumentValidationandParsing

AgreementIdentification

DocumentIdentification

Sender and RecipientIdentification

Document Lifecycle

Inbound processing Core processing Outbound Processing

AgreementIdentification

DocumentIdentification

Sender and RecipientIdentification

Document Constructionand Validation

Message Handling and Routing

• Document Handling Orchestration

– Rejection

– Enrichment

– Business Validation

– Deferring

– Duplication

– others

• Document Routing

– Downgrade/Upgrade – Versions

• Canonicalization/Normalization

– Document Protocol Conversion

– Envelope Conversion

– Envelope Enrichment

– others

SE

ND

ER

RE

CIP

IEN

T


SOLUTION ARCHITECTURE


CUSTOM DOCUMENT FRAMEWORK

• Added by patch and later included in 12c

• Associate custom java classes to document types – document callout

• Parsing and validation capabilities

• Passage between channel callout and document callout

• Possibility to cope with batch documents

• Shared B2B exception handling

14


DEPLOYMENT ARCHITECTURE

• High availability clustering

• Two domains (A and B) allowing hot switch to guarantee no down time during patches and upgrades

• Simplified switch using B2B trading partners listening channels and traffic director for http/ws integration

• High availability 24/7/52

• SOA and B2B Server sharing the same SOA Servers – allow in memory integration


PERFORMANCE, ACHIEVED

• All features on top of SOA Infra DB

– Reduced dehydration

• One-way-delivery message exchange pattern w/o dehydration points

• One-way-delivery property set to sync

• In memory B2B-SOA integration

• Use of JMS Queue as Default instead of AQ for B2B_IN_QUEUE and B2B_OUT_QUEUE - B2B internal queueing mechanism

• Oracle Coherence Cache usage Trading Partner Metadata API

• JVM tuning is important (i.e. memory, garbage collection, etc.)

16


PROGRAM AGENDA

About us

The Use Case

Product Selection

Architecture


Demo

Conclusion

1

2

3

4

5

17

6

7


• Document Translation Callout Framework

– Introduced Document Callout for custom document parsing (inbound), validation and construction (outbound)

• Regular Expression Document Identification

• Trading Partner Metadata API

– Parameters, Identifiers and TP Agreements accessible via Java API and WS

• SSL Support for SMTP

• Trading Partner Identifier via Regular Expression

• Batching of Custom Documents

• xPath payload extraction from SOAP Body

• xEngine (B2B Parser) API for EDIFACT

• Bulk Listening Channel activation

• Enriched exchange information on message metadata

– Channel used

– Agreement

• Priority on Document Identification

• Message IN/OUT Collaboration by ID

• Improved Provisioning Self Service

– Callouts

– Identifiers

– Parameters

– Channel details

– Incremental Update

18

ORACLE B2B 12C – WHAT’S NEW

Note: All of this features are available for the version 11g of SOA Suite by installation of patch SOA bundle Patch 19190139 11.1.1.7.5


DEMO

19


PROGRAM AGENDA

About us

The Use Case

Product Selection

Architecture


Demo

Conclusion

1

2

3

4

5

20

6

7


CONCLUSIONS

• Standardization of messages lead to reduction of costs

• Efficiency augmented due to reducing processing of invalid messages

• Flexibility with business users empowered

• Normalization of messages eliminated point-to-point costly conversions

• Agility on-boarding customers

customer case - oracle b2b critical mission hub

Software