How to Designate an Asynchronous Workflow Process to Run on a Specific Siebel Server
(Doc ID 541013.1)
Last updated on JUNE 01, 2018
Applies to:Siebel Workflow - Version 184.108.40.206 SIA  to 8.1.1  [Release V7 to V8]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 220.127.116.11  Fin Svcs
Database: Oracle 18.104.22.168
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-1355420851.
***Checked for relevance on 14-Nov-2013***
*** Checked for currency DEC-28-2016 ***
For example a Siebel environment with three application servers and only one of the servers has the MQ software installed.
A workflow process that performs MQ integration is invoked by runtime events. However if the workflow process happens to run on an Object Manager without MQ it fails.
The following solutions for the requirement have been tested but did not resolve the problem:
-Setting the processing mode to "Remote Asynchronous" to force a server request operation to start up WfProcMgr. The workflow start step has this set already and it did not have any effect.
-Setting the Runtime event Business Service to "Workflow Process Manager (Server Request)". This results in error message "Required in Argument "ProcessName" not supplied for 'Runprocess' method in Business Service "Workflow Process Manager (Server Request)"
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