Discussion

Batch Processing in PEGA

We need to do batch processing across mutiple pega app servers to reduce the batch window processing time . the current batch process runs on only server ( we have a pool of 3 servers) and processes all the work covers . any thoughts on how to split the processing across multiple servers without contention. any ideas /suggestions. any issues we might run into , please post your experiences.

***Updated by moderator: Marissa to close post***

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

June 3, 2008 - 3:04pm

V5.2

Pega
June 3, 2008 - 5:36pm

3 servers, eh? The last digit of pxUpdateDateTime is essentially random. This algorithm doesn't provide failover support, but you could have server A process all work objects whose pxUpdateDateTime ends 0-3, server B process all work objects whose pxUpdateDateTime ends 4-6, and server C process all work objects whose pxUpdateDateTime ends 7-9. I'm not exactly sure how to write the SQL to do that, but I'm told it is straightforward to use a character conversion to achieve this objective.

Note that this algorithm can take up to 10 servers (each doing one digit of 0-9). For more than 10 servers, you'll have to start using the last two digits of pxUpdateDateTime.

Again, if a server goes down, its quotient of work objects won't be handled so you'll need to bring it back up or schedule one of the other servers to run the sequel the downed server was supposed to run.

Pega
May 29, 2008 - 3:33pm

What PRPC version are you on?