What do I like Most in 11g - Keystore Caching
By Krishnamoorthy on Jul 17, 2009
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).
1. No B2B restart required for certificate changes
2. Keystore cached in memory