My Oracle Support Banner

RTD: How to Run Batch Processing In A Cluster (Doc ID 1510174.1)

Last updated on APRIL 22, 2021

Applies to:

Oracle Real-Time Decisions Base Application - Version 3.0.0.1 [365] and later
Information in this document applies to any platform.

Goal

Qn1:Our goal is to designate the batch jobs to run only on a subset of the RTD servers in the cluster. We thought that it can be achieved by either
1. enabling the batch agent only on a subset of the RTD servers, or
2. using the load balancer (bigIP) to control the set of RTD servers receiving the requests

It seems like both don't work based on our testing. If they should work, would you please provide more detail on how to get it work?

Here is a detailed information:

We have multiple RTD servers in a cluster. We have a project that requires batch processing. We are trying to see how we can leverage all the servers for this. So we were testing this in our performance environment. We have two RTD servers in perf enviroment. app01 and app02. app01 also serves as the admin server.

First scenario and question
1) A batch registered ILS can only be deployed to a RTD server with the batch agent running.
2) The RTD cluster will automatically deploy the batch registered ILS to all other active RTD servers in the cluster.
3) If the batch agent is not running, the batch registered ILS will automatically set to failed across the cluster.
So if we want to deploy a batch registered ILS to a RTD cluster successfully, the batch agent has to be running in all the active RTD server in the cluster. Is there any way we can control this? How this synchronization can be controlled.

Second scenario and question
1)We had RTD Batch Manager running on both app01 and app02. RTD Batch agents enabled on both app01 and app02. Ebm.jar in app01 is pointing to app01 RTD url and ebm.jar in app02 pointing to app02 RTD url.
2)Servers restarted sequentially. We brought app01 first, so when I took app02 up, it saw batch manager running on app01 and registered the batch agents. We could also see batch agents registered in both servers from server.log
3)First we started the ebm from app02. All the jobs were running on app02 and I could see the RTD logs(server.log and .out) on app02 and batch manager logs in app01.
4)Next time we started the ebm from app01. We could still see the jobs running on app02 and batch manager logs in app01. The jobs didn't started in app01 even though we had app01 as the rtd url in the ebm.jar file in app01 server.

So why the jobs didn’t run on the server on which the batch manager is running when in cluster. It worked on the same server where batch manager and agents with one server in a cluster.
 
Qn2:Our goal is to designate the batch jobs to run only on a SUBSET of the RTD servers in the cluster. Load balancing is not the key issue here. Can it be done?
 

Solution

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
Goal
Solution


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