1.5

Page 22
Communication between the plug-in and the database occurs using port 9001 (the default port
for HSQLDB). However, there may be situations where this port is already blocked by another
application and may need to be changed.
Several database settings can be modified by creating an ini file. This file must be named
“OLCSSvc.ini” and stored in the same folder as the executable OLCSSvc.exe, located under
“%CommonProgramFiles(x86)%\Objectif Lune\<Workflow Name>\Plugins\CPD”.
By adding the entry “DBPort = <new port number>” under [HSQLDBSETTINGS] and then
restarting the service, the communication port is changed.
Note: Workflow has to be restarted after such a modification.
Timeout
During a job transfer from the Printer Driver to Workflow, a timeout could occur (indicated by a
log entry like “ERROR: sendBinaryContents: Could not open request. Reason: 12002”). In this
case, the timeout for the HTTP service in Workflow needs to be increased. We recommend
using a value of more than 5 minutes (>600 seconds).
Additionally, the timeout in the browser on the client side should be enhanced. Please see the
help pages for your browser about how to do this.
Compatibility
The OLCS components communicate with each other by using a well-defined and versioned
protocol. As long as these components use the same protocol version, the job transfer will work
even if the plug-ins themselves are changed. The protocol version can be found in the third part
of the version number of both components; i.e. if plug-in shows version 1.0.5.11221, the “5”
indicates protocol version 1.5 (omitting the leading 1).
Any Printer Driver can communicate with any plug-in, as long as this third version number part is
identical.
Known Issues
Paper size vs Printer page size
It is important to ensure that paper size settings match the printer driver settings. If this is not
done, it’s possible that the print job transferred to Connect Send may include some extra white
space on the page. In interactive mode, this can be seen, but in non-interactive mode the job
will be processed without notification.
OLCS Plug-In and Connect on the same machine
OLCS Plug-Ins are installed with Workflow; however Connect may be installed on another
machine. Where Workflow and Connect are installed on the same machine there is a chance
that interference between the OLCS's internal database and Connect may occur causing the
browser popup to be blocked. This can be fixed by applying a startup wait to the Connect
Service. If the issue occurs during runtime, restarting the Connect Server Service will
fix the issue.