Default backgroung job server.

[Former Member]

Hello Experts

I have one Appl server and one CI. I have builded application server specially for jobs which need more extended memory. Now if some one logging on to application server and scheduling some background job message server is doing load balancing.. like one Job on appl server 2nd on CI.. 3rd on Appl serve ..4th on CI ..I dont want this to happen. If some one logged into application server and scheduling some jobs his jobs should run on application server only ..

can you help me how to configure this,.

Kind Regards

Abhijeet Rathi

[Former Member]

Dear Olivier,

Thanks for immediate response. This could be two easiest way which any BASIS consultant can this. But I am facing one more level of difficulty which is not allowing me to accept this options.

@ Reducing btc work process to zero -> Some jobs which is not extended memory hungly must run on CI else other server will be over loaded.

@ Specifting target server -> This job scheduling work is done by back office people. We just got SAP in our organization. End users are already struggling with new SAP system.

So I am looking for some solution, using that I sould able to put this restriction from my side.

I found one parameter " rdisp/btcname ". If I set this parameter in instance profile of my application server, will it help? or this parameter is only effective for chain jobs

Kind Regards

Abhijeet Rathi

[JPReyes]

Some jobs which is not extended memory hungly must run on CI else other server will be over loaded.

I don't undestand the problem... basically you have a CI that cannot handle "hungry" jobs and at the same time you don't want to move all the jobs to the DI's?... I mean why don't you just get extra memory for your CI?... its very cheap and its important that your CI can handle the heaviest loads. Also make sure that your swap space is at least 4 times the size of your physical memory.

This job scheduling work is done by back office people. We just got SAP in our organization. End users are already struggling with new SAP system

Adding one step to the process of creating a job shouldn't be problematic... but again... why don't you kill the snake by the head and get your CI to a decent level so job balancing isn't an issue?

found one parameter " rdisp/btcname ". If I set this parameter in instance profile of my application server, will it help? or this parameter is only effective for chain jobs

The definition of that parameter is "Name of the server for handling background processing events"... that doesn't mean that the job is going to run on the instance set on the parameter, mean that is going to use the instance to handle the job events.

Regards

Juan

[Former Member]

Hi,

You have 2 possibilities :

Remove the background processes ftom the CI server.

or

Select the DI as "Executing Target" when creating the job.

Regards,

Olivier