My Oracle Support Banner

Basic Troubleshooting Steps for EAI JMS Transport (Doc ID 850954.1)

Last updated on OCTOBER 18, 2019

Applies to:

Siebel CRM - Version 7.7.2 [18325] and later
Information in this document applies to any platform.

Purpose

The EAI JMS Transport is provided to allow connection to a JMS queue / topic.  This document will outline overall required steps (referencing document as necessary) in order to achieve this as well as to assist with basic troubleshooting of issues with EAI JMS Transport.

Provided example demonstrates usage of Siebel EAI JMS Transport with the JMS Resource Adapter of Fusion Middleware J2EE Application Server 10g (OC4J) setup to access Oracle Advanced Queueing (AQ) Messaging System.  However, the same java code can be used for any JMS provider (with appropriate changes to the connection details, classpath etc, as required for your JMS provider). 

 

The KM steps here are for using Java 32 bit.  For using JAVA 64 bit, please refer to KM articles:

- JAVA 32 bit versus JAVA64 64 bit JVM Named Subsystem Comparisons/Chart/Table (Doc ID 2332700.1)

- Setting Up And Using JAVA64 Named Subsystem For Siebel EAI JMS Transport With JMS AQ Database Integration (Doc ID 2332726.2

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 Overview
 Review required settings for EAI JMS Transport
 1. JVM / CLASSPATH
 2. The jndi.properties
 3. Tracing / Logging
 Verify JMS is working as expected outside of Siebel application
 Common Errors
References

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