DocBridge Mill: Client/Server Mode of mcopy Accelerates Conversion
Typical corporate scenario: you're stuck with a lot of individual files that need way too many external resources (Unicode fonts, graphics, etc.). Converting these files is quite costly, since the resources have to be reloaded every time mcopy starts. But with mcopy Client/Server Mode in DocBridge Mill, resources are held in memory and used for subsequent conversions.
Sample calls for the server start/shutdown and the actual conversion request follow:
Server Start
cpmcopy.exe -v -q -pro . [logging] -cs.server -cs.start -cs.hostname localhost -maxthreads 2
Logging Server
-logdir Logs -loglevel D -logappend -logtime -logdate -logfile server.log -tracefile server.trc
Client Conversions
cpmcopy.exe -v -q -pro . [logging] -cs.client -cs.retries 1
Logging Client Example
-logdir Logs -loglevel D -logappend -logtime -logdate -logfile auto.log -cs.clientlogdir Logs -cs.clientlogfile client.log
Server Shutdown
cpmcopy.exe -cs.server -cs.shutdown -cs.hostname localhost -v
Note:
After startup, the server needs to remain open and ergo requires a separate console (separate process). You can initiate the server shutdown either with a separate mcopy call (see above) or by exiting the process/closing the console.
To boost performance through parallelization, the system hardware needs sufficient processors (CPUs) and memory, which must also be licensed.
The clients and server need to run on the same system (localhost)