Start parameters enable the running of the programme in the so-called unsupervised mode. This means that all actions are defined by the command line.
The call-up is:
UBProfessionel.exe /Mode:FILE /Profile:maxcrc /AttributeCategory:loginProperties /Outfile:LoginProperties.xml
/Css:Report.css /Xsl:reportlist.xsl /Logo:CompanyLogo.jpg /Servertype:Microsoft
The following options are possible:
- config
allows the transfer of a configuration file, instead of the individual parameters
- outfile
-
defines the output file. The extension controls the corresponding output format. The following formats are currently supported:
.xls – MS Excel
.csv – Comma Separated Value Format
.ldif – Lightweight Directory Interchange Format
.xml – Extended Markup Language Format
- servertype
-
defines the manufacturer. The following values are possible:
Microsoft
Novell
Linux
- css
defines the Style Sheet file used, only necessary when using XML
- xsl
defines the relevant Transform file, only necessary when using XML
- logo
defines a graphic symbol, only necessary when using XML
- mode
-
defines the direction of the export, possible values:
LDAP
FILE
LDAP – The file specified under outfile will be used for the export into the directory service. The information given under profile will be used, and the attributes specified under AttributeCategory will be taken into account.
FILE – The file specified under outfile will be used for the export into the file system. The information given under profile will be used, and the attributes specified under AttributeCategory will be taken into account.
- AttributeCategory
defines the attributes which will be taken into account in the current enquiry
- profile
defines the connection information which comes from the configuration file ub.xml
- ubxml
defines the file location of the configuration file (optional)
So-called variables are supported in the specification of the output file.
%Y – current year
%m – current month
%D – current day
%H – current hour
%M – current minute
%S – current second
In order to archive the export automatically, the following formatting could be used:
/outfile:<Dir>\/outfile:arch-%YYYY-%MM-%DDT%hh-%mm_Login.xml
Example of an export configuration file
#
# UBProfessional example configuration
#
#
# Comments:
# lines beginning with # or // are treaded as comments
# however, you cannot start a comment within a line!
#
#
# You can use this config file by passing /config:<filename> to the executable. Concurring
# parameters given at the command prompt will override parameters given here!
#
#
# Every parameter supports the following meta-strings:
#
# %Y - current year
# %m - current month
# %D - current day
#
# %H - current hour
# %M - current minute
# %S - current second
#
# mode of the export definition to use
# available values: FILE, LDAP
#
mode=FILE
#
# Name of the file to generate.
# the filename extension is used to determine the output format (xls, ldif, csv, xlm)
# the path to the output file will be created if it does not exist.
#
outfile = demo%YYYY-%MM-%DDT%hh-%mm-%ss/loginproperties.xml
####### xml configuration options
#
# additional settings, when using xml output format.
#
css = <name of="" css="" file="">
xsl = <name of="" xsl="" file="" >
logo = <name of="" logo="" file="" >
#
# name of the profile, you must configure in the user interface of UBProfessional
#
profile = maxcrc
#
# amount of attributes collected in the category name, you have to create the category in the user
# interface first
#
attributeCategory = loginPproperties
#
# the configuration file parameter is optional. If no value is defined, the search order looking for the file ub.xml is as follows:
#
# 1. Local program folder of UBProfessional.exe
# 2. All path entries defined be the environment value ‘path’
#
# ubxml = C:\Programmes\ublight\ub.xml
#