Tuesday Nov 27, 2012

Customisation / overriding of the Envelop ecs files

There are few usecases where the requirement is to customise the envelop information (Interchange/Group ecs file).
Such scenarios might be required to be used for only few of the customers.
Hence, in addition to the default seeded envelop definitions, it also required to upload the customised definitions.

Here is the steps for achieving the same.
1. Create only the Interchange ecs and save
2. Create only the group ecs and save
3. Use the same in B2B

1. Create only the Interchange ecs and save :
      Open the document editor and select the required version and doctype. During creating new ecs, ensure to select the checkbox for insert envelop.
      Once created, delete the group and transactionset nodes and retain only the Interchange ecs nodes, including both header and trailer. Save this file.

2. Create only the group ecs and save
      After creating the ecs file as mentioned in steps of Interchange creation, delete the Interchange and transactionset nodes and retain only the group ecs nodes, including both header and trailer. Save this file.


3. Use the same in B2B
      These newly created ecs can be used in B2B by 2 ways.
             a. By overriding at the trading partner Level:
             This will be very useful when the configuration is complete and then need to incorporate the customisation. In this case, just select the Trading partner -> document -> select the document which need to be customised.
             Upload the newly created Interchange and group ECS files under the Interchange and group tabs respectively and re-deply the associated agreement.
             The advantage of this approach is
             - Flexibility to add customised envelop definitions to the partners
             - Save the re-work of design time effort.

             b. By adding another document definition in Administration -> document screen:
             This scenario can be used if there is no configuration done at the trading partner level. Create the required document revision and overtide the Interchange and group ECS files under the Interchange and group tabs respectively. Add the document in Trading partner -> document. Create and deploy the agreements

Tuesday Oct 02, 2012

Come visit us at OOW 2012 B2B Demo Booth!

You’re invited to visit us at the Oracle B2B Demo POD at Oracle OpenWorld and JavaOne 2012. Please stop by at our booth to see cool demos on EDI X12, EDIFACT and SBRES (used in Airlines industry). We will also be showing integration with OSB, SOA Suite and BAM. Use this opportunity to see the product in action, learn, and get answers to your questions. We will be happy to meet you and hear about your B2B integration usecases and discuss our roadmap. The demo pod will be available at the Fusion Middleware Demo POD area on Monday, October 1 through Wednesday, October 3, 2012. Look forward to seeing you there! Happy OOW 2012!
Ref: https://blogs.oracle.com/SOA/entry/come_visit_us_at_oow

Tuesday Jun 29, 2010

OSB - B2B Integration - EDIFACT

Usecase 1: OSB to use B2B for translating the EDIFACT XML document to native using the translation webservice exposed by B2B .

 

B2B Configuration

 

Oracle B2B 11g PS2 release has exposed webservices to translate XML document to Native document. This service needs an outbound agreement in B2B configured with appropriate document  targeted for a specific trading partner.

 

For e.g FromTP - MarketInc,  and toTP -OracleServices ( these value has to be updated in OSB configuration - File-In ProxyService). From EDIFACT XML document, we can identify the document type and document revision.  These details used to identify the agreement in B2B.

 

B2B translation webservice can be used in two modes, one for only translation and another for translation and routing.

 

OSB-B2B integration sample are developed based on the B2B sample "b2b-003-EDIFACT" in OTN, which deals with the creation/management of B2B configuration in detail.

 

Path structure:

b2b_003_edifact_1.0.zip\SOASamples\b2b\b2b_003_edifact\artifacts\b2b\

b2b_003_MI_EDIFACT_ORDERS_CONTRL_v1.zip\AS2_M_O_EDIFACT_D3_CONTRL_Agr.zip

 

 
 
msgosb1.jpg
 
 

 

 
OSB Configuration

 

Steps to create OSB Configuration sample:

1.       Create a OSB Project with name OSB-B2B

2.       Create BusinessService with name B2BBusinessService to consume B2B TranslateService

URL http://<host:8001>/b2b/services/ TranslateService

 

 

3.       Create BusinessService with name File_Out

Property Name

Value

RequestType

text

Provider id

File

URI

file:///C:/temp/OSB/out

Suffix

.txt

 

4.       Create ProxyService with name local_Proxy with following properties

Property Name

Value

requestType

text

reponseType

text

Provider id

local

 

5.       Add Rout node for local_Proxy

6.       Add Service Callout to Rout node to wire OSB-B2B/File_Out

7.       Create ProxyService with name File_in  with following properties

Property Name

Value

fileMask

.xml

pollingInterval

5

Binding type

XML

postAction

delete

Provider id

 File

URI

file:///C:/temp/OSB/in

stageDir

C:\temp\OSB\stage

errorDir

C:\temp\OSB\error

 

8.       Add pipeline pair

9.       In request pipeline pair create following assign actions

Variable

XQuery Text

documentType 

$body//pf1:Element-0065/text()

version

xs:string($body/(@Version))

from

xs:string('MarketInc')

to

xs:string('OracleServices')

body1

<![CDATA[<b2b:TranslateRequest xmlns:b2b="http://xmlns.oracle.com/integration/b2b">

    <!--Optional:-->

    <b2b:from type="Name">{$from}</b2b:from>

    <!--Optional:-->

    <b2b:to type="Name">{$to}</b2b:to>

    <b2b:documentTypeName>{$documentType}</b2b:documentTypeName>

    <b2b:documentProtocolVersion>{$version}</b2b:documentProtocolVersion>

    <!--Optional:-->

    <b2b:action>anyType</b2b:action>

    <!--Optional:-->

    <b2b:encoding>utf-8</b2b:encoding>

    <b2b:payload>{$body/*}</b2b:payload>

</b2b:TranslateRequest>]]>

body

&lt;soap:Body xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

{$body1}

&lt;/soap:Body>

 

10.    In response pipeline pair create following assign actions

Property Name

Value

body1

fn:data($body/*)

 

11.    In response pipeline pair create following sevice callout with Service reference "B2B-OSB/local proxy"

Property Name

Value

Request

$body1

response

response

 

clip_image003.jpg

 

 

12.       Add route node for File_in  with  Service reference "B2B-OSB/B2BBusinessService" and select operation "Translate"

 

 

 

osb4.jpg
 

 

 

 

13.       File_in ProxyService

 

 

 

osb5.jpg
 

 

 

 

 

14.       OSB project elements

 

 

 

osb6.jpg
 

 

 

 

Usecase 2: B2B webservice used for translation and routing as well.

 

For translation and routing, OSB is required to create the BusinessService using the URL.

 

http://<host:port>/b2b/services/OutboundService

 

Useful Links:

OTN B2B website

B2B Samples in OTN

  

Same approach can be used for B2B-OSB integration for a healthcare scenario. This is one way of integrating B2B translation service with OSB. Refer for more details in OTN B2B website .

[Read More]
About

To Discover and discuss the capability of B2B in the world of Trading Partner Integration. This blog is primarily intended to share thoughts on Oracle B2B Product and to share best practices in performance, scalability and various topologies.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today