B2B Configuration : Various Flavours of Import

B2B metadata import brings already created configuration which ever get exported from an environment(for instance test environment, selfservice API, or upgrade 10g export).

No business validation applied while importing configurations, means that B2B Import brings configuration which confirms basic constraints like XSD, MDS relationship. However, deployment process will validate and confirms business integrity and brings to runtime.

Compressed format of Import

Single XML/XSD/ecs import also needs to be bundled in a ZIP file and content must to be placed in /soa/b2b/ folder.

Import comes with following flavours

1. Import only document protocols.
Using Selfservice, only documentprotocols possible to create, we can eventually import to B2B repository.

2. Import Trading partners alone(no document protocols).
Using Trading partner export from B2B UI partner page, we can export only Trading partner with identification details. This configuration allowed to import in B2B repository.

3. Import Agreement.
Import document protocol, trading partner and agreement as a bundle (or we can eventually say business unit). If we are doing agreement export from design or deployment page, single agreement get exported.

B2B has provision to export multiple agreements, which will export a zip file which contains multiple agreements. In this scenario, ZIP file has to be extracted and one by one agreement has to be imported.

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