Siebel Order Failed Due to Message Stuck in Weblogic SAF Queue (Doc ID 2970380.1)

Last updated on FEBRUARY 29, 2024

Applies to:

Goal

Setup:
-------------

• Application Integration Architecture (AIA) for Communications Process Integration Pack 12.3 (O2C - Order to Cash) on top of service-oriented architecture (SOA) 12.2.1.4 and Weblogic 12.2.1.4 using JDK 1.8.0_371.
• Here Siebel is integrated with Order and Service Management (OSM) using AIA.
• O2C (or AIA) - is deployed in WebLogic server in a cluster based environment having 1 admin server and 2 managed server (ms1 and ms2 on two different machines).
• OSM - is deployed in WebLogic server in a cluster based environment having 1 admin server and 4 managed servers (ms1/ms2 on one machine and ms3/ms4 on second machine).
• O2C application (uses WebLogic SAF - Store and Forward Agents) is integrated with OSM application (uses weblogic JMS Queues) successfully.

Issue
-------------

In production, messages in the SAF queue are not being sent forward.

Details
-------------

• as per the order flow scenario here involving AIA and OSM, AIA publishes message into the SAF queue, this message is supposed to be pushed to the corresponding JMS queue on the OSM server, but it is not happening. The OSM server has not received any messages and there are no related log messages too.
• the communication between O2C (AIA) and OSM server (through telnet and ping) is fine. But still orders are not flowing from source SAF to target JMS Queues.
• the system is a fresh install of AIA 12.3 (not an upgrade).
• Note: Here in this scenario, following managed servers were up and running in the environment:
  O2C domain [ms1 is up and ms2 is up]
  OSM domain [ms1 is up, ms2 is down, ms3 is down, ms4 is down].

Solution

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