Job Scheduling using server pool

[Former Member]

Is there any way to use a pool of servers for job scheduling?

I know you can tell it the target server you want, but I want it to find an available server from a list.

The reason is, the job runs software on the app server. Not all app servers have this software installed. But it is installed on more than one. I want it to find an available server, but only one that has the software installed. It would be great to somehow define a pool of servers where the job can run.

I don't think I can get creative with job class. This looks at all work processes on all servers.

If I go this way, I'd have to set all work processes as A on the servers I don't want to use, and set my job as B. That is definately not an option.

Any ideas?

Thanks

[Former Member · Accepted solution]

Hello dskdell,

I guess u want to use some kind of load balancing with the background servers,

well when u define a job,dont give the server name there,then it will look for the available server and schedule the job there

" Although a job can specify to use a particular background server (an application server that has at least one background work process), it is best to allow the background processing system to use load balancing to distribute the workload among the available servers"

Refer to http://help.sap.com/saphelp_nw70/helpdata/en/4a/2d513897110872e10000009b38f889/frameset.htm

Hope it helps

Rohit

[tholuganti]

Please check this document, it should help you with you request:

Regards,

Raj

[Former Member]

Yes I know that I can leave the target blank and will look at all background processes on all servers.

I am trying to limit which servers are searched.

I also want to avoid re-defining all my WP's and dedicating some servers as strictly background.

I don't think logon groups will work. This is just for logon, correct? This does not have any bearing on scheduled jobs.

Thanks for your input. It doesn't look like there is any easy way to do what I want.

[Former Member]

Hi

I think configuring logon groups and dedicating certain servers for background processing can be a possible solution for your problem. In such servers, the WP could be configured such that there are a minimum number of dialog WP and the rest used for background processing.

Also while creating a certain background job, we get the option of Execution target which is used to set the dedicated server in which the job is supposed to run.

For more details on logon groups , please check:

http://help.sap.com/saphelp_nwpi71/helpdata/en/c4/3a64b4505211d189550000e829fbbd/content.htm

Regards

Chen