Filter
Top Products
When a new job submission occurs, the callback library will query the LDAP server to check whether a default device destination
was defined for the current job originator if no explicit destination was specified by the originator. If it finds out a destination,
the job will be automatically directed to this destination, otherwise, the usual process will take place.
This operation is transparent for the job originator. If the default destination returned by LDAP is invalid or not matching the job
requirements, an error message will be thrown by the xpadd - job command.
3.5.21.1 Configuration
3.5.21.1.1 Configuration file
A configuration file stored in the Xprint system directory must contain the necessary information to query the LDAP server. Here
is an example showing how the configuration file should look like
#This file contains the parameters allowing XPRINT to perform the LDAP query.
#"command" is the path trough the ldapseach command
# "rootdn" is the location where ldapsearch must start searching
#An anonymous authentication is required.
command=c:\openldap\ldapsearch.exe
ldapserver=d241peys
rootdn=dc=osl,dc=oce,dc=net
As you can see, three variables must be provided.
- command is the path of the ldapsearch command
- ldapserver is the hostname on which the LDAP server is running
- rootdn is the typical LDAP information indicating where the ldapsearch command is to start searching.
3.5.21.1.2 Activating the callback library
To enable the LDAP interoperability, you must rename the file _CL_callbacks.cfg to CL_callbacks.cfg and you have to restart
Xprint to make the activation effective.
The example provided with Xprint 8.0 has been tested using the OpenLDAP software providing an LDAP server and a few LDAP
client commands.
3.5.21.1.3 Example of a job submission using the LDAP interoperability
When you have been through the two above steps, you can add a job the following way
xpadd -dr <file_to_print> -<any job option except -de>
If you specify a destination with the '-de' flag, no LDAP query will be done.
3.6 Obsolete functions
-/-
3.7 Incompatibilities
● The SNMP component is not activated anymore after the installation. If you want use it, you have to activate it
manually by adding an entry referencing the libCacheMan library in the following files:
■ ..\Xprint\addons\BE_callbacks.cfg
■ ..\Xprint\addons\DA_callbacks.cfg
■ ..\Xprint\addons/DB_callbacks.cfg
■ ..\Xprint\addons/SP_callbacks.cfg
■ ..\Xprint\addons/SV_callbacks.cfg
For Windows , you will have to ensure that the entry below is present in the above files: