Communication Outbound Manager Jobs in QUEUED status for email sent from a custom Workflow
(Doc ID 523283.1)
Last updated on JANUARY 13, 2020
Applies to:Siebel eCommunications eMail Response - Version 7.5.2 SIA  to 184.108.40.206.9 [IP2013] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2  Life Sci
Database: Microsoft SQL Server 2000
Application Server OS: Microsoft Windows 2000 Advanced Server
Database Server OS: Microsoft Windows 2000 Advanced Server
This document was previously published as Siebel SR 38-1696231251.
User was trying to test new Workflow processes in Dev server. The Dev environment lies on one server only that contains the Gateway, Siebel Server, and Database.
The WF process was designed to send email using the Comm Outbound Manager business service, Send Message method. When I run the WF using the simulator, the process was able to complete without errors. But, no email is being sent. User checked the Component Requests view, and coul see that the Outbound Comm Mgr request generated by the WF remains in Queued status and is assigned to the wrong server (server is set as the Production server). The request is being routed to the wrong server and remains in queue.
What parameters do we need to check and modify to ensure that component requests in the Dev environment are sent and processed in the Dev server and not routed to the Prod server ?
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