Last updated on MARCH 02, 2017
Applies to:Siebel Loyalty Engine - Version 188.8.131.52 SIA  to 184.108.40.206  [Release V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 220.127.116.11  SVE Transp
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-3147777141.
I have successfully setup the eLoyalty Processing Engine - Batch component to run continously, with LOYEngineNumberOfRuns set to "-1" and LOYEngineQueueObjects set to Transactions:5000 on the component. In this scenario I have started the component manually and then 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. Now I am trying to secure controlled batch runs of "eLoyalty Processing Engine - Batch". We will want to run transaction processing nightly at a certain time, e.g. 2:00 AM. I have planned to set LOYEngineNumberOfRuns on "eLoyalty Processing Engine - Batch" to an integer, for now it is set to 5. I would then invoke the vanilla workflow "LOY Engine - Start Engine" to initiate the jobs needed to initiate a batch processing of transactions. I have planned to set a repeating server request for "Workflow Process Manager" to run "LOY Engine - Start Engine", to achieve invocation at 2:00 AM.
I have run into problems starting a batch run by running the workflow "LOY Engine - Start Engine". When I start the "eLoyalty Processing Engine - Batch" component (manually or at server restart) a batch run invoking several jobs is executed and transactions due for processing are processed. But when I run "LOY Engine - Start Engine" (invoked from the GUI using a "Workflow Process Manager" request) the expected number of jobs are started and run - but no transactions are processed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms