My Oracle Support Banner

LOY Engine - Start Engine Workflow Starts Tasks, But They Do Not Process Any Transactions (Doc ID 508704.1)

Last updated on SEPTEMBER 09, 2021

Applies to:

Siebel Loyalty Engine - Version SIA [19221] to [23021] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: [19221] SVE Transp
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server


Problem Scenario:

eLoyalty Processing Engine - Batch component has been configured to run continously, with LOYEngineNumberOfRuns set to "-1" and LOYEngineQueueObjects set to Transactions:5000 on the component.

In this scenario the component was started manually and started as many jobs as I have seen fit manually, in the view "Batch Job Submission View". Once the jobs were running, transactions were processed by the Loyalty Engine when they met the search specification "LOY Queue Manager SearchSpec: Batch" in BC LOY Engine Transaction. This setup worked as expected and desired.

The part above was done to secure that the processing worked. Nowneed to secure controlled batch runs of "eLoyalty Processing Engine - Batch". Need to run transaction processing nightly at a certain time, e.g. 2:00 AM. The plan is to set LOYEngineNumberOfRuns on "eLoyalty Processing Engine - Batch" to an integer, for now it is set to 5. Then invoke the vanilla workflow "LOY Engine - Start Engine" to initiate the jobs needed to initiate a batch processing of transactions. Set a repeating server request for "Workflow Process Manager" to run "LOY Engine - Start Engine", to achieve invocation at 2:00 AM.

However, seeing problems when  starting a batch run by running the workflow "LOY Engine - Start Engine". When  "eLoyalty Processing Engine - Batch" component is started (manually or at server restart) a batch run invoking several jobs is executed and transactions due for processing are processed. But when "LOY Engine - Start Engine" is run (invoked from the GUI using a "Workflow Process Manager" request) the expected number of jobs are started and run - but no transactions are processed.


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

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