B2B Import : replace flag

While doing B2B Import page, it is possible to either set true or false to replace flag, and the same is used in merging xml elements in repository.

If Import set with replace = false , following new objects will be added to repository


  1. document protocol objects like version, type, and definition found in source

  2. trading partner found in source

  3. agreement found in source

  4. delivery channel found in source for existing trading partner

  5. supported document definition found in source for existing trading partner

  6. identification found in source for existing trading partner

None of the existing document protocol objects, trading partner, agreement, delivery channel, supported document definition, and identification will be affected.


In this mode, most of the properties like host, port details which are captured in ParameterValue elements which will not be modified/added. For instance, Deliverychannel Acme_HTTP_Outbound exist with port=7777, importing configuration comes with port=8888


If Import set with replace = true , following objects will be added/modified to repository.

In addition to adding new objects to repository, it replaces


  1. existing delivery channel

  2. existing agreements

  3. existing document protocol objects

  4. existing ParameterValue list

  5. attributes of deliverychannel like ackMode, retryInterval.

  6. wallet location in host

Merge Logic:

B2B Import identifies particular element exist or not based on the value of name attribute along with the parent

For example, in case of delivery channel

1. Trading partner Acme has delivery channel name Acme_HTTP_Outbound in repository.
If import file has trading partner Acme with delivery channel name as Acme_HTTP_Outbound, it is considered as same and with replace flag set to true existing delivery channel will be replaced. Otherwise existing delivery channel in repository is untouched.

2. Trading partner Acme has delivery channel name Acme_HTTP_Outbound in repository. if import file has host trading partner GlobalChips with delivery channel name as Acme_HTTP_Outbound, then it is considered as different because the delivery channel appears in different trading partner. This delivery channel will be added to trading partner GlobalChips.

3. The point 2 behaves little different for MLLP channels. Trading partner Acme has delivery channel name Acme_MLLP_Outbound in repository. If source trading partner GlobalChips has delivery channel name as Acme_MLLP_Outbound, then treated as equal, because of the fact that all the MLLP delivery channels are get created in tp_MyCompany.xml(Host) itself.


Merge logic for Agreement and Trading partner is pretty simple, if existing trading partner name is found in the import then this is considered as same, similar logic is used for Agreement as well.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
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