on 10-21-2013 7:48 PM
Dear all,
Is it possible to schedule a 40 Work Processes job to run on 2 SAP instances (DIA) only, while the SAP system has 6 SAP instances (CI + 5DIA).
We are using Control M + CPS Redwood.
I suppose some RZ12/Logon groups or SM61 would be involved? Or any concrete trick in CPS/ Control M?
Thanks in advance!
Marian
Hi Marian,
Let me clarify whether i understood your requirement clearly.
You want to schedule the jobs with 2 SAP Dialog instances specifically instead of doing load balancing.
Regards,
Raja. G
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raja,
This we only plan to implement (new Instances) / schedule (jobs after instances are in place)...
So we can really create a separate kind of "Project" in CPS for the new instances only, so all jobs scheduled for this "project" will run only on the 2 newly configured instances?
How can we ensure, that the SAP will not do the Load balancing also on existing Instances?
Any setting similar as per below should be setup?
http://scn.sap.com/community/cps-by-redwood/blog/2013/04/18/application-server-load-balancing-option
-> but this is for SAP to do LB, we need the opposit to this?
-> for current jobs we need the LB to be done on current instances only, not on new ones.
Thanks a lot in advance!
Marian
Hi Raja,
Yes, I see that it is possible to setup a parameter like this on the Job scheduling settings part...
But that would schedule the "mother" report on the instance - but if it has to run on 40 WPs, how can we make sure that child jobs will not be triggered on other instances?
Can we turn off SAP load balancing somehow?
On the picture, last field -> Target server group name: is this the "RFC server group" (parallel generators) setting -> RZ12 is SAP? Or rather Logon Group?
Cheers,
Marian
My assumption:
I think it is neither logon group nor RFC group.There is something called background processing server groups. Please check SM61-->Job-Servergruppen
There you can maintain the background jobs server groups.
So once you create your BP server group, you can use the MSHOST connection string which will take care of the load balancing.
MSHOST=<MS host> R3NAME=<SID> GROUP=<group>
Thanks
Nanda.
Hello Nanda,
It is a common misunderstanding that the connect string on the SAP System connection is responsible for the load balancing of jobs. This only load balances the connections from CPS to the remote SAP System.
Load balancing of jobs in SAP can be done in 3 ways:
1) Let SAP do it. In this case uncheck the 'Load balancing' flag on the SAP system on the CPS side and leave the fields TARGET_SERVER and TARGET_GROUP empty on your jobs. Now SAP will pick the application server the job has to run on on the fly.
2) Do it manually. Use parameter TARGET_SERVER to force jobs to run on specific application servers. You can create your own function to determine the one you want of course. Or use parameter TARGET_GROUP, here you specify the batch group the job can run on and now SAP will pick one of the servers from the group to run the job on.
3) Let CPS do it. Now leave the 'Load balancing' flag on the SAP system in CPS checked and leave the fields TARGET_SERVER and TARGET_GROUP empty. Now when the job starts and just before the job is created in the remote SAP system CPS does the load balancing calculation based on the Load Factors for the different application server defined on the SAP system object (go to your SAP system->Maintain Objects and check out the Application Servers section). Then it will fill in the best server based on the calculation (default is the server with most free batch processes) in the TARGET_SERVER field and the job will be executed there.
Hope this helps.
Regards Gerben
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.