My Oracle Support Banner

Keystore Defaults To The Siebel Server Keystore Instead Of The JMS Custom Keystore For JMS Integrations After Patch From 22.5 to 23.9 (Doc ID 3008131.1)

Last updated on MARCH 03, 2024

Applies to:

Siebel CRM - Version 23.9 and later
Information in this document applies to any platform.


On : 23.9 version, Siebel EAI

In Siebel versions earlier than 22.12, it was possible to use different keystores for MQ certificates.

This was accomplished by using the System Property Setting of Tomcat Service Manager with the below configuration:

4. Review the logs and confirm that the referenced keystore is not the custom keystore.


Patch Siebel from 22.5 to 23.9.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.