What do I like Most in 11g - Keystore Caching

In 10g Oracle B2B, whenever certificate is added/removed, we need to bounce the B2BServer to make the certificate available to B2B Engine as the caching of the certificate happen in the intialization stage. On the flip side B2B will continue to use the certificate even if it gets deleted from the wallet. This limitation is addressed in 11g Oracle B2B.

Keystore is internally cached in 11g rather caching certificate as in 10g. For every change in the keystore due to certificate management, B2B recognizes the change and reloads the complete keystore in memory.
This improves the message processing performance, while accessing any certificate(it could be most used or least used).

Advantages:
1. No B2B restart required for certificate changes
2. Keystore cached in memory

Comments:

Thanks Krishna. It's really a good feature in 11g because in production no one wants unneccessary server restart. Does B2B 11g supports wallet containing 2 private keys? I am asking this question because in 10g we encountered such requirement and IDC team has assured us that they will try to include this feature in 11g.

Posted by Anuj on July 25, 2009 at 07:47 AM IST #

Anuj, B2B rely on underlying Weblogic infrastructure for its security requirement for example, SSL. So, we would say it has support for all or most of the usecase supported by the infrastructure. We would recommend you to follow the Weblogic documentation to figure out the list of supported documentation. Thanks, Sinkar

Posted by Sinkar on July 27, 2009 at 05:32 AM 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