OpenOffice.org is scripted using the UNO client-server model. When a ITP/Document Processor loads the OpenOffice.org client this client connects to an OpenOffice.org server process running in server mode over a TCP/IP network connection. This server process can be shared between multiple processes and will remain active when the ITP/Document Processor shuts down.
Due to design limitations in OpenOffice.org it is not possible to control a single OpenOffice.org server simultaneously from multiple ITP/Document Processors with the same user profile. This could result in deadlocks in OpenOffice.org. To avoid these deadlocks ITP/Server will serialize all requests from a single user to an OpenOffice.org server.
This serialization, however, will increase latency because the ITP/Document Processors will have to wait for each other to finish printing and convert documents. This can be avoided by using multiple user profiles that all connect to the OpenOffice.org server installation separately. Each user will get a separate OpenOffice.org process. Below, we will explain how to realize this for ITP/Server. Preferably every ITP/Document Processor should have its own OpenOffice.org process because shared servers will still be serialized.