Agreement Caching - Performance Best Practice

TPA Caching : Trading Partner Agreement is the deployable unit, Oracle B2B Identifies the agreement based on From Party, To Party , Business Action which is a combination of Document Type, Revision. Ideally this query is little costly as the number of Agreement increases as it has to go through multiple tables. For performance reason, there is a feature introduced to cache all the Agreement information to be used in the subsequent message processing.

When this property is enabled all the TPA details will be read from the cache instead of runtime repository.

Set the below property in tip.properties and restart b2b Engine.

oracle.tip.adapter.b2b.TPACache=true

This feature works for Agreement Identification based on Document as well as Business Action.

Note: Make sure to increase the heap size in opmn.xml as caching consumes more memory

Comments:

Looks Nice!

Posted by אימון אישי on July 15, 2008 at 08:32 PM IST #

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