I was going through the following lines (double quoted) in one of the article, mentioned my query at the end. Please clarify.
"For example, jobs that execute against SAP have historically been defined to execute against an XA workstation. TWS uses the TWS for Applications supplied method r3batch to communicate with the target SAP system. The r3batch method connects to the target SAP system using the Remote Function Call (RFC) interface using configuration options from the associated r3options file. The XA workstation name determines the r3options file to be used for connection to SAP.
When a SAP job executes using a POOL workstation, the advanced job type of “xajob” includes a reference to the r3options file to be used to access the target SAP system. As the job can execute on any agent defined as a member of the POOL, the r3options file must be available on every agent within the POOL."
I saw an example in one of the knowledge articles related to SAP (r3batch method) job execution. What happens when target SAP system itself is DOWN? In that case, no jobs are allowed to execute right even if we are going to have dynamic pooling enabled for SAP r3batch as you suggested. Additionally, even though we use dynamic pooling here, the actual job is being executed on the SAP systems right? So the computing resources used for execution of jobs is actually on the target SAP system and not on the dynamic agents in the pool, correct? How does dynamic pooling benefits us here? Not sure if I am understanding correctly, please correct me.
you are right if the SAP system is down no jobs can be executed, note also that if the TWS agent with which you schedule the SAP's job is down, the job can not be submitted and executed. If the job is submitted to the POOL every member can be used to schedule the job so no matter if one of the member is down.
Thanks Much for your response.
But Can you also clarify the 2nd part which I have mentioned in my query please?
"Additionally, even though we use dynamic pooling here, the actual job is being executed on the SAP systems. So the computing resources used for execution of jobs is actually on the target SAP system and not on the system where dynamic agent is associated in the pool, So how does dynamic pooling benefits us here? Not sure if I am understanding correctly, please correct me."