Yes, it is. It must be done within the licensing restrictions of the product (max. jobs per day, max. cpu's, etc.), but it is possible.

What is required is the installation of multiple instances of Central (which the product will do itself) and then some sort of arbiter that can receive all jobs from the producing system(s) and then assign these to the extra instances as they become available.

This arbiter could be a simple script or a much more complex application that can distribute jobs to different instances based on their priority, size (and thus their estimated time to process) or one that can split large jobs into chunks for parallel processing.

If you're running a large SAP system in Omaha, for example, you might want to have several Central servers scattered across the country...or the World. Text is almost always smaller than printer language, so you might want to have your arbiter distribute jobs coming from the systems in Omaha to the other Central servers, perhaps based on the target device names or IP ranges. This saves your SAP system from having to know or care about this, and you will get less network traffic and your users will get faster response.

On systems with a number of CPU's and fast disk arrays, it is possible to run several instances of Central simply to increase throughput. You'll only see gains if the bottlenecks in the process aren't on the Central server. Such as if your network print queues are dispersed and take time to respond, or if your jobs need to access a database or some other external resource to complete.

I'll write more about this if anyone shows interest. To register your interest...ask!