My Oracle Support Banner

Siebel IP17 JMS Integration Call Over ApplicationContainer To WebLogic Using wlfullclient.jar Returns HTTP 404 'Status code - 404' Error (Doc ID 2425115.1)

Last updated on FEBRUARY 05, 2019

Applies to:

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

Symptoms

PRODUCT VERSION: 17.4 [IP2017] version, Siebel EAI

When Siebel client invokes EAI JMS Transport call to WebLogic JMS Server, it generates an error.


ERROR

-----------------------
ObjMgrLog Error 1 000000235b23f7f8:0 2018-06-15 09:43:52 (httptransport.cpp (1795)) SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 404'


STEPS
-----------------------
The issue can be reproduced at customer environment with the following steps:

1. The JAVA64 subystem has been configured to use the Siebel ses ApplicationContainer.

2.  The Siebel Application Object Manager component has JVM Subsystem = JAVA64, so outbound EAI JMS Transport service calls will route to the ses applicationcontainer to be sent out to the external system.

3.  The external system in this case is WebLogic acting as the JMS Server. Since it is using WebLogic, the WebLogic wlfullclient.jar file ahs been copied over to the ses\applicationcontainer\lib directory.

4.  When the Siebel Client invokes the EAI JMS Transport call, the call fails with an error.

 

Cause

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
Symptoms
Cause
Solution
References


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