0% found this document useful (1 vote)

65 views228 pages

JInstall 7400 Manual

Uploaded by

Serge Adeossi

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (1 vote)

65 views228 pages

JInstall 7400 Manual

Uploaded by

Serge Adeossi

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

J/Install

J/Install
Reference and Using

User Guide

Date: Aug 21, 2018

Software version: 7.4/00
Document version: 002
Trademark rights
As long as hardware and software names are contained in this document, they may have been also
registered as trademarks of their respective product owners and shall be treated as such. Diebold
Nixdorf has, in the main, followed the manufacturers' spelling for product names.

Confidentiality undertaking
Copyright © Wincor Nixdorf International GmbH 2005 -2018
The contents of this document may not be reproduced, exploited or published, whether in whole or in
part, without the prior written permission of Wincor Nixdorf International GmbH.
The copyright applies to all forms of storage and reproduction in which this information is incorporated
including, but not limited to, magnetic memory, computer printouts and visual displays.
Offenders will be prosecuted and liable for all cost and damages incurred by the breach.
All rights, including rights created by patent grant or registration of a utility model or design, are
reserved. Right of any technical modifications reserved..

Names and other data

The names, e-mail addresses, telephone numbers and other data used in this document are purely
fictional (except the e-Mail addresses listed below to return feedback to this document). Any
resemblance to actual persons, living or dead, is coincidental.

Comments, Findings
In case there is something you want to tell us about this document please inform us via our iSupport
interface.
There you can open an incident to inform us regarding comments or findings related to this document:
External: [Link]
Internal: [Link]
If you do not have access to iSupport and there is nobody known having an account, please login to the
Diebold Nixdorf
Learning Suite ([Link] and complete the iSupport Web-based training
(WBT) to receive access to iSupport.
J/Install
About this document

Target group
This manual describes J/Install. J/Install is a framework that processes a set of
commands specified in a control file.
General knowledge on Windows and XML are preconditions for using J/Install.

Status of this document

Final version – right of changes reserved

Notational conventions
Notation Application Example
Italics External cross references "...further information is available in
the manual XYZ for the product
ABC..."
Names of interactive elements "...in the field Routingcode..."
Emphasized italics Internal cross references "...see page 23..."
provide page numbers
Bold For emphasis "...the module ABC is..."
Buttons, name enclosed in [ Sav e]
square brackets
Accessible screen elements "...click on the appropriate I D to...."
Menu items "Select Fi l e - Sav e to…"
Non-proportional Source texts <head>
<title>XYZ</title>
</head>

Directory and file names The customer clicks on this link and
the file [Link] is opened.

Note
Notes providing additional explanation and tips on how to use the product
more effectively are shown in this format.

Caution
Information critical to operation of the product and the avoidance of faults,
misoperation, and so on is shown in this format.

Document version: 002 Reference and Using – User Guide iii

J/Install

iv Reference and Using – User Guide Document version: 002

Contents

J/Install
Trademark rights .............................................................................................................. ii
Confidentiality undertaking .............................................................................................. ii
Names and other data ..................................................................................................... ii
Comments, Findings ........................................................................................................ ii
About this document ....................................................................................................... iii

Chapter 1 Installing with J/Install 1-1

Installing J/Install 1-2

Attended installation of J/Install .........................................................................1-4
Unattended installation of J/Install ....................................................................1-7
Updating J/Install ...............................................................................................1-8
After installation .................................................................................................1-8

Running J/Install 1-10

J/Install files 1-13

Processing of packages 1-21

J/Launch 1-24

Running programs under a different user 1-26

Logging 1-28

Chapter 2 J/Install reference 2-31

Changes regarding previous releases 2-33

Variables 2-45

The main area "Variables" 2-46

The main area "Status" 2-47

The action Write ..............................................................................................2-47

The main area "Requirement" 2-49

The main area "Sequence" 2-50

The command AskUser ...................................................................................2-53
The command CheckPassword ......................................................................2-55
The command Compress ................................................................................2-56

Document version: 002 Reference and Using – User Guide v

Contents
J/Install

The command Condition ................................................................................ 2-58

The command ConfAutologon ....................................................................... 2-83
The command ConfNonAdmin ....................................................................... 2-84
The command CopyFile ................................................................................. 2-86
The command CreateDir ................................................................................ 2-88
The command CreateList ............................................................................... 2-89
The command CreateShortcut ....................................................................... 2-90
The command Decompress ........................................................................... 2-91
The command Definition ................................................................................ 2-94
The command Delete ................................................................................... 2-101
The command DeleteRegistryKey ............................................................... 2-102
The command Dialog ................................................................................... 2-103
The command Exception .............................................................................. 2-109
The command Execute ................................................................................ 2-110
The command Exit ....................................................................................... 2-113
The command Extern ................................................................................... 2-114
The command Fallback ................................................................................ 2-117
The command GetSource ............................................................................ 2-119
The command GetTextFile ........................................................................... 2-121
The command GetToken ............................................................................. 2-122
The command GetValue .............................................................................. 2-123
The command Import ................................................................................... 2-125
The command Jre ........................................................................................ 2-126
The command Keep ..................................................................................... 2-128
The command Loop ..................................................................................... 2-129
The command LoopEnd ............................................................................... 2-132
The command ModifyEnvironmentVariable ................................................. 2-133
The command ModifyPendingFile ................................................................ 2-135
The command ModifyString ......................................................................... 2-136
The command ModifyTextFile ...................................................................... 2-137
The command ModifyToken ......................................................................... 2-140
The command ModifyValue ......................................................................... 2-142
The command ModifyVariable ..................................................................... 2-145
The command OsBootLogo ......................................................................... 2-147
The command ProClassic ............................................................................ 2-148
The command Register ................................................................................ 2-159
The command Restart .................................................................................. 2-160
The command Script .................................................................................... 2-162
The command SetVariable ........................................................................... 2-163
The command ShowMessage ...................................................................... 2-164
The command ShowTextFile ....................................................................... 2-165
The command TuneOs ................................................................................. 2-166
The command Wait ...................................................................................... 2-168
The command WriteLog ............................................................................... 2-169
The command WriteVersion ......................................................................... 2-170

Values and addressing of data 2-171

Using regular expressions ............................................................................ 2-171

vi Reference and Using – User Guide Document version: 002

Contents

J/Install
Using patterns ...............................................................................................2-172
Data access paths .........................................................................................2-174
Error handling ................................................................................................2-181

Chapter 3 Sample installation with J/Install 3-183

The problem 3-184

Encoding 3-185
The Variables section ....................................................................................3-185
The Sequence section ..................................................................................3-185

Chapter 4 Installing ProClassic with J/Install 4-187

Installation media 4-188

ProClassic CD ...............................................................................................4-188
Registration Key Disk ....................................................................................4-188
Customizing Disk ...........................................................................................4-188

The file [Link] 4-190

Running ProClassic installations 4-197

Procedure of a ProClassic installation 4-199

Sequence of a ProClassic start 4-203

Installing an XFS-ADDON component 4-204

System informationen ...................................................................................4-206

Updating the Java Runtime Environment 4-213

Index A-215

Document version: 002 Reference and Using – User Guide vii

Contents
J/Install

viii Reference and Using – User Guide Document version: 002

J/Install
1 Installing with J/Install

The following chapter describes the automatic installation procedure with

J/Install.
In this chapter you will find information about the following topics:
Installing J/Install 2

Attended installation of J/Install ............................................................................... 4

Unattended installation of J/Install .......................................................................... 7
Updating J/Install ..................................................................................................... 8
After installation ....................................................................................................... 8

Running J/Install 10

J/Install files 13

Processing of packages 21

J/Launch 24

Running programs under a different user 26

Logging 28

Document version: 002 Reference and Using – User Guide 1

Installing with J/Install
J/Install

Installing J/Install
J/Install is a framework that processes a set of commands specified in a
control file.
J/Install is located on the CD in the \install\jinstall\<Version>
directory.
[Link]
Use the [Link] installer only if you have a Java Runtime
Environment (JRE) 1.8 already installed on the target machine. This
JRE's folder name must be present in the Registry parameter:
[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime
Environment\1.8], for example:

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.8]

"JavaHome"="C:\\my-jre8"

If you install on a 64-bit system then the above parameter must be set in
the Registry area designed for 32-bit applications ([Link] is a 32-
bit application):

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\JavaSoft\Java Runtime Environment\1.8]

"JavaHome"="C:\\my-jre8"

Instead of setting the above Registry parameter you can also set the
environment variable JAVA_HOME:

JAVA_HOME=C:\my-jre8

If the above preconditions are not fulfilled, a [Link] call is followed

by the error message:

Click on [ L o c at e] to tell the installer where your JRE is located, or you

can cancel the installation.
[Link]
Use this file to install J/Install using the Java runtime environment that is
included in the setup. This file shall be used if no or none of the required
Java runtime environments for the installation is present at the target
system.
[Link]
Template response file for unattended installation (see "Unattended
installation of J/Install" on page 1-7)

2 Reference and Using – User Guide Document version: 002

Installing J/Install

J/Install
Windows 7
If Windows 7 is running with activated UAC, an installation from a drive
mounted by subst or net use is not possible since this mounted drive is not
available for users with expanded installation rights.

Installation steps
Product installation started from the installation CD consists of two steps:
1 Installation of J/Install.
Source: <CD>:\Install\JInstall\<version>
Target: C:\JInstall
Installation engine: install4j
Log file: C:\Users\<user>\AppData\Local\Temp\
setup_JInstall.log
2 Installation of the product.
Source: <CD>:\Setup\<product>\version
Target(s): depends on the product to be installed.
Installation engine: J/Install installed with step 1
Log file: C:\JInstall\[Link] (for more details, see "Logging"
on page 1-28)

Document version: 002 Reference and Using – User Guide 3

Installing with J/Install
J/Install

Attended installation of J/Install

You can install J/Install using a setup wizard.
To start this wizard:
• On the installation CD, go to the directory \install\jinstall\
<version> and run the file [Link] or [Link].
The setup wizard is then being prepared.
After completing the preparations, the Welcome dialog of the setup wizard
appears:

• Click on [ Nex t >] .

If you do not wish to continue the installation, you can click on [ Can c el ] either
here or in any of the subsequent masks to cancel the procedure.
At several points during the installation procedure you can click on [ < B ac k ] to
return to the previous screen.
In the next screen you can define the directory into which you want to install
J/Install. In the following sections, this directory is referred as
%JINSTALL_ROOT%:

• Accept the current selection or select another directory. Click on [ Nex t >] .

4 Reference and Using – User Guide Document version: 002

Installing J/Install

J/Install
In addition, logging information can be written to the Windows event log (check
box Windows Event Log), and already existing log files can be backed-up
before being overwritten by storing them in subfolder history using the
filename pattern YYYYMMDD_HHMMSS_jinstall.log (check box Log file
history).

• Accept the current selection or select another directory. Click on [ Nex t >] .
The setup wizard then displays the gathered information.

If you agree with the displayed information:

• Click on [ Nex t >] .
J/Install will then be installed into the specified directory.
During this process, an information screen shows how the procedure is
processing and the names of the various files that ar ebeing installed.

Document version: 002 Reference and Using – User Guide 5

Installing with J/Install
J/Install

J/Install can optionally be called immediately after installing it.

While J/Install is running, the setup program is waiting in the background until
J/Install has finished:

After finishing the installation and the optional call of J/Install, the dialog
indicating the completion of the entire setup procedure, is displayed:

6 Reference and Using – User Guide Document version: 002

Installing J/Install

J/Install
• Click on [ F i n i s h ] to finally complete the installation.

Unattended installation of J/Install

You can install J/Install without user interaction (unattended).
For unattended processing you must pass the following parameters when you
call the installation program of J/Install:

[Link] -q -varfile <response file> [-V<Variable>=<value>]

or
[Link] -q -varfile <response file> [-V<Variable>=<value>]

Call parameters -q
Installation without user interaction.
-varfile <response file>
Response file for the unattended installation procedure. With each
manual (attended) installation, this file is created automatically in
subdirectory .install4j using filename [Link].
-V<Variable>=<Value>
Optional parameter.
Overwriting one of the following user-specific variables of the <response
file>:

Variable Meaning
[Link] overwrites the installation directory
[Link]$Boolean defines whether a passed control file shall be executed
('true') or not ('false')
[Link] overwrites the control file
[Link]$Boolean specifies whether the logging information will be written
additionally into the Windows event log ('true') or not
('false')

Document version: 002 Reference and Using – User Guide 7

Installing with J/Install
J/Install

Variable Meaning
[Link]$Boolean specifies that an already existing log file [Link] is being
copied into folder ../history using the filename pattern
YYYYMMDD_HHMMSS_jinstall.log ('true') or not ('false)

Example 1-1 Sample call

[Link] –q –varfile c:\[Link] -[Link]=c:\jinstall -
[Link]=c:\[Link]

or
[Link] –q –varfile c:\[Link] -[Link]=c:\jinstall -
[Link]=c:\[Link]

Updating J/Install
During execution of the setup program, J/Install can be updated as follows:
• a file with name [Link] exists in the setup directory of J/Install
besides the setup files [Link] or [Link], respectively,
• a file with name [Link] exists in the same directory where the
control XML or PAR files are located.
The file [Link] is a ZIP archive that will be unpacked to directory
%JINSTALL_ROOT%. Files to be deleted can be specified within file
[Link] that is located in the root of file [Link]. Each file
that shall be deleted, is specified relative to folder %JINSTALL_ROOT% in a
separate line.

After installation
The Windows Registry
The J/Install settings in the Registry are located in the Registry directory
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\JInstall\
CurrentVersion.

Parameters Description
Build internal release representation with structure x.y.z.b
EventLog Logging to Windows event log ("True", "False")
Root Installation folder
Release external release representation with structure Vx.y/zz
(Build bbbbbb)

Example 1-2 Windows Registry

[HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\JInstall\CurrentVersion]
"Build"="4.0.0.2046"
"EventLog"="False"
"Root"="C:\\JINSTALL"
"Version"="V4.0/00 (Build 002046)"

8 Reference and Using – User Guide Document version: 002

Installing J/Install

J/Install
The environment variables

Environment variable Description

JINSTALL_ROOT Installation folder

JINSTALL_JAVAHOME refers to the installed JRE (only if [Link] is being

used)

Example 1-3 environment variables

JINSTALL_ROOT=c:\jinstall
JINSTALL_JAVAHOME=c:\jinstall\jre

The directory structure

The installation procedure of J/Install results in the directory structure within
the installation directory below:
.install4j
Information regarding deinstallation of J/Install
bin
Tools
bin\erunt
backup/restore of Windows Registry
bin\fallback
Files for fallback in case of system error
bin\tuneos
Operating system and user configuration
bin\proclassic
ProClassic files
example
Sample files
history
History of log files
jre
Java Runtime Environment
lib
Program libraries of J/Install
template
Template files

Document version: 002 Reference and Using – User Guide 9

Installing with J/Install
J/Install

Running J/Install
The parameters with which %JINSTALL_ROOT%\bin\[Link] can be
started are described below:
Call parameters --[Link]
Definition of value of format ’Type|File|Path|Value’ that is written in cas
of a reboot (optional). The reboot is not carried out, but has to be started
by another (external) process after evaluating the written value.
More information about the value parts Type, File, Path and Value is
provided in section "The command ModifyValue" on page 2-142.
--[Link]
Definition of value of format ’Type|File|Path|Value’ that is written in case
of no reboot (optional).
More information about the value parts Type, File, Path and Value is
provided in section "The command ModifyValue" on page 2-142.
--[Link]
Definition of value of format ’Type|File|Path|Value’ that is written instead
of a reboot (optional). The reboot is not carried out, but has to be started
by another (external) process after evaluating the written value.
More information about the value parts Type, File, Path and Value is
provided in section "The command ModifyValue" on page 2-142.
--[Link]
Definition of value of format ’Type|File|Path|Value’ that is written in case
of no relogon (optional). Nähere Informationen zu den
More information about the value parts Type, File, Path and Value is
provided in section "The command ModifyValue" on page 2-142.
-f, --file <filename>
Specification of PAR or XML file incl. path or package folder.
For more detailed information about the structure and on using PAR or
XML files, see section "The file [Link]" on page 1-14 and in section
"The file [Link]" on page 1-13.
-h, --help
Lists the call parameter (optional).
--nocancel
Supresses displaying of button [ Can c el ] (optional).
--optimize
Optimization of entry PendingFileRenameOperations of Windows
Registry database. While considering additional version information,
multiple entries will be deleted (optional).
--[Link]
Specification of a run for checking packages that shall be processed
(optional).

10 Reference and Using – User Guide Document version: 002

Running J/Install

J/Install
--[Link]
Suppresses deletion of successful processed packages (optional)
--[Link]
Specification of a package run (optional).
-q, --quit
Starting of a unattended installation without console output (optional)
--[Link]
Initiation of specified restarts at the end of installation (optional).
--shortversion
For a ProClassic installation software release numbers will be displayed
shortened if the minor release number is '00' (optional).
-s, --source <directory name>
Specification of the CurrentSource directory (optional).
-t, --test
Requesting command confirmations for testing purposes (optional).
-u, --unattend
Definition of an unattended installation (optional).
-v, --variable <name>=<value>
Definition of one or more user-specific variables (optional).

Provided parameter values

The values passed here overwrite the values that were defined for these
variables in the Variables section of the [Link] file. For more
information about the [Link] file, see section "The file [Link]"
on page 1-13.

Note
When using the call parameter -q or --quiet, the call parameter -u or --
unattend is not being evaluated.

Example 1-4 Sample call of J/Install

Sample call of J/Install:
[Link] -f c:\install\custom\[Link] -u -v HW=c:\install\hw -v
CUSTOM=c:\install\custom -v REG=c:\install\reg

Sample call of a package run:

[Link] --[Link] -f c:\package -u

Sample call of a check run for packages to be processed:

[Link] --[Link] -f c:\package -q

Document version: 002 Reference and Using – User Guide 11

Installing with J/Install
J/Install

Administrative rights
Since for the most system or software modifications administrative rights are
required, J/Install should be run under an account that has been granted
administrative rights. If the user that is currently logged in does not have
these rights, J/Install can be started using the identity of an administrator via
the PCRunAs tool (see "Running programs under a different user" on
page 1-26).

12 Reference and Using – User Guide Document version: 002

J/Install files

J/Install
J/Install files
In this section you will find the files that are written, required and evaluated by
J/Install.

The file [Link]

The [Link] file is the control file for automatic installation with
J/Install. It consists of the sections:
• Variables (optional)
• Status (optional)
• Requirement (optional)
• Sequence
Template for file [Link]:

<?xml version="1.0" encoding="utf-8"?>

Attribute version of root element JInstall specifies the version of J/Install that is
required for processing this control file. The version representation is expected
in internal formatting (x[.y[.z[.b]]]).
The elements in the various sections use user-specific variables and control
the execution of J/Install.
These sections and their elements are described in chapter "J/Install
reference" on page 2-1.
Standard entities Some characters are not permitted within elements of XML documents but
must be replaced by specific entity sequences that are called entity references.
An entity reference starts with an '&' character (ampersand) followed by a
specific code and is closed with a semicolon.
The five most often used standard entity references in XML are:

Sign Entity reference Meaning

< < less than
> > greater than
& & ampersand or ‚and’ sign
' ' apostrophe
" " quotation mark

All of these characters have a specific meaning within the syntax of XML code:
the characters ’<’ and ’>’ enclose tag names; the values of attributes are often
given using quotation marks or are enclosed using apostrophes; and the
character ‚&’ is used to identifiy entity references.

Document version: 002 Reference and Using – User Guide 13

Installing with J/Install
J/Install

The file [Link]

The process of a J/Install run is being logged in file [Link]. This file is
created new or overwritten with each call of J/Install. An already existing log
file will be copied into subdirectory history. For more detailed information
about the operational concept, see section "Logging" on page 1-28.
If your [Link] file uses the 'TuneOs' task, then you may also have
another file logging changes made on the system. See section "Logging" on
page 1-28 for more details.

The file [Link]

The call parameters of J/Install can be stored in a file using properties
formatting and are provided to J/Install. Default values are displayed in bold.

Job name Type Value Description

cancel boolean true Display of [Cancel] button
false no display of [Cancel] button
[Link] string Type|File|Path| Value that is written instead of
Value reboot. For more detailed
information about value parts, see
the section "The command
ModifyValue" on page 2-142.
[Link] string Type|File|Path| Value that is written instead of no
Value reboot. For more detailed
information about value parts, see
the section "The command
ModifyValue" on page 2-142.
[Link] string Type|File|Path| Value that is written instead of
Value relogon. For more detailed
information about value parts, see
the section "The command
ModifyValue" on page 2-142.
[Link] string Type|File|Path| Value that is written instead of no
Value relogon. For more detailed
information about value parts, see
the section "The command
ModifyValue" on page 2-142.
file string any J/Install control file
optimize boolean true Optimization of entry
PendingFileRenameOperations of
Windows Registry database.
false no optimization of entry
PendingFileRenameOperations of
Windows Registry database.
[Link] boolean true Check run of packages to be
executed.
false no check run of packages to be
executed

14 Reference and Using – User Guide Document version: 002

J/Install files

J/Install
Job name Type Value Description
[Link] boolean true Do not delete successful processed
packages
false Delete successful processed
packages
[Link] boolean true Package run
false no package run
quiet boolean true unattended processing without
console output
false processing with console output
[Link] boolean true Initiation of specified restarts at the
end of installation
false Initiation of specified restarts at
time of request
shortversion boolean true shortened display of software
release number for a ProClassic
installation
false no shortened display of software
release number for a ProClassic
installation
source string any Specification of the CurrentSource
directory
unattend boolean true unattended procedure
false manual procedure
test boolean true command confirmation for test
purposes
false Normal flow
variable.<name> string any Definition of a user-specific variable
version string any Version in internal representation

Example 1-5 Example for file [Link]

Example 1-6 Sample call using the [Link] file

[Link] -f c:\[Link]

Document version: 002 Reference and Using – User Guide 15

Installing with J/Install
J/Install

The file [Link]

The [Link] file contains details of the files and directories
that are important for the installation and the system restart. It is being created
during the first start. The file is neither deleted, nor edited nor re-created as a
result of a reboot or relogon, resp., in the [Link] flow.
The file [Link] contains the following entries:

Job name Type Value Description

cancel boolean true Display of [Cancel] button
false no display of [Cancel] button
controlfile string any J/Install control file
currentdate string any Date using format YYYY-MM-
DD
currentsource string any Definition of the current
source directory
currenttime string any Time using format HH:MM
errortext string any Error text of command Exit
exitcode integer 0-x ExitCode of J/Install
[Link] string Type|File|Path| Value that is written to the
Value specified file if no reboot is
carried out.
[Link] string Type|File|Path| Value that is written to the
Value specified file if the reboot
shall be started by an
external process.
[Link] string Type|File|Path| Value that is written to the
Value specified file if no relogon is
carried out.
[Link] string Type|File|Path| Value that is written to the
Value specified file if the relogon
shall be started by an
external process.
fallbackreboot boolean true Reboot after restoring of
Fallback information
false no reboot after restoring of
Fallback information
fallbacktask boolean true current task is Fallback task
false current task is no Fallback
task
installdir string any J/Install installation (target)
dir
lastselecteddir string any last directory that has been
selected using the GetSource
command

16 Reference and Using – User Guide Document version: 002

J/Install files

J/Install
Job name Type Value Description
logfile string any log file ([Link])
nexttask string any Task that is being processed
immediately after restart
optimize boolean true Optimization of entry
PendingFileRenameOperatio
ns of Windows Registry
database.
false Optimization of entry
PendingFileRenameOperatio
ns of Windows Registry
database.
[Link] boolean true Check run of packages to be
executed.
false no check run of packages to
be executed
[Link] string any Folder with unpacked
package content
[Link] string any File name
[Link] string any Package name (filename
without extension)
[Link] boolean true Package run
false no package run
[Link] string any Folder with packages
[Link] integer 0,2,3,6,7 or >100 0 - no error
2 - processed with error
3 - processed with error but
successful fallback
6 - not yet processed
7 - processing
>100 - finished with project-
specific exit
prosetup boolean true Call via ProSetup
false Normal flow
quiet boolean true unattended processing
without console output
false processing with console
output
[Link] boolean true Initiation of specified restarts
at the end of installation
false Initiation of specified restarts
at time of request

Document version: 002 Reference and Using – User Guide 17

Installing with J/Install
J/Install

Job name Type Value Description

[Link] booelan true Restart is to be carried out
false no restart required
[Link] string any Domain
[Link] string Type|File|Path| Value that is written instead
Value of no reboot/relogon.
[Link] string Type|File|Path| Value that is written instead
Value of reboot/relogon.
[Link] string any password
[Link] boolean true secret storing
false no secret storing
[Link] string any Username
[Link] string REBOOT Reboots the system
RELOGON Logs off a user and then logs
on
[Link] integer any vertical screen size
[Link] integer any horizontal screen size
[Link] string any Shell folder "AppData" of
current user
[Link] string any Shell folder "Desktop" of
current user
[Link] string any Shell folder "Programs" of
current user
[Link] string any Shell folder "Start Menu" of
current user
[Link] string any Shell folder "Startup" of
current user
[Link] string any Common shell folder
"AppData" of all users
[Link] string any Common shell folder
"Desktop" of all users
[Link] string any Common shell folder
"Programs" of all users
[Link] string any Common shell folder "Start
Menu" of all users
[Link] string any Common shell folder
"Startup" of all users

18 Reference and Using – User Guide Document version: 002

J/Install files

J/Install
Job name Type Value Description
shortversion boolean true shortened display of software
release number for a
ProClassic installation
false no shortened display of
software release number for
a ProClassic installation
status string END J/Install finished
END_REBOOT terminates J/Install and
reboots the system
REBOOT reboot within J/Install process
END_RELOGON terminates J/Install and
reboots the system and
relogon
RELOGON relogon within J/Install
process
test boolean true command confirmation for
test purposes
false Normal flow
unattend boolean true unattended procedure
false manual procedure
variable.<name> string any Definition of a user-specific
variable
version string any Version in internal
representation
versionfile string any version file
([Link])
[Link] integer 0,1 current Windows setting of
AutoAdminLogon
[Link] string any current Windows setting of
DefaultDomain
[Link] string any current Windows setting of
DefaultPassword
[Link] string any current Windows setting of
DefaultUsername
[Link] integer 0,1 current Windows setting of
ForceAutoLogon
[Link] string any current Windows setting for
DefaultPassword within the
secret area

Document version: 002 Reference and Using – User Guide 19

Installing with J/Install
J/Install

The file [Link]

The properties file [Link] is used for version administration
for the various products. The entries are saved in the format
<Name>=<Value>
. The name uniquely identifies an entry. If an entry with this name already
exists the existing entry or value is replaced, otherwise a new entry is created
in the file.

Example 1-8 Example of file [Link]

JInstall=4.0.0.2046

20 Reference and Using – User Guide Document version: 002

Processing of packages

J/Install
Processing of packages
Besides using control files in XML to run installations, J/Intall provides a
package mode that analyzes packages and processes them if they are located
within a specific folder.
A package is a ZIP file that contains a control file [Link] in its root.
Optionally this ZIP file can contain additional files that are referred by the
control file [Link]. A package or the commands specified in main
area Sequence, respectively, are carried out if the specified conditions in main
area Requirement are met.

Example 1-9 Sample package [Link]

[Link]
[Link]

<Sequence>
<Decompress>
<Source>{I:[Link]}\[Link]</Source>
<Destination>c:\</Destination>
<Type>ALWAYS</Type>
</Decompress>
</Sequence>
</JInstall>

Use the following call to check if packages are present:

jinstall --[Link] --file "<Package folder>" --unattend

Example 1-11 Sample call of package check

jinstall --[Link] --file "%JINSTALL_ROOT%\package" --unattend

A return code of '6' indicates that at least on package exists for which the
specified preconditions are met.

Document version: 002 Reference and Using – User Guide 21

Installing with J/Install
J/Install

The package run is started with the following call and does not require a
previous check:

jinstall --[Link] --file "<Package folder>" --unattend

Example 1-12 Sample call for package installation

jinstall --[Link] --file "%JINSTALL_ROOT%\package" --unattend

jinstall --[Link] --[Link] --file "%JINSTALL_ROOT%\package" --unattend

In both calls, the packages in the package folder are being analyzed in
alphabetical order. As soon as a package mets the specified preconditions, the
processing is stopped when using call parameter ’--[Link]’ or the
package is executed if using call parameter ’--[Link]’.
After successful processing, the package is going to be deleted as default
whereas it is being moved into folder <Package folder>\error if an error
occurred.
When using the call parameter '--[Link]' , the successful processed
package is not deleted but moved to folder <Package folder>\keep.
Then all remaining packages will be analyzed again in alphabetical order. This
procedure is repeated until no more packages are found or no remaining
package meets the specified preconditions.
When running a package its content is unpacked into a temporary folder and
the following variables will be provided:

Internal variable Description

[Link] Folder with unpacked package content
[Link] Filename
[Link] Name of package (filename without extension)
[Link] Folder with packages
[Link] Status of package

A return code of '0' indicates a successful run of all packages found; a return
code of '2' indicates that at least for one package an error occurred.
The state of a single package is indicated in a properties file with filename
<package folder>\status\<Package filename>-<package
status> and the following content:

File=<Filename of package>
Name=<Name of package>
Status=<Status of package>
Date=<Date of status change>
Time=<Time of status change>

The following states are possible:

State Meaning
0 no error occurred

22 Reference and Using – User Guide Document version: 002

Processing of packages

J/Install
State Meaning
2 processing errors
3 processing errors with sucessful fallback
6 not yet processed
7 currently being processed
>100 finished with project-specific exit

Using the main area Status, additional actions can be defined that are being
called with each status change of the corresponding package.
Note that a terminal should be taken out of service if packages to be processed
exist for this terminal. The terminal should be taken in service again only if no
errors occur while processing these packages.

Example 1-13 Sample script for package installation with prepending check
ECHO OFF
ECHO Checking packages
jinstall --[Link] --file "%JINSTALL_ROOT%\example\package" --unattend
IF NOT "%ERRORLEVEL%"=="6" GOTO END
ECHO Stopping application
<Stopping application>
ECHO Running packages
jinstall --[Link] --file "%JINSTALL_ROOT%\example\package" --unattend
IF NOT "%ERRORLEVEL%"=="0" GOTO END
ECHO Starting application
<Starting application>
:END

Document version: 002 Reference and Using – User Guide 23

Installing with J/Install
J/Install

J/Launch
J/Launch is used to perform an automatic installation controled by a predefined
J/Install script file.
Call You will find the file [Link] in directory %JINSTALL_ROOT%\BIN. The
executable requires a configuration file [Link] in the same
directory as file [Link].
Configuration The [Link] program configuration is created in the
parameters [Link] file.

Entry Meaning
Program specifies which program is to be started
Parameters spezifies call parameters of the program configured
with Program
Parameter.<.Selection> specifies calling parameter for the application specified
with program for a specific <Selection>
NoWaitDlg 0 - displays the wait dialog
1 - no display of the wait dialog
WaitDlgMessage referred text, that is displayed until the specified
program has started or a dialog of the specified title has
appeared (optional)
WaitDlgTerminatingWindowCaption refers title or part of title of a dialog that is required to
proceed the installation procedure (optional)
For the entries Program and Parameter, placeholders can be used. The
placeholders {RootSource} and {ExeSource} are available:

Wildcard characters Meaning

{RootSource} This placeholder points to the root directory of the data
medium from which [Link] was started.
{ExeSource} This placeholder references the directory containing the
called file [Link].
Sample content of file [Link]:

Program={RootSource}\install\jinstall\30.00\[Link]
Parameter=-q –varfile {ExeSource}\[Link] [Link]={RootSource}
–[Link]={ExeSource}
NoWaitDlg=1

Call parameters -nowaitdlg

The waiting message is being supressed (optional).
-waitdlg
The waiting message is being displayed (optional).
-par:<selection>
Using the parameter call "Parameter.<Selection>" instead of the default
call "Parameter" (optional).

Example 1-14 Sample call

[Link] -nowaitdlg -par:prosetup

24 Reference and Using – User Guide Document version: 002

J/Launch

J/Install
Example 1-15 [Link] of Example 1-14
Program={RootSource}\install\jinstall\30.00\[Link]
[Link]=-q -varfile {ExeSource}\[Link] -
[Link]={RootSource} -[Link]={ExeSource}

Return values Return values of the called program are being forwarded by J/Launch. For
J/Launch error codes the range 10000 to 10006 is being used.

Return value Description

0 successful calling and processing
10000 Unknown error
10001 Malformed call parameter
10002 file [Link] is missing
10003 file [Link] cannot be opened
10004 invalid [Link] entries
10005 error during system call
10006 entry "Parameter.<Selection>" does not exist in file
[Link]

Administrative rights
Since for the most system or software modifications administrative rights are
required, J/Launch should be run under an account that has been granted
administrative rights. If the user that is currently logged in does not have
these rights, J/Launch can be started using the identity of an administrator
via the PCRunAs tool (see "Running programs under a different user" on
page 1-26).

Document version: 002 Reference and Using – User Guide 25

Installing with J/Install
J/Install

Running programs under a different user

PCRunAs is a command-line tool that launces programms under a different
user account. You will find the file [Link] in directory
%JINSTALL_ROOT%\BIN.
Unlike the Windows tool [Link], it offers the following advantages:
• All required settings are carried out using the command line.
• The password to be used is provided encrypted.
• The application to be called can be run in a synchronized or asynchronized
way.
• The application to be called can be run in a normal window or minimized.
• With synchronize operation, PCRunAs will return the exitcode of the called
application.

Call parameters /u[ser] <user name>

Specification of the user account to be used
/p[assword] <password>
Specification of the encrypted password; the encrypted password can
be created using the tool %JINSTALL_ROOT%\BIN\[Link] .
/a[pplication] "<application>"
Specification of the application to be called including call parameters;
quotation marks in the application specification string have to be
masked with \" (leading backslash; see sample call below).
/m[ode] s[ynchronous]|a[synchronous]
Specification of execution mode (optional)
s[ynchronous] - synchronous execution
a[synchronous] - asynchronous execution (default)
/w[indow] 1|0
Specification of presentation mode (optional)
1 - normal presentation mode (default)
0 - minimized presentation mode
/e[rror] <file>
Specification of a file that will be created in case of errors (optional).

Example 1-16 Sample call

[Link] /user wn_application /password CB81E16A2C5E376D76F0A1AC775D1A23
/application "%JINSTALL_ROOT%\bin\[Link] /c \"HKEY_LOCAL_MACHINE\SOFTWARE\
Wincor Nixdorf\ProTopas\CurrentVersion\CCOPEN\RESTART\DEFAULTS\" MAXREBOOT 3"
/mode synchronous

Return values Return values of the called application are being forwarded by PCRunAs. For
PCRunAs error codes the range 10000 to 10004 are being used.

26 Reference and Using – User Guide Document version: 002

Running programs under a different user

J/Install
Return value Description
0 successful calling and processing
10000 Application could not be started
10001 Unknown error
10002 Malformed call parameter
10003 Specification of user or password is missing
10004 Specification of application is missing

Document version: 002 Reference and Using – User Guide 27

Installing with J/Install
J/Install

Logging
Logging is carried out using the library log4j, that differentiates messages as
DEBUG, INFO, WARN, ERROR or FATAL.
The configration of log4j is stored in folder %JINSTALL_ROOT%\LIB in file
[Link].
In the configuration file a level (message scope) and one or more appender
(output medium) can be assigned to a logger.
For a level it is differentiated by order of importance (falling number of
messages) between ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL
and OFF. In each level all messages of the specified level and all more
messages of more important levels are being logged.
For each appender a layout (output format) can be specified that formats the
message.

[Link]=Level, Name of appender, ...

[Link] of appender=Appender class
[Link] of [Link]=Layout class

After running an installation with activated Windows event logging, the file
[Link] has the following content:

[Link]=INFO, File, EventLog

#[Link]=ALL, File, EventLog

[Link]=[Link]
[Link]=${jinstallRoot}
[Link]=true
[Link]=[Link]
[Link]=%d{HH:mm:ss} %-5p %m%n
#[Link]=%d{ISO8601} %-5p %C [%M,%L] %m%n

[Link]=[Link]
[Link]=[Link]
[Link]=%m\n

For logger rootLogger the level INFO and the appender File and Eventlog are
specified, whereas both appender use the PatternLayout to format the
messages. Appender Eventlog provides no more additional configuration
where as appender File provides the following options:

Option Value Meaning

Dir any Folder into which the log file [Link] is written to
History true Backup of log file [Link] as file
YYYYMMDD_HHMMSS_jinstall.log in sub folder history before
overwriting it
false Overwriting log file [Link] without backup.

28 Reference and Using – User Guide Document version: 002

Logging

J/Install
With using option ConversionPattern of PatternLayouts the output format can
be specified using patterns similar to the C function printf, using the
following abbreviations:

Abbrevi
ation Description
C class name;
the output can be limited by using a decimal constant within curly brackets. With a
set limitation the number of components starting from the right are printed.
Example: The class [Link] is printed as SomeClass using pattern
%C{1}.
d date;
the date format can be specified in culry brackets, ad default the format as specified
with ISO8601 is being used.
The format is applied similar to the Pattern string of the SimpleDateFormats:
y - years
m - months
d - days
h - hours
m - minutes
s - seconds
S - milliseconds
Example: The date 15.09.2011 [Link] is printed as 2011-09-15 11:55 using the
specified pattern %d{yyyy-MM-dd HH:mm}.
L line number
m Message
M MethodName
n carriage return
p Level
% percentage sign

Each abbreviation must be prefixed with a percentage sign ('%').

Optionally the output formatting can be specified between percentage sign and
abbreviation.

%-[Link]

A minus sign ('-') following the percentage sign indicates a text alignment of the
right. Then a minimum length is specified. If the output is shorter than it is filled
with spaces.
Starting with a dot ('.') a maximum length can be specified. Longer outputs are
being cut down to the maximum.
Examples:

%20M Left justified with a minimum of 20 characters

%-20M Right justified with a minimum of 20 characters
%.30M Maximum output of 30 characters

Document version: 002 Reference and Using – User Guide 29

Installing with J/Install
J/Install

%20.30M Left justified with a minimum of 20 characters and a maximum of 30 characters

%-20.30M Right justified with a minimum of 20 characters and a maximum of 30 characters

Note
To downtrack problems it is recommended to remove the comment signs for
lines markes as comment in the provided [Link] and to mark
the previous line as comment in order to log extensive information.

In the configuraton file, all appender that are provided for log4j can be used, for
example FileAppender, RollingFileAppender, and all layouts, for example
XMLLayout, HTMLLayout can be used.

30 Reference and Using – User Guide Document version: 002

J/Install
2 J/Install reference

This section describes the J/Install commands. It is a complete command

reference for the control file jinstall.

Element identification
The highlighted elements are mandatory elements. Default values are
displayed in bold.
The column V describes the J/Install version until or from which version the
respective element or command is supported. „ –1.3“ means, that the
element is supported by all versions up to the displayed version; “1.4+”
means the element is supported by the displayed version and all later
versions.

In this chapter you will find information about the following topics:
Changes regarding previous releases 33

Variables 45

The main area "Variables" 46

The main area "Status" 47

The action Write .................................................................................................... 47

The main area "Requirement" 49

The main area "Sequence" 50

The command AskUser ......................................................................................... 53

The command CheckPassword ............................................................................ 55
The command Compress ...................................................................................... 56
The command Condition ....................................................................................... 58
The command ConfAutologon .............................................................................. 83
The command ConfNonAdmin .............................................................................. 84
The command CopyFile ........................................................................................ 86
The command CreateDir ....................................................................................... 88
The command CreateList ...................................................................................... 89
The command CreateShortcut .............................................................................. 90
The command Decompress .................................................................................. 91
The command Definition ....................................................................................... 94
The command Delete .......................................................................................... 101
The command DeleteRegistryKey ...................................................................... 102
The command Dialog .......................................................................................... 103
The command Exception .................................................................................... 109
The command Execute ....................................................................................... 110
The command Exit .............................................................................................. 113
The command Extern .......................................................................................... 114
The command Fallback ....................................................................................... 117
The command GetSource ................................................................................... 119
The command GetTextFile .................................................................................. 121
The command GetToken .................................................................................... 122

Document version: 002 Reference and Using – User Guide 31

J/Install reference
J/Install

The command GetValue ......................................................................................123

The command Import ...........................................................................................125
The command Jre ................................................................................................126
The command Keep ............................................................................................128
The command Loop .............................................................................................129
The command LoopEnd ......................................................................................132
The command ModifyEnvironmentVariable .........................................................133
The command ModifyPendingFile .......................................................................135
The command ModifyString .................................................................................136
The command ModifyTextFile .............................................................................137
The command ModifyToken ................................................................................140
The command ModifyValue .................................................................................142
The command ModifyVariable .............................................................................145
The command OsBootLogo .................................................................................147
The command ProClassic ....................................................................................148
The command Register .......................................................................................159
The command Restart .........................................................................................160
The command Script ............................................................................................162
The command SetVariable ..................................................................................163
The command ShowMessage .............................................................................164
The command ShowTextFile ...............................................................................165
The command TuneOs ........................................................................................166
The command Wait ..............................................................................................168
The command WriteLog ......................................................................................169
The command WriteVersion ................................................................................170

Values and addressing of data 171

Using regular expressions ...................................................................................171

Using patterns ......................................................................................................172
Data access paths ...............................................................................................174
Error handling ......................................................................................................181

32 Reference and Using – User Guide Document version: 002

Changes regarding previous releases

J/Install
Changes regarding previous releases
V2.x -> V3.0 Compared to previous releases, the following incompatible changes have
been made with J/Install 3.0:
• The section ProSetup is no longer used.
• The command SetVariable was renamed to GetValue.
• The commands Reboot and Relogon have been merged to command
Restart.
• For command Execute, the elements <CopyRoot>, <AltTagFile>,
<AltTagFileContent>, <AltTagLabelContent>, <AltText>, <AltProgram>,
<AltVariable>, <AltUnattend>, <AltCopyRoot> and <AltParameter> are
omitted.
• For command Condition the elements <TrueBranch> and <FalseBranch>
have been renamed to <True> and <False>.
• The elements <SuccessCode>, <SuccessFile>, <ErrorCode>, <ErrorFile>
and <WaitFile> can only be used once per command. Multiple appliance
can be achieved by using the delimiter ‘|’ (pipe symbol).
• The property identifiers in file [Link] and thus, the
identifiers of internal J/Install variables have been changed.
V3.0 -> V3.1 Changes/Extensions:
• new command Definition
• new command Fallback
V3.1 -> V3.1/50 Changes/Extensions:
• replaced jRegistryKey and xFunction with JniWrapper
• now supporting Windows Registry types REG_MULTI_SZ and
REG_BINARY
V3.1/50 -> V3.2 Changes/Extensions:
• New call parameter -n/--nohistory
• New condition UserIsAdmin
V3.2/00 -> V3.2/10 Changes/Extensions:
• New properties in file [Link] ([Link],
[Link])
V3.2/10 -> V3.2/20 Changes/Extensions:
• changing directory structure of ProClassic CD; when using a product type
the directory structure below INSTALL\<Produkt> and INSTALL\
PRODUCTS\<Product> changes to <Type>\R<Version>
• extending ProClassic [Link] with unpacking of any update
archives
V3.2/20 -> V3.3 Changes/Extensions:
• New commands: CreateDir, GetToken, ModifyEnvironmentVariable,
ModifyString, ModifyToken, Script
• New conditions: ChecksumCheck, IsFalse, IsTrue, TokenExists,
VersionCheck

Document version: 002 Reference and Using – User Guide 33

J/Install reference
J/Install

• extending the commands GetValue, ModifyTextFile, ModifyValue with

element CaseSensitive
• extending the conditions StringCheck, ValueCheck and ValueExists with
attribute casesensitive
• extending the conditions ValueCheck and ValueExists with attributes token
and delimiter
• extending the command WriteLog with element AddVariables
• extending the condition FileExists with attribute type
• Command Decompress now supports the new types VERSION, MODSEG
and NOTEXISTS
• Command CopyFile now supports the new types VERSION, MODSEG and
NOTEXISTS
• Element Token of command GetValue now processes regular expressions
• Command ModifyValue now supports the PARAC file format
• Direct addressing of token position with commands GetValue and
ModifyValue must follow {TokenPos}<Position>
• Attribute and element specifications can be applied using lower or capital
letters.
• Element definitions can be applied as attributes
• Access of parameters ({I:<name>}) and variables ({V:<name>}) can use
lower or capital letters.
• Command Restart now supports the new mode NO.
V3.3 -> V3.4 Changes/Extensions:
• Command ProClassic now supports the new type
SOURCECORRECTION.
• Extending the commands CopyFile, Decompress and Delete with element
PendingFileHandling
• Command ProClassic does not supports the type JRE anymore.
• New command InstJre
• New command CreateShortcut
• New entries for file [Link] ([Link],
[Link], [Link], [Link],
[Link], [Link],
[Link], [Link],
[Link], [Link])
• The command Delete does not support element List any longer; a file list is
recognized by using prefix {List}.
• The command Decompress now supports processing text files that contain
the files to be decompressed.
• The command ModifyTextFile now supports processing text files that
contain the files to be changed.

34 Reference and Using – User Guide Document version: 002

Changes regarding previous releases

J/Install
• For the commands ConfAutologon, ConfNonAdmin and Restart the
password can be provided as plain text.
• The command Extern supports the submission of values during runtime
while running the task SetVariable.
• The command DeviceHandler is not supported any longer.
• The definitions FallbackValue and ImportFallbackInf are not supported any
longer.
• New definitions Variable and ProClassic
• Extending definitions Keep and KeepValue with attribute merge
• Extending definitions KeepValue by types PROPERTY, PCE and PARAC
• Extension of definition Fallback by the types ZIP and DECOMPRESS as
well as by the attributes root and prefix
• New commandline parameter --fallback
• Extending the command Fallback with element Reboot
• New condition VariableExists
V3.4/00 -> V3.4/01 Changes/Extensions:
• Extending the command Exit with element Text
V3.4/01 -> V3.5/00 Changes/Extensions
• Command ProClassic does not supports InstallShield scripts anymore.
• Extending the command InstJre with element File
• If an error occurs, an ERROR file is created containing an error description
and the ExitCode.
• In the dialog of command GetSource, an icon is provided to update the
folder structure.
• The command Execute can now run attended batch files using the program
[Link].
• Extending command Restart with mode YES
• During an unattended installation, mode ASK of command Restart is
treated similar to NO.
V3.5/00 -> V3.6/00 Changes/Extensions
• Extending the command Decompress with element PreserveDate
• Extending command CopyFile with elements PreserveDate and
PreserveAttribute
• Extending command GetSource with elements PreserveDate and
PreserveAttribute
• The default optimization of entry PendingFileRenameOperations of the
Windows registry at the end of J/Install has been removed. It can be now
activated by either the call parameters -o and --optimize or the entry
optimize in file [Link].
V3.6/00 -> V3.7/00 Changes/Extensions
• The element Variable of command ModifyVariable was renamed to Name.

Document version: 002 Reference and Using – User Guide 35

J/Install reference
J/Install

• Extending the command SetVariable with element Index

• Extending the command Script with element Return
• Extending the command Delete with element Backup
• Extending the command CopyFile with element Backup
• new conditions DateTimeCheck, DriveCheck
• new internal variables currentdate (date with format YYYY-MM-DD) and
currenttime (time with format HH:MM)
• New commands Register, CreateList
• Extending the command Decompress with element ResultFile
• Element Value of command WriteVersion is now optional
• Element Source of command CopyFile now supports processing of file lists
using the prefix {List}
• The PCRunAs tool allows the running of applications under another user
account.
V3.7/00 -> V3.8/00 Changes/Extensions
• Extending command Compress with elements Folder, Password and Type
• Extending command Decompress with elements Filter, Password and
PreserveAttribute
V3.8/00 -> V3.8/03 Changes/Extensions
• Extending command Extern with AskEncr functionality
V3.8/03 -> V3.9/00 Changes/Extensions
• optional logging of J/Install installations into the Windows Event log
• additional call parameters --shortversion, --nocancel
• Extending the command ConfAutologon with element Private
• Extending the command Restart with element Private
• Extending the command ConfNonAdmin with element Private
V3.9/00 -> V4.0/00 Changes/Extensions
• The conditions ValueCheck and ValueExists support XML files.
• The definitions KeepValue and Variable support XML files.
• The commands GetValue and ModifyValue support XML files.
• Using log4j for logging
• The root element Custom was renamed to JInstall
• Expanding the root element JInstall by attribute version
• Extending command Keep with type DELETE
• Extending command Fallback with type DELETE
• Extending command ModifyTextFile with elements Encoding, FileToAdd
and FileToAddEncoding
• Extending the command ShowTextFile with element Encoding

36 Reference and Using – User Guide Document version: 002

Changes regarding previous releases

J/Install
• Extending command WriteLog with elements Encoding and
AddLogFileContentEncoding
• Extending command Execute with elements LogFileEncoding,
ErrorLogFileContentToAddEncoding and LogFileContentToAddEncoding
• Extending command Restart with elements ExternTrue and ExternFalse
• Extending element Mode of command ModifyTextFile with entries
AddFileBegin, AddFileEnd, AddFileBefore and AddFileAfter
• new condition RestartCheck
• new main area Requirement
• new return codes 4, 5 and 6
• removed J/Install call parameters -o and --nohistory
• additional J/Install call parameter --[Link], --[Link],
--[Link], --[Link], --[Link],
--[Link] and --[Link]
• additional J/Install call parameter [Link], [Link],
[Link], [Link], [Link], [Link]
and [Link] in file [Link]
• Extending element Mode of commands ModifyValue, ModifyToken and
ModifyEnvironmentVariable with attributes TokenRemoveBegin,
TokenRemoveEnd, TokenRemoveAfter and TokenRemoveBefore
• Extending file [Link] of command ProClassic with
parameter version
V4.0/00 - > V4.1/00 Changes/Extensions
• Extending command ModifyTextFile with elements AddTextBegin,
AddTextEnd, AddTextBefore and AddTextAfter
• Command Script now allows use of commands Definition, Fallback, Keep
and ProClassic.
• The state of single J/Install packages is indicated in folder <Pacakge
folder>\status abgebildet.
• additional J/Install call parameter -q and --quiet
• Extending command Execute with elements TailFile,TailFileEncoding and
Output
• Extending commands Compress, CopyFile, CreateDir, CreateShortcut,
Decompress, Delete, GetSource, ModifyTextFile, ModifyValue,
OsBootLogo, WriteLog and WriteVersion with attribute fallback
• Extending command CreateList with elements Type and Name
• New commands GetTextFile, Loop, LoopEnd and Exception
• New loops Endless, Counter, FileExists and TextFile
V4.1/00 - > V4.2/00 Changes/Extensions
• Command InstJre removed
• New commands Jre and ModifyPendingFile
• Extending command Execute with element PendingFileHandling

Document version: 002 Reference and Using – User Guide 37

J/Install reference
J/Install

• Program JreUpdate allows updating the Java Runtime Environment.

V4.2/00 - > V5.0/00 Changes/Extensions
• New condition OsCheck
• Extending access to data of Windows Registry (<RegPath>)
• Additional J/Install call parameter --[Link]
• Additional entry [Link] in file [Link]
• New entries in file [Link] ([Link],
[Link])
• New variable [Link] to specifiy the date format of internal
variable currentdate
• New variable [Link] to specify time format of internal variable
currenttime
• New main area Status
• Extending commands Execute, Import and Register with element Access
V5.0/00 -> V6.0/00 Changes/Extensions
• New Default (FALSE) for element PreserveAttribute of command
Decompress
V6.0/00 -> V6.2/00 Changes/Extensions
• New condition TextFileCheck for command Condition
V6.2/00 -> V6.3/00 Changes/Extensions
• Extending check condition OsCheck of command Condition with new
operating system types in attribute name
• New loop type TokenString for command Loop
V6.3/00 -> V6.4/00 Changes/Extensionsn
• Task 'ProClassic': Device handling extended by CDM30_2 ->
HW_CashOut2, IDCC30 -> ContactlessCardReader.
• Task 'ProClassic': Installation units PCE/FLEX_RC_MANAGER,
PROFLEX_NDC and PROFLEX_NDC-KIT inserted.
• Task 'ProClassic': Installing on WN machines: if ProBase reports the receipt
printer PRR230 (thermal printer TH23 which prints on A4 sheets) then the
parameter LOGICAL_OPEN_NAME_REPLACEMENT is extended by
",PRD30>PRR230".
• Task 'ProClassic': Bug-fix in function parsing the file HW_CONF.INI: if the
file contains syntax errors (e.g. missing square bracket(s) in section
names), JInstall will log the error and stops the processing.
V6.4->V6.5 Changes/Extensions
• new command CheckPassword incl. new tool for checking password
• ProClassic task: new ProClassic components; following ProClassic
components were inserted:
– PROFLEX4_BASE (successor of PROTOPAS_BASE and
PROTOPAS_DEVSUITE)

38 Reference and Using – User Guide Document version: 002

Changes regarding previous releases

J/Install
– PROFLEX4_UI (successor of PCE/FLEX_UI component)
– PROFLEX4_TOOLING (successor of PCE/FLEX_TOOLING
component)
– PROFLEX4_RCM (successor of PCE/FLEX_RC_MANAGER
component)
– PROFLEX4_NDC (successor of PROFLEX_NDC component)
• ProClassic task: List of products based on ProTopas/Base extended; the
list PROCASH/IFX, PROCASH/TDC, PROFLEX/NDC,
PROTOPAS/CASHBOX, PROTOPAS/DEVSUITE, PROTOPAS/SHOP,
PROTOPAS/SLIMCASH, PROTOPAS/SUITE (a dummy product that was
introduced to simplify the customizing), SLIMCASH/TDC was extended by
three new products:
– PROFLEX4-OP,
– PROFLEX4-SDK,
– PROFLEX4-NDC

V6.5->V6.6 Changes/Extensions
• Extensions in command Fallback: introducing new property OmitRegistry
• Processing the ProClassic compoment XFS_ADDON:
– New parameters in [Link]:
proclassic.XFS_ADDON.DETECTION_PREFER (in addition to the
existing proclassic.XFS_ADDON.PREFERRED_LOGICALNAMES) and
proclassic.XFS_ADDON.DETECTION_IGNORE.
• Bug fix: logging information about ‘virtual’ products (e.g. PROFLEX4_ATM,
PROFLEX4_KIOSK) changed to avoid confusion in its interpretation
• Refactoring
• Task ProClassic: extending the format of [Link] files with the
capability to license more than one component version
V6.6->V6.7 Changes/Extensions
Tasks 'ConfAutoLogon' and 'ConfNonAdmin', attribute 'Private': Default value
changed to TRUE.
V6.7->V6.8 Changes/Extensions
• Tool [Link] updated to release 1.1/04.
• Declaration <Definition> / <Feedback> enhanced by type REG.
• Task 'Fallback': attribute 'OmitRegistry' removed
• Added new ProClassic components: PROFLEX4_DDC and
PROFLEX4_PCE.
• Task 'ProClassic': implemented support for cashout dispenser CDMV7
V6.8 -> V6.9/00 Changes/Extensions
• New feature: New condition <IsValidPassword>
• Improvement: New ProClassic component PROFLEX4_ISO8583

Document version: 002 Reference and Using – User Guide 39

J/Install reference
J/Install

• Improvement: Internal variable IsCommonPasswordAsk addedd. It is set if

the user is requestd to enter the password of the non-adminitrative user.
This variable can be avaluated using the [Link] file.
• Bug: task 'Jre' - JRE 8 can be installed without erros
• Removed: No further support of command InstJre, since this command was
already removed with J/Install V4.2 (InstJre was replaced by Jre).
• Improvement: Support of new ProClassic products which are based on
PROFLEX4_BASE component:
– PROFLEX4-DDC
– PROFLEX4-ISO8583
– PROFLEX4-PCE
• Improvement: [Link]' parameter CustomerChapter can hold
more than one feature entry.
Example:
[Link]=customizing,customizing2
• Internal change: File [Link] moved from the folder
%JINSTALL_ROOT% to %JINSTALL_ROOT%\bin.
• Improvement: command TuneOs was enhanced by the REG file
Windows_DesktopIcons_Remove.reg, which deletes all icons from the
desktop and deactivates the context menu of the desktop. The REG file is
part of the default set of Registry settings that are being processed with
activated TuneOS command.
• Improvement: Task 'Fallback': Reintroduction of attribute 'OmitRegistry'.
• Bug: tool [Link], which was being used by command <Fallback>
removed in V6.8, was added again to installation.
• New Feature: new command AskUser.
• New Feature: new command DeleteRegistryKey
• New Feature: new condition RegistryKeyExists
• Improvement: condition FileExists enhanced; list of entries can be provided
now
• Improvement: condition VariableExists enhanced; list of entries can be
provided now
• New Feature: New tools in the installation folder %JINSTALL_ROOT%\bin:
– [Link]
– [Link]
V6.9/00 -> V6.9/01 Changes/Extensions
• Improvement: Command 'TuneOs':
– File Windows_DesktopIcons_Remove.reg removed from
%JINSTALL_HOME%\bin\tuneos\user and from
%JINSTALL_HOME%\template\tuneos\user.
Reason: the reg file contained an entry for the 'Policies' regkey HKCU\
SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer which

40 Reference and Using – User Guide Document version: 002

Changes regarding previous releases

J/Install
cannot be processed by [Link] when the user is a standard
user.
– File Windows_DesktopIcons_Remove.reg inserted to
%JINSTALL_HOME%\template\tuneos\all. It writes in the regkey
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\
Explorer and thus removes desktop icons for ALL users on the machine.
HINT: this file is deployed in the template folder. It doesn't belong to
the default reg file set processed by J/Install. To activate the file the
customizer has to create an own [Link] file and insert
Windows_DesktopIcons_Remove.reg in there.
– File Windows_RecycleBinIconOnDesktop_Remove.reg inserted
again to %JINSTALL_HOME%\bin\tuneos\all and
%JINSTALL_HOME%\template\tuneos\all. It belongs to the
default set of reg files processed by J/Install, step 'TuneOs'.
V7.0/00 Changes/Extensions
• Installation precondition. When installing with [Link] then the JRE
that must already be installed on the target machine must have version 1.8
(previously: 1.6-1.7).
• Oracle JRE 1.8.0_112 integrated into [Link] installer. .
• Condition ’OsCheck’: Window 10 detection implemented.
• Task ’ModifyTextFile’: Parameter HideDetails inserted.
• New feature: PCI DSS compliance: Logging of the value of the [Link]
parameter [Link] removed. Affected files: [Link],
[Link]. Instead password, the information [Password
masked due to PCI DSS requirements] is logged.
• New feature: File DISKID from the CD's root folder is copied to the
J/Install's installation folder C:\JInstall.
• Improvement: Task ’TuneOS’: the default set of REG files processed by the
task was extended by the file
Windows_VSS_FilesNotToSnapshot.reg. This file, when processed
on Windows 7, inserts the following parameter to the Windows registry:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
BackupRestore\FilesNotToSnapshot]
"dieboldnixdorf-exclude-cccmos-files"=hex(7):...
The parameter name is irrelevant. What's most important is the parameter
value. It saves a list of files which should be excluded from creating shadow
copies done by Windows Volume Shadow Copy service (VSS).
• The value of the REG_MULTI_SZ parameter
dieboldnixdorf-exclude-cccmos-files is:
%PROTOPAS_ROOT%\work\[Link]
%PROTOPAS_ROOT%\work\[Link]
• Improvement: Task ’TuneOS’: registry parameters are written to Windows
using [Link] (instead of [Link]) to be able to log the changes
made in the Windows registry. Logging modifications is a PCI DSS
requirement.

Document version: 002 Reference and Using – User Guide 41

J/Install reference
J/Install

• Improvement: File %JINSTALL_ROOT%\bin\[Link] updated to

the version [Link] (timestamp: 29.09.2016).
• ProFlex4 installer. New [Link] parameter
’[Link]’ inserted.
• New feature: Task ProClassic; new processing mode: CONFIG. When
called in a separate J/Install run after installation, it executes a new
configuration of ProTopas Repository Manager.
To simplify the usage of the new mode the following new folder is created
on the target machine after installation: %JINSTALL_ROOT%\bin\
proclassic\config. It contains two files: [Link] and
[Link].
Call [Link] to configure Repository Manager anew.
V7.1/00 Changes/Extensions
• New feature. Task TuneOs: Support for installations on Windows 10 64-bit
implemented. Subfolder '10' can be used to store reg/cmd/inf file to be
processed only when installing on Windows 10.
• New feature. Task TuneOs : File Windows_DefinePowerPolicy.cmd
inserted the default set of 'user' TuneOs files. When processed it turns off
'Low battery notification' in Windows 'Power Options' (only for Windows
7/10 installations).
• New feature: New tool %JINSTALL_HOME%\bin\[Link].
Used in the script [Link] to delay ATM application start until the XFS
layer is initialized.
• New feature: New component PROFLEX4_XPRESSION implemented in
jinstall-engine. See also JINSTALL-87 IN DEV. In the component
installation sequence J/Install installs it after all other ProFlex4
components.
• Improvement: Task TuneOs: Files of type cmd64, reg64 and inf64
removed from processing. They were unnecessary and redundant.
• Improvement: Make some error messages appearing when regkey file are
invalid more understandable.
• Improvement: Task ConfAutologon: Remove task's password attribute
value from J/Install log to improve security.
• Improvement: Task ProClassic: Additionally to the naming convention
<feature-name>.ZIP custom feature files can now also use the naming
RTS_<feature-name>.ZIP (run-time) or KIT_<feature-name>.ZIP
(KIT installation).
• Improvement: File %JINSTALL_ROOT%\bin\[Link] updated to
the version [Link] (timestamp: 31.10.2016).
• Bug-fix: Task ProClassic: Set Windows environment variable COPYCMD
independent of Windows version on the target machine.
• Bug-fix: Fix problems which can appear when J/Install is used on systems
using localization other than English or German.
V7.2/00 Changes/Extensions
• New Feature: TuneOs for Windows 10: Turn off Windows Taskbar on ALL
screens for non-admin user.

42 Reference and Using – User Guide Document version: 002

Changes regarding previous releases

J/Install
• New Feature: TuneOs for Windows 10: Enable Task Manager's 'Always On
Top' option for non-admin user.
• Improvement: J/Install: Use latest CCCommon ([Link]).
• Bug-fix: ProCash and ProFlex4 product installations: Wrong handling of
J/Install parameter provided in '[Link]' in [Link].
V7.2/01 Changes/Extensions
• Improvement: Update 3rd-party dependencies to their newest versions.
• Improvement: Optimize J/Install condition 'IsValidPassword'.
V7.3/00 Changes/Extentions
• Improvement: Extend <Jre> task to support OpenJDK JRE installations
• [Link] installer: OpenJDK JRE version 8u151 integrated
(replaces previously used Oracle JRE).
V7.3/10 Changes/Extensions
• Manual extended.
• Improvement: [Link] installer: OpenJDK JRE version 8u161
integrated (replaces 8u151).
• Bug-fix: Null-pointer exception in J/Install's install4j script.
V7.3/20 Changes/Extensions
• Improvement: Task <ShowMessage>. Evaluate user feedback ([ OK ] or
[ C an c el ] button clicked in dialog).
• Improvement: Tasks <ProClassic> and <ConfNonAdmin>. Implemented
support for ProBase 1.4.
– Search in ..\Diebold Nixdorf\ProBase\... Registry section for
keys which were stored in older ProBase versions under ..\Wincor
Nixdorf\CSC-W32\... section.
– Add parameter Products in Registry in case it does not exist
• Improvement: Task <ProClassic>. For installations on WN machines, insert
new valid CashOut type: ’AFD’
• Improvement: Inserted [Link]'s new version 2.1.0 (proper
autologon configuration on 64-bit Windows systems).
• Improvement: Removed deprecated tool [Link] from J/Install
installation package.
V7.3/30 Changes/Extensions
• Improvement: Task <ProClassic>. New component PROFLEX4_ISO20022.
• Improvement: [Link] updated to the new version 1.2.0 supporting
ProBase 1.4.
• Improvement: [Link] updated to the new version [Link].
• Improvement: Task <ProClassic>. Support for ProBase 1.4 with new
Registry location in Diebold Nixdorf Registry key. Support for ProBase 1.4
on NSL hardware.
• Improvement: [Link] installer: OpenJDK JRE version 8u181
integrated.

Document version: 002 Reference and Using – User Guide 43

J/Install reference
J/Install

V7.4/00 Changes/Extensions
• Incompatible improvement: Usage of ’[Link]’ parameters in
[Link] customizing file changed. Parameter value must be
surrounded by double quotation marks.
• New Feature: TuneOs: Disable Internet Explorer Pinch-Zoom.
• Improvement: Rebranding in J/Install GUI. Legacy company name 'Wincor
Nixdorf' was replaced by 'Diebold Nixdorf'.

44 Reference and Using – User Guide Document version: 002

Variables

J/Install
Variables
Elements and attributs in the various main areas can contain variables using
the syntax {<Variable type>:<Variable name>}. These variable will be resolved
during runtime.
These variable types exist:

Type Meaning
E Environment variable
J Java System Property
I Internal variable
With internal variables you can access the corresponding entry in file
[Link]. In addition, the internal variables currentdate and currenttime
provide the current date and current time using the format YYYY-MM-DD or
HH:MM, respectively.
V User-specific variables
These variables can be defined in section Variables of file [Link] (see "The
main area "Variables"" on page 2-46) and can be set or modified using the
commands SetVariable and ModifyVariable. In addition, the format to be used by
variables currentdate and currenttime can be set using the user-specific
variables [Link] and [Link], respectively. J/Install uses
the SimpleDateFormat as provided by the JRE. A complete description can be
found here: [Link] class
[Link].

Document version: 002 Reference and Using – User Guide 45

J/Install reference
J/Install

The main area "Variables"

This section defines user variables and assigns values to them. The content of
the variables can be used in the sequence section (see section "The main area
"Sequence"" on page 2-50) using the character string
{V:<VariableName>}.
The placeholder {CurrentSource} can be assigned to a variable as a value.
This placeholder is initialized with the entry JInstallCurrentSource from
the [Link] file when J/Install is started.
User-specific variables can either be overwritten during the J/Install start or
specified for the first time via call parameters.
Element definitions
Name Type Value Meaning V
Name string any defines the name/designation of the variables. 1.0+
The following names are permanently
reserved for ProSetup:
HW = Hardware disk
REG = RegistrationKey disk
CUSTOM = Customizing disk
PROCLASSIC = ProClassic CD
If J/Istall is used together with ProSetup, the
name of the variable must not be longer than 8
characters.
Value string any This element defines the content of the variables. 1.0+

Example 2-1 Example for the use of the section Variables

<Variables>
<Variable>
<Name>CUSTOM</Name>
<Value>c:\install\custom</Value>
</Variable>
...
<Variable>
<Name>HW</Name>
<Value>c:\install\hw</Value>
</Variable>
</Variables>

46 Reference and Using – User Guide Document version: 002

The main area "Status"

J/Install
The main area "Status"
This area defines one or more actions, that will be processed if a J/Install
package status has changed.
The defined actions are going to be processed in the order they are defined in
section Status.

Example 2-2 Example for using area Status

<Status>
[Action(s)]
</Status>

The actions are specified with the following elements:

Element Meaning V
Write changes the parameter value of a file or in the Windows Registry; 5.0+
see "The action Write" on page 2-47

The action Write

Diese Aktion ändert einen Parameterwert in einer Datei oder in der
Windows-Registry.
Attributedefinitionen
Name Type Value Description V
type string INI INI file 5.0+
REG Registry
PROPERTY Properties file
PCE PC/E file
XML XML file
file string any File name 5.0+
HKCR or HKEY_CLASSES_ROOT
HKEY_CLASSES_ROOT
HKCU or HKEY_CURRENT_USER
HKEY_CURRENT_USER
HKLM or HKEY_LOCAL_MACHINE
HKEY_LOCAL_MACHINE
HKCC or HKEY_CURRENT_CONFIG
HKEY_CURRENT_CONFIG
HKU or HKEY_USERS
HKEY_USERS

Document version: 002 Reference and Using – User Guide 47

J/Install reference
J/Install

Name Type Value Description V

path string <IniPath> Refers to INI file 5.0+
<RegPath> Referse to Registry
<Property> Property of Properties file
<PcePath> Refers to PC/E file
<XmlPath> Refers to XML file
value string any Value to be set 5.0+

Example 2-3 Example for using action Write

48 Reference and Using – User Guide Document version: 002

The main area "Requirement"

J/Install
The main area "Requirement"
This area specifies one or more conditions that have to be meet in order to
process the main area Sequence.
All commands except commands Definition, Exit, Fallback, Keep, ProClassic
and Restart, can be used. All commands will be processed in the order given
by section Requirement.
The processing of specified commands is stopped if one condition was not
met.

Example 2-4 Example for the use of the section Requirenment

<Condition description="Condition to check the os">

Document version: 002 Reference and Using – User Guide 49

J/Install reference
J/Install

The main area "Sequence"

The Sequence section controls the J/Install flow, whereby the specified
commands are processed in the sequence in which they are specified in the
section Sequence.
The supported commands are (in alphabetical order):

Command Meaning Parameters V

AskUser displays a user information and see "The command AskUser" 6.9+
requests the user to either click on page 2-53
Yes, No or Cancel
CheckPassword checks a given password for see "The command 6.5+
compliance with password CheckPassword" on
policies on machine page 2-55
Compress creates a compressed file in ZIP see "The command 1.0+
format Compress" on page 2-56
Condition execution of commands due to see "The command 1.5+
certain conditions Condition" on page 2-58
ConfAutologon set Autologon for Windows see "The command 3.0+
ConfAutologon" on page 2-83
ConfNonAdmin configuring the application see "The command 3.0+
usage without having ConfNonAdmin" on
administrative rights page 2-84
CopyFile copies files see "The command CopyFile" 1.0+
on page 2-86
CreateDir creates an applied directory see "The command 3.3+
CreateDir" on page 2-88
CreateList creates a list of filenames from see "The command 3.7+
files in a given folder CreateList" on page 2-89
CreateShortcut creates a shortcut for an see "The command 3.4+
application CreateShortcut" on
page 2-90
Decompress decompresses files that exist in see "The command 1.0+
ZIP or JAR format Decompress" on page 2-91
Definition definitions for commands see "The command 3.1+
Fallback and Keep Definition" on page 2-94
Delete deletes files or directories see "The command Delete" 3.0+
on page 2-101
DeleteRegistryKey deletes one or more Registry see "The command 6.9+
keys DeleteRegistryKey" on
page 2-102
Dialog interprets a dialog file see "The command Dialog" 3.0+
on page 2-103
Exception stops processing of control file see "The command 4.1+
with an error Exception" on page 2-109
Execute executes a command see "The command Execute" 1.0+
on page 2-110
Exit stops the processing of the see "The command Exit" on 3.0+
control file page 2-113

50 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Command Meaning Parameters V
Extern processes externally specified see "The command Extern" 3.0+
J/Install commands on page 2-114
Fallback saves and restores Fallback see "The command Fallback" 3.1+
information on page 2-117
GetSource requests a data medium see "The command 1.0+
GetSource" on page 2-119
GetTextFile reads a line from a text file and see "The command 4.1+
assigns it to a user-specific GetTextFile" on page 2-121
variable
GetToken reads a token from a token list see "The command 3.3+
and assigns this token a GetToken" on page 2-122
user-specific variable
GetValue reads a parameter value from see "The command 3.0+
file or Windows Registry GetValue" on page 2-123
Import imports Registry or INF files see "The command Import" 3.0+
on page 2-125
Jre installs or updates a JRE see "The command Jre" on 4.2+
version page 2-126
Keep stores information for restoring see "The command Keep" on 3.0+
page 2-128
Loop carries out commands in a loop see "The command Loop" on 4.1+
page 2-129
LoopEnd finishs a complete loop or a see "The command LoopEnd" 4.1+
single loop run on page 2-132
ModifyEnvironment changes a system-specific or see "The command 3.3+
Variable user-specific environment ModifyEnvironmentVariable"
variable on page 2-133
ModifyPendingFile changes Registry entry see "The command 4.2+
PendingFileRenameOperations ModifyPendingFile" on
page 2-135
ModifyString modifies a string see "The command 3.3+
ModifyString" on page 2-136
ModifyTextFile changes texts in files see "The command 2.1+
ModifyTextFile" on
page 2-137
ModifyToken modifies a token list see "The command 3.3+
ModifyToken" on page 2-140
ModifyValue sets a parameter value in file or see "The command 2.0+
Windows Registry ModifyValue" on page 2-142
ModifyVariable changes or sets a user-specific see "The command 2.2+
variable ModifyVariable" on
page 2-145
OsBootLogo replaces the boot image of the see "The command 3.0+
operating system OsBootLogo" on page 2-147
ProClassic installs ProClassic applications see "The command 3.0+
ProClassic" on page 2-148
Register registers OCX files, DLLs or see "The command Register" 3.7+
fonts with the system on page 2-159

Document version: 002 Reference and Using – User Guide 51

J/Install reference
J/Install

Command Meaning Parameters V

Restart logs out and logs on users or see "The command Restart" 3.0+
restarts the system on page 2-160
Script executes a J/Install file see "The command Script" on 3.3+
page 2-162
SetVariable sets a user-specific variable see "The command 3.0+
SetVariable" on page 2-163
ShowMessage displays a message with a see "The command 3.0+
confirmation button ShowMessage" on
page 2-164
ShowTextFile shows a text dialog see "The command 3.0+
ShowTextFile" on page 2-165
TuneOs configures the operating system see "The command TuneOs" 3.0+
for all users or for a specific user on page 2-166
Wait waits for keystroke or timeout see "The command Wait" on 1.4+
page 2-168
WriteLog writes log file entries see "The command WriteLog" 1.0+
on page 2-169
WriteVersion writes an entry to the see "The command 1.0+
[Link] WriteVersion" on page 2-170
file

52 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command AskUser
The command AskUser is used to provide a user input. It opens a dialog box
provideing three buttons for user interaction:
• Yes
• No
• Cancel
The response as selected by the user („Yes“, „No“ or „Cancel“) is stored with
the internal J/Install variable [Link] and can be evaluated with the
file [Link] after the AskUser was called.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 6.9+

ignoreerror boolean TRUE Errors are ignored during processing 6.9+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Name string any Text mit der Frage, die an den 6.9+
Benutzer gerichtet ist.
Caption string any Text für den Titel des Dialogfeldes. 6.9+

Example 2-5 Beispiel für den Einsatz des Befehls AskUser

<AskUser
description="Ask user how we should deal with the items that should be
deleted.">
<Caption>Handling unwanted items</Caption>
<Text>J/Install detected one or more disturbing folders, registry keys and/or
environment variables:
- Folders: '{V:[Link]}'
-Regkeys: '{V:[Link]}'
- EnvVars: '{V:[Link]}'

Press YES to delete the items and continue the installation.

Pres NO to not delete the items and continue the installation anyway.
Press CANCEL to stop the installation.</Text>
</AskUser>
<Condition operator="AND"
description="Check how '[Link]' was set by the preceding AskUser
task.">
<VariableExists name="[Link]" type="I"/>
<StringCheck
name="{I:[Link]}"
expression="Yes"
evaluate="MustBeMet"/>
<True>
<Delete description="Delete folders that may not exist before the
installation.">
<Type>DIR</Type>
<Name>{V:[Link]}</Name>
</Delete>
<DeleteRegistryKey description="Delete all unnecessary registry keys.">
<Name>{V:[Link]}</Name>
</DeleteRegistryKey>
<ModifyEnvironmentVariable description="Delete all unnecessary
environment variables.">
<Name>{V:[Link]}</Name>
<Mode>Remove</Mode>
</ModifyEnvironmentVariable>

Document version: 002 Reference and Using – User Guide 53

J/Install reference
J/Install

<Condition description="If environment variables were removed then the

current installation must quit. A new installation must be started for
changes to take effect.">
<StringCheck name="{V:[Link]}"
expression="true"/>
<True>
<Exit description="Installation terminated because J/Install
removed old environment variables. Restart the installation for
changes to take effect!">
<Code>16</Code>
</Exit>
</True>
</Condition>
</True>
<False>
<Condition>
<VariableExists name="[Link]" type="I"/>
<StringCheck
name="{I:[Link]}"
expression="No"
evaluate="MustBeMet"/>
<True>
<WriteLog>
<Entry>User decided to NOT delete the old items and to continue the
installation.</Entry>
</WriteLog>
</True>
<False>
<Exit description="User canceled the installation.">
<Code>15</Code>
</Exit>
</False>
</Condition>
</False>
</Condition>

If the command AskUser from the example above is being processed, the
following dialog will pop up:

54 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command CheckPassword
This task checks given password for compliance with the current password
policy configured on the machine.

Tool [Link]
A new tool for checking password for compliance with configured password
policy was integrated into J/Install. It’s saved in the folder C:\jinstall\
bin.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 6.5+

ignoreerror boolean TRUE Errors are ignored during processing 6.5+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Password string any Encrypted or plain password of user 6.5+
Username.
The encrypted password can be
created using the
%JINSTALL_ROOT%\BIN\
[Link] tool.
The password will be then checked
for compliance with the Windows
password policy configured on the
target machine.

Example 2-6 Example for the use of the command CheckPassword

Hint
As of V6.9 J/install provides the condition <IsValidPassword> which allows
even more control when checking user passwords for validity.
Related information:
"The condition IsValidPassword" on page 2-66

Document version: 002 Reference and Using – User Guide 55

J/Install reference
J/Install

The command Compress

This command creates a compressed file in ZIP format.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 1.4+

ignoreerror boolean TRUE Errors are ignored during processing 1.4+

FALSE Errors cause cancellation of
processing

fallback boolean TRUE Automatical extending of fallback 4.1+

information with the files being
processed by this command
FALSE No automatical extending of fallback
information

Element definitions
Name Type Value Meaning V
Source string any Files to be compressed (including 1.0+
path); by using the wildcards '?' for
any single character or '*' for any
strings, more than one file can be
addressed.
Destination string any ZIP archive including path 1.0+
Folder string any Folder within the ZIP archive that 3.8+
shall contain the files to be added
Type string ALWAYS Files are always added. 3.8+
MODSEG Files are only added if the MODSEG
is higher than the files that already
exist. If both files have no MODSEG,
the date and time are being
compared. If only one file has a
MODSEG, this file is regarded
always as most current one.
NEWER Files are only added if they are
newer than the files that already
exist.
NOTEXISTS Files are added only if they not yet
exist in the target location.
VERSION Files are only added if the version
number is higher than the version
number of the files that already exist.
If both files have no version
information, the date and time are
being compared. If only one file has
a version information, this file is
regarded always as most current
one.

56 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Name Type Value Meaning V
Password string any Encrypted or plain password 3.8+
The encrypted password can be
created using the
%JINSTALL_ROOT%\BIN\
[Link] tool.
Recursive boolean TRUE Processing will include subfolders. 1.0+
FALSE Processing excludes subfolders.
Overwrite boolean TRUE File is re-created 1.0+
FALSE An existing file is extended

Example 2-7 Example for the use of the command Compress

<Compress>
<Source>c:\frm\hw\*.*</Source>
<Destination>c:\productizing\hw\firmware\[Link]</Destination>
</Compress>

<Compress>
<Source>c:\frm\reg\*.*</Source>
<Destination>c:\productizing\hw\firmware\[Link]</Destination>
<Folder>reg</Folder>
<Type>NEWER</Type>
</Compress>

Document version: 002 Reference and Using – User Guide 57

J/Install reference
J/Install

The command Condition

This command checks one or several conditions connected by conjunctions or
disjunctions. If the result is positive, all commands listed under True are
executed. When the result is negative, all commands listed under False are
executed. All commands from the Sequence section can be used.
Attribute definitions
Name Type Value Meaning V

operator string AND Conjunction 1.5+

OR Disjunction

description string any Text describing the command 1.5+

ignoreerror boolean TRUE Errors are ignored during processing 1.5+

FALSE Errors cause cancellation of processing

Example 2-8 Example for the use of the command Condition

<Condition operator="AND">
[condition(s) to be checked]
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

The conditions to be checked are defined by the following elements:

Element Meaning V
ChecksumCheck checking for the checksum of a file; see"The condition 3.3+
ChecksumCheck" on page 2-60
DateTimeCheck checking for date or time; see "The condition DateTimeCheck" 3.7+
on page 2-61
DriveCheck checking for size, free memory, type and label of a drive; see 3.7+
"The condition DriveCheck" on page 2-62
FileExists checking for availability of file or directory; see "The condition 1.5+
FileExists" on page 2-63
IsFalse checking if a 'False' representation value is part of a string; see 3.3+
"The condition IsFalse" on page 2-64
IsTrue checking if a 'True' representation value is part of a string; see 3.3+
"The condition IsTrue" on page 2-65
IsValidPassword Check for password compliance with regard to a password 6.9+
policy; siehe "The condition IsValidPassword" on page 2-66
MemoryCheck checking for available physical memory; see "The condition 3.0+
MemoryCheck" on page 2-68
ModSegCheck checking for a MODESG of a file; see"The condition 3.0+
ModSegCheck" on page 2-69
OsCheck checking for operating system; see "The condition OsCheck" 5.0+
on page 2-70

58 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Element Meaning V
RegistryKeyExists checking for specific Registry Keys in general; see "The 6.9+
condition RegistryKeyExists" on page 2-71
RestartCheck checking for existing Registry entry 4.0+
PendingFileRenameOperations; see "The condition
RestartCheck" on page 2-72
StringCheck checking of a string; see "The condition StringCheck" on 2.0+
page 2-73
TextFileCheck checking for existing text lines in a text file; see "The condition 6.2+
TextFileCheck" on page 2-74
TokenExists checking of existence of a token within a token list; see "The 3.3+
condition TokenExists" on page 2-75
UserIsAdmin Checking of administrative rights; see "The condition 3.2+
UserIsAdmin" on page 2-76
ValueCheck checking of a parameter value; see "The condition 2.0+
ValueCheck" on page 2-77
ValueExists checking of a parameter; see "The condition ValueExists" on 2.0+
page 2-79
VariableExists checking of a variable; see "The condition VariableExists" on 3.4+
page 2-81
VersionCheck checking for Windows vrsion of a file; see"The condition 3.3+
VersionCheck" on page 2-82

Document version: 002 Reference and Using – User Guide 59

J/Install reference
J/Install

The condition ChecksumCheck

This condition checks the checksum of a file.
Attribute definitions
Name Type Value Meaning V
file string any File name 3.3+
type stríng CRC32 CRC32 algorithm 3.3+
MD5 MD5 algorithm
SHA-1 SHA-1 algorithm
SHA-256 SHA-256 algorithm
SHA-384 SHA-384 algorithm
SHA-512 SHA-512 algorithm
expression string RegularExp Counter value for comparison 3.3+
evaluate string MustBeMet RegularExp must be fulfilled 3.3+
MustNotBeMet RegularExp may not be met

Example 2-9 Example for the use of the condition ChecksumCheck

<Condition>
<ChecksumCheck file="c:\protopas\bin\[Link]" type="CRC32"
expression="19146A34" evaluate="MustBeMet"/>
<ChecksumCheck file="c:\protopas\bin\[Link]" type="MD5"
expression="6CAAD464E7DF1B98656BF8A69382C901" evaluate="MustBeMet"/>
<ChecksumCheck file="c:\protopas\bin\[Link]" type="SHA-1"
expression="A3F7F6253BAA6B5E483C4638BDB39BA02E26347A" evaluate="MustBeMet"/>
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

60 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition DateTimeCheck
This condition is used tor check for a specific date or time.
Attribute definitions
Name Type Value Meaning V
type stríng DATE Date using format YYYY-MM-DD 3.7+
TIME Time using format HH:MM
expression string RegularExp or any Counter value for comparison 3.7+
evaluate string MustBeMet RegularExp must be fulfilled 3.7+
MustNotBeMet RegularExp may not be met
Less or LSS Less than
LessEqual or LEQ Less than or equal
greater or GTR Ggreater than
GreaterEqual or GEQ Greater than or equal
Equal or EQU Equal
NotEqual or NEQ Not equal

Example 2-10 Example for the use of the condition DateTimeCheck

<Condition>
<DateTimeCheck type="DATE" expression="2010-10-10" evaluate="Greater" />
<DateTimeCheck type="TIME" expression="10:10" evaluate="Greater" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

Document version: 002 Reference and Using – User Guide 61

J/Install reference
J/Install

The condition DriveCheck

This condition checks size, free storage amount, type and label of a given
drive.
Attribute definitions
Name Type Value Meaning V
file string any Directory at the drive to be 3.7+
checked
type stríng SPACE_FREE Available memory in MB 3.7+
SIZE_TOTAL Total amount of memory in MB
LABEL Name
TYPE Type
FREE - Drive unused
CDROM - CDROM
FIXED - Harddrive
REMOTE - Network share
REMOVABLE - Removable drive
RAM - RAM drive
expression string RegularExp or any counter-value for comparison 3.7+
evaluate string MustBeMet RegularExp must be fulfilled 3.7+
MustNotBeMet RegularExp may not be met
Less or LSS Less than
LessEqual or LEQ Less than or equal
greater or GTR Greater than
GreaterEqual or GEQ Greater than or equal
Equal or EQU Equal
NotEqual or NEQ Not equal

Example 2-11 Example for the use of the condition DriveCheck

<Condition>
<DriveCheck file="c:\" type="SPACE_FREE" expression="100"
evaluate="GreaterEqual"/>
<DriveCheck file="c:\" type="SIZE_TOTAL" expression="500000"
evaluate="GreaterEqual"/>
<DriveCheck file="c:\" type="TYPE" expression="FIXED"/>
<DriveCheck file="c:\" type="LABEL" expression="SYSTEM"/>
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

62 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition FileExists
This condition checks, whether a file or directory exists.
Attribute definitions
Name Type Value Meaning V
name string any File or directory; the use of the 1.5+
Windows-specific wildcard characters * and ?
for character strings and individual characters
is supported
Extended syntax (V6.9+):
Comma-separated list of file names or folder
names that shall be checked for existence.
Attribute 'operator' specifies whether all
(AND) or at least one (OR) specified
files/folders have to exist.
evaluate string MustBeMet File or directory must exist 1.5+
MustNotBeMet File or directory must not exist
operator string AND Evaluated only if attribute ’name’ contains 6.9+
more than one name
OR
type string FILE Check of file 3.3+
DIR Check of directory

Example 2-12 Example for the condition FileExists

<Condition operator="AND">
<FileExists name="c:\install" evaluate="MustNotBeMet" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

Document version: 002 Reference and Using – User Guide 63

J/Install reference
J/Install

The condition IsFalse

This condition checks if a string contains a substring representing the boolean
False value. The boolean value can be represented by one of the strings
’FALSE’, ’F’, ’NO’, ’N’ or ’0’. This check is not case-sensitive.
Attribute definitions
Name Type Value Meaning V
expression string any String to be checked 3.3+
evaluate string MustBeMet String must be a valid False 3.3+
value
MustNotBeMet String must not be a valid
False value

Example 2-13 Example for the use of the condition IsFalse

<Condition operator="AND">
<IsFalse expression="no" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

64 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition IsTrue
This condition checks if a string contains a substring representing the boolean
TRUE value. The boolean value can be represented by one of the strings
’TRUE’, ’T’, ’YES’, ’Y’ or ’1’ . This check is not case-sensitive.
Attribute definitions
Name Type Value Meaning V
expression string any String to be checked 3.3+
evaluate string MustBeMet String must be a valid TRUE 3.3+
value
MustNotBeMet String must not be a valid
TRUE value

Example 2-14 Example for the use of the condition IsTrue

<Condition operator="AND">
<IsTrue expression="yes" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

Document version: 002 Reference and Using – User Guide 65

J/Install reference
J/Install

The condition IsValidPassword

This condition checks whether the entered or provided password is compliant
to the password policy which is applied on the terminal.
It can be used if a new user is created during installation or if the password of
an already existing user shall be changed. These action are usually carried out
at the end of the installation process. Using this IsValidPassword condition an
applied password can be checked at the beginning of the installation.
Attribute definitions
Name Type Value Meaning V
name string any Password that has to be checked against the 6.9+
valid password policy.
If the value of 'name' is a hexadecimal string
(consisting of characters 0-9, a-f, A-F, and
having the length divisible by 2), then J/Install
assumes 'name' is an encrypted password
and decrypts it. The decrypted password
value is then passed to the internal password
checking routine.
Hint: Value of 'name' is processed as is.
Leading/trailing blanks will not be truncated.
evaluate string MustBeMet TRUE, if the password provided with the
name attribute is compliant to the password
policy and can be stored.
MustNotBeMet TRUE, if the password provided with the
name attribute cannot be stored with
Windows since it is not compliant with the
password policy

Example 2-15 Using condition IsValidPassword

<Loop>
<FileExists
name="{E:TEMP}\[Link]"
type="FILE"
evaluate="MustNotBeMet" />
<Do>
<Extern description="Read common variables in from [Link].">
<File>{V:CUSTOM_FOLDER}\[Link]</File>
<Prefix>common</Prefix>
<Task>SetVariable</Task>
</Extern>
<Condition
operator="AND"
description="Check the non-admin user password entered [Link] file
for compliance with the password policy configured on the machine.">
<VariableExists name="[Link]" type="V"/>
<True>
<Condition
description="Check non-admin user password for compliance.">
<IsValidPassword name="{V:[Link]}" evaluate="MustBeMet"/>
<True>
<WriteLog
ignoreerror="true"
description="Non-admin user's password verified successfully. Write
dummy tag file to break the loop and continue processing.">
<File>{E:TEMP}\[Link]</File>
<Entry>Dummy entry. Non-admin user's password verification
successful.</Entry>
</WriteLog>
</True>
<False>

66 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install

<Condition
operator="AND"
description="Was the password entered interactively or does it come
directly from [Link]?">
<VariableExists name="IsCommonPasswordAsk" type="I"/>
<StringCheck
name="{I:IsCommonPasswordAsk}"
expression="true"
evaluate="MustBeMet"/>
<True>
<ShowMessage>
<Text>Non-admin user's password verification failed! Enter another
password.</Text>
</ShowMessage>
</True>
<False>
<Exit>
<Code>19</Code>
<Text>Non-admin user's password verification failed!</Text>
</Exit>
</False>
</Condition>
</False>
</Condition>
</True>
<False>
<WriteLog description=" Password doesn't have to be checked. Write dummy
tag file to break the loop and continue processing.">
<File>{E:TEMP}\[Link]</File>
<Entry>dummy2</Entry>
</WriteLog>
</False>
</Condition>
</Do>
</Loop>
<Delete description="Delete the dummy tag file.">
<Type>FILE</Type>
<Name>{E:TEMP}\[Link]</Name>
</Delete>

Document version: 002 Reference and Using – User Guide 67

J/Install reference
J/Install

The condition MemoryCheck

This condition checks the physical memory that is currently available.
Attribute definitions
Name Type Value Meaning V
type string PHYS_TOTAL Total physical memory in MB 3.0+
PHYS_AVAIL Available memory in MB
expression string RegularExp or any Counter value for comparison 3.0+
evaluate string MustBeMet RegularExp must be fulfilled 3.0+
MustNotBeMet RegularExp may not be met
Less or LSS Less than
LessEqual or LEQ Less than or equal
greater or GTR Greater than
GreaterEqual or GEQ Greater than or equal
Equal or EQU Equal
NotEqual or NEQ Not equal

Example 2-16 Example for the use of the condition MemoryCheck

<Condition>
<MemoryCheck type="PHYS_TOTAL" expression="500" evaluate="Greater" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

68 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition ModSegCheck
This condition checks the MODSEG of a file.
Attribute definitions
Name Type Value Meaning V
file string any File name 3.0+
expression string RegularExp or any Counter value for comparison 3.0+
evaluate string MustBeMet RegularExp must be fulfilled 3.0+
MustNotBeMet RegularExp may not be met
Less or LSS Less than
LessEqual or LEQ Less than or equal
greater or GTR Greater than
GreaterEqual or GEQ Greater than or equal
Equal or EQU Equal
NotEqual or NEQ Not equal

Example 2-17 Example for the use of the condition ModSegCheck

<Condition>
<ModSegCheck file="c:\protopas\bin\[Link]" expression="5000"
evaluate="Greater"/>
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

Document version: 002 Reference and Using – User Guide 69

J/Install reference
J/Install

The condition OsCheck

This condition checks the operating system.
Attribute definitions
Name Type Value Meaning V
name string Windows any Windows OS 5.0+
Windows_NT Windows NT
Windows_2000 Windows 2000
Windows_XP Windows XP
Windows_Vista Windows Vista
Windows_7 Windows 7
Windows_8 Windows 8
Windows_8_1 Windows 8.1 6.3+
Windows_Server_2003 Windows Server 2003
Windows_Server_2008 Windows Server 2008
Windows_Server_2008_R2 Windows Server 2008 R2
Windows_Server_2012 Windows Server 2012
Windows_Server_2012_R2 Windows Server 2012 R2
type string 32 32Bit 5.0+
64 64Bit
evaluate string MustBeMet Operating system has to be of 5.0+
the specified type
MustNotBeMet Operating system has not to be
of the specified type

Example 2-18 Example for the use of condition OsCheck

<Condition>
<OsCheck name="Windows_7" type="64" evaluate="MustBeMet" />
<True>
[Befehl(e)]
</True>
<False>
[Befehl(e)]
</False>
</Condition>

70 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition RegistryKeyExists
The condition RegistryKeyExists checks if one or more Registry keys are pres-
ent.
Attribute definitionen
Name Typ Wert Bedeutung V
name string beliebig Simple syntax: 6.9+
Name of Registry Key to be
checked for presence.
Extended syntax:
Comma-separated list of Registry
keys to be checked for presence.
Attribute 'operator' defines whether
all (AND) or at least one (OR) of
these keys have to be present.

Note: All Registry keys have to

provided including Hive. Both Hive
formats (short and long) are
supported.
Examples:
HKLM\SOFTWARE\Wincor Nixdorf,
HKEY_LOCAL_MACHINE\
SOFTWARE\Wincor Nixdorf
evaluate string MustBeMet TRUE, if the provided Registry key 6.9+
is present
MustNotBeMet TRUE, if the provided Registry key
is not present
operator string AND Evaluated only if attribute 'name' 6.9+
provides more than one Registry
OR key.

Example 2-19 Example for the use of the condition RegistryKeyExists

<Condition>
<RegistryKeyExists evaluate="MustBeMet" />
<True>
[Befehl(e)]
</True>
<False>
[Befehl(e)]
</False>
</Condition>

Document version: 002 Reference and Using – User Guide 71

J/Install reference
J/Install

The condition RestartCheck

This copndition checks whether the Registry entry PendingFileRenameOpera-
tions does exist or not.
Attribute definitionen
Name Type Value Meaning V
evaluate string MustBeMet Registry entry 4.0+
PendingFileRenameOperations
must exist
MustNotBeMet Registry entry
PendingFileRenameOperations
must not exist

Example 2-20 Example for the use of the condition RestartCheck

<Condition operator="AND">
<RestartCheck evaluate="MustBeMet" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

72 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition StringCheck
This condition compares the content of a character string to a specified
expression.
Attribute definitions
Name Type Value Meaning V
name string any Character string 2.0+
expression string RegularExp or any Counter value for comparison 2.0+
casesensitive boolean TRUE Case-sensitive check 3.3+
FALSE No case-sensitive check
evaluate string MustBeMet RegularExp must be fulfilled 2.0+
MustNotBeMet RegularExp may not be met
Less or LSS Less than
LessEqual or LEQ Less than or equal
greater or GTR Greater than
GreaterEqual or GEQ Greater than or equal
Equal or EQU Equal
NotEqual or NEQ Not equal

Example 2-21 Example for the use of the condition StringCheck

<Condition operator="AND">
<StringCheck name="{E:SystemDrive}" expression="C:" />
<StringCheck name="{J:[Link]}" expression="x86" />
<StringCheck name="{J:[Link]}" expression=".*Windows.*" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

Document version: 002 Reference and Using – User Guide 73

J/Install reference
J/Install

The condition TextFileCheck

This condition compares the lines of a text file with a provided expression.
Attribute definitions
Name Typ Wert Bedeutung V
name string any Character string 6.2+
expression string RegularExp or any Counter value for comparison 6.2+
casesensitive boolean TRUE Case-sensitive check 6.2+
FALSE No case-sensitive check
encoding string any Code set (for example 6.2+
ISO-8859-1,UTF-8, UTF-16)
evaluate string MustBeMet RegularExp must be fulfilled 6.2+
MustNotBeMet RegularExp may not be met

Example 2-22 Example for the use with condition TextFileCheck

<Condition>
<TextFileCheck name="c:\[Link]" expression=".*timeout.*" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

74 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition TokenExists
This condition checks whether a token is part of a list of several tokens.
Attribute definitions
Name Type Value Meaning V
input string any List of token 3.3+
delimiter string any Delimiter for token list 3.3+
token string RegularExp Token to be searched for; 3.3+
alternatively a token can be
addressed directly via
{TokenPos}<Position>,
whereas the token list starts
with 1
evaluate string MustBeMet RegularExp must be fulfilled 2.0+
MustNotBeMet RegularExp may not be met
casesensitive boolean TRUE Case-sensitive check 3.3+
FALSE No case-sensitive check

Example 2-23 Example for the use of the condition TokenExists

<Condition operator="AND">
<TokenExists input="Jxfs30,JDevice,Common" token="(?i)jxfs.*" delimiter="," />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

Document version: 002 Reference and Using – User Guide 75

J/Install reference
J/Install

The condition UserIsAdmin

This condition checks whether the logged-in user has administrative rights.
Attribute definitions
Name Type Value Meaning V
evaluate string MustBeMet User must have administrative 3.2+
rights
MustNotBeMet User must not have
administrative rights.

Example 2-24 Example for the use of the condition UserIsAdmin

<Condition operator="AND">
<UserIsAdmin evaluate="MustBeMet" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

76 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition ValueCheck
This condition checks, whether an entry in a file or in the Windows registry
matches the specified expression. The checked entries are addressed via file
paths. For a description od the different addressing procedures see section
"Data access paths" on page 2-174. You can use reqular expressions to
specify the counter value the variable content is compared with. The section
"Using regular expressions" on page 2-171 describes the different possibilities.
Attribute definitions
Name Type Value Meaning V
type string INI INI file 2.0+
REG Registry
PROPERTY Properties file
PCE PC/E file
XML XML files 4.0+
file string any File name 2.0+
HKCR or HKEY_CLASSES_ROOT
HKEY_CLASSES_ROOT
HKCU or HKEY_CURRENT_USER
HKEY_CURRENT_USER
HKLM or HKEY_LOCAL_MACHINE
HKEY_LOCAL_MACHINE
HKCC or HKEY_CURRENT_CONFIG
HKEY_CURRENT_CONFIG
HKU or HKEY_USERS HKEY_USERS
path string <IniPath> Reference to INI file 2.0+
<RegPath> Refers to registry
<Property> Property in property file
<PcePath> Reference to PC/E file
<XmlPath> Reference to XML file 4.0+
expression string RegularExp or any Counter value for comparison 2.0+
casesensitive boolean TRUE Case-sensitive check 3.3+
FALSE No case-sensitive check
delimiter string any Delimiter for token list 3.3+

Document version: 002 Reference and Using – User Guide 77

J/Install reference
J/Install

Name Type Value Meaning V

evaluate string MustBeMet RegularExp must be fulfilled 2.0+
MustNotBeMet RegularExp may not be met
Less or LSS Less than
LessEqual or LEQ Less than or equal
greater or GTR Greater than
GreaterEqual or GEQ Greater than or equal
Equal or EQU Equal
NotEqual or NEQ Not equal
token string RegularExp Token to be searched for; 3.3+
alternatively a token can be
addressed directly via
{TokenPos}<Position>,
whereas the token list starts
with 1

Example 2-25 Example for the use of the condition ValueCheck

<Condition operator="AND">
<ValueCheck type="INI" file="c:\[Link]" path="[boot loader]timeout" ~
expression="30" />
<ValueCheck type="REG" file="HKLM" path="[SOFTWARE\Wincor Nixdorf\ ~
CSC-W32\CurrentVersion\CSCCNG]LOAD" expression="FRONT" />
<ValueCheck type="PROPERTY" file="c:\[Link]" ~
path="[Link]" expression="hide" />
<ValueCheck type="XML" file="c:\[Link]" ~
path="/Custom/Variables/Variable[@name='CUSTOM_COPY']/@value"~
expression="true" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

78 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition ValueExists
This condition checks, whether an entry exists in a file or in the Windows
registry. The condition does not check the value of the entry. The checked
entries are addressed via file paths. For a description od the different
addressing procedures see section "Data access paths" on page 2-174.
Attribute definitions
Name Type Value Meaning V
type string INI INI file 2.0+
REG Registry
PROPERTY Properties file
PCE PC/E file
XML XML files 4.0+
file string any File name 2.0+
HKCR or HKEY_CLASSES_ROOT
HKEY_CLASSES_ROOT
HKCU or HKEY_CURRENT_USER
HKEY_CURRENT_USER
HKLM or HKEY_LOCAL_MACHINE
HKEY_LOCAL_MACHINE
HKCC or HKEY_CURRENT_CONFIG
HKEY_CURRENT_CONFIG
HKU or HKEY_USERS HKEY_USERS
path string <IniPath> Reference to INI file 2.0+
<RegPath> Refers to registry
<Property> Property in property file
<PcePath> Reference to PC/E file
<XmlPath> Reference to XML file 4.0+
casesensitive boolean TRUE Case-sensitive check 3.3+
FALSE No case-sensitive check
delimiter string any Delimiter for token list 3.3+
evaluate string MustBeMet Value must exist 2.0+
MustNotBeMet Value must not exist
token string RegularExp Token to be searched for; 3.3+
alternatively a token can be
addressed directly via
{TokenPos}<Position>,
whereas the token list starts
with 1

Document version: 002 Reference and Using – User Guide 79

J/Install reference
J/Install

Example 2-26 Example for the use of the condition ValueExists

<ValueExists type="REG" file="HKLM" path="[SOFTWARE\Wincor Nixdorf\ ~

CSC-W32\CurrentVersion\CSCCNG]" />

<ValueExists type="PROPERTY" file="c:\[Link]" ~

path="[Link]" />

80 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The condition VariableExists
This condition checks the presence of a variable.
Attribute definitions
Name Type Value Meaning V
name string RegularExp Value for comparison 3.4+
Extended syntax (V6.9+):
Comma-separated list of
variable names to be checked
for presence.
evaluate string MustBeMet Variable must exist 3.4+
MustNotBeMet Variable must not exist
operator string AND Evaluated only if attribute 6.9+
’name’ contains more than one
OR name
type string E Environment variable 3.4+
J Java system property
I Internal variable
V User variable

Example 2-27 Example for the condition VariableExists

<Condition description="Condition to set 'CUSTOM_FOLDER'">
<VariableExists name="CUSTOM_COPY_" type="V" />
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

Document version: 002 Reference and Using – User Guide 81

J/Install reference
J/Install

The condition VersionCheck

This condition checks the Windows version of a file.
Attribute definitions
Name Type Value Meaning V
file string any File name 3.3+
expression string RegularExp or any Value for comparison 3.3+
evaluate string MustBeMet RegularExp must be fulfilled 3.3+
MustNotBeMet RegularExp may not be met
Less or LSS Less than
LessEqual or LEQ Less than or equal
greater or GTR Greater than
GreaterEqual or GEQ Greater than or equal
Equal or EQU Equal
NotEqual or NEQ Not equal

Example 2-28 Example for the use of the condition VersionCheck

<Condition>
<VersionCheck file="{E:WINDIR}\[Link]" expression="5.1.2600.2180"
evaluate="Greater"/>
<True>
[command(s)]
</True>
<False>
[command(s)]
</False>
</Condition>

82 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command ConfAutologon
This command configures the Autologon feature of the Windows operating
system.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V
Username string any User name that shall be used for automatic 3.0+
logon
Password string any Encrypted or plain password of user 3.0+
Username.
The encrypted password can be created
using the %JINSTALL_ROOT%\BIN\
[Link] tool.
Domain string any Domain 3.0+
ForceAutologon boolean TRUE Automatic logon 3.0+
FALSE No automatic logon
Private boolean TRUE Secret storing of password (starting with 3.9+
Windows XP SP2)
FALSE No secret storing of password

Example 2-29 Example for the use of the command ConfAutologon

Document version: 002 Reference and Using – User Guide 83

J/Install reference
J/Install

The command ConfNonAdmin

This command creates a new user group or extends an already existing user
group in a way, that members of this group can use the application without
having appropriate administrative rights.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Group string any Name of an already existing or of a 3.0+
new to be created group
Source string any Directory of the PRC files to be 3.0+
processed
Default: c:\install\prc
Username string any Name of an already existing or new to 3.0+
be created users that is to added to
group Group
Password string any Encrypted or plain password of user 3.0+
Username.
The encrypted password can be
created using the
%JINSTALL_ROOT%\BIN\[Link]
tool.
The password must be set and must
be compliant to the Windows password
policies.
Autologon boolean TRUE Automatic logon of the user. Entering 3.0+
Username as well as Password is
required. A logon using a different user
account is possible by pressing the
SHIFT key during the start-up of the
operating system.
FALSE No automatic logon of the user.
ForceAutologon boolean TRUE Automatic logon after logout. Requires 3.0+
Autologon parameter.
FALSE No automatic logon.
Attributes string Bit structure Configuration of user properties via a 3.0+
bit structure (0=off,1=on):
Bit 1: user must change password with
next login
Bit 2: user cannot change password
Bit 3: password never expires
Bit 4: account deactivated
Default: 0010 (password never
expires)

84 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Name Type Value Meaning V
Private boolean TRUE Secret storing of password (starting 3.9+
with Windows XP SP2)
FALSE No secret storing of password
SetUserShell boolean TRUE Enables setting shell application for the 7.1+
non-admin user.
FALSE Disables setting shell application for
the non-admin user.
UserShell string any Command line starting a process 7.1+
acting as the shell application of the
non-admin user. This parameter is
evaluated only if attribute SetUserShell
was set to ’TRUE’.

Example 2-30 Example for the use of the command ConfNonAdmin

<ConfNonAdmin>
<Group>WN_GROUP</Group>
<Username>WN_USER</Username>
<Password>C4E0E6E72960F375</Password>
<Autologon>true</Autologon>
<ForceAutologon>true</ForceAutologon>
<Attributes>0010</Attributes>
</ConfNonAdmin>

The configuration is carried out with the tool [Link] located in

directory %JINSTALL_ROOT%\BIN. Further information and application hints
can be found in the help file [Link] of this tool.
If further rights shall be specified, a PRC file can be provided with J/Install and
shall be copied into directory <Source>.
In any case the tool [Link] can be used to process on PRC files
without J/Install.

Document version: 002 Reference and Using – User Guide 85

J/Install reference
J/Install

The command CopyFile

This command copies files from a source directory to a target directory. You
can copy the sub-directories as well (Recursive element). You can control the
command behavior using the elements described below.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 1.4+

ignoreerror boolean TRUE Errors are ignored during 1.4+

processing
FALSE Errors cause cancellation of
processing

fallback boolean TRUE Automatical extending of fallback 4.1+

information with the files being
processed by this command
FALSE No automatical extending of
fallback information

Element definitions
Name Type Value Meaning V
Source string any Specification of the source 1.0+
directory as a filemask with
directory names; the use of the
Windows-specific wildcard
characters * and ? for character
strings and individual characters is
supported. A text file with a list of
Source entries can be provided
with prefix {List}.
Destination string any Target directory 1.0+
Backup boolean TRUE Existing target file will be saved 3.7+
with extension '.bak'
FALSE Existing target file will be
overwritten without backup
Recursive boolean TRUE Sub-directories will be handled 1.0+
FALSE Sub-directories will not be handled
Name string any Name of a single file in the target 3.0+
directory Destination to copy a
single file with a different name.
PendingFileHandling boolean TRUE If a file is being accessed by other 3.4+
applications, it will be replaced
during the restart of the Windows
system.
FALSE If a file cannot be overwritten
because it is used by other
applications, an error occurs.

86 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Name Type Value Meaning V
PreserveDate boolean TRUE Applying date/time of source file 3.6+
FALSE Date/time of source file will be
changed to current system time for
target file
PreserveAttribute boolean TRUE Applying file attributes of source 3.6+
file on target file
FALSE Source file attributes will not be
used; Archive attribute will be set
Type string ALWAYS Files are always copied. 1.0+
MODSEG Files are only added if the 3.3+
MODSEG is higher than the files
that already exist. If both files have
no MODSEG, the date and time
are being compared. If only one
file has a MODSEG, this file is
regarded always as most current
one.
NEWER Files are only added if they are 1.0+
newer than the files that already
exits.
NOTEXISTS Files are copied only if they not yet 3.3+
exist in the target location.
VERSION Files are only added if the version 3.3+
to be copied is is higher than the
version of the file that already
exist. If both files have no version
information, the date and time are
being compared. If only one file
has a version information, this file
is regarded always as most
current one.

Example 2-31 Example for the use of the command CopyFile

<CopyFile fallback="true">
<Source>{CurrentSource}\install\firmware\10.22\*.*</Source>
<Destination>c:\productizing\hw\current</Destination>
</CopyFile>

<CopyFile>
<Source>{List}\install\[Link]</Source>
<Destination>c:\productizing\hw\current</Destination>
</CopyFile>

Example 2-32 Copying and renaming using command CopyFile

Document version: 002 Reference and Using – User Guide 87

J/Install reference
J/Install

The command CreateDir

This command creates a directory including all parent directories.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.3+

ignoreerror boolean TRUE Errors are ignored during processing 3.3+

FALSE Errors cause cancellation of
processing

fallback boolean TRUE Automatical extending of fallback 4.1+

information with the folder being
created by this command
FALSE No automatical extending of fallback
information

Element definitions
Name Type Value Meaning V
Name string any Directory to be created 3.3+

Example 2-33 Example for the use of the command CreateDir

<CreateDir description="Making directory">
<Name>c:\parac\def</Name>
</CreateDir>

88 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command CreateList
This command creates a text file containing a list of filenames or directories
that can be used by other commands when applying the parameter {List}.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.7+

ignoreerror boolean TRUE Errors are ignored during processing 3.7+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V
Source string any Specification of the source directory as a 3.7+
filemask with directory names; the use of
the Windows-specific wildcard characters *
and ? for character strings and individual
characters is supported
ResultFile string any Text file with list of files 3.7+
Recursive boolean TRUE Sub-directories will be handled 3.7+
FALSE Sub-directories will not be handled
Type string FILE Applies on files 4.1+
DIR Applies on directories
Name boolean TRUE Return of name without leading path 4.1+
FALSE Return of name including leading path

Example 2-34 Example for the use of the command CreateList

<CreateList>
<Source>c:\install\custom\*.zip</Source>
<ResultFile>c:\install\[Link]</ResultFile>
<Recursive>false</Recursive>
<Type>FILE</Type>
</CreateList>

Document version: 002 Reference and Using – User Guide 89

J/Install reference
J/Install

The command CreateShortcut

This command creates an application shortcut.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.4+

ignoreerror boolean TRUE Errors are ignored during processing 3.4+

FALSE Errors cause cancellation of processing

fallback boolean TRUE Automatical extending of fallback 4.1+

information with the shortcut being created
by this command
FALSE No automatical extending of fallback
information

Element definitions
Name Type Value Meaning V
Shortcut string any Name of shortcut file 3.4+
Target string any Name of file the shortcut refers to 3.4+
Parameters string any Call parameters 3.4+
Folder string any Working folder 3.4+
Style string NORMAL Normal execution 3.4+
MIN Minimized execution
MAX Maximized execution

Example 2-35 Example for the use of the command CreateShortcut

<CreateShortcut description="Shortcut anlegen">
<Shortcut>c:\[Link]</Shortcut>
<Target>{E:WINDIR}\[Link]</Target>
<Parameter>c:\[Link]</Parameter>
<Style>MAX</Style>
</CreateShortcut>

90 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command Decompress
This command decompresses ZIP or JAR archives in the specified target
directory.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 1.4+

ignoreerror boolean TRUE Errors are ignored during 1.4+

processing
FALSE Errors cause cancellation of
processing

fallback boolean TRUE Automatical extending of fallback 4.1+

information with the files being
processed by this command
FALSE No automatical extending of
fallback information

Element definitions
Name Type Value Meaning V
Source string any Name of ZIP archive including 3.0+
path; by using the wildcards ‘?’ for
any single character and ‘*’ for any
strings, multiple files can be
addressed, that will then
uncompressed in their alphabetical
order.
Decompressing archives
referenced in a text file:
If the content of the referenced file
starts with the prefix ’{List}’, all
archives listed behind this prefix
will be decompressed.
Destination string any Target directory 1.0+

Document version: 002 Reference and Using – User Guide 91

J/Install reference
J/Install

Name Type Value Meaning V

Type string ALWAYS Files are always uncompressed. 1.0+
MODSEG Files are only uncompressed if the 3.3+
MODSEG is higher than the files
that already exist. If both files have
no MODSEG, the date and time
are being compared. If only one file
has a MODSEG, this file is
regarded always as most current
one.
NEWER Files are only uncompressed if they 1.0+
are newer than the files that
already exist.
NOTEXISTS Files are uncompressed only if they 3.3+
not yet exist in the target location.
VERSION Files are only uncompressed if the 3.3+
version is higher than the version of
the files that already exist. If both
files have no version information,
the date and time are being
compared. If only one file has a
version information, this file is
regarded always as most current
one.
filter string any Files to be uncompressed; 3.8+
absolute paths start with '/', any
depth of subfolders can be
indicated with '//'; by using the
wildcards '?' for any single
character or '*' for any strings, more
than one file can be addressed;
multiple filter can be set by using
the pipe symbol ('|').
Password string any Encrypted or plain password The 3.8+
encrypted password can be
created using the
%JINSTALL_ROOT%\BIN\
[Link] tool.
PendingFileHandling boolean TRUE If a file is being accessed by other 3.4+
applications, it will be replaced
during the restart of the Windows
system.
FALSE If a file cannot be overwritten
because it is used by other
applications, an error occurs.
PreserveDate boolean TRUE Applying date/time of source file 3.6+
FALSE Date/time of source file will be
changed to current system time for
target file

92 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Name Type Value Meaning V
PreserveAttribute boolean TRUE Applying file attributes of source file 3.8-
on target file 5.0
FALSE Source file attributes will not be
used; Archive attribute will be set
PreserveAttribute boolean TRUE Applying file attributes of source file 6.0+
on target file
FALSE Source file attributes will not be
used; Archive attribute will be set
ResultFile string any Text file, that will contain a list of 3.7+
archives which have been
processed during the
uncompressing.

Example 2-36 Examples for the use of the command Decompress

<Decompress description=“Decompress sample files“>
<Source>{List}c:\list_files.txt</Source>
<Destination>c:\</Destination>
<Type>ALWAYS</Type>
</Decompress>
<Decompress description=“Decompress sample files“>
<Source>c:\install\custom\*.zip</Source>
<Destination>c:\</Destination>
<Type>ALWAYS</Type>
<ResultFile>c:\install\custom\decompress_result.txt</ResultFile>
</Decompress>
<Decompress description=“Decompress sample files“>
<Source>c:\install\custom\*.zip</Source>
<Destination>c:\</Destination>
<Type>VERSION</Type>
<Filter>/windows//*.exe|//*.doc</Filter>
<Password>A3452D8C437992B173E59DCF27E883BE</Password>
</Decompress>
<Decompress description=“Decompress sample files“ fallback=“true“>
<Source>c:\install\custom\*.zip</Source>
<Destination>c:\</Destination>
<Type>NEWER</Type>
<PreserveDate>false</PreserveDate>
<PreserveAttribute>false</PreserveAttribute>
<Filter>/reg/*.*|hw_conf.ini</Filter>
</Decompress>

Document version: 002 Reference and Using – User Guide 93

J/Install reference
J/Install

The command Definition

This command specifies information that are used by the commands Fallback
and Keep.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.1+

ignoreerror boolean TRUE Errors are ignored during processing 3.1+

FALSE Errors cause cancellation of
processing

Example 2-37 Example for the use of the command Definition

<Definition>
[Definitionen]
</Definition>

The definitions to be checked are defined by the following elements:

Name Description V
Fallback "The definition Fallback" on page 2-96 3.1+
FallbackExecuteRestorePost "The definition FallbackExecuteRestorePost" on 3.1+
page 2-95
FallbackExecuteRestorePre "The definition FallbackExecuteRestorePre" on 3.1+
page 2-95
FallbackExecuteSavePost "The definition FallbackExecuteSavePost" on page 2-95 3.1+
FallbackExecuteSavePre "The definition FallbackExecuteSavePre" on page 2-95 3.1+
Keep "The definition Keep" on page 2-97 3.1+
KeepValue "The definition KeepValue" on page 2-98 3.1+
ProClassic "The definition ProClassic" on page 2-98 3.4+
Variable "The definition Variable" on page 2-100 3.4+

94 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The definition FallbackExecuteRestorePost
This definition specifies programs that shall be executed after restoring the
Fallback information finishs.
The attribute definitions are similar to the element definitions (in small letters)
of command <Execute> (see "The command Execute" on page 2-110).

Example 2-38 Specification of a FallbackExecuteRestorePost definition

The definition FallbackExecuteRestorePre

This definition specifies programs that shall be executed prior restoring the
Fallback information starts.
The attribute definitions are similar to the element definitions (in small letters)
of command <Execute> (see "The command Execute" on page 2-110).

Example 2-39 Specification of a FallbackExecuteRestorePre definition

The definition FallbackExecuteSavePost

This definition specifies programs that shall be executed after saving the
Fallback information finishs.
The attribute definitions are similar to the element definitions (in small letters)
of command <Execute> (see "The command Execute" on page 2-110).

Example 2-40 Specification of a FallbackExecuteSavePost definition

The definition FallbackExecuteSavePre

This definition specifies programs that shall be executed prior saving the
Fallback information starts.
The attribute definitions are similar to the element definitions (in small letters)
of command <Execute> (see "The command Execute" on page 2-110).

Example 2-41 Specification of a FallbackExecuteSavePre definition

Document version: 002 Reference and Using – User Guide 95

J/Install reference
J/Install

The definition Fallback

This definition specifies files or directories. Existing files or directrories are
saved by the command Fallback (see "The command Fallback" on
page 2-117) and will be restored if an error occcurs. If the applied files or
directories do not exist, they will be removed if an error occurs.
Artefacts that were specified in section <Definition> are being processed by
task 'Fallback' of type SAVE. These artefacts will be stored in folder
%JINSTALL_ROOT%\fallback.
If the installation was successful, this folder is going to be deleted
automatically at the end of the installation procedure. In case of installation
errors, the task 'Fallback' with type RESTORE is being called implicitely and
the previously stored data will be restored.
For type REG the entire content of the specified HKKLM regitry kex will be
exported into a REG file in folder %JINSTALL_ROOT%\fallback\registry.
If the specified registry key was not found, this information will be stored in a
REG file as well. In case the installation will fail all of these REG files will be
processed and their content will be reimported into the Registry. Not existing
registry keys will be deleted.
The Windows tool [Link] id being used for all export and import operations
affecting the Registry.

Required rights
If J/Install is running without administrative rights, it has to be ensured that
the user who is running the installation has been granted full access rights to
the affected registry keys.

Attribute definitions
Name Type Value Meaning V
name string any File or directory name; with FILE and 3.1+
ZIP the wildcard '?' for any single
character or the wildcard '*' for any
strings can be applied.
If the type attributis set to ’REG’, this
attribute holds the name of the
registry key. Note that only registry
keys or hive
HKEY_LOCAL_MACHINE can be
stored. Wildcards are not permitted
with type =REG.
type string FILE Only filenames of the current 3.1+
directory are affected.
DIR Directories including the contained
files are affected.
ZIP Files in ZIP archives are affected 3.4+
DECOMPRESS All files referred in a properties file 3.4+
and contained in ZIP archives, are
affected
REG The registry key specified with the 6.8+
name attribute will be stored.

96 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Name Type Value Meaning V
recursive boolean TRUE Sub-directories are affected with DIR 3.1+
FALSE Sub-directories are not affected with
DIR
root string any Target directory for unzipping file 3.4+
prefix string any Consideration of ZIP files referred in 3.4+
the properties file and that begin with
this prefix

Example 2-42 Specification of a Fallback definition for a directory to be saved including sub-directories
<Definition>
...
<Fallback type="DIR" name=”C:\PACKAGE” recursive=”true” />
<Fallback type="FILE" name="C:\[Link]"/>
<Fallback type="ZIP" name="C:\[Link]" root="c:\"/>
<Fallback type="DECOMPRESS" name="C:\[Link]"
prefix="decompress"/>
<Fallback type="REG" name="SOFTWARE\Wincor Nixdorf" />
...
</Definition>

The definition Keep

This element specifies files and directories, that will be saved and restored, by
using the element’s attributes.
Attribute definitions
Name Type Value Meaning V
name string any File or directory name; with files the 3.1+
wildcard '?' for any single character
or the wildcard '*' for any strings can
be applied.
type string FILE Only filenames of the current 3.1+
directory are affected.
DIR Directories including the contained
files are affected.
merge boolean TRUE If type DIR, the directory will not be 3.4+
deleted before restoration
FALSE If type DIR, the directory will be
deleted before restoration
recursive boolean TRUE Sub-directories will be handled 3.0+
FALSE Sub-directories will not be handled

Example 2-43 Specification of a Keep definition for a directory to be saved including sub-directories
<Definition>
...
<Keep type="DIR" name=”C:\PACKAGE” recursive=”true” />
...
</Definition>

Document version: 002 Reference and Using – User Guide 97

J/Install reference
J/Install

The definition KeepValue

This element specifies file or registry entries that will be saved and restored by
using the command Keep.
Attribute definitions
Name Type Value Meaning V
type string INI INI file 3.1+
REG Registry
PROPERTY Properties file 3.4+
PCE PC/E file
PARAC PARAC file
XML XML files 4.0+
file string any File name 3.1+
HKCR or HKEY_CLASSES_ROOT
HKEY_CLASSES_ROOT
HKCU or HKEY_CURRENT_USER
HKEY_CURRENT_USER
HKLM or HKEY_LOCAL_MACHINE
HKEY_LOCAL_MACHINE
HKCC or HKEY_CURRENT_CONFIG
HKEY_CURRENT_CONFIG
HKU or HKEY_USERS HKEY_USERS
- Set if type PARAC 3.4+
path string <IniPath> Reference to INI file 3.1+
<RegPath> Refers to registry
<Property> Property in property file 3.4+
<PcePath> Reference to PC/E file
<ParacPath> Reference to PARAC file
<XmlPath> Reference to XML file 4.0+
merge boolean TRUE If a <RegPath> refers to registry 3.4+
path, this path is not deleted
before restoration.
FALSE If a <RegPath> refers to registry
path, this path will be deleted
before restoration.

Example 2-44 Specification of a KeepValue definition for a value to be saved

The definition ProClassic

This definition generates all required definitions for a preceding ProClassic
command

98 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Example 2-45 Specification of a ProClassic definition
<Definition>
...
<ProClassic/>
...
</Definition>

Document version: 002 Reference and Using – User Guide 99

J/Install reference
J/Install

The definition Variable

This command reads a parameter value from a file or the Windows Registry
and assigns it to a user-specific variable.
Attribute definitions
Name Type Value Meaning V
type string INI INI file 3.4+
REG Registry
PROPERTY Properties file
PCE PC/E file
XML XML files 4.0+
file string any File name 3.4+
HKCR or HKEY_CLASSES_ROOT
HKEY_CLASSES_ROOT
HKCU or HKEY_CURRENT_USER
HKEY_CURRENT_USER
HKLM or HKEY_LOCAL_MACHINE
HKEY_LOCAL_MACHINE
HKCC or HKEY_CURRENT_CONFIG
HKEY_CURRENT_CONFIG
HKU or HKEY_USERS HKEY_USERS
path string <IniPath> Reference to INI file 3.4+
<RegPath> Refers to registry
<Property> Property in property file
<PcePath> Reference to PC/E file
<XmlPath> Reference to XML file 4.0+
name string any Variable name 3.4+
default string any Default value 3.4+

Example 2-46 Specification of Variable definition

100 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command Delete
This command deletes one or more files or directories.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

fallback boolean TRUE Automatical extending of fallback 4.1+

information with the files being
processed by this command
FALSE No automatical extending of fallback
information

Element definitions
Name Type Value Meaning V
Type string FILE Deletes files. 3.0+
DIR Deletes directories.
Name string any File or directory to be deleted; for 3.0+
type FILE wildcards ‚?’ for single
characters or ‚*’ for any strings can
be used; for type DIR no wildcards
are allowed.
A text file with a list of Name entries
can be provided with prefix {List}.
Extended syntax (V6.9+):
Comma-separated list of filenames
or folder names that shall be deleted.
Backup boolean TRUE The file to be deleted will be saved 3.7+
with '.bak' extension before deletion.
FALSE File will be removed without backup.
PendingFileHan boolean TRUE If a file is being accessed by other 3.4+
dling applications, it will be deleted during
the restart of the Windows system.
FALSE If a file cannot be deleted because it
is used by other applications, an
error occurs.

Example 2-47 Example for the use of the command Delete

<Delete description="Deleting file">
<Type>FILE</Type>
<Name>c:\install\[Link]</Name>
</Delete>

<Delete description="Deleting folder">

<Type>DIR</Type>
<Name>c:\install\custom</Name>
</Delete>

<Delete description="Deleting files">

<Type>FILE</Type>
<Name>{List}c:\list_files.txt</Name>
</Delete>

Document version: 002 Reference and Using – User Guide 101

J/Install reference
J/Install

The command DeleteRegistryKey

This command deletes one or more Registry entries from the Registry of the
operating system.
Attribute definitionen
Name Type Value Description V

description string any Text describing the command 6.9+

ignoreerror boolean TRUE Errors are ignored during processing 6.9+

FALSE Errors cause cancellation of
processing

Element definitionen
Name Type Value Meaning V
Name string any Simple syntax: 6.9+
Name of Registry key to be deleted.
Extended syntax:
Comma-separated list of Registry
keys to be deleted.

Note: All Registry keys have to

provided including Hive. Both Hive
formats (short and long) are
supported.
Examples:
HKLM\SOFTWARE\Wincor Nixdorf,
HKEY_LOCAL_MACHINE\
SOFTWARE\Wincor Nixdorf

Example 2-48 Deleting one Registry keys with command DeleteRegistryKey

<DeleteRegistryKey description="Delete all unnecessary registry keys.">
<Name>HKLM\SOFTWARE\Wincor Nixdorf\ProTopas </Name>
</DeleteRegistryKey>

Example 2-49 Deleting more than one Registry keys with command DeleteRegistryKey
<DeleteRegistryKey description="Delete all unnecessary registry keys.">
<Name>{V:[Link]}</Name>
</DeleteRegistryKey>

where
<Variable description="List of registry keys which MAY NOT exist before
installation.">
<Name>[Link]</Name>
<Value>HKLM\SOFTWARE\Wincor Nixdorf\ParacNT,HKLM\SOFTWARE\Wincor Nixdorf\
ProInstall,HKLM\SOFTWARE\Wincor Nixdorf\ProTopas</Value>
</Variable>

102 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command Dialog
This command interprets a dialog file.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Type string INI INI file (ProInstall) 3.0+
File string any Filename of dialog file 3.0+

Example 2-50 Example for the use of the command Dialog

<Dialog>
<Type>INI</Type>
<File>c:\install\custom\[Link]</File>
</Dialog>

Processing dialogs using INI files

Files using the INI or properties format can be created or modified using a
dialog.
A dialog can have the following representations:
• numeric input; input of variable or fixed length
• variable input; alphanumeric input of variable or fixed length
• Option box; single or multiple selection

Structure of a dialog control file

Section Keyword Value Meaning

[DIALOG] CHAIN xx Number of dialogs

[DIALOG<x>]1 Dialog specification

1.<x> within the keyword represents the incrementing number of keyword CHAIN

Example 2-51 Dialog sections

[DIALOG]
CHAIN = 1

[DIALOG1]
...

You can use the keywords below to enter numeric and alphanumeric values.
The value is appended on the parameter to be entered. Bold keywords must
be used, all others are optional.

Document version: 002 Reference and Using – User Guide 103

J/Install reference
J/Install

Keyword Value Meaning

TEXT <String> Dialog text
TYPE NUMVAR Numeric value of variable length
NUMFIX Numeric value of fixed length
CHARVAR Alphanumeric value of variable length
CHARFIX Alphanumeric value of fixed length
WRITEPARAM Setting of the parameter value as defined with VALUE
without using a dialog box
VALUE <String> Parameter Value
LENGTH xx Maximum input length
FILE<x> <File name> Filename incl. path that contains the parameter; <x>
can be omitted or can have the value 1 to 99
By using various FILE, SECTION and IDENT entries,
the parameter can be written to more than onen place
in this file.
SECTION<x> <Section> Section in which the parameter is to be written; this
keyword may not be given if the file has properties
format.
IDENT<x> <Keyword> Key of the parameter to be written.
DEFAULT <String> Value that is provided as default.
STEP <Section> Jumps to another dialog or section.
FRONT <String> Prefix; the value is prepended before the parameter to
be entered.
APPEND <String> Suffix

If the dialog represents a dropdown list box, use the keywords below. The
value is appended on the parameter to be entered. Bold keywords must be
used, all others are optional.

Keyword Value Meaning

TEXT <String> Dialog text
TYPE OPTVAR Selection box with multiple selections (check box)
OPTFIX Selection box with single selection (option box or radio
button)
WRITEPARAM Setting of the parameter value as defined with VALUE
without using a dialog box
VALUE <String> Parameter Value
FILE<x> <File name> Filename incl. path that contains the parameter; <x>
can be omitted or can have the value 1 to 99 By using
various FILE, SECTION and IDENT entries, the
parameter can be written to more than one place in this
file; the first entry is applied without <x> (value).

104 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Keyword Value Meaning
SECTION<x> <Section> Section in which the parameter is to be written; this
keyword may not be given if the file has properties
format.
IDENT<x> <Keyword> Key of the parameter to be written.
CHAIN xx Number of dialog elements
FIELD<x> <String> Selectable text to be displayed; max. 10 values for
selection can be provided; <x> within the keyword
represents the increasing number from keyword
CHAIN.
ON_VALUE<x> <String> Assigns the selection FIELD <x> the value that is to be
written
#LINK# New dialog that shall be called if this option was
selected
LINK<x> <Section> Specification of the dialog that is to be called with entry
#LINK#
EXIT Ends dialog
STEP <Section> Jumps to another dialog or section.

Using LINK, STEP and RETURN

The keywords LINK, STEP and RETURN are jump lables. Their value refers to
the position of the dialog that is being accessed to proceeed with the
procedure.
You can use LINK and STEP to jump to any position in a dialog whereas using
RETURN always returns to the starting point.

Important
Note that using LINK requires a dialog area that is composed of the name of
the current dialog and the LINK entry. If, for example, a link to DSPL is set in
area DIALOG1, an area with the name DIALOG1DSPL is expected.

The dialog of ProInstall is cancelled if the jump label does not exist.

Sample dialogs
The following two dialog examples should give an idea of how dialogs are
structured and keywords can be used.
The first example includes two dialogs:
• an interface card has to be selected
• an X.25 call number must be entered.
In order to comprehend the examples better dialogs, the individual lines are
numbered and commented at the end of the dialog.

Example 2-52 Coding and comments for the first dialog sample
1) [DIALOG]
2) CHAIN = 2

Document version: 002 Reference and Using – User Guide 105

J/Install reference
J/Install

3) [DIALOG1]
4) TEXT = Please choose Rocket Board Card Type
5) TYPE = OPTFIX
6) CHAIN = 2
7) FIELD1 = Rocket PCI
8) FIELD2 = Rocket ISA
9) ON_VALUE1 = RocketPCIP2.nt4
10)ON_VALUE2 = RocketISAP2.nt4
11)FILE = C:\INSTALL\CUSTOM\[Link]
12)SECTION = STRICT_INSTALL_OEM
13)IDENT = PACKAGE3

14)[DIALOG1]
15)TEXT = own_X.25-Nummer
16)DEFAULT = 026411525011170
17)TYPE = NUMVAR
18)LENGTH = 15
19)FILE = C:\INSTALL\CUSTOM\[Link]
20)SECTION = X25
21)IDENT = LOCALADR

Comments
Line 1: Start of dialog
Line 2: Number of dialogs to be executed
Line 3: Dialog designation
Line 4: Assign text to be displayed
Line 5: Specify type of selection (dialog box - either/or decision)
Line 6: Number of selection options
Line 7: Text to be displayed for the first selection option
Line 8: Text to be displayed for the second selection option
Line 9: Value assigment of the first selection (internal)
Line 10: Value assignment of the second selection (internal)
Line 11: Address of file to be changed
Line 12: Section in file to be changed
Line 13: Parameter within the file to be changed to which the value should be
assigned
Line 14: Dialog designation
Line 15: Assign text to be displayed
Line 16: Input field (default value is preset)
Line 17: Define input type
Line 18: Restriction of input length
Line 19: Address of file to be changed
Line 20: Section in file to be changed
Line 21: Parameter within the file to be changed to which the value should be
assigned

The second example is more extensive. The STEP and LINK keywords are
used here. The specified dialog is used to configure a display and a keyboard,
and assign a value.

106 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Example 2-53 Coding and comments for the second dialog sample
1) [DIALOG]
2) CHAIN = 1

3) [DIALOG1]
4) TEXT = Please choose configuration type
5) TYPE = OPTFIX
6) CHAIN = 3
7) FIELD1 = Configure Display
8) FIELD2 = Configure Keyboard
9) FIELD3 = Exit
10)ON_VALUE1 = #LINK#
11)ON_VALUE2 = #LINK#
12)ON_VALUE3 = #LINK#
13)LINK1 = DSPL
14)LINK2 = KBD
15)LINK3 = EXIT
16)FILE = NONE
17)SECTION = NONE
18) IDENT = NONE

19)[DIALOG1DSPL]
20)TEXT = Display Configuration
21)TYPE = WRITEPARAM
22)FILE = C:\INSTALL\CUSTOM\[Link]
23)SECTION = HARDWARE
24)IDENT = DISPLAY
25)VALUE = xxxxxxx
26)LINK = DRIVER_DSPL

27)[DIALOG1DRIVER_DSPL]
28)TEXT = Driver for Display
29)TYPE = WRITEPARAM
30)FILE = C:\INSTALL\CUSTOM\[Link]
31)SECTION = DRIVER_DSPL
32)IDENT = DRIVER
33)VALUE = xxxxxxx
34)STEP = DIALOG1

35)[DIALOG1KBD]
36)TEXT = Keyboard Configuration
37)TYPE = WRITEPARAM
38)FILE = C:\INSTALL\CUSTOM\[Link]
39)SECTION = HARDWARE
40)IDENT = KEYBOARD
41)VALUE = xxxxxxx
42)STEP = DIALOG1

Comments for this example:

Line 1: Start of dialog
Line 2: Number of dialogs to be executed
Line 3: Dialog designation
Line 4: Assign text to be displayed
Line 5: Specify type of selection (dialog box - either/or decision)
Line 6: Number of selection options
Line 7: Text to be displayed for the first selection option
Line 8: Text to be displayed for the second selection option
Line 9: Text to be displayed for the third selection option
Line 10: Reference to LINK1
Line 11: Reference to LINK2
Line 12: Reference to LINK3

Document version: 002 Reference and Using – User Guide 107

J/Install reference
J/Install

Line 13: Define LINK references to next address

Line 14: Define LINK references to next address
Line 15: End of dialog
Line 16: As the main dialog is used only to control the menu and no
assignements
Line 17: or references are input in lines 16 to 18, NONE
Line 18: must have to in these fields.
Line 19: Dialog designation (name + LINK reference=> see line 13)
Line 20: Assign a useful text, for example, purpose of this dialog
Line 21: No (yet) displaying of the text, just reference to direct setting of a
parameter
(without dialog control)
Line 22: Address of file to be changed
Line 23: Section in file to be changed
Line 24: Parameter within the file whose value is to be changed
Line 25: Fixed parameter input that shall be assigned
Line 26: Jump to next address in dialog that starts further processing
Line 27: Dialog designation (name + LINK reference=> see line 27)
Line 28: Assign a useful text, for example, purpose of this dialog
Line 29: No (yet) displaying of the text, just reference to direct setting of a
parameter
(without dialog control)
Line 30: Address of file to be changed
Line 31: Section in file to be changed
Line 32: Parameter within the file whose value is to be changed
Line 33: Fixed parameter input that shall be assigned
Line 34: Jump to next address in dialog that starts further processing
Line 35: Dialog designation (name + LINK reference=> see line 14)
Line 36: Assign a useful text, for example, purpose of this dialog
Line 37: No (yet) displaying of the text, just reference to direct setting of a
parameter
(without dialog control)
Line 38: Address of file to be changed
Line 39: Section in file to be changed
Line 40: Parameter within the file whose value is to be changed
Line 41: Fixed parameter input that shall be assigned
Line 42: Jump to next address in dialog that starts further processing

108 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command Exception
This command stops the processing of the control file and generates an error
message. Use this command, for example to simulate a runtime error.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 4.1+

ignoreerror boolean TRUE Errors are ignored during processing 4.1+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Description V
Text string any Error message to be displayed 4.1+

Example 2-54 Example for the use of command Exception

<Exception>
<Text>Requirements not fulfilled.</Text>
</Exception>

Document version: 002 Reference and Using – User Guide 109

J/Install reference
J/Install

The command Execute

Using this command you can start programs.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 1.4+

ignoreerror boolean TRUE Errors are ignored during 1.4+

processing
FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Program string any Name and path of the 1.0+
program to be executed
Access string WOW32 Accessing the 32 bit area of 5.0+
the file system
WOW64 Accessing the 64 bit area of
the filesystem
ErrorCode integer any numerical Expected return values in -2.2
value case of execution errors; 3.0+
multiple values are separated
using the pipe symbol ('|')
ErrorFile string any The existence of such a file -2.2
indicates that the processing 3.0+
results in errors; multiple
values are separated using
the pipe symbol ('|')
ErrorLogFileContent string any Directory and file name of a 1.4+
ToAdd log file; the contents of the log
file are added to the file
specified by the element <
LogFile> .
ErrorLogFileContent string any Character set, for example 4.0+
ToAddEncoding ISO-8859-1, UTF-8, UTF-16
Folder string any Specification of a working 3.0+
directory
LogFile string any Complete path to log file 1.4+
(inclusding filename); if this
element is empty or missing
the default
JINSTALL_ROOT%\
[Link] is used
LogFileEncoding string any Character set, for example 4.0+
ISO-8859-1, UTF-8, UTF-16

110 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Name Type Value Meaning V
LogFileContentToAd string any Directory and file name of a 1.4+
d log file; the contents of the log
file are added to the file
specified by the
element<LogFile>
LogFileContentToAd string any Character set, for example 4.0+
dEncoding ISO-8859-1, UTF-8, UTF-16
Parameters string any Call parameters 1.0+
Output boolean TRUE Console output of STDOUT, 4.1+
STDERR and Trail
FALSE No console output of
STDOUT, STDERR and Trail
PendingFileHandling boolean TRUE An existing Regsitry entry 4.2+
PendingFileRenameOperatio
ns is going to be removed
before carrying out the
command and restored after
running the command.
FALSE No manipulation of Registry
entry
PendingFileRenameOperatio
ns atall.
SuccessCode integer any numerical Expected return values in -2.2,
value case of a successful run; 3.0+
multiple values are separated
using the pipe symbol ('|')
SuccessFile string any The existence of such a file -2.2
indicates that the processing 3.0+
ends sucessfully; multiple
values are separated using
the pipe symbol ('|')
TailFile string any Directory and file name of a 4.1+
Tail file; the contant of that Tail
file is being appended to the
file specified with element
<LogFile>
TailFileEncoding string any Character set, for example 4.1+
ISO-8859-1, UTF-8, UTF-16
UnattendParameter string any valid call Call parameter for unattended 1.0+
parameter execution;
The parameter specified here
is used instead of the
parameter specified with the
<Parameter> element when
J/Install is executed with the
unattend calling parameter.
Variable string any Name of a user-specific 3.0+
variable that contains the
program exitcode

Document version: 002 Reference and Using – User Guide 111

J/Install reference
J/Install

Name Type Value Meaning V

Wait boolean TRUE There is a wait until the called 1.0+
command has been executed
FALSE Processing of the control file 1.0+
continues even though the
called command is still being
executed
WaitFile string any It is being wait until the -2.2
specified file was created 3.0+
within the filesystem;
multiple values are separated
using the pipe symbol ('|').

Example 2-55 Example for the use of the command Execute

<Execute description="Configuration" ignoreerror="true">
<Program>c:\install\custom\[Link]</Program>
<TailFile>c:\install\custom\[Link]</TailFile>
<SuccessCode>0</SuccessCode>
<ErrorCode>1|2|3</ErrorCode>
<Variable>[Link]</Variable>
</Execute>

Displaying processing of batch files

If the processing of batch files shall be displayed, use the tools
[Link] or [Link], respectively:
<Execute description="Batch" ignoreerror="true">
<Program>{E:JINSTALL_ROOT}\bin\[Link]</Program>
<Parameter>[Link] parameter1 parameter2</Parameter>
</Execute>

Note that the batch file must end with command exit!

Addressing the 64 bit filesystem area

The element Access is required only if on a 64 bit operating system the 64
bit filesystem area shall be addressed.
Otherwise on a 64 bit operating system the 32 bit J/Install application will
access the 32 bit filesystem area.
A detailed description of this topic is provide with this URL
[Link]
5).aspx.

112 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command Exit
This command ends the processing of the control file.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Code integer 0 The value '0' indicates the successful 3.0+
processing of the control file.
<>0 A value <>0 indicates the processing
stop after errors occur.
Text string any Error text to be displayed 3.4+

Example 2-56 Example for the use of the command Exit

<Exit>
<Code>10</Code>
<Text>Requirements not fulfilled.</Text>
</Exit>

Document version: 002 Reference and Using – User Guide 113

J/Install reference
J/Install

The command Extern

This command executes J/Install commands that are specified externally in a
properties file.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
File string any Filename of property file 3.0+
Prefix string any Significance if properties that start 3.0+
with this prefix
Task string Compress Command to be executed 3.0+
ConfAutologon
ConfNonAdmin
CopyFile
CreateDir
CreateList
CreateShortcut
Decompress
Definition
Delete
Execute
GetValue
Import
ModifyEnvironm
entVariable
ModifyTextFile
ModifyValue
Register
Script
SetVariable
WriteLog
WriteVersion

Example 2-57 Example for the use of the command Extern

<Extern>
<File>c:\install\custom\[Link]</File>
<Prefix>[Link]</Prefix>
<Task>Decompress</Task>
</Extern>

Structure of property file

Each line has the following structure (except for the commands Definition and
SetVariable):

<Prefix>.[<numeric counter>.]<element/attribute name>=<element/attribut value>

114 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Example 2-58 Sample of an external J/Install definition file (single occurence)
[Link] = unpack [Link]
[Link] = c:\install\custom\[Link]
[Link] = c:\

Example 2-59 Sample of an external J/Install definition file (more than one occurrence of the command)
[Link] = unpack [Link]
[Link] = c:\install\custom\[Link]
[Link] = c:\
#
[Link] = unpack [Link]
[Link] = c:\install\custom\[Link]
[Link] = c:\

Specification for command Definition

Example 2-60 Sample of an external J/Install file for Definition

[Link] = INI
[Link] = c:\[Link]
[Link] = [boot loader]timeout
[Link] = DIR
[Link] = c:\package
[Link] = true

Specification for command SetVariable

Example 2-61 Sample of an external J/Install file for SetVariable

[Link] = WN
[Link] = true
[Link] = false
[Link] = false
[Link] = c:\install\custom\[Link]

If for a <Value> the string {Ask} or {AskEncr} or {Ask:<Default>} or

{AskEncr:<Default>}, respectively, is set, the value is going to be requested
during runtime.
Whereas for the value {Ask:<Default>} or {AskEncr:<Default>} the string
<Default> is preset in the input field, the input field is empty if using the value
{Ask} or {AskEncr}.

[Link] = {Ask:WN}

{Ask} vs. {AskEncr}

AskEncr is different from Ask by the way that the entered string is being
encrypted.

If {Ask} or {AskEncr}, respectively, is used, the internal variable

IsCommonPasswordAsk with value ’true’ is going to be created. It is set when
the user was requested to enter the password of the non-administrative user.
This variable can be evaluated with the [Link] process control file.

Document version: 002 Reference and Using – User Guide 115

J/Install reference
J/Install

Numeric counter
Numeric counters must not have leading zeros.

116 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command Fallback
This command saves information that have been specified with the command
Definition and its elements FallbackValue, Fallback and
FallbackExecute<xxx>, and restores these information in case of errors or if
required for the installation.

Note
In addition, information that have been specified with command Definition
and its elements KeepValue and Keep, are being stored.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.1+

ignoreerror boolean TRUE Errors are ignored during processing 3.1+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Type string SAVE Saves the Fallback information 3.1+
RESTORE Restores the saved Falback
information
Folder string any Directory that shall be used to store 3.1+
the saved Fallback information for
type ='SAVE' (Default:
%JINSTALL_ROOT%\fallback)
OmitRegistry boolean TRUE Backup of Registry is omitted. 6.6+
FALSE Backup of Registry will be carried -6.8
out. For more information see below. 6.9+
Reboot boolean TRUE Automatic reboot after restoring of 3.4+
Fallback information
FALSE No automatic reboot after restoring
of Fallback information

Registry-Backup
If the Windows Registry shall be saved during processing the <Fallback>
command (element OmitRegistry is not present or set to ’FALSE’), the backup
processing is controlled by the <Fallback> entries of the <Definition>
command.
Complete backup of If no <Fallback> entries of type ’REG’ are present with the <Definition>
Registry command, the entire Registry will be saved. Saving is being carried out using
the [Link] tool. Note that administrative rights are required for a
complete Registry backup!
This scenarion has been supported by J/Install for several releases.

Document version: 002 Reference and Using – User Guide 117

J/Install reference
J/Install

Example 2-62 Complete backup of Registry

Partial backup of If there are any <Fallback> entries of type ’REG’ for the <Definition>
Registry command, only Registry keys specified there will be saved. Note that only
Registry keys of hive HKEY_LOCAL_MACHINE can be saved. The backup is
being carried out using the Windows tool [Link]. No administrative rights
are required for this type of backup. Therefor it is recommended for use cases
when J/Install is running with default user rights.

Example 2-63 Partial backup of Registry

In the example above only the Registry key HKEY_LOCAL_MACHINE\

SOFTWARE\Wincor Nixdorf will be saved.

Related information:
"The command Definition" on page 2-94

Example 2-64 Example for the use of command Fallback for type SAVE
<Fallback>
<Type>SAVE</Type>
<Folder>c:\jinstall\fallback</Folder>
<Reboot>TRUE</Reboot>
</Fallback>

Note
If, in case of an J/Install error or exception, Fallback information exist, that
were created by calling this command with type SAVE, these information will
be restored automatically by J/Install.

Fallback with unexpected program abortions

In case of unexpected program abortions or power blackouts J/Install is
unable to restore Fallback information unattended. For this reason the file
%JINSTALL_ROOT%\BIN\FALLBACK\[Link] should be run
during system startup. Ensure that the call of this file is carried out with
administrator rights.

118 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command GetSource
This command is used to request data media.
Attribute definitions
Name Type Value Description V

optional boolean TRUE Data medium request can be skipped 1.4+

without error message via the button
[Cancel]
FALSE Data medium request can not be
skipped. a directory must be selected.

description string any Text describing the command 1.4+

ignoreerror boolean TRUE Errors are ignored during processing 1.4+

FALSE Errors cause cancellation of
processing

fallback boolean TRUE Automatical extending of fallback 4.1+

information with the files being
processed by this command
FALSE No automatical extending of fallback
information

Element definitions
Name Type Value Meaning V
Text string any Request text for the data medium 1.0+
Variable string <Variable> User variable that saves the selected 2.0+
directory;
before the selection window is
opened, a check is performed to
determine whether the directory
stored in this variable meets the
requirements for the GetSource
command. If these requirements are
met, no data medium is selected.
Otherwise you can select the data
medium/directory in a dialog.
CopyDestination string any Target directory for the files to be 1.0+
copied;
the <CopySource> element must be
available
CopyRecursive boolean TRUE Sub-directories are copied 1.0+
FALSE Sub-directories are not copied;
the <CopySource> and
<CopyDestination> elements must
be available

Document version: 002 Reference and Using – User Guide 119

J/Install reference
J/Install

Name Type Value Meaning V

CopySource string any File mask with optional directory 1.0+
information (related to the selected
directory); use of the
Windows-specific wildcard
characters * and ? for character
strings and individual characters is
supported in the file mask
CopyType string ALWAYS Files are always copied 1.0+
NEWER Files are only copied if they are
newer than the files already installed
MultiDisk boolean TRUE Request for multiple data media 1.0+
FALSE Request for only one data medium
MultiDiskText string any Overwrites the default text hint 3.0+
during another medium request in
multi-disk operation
TagFile string any Tag file for identification of the data 1.0+
medium
TagFileContent string any Part of tag file content for 1.0+
identification of the data medium;
the <TagFile> element must be
available
TagFolder string any Tag directory for identification of the 3.0+
data medium; multiple values are
separated using the pipe symbol ('|').
TagLabelContent string any Part of data medium label content for 1.0+
identification of the data medium
PreserveDate boolean TRUE Applying date/time of source file 3.6+
FALSE Date/time of source file will be
changed to current system time for
target file
PreserveAttribute boolean TRUE Applying file attributes of source file 3.6+
on target file
FALSE Source file attributes will not be used;
Archive attribute will be set

Using placeholders
You can use the wildcard "{CurrentSource}", to access the data
medium/directory that the GetSource command has called last. The
placeholder is preset with the value from the JInstallCurrentSource
property in the [Link] file whenJ/Install is started.

Example 2-65 Example for the use of the command GetSource

<GetSource description="Requesting Registration key disk" >
<Text>Please insert registration key disk</Text>
<TagFile>reg_key.ini</TagFile>
<TagFolder>post</TagFolder>
<CopySource>*.*</CopySource>
<CopyDestination>c:\install\reg2</CopyDestination>
<MultiDisk>true</MultiDisk>
<MultiDiskText>Do you have another registration key disk?</MultiDiskText>
<Variable>REG</Variable>
</GetSource>

120 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command GetTextFile
Use this command to read a text line from a text file and assign it to a
user-spcific variable.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 4.1+

ignoreerror boolean TRUE Errors are ignored during 4.1+

processing
FALSE Errors cause cancellation of
processing

Elementdefinitionen
Name Type Value Description V
File string any Filename 4.1+
Line integer 1-x Line number 4.1+
Variable string any Variable name 4.1+
Default string any Default value 4.1+
Encoding string any Character set (for example 4.1+
ISO-8859-1, UTF-8, UTF-16)
Trim boolean TRUE Removes leading and trailing 4.1+
whitespace characters from the
line
FALSE No remove of whitespaces at all

Example 2-66 Example for the use of command GetTextFile

<GetTextFile>
<File>c:\[Link]</File>
<Line>10</Line>
<Variable>MyVar</Variable>
</GetTextFile>

Document version: 002 Reference and Using – User Guide 121

J/Install reference
J/Install

The command GetToken

Use this command to read a token from a token list and assign this token as
value to a user-specific variable.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.3+

ignoreerror boolean TRUE Errors are ignored during 3.3+

processing
FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Input string any List of token 3.3+
Variable string any Variable name 3.3+
Token integer any Token to be searched for; 3.3+
alternatively a token can be
addressed directly via
{TokenPos}<Position>, whereas
the token list starts with 1
Delimiter string any Delimiter for token list 3.3+
CaseSensitive boolean TRUE Case-sensitive check 3.3+
FALSE No case-sensitive check

Example 2-67 Example for the use of the command GetToken

<GetToken>
<Input>Jxfs30,JDevice,Common</Input>
<Delimiter>,</Delimiter>
<Token>(?i)jxfs.*</Token>
<Variable>MyVar</Variable>
</GetToken>

122 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command GetValue
This command reads a parameter value from a file or the Windows Registry
and assigns it to a user-specific variable. The checked entries are addressed
via file paths. For a description of the different addressing procedures see
section "Data access paths" on page 2-174.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 2.0+

ignoreerror boolean TRUE Errors are ignored during 2.0+

processing
FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Type string INI INI file 2.0+
REG Registry
PROPERTY Properties file
PCE PC/E file
XML XML files 4.0+
File string any File name 2.0+
HKCR or HKEY_CLASSES_ROOT
HKEY_CLASSES_ROOT
HKCU or HKEY_CURRENT_USER
HKEY_CURRENT_USER
HKLM or HKEY_LOCAL_MACHINE
HKEY_LOCAL_MACHINE
HKCC or HKEY_CURRENT_CONFIG
HKEY_CURRENT_CONFIG
HKU or HKEY_USERS HKEY_USERS
Path string <IniPath> Reference to INI file 2.0+
<RegPath> Refers to registry
<Property> Property in property file
<PcePath> Reference to PC/E file
<XmlPath> Reference to XML file 4.0+
Variable string any Variable name 2.0+
default string any Default value 2.0+

Document version: 002 Reference and Using – User Guide 123

J/Install reference
J/Install

Name Type Value Meaning V

Token string RegularExp Token to be searched; 3.3+
alternatively a token can be
addressed directly via
{TokenPos}<Position>,
whereas the token list starts
with 1
Delimiter string any Delimiter for token list 2.0+
CaseSensitive boolean TRUE Case-sensitive check 3.3+
FALSE No case-sensitive check

Special features when using INI files

When using the commend with an INI file, instead of using the value of an
entry, the name of an area that contains the entry can be retrieved.
For this reason, the value to be searched for has to be applied as regular
expression together with prefix {Value}.
If a specific entry is defined with the IniPath, it is now checked. If only an
area is specified with the IniPath all entries of this area will be checked.

Example 2-68 Example for the use of the command GetValue

<GetValue>
<Type>INI</Type>
<File>c:\hw\hw_conf.ini</File>
<Path>[1750103928]FILE1</Path>
<Variable>MyVar</Variable>
</GetValue>

<GetValue>
<Type>INI</Type>
<File>c:\hw\hw_conf.ini</File>
<Path>[{Value}^[Link]]FILE1</Path>
<Variable>MyVar</Variable>
</GetValue>

<GetValue>
<Type>INI</Type>
<File>c:\hw\hw_conf.ini</File>
<Path>[{Value}^[Link]]</Path>
<Variable>MyVar</Variable>
</GetValue>

<GetValue>
<Type>PROPERTY</Type>
<File>c:\[Link]</File>
<Path>[Link]</Path>
<Variable>MyVar</Variable>
</GetValue>

<GetValue>
<Type>XML</Type>
<File>c:\[Link]</File>
<Path>/Custom/Variables/Variable[@name='Umlaute']</Path>
<Variable>MyVar</Variable>
<Default>default</Default>
</GetValue>

124 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command Import
This command imports Windws INF or Registry (Reg) files.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Type string INF INF files 3.0+
REG REG files
File string any Filename; by using wildcards more 3.0+
than one file can be processed
Access string WOW32 Accessing the 32 bit area of the file 5.0+
system
WOW64 Accessing the 64 bit area of the
filesystem
PostAction string NOTHING File will not be changed after 3.0+
importing.
DELETE File will be deleted after importing.
RENAME After importing the file will be
renamed as follows:
*.<Extension> -> *.P<Extension>

Example 2-69 Example for the use of the command Import

<Import>
<Type>INF</Type>
<File>c:\parac\inf\*.inf</File>
<PostAction>RENAME</PostAction>
</Import>

Addressing the 64 bit filesystem area

Document version: 002 Reference and Using – User Guide 125

J/Install reference
J/Install

The command Jre

This command installs Java JRE provided in the task elements. It supports
both, Oracle JRE and OpenJDK JRE installations.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 4.2+

ignoreerror boolean TRUE Errors are ignored during processing 4.2+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Folder string any Folder where the JRE to be installed 4.2+
is located; more than one filename
can be set by using the pipe symbol
('|'); filename of the setup must follow
the structure
jre-<version>-windows-<type>.exe,
for example
[Link].
Version string any or NONE Version of JRE to be installed; the 4.2+
version must be provided this way: 7.3+
<Family>u<Update>, for example
7u9; the keyword NONE suppresses
the JRE installation
As of version 7.3 J/Install supports
installation of Diebold Nixdorf
OpenJDK JRE. In this case the value
of Version must follow this format:
<Family>u<Update>dn.<Build>, for
example ’8u151dn.0’.
Please note usage of element
Destination below!
Variable string any Environment variable holding the 4.2+
installation folder for the JRE version
Destination string any Target destination where the JRE is 7.3+
to be installed.
This parameter is mandatory for
Diebold Nixdorf OpenJDK JRE
installations!
For Oracle JRE installations this
parameter is ignored.
Static boolean TRUE Static installation 4.2+
FALSE Patch-In-Place installation
Type string I586 x86 installation (32 bit) 4.2+
X64 x64 installation (64 bit)

126 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Example 2-70 Example for the use of command Jre with Oracle JRE installtion
with Oracle JRE installa

<Jre>
<Folder>{V:PROCLASSIC}\INSTALL\JRE</Folder>
<Version>7u9</Version>
<Variable>APPLICATION_JAVAHOME</Variable>
<Type>i586</Type>
<Static>false</Static>
</Jre>

Example 2-71 Example for the use of command Jre in ProFlex4 product installer
<Jre description="Installing JRE either from customizing disk or from CD.">

<Folder>{V:CUSTOM_FOLDER}|{V:PROCLASSIC}\INSTALL\JRE|{V:CUSTOM_FOLDER}\
JRE</Folder>
<Version>{V:[Link]}</Version>

<Destination>{E:ProgramFiles}\Java\jre1.{V:[Link]}</Destination>
<Variable>APPLICATION_JAVAHOME</Variable>
<Type>{V:[Link]}</Type>
<Static>{V:[Link]}</Static>
</Jre>

Static and Patch-In-Place Oracle JRE installations

A detailed description of the installation types ’static’ and ’patch-in-place’ is
provided here:
[Link]
[Link]

Document version: 002 Reference and Using – User Guide 127

J/Install reference
J/Install

The command Keep

This command saves information that have been specified with the command
Definition and its elements KeepValue and Keep , and restores them if
required.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Type string SAVE Storing the Keep information 3.0+
RESTORE Restores the saved Keep information
Folder string any Directory that shall be used to store 3.0+
the saved Keep information for type
SAVE (Default:
%JINSTALL_ROOT%\keep)

Example 2-72 Example for the use of the command Keep

<Keep>
<Type>SAVE</Type>
<Folder>c:\jinstall\keep</Folder>
</Keep>

128 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command Loop
This command is processing all commands within element Do in a loop.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

Example 2-73 Example for the use of command Loop

<Loop>
[loop type]
<Do>
[command(s)]
</Do>
</Loop>

The loop type is specified with the elements below:

Element Meaning V
Counter Executing a defined number of loop runs; see "The Counter loop" on 4.1+
page 2-130
Endless Endless execution; see "The Endless loop" on page 2-130 4.1+
FileExists Execution if a file or directory exists; see "The FileExists loop" on 4.1+
page 2-130
TextFile Linewise execution of a text file; see "The TextFile loop" on page 2-131 4.1+
TokenString Execution of a loop according to the number of tokens in a provided 6.3+
token list; see "The condition TokenExists" on page 2-75

Within the element Do these internal variables can be used:

Name Meaning
LoopCounter Loop counter starts with ’1’.
LoopValue Loop value regarding of the loop type, for example the current token if loop
type is ’TokenString’

Document version: 002 Reference and Using – User Guide 129

J/Install reference
J/Install

The Counter loop

The Counter loop runs a defined number of loops.
Attribute definitions
Name Type Value Meaning V
start integer any Start value 4.1+
end integer any End value 4.1+
step integer any Increasing value of loop counter per 4.1+
loop (default = 1)

Example 2-74 Example of loop type Counter

<Loop>
<Counter start="10" end="20" step="2" />
<Do>
[command(s)]
</Do>
</Loop>

The Endless loop

This loop type is executing loops as long as its is being stopped with the
command LoopEnd of type BREAK.

Example 2-75 Example of loop type Endless

<Loop>
<Endless/>
<Do>
[command(s)]
<LoopEnd>
<Type>BREAK</Type>
</LoopEnd>
[command(s)]
</Do>
</Loop>

The FileExists loop

This loop is running as long as a file or directory exists.
Attribute definitions
Name Type Value Meaning V
name string any File or directory; the use of placeholder ’*’ 4.1+
for strings and ’?’ for single characters is
permitted.
evaluate string MustBeMet File/directory must exist 4.1+
MustNotBeMet File/directory must not exist
type string FILE Check for file 4.1+
DIR Check for directory

Example 2-76 Exampe of loop type FileExists

<Loop>
<FileExists name="c:\result.*" type="FILE" evaluate="MustNotBeMet" />
<Do>
[command(s)]
</Do>
</Loop>

130 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The TextFile loop
This loop is being executed according to the lines of a text file.
Attribute definitions
Name Type Value Meaning V
file string any Filename 4.1+
empty boolean TRUE Empty lines are being considered as 4.1+
lines
FALSE Empty lines are not being considered
encoding string any Character set (for example ISO-8859-1, 4.1+
UTF-8, UTF-16)
resolve boolean TRUE Resolving of J/Install variables 4.1+
FALSE No resolving of J/Install variables
trim boolean TRUE Removing of leading and trailing 4.1+
whitespaces
FALSE No removing of whitespaces at all

Example 2-77 Example of loop TextFile

<Loop>
<TextFile file="c:\[Link]" resolve="false" />
<Do>
[command(s)]
</Do>
</Loop>

The TokenString loop

This loop is being executed according to the number of tokens provided with a
token list.
Attribute definitions
Name Type Value Meaning V
input string any Token list 6.3+
delimiter string any Delimiter to separate the tokens in the 6.3+
provided list
trim boolean TRUE Removing of leading and trailing 6.3+
whitespaces
FALSE No removing of whitespaces at all

Example 2-78 Example of loop TokenString

<Loop>
<TokenString input="Token1,Token2,Token3, Token4" delimiter="," trim="true"/>
<Do>
[command(s)]
</Do>
</Loop>

Document version: 002 Reference and Using – User Guide 131

J/Install reference
J/Install

The command LoopEnd

This command stops an entire loop or the current loop run.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Description V
Type string BREAK Stops the complete loop 4.1+
CONTINUE Stops the current loop run

Example 2-79 Example for command LoopEnd

<Loop>
[loop type]
<Do>
[command(s)]
<LoopEnd>
<Type>CONTINUE</Type>
</LoopEnd>
[command(s)]
</Do>
</Loop>

132 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command ModifyEnvironmentVariable
This command is used to change the value of environment variables.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.3+

ignoreerror boolean TRUE Errors are ignored during 3.3+

processing
FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V

Mode string Set Set value 3.3+

Remove Delete a value
Replace Replace a value
TokenRemove Delete a token from list
TokenRemoveBegin Remove token at the beginning 4.0+
of list
TokenRemoveEnd Remove token at the end of list
TokenRemoveBefore Remove a token before
another token
TokenRemoveAfter Remove a token behind
another token
TokenSetBegin Put token at the beginning of 3.3+
list
TokenSetEnd Put token at the end of list
TokenSetBefore Put a token before another
token
TokenSetAfter Put a token after another token
TokenSet Put token in position "Search"

Name string any Name of environment variable 3.3+

Extended syntax (V6.9+):
Comma-separated list of
environment variables to be
processed.

Value string any The value that must be set 3.3+

Search string RegularExp Value to be replaced or token 3.3+

to be searched; alternatively a
token can be addressed
directly via
{TokenPos}<Position>,
whereas the token list starts
with 1

Document version: 002 Reference and Using – User Guide 133

J/Install reference
J/Install

Name Type Value Meaning V

Delimiter string any Delimiter for token list 3.3+

User boolean TRUE User-specific environment 3.3+

variable
FALSE System-specific environment
variable

Example 2-80 Examples for command ModifyEnvironmentVariable

<ModifyEnvironmentVariable>
<Name>PROTOPAS_ROOT</Name>
<Mode>Set</Mode>
<Value>c:\protopas</Value>
</ModifyEnvironmentVariable>
<ModifyEnvironmentVariable>
<Name>PATH</Name>
<Mode>TokenSetEnd</Mode>
<Value>c:\protopas\bin</Value>
<Delimiter>;</Delimiter>
</ModifyEnvironmentVariable>

134 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command ModifyPendingFile
This command is used to change the Registry entry
PendingFileRenameOperations.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.3+

ignoreerror boolean TRUE Errors are ignored during 3.3+

processing
FALSE Errors cause cancellation of
processing

Element definitionens
Name Type Value Description V

Mode string AddDelete Insert deletion entry 4.2+

AddRename Insert renaming entry
RemoveDelete Remove deletion entry
RemoveRename Remove renaming entry
Optimize Optimizing all entries

Source string any Name of file to be deleted or 4.2+

renamed; for removing a
regular expression is to be
used.

Destination string any Target name of file for 4.2+

renaming; for removing a
regular expression is to be
used.

Example 2-81 Example for command ModifyPendingFile

Optimizing entries:
<ModifyPendingFile>
<Mode>Optimize</Mode>
</ModifyPendingFile>

Adding the deletion of a file:

<ModifyPendingFile>
<Mode>AddDelete</Mode>
<Source>c:\data\[Link]</Source>
</ModifyPendingFile>

Adding the renaming of a file:

<ModifyPendingFile>
<Mode>AddRename</Mode>
<Source>c:\data\jinstall.1</Source>
<Destination>c:\data\[Link]</Destination>
</ModifyPendingFile>

Removing deletion of a file:

<ModifyPendingFile>
<Mode>RemoveDelete</Mode>
<Source>.*\\[Link]</Source>
</ModifyPendingFile>

Document version: 002 Reference and Using – User Guide 135

J/Install reference
J/Install

The command ModifyString

This command modifies a string.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.3+

ignoreerror boolean TRUE Errors are ignored during processing 3.3+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Description V
Input string any Character string 3.3+
Search string RegularExp Regular expression of value to be searched 3.3+
Value string any Value to be set; using the string {RegEx} the 3.3+
result of the regular expression of element
"Search" can be addressed
Occurrence string First Limitation of first value found 3.3+
Every Considers all found values
Variable string any Variable name 3.3+
CaseSensitive boolean TRUE Case-sensitive check 3.3+
FALSE No case-sensitive check

Example 2-82 Example for the use of the command ModifyString

<ModifyString>
<Input>Jxfs30,JDevice,Common</Input>
<Search>Jxfs..</Search>
<Value>-{RegEx}-</Value>
<Occurrence>First</Occurrence>
<Variable>MyVar</Variable>
</ModifyString>

136 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command ModifyTextFile
This command is used to change text files. Use the element Mode to control
the command operation. Depending of the selected mode you can add, delete
or exchange text lines. You can also replace or delete portions of text in a line.
You can use regular expressions for the text you want to change. The section
"Using regular expressions" on page 2-171 describes the different possibilities.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 2.0+

ignoreerror boolean TRUE Errors are ignored during 2.0+

processing
FALSE Errors cause cancellation of
processing

fallback boolean TRUE Automatical extending of 4.1+

fallback information with the
files being processed by this
command
FALSE No automatical extending of
fallback information

Element definitions
Name Type Value Meaning V

File string any Filename, a text file with a list 2.1+

of File entries can be provided
with prefix {List}.

Mode string AddFileBegin Adds file at beginning of file 4.0+

AddFileEnd Appends file at file end
AddFileBefore Adds a file before another line
AddFileAfter Appends a file after another
line
AddLineBegin Adds line at beginning of file 2.1+
AddLineEnd Adds line at end of file
AddLineBefore Adds a line before another line
AddLineAfter Adds a line after another line
AddTextBegin Insert text at line start 4.1+
AddTextEnd Appends text at line end
AddTextBefore Inserts text before text into a
line
AddTextAfter Adds text after text into a line

Document version: 002 Reference and Using – User Guide 137

J/Install reference
J/Install

Name Type Value Meaning V

RemoveLine Removes a line 2.1+
RemoveText Removes text in a line
ReplaceLine Replaces a line
ReplaceText Replaces text in a line

Encoding string any Character set, for example 4.0+

ISO-8859-1, UTF-8, UTF-16

Occurrence string First Limitation of action to first 2.1+

found line
Every Considers all found lines

Line string Regular Expr' The value that the line must 2.1+
contain so that it is found

Value string any Value to be set; using the string 2.1+

{RegEx} the result of the
regular expression of element
"Search" can be addressed

Search string Regular Expr' The value that must be 2.1+

replaced or deleted

CaseSensitive boolean TRUE Case-sensitive check 3.3+

FALSE No case-sensitive check

FileToAdd string any Name of file to be added 4.0+

FileToAddEncoding string any Character set, for example 4.0+

ISO-8859-1, UTF-8, UTF-16
HideDetails boolean TRUE Shows (setting FALSE)/hides 7.0+
(setting TRUE) details about
FALSE the modification made by the
task when logging task
activities in the J/Install log file.

Example 2-83 Example for the use of the command ModifyTextFile

Replace text in a line
<ModifyTextFile fallback="true">
<File>{I:ProductHomeDir}\etc\[Link]</File>
<Mode>ReplaceText</Mode>
<Line>.*\{!APBI LIB FOLDER!\}.*</Line>
<Occurrence>First</Occurrence>
<Search>\{!APBI LIB FOLDER!\}</Search>
<Value>APBI folder</Value>
</ModifyTextFile>

Add line at beginning of file:

<ModifyTextFile>
<File>{I:ProductHomeDir}\etc\[Link]</File>
<Mode>AddLineBegin</Mode>
<Value>Comment</Value>
</ModifyTextFile>

138 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Add a line at the beginning of various files:
<ModifyTextFile>
<File>{List}c:\list_files.txt</File>
<Mode>AddLineBegin</Mode>
<Value>Comment</Value>
</ModifyTextFile>

Appending a file after another line:

<ModifyTextFile>
<File>{I:ProductHomeDir}\etc\[Link]</File>
<Encoding>UTF-8</Encoding>
<Mode>AddFileAfter</Mode>
<Line>.*\{!APBI LIB FOLDER!\}.*</Line>
<FileToAdd>c:\[Link]</FileToAdd>
<FileToAddEncoding>UTF-8</FileToAddEncoding>
</ModifyTextFile>

Suppress details in change log (Example Masking user password in

[Link]:
<ModifyTextFile
description="Modify the [Link] in the target folder. Mask the value of
[Link] parameter.">
<File>{E:JINSTALL_ROOT}\[Link]</File>
<Encoding>UTF-8</Encoding>
<Mode>ReplaceText</Mode>
<Line>^common\.password\s*=.*</Line>
<Occurrence>First</Occurrence>
<Search>^common\.password\s*=.*</Search>
<Value>[Link] = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</Value>
<HideDetails>true</HideDetails>
</ModifyTextFile>

Document version: 002 Reference and Using – User Guide 139

J/Install reference
J/Install

The command ModifyToken

This command changes a list of tokens.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.3+

ignoreerror boolean TRUE Errors are ignored during 3.3+

processing
FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Description V
Input string any List of token 3.3+
Delimiter string any Separator 3.3+
Mode string TokenRemove Deletes a token from list 3.3+
TokenRemoveBegin Removes token at the beginning of 4.0+
list
TokenRemoveEnd Removes token at the end of list
TokenRemoveBefore Removes a token before another
token
TokenRemoveAfter Removes a token behind another
token
TokenSetBegin Puts token at the beginning of list 3.3+
TokenSetEnd Puts token at the end of list
TokenSetBefore Inserts token before position
"Token"
TokenSetAfter Inserts token after position "Token"
TokenSet Puts token in position "Token"
Variable string any Variable name 3.3+
Token string RegularExp Token to be searched; alternatively 3.3+
a token can be addressed directly
via {TokenPos}<Position>, whereas
the token list starts with 1
Value string any the value that must be set 3.3+
CaseSensitive boolean TRUE Case-sensitive check 3.3+
FALSE No case-sensitive check
Occurrence string First Limitation of first value found 3.3+
Every Considers all found values

140 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Example 2-84 Example for the use of the command ModifyToken
<ModifyToken>
<Input>Jxfs30,JDevice,Common</Input>
<Delimiter>,</Delimiter>
<Mode>TokenSetAfter</Mode>
<Token>(?i)jxfs.*</Token>
<Value>Custom</Value>
<Variable>MyVar</Variable>
</ModifyToken>

Document version: 002 Reference and Using – User Guide 141

J/Install reference
J/Install

The command ModifyValue

sets a parameter value in file or Windows Registry You can use regular
expressions for the value you want to change. The checked entries are
addressed via file paths. For a description od the different addressing
procedures see section "Data access paths" on page 2-174.
Use the element Mode to control the command operation.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 2.0+

ignoreerror boolean TRUE Errors are ignored during 2.0+

processing
FALSE Errors cause cancellation of
processing

fallback boolean TRUE Automatical extending of 4.1+

fallback information with the file
being processed by this
command
FALSE No automatical extending of
fallback information

Element definitions
Name Type Value Meaning V

Type string INI INI file 2.0+

REG Registry
PROPERTY Properties file
PCE PC/E file
PARAC PARAC file 3.3+
XML XML files 4.0+

File string any File name 2.0+

HKCR or HKEY_CLASSES_ROOT
HKEY_CLASSES_ROOT
HKCU or HKEY_CURRENT_USER
HKEY_CURRENT_USER
HKLM or HKEY_LOCAL_MACHINE
HKEY_LOCAL_MACHINE
HKCC or HKEY_CURRENT_CONFIG
HKEY_CURRENT_CONFIG
HKU or HKEY_USERS HKEY_USERS

142 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Name Type Value Meaning V

Path string <IniPath> Reference to INI file 2.0+

<RegPath> Refers to registry
<Property> Pproperty in property file
<PcePath> Reference to PC/E file
<ParacPath> Reference to PARAC file 3.3+
<XmlPath> Reference to XML file 4.0+

Mode string Set Sets value 2.0+

Remove Deletes a value
Replace Replaces a value
TokenRemove Deletes a token from list
TokenRemoveBegin Removes token at the 4.0+
beginning of list
TokenRemoveEnd Removes token at the end of
list
TokenRemoveBefore Removes a token before
another token
TokenRemoveAfter Removes a token behind
another token
TokenSetBegin Puts token at the beginning of 2.0+
list
TokenSetEnd Puts token at the end of list
TokenSetBefore Inserts token before position
"Search"
TokenSetAfter Inserts token after position
"Search"
TokenSet Puts token in position "Search"

Value string any Value to be set; using the string 2.0+

{RegEx} the result of the
regular expression of element
Search can be addressed

Search string RegularExp Value to be replaced or token to 2.0+

be searched; alternatively a
token can be addressed
directly via
{TokenPos}<Position>,
whereas the token list starts
with 1

Delimiter string any Delimiter for token list 2.0+

CaseSensitive boolean TRUE Case-sensitive check 3.3+

FALSE No case-sensitive check

Document version: 002 Reference and Using – User Guide 143

J/Install reference
J/Install

Example 2-85 Example for the use of the command ModifyValue

Setting property in property file:
<ModifyValue fallback="true">
<Type>PROPERTY</Type>
<File>c:\[Link]</File>
<Path>[Link]</Path>
<Mode>Set</Mode>
<Value>show</Value>
</ModifyValue>

Deleting value in ini file

<ModifyValue>
<Type>INI</Type>
<File>c:\[Link]</File>
<Path>[boot loader]timeout</Path>
<Mode>Remove</Mode>
</ModifyValue>

Replacing value in registry:

<ModifyValue>
<Type>REG</Type>
<File>HKLM</File>
<Path>[SOFTWARE\Wincor Nixdorf\CSC-W32\CurrentVersion\CSCCNG]LOAD</Path>
<Mode>Replace</Mode>
<Search>FRONT</Search>
<Value>FRONTDOOR</Value>
</ModifyValue>

Adding token at the end of PC/E file

<ModifyValue>
<Type>PCE</Type>
<File>{I:[Link]}/config/[Link]</File>
<Path>Components</Path>
<Mode>TokenSetEnd</Mode>
<Value>SopIntegrated</Value>
<Delimiter>,</Delimiter>
</ModifyValue>

Adding token before token "Common" in PC/E file

<ModifyValue>
<Type>PCE</Type>
<File>{I:[Link]}/config/[Link]</File>
<Path>Components</Path>
<Mode>TokenSetBefore</Mode>
<Value>SopIntegrated</Value>
<Delimiter>,</Delimiter>
<Search>Common</Search>
</ModifyValue>

Changing token in position 2 in PC/E file

<ModifyValue>
<Type>PCE</Type>
<File>{I:[Link]}/config/[Link]</File>
<Path>Components</Path>
<Mode>TokenSet</Mode>
<Value>SopIntegrated</Value>
<Delimiter>,</Delimiter>
<Search>2</Search>
</ModifyValue>

144 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command ModifyVariable
This command changes the value of a variable or assigns a new value to a
variable. You can use patterns for the value you want to change. The section
"Using patterns" on page 2-172 describes the different possibilities. Use the
element Mode to control the command operation.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 2.2+

ignoreerror boolean TRUE Errors are ignored during processing 2.2+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V

Name string any Name of variable 3.7+

Type string INT Changing of an integer value 2.2+

DATE Changing of a date expression
STRING Changing of a string

Mode string = Assigning a value 2.2+

+ Increasing by value Value
- Decreasing by value Value

Value string any Value to be change, increased or decreased 2.2+

according to Mode setting. The entry ‚now’ returns
the current system date if Type is set to ‘DATE’.

Pattern string any Pattern that is used to represent a numeric value 2.2+
or a date.
Default settings:
for DATE: ’yyyy/MM/dd HH:mm’
for INT: ####################
A description of the patterns can be found in the
section "Using patterns" on page 2-172.

Unit string Millisecond, Specification of part of date that is to be changed 2.2+

Second, according to attribute Mode.
Minute,
Hour, Day,
Week,
Month, Year

Index string <start> Restriction of part of string that is to be changed. 2.2+

Document version: 002 Reference and Using – User Guide 145

J/Install reference
J/Install

Example 2-86 Example for the use of the command ModifyVariable

Assign the current system date:
<ModifyVariable>
<Name>MyVar</Name>
<Type>DATE</Type>
<Value>now</Value>
<Mode>=</Mode>
<Pattern>yyyy/MM/dd HH:mm</Pattern>
</ModifyVariable>

Incrementing day of date:

<ModifyVariable>
<Name>MyVar</Name>
<Type>DATE</Type>
<Value>1</Value>
<Mode>+</Mode>
<Pattern>yyyy/MM/dd HH:mm</Pattern>
<Unit>Day</Unit>
</ModifyVariable>

Assigning numeric value:

<ModifyVariable>
<Name>MyVar</Name>
<Type>INT</Type>
<Value>12345</Value>
<Mode>=</Mode>
<Pattern>000000</Pattern>
</ModifyVariable>

Decrease numeric value:

<ModifyVariable>
<Name>MyVar</Name>
<Type>INT</Type>
<Value>5</Value>
<Mode>-</Mode>
<Pattern>000000</Pattern>
</ModifyVariable>

Assigning string:
<ModifyVariable>
<Name>MyVar</Name>
<Type>STRING</Type>
<Value>Dies ist ein Test.</Value>
<Mode>=</Mode>
</ModifyVariable>

Appending string to string:

<ModifyVariable>
<Name>MyVar</Name>
<Type>STRING</Type>
<Value>..</Value>
<Mode>+</Mode>
</ModifyVariable>

Changing string:
<ModifyVariable>
<Name>MyVar</Name>
<Type>STRING</Type>
<Value>x</Value>
<Mode>=</Mode>
<Index>16,16</Index>
</ModifyVariable>

146 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command OsBootLogo
This command changes the boot logo of the operating system.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of processing

fallback boolean TRUE Automatical extending of fallback information 4.1+

with the file being processed by this command
FALSE No automatical extending of fallback information

Element definitions
Name Type Value Meaning V

File string any Source directory and filename of graphics file 3.0+
(file format for Windows XP: BMP, 640x480, 16
Farben)

Example 2-87 Example for the use of the command OsBootLogo

<OsBootLogo>
<File>c:\install\custom\[Link]</File>
</OsBootLogo>

Document version: 002 Reference and Using – User Guide 147

J/Install reference
J/Install

The command ProClassic

This command checks/installs the ProClassic application and installs
permanent licences in order to remove demo licences.
Attribute definitions
Name Type Value Description V

description string any Text describing the 3.0+

command

ignoreerror boolean TRUE Errors are ignored during 3.0+

processing
FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V
Type string CHECK Check of fulfillment of 3.0+
installation requirements
INSTALL Installation
SOURCECORRECTION Installing
SourceCorrections
LICENCE Installing permanent
licences
CONFIG Reconfiguration of 7.0+
ProTopas Repository
Manager.
J/Install provides a
ready-to-use script using
this task mode:
%JINSTALL_ROOT%\bin\
proclassic\config\
[Link]
File string any Filename of property file 3.0+
Prefix string any Significance if properties 3.0+
that start with this
’<Prefix>.’
RegFolder string any Directory of RegKey files 3.0+

Example 2-88 Example for the use of the command ProClassic

<ProClassic>
<Type>CHECK</Type>
<RegFolder>c:\install\reg</RegFolder>
<Prefix>proclassic</Prefix>
<File>c:\install\custom\[Link]</File>
</ProClassic>
<ProClassic>
<Type>INSTALL</Type>
</ProClassic>

The properties file has the following structure:

148 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Example 2-89 Sample of properties file for ProClassic installation
[Link]/[Link] = 20
[Link]/[Link] = NVISION
[Link]/[Link] =
add2,shop_base,shop_postalpf,shop_postalst
[Link]/[Link] = YES
[Link]/[Link] = WN_WHITE_BLUE
[Link] = 33a
[Link].HW_DETECTION = NO
[Link].HW_REG = [Link]
proclassic.PROTOPAS_BASE.VERSION = 12a
[Link] = 00a

Structure of the ProClassic CD

The ProClassic CD contains all components required for a software product.
The products that the customers want to install on their self-service terminals
are selected using a registration key from the key disc. The release to be
installed is specified customer-specific with the customizing.
For products that are to be installed from the product CD the customers need a
licence agreement.

Directory structure
On CD the directory Install is located that contains all components that are
required for the installation of the product. For each product different releases
can be provided. For some products an additional differentiation of various
product variants is possible.

Figure 2-1 Structure of the Install directory for a ProClassic installation

Software and release determination

The definition, which release of a software product is to be installed, is
determined in two different ways. These procdures are called 'registration key
procedure' and 'product registration procedure'. During an installation both
procedures might be used.
With both procedures, the file REG_KEY.INI can contain default parameters
for customizing. The values of these parameters can be overwritten by the
customizing itself.

Document version: 002 Reference and Using – User Guide 149

J/Install reference
J/Install

A product differentiation is being made using the terms version and release.
The release identifies the scope of work of the product whereas the version
contains also the patch level of the product in addition to the scope of work.
The terms Version and Release are illustrated with the product ProChip/EMV
21.01 in the sample below:

Product Rrelease Version (Release + Patch level)

ProChip/EMV 21 21.01

The registration key disc

The registration key disc contains information on, which products are to be
installed, that means it contains the registration keys. This disc customers will
receive if they have signed a licence agreement for the corresponding
software. The information regarding the registration keys is stored on the disc
in file REG_KEY.INI.
Since the creation date and time of the file as well as the file attributes are part
of the protection algorithm, it is essential to preserve those information during
a copy procedure. Modifications of this file result result in the effect that an
installation cannot be performed.
If additional software products are purchased, for example ProChip or ProScan
(add-on products, i.e. licenced extensions of applications), other registration
key disc are being added.
To minimize the number of discs, the files on the individual the separate discs
can be combined on one disc. Note that, except from the original file
REG_KEY.INI, all other files are given a three-digit extension in numeric
ascending order starting with REG_KEY.001.

Example 2-90 Possible content of a registration key disc:

REG_KEY.INI (Standard full product)
REG_KEY.001 (ProChip add-on product)
REG_KEY.002 (ProCashIN/Offline add-on product)
REG_KEY.003(ProView/Client standard full product)

Demo registration keys and licenced registration keys

These variants have the following differences:
• Licenced registration keys allow the unrestricted usage of the product
• Demo registration keys allow the usage of a product only for a limited
timeframe (in days) starting from the installation day. Demo registration
keys can be changed into licenced registration keys without reinstallation.
Licenced registration keys and demo registration keys can be differentiated
with the entry TOPICAL. For example, the value 'TOPICAL=180' specifies that
the installation can be used for 180 days starting from the day of installation.

150 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Licenced registration keys:
[SECURITY]
INITIALMASTER =498815095
Demo registration keys:
[SECURITY]
INITIALMASTER =499815681
TOPICAL=180

Replacing demo registration keys with licenced registration keys

With ProClassic installations with one or more demo registration keys, the
following file is being created:

%JINSTALL_ROOT%\[Link]

Demo registration keys can be replaced by licenced registration keys using a

batch file.

%JINSTALL_ROOT%\bin\proclassic\demo\[Link]

This batch file requires the directory where the licenced registration keys are
stored. Only those demo registration keys will be replaced where name and
version match the name and version of the corresponding registration key.
If all demo registration keys are replaced by licenced registration keys, the file
[Link] is being deleted and the demo registration key procedure
will be deactivated.
The unattended installation of licenced registration keys (for example remote)
can be carried out with the following commands:

[Link] -u -v "REG=<directory with permanent licences>"

[Link] --unattend --variable "REG=<directory with permanent licences>"

The registration key procedure

For this procedure the following requirements must be met:
• REG_KEY.INI (REG_KEY.001, REG_KEY.002, ….) (below only the name
REG_KEY.INI is used)
• Customizing
The release of a product or of a component is specified by the first two digits of
its version. The release of a product and of all components belonging to this
product are stored in file REG_KEY.INI.

File integrity
The file REG_KEY.INI is protected and may not be modified. Each
modification causes an invalidating of this file, and thus, this file cannot be
processed anymore.

The last two digits (patch level) are determined by the customizing. If
necessary, this part of the version identifier might be changed by the system
integrator.

Document version: 002 Reference and Using – User Guide 151

J/Install reference
J/Install

An installation of a componnet can be prevented if the keyword NONE is used

instead of the patch level.
The figure below illustrates the determination of the version with the
registration key procedure:

Figure 2-2 Version determination using the registration key procedure

Installing a specific component type with the registration key procedure

Product components exist whose version are characterized by different types.
An example of such a product component is ProCashIn/Online. For this
component, the same version exists for CRS NDC as well as for CRS DDC.
The figure below illustrates how the customizing can be used to access a
specific component type, using the registration key procedure as example.

Figure 2-3 Component installation using the registration key procedure

152 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The product registration key procedure
The product registration key procedure has been introduced to enhance the
flexibility in supplying software products. For this procedure the following
requirements must be met:
• REG_KEY.INI (REG_KEY.001, REG_KEY.001, …..); below only the name
REG_KEY.INI is used
• [Link]; this file is located on the ProInstall CD, and it is secured
similar to the REG_KEY.INI file
• Customizing
With this procedure the release identifier of the product is set in the
REG_KEY.INI. The last two digits (patch level) of the version are specified by
the customizing. For example, the product ProCash/NDC emulation version
1.5/00 is specified by the entry '15' in file REG_KEY.INI and entry '00' in file
[Link].
The component versions of product ProCash/NDC emulation is defined with
file [Link]. Here you find the complete version identifier of this
component, for example, ProTopas 41.35. The patch level of the release can
again be overwritten by the customizing.
The figure below illustrates the version determination. In this example a
ProCsh/NDC emulation of version 15.00 will be installed. Among others, this
product contains the component ProTopas version 41.35 in its default scope of
delivery. With customizing this version is overwritten, ProTopas 41.40 will be
installed instead.

Figure 2-4 Version determination using the product registration key procedure

Document version: 002 Reference and Using – User Guide 153

J/Install reference
J/Install

Installing a specific product type with the product registration key

procedure
Product components exist whose version are characterized by different types.
An example of such a product component is ProTopas/Base. For this product
component the same version for Wincor Nixdorf hardware as well as for
MultiVendor hardware is available.
The figure below illustrates how customizing accesses a specific product type.

154 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Figure 2-5 Determination of installation components case 1: Common method / overloading
component version

Figure 2-6 Determination of installation components case 2: Common method / Disabling

component installation

Document version: 002 Reference and Using – User Guide 155

J/Install reference
J/Install

Figure 2-7 Determination of installation components case 3: Extended method / full component
version

Figure 2-8 Determination of installation components case 4: Extended method / Overloading

component version

156 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Figure 2-9 Determination of installation components case 5: Extended method / Default component
version

SourceCorrections
If a file [Link] is located in directory <cdrom>\<product>\
<version>\SRCCORR or <cdrom>\<product>\<type>\<version>\
SRCCORR, resp., this file will be unpacked into the root directory of drive C:
after the product installation has been carried out.
In parallel to a ZIP file, a SourceCorrection with the same name and format
can be stored in folder SRCCORR, that is decompressed into the target folder of
the origin ZIP file after decompressing all product archives and before
configuring the product, after the origin ZIP file has been processed.
SourceCorrections might not only located in sub-directory SRCCORR, but also
on the customizing medium in sub-directory SRCCORR. In order to process
those SourceCorrections, the file [Link] has to be extended
accordingly.

proclassic.<produkt>.SRCCORR.<archiv name> = <name>.ZIP

Example 2-91 Sample to submit SourceCorrections

[Link] = 00
[Link] = PROTOPAS_CSCW.ZIP
[Link] = PROTOPAS_PROTOPAS.ZIP
[Link] = PROTOPAS_SYSROOT.ZIP

Document version: 002 Reference and Using – User Guide 157

J/Install reference
J/Install

The file [Link]

The file [Link] is a properties file with the following
structure:

Prefix Description
jre JRE settings
definition Specification for command Definition
root Directory Definition
version Alternative version representation that is being displayed in the
overview and that is stored with file [Link].
Example: version=23.00

General parameters
Parameters Description
version Alternative version representation that is being
displayed in the overview and that is stored with file
[Link].
Example: version=23.00

Specification for Specification as follows:

command Definition
definition.[<numeric counter>.]<definition>.<attribute> = <attribute value>

Directory Definition Specification of directory, referred by the ZIP file's content. By using the
wildcards '?' for any single character or '*' for any strings, more than one file
can be addressed.

root.<ZIP file> = <Directory>[|<Directory>]

158 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command Register
This command register existing files (OCX, DLLs) or fonts with the operating
system.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.7+

ignoreerror boolean TRUE Errors are ignored during processing 3.7+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V

Type string FILE OCX or DLL files 3.7+

FONT Font files

File string any Filename; by using wildcards more than one file 3.7+
can be processed
Access string WOW32 Accessing the 32 bit area of the file system 5.0+
WOW64 Accessing the 64 bit area of the filesystem

Example 2-93 Example for the use of the command Register

<Register>
<Type>FILE</Type>
<File>c:\protopas\web\ocx\*.ocx</File>
</Register>

Addressing the 64 bit filesystem area

Document version: 002 Reference and Using – User Guide 159

J/Install reference
J/Install

The command Restart

This command restarts the system or logs off and logs on a user to the system.
When further commands follow in the file [Link], processing of the
file is resumed from this point after the new log-on.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of
processing

Element definitions
Name Type Value Meaning V

Type string REBOOT Reboots the system 3.0+

RELOGON Logs off a user and then logs on

Mode string AUTO Reboot/Relogon without user 3.0+

interaction
ASK User can choose between
reboot/relogon or proceeeding with
the current session.
CAUTION: During an unattended
installation ASK is being treated
similar to NO.
COMMIT A reboot/relogon is to be confirmed by
the user.
CAUTION: During an unattended
installation COMMIT is being treated
similar to YES.
NO Supressing reboot/relogon 3.3+
YES Reboot/Relogon without user 3.5+
interaction

Domain string any Domain for automatic logon 3.0+

Username string any Username for automatic logon 3.0+

Password string any Encrypted or plain password of user 3.0+

Username to be used for the
automatic login during processing.
The encrypted password can be
created using the
%JINSTALL_ROOT%\BIN\
[Link] tool.
Private boolean TRUE Secret storing of password (starting 3.9+
with Windows XP SP2)
FALSE No secret storing of password

160 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
Name Type Value Meaning V
ExternTrue string Type|File|Path|Value Value that is written instead of 4.0+
reboot/relogon. For more detailed
information about value parts, see the
section "The command ModifyValue"
on page 2-142.
ExternFalse string Type|File|Path|Value Value that is written instead of no 4.0+
reboot/relogon. For more detailed
information about value parts, see the
section "The command ModifyValue"
on page 2-142.

Example 2-94 Example for the use of the command Restart

Document version: 002 Reference and Using – User Guide 161

J/Install reference
J/Install

The command Script

This command interprets a J/Install file.

Not available commands

In the J/Install file the command Restart is not allowed to be executed.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.3+

ignoreerror boolean TRUE Errors are ignored during processing 3.3+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V
File string any Filename of J/Install file 3.3+
Return boolean TRUE Modfications of variables will affect the calling 3.7+
script
FALSE Modifications of variables will be effective in the
called script only

Example 2-95 Example for the use of the command Script

<Script>
<File>c:\install\custom\[Link]</File>
<Return>true</Return>
</Script>

162 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command SetVariable
This command assigns a value to a user-specific variable.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V
Name string any Name of variable 3.0+
Value string any Value of variable 3.0+

Index string <start> Limitation of part of string that is to be 3.7+

<start>,<end> assigned.
Counting starts with ‚1’.

Example 2-96 Example for the use of the command SetVariable

Assigning of value 'true':
<SetVariable>
<Name>[Link]</Name>
<Value>true</Value>
</SetVariable>

Assigning of substring 'test' as variable value:

Assigning of substring 'test' as variable value:

<SetVariable>
<Name>[Link]</Name>
<Value>this is a test value</Value>
<Index>11.14</Index>
</SetVariable>

Document version: 002 Reference and Using – User Guide 163

J/Install reference
J/Install

The command ShowMessage

This command displays as message box.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V
Text string any Text to be displayed 3.0+

Example 2-97 Example for the use of the command ShowTextFile

<ShowMessage>
<Text>Requirements not fulfilled.</Text>
</ShowMessage>

The Message box displayed by the task can be closed by clicking either [ OK ]
button (alternatively press ENTER key on the keyboard) or by [ X] button
(alternatively press ESC key on the keyboard).
Which option was selected is stored in the internal J/Install variable
[Link]. Possible values are either ’OK’ or ’Cancel’. This
variable can be evaluated later in the [Link] script that is running the
<ShowMessage> task.

Example 2-98 Evaluating Message box input

<ShowMessage>
<Text>Non-admin user's password verification failed! Enter another
password.</Text>
</ShowMessage>
<Condition operator="AND" description="Does the user want to enter password once
again or cancel the whole installation?">
<VariableExists name="[Link]" type="I"/>
<StringCheck
name="{I:[Link]}"
expression="OK"
evaluate="MustNotBeMet"/>
<True>
<Exit description="User interrupted password entry and canceled the
installation.">
<Code>25</Code>
</Exit>
</True>
</Condition>

164 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command ShowTextFile
This command displays the content of a text file.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V
File string any File name 3.0+
Encoding string any Character set, for example ISO-8859-1, UTF-8, 4.0+
UTF-16
CancelButton boolean TRUE Displays the additional button [Cancel]. Clicking 3.0+
the [Cancel] button results in a error situation.
FALSE Only the button [OK] is being displayed. Clicking
the [OK] button will continue the installation
procedure with the next command.

Example 2-99 Example for the use of the command ShowTextFile

<ShowTextFile>
<File>c:\install\error</File>
<Encoding>UTF-8</Encoding>
<CancelButton>true</CancelButton>
</ShowTextFile>

Document version: 002 Reference and Using – User Guide 165

J/Install reference
J/Install

The command TuneOs

This command configures the operating system in general and for a specific
user.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 3.0+

ignoreerror boolean TRUE Errors are ignored during processing 3.0+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V

File string any Name of a ZIP file, that contains an alternative 3.0+
structure that is being processed instead of the
directory %JINSTALL_ROOT%\bin\tuneos.

Example 2-100 Example for the use of the command TuneOs

<TuneOs>
<File>c:\install\custom\[Link]</File>
</TuneOs>

All files with extension .cmd, .reg, .reg64, .inf and .inf64 will be run,
that are located in sub-directory %JINSTALL_ROOT%\bin\tuneos.
General settings are located in sub-directory \all and are being installed with
J/Install.
User-specific configurations are located in directory \user and will be
processed with the first user logon by calling the batch file
%JINSTALL_ROOT%\bin\tuneos\[Link].
This script is created automatically by J/Install while its run. Changes made by
the script are logged in the file C:\JINSTALL\bin\tuneos\
[Link].

Example 2-101 Calling a user-specific configuration

...
@ECHO OFF
REM
REM Check user
@ECHO.
ECHO **********************************
ECHO *** Check application user ***
ECHO **********************************
@ECHO.
%JINSTALL_ROOT%\BIN\[Link]
IF "%ERRORLEVEL%"=="1" EXIT
REM
REM Check configuration tag file
IF EXIST %JINSTALL_ROOT%\BIN\TUNEOS\[Link] GOTO AFTER_USERCONFIG
IF NOT EXIST %JINSTALL_ROOT%\BIN\TUNEOS\[Link] GOTO AFTER_USERCONFIG
REM
REM Configure user
@ECHO.
ECHO ******************************
ECHO *** User Configuration ***
ECHO ******************************
@ECHO.
CALL %JINSTALL_ROOT%\BIN\TUNEOS\[Link]
REM

166 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
REM Reboot or Logoff
%JINSTALL_ROOT%\BIN\[Link] T:5
REM %JINSTALL_ROOT%\BIN\[Link] T:5
PAUSE
REM
:AFTER_USERCONFIG
...

The internal structure of the ZIP file must be similar to structure

%JINSTALL_ROOT%\bin\tuneos, whereas directory %JINSTALL_ROOT%\
template\tuneos can be used as a template:

\ALL (general settings)

\<OS> (contains general operating system settings)
\USER (user-specific settings)
\<OS> (contains user-specific operating system settings)

A list of all available settings is provided with file %JINSTALL_ROOT%\

template\tuneos\[Link].

File execution
Files with extesions .cmd64, .reg64 and .inf64 will be run on 64 bit
operating systems in the 64 bit area whereas they will be ignored on a 32 bit
operating system.
All other files with extesion .cmd, .reg and .inf will be run on a 64 bit
operating system in the 32 bit area and without restrictions on a 32 bit
operating system.

Document version: 002 Reference and Using – User Guide 167

J/Install reference
J/Install

The command Wait

This command causes waiting for a specified number of seconds or a key
stroke.
Attribute definitions
Name Type Value Description V

description string any Text describing the command 1.4+

ignoreerror boolean TRUE Errors are ignored during processing 1.4+

FALSE Errors cause cancellation of processing

Element definitions
Name Type Value Meaning V

Duration integer 0 Waiting for manual operation 1.4+

1-x Number of seconds to be waited

Text string any Text of notice 1.4+

Example 2-102 Example for the use of the command Wait

<Wait>
<Duration>30</Duration>
<text>wait 30 seconds</text>
</Wait>

168 Reference and Using – User Guide Document version: 002

The main area "Sequence"

J/Install
The command WriteLog
This command adds a log entry to an existing log file.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 1.4+

ignoreerror boolean TRUE Errors are ignored during processing 1.4+

FALSE Errors cause cancellation of processing

fallback boolean TRUE Automatical extending of fallback 4.1+

information with the file being processed
by this command
FALSE No automatical extending of fallback
information

Element definitions
Name Type Value Meaning V
Entry string any Log entry 1.0+
File string any Full log file details (including path); 1.0+
if this element is not being used, the log
entries will be written into file
%JINSTALL_ROOT%\[Link].
Encoding string any Character set, for example ISO-8859-1, 4.0+
UTF-8, UTF-16
AddLogFileContent string any Directory and file name of a log file; the 1.0+
contents of the log file are added to the
J/Install log File
AddLogFileContent string any Character set, for example ISO-8859-1, 4.0+
Encoding UTF-8, UTF-16
AddVariables boolean TRUE The internal and user-specific variables 3.3+
are written to the log file File
FALSE No logging of internal and user-specific
variables

Example 2-103 Example for the use of the command WriteLog

<WriteLog description=“J/Bos installation“>
<Entry>J/Bos log file:</Entry>
<AddLogFileContent>c:\install\[Link]</AddLogFileContent>
<AddLogFileContentEncoding>UTF-8</AddLogFileContentEncoding>
</WriteLog>

Document version: 002 Reference and Using – User Guide 169

J/Install reference
J/Install

The command WriteVersion

An entry was added, changed or removed to or from a Versions properties file.

Attribute definitions
Name Type Value Description V

description string any Text describing the command 1.4+

ignoreerror boolean TRUE Errors are ignored during processing 1.4+

FALSE Errors cause cancellation of processing

fallback boolean TRUE Automatical extending of fallback information with 4.1+

the file being processed by this command
FALSE No automatical extending of fallback information

Element definitions
Name Type Value Meaning V
Name string any Name of software 1.0+
Value string any Version of software -3.6
Value string any Version of software; a previous entry will be 3.7+
removed if no value is provided
File string any Full details of the version file (including path); 1.0+
if the element is not used, the version is written
into file %JINSTALL_ROOT%\[Link].

Example 2-104 Example for the use of the command WriteVersion

<WriteVersion>
<Name>Wincor_Nixdorf_PC/E-SmartClient/Base</Name>
<Value>V2.1/01 (Build 0145)</Value>
</WriteVersion>

170 Reference and Using – User Guide Document version: 002

Values and addressing of data

J/Install
Values and addressing of data
In some commands you can use regular expressions in attibutes or elements
to extend comparisons to a certain section. Using these expressions you can
describe characters or character strings by patterns. This can be compared to
the use of the wildcards '?' and '*' for file name specifications like, for example,
in file selection dialogs. You can use regular expressions to define more
precise constraints. For more informagtion on using regular expressions see
section: "Using regular expressions" on page 2-171.
J/Install can process different file formats. All files are accessed via paths.
J/Instal encapsulates the file access. You only need to know the type of the
configuration file and the entry in this file to access this entry. The section
"Data access paths" on page 2-174 describes the different possibilities.

Using regular expressions

Values can be entered as regular expressions for certain attributes of the
condition checking process. Regular expressions are patterns which can be
applied to a sign string to state whether the string meets certain requirements
(only numbers, two words and so on).
J/Install uses the regular expressions offered by JRE from version 1.4.2
onwards. A detailed description can be found on the Internet
([Link] class
[Link]).
Basic functionality
Sign (string) Description
single signs
X sign X
\\ backslash
\t tabulator
\n line break (LF)
Groups
[abc] a, b or c
[^abc] all signs except a, b, c (negation)
[a-zA-Z] all signs from a to z and A to Z (range)
partial expressions
. any sign
\d decimal number [0-9]
\D all signs except decimal numbers [^0-9]
\s whitespace (space, tabulator and so on) [\t\n]
\S all signs except whitespace [^\s]
\w all word signs (letters, numbers, underscore) [a-zA-Z_0-9]
\W all [Link] signs [^\w]

Document version: 002 Reference and Using – User Guide 171

J/Install reference
J/Install

Sign (string) Description

Position
^ line start
$ line end
Frequency
? none/once
* none or of arbitrary frequency
+ at least once
{n} exactly n times
{min,} at least min times
{,max} none until but not exceeding max times
{min,max} at least min times, but not exceeding max times

Considering lower and upper cases

No checking of case-sensivity is being performed if the regular expression
starts with the string '(?i)'. On the other hand, the string '(?-i)' switches on
case-sensivity.

Example The expression <String> matches the sign string <String>.

The expression .*<String>.* matches the sign string <String> in any position
of the checked sign string.
The expression .*<String>.* matches the sign string <String> at the
beginning of the checked sign string.
The expression .*<String>.* matches the sign string <String> at the end of
the checked sign string.

Using patterns
numbers, percentages and currencies
For pattern strings, the system uses the formatting definitions offered by JRE
version 1.4.2 and higher. A detailed description can be found on the Internet
([Link] Klasse
[Link]).

Formatting definition Meaning

0 represents a digit; if not used a ‚0’ is displayed
# represents a digit; if not used it remains empty to avoid
leading zeros and unused zeros behind the comma
. decimal separator separates decimal places
, groups the digits (one group is as large as the distance
between ‘,’ and ‘.’)

172 Reference and Using – User Guide Document version: 002

Values and addressing of data

J/Install
Formatting definition Meaning
; Separator on the left side positive numbers are represented,
whereas on the right negative numbers are represented
- the default sign used as negative prefix
% The number is multiplied by 100 and represented as
percentage value.
%% Similar to ‚%’ but represents per mill.
X All other signs (symbol X) can be used as usually.

Formatting dates
For pattern strings, the system uses the formatting definitions offered by JRE
version 1.4.2 and higher. A detailed description can be found on the Internet
([Link] class
[Link]).

Format: Meaning
y year
M month in year (1 to 12)
MM month in year (01 to 12)
MMM short month in year (Jan, Feb, … Dec)
MMMM long month in year (January, February, … December)
d day in month
h hour (1 to 12)
H hour in day (0 to 23)
m minute in hour
s second in minute
S millisecond
E day in week short (Mo, Tu, … Su)
EEEE day in week long (Monday, Tuesday, … Sunday)
D day in year
F day of week in month
w week in year (calendar week)
W week in month
a AM and PM text
k hour in day (1 to 24)
C hour (0 to 11)

Document version: 002 Reference and Using – User Guide 173

J/Install reference
J/Install

Data access paths

Using data paths you can define access to the contents of INI files, PC/E-,
XML- and property files or the Windows registry. These paths provide access
to the internal file structures. These files have different data structures. A
differentiation between these structures is made by an element Type or an
attribute type in the respective command. The file that is accessed via J/Install
can be defined in an element File or in an attribute file; the access path is
defined in the element Path or the attribute path.

Element or attribute
The file type, the file name and the access path is specified in conditions via
attribute definitions. In commands the file types, file names and access
paths are specified as elements.

Accessing INI files (<IniPath>)

INI files are divided into sections. These sections are structured by
parameter-value entries. J/Install supports the addressing of a section and the
addressing of a particular entry within this section.

Example 2-105 Extract from a trace INI file for ProPackage

[PARAMETER]
MODE = QUIET
FALLBACK = YES
ROLLBACK = NO
ROLLBACKMAX = 5
ONERROR = RENAME
REBOOT = PROPACKAGE
TMPDIR = C:\PACKAGE\TMP
PACKAGELOG = C:\PACKAGE\[Link]
HISTORYLOG = C:\PACKAGE\[Link]
VERSIONPROP = C:\JINSTALL\[Link]
PACKAGEDIR = C:\PACKAGE\UPDATE
FALLBACKDIR = C:\PACKAGE\FALLBACK
ROLLBACKDIR = C:\PACKAGE\ROLLBACK

Addressing a section: Sections are addressed by the section name in square brackets. [<Section>].

In the sample file the section [PARAMETER] can be accessed by

“[PARAMETER]“.

Addressing an entry Parameter-value entries in INI files are accessed by extending the path by the
parameter name: [<Bereich>]<Name>.

In the sample file the parameter PACKAGEDIR can be accessed by

“[PARAMETER]PACKAGEDIR“.

Accessing PARAC files (<ParacPath>)

PARAC files are of the same structure as INI files, except token list which have
a different format.

Accessing PC/E configuration files (<PcePath>)

PC/E configuration files have their own format. The two kinds of PC/E
configuration files are: PC/E configuration files with owner/section structure
and with no owner/section structure. The PC/E configuration files with no

174 Reference and Using – User Guide Document version: 002

Values and addressing of data

J/Install
owner/section are similar, but not identical to property files and must be treated
differently. For this reason you cannot access these files via the type
PROPERTY, but only via the type PCE .
New configuration sections in PC/E configuration files with an owner/section
structure are marked by the line @ Config . The entries Owner = <Owner>
and Section = <Section> define the name of the section.
Parameters in a configuration section are sepecified as follows:
<parameter name>.Value = “parameter value“
<parameter name>.Default = “default parameter value“
<parameter name>.Description = “parameter description“
<parameter name>.ID = “parameter ID that is unique in the PC/E system“

Note
The term "parameter" has different meanings within PC/E and the
customizing. In PC/E a "parameter" is the representation of <parameter
name>. In J/Install a "parameter" is the entire key (as in a property file) =>
<parameter name>.value.

Example 2-106 Section from PC/E configuration file with owner/section structure
Sample PC/E configuration file with owner/section structure
@ Config

Owner = "[Link]"
Section = "DEFAULT_SECTION"
Description = "Complete set of startup parameters. Some of them may be redefined
by the configuration of the server."
Id = "1123735270794"
Version = "1.0"
AccessMode = "Hidden"

[Link] = "wn/html/Init_Develop.html"
[Link] = "wn/html/Init_Develop.html"
[Link] = "First remote html page"
[Link] = "1120163308039"

[Link] = "15"
[Link] = "15"
[Link] = "Time in seconds,in which a
server must establish a connection for a client. Otherwise a lost connection is
assumed. This parameter is reset on reinitialize."
[Link] = "1121752084699"

...

Paths are specified by the owner, the section (section name) and the
parameter name.
Addressing a section Sections are addressed using the section name in square brackets:
[<Owner>:<Section>].

In the Example 2-106 file the section DEFAULT_SECTION of the owner

[Link] can be accessed using
“[[Link]:DEFAULT_SECTION]“.

Addressing a parameter Use the following pattern to address a parameter in a section:

in a section [<Owner>:<Section>]<Name>.

Document version: 002 Reference and Using – User Guide 175

J/Install reference
J/Install

In the Example 2-106 file the parameter [Link] can be

addressed by the following access path:
[[Link]:DEFAULT_SECTION]
[Link].

Addressing a section Use the following pattern to select a parameter, whose value fulfils a certain
parameter using condition: [<owner>:<section>]<name>[<condition>]. The formulation of the
conditions condition must conform to the common J/Install rules. For information about
J/Install rules see section "Addressing rules" on page 2-177.

If, for example, you want to address the

[Link] in the
Example 2-106 file, when its value is less than 20, enter
“[[Link]:DEFAULT_SECTION]
[Link][<20']“.

Example 2-107 Section from a PC/E configuration file with no owner/section structure
Variables = ./[Link], [Link]

Variant = {Variant}

[Link].0 = [Link]
[Link].14 = [Link]
[Link].15 = [Link]
[Link].16 = [Link]
[Link].17 = [Link]
[Link].18 = [Link]
[Link].26 = [Link]

[Link].0 = [Link]
[Link].4 = {JDeviceHome}/params/[Link]
[Link].5 = {JDeviceHome}/params/[Link]
[Link].5 = {JDeviceHome}/params/[Link]
[Link].7 = {JDeviceHome}/params/[Link]
[Link].8 = {JDeviceHome}/params/[Link]
[Link].9 = {JDeviceHome}/params/[Link]
[Link].10 = {JDeviceHome}/params/[Link]
[Link].11 = {JDeviceHome}/params/[Link]
[Link].12 = {JDeviceHome}/params/[Link]
[Link].13 = {JDeviceHome}/params/[Link]
[Link].18 = [Link]
[Link].19 = {JDeviceHome}/params/[Link]
[Link].20 = {JDeviceHome}/params/[Link]
[Link].21 = {JDeviceHome}/params/[Link]
[Link].22 = {JDeviceHome}/params/[Link]
[Link].23 = {JDeviceHome}/params/[Link]
[Link].24 = {JDeviceHome}/params/[Link]
[Link].25 = {JDeviceHome}/params/[Link]
[Link].26 = [Link]
...

Paths are specified by the parameter names only.

Addressing an entry Parameters in sections are addressed according to the scheme:<Name>.

The parameter [Link].0 in the Example 2-107 file is, for example,
addressed by the path “[Link].0“.

Addressing an entry Use the following pattern to select a parameter, whose value fulfils a certain
using conditions condition: <name>[<condition>].
The formulation of the condition must conform to the common J/Install rules.
For information about J/Install rules see section "Addressing rules" on
page 2-177.

176 Reference and Using – User Guide Document version: 002

Values and addressing of data

J/Install
If, for example, you want to address the parameter [Link].0 in the
Example 2-107 file, when ist value contains the string {JDeviceHome}, use
the following path: [Link].0[='.*{JDeviceHome}.*'].

Addressing a list entry Multiple entries (versions) of a parameter are marked by the addition
using conditions <number>. In this enumeration numbers may be missing. A condition must be
used to access these parameters independent from their numbers. Use the
following pattern to address these parameters: <name>.#[<condition>].
The statement of a condition has to follow these rules:
Addressing rules
Condition Meaning Example
='<Regular Expr>' Regular Expression must be met ='.*[Link]
$'
!='<Regular Expr>' Regular Expression may not be met !='.*[Link]
p$'
<<Value> less than <value> <20
<=<Value> less than <value> or equal <value> <=20
><Value> greater than <value> >20
>=<Value> greater than <value> or equal >=20
<value>
=<Value> equal to <Value> =20
!=<Value> unequal to <Value> !=20

If you want to address a parameter [Link].# with the string

[Link] as part of its content in the Example 2-107, use the
following path: [Link].#[='.*[Link]$'].

Accessing properties files (<property>)

Property files consist of key-value pairs with each pair listed in one line. Keys
and values are divided by the '=' sign. The parameter value is accessed via the
key.

Example 2-108 Sample properties file

[Link]=Default
[Link]=true
[Link]=true
[Link]=1.4
[Link]=true
[Link]=Windows
[Link]=C\:\\env\\Java\\j2re1.4.2_03\\bin\\[Link]
[Link]=1.4.2_03
[Link]=x86
[Link]=-classpath c\:\\pce/lib/[Link];c\:\\
pce/lib/[Link];c\:\\pce\\smartclient/lib/[Link];c\:\\
pce/lib/ext/[Link] -[Link]\
=[Link] -[Link]\=\=c\
:\\pce\\smartclient/config/security/[Link]
-[Link]\=c\:\\pce\\sop/config/security/[Link]
[Link]=Default
[Link]=http\://[Link]/products/autodl/j2se
[Link]=javaws-1.4.2_03
[Link]=hide
[Link]=true

Document version: 002 Reference and Using – User Guide 177

J/Install reference
J/Install

Apart from the key you need no further data to address properties.

Accessing Windows registry data (<RegPath>)

The Windows registry is a database with an hierarchical structure. The
Windows tool [Link] displays the database in a tree structure, similar
to a file system. The key represents the path to a parameter (like a directory in
a file system). The parameter itself is represented by a name, the data type
and its value/content (like a file in a file system).

Example 2-109 Sample registry entry

Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\CSC-W32\CurrentVersion\CSCCNG

Entry:
CURRENCIES (type: REG_SZ, Wert: 1)

Addessing keys: Keys are addressed via the name of the registry key (without main key) in
square brackets: [<Key>].

In the Example 2-109 the key is accessed via “HKLM“ and “[SOFTWARE\
Wincor Nixdorf\CSC-W32\CurrentVersion\CSCCNG]“.

Addressing entries: Entries (parameters) under a key can be accessed by extending the key
address by the parameter name: [<Key>]<Name>.

The parameter CURRENCIES, for example, is accessed via“[SOFTWARE\

Wincor Nixdorf\CSC-W32\CurrentVersion\CSCCNG]CURRENCIES“.

Addressing standard Each key has a default value. This default value can be accessed in the form:
entries [<Key>](Default).

In Example 2-109 the key is accessed via “[SOFTWARE\Wincor Nixdorf\

CSC-W32\CurrentVersion\CSCCNG](Default)“.

178 Reference and Using – User Guide Document version: 002

Values and addressing of data

J/Install
Addressing an entry and In general, a type specification is only required if the entry does not yet exist in
its type definition the Registry or the entry shall be written using a different type. These types are
supported: REG_SZ, REG_EXPAND_SZ, REG_MULTI_SZ, REG_DWORD,
and REG_BINARY. If an entry of type REG_EXPAND_SZ shall be read without
resolving its value automatically, the type REG_EXPAND_SZ must be
provided. Otherwise all placeholders will be resolved.

Type Representation Example

REG_SZ string ProCash_3100
REG_EXPAND_SZ string using type REG_EXPAND_SZ:
%USERPROFILE%\Local Settings\Temp
without using type REG_EXPAND_SZ:
D:\Data\DOCUME~1\<User>\LOCALS~1\Temp
REG_MULTI_SZ string[|string] Line1|Line2|Line3|Line4
REG_DWORD string 256
REG_BINARY string[,string] 20,a0,20

Use the following pattern to address entry types:: [<key>]<name>@<type>.

For Example 2-109 this results in “[SOFTWARE\Wincor Nixdorf\CSC-W32\

CurrentVersion\CSCCNG]CURRENCIES@REG_SZ“.

Addressing a key and an An access definition for a key is required only if with a 64 bit operating system
access definition a 64 bit Registry area shall be addressed .
Otherwise the access by the 32 bit application J/Install is performed within the
32 bit Registry area in a 64 bit operating system (HKEY_LOCAL_MACHINE\
SOFTWARE\Wow6432Node).

Note
A detailed description of this topic is provided with this URL:
[Link]

For addressig you use this syntax: [<Key>@<Access>]

Access Description
WOW32 Accessing the 32 bit area of the Registry (default)
WOW64 Accessing the 64 bit area of the Registry

For Example 2-109 this results in "[SOFTWARE\Wincor Nixdorf\CSC-W32\

CurrentVersion\CSCCNG@WOW64]CURRENCIES@REG_SZ".

Accessing XML files (<XmlPath>)

XML files are text files with hierarchical structured data. Addressing these data
by J/Install is carried out using XPath.
Selecting nodes In order to select nodes, XPath is using path expressions as known from the
file system.

Document version: 002 Reference and Using – User Guide 179

J/Install reference
J/Install

Expression Meaning
/ root node
// any structure depth
@ Attribute
* Wildcard

Example 2-110 Examples of selecting nodes

XPath Selection
/store root element <store>
/store/book All <book> elements below root element <store>
//store all <book> elements
/store/book/title/@lang all lang attributes of a <title> element below store/book
/store/* all child elements of root element <store>

Rating One or more rating expressions optional restrict the node amount.
Ratings are always embedded with brackets and evaluated from the left to the
right.

Example 2-111 Examples for using ratings

XPath Selection
/store/book[1] First <book> elements below root element <store>
/store/book[price] all <book> elemente that include a <price> child element
/store/book[price][2] the second <book> elemente that includes a <price> child element
//title[@lang] all <title> elements that have a lang attribute
//title[@*] all <title> elements that have any attribute

Operators XPath provides a variety of operators that can be used to compare values,
carry out calculations or evaluate expressions.

Operator Meaning
+ Addition
- Subtraction
* Multiplication
div Division
mod Modulo
= equal
!= not equal
< less than
> greater than
<= less than or equal

180 Reference and Using – User Guide Document version: 002

Values and addressing of data

J/Install
Operator Meaning
>= greater than or equal
and logical conjunction
or logical disjunction

Example 2-112 Examples of using operators

XPath Selection
//title[@lang='eng'] All <title> elements that have a lang attribute with value ’eng’
/store/book[price>35.00] All <book> elements below <store> that have a <price> element
larger than 35.00
/store/book[price>35.00 all <book> elements below <store> that have a <price> element
and @id] larger than 35.00 and an id attribute
/store/book[price>35.00] all <title> elements below <book> elements below <store> that
/title have a <price> element larger than 35.00

Error handling
Return codes
A returncode of '0' indicates a successful processing whereas a returncode
unequal '0' indicates the occurrence of errors.
Usually the returncodes '1' and '2' are used:

Returncode Meaning
0 no error
1 call parameter invalid
2 errors during processing
3 errors during processing and successful Fallback
4 Reboot
5 Relogon
6 Package exists

For own projects (for example 'Exit') returncodes higher than '100' should be
used.

Task ID
To enable restarts (see "The command Restart" on page 2-160) and to ease
the error analysis, each command in the J/Install file [Link] is being
assigned a unique ID that is written within brackets in the log file:

Example 2-113 Sample of Task ID

...
[Link] >>> Task 'Wait' [<ID>]:
...

Document version: 002 Reference and Using – User Guide 181

J/Install reference
J/Install

All commands of a level will get an ID in numeric ascending order starting with
'001'. For a condition the string 'T_' (true) or 'F_' (false) is being added to the
ID. The numeric order of subsequent commands within the according tree (true
or false) is then started with '001' and is being appended to the already
assigned ID.
Conditions within a condition processing will have a numeric ID, too. However,
this ID has only two digits and is prefixed with 'C'. The example below
illustrates the ID assignation using a sample command sequence:

Example 2-114 Sample command sequence

...
<Sequence>
<Wait> => 001
<Duration>1</Duration>
<Text>Wait one second...</Text>
</Wait>
<Condition operator="AND"> => 002
<FileExists name="c:\[Link]" /> => C01
<True>
<Wait> => 002T_001
<Duration>1</Duration>
<Text>Wait one second...</Text>
</Wait>
<Condition operator="AND"> => 002T_002
<FileExists name="c:\boot_.ini" /> => C01
<True>
</True>
<False>
<Wait> => 002T_002F_001
<Duration>1</Duration>
<Text>Wait one second...</Text>
</Wait>
<Wait> => 002T_002F_002
<Duration>1</Duration>
<Text>Wait one second...</Text>
</Wait>
</False>
</Condition>
<Wait> => 002T_003
<Duration>1</Duration>
<Text>Wait one second...</Text>
</Wait>
</True>
<False>
</False>
</Condition>
<Wait> => 003
<Duration>1</Duration>
<Text>Wait one second...</Text>
</Wait>
</Sequence>
...

182 Reference and Using – User Guide Document version: 002

J/Install
3 Sample installation with J/Install

This chapter uses an example to explain how to configure and control a

J/Install installation.
You will find this information in the following sections:
The problem 184

Encoding 185

The Variables section .......................................................................................... 185

The Sequence section ........................................................................................ 185

Document version: 002 Reference and Using – User Guide 183

Sample installation with J/Install
J/Install

The problem
The creation of the file [Link] is determined by specific installation
requirements. If it is required that the latest versions of the operating system
and of Internet Explorer (IE) are available on the system, these components
can be ignored.
The Variables and Sequence sections of the [Link] file are
explained below.
The Variables section The following variables should be defined for the necessary scope of the
PC/E-SmartClient installation:
• CUSTOM
• EPP
• HW
• JBOS
• PCE
The parameters are declared in the variables section.
The Sequence section The individual installation steps are specified in this section.

Required data media

Different data media are required for the installation. For information about
the content of these media see the instructions for the installation of the
respective products.

For the example, the following installation steps should be executed:

1 Requesting of the customizing disk containing the customizations.
2 Optional requesting of the disk containing the EPP firmware.
3 Requesting of the PC/E installation CD for performing the Java Runtime
Environment (JRE) installation.
4 Execution of the JRE installation.
5 Decompression of the firmware (this is available as a self-extracting file on
the data medium).
6 Requesting of the PC/E installation CD for the installation of J/Bos.
7 Execution of the J/Bos installation.
8 Requesting of the PC/E installation CD for the installation of PC/E-
SmartClient.
9 Execution of the PC/E-SmartClient/Base installation.

184 Reference and Using – User Guide Document version: 002

Encoding

J/Install
Encoding

The Variables section

The individual parameters are declared in the Variables section. These
parameters are specified in the section "The main area "Variables"" on page 2-
46. This area is shown in the figure below.

<Variables>
<Variable>
<Name>CUSTOM</Name>
<Value/>
</Variable>
<Variable>
<Name>HW</Name>
<Value/>
</Variable>
<Variable>
<Name>PCE</Name>
<Value/>
</Variable>
<Variable>
<Name>EPP</Name>
<Value/>
</Variable>
<Variable>
<Name>JBOS</Name>
<Value/>
</Variable>
</Variables>

The Sequence section

The command sequence illustrated below is based on the individual steps
described in the section "The Sequence section" on page 3-184.
In the first installation step, the files for the customizing data and for the
hardware are copied from the installation medium to the target system. The
<MultiDisk> element specifies that the user will be asked whether there is
another data medium available.

<GetSource description=“Customizing disk request“>

<Text>Please insert customizing disk</Text>
<TagFile>[Link]</TagFile>
<CopySource>*.*</CopySource>
<CopyDestination>c:\jinstall\custom</CopyDestination>
<MultiDisk>true</MultiDisk>
<Unattend>CUSTOM</Unattend>
</GetSource>
<GetSource description=“Hardware disk request“>
<Text>Please insert hardware disk</Text>
<TagFile>hw_conf.ini</TagFile>
<CopySource>*.*</CopySource>
<CopyDestination>c:\jinstall\hw</CopyDestination>
<Unattend>HW</Unattend>
</GetSource>

The EPP firmware disk is now requested and copied.

<GetSource description="EPP firmware disk request" optional="true" >

<Text>Please insert EPP firmware disk</Text>
<TagFile>[Link]</TagFile>
<CopySource>*.*</CopySource>
<CopyDestination>c:\frm\all</CopyDestination>
<CopyRecursive>true</CopyRecursive>
<CopyType>ALWAYS</CopyType>
<Unattend>EPP</Unattend>
</GetSource>

In the next step the PC/E installation CD is requested and the Java Runtime
Environment is installed.

Document version: 002 Reference and Using – User Guide 185

Sample installation with J/Install
J/Install

<GetSource description="PC/E cd request" >

<Text>Please insert PC/E cd</Text>
<TagFile>diskid</TagFile>
<TagFileContent>PC/E</TagFileContent>
<Unattend>PCE</Unattend>
</GetSource>
<Execute description="JRE installation" >
<Program>{CurrentSource}\install\jre\windows\[Link]</Program>
<Parameter>/s /v"/qn ADDLOCAL=ALL IEXPLORER=1 REBOOT=Suppress
JAVAUPDATE=0 /L c:\jinstall\[Link]"</Parameter>
<SuccessCode>0</SuccessCode>
<LogFileContentToAdd>c:\jinstall\[Link]</LogFileContentToAdd>
</Execute>

The self-extracting archive containing the firmware is then called and saved to
the target system in a separate directory.

<Execute description="Decompress firmware" >

<Program>{CurrentSource}\install\firmware\10.46\[Link]</Program>
<Parameter>-auto</Parameter>
<SuccessCode>0</SuccessCode>
<CopyRoot>{CurrentSource}\install\firmware\10.46</CopyRoot>
</Execute>

The requirements for installing J/Bos have now been met. Installation is
performed in the following steps:

<GetSource description="PC/E cd request" >

<Text>Please insert PC/E cd</Text>
<TagFile>diskid</TagFile>
<TagFileContent>PC/E</TagFileContent>
<Unattend>PCE</Unattend>
</GetSource>
<Execute description="J/Bos installation" >
<Program>{CurrentSource}\install\jbos\12.20_F70_B13\setup\[Link]</Program>
<Parameter>/NOD /NOJRE /B=CUS /H=c:\jinstall\hw /I=c:\jinstall\custom
/P=c:\jbos /A1=c:\frm\all /A2=c:\frm\hw /A3=c:\frm\cur -SMS</Parameter>
<SuccessCode>0</SuccessCode>
<ErrorFile>c:\install\error</ErrorFile>
<LogFileContentToAdd>c:\install\[Link]</LogFileContentToAdd>
</Execute>

All of the requirements for installing the PC/E-SmartClient/Base component

have now been met.

<GetSource description="PC/E cd request" >

<Text>Please insert PC/E cd</Text>
<TagFile>diskid</TagFile>
<TagFileContent>PC/E</TagFileContent>
<Unattend>PCE</Unattend>
</GetSource>
<Execute description="PC/E-SmartClient/Base installation" >
<Program>{CurrentSource}\install\scbase\23.00.000077\windows\console\setup.
exe</Program>
<Parameter>-pi:custom c:\jinstall\custom\[Link] -pi:optional -silent -
options c:\jinstall\custom\[Link]</Parameter>
<UnattendParameter>-pi:custom c:\jinstall\custom\[Link] -pi:optional -
silent -options c:\jinstall\custom\[Link]</UnattendParameter>
<SuccessCode>0</SuccessCode>
<LogFileContentToAdd>{E:PCE_HOME}\log\product_smartclientbase.
log</LogFileContentToAdd>
<ErrorLogFileContentToAdd>{E:TEMP}\product_smartclientbase.
log</ErrorLogFileContentToAdd>
</Execute>

The installation sequence ends with a system restart.

<Reboot>
<Type>ASK</Type>
</Reboot>
...

186 Reference and Using – User Guide Document version: 002

J/Install
4 Installing ProClassic with J/Install

Using J/Install 3.0 and higher ProClassic can be installed with J/Install. In this
chapter you will find information about the following topics:
In this chapter you will find information about the following topics:
Installation media 188

ProClassic CD ..................................................................................................... 188

Registration Key Disk .......................................................................................... 188
Customizing Disk ................................................................................................ 188

The file [Link] 190

Running ProClassic installations 197

Procedure of a ProClassic installation 199

Sequence of a ProClassic start 203

Installing an XFS-ADDON component 204

System informationen ......................................................................................... 206

Updating the Java Runtime Environment 213

Document version: 002 Reference and Using – User Guide 187

Installing ProClassic with J/Install
J/Install

Installation media

ProClassic CD
The structure of a ProClassic CD is illustrated with the figure below:

Figure 4-1 Structure of the ProClassic CD

Registration Key Disk

File Description
REG_KEY.INI Registration key file

Customizing Disk
File Description
[Link] J/Install Customizing file (see "The file [Link]" on page 4-
190)

188 Reference and Using – User Guide Document version: 002

Installation media

J/Install
File Description
[Link] PARAC parameters; optional
[Link] PARAC parameters; optional
[Link] Dialog control; optional
[Link] Operating system configuration; this file is used to overwrite the
default settings of the operating system and user configuration;
optional
JRE\*.exe JRE files, optional
PRE\*.ZIP Update archives; the files will be unpacked relative to drive C:;
POST\*.ZIP optional
END\*.ZIP
PRE\*.REG REG files; optional
POST\*.REG
END\*.REG
PRE\*.INF INF files; optional
POST\*.INF
END\*.INF
PRE\[Link] J/Install files; optional
POST\[Link]
END\[Link]
SRCCORR\*.ZIP SourceCorrection; optional (see "SourceCorrections" on page 2-
157)
*.ISS Response files for ProAgent, etc.; by using these files the settings in
the *.ISS files of the corresponding product directories will be
overwritten; optional

Document version: 002 Reference and Using – User Guide 189

Installing ProClassic with J/Install
J/Install

The file [Link]

To simplify adjustments for projects, the more complex script file
[Link] is being overlain with the customizing file [Link].
The file [Link] is a properties file with the following structure:

Prefix Description
autologon Autologon configuration (processing with setting
’[Link]=true’)
common General settings (see "General settings" on page 4-191)
[Link] Update archives that will be processed right before the J/
Install program sequence is completed
[Link] Update archives, that are called after the installation of the
application
[Link] Update archives, that are called before the installation of the
application
definition Specification of Fallback and Keep information
[Link] Programs that will be run right before the J/Install program
sequence is completed
[Link] Programs, that are called after the installation of the
application finishs
[Link] Programs, that are called prior the installation of the
application starts
nonadmin NonAdmin configuration (processing with setting
’[Link]=true’)
proclassic Specific settings for a ProClassic application installation
To specify ProClassic-specific settings, the format below has
to be used:
proclassic.<artifact-name>.<setting-name>
with:
<artifact-name> - name of ProClassic product or component,
for example PROFLEX4-SDK (produkc), PROFLEX4_BASE
(component), PARACNT (component)
<setting-name> - name of product or component parameter,
for example VERSION, TYPE, USER_ROLE
The parameter VERSION can be used with the two formats
below:
(1) ZZ
(2) [Link] (starting with J/Install, release 6.6/00) with:
ZZ - patch version
X - major version
Y - m inor version
Examples:
proclassic.PROFLEX4_BASE.VERSION = 10
proclassic.PROFLEX4_UI.VERSION = 11.20
product.<Product>.VERSION Version definitions of add-on products; the add-on product is
not being installed if the value NONE is set instead of a
version

190 Reference and Using – User Guide Document version: 002

The file [Link]

J/Install
Prefix Description
[Link] Setting of software versions

General settings Default values are displayed in bold.

Settings name Value Description

[Link] true Autologon configuration
false no Autologon configuration
[Link] any Filename of a boot logo graphics file; the boot
logo is set only if the applied file exists.
[Link] 8, 16, 24, 32 color quality in bits per pixel; for example 8 = 256
colors
Sets the following registry parameter:
[HKLM\SOFTWARE\Wincor Nixdorf]
ApplicationScreenColors
[Link] LAN, MODEM Connection mode
In ProFlex4 installations: Sets the following
registry parameter:
[HKLM\SOFTWARE\Wincor Nixdorf\ProInstall]
CONNECTION
[Link] true Request for a Hardware disk
false No request for a Hardware disk
[Link] true Request for a Registration Key disk
false No request for a Registration Key disk
[Link] true Request for an Update disk
false No request for an Update disk
[Link] any Domain
[Link] true Support of fallback
false No support of fallback
[Link] any Directory to backup Fallback information
Default: %JINSTALL_ROOT%\FALLBACK
[Link] true Reboot after restoring of Fallback information
false No reboot after restoring of Fallback information
[Link] true Keep support
false no Keep support
[Link] any Directory to backup Keep information
Default: %JINSTALL_ROOT%\KEEP
[Link] integer Required physical memory in MB (default: 250)

Document version: 002 Reference and Using – User Guide 191

Installing ProClassic with J/Install
J/Install

Settings name Value Description

[Link] Primary Application is being displayed on main monitor;
sets the following registry parameter:
[HKLM\SOFTWARE\Wincor Nixdorf]
ApplicationMonitor
Secondary Application is being dispalyed on second
monitor
[Link] true NonAdmin configuration
false no NonAdmin configuration
[Link] true PARAC call using parameter -Ac
false PARAC call using parameter -An
[Link] true PARAC calls in file [Link]
false no PARAC calls in file [Link]
[Link] any Encrypted password surrounded by double
quotation marks. Quoting of password value is
mandatory! The string entered in double
quotation marks must not be empty.
Use [Link] tool (folder \Tools\PCEncr\ on
CD) to encrypt your password.
[Link] true This parameter indicates whether the password
crypted set with [Link] is treated as
false encrypted (true) or not (false).
Setting this parameter to ’false’ is not compliant
with the PCI PA-DSS specification. Don't set it to
’false’ if you require PCI PA-DSS compliance.
Instead, leave it on the default value (true) as
shipped with the product.
[Link] any Filename of a Readme file to be displayed; the
ReadMe file is displayed only if the applied file
exists.
[Link] AUTO Automatic reboot
ASK Reboot dialog
CAUTION: During an unattended installation
ASK is being treated similar to NO.
COMMIT Reboot confirmation
CAUTION: During an unattended installation
COMMIT is being treated similar to YES.
NO No reboot
YES Reboot

192 Reference and Using – User Guide Document version: 002

The file [Link]

J/Install
Settings name Value Description
[Link] <width>x<height> Screen resolution;
Example: 1024x768
Default: screen resolution during installation
The supported resolutions depend on the
installed application.
Sets the following registry parameter:
[HKLM\SOFTWARE\Wincor Nixdorf]
ApplicationScreenResolution
For ProFlex4 applications:
Registry parameter
ApplicationScreenResolution is read by the
application's [Link] script to provide a
correct resolution for the [Link] call inside
the script.
[Link] true Automatic start of application using entry
HKLM\SOFTWARE\Microsoft\Windows\Current
Version\Run
false No automatic start of application
[Link] true Terminal installation
Sets the following registry parameter:
[HKLM\SOFTWARE\Wincor Nixdorf]
ApplicationRuntime
false Developer installation
[Link] true If set to 'true', the global 'shell' parameter in
Windows Registry is changed:
false - Removed: [Link]
- Inserted: Command starting [Link] script.
Available with ProFlex4 product installations,
version R4.2/00 or later.
[Link] true Update
false Initial installation
[Link] any Application user
Sets the following registry parameter:
[HKLM\SOFTWARE\Wincor Nixdorf]
ApplicationStartUser
[Link] true Operating system configuration
false No operating system configuration
[Link] WN, NCR, Vendor name
DIEBOLD, KEBA,
OLIVETTI,
DELARUE,
FUJITSU,
NAUTILUS

Document version: 002 Reference and Using – User Guide 193

Installing ProClassic with J/Install
J/Install

JRE settings
Parameters Description
[Link] Version of the JRE to be installed; the version must be
submitted using the pattern <Family>u<Update>, for
example 7u9; the keyword NONE suppresses
installation of an JRE

If the value of a parameter read from file [Link] contains leading/

trailing blanks, they will be truncated.

Example 4-1 Example (<> are used here as delimiters to visualize the issue)
When parsing the line
<[Link] = my test user > (one leading and two trailing blanks
in value)
J/Install processes the following:
<[Link] =my test user>
Parameter value is <my test user>.

Parameter values in quotes

Parameter values cannot be enclosed in quotes because J/Install doesn't
support this method!
Example:
For the parameter <[Link] = "my test user"> its value is <"my
test user">. Quotes would belong to the value.

194 Reference and Using – User Guide Document version: 002

The file [Link]

J/Install
Example 4-2 Example for file [Link]
#
[Link] = WN
[Link] = LAN
[Link] = Wincor
[Link] = 500
[Link] = Primary
[Link] = ASK
[Link] = 48AF8F955A456A8215AE3CF21ADA7AF0
[Link] = {E:COMPUTERNAME}
[Link] = true
[Link] = false
[Link] = true
[Link] = true
[Link] = true
[Link] = true
[Link] = true
[Link] = c:\install\custom\[Link]
[Link] = c:\install\custom\[Link]
[Link] = true
[Link] = c:\save\fallback
[Link] = true
[Link] = true
[Link] = c:\save\keep
[Link] = 1024x768
[Link] = 32
#
[Link] = 10.10
[Link] = 7u9
[Link] = 10.60
[Link] = 39.20
#
[Link]/[Link] = 00
proclassic.XFS_ADDON.VERSION = 00
proclassic.XFS_ADDON.VENDORNAME = {V:[Link]}
proclassic.XFS_ADDON.SYN = YES
proclassic.XFS_ADDON.SMI = 30
[Link] = 35
[Link]/[Link] = 00
[Link] = 20
[Link] = 11
[Link] = CRSNDC
[Link]/[Link] = 80
[Link]/[Link] = CRSNDC
[Link]/EMV-D/[Link] = 00
[Link]/EMV-D/[Link] = ADDON
[Link]/[Link] = 01
[Link] = 37
#
# [Link] =
# [Link] =
# [Link] =
# [Link] =
#
# [Link] =
# [Link] =
# [Link] =
# [Link] =
#
# [Link] =
# [Link] =
# [Link] =
# [Link] =
#
# [Link] =
# [Link] =
# [Link] =
# [Link] =
#
# [Link] =
# [Link] =
# [Link] =
# [Link] =
#
# [Link] =
# [Link] =
# [Link] =
# [Link] =

Document version: 002 Reference and Using – User Guide 195

Installing ProClassic with J/Install
J/Install

#
[Link] = WNUsers0
[Link] = {V:[Link]}
[Link] = {V:[Link]}
[Link] = 0010
#
[Link] = {V:[Link]}
[Link] = {V:[Link]}
[Link] = {V:[Link]}
[Link] = true
#
[Link] = INI
[Link] = c:\[Link]
[Link] = [boot loader]timeout
[Link] = DIR
[Link] = c:\package
[Link] = true
[Link] = REG
[Link] = HKLM
[Link] = [SOFTWARE\Wincor Nixdorf\Custom]
[Link] = DIR
[Link] = c:\custom
[Link] = true
[Link] = c:\install\custom\[Link]
#
[Link] = [Link]/NDC-EMULATION
[Link] = 3.0/00

If for entries with prefix 'common' for a <Value> the string {Ask} or
{Ask:<Default>} is set, the value is going to be requested during runtime.
Whereas for the value {Ask:<Default>} the string <Default> is preset in the
input field, the input field is empty if using the value {Ask}.
Example

[Link] = {Ask:WN}
[Link] = {Ask}

196 Reference and Using – User Guide Document version: 002

Running ProClassic installations

J/Install
Running ProClassic installations
ProClassis can be installed using several ways:
• dialog-guided installation (with user interaction)
• unattended installation, with ProSetup
• unattended installation, without ProSetup

Installing dialog-guided
• On the ProClassic CD, go to the directory
\setup\<Produkt>\R<Version> and run the file [Link].
By using the information stored in file [Link] all required data media
will be requested:

file={J:[Link]}\[Link]
#unattend=true
#test=true
#[Link]={J:[Link]}\custom
#variable.CUSTOM_COPY=false
#[Link]={J:[Link]}\reg
#[Link]={J:[Link]}\update
#[Link]={J:[Link]}\hw
#[Link]=b:\

Installing unattended with ProSetup

In order to run an unattended installation with ProSetup, the customizing data
medium must provide a file [Link] with following content:

file={J:[Link]}/[Link]
unattend=true
[Link]={E:PROSETUP_HW}
[Link]={E:PROSETUP_CUSTOM}
#variable.CUSTOM_COPY=false
[Link]={E:PROSETUP_REG}
[Link]={E:PROSETUP_UPDATE}
[Link]={E:PROSETUP_PROCLASSIC}

The corresponding call in file [Link] is to set as follows:

[Link] = %PROSETUP_PROCLASSIC%/setup/<Produkt>/R<Version>/
[Link]
[Link].instcmd_params = -par:prosetup

Installing unattended without ProSetup

In order to run an unattended installation without ProSetup, a file [Link]
is to be created that provides references to the directories that contain the
corresponding data media content:

file={J:[Link]}/[Link]
unattend=true
[Link]=c:\disks\hw
[Link]=c:\disks\custom
#variable.CUSTOM_COPY=false
[Link]=c:\disks\reg
[Link]=c:\disks\update
[Link]=c:\disks\proclassic

Before starting JLaunch, an environment variable PROJECT_CUSTOM must

be specified. This variable refers to the folder where the file [Link] is
stored.
Then JLaunch is called as following:

Document version: 002 Reference and Using – User Guide 197

Installing ProClassic with J/Install
J/Install

<ProClassic CD>\setup\<Produkt>\R<Version>\[Link] -par:custom

Suppressing copying of customizing files

When using the entry variable.CUSTOM_COPY=false in the PAR file, the
copying of the customizing (variable CUSTOM) into folder
c:\install\custom. This should be used only if the customizing is
stored in a folder for which access is granted during the entire installation
procedure.

Windows 7
If Windows 7 is running with activated UAC, an installation from a drive
mounted by subst or net use is not possible since this mounted drive is not
available for users with expanded installation rights.

198 Reference and Using – User Guide Document version: 002

Procedure of a ProClassic installation

J/Install
Procedure of a ProClassic installation
Action Installation Update
Deleting directory C:\INSTALL\CUSTOM X X
Deleting directory C:\INSTALL\REG X X
Deleting directory C:\INSTALL\HW X X
Requesting a customizing disc and copying it to X X
C:\INSTALL\CUSTOM
Processing an existing dialog control file X X
C:\INSTALL\CUSTOM\[Link]
Reading of settings with prefix 'common' from the X X
customizing file [Link]
Reading of settings with prefix 'product' from the X X
customizing file [Link]
Requesting one or more Registration Key discs and X X
copying them to C:\INSTALL\REG if customizing setting is
'[Link]=true'
Requesting a Hardware disc and copying them to X X
C:\INSTALL\HW if customizing setting is
'[Link]=true'
Checking system requirements (operating system/physical X X
memory)
Checking platform requirements (in case of Wincor Nixdorf X X
systems)
Requesting the ProClassic CD X X
Checking registration keys and components on the X X
ProClassic CD
Specifying the KEEP and FALLBACK information - X
Creating the FALLBACK information - X
Creating the KEEP information - X
Saving all PARAC parameters of file C:\PARAC\[Link] - X
Saving all PARAC parameters of file
C:\INSTALL\CUSTOM\[Link], if no file
[Link] exists
Saving all PARAC parameters of file - X
C:\PARAC\[Link], if no file [Link] or
[Link] exists
Saving all dynamic PARAC parameters, if no files - X
[Link] or [Link] or [Link] exist
Saving all dynamic PARAC parameters, if no files - X
[Link] or [Link] or [Link] exist
Installing JREs required for ProClassic components X X

Document version: 002 Reference and Using – User Guide 199

Installing ProClassic with J/Install
J/Install

Action Installation Update

Setting connection mode ’[Link]’ in Registry X X
([HKLM\SOFTWARE\Wincor
Nixdorf\ProInstall]CONNECTION)
Setting application user ’[Link]’ in Registry X X
([HKLM\SOFTWARE\Wincor
Nixdorf]ApplicationStartUser). The executable
[Link] in file [Link] is checking this entry
against the environment variable USERNAME. The
domain is not considered with this check.
Setting of monitor '[Link]' in X X
([HKLM\SOFTWARE\WincorNixdorf]ApplicationMonitor)
Setting screen resolution '[Link]' in Registry X X
([HKLM\SOFTWARE\Wincor
Nixdorf]ApplicationScreenResolution)
Applying color quality setting '[Link]' in Registry X X
([HKLM\SOFTWARE\Wincor
Nixdorf]ApplicationScreenColors)
Applying runtime setting '[Link]' in Registry X X
([HKLM\SOFTWARE\Wincor Nixdorf]ApplicationRuntime)
Unpacking the update archives specified with prefix X X
'[Link]’ in file [Link].
Unpacking ZIP files in alphabetical order from directory X X
C:\INSTALL\CUSTOM\PRE to directory C:\.
Importing REG files in alphabetical order from directory X X
C:\INSTALL\CUSTOM\PRE to directory C:\.
Unpacking INF files in alphabetical order from directory X X
C:\INSTALL\CUSTOM\PRE
Running the programs that are specified with prefix X X
'[Link]' in file [Link].
Running the J/Install file [Link] of directory X X
C:\INSTALL\CUSTOM\PRE.
Installing TLS-W32 on Multivendor terminals X X
Installing the ProClassic application X X
Installing ProAgent X X
Unpacking the update archives specified with prefix X X
'[Link]’ in file [Link].
Unpacking ZIP files in alphabetical order from directory X X
C:\INSTALL\CUSTOM\POST to directory C:\.
Unpacking REG files in alphabetical order from directory X X
C:\INSTALL\CUSTOM\POST
Unpacking INF files in alphabetical order from directory X X
C:\INSTALL\CUSTOM\POST

200 Reference and Using – User Guide Document version: 002

Procedure of a ProClassic installation

J/Install
Action Installation Update
Running the programs that are specified in [Link] X X
with prefix '[Link]'
Running the J/Install file [Link] of directory X X
C:\INSTALL\CUSTOM\POST.
Importing REG files from directory C:\PARAC\REG X X
Importing INF files from directory C:\PARAC\REG X X
Processing file C:\PARAC\[Link], that has been X X
created during the ProClassic installation, using PARAC
Restoring the KEEP information - X
Processing file C:\INSTALL\CUSTOM\[Link] X X
using PARAC
Processing file C:\INSTALL\CUSTOM\[Link] X X
using PARAC
Configuring a boot logo, if the customizing entry X X
'[Link]' and the specified file exist
Configuring the operating system if the customizing setting X X
is '[Link]=true'
Configuring the Autologon mode if the customizing setting X X
is '[Link]=true'
Configuring the NonAdmin mode if the customizing setting X X
is '[Link]=true'
Copying a template file [Link] to X X
C:\PROTOPAS\BIN
Setting RUN entry in Registry X X
Unpacking the update archives specified with prefix X X
'[Link]’ in file [Link].
Unpacking ZIP files in alphabetical order from directory X X
C:\INSTALL\CUSTOM\END to directory C:\.
Unpacking REG files in alphabetical order from directory X X
C:\INSTALL\CUSTOM\END
Unpacking INF files in alphabetical order from directory X X
C:\INSTALL\CUSTOM\END
Running the programs that are specified in [Link] X X
using prefix '[Link]'
Running the J/Install file [Link] of directory X X
C:\INSTALL\CUSTOM\END.
Writing the version information set with the customizing X X
option prefix '[Link]'
Displaying a ReadMe file, if the customizing entry X X
'[Link]' and the specified file exist

Document version: 002 Reference and Using – User Guide 201

Installing ProClassic with J/Install
J/Install

Action Installation Update

Displaying a warning file X X
(%JINSTALL_ROOT%\[Link]) if this file exists
Performing a reboot using the options specified with X X
'[Link]'

202 Reference and Using – User Guide Document version: 002

Sequence of a ProClassic start

J/Install
Sequence of a ProClassic start
The ProClassic application is started automatically via the batch file
%PROTOPAS_ROOT%\BIN\[Link] that is referred with the Registry
entry [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]ProCash.

Step Action
1 Checking for application user ’[Link]’
2 Displaying of image %PROTOPAS_ROOT%\BIN\[Link] in foreground
3 Applying the screen resolution of setting ’[Link]’
4 Applying the color quality as set with ’[Link]’
5 One-time configuration of application user and reboot
6 Calling of [Link]
7 Calling batch file %PROTOPAS_ROOT%\CONF\[Link]
8 Calling batch file %PROTOPAS_ROOT%\BIN\[Link] for project-
specific actions
9 Calling batch file C:\PARAC\[Link] for PARAC actions
10 Calling batch file %PROTOPAS_ROOT%\BIN\[Link] in order to
start the ProClassic application

Document version: 002 Reference and Using – User Guide 203

Installing ProClassic with J/Install
J/Install

Installing an XFS-ADDON component

An installation on a Multivendor system or a Wincor Nixdorf machine with
ProBase/C requires to install the XFS-ADDON component that is configured
with parameter proclassic.XFS_ADDON.<keyword> in file [Link].
This component collects information on
• the hardware equipment
• physical and logical XFS services and CCBase
• the mappings between hardware and logical services
These information will be stored in the Registry. A description of the stored
information is provided below:
Default values are displayed in bold.

Keyword Values Meaning

DETECTION_IGNORE <list> List of device names with format
<device name>[,<device name,...] that
shall be ignored during device
detection.
DETECTION_PREFER <list> List of preferred device names with
format <device name>[,<device
name,...]
Can be used in conjunction with
PREFERRED_LOGICALNAMES. If
both keywords are used, the
corresponding values will be merged.
FUNCKEYS <list> Usage of softkey with format
<specification FDK1> <specification
FDK2> … <specification FDK8>
FUNCKEYS_POS <list> Position of softkey with format <X
position of FDK1>,<Y position of
FDK1>:…:<X position of FDK8>,<Y
position of FDK8>
HW_DETECTION YES Multivendor hardware detection
NO no Multivendor hardware detection; an
installation without hardware detection
is possible if the registry key
HKEY_LOCAL_MACHINE\SOFTWAR
E\Wincor Nixdorf\MvDetect exists as a
result of [Link].
LOGICALNAMES <LOGICAL_OPE Replacement list that is used with
N_NAME_REPL Multivendor installations
ACEMENT>

204 Reference and Using – User Guide Document version: 002

Installing an XFS-ADDON component

J/Install
Keyword Values Meaning
PREFERRED_LOGICALNAMES <list> List of preferred device names with
format <device name>[,<device
name,...]
Can be used in conjunction with
DETECTION_PREFER. If both
keywords are used, the corresponding
values will be merged.
SMI NO Installation without SMI service
20 Installation with SMI 2.0
30 Installation with SMI 3.0
SYN NO Installation without SYN service
YES Installation with SYN service
SYSTEMNAME <Job name> Multivendor system name, optional

TOUCH1 NO no Touch integrated into system

YES Touch integrated into system
TTU NO TTU devices are not evaluated
YES TTU devices are evaluated
VENDORNAME WN, NCR, Vendor name
DIEBOLD, KEBA,
OLIVETTI,
DELARUE,
FUJITSU,
NAUTILUS
VDM NO VDM devices are not evaluated
YES VDM devices will be evaluated
XFS CENXFS CEN/XFS installation
JXFS J/XFS installation

[Link] setting is ignored for NCR systems since corresponding hardware is being detected automatically.

Example 4-3 Extract from a Customizing file:

proclassic.XFS_ADDON.VENDORNAME = WN
proclassic.XFS_ADDON.VERSION = 00a
proclassic.XFS_ADDON.TOUCH = YES
proclassic.XFS_ADDON.TTU = NO
proclassic.XFS_ADDON.VDM = YES
proclassic.XFS_ADDON.SYN = YES
proclassic.XFS_ADDON.SMI = 30
proclassic.XFS_ADDON.LOGICALNAMES =
CDM30>DBD_AdvFuncDisp,IDC30>DBD_MotoCardRdr,PIN30>DBD_EPP4,SIU30>DBD_TerminalIO
proclassic.XFS_ADDON.PREFERRED_LOGICALNAMES = DBD_AdvFuncDisp,DBD_MotoCardRdr
proclassic.XFS_ADDON.FUNCKEYS = 0x0010 0x0020 0x0040 0x0080 0x0008 0x0004 0x0002
0x0001
proclassic.XFS_ADDON.FUNCKEYS_POS =
0,37:0,55:0,72:0,90:100,37:100,55:100,72:100,90

Document version: 002 Reference and Using – User Guide 205

Installing ProClassic with J/Install
J/Install

System informationen
To remain compatible, with previous installations with ProInstall the information
below are provided:
• Hardware equipment
• Physical and logical XFS services, and CCBase information
• Mappings between hardware and logical services

Hardware equipment
The available hardware configuration is provided in the registry under the
branch:

HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProInstall\Hardware

Entry Values Description

AlphaKeyboard yes, no Alphanumeric keyboard is present
AntiSkimming yes, no Anti Skimming module available
AntiSkimmingInterface SEL, V24, USB, Anti Skimming interface
CP1, CSE
BarcodeReader yes, no Barcode reader available
BarcodeReaderInterface V24, USB Barcode reader interface
BarcodeReaderType BCR, BCR_1D, Barcode reader type
BCR_2D, IS4920
Camera yes, no Camera available
CameraInterface V24, USB Camera interface
CameraType CAM Camera type
CardReader yes, no Card reader available
CardReaderForm MOTOR, SWIPE, Model of card reader
DIP,
CONTACTLESS,
LATCHEDDIP,
PERMANENT
CardReaderInterface V24, USB Card reader interface
CardReaderPosition UP, DOWN, Card reader track position
RIGHT, LEFT
CardReaderType ID14, ID15, ID18, Card reader type
ID24, SWIPE,
CHD_ICM300,
CHD_ICM330,
CHD_V2X,
CHD_V2XU,
CHD_V2CU,
CHD_MCT,
CHD_ICT3S5

206 Reference and Using – User Guide Document version: 002

Installing an XFS-ADDON component

J/Install
Entry Values Description
CardReaderTypeOrg ID_4060, Card reader CSC-W32 identification
ID_4058,
HYBRID,
MANUAL,
SWIPE, ICM300,
ICM330, V2X,
V2XU, V2A,
V2CU, MCT,
ICT3S5
CashCycleManagementProcess DISABLED, XFS customizing parameter
ENHANCED, [Link]
SIMPLE
CashIn yes, no Cash recycler available
CashInP6Data SIGNATURE, Recognition method either signature or
NUMBER serial number
CashInCompareDLL <File name> List of Compare DLLs
CashInInterface V24, USB Cash recycler interface
CashInType CRS, CCDM, Cash-in type
CCDM2, RM2,
RM3, WBA
CashOut yes, no Cash-out module available
CashOutInterface V24, USB Cash-out module interface
CashOutType Vx, NG, CRS, Cash-out module type
RM2, RM3, SCP,
CDMV5, CDMV7
ChequeDeposit yes,no Cheque deposit available
ChequeDepositInterface V24, USB Cheque deposit interface
ChequeDepositType CCDM Cheque deposit type
CoinIn yes, no Coin-in module available
CoinInInterface V24, USB Coin-in module interface
CoinInType REIS, Coin-in module type
NOVOTECH
CoinInTypeOrg R, N Coin-in module CSC-W32 identification
CoinOut yes, no Coin-out module available
CoinOutInterface V24, USB Coin-out module interface
CoinOutType Reis, Azkoyen, Coin-out type
WN, Hess
CoinOutTypeOrg R, A, C, T, O Coin-out module CSC-W32
identification
ContactlessCardReader yes, no Contactless card reader available
ContactlessCardReaderInterface V24, USB Contactless card reader interface

Document version: 002 Reference and Using – User Guide 207

Installing ProClassic with J/Install
J/Install

Entry Values Description

ContactlessCardReaderType ACG Contactless card reader type
Display yes, no Display available
DisplayType STANDARD, OPL Display type
DocumentPrinter yes, no Document printer available
DocumentPrinterGDI yes, no Document printer installed as GDI
printer
DocumentPrinterInterface LPT, V24, USB Document printer interface
DocumentPrinterLogunit BELEG1 - Document printer logical unit name
BELEG16
DocumentPrinterName ND75, ND75S, Document printer description
ND94, ND97,
NP01, TH97,
TP20
DocumentPrinterWindowsName Wincor Nixdorf Document printer windows printer name
TH97/G, Wincor
Nixdorf TP01,
Wincor Nixdorf
TP20
EnvelopeDeposit yes, no Envelope deposit unit available
EnvelopeDepositInterface V24, USB Envelope deposit unit interface
EnvelopeDepositType DPS, EDU Envelope deposit unit type
JournalPrinter yes, no Document printer available
JournalPrinterGDI yes, no Document printer installed as GDI
printer
JournalPrinterInterface LPT, V24, USB Document printer interface
JournalPrinterLogunit JOURNAL1 - Document printer logical unit name
JOURNAL16
JournalPrinterName ND71, ND98, Document printer description
TH30, TP06,
NP06
JournalPrinterWindowsName Wincor Nixdorf Document printer Windows printer
TP06 name
OperatorPanel yes, no Operator panel available
OperatorPanelEmuMode WIN, NO, YES Customizing parameter
OperatorPanelInterface V24, USB Operator panel interface
OperatorPanelPrimary yes, no Customizing parameter
OperatorPanelSecondScreen yes, no Operator panel works as 2nd screen or
as operator panel

208 Reference and Using – User Guide Document version: 002

Installing an XFS-ADDON component

J/Install
Entry Values Description
OperatorPanelType OP01, OP02, Operator panel type
V24_GRAPHIC_
OPL,
USB_GRAPHIC_
OPL,
USB_GRAPHICA
L_OPL,
PROPRINT_LCD
OperatorPanelTypeOrg OP01, OP02, Operator panel CSC-W32 identification
OP03, OP04,
OP05,
PROPRINT_LCD
PassbookPrinter yes, no Passbook printer available
PassbookPrinterGDI yes, no Passbook printer installed as GDI
printer
PassbookPrinterInterface LPT, V24, USB Passbook printer interface
PassbookPrinterLogunit PASSBOOK1 - Passbook printer logical unit name
PASSBOOK16
PassbookPrinterName ND05, HPEM, Passbook printer description
PUH
PassbookPrinterWindowsName Passbook printer Windows printer name
PINpad yes, no PINpad / EPP available
PINpadInterface V24, USB PINpad / EPP interface
PINpadType PINPAD, PINpad / EPP type
EPP_V4,
EPP_V4+,
EPP_V5,
EPP_V6,
PINPAD_SEL,
PINPAD_CIT
PrintingCassette yes, no Printing cassette available
PrintingCassetteGDI yes, no Printing cassette installed as GDI
printer
PrintingCassetteHeight 1,2 Printing cassette height
PrintingCassetteInterface LPT, USB Printing cassette interface
PrintingCassetteName TH50, TH60 Printing cassette description
PrintingCassetteWindowsName Printing cassette Windows name
ReceiptPrinter yes, no Receipt printer available
ReceiptPrinterGDI yes, no Receipt printer installed as GDI printer
ReceiptPrinterInterface LPT, V24, USB Receipt printer interface
ReceiptPrinterLogunit BON1 - BON16 Receipt printer logical unit name

Document version: 002 Reference and Using – User Guide 209

Installing ProClassic with J/Install
J/Install

Entry Values Description

ReceiptPrinterName ND74, ND79, Receipt printer description
ND99, ND9A,
ND9C, NP9D,
ND9E, ND9G,
TP07, NP07,
TP12, TH21,
TH22, TH23
ReceiptPrinterWindowsName Wincor Nixdorf Receipt printer Windows printer name
TP07, Wincor
Nixdorf TP12,
Wincor Nixdorf
ND9G, WN TH21,
WN TH22, WN
TH23
Scanner yes, no Scanner available
ScannerInterface LPT, V24, USB Scanner interface
ScannerLogunit BELEG1 - Scanner logical unit name
BELEG16
ScannerName ND05, CM3K, Scanner description
TSC, S500,
RS89X, BSC
ServiceSide FRONT, REAR System service side
SpecialElectronics yes, no Special electronics available
SpecialElectronicsInterface ECP, V24, Special electronics interface
COMM, USB,
SDS
SpecialElectronicsType SE3, SE4, SE5, Special electronics type
SDS
SystemName <Name> System name
Touch yes, no Touchscreen available
TouchInterface V24, USB Touchscreen interface
TouchType Touchscreen type
UPS yes, no Power supply available
UPSInterface V24, USB, SEL UPS (Uninterruptible power supply)
interface
UPSType UPS, SEL UPS (Uninterruptible power supply)
type
VendorName WN, NCR, Vendor name
DIEBOLD, KEBA,
OLIVETTI,
DELARUE,
FUJITSU,
NVISION
NAUTILUS

210 Reference and Using – User Guide Document version: 002

Installing an XFS-ADDON component

J/Install
It is not possible to assume that all the entries exist For example only the
highlighted information are available. For this reason the entries should be
accessed in the following way:
PCCfgReg /r <Key> <Name> <Default>

Example 4-4 Accessing system information

PcCfgReg /r "HKEY_LOCAL_MACHINE\SOFTWARE\Wincor ~
Nixdorf\ProInstall\Hardware" Camera no

Physical and logical XFS services, and CCBase information

The physical and logical XFS services that are available, and the relevant
CCBase information are provided in the registry under the branch:

HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProInstall\Wosassp

Entry Description
Services List of all physical services separated by blanks
Service#<x> Individual physical service
LogServices List of all logical services separated by blanks
LogService#<x> Individual logical service
VendorName Vendor name
CCBase Program call for the PARAC parameter [START_APPLICATION]
CCBASE_SET
CCBaseAddOn Call parameter for the PARAC parameter [START_APPLICATION]
CCBASE_SET
CCBaseCtrl Program call for the PARAC parameter [START_APPLICATION]
CCBASE_CONTROL
CCBaseCtrlAddOn Call parameter for the PARAC parameter [START_APPLICATION]
CCBASE_CONTROL
LOGICAL_OPEN_NAME Mapping of the logical service names
_REPLACEMENT

Example 4-5 example

VendorName = WN
CCBase = C:\WOSASSP\BIN\[Link]"
CCBaseAddOn = ,4,1,0,,,/[Link] -e SYN SMI SIU OPP SSI EPP ATM PRD PRR PRJ
CCBaseCtrl = C:\\WOSASSP\\BIN\\[Link]
CCBaseCtrlAddOn = ,4,1,8
LOGICAL_OPEN_NAME_REPLACEMENT =
Services = SYN SMI SIU OPP SSI EPP ATM PRD PRR PRJ
Service#1 = SYN
Service#2 = SMI
Service#3 = SIU
Service#4 = OPP
...
LogServices = SYN SMI SIU OPP SSI EPP ATM PRD PRR PRJ
LogService#1 = SYN
LogService#2 = SMI
LogService#3 = SIU
LogService#4 = OPP
...

Mappings between hardware and logical services

A mapping between hardware and logical service is listed under the branch:

Document version: 002 Reference and Using – User Guide 211

Installing ProClassic with J/Install
J/Install

HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProInstall\Wosassp

Entry Description
HW_<Hardware> <logical service>

Example 4-6 Example of assigning hardware to logical services

...
"HW_CashOut"="ATM"
"HW_JournalPrinter"="PRJ"
"HW_ReceiptPrinter"="PRR"
"HW_OperatorPanel"="OPP"
"HW_SpecialElectronics"="SIU"
"HW_CardReader"="SSI"
"HW_PINpad"="EPP"
...

Softkeys
The allocation and position of softkeys are provided in the Windows registry
using the following registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProInstall\Wosassp

Entry Description
FuncKeys Usage of softkey with format <specification FDK1> <specification FDK2>
… <specification FDK8>
FuncKeysPos Position of softkey with format <X position of FDK1>,<Y position of
FDK1>:…:<X position of FDK8>,<Y position of FDK8>

Example 4-7 Example for softkeys

...
FuncKeys = 0x0001 0x0002 0x0004 0x0008 0x0010 0x0020 0x0040 0x0080
FuncKeysPos = 100,50:100,64:100,78:100,93:0,93:0,78:0,64:0,50
...

212 Reference and Using – User Guide Document version: 002

Updating the Java Runtime Environment

J/Install
Updating the Java Runtime Environment
JreUpdate is a command line tool that can be used to install a Java Runtime
Environment. The executable file [Link] is located in folder
%JINSTALL_ROOT%\BIN. This tool is updating all references of the updated
environment automatically. As an option, this can be carried out also for
ProBase/C and J/Install.
Call parameters /f[older] "<directory>"
Specification of a folder where the JRE setup file with the filename in
notation jre-<version>-windows-<type>.exe is located.
/v[ersion] <version>
Specification of the JRE release that is to be installed or used in notation
<family>u<update>.
With a patch-in-place installation a JRE release is being installed only if
no or a previous JRE release of the same family is already installed.
With a static installation the JRE is being installed if neither a
corresponding family release nor the same static version has been
already installed.
/s[tatic] 0|1
Specification of installation type (optional)
0 - patch-in-place installation (one folder for each family) (default)
1 - static installation (different folder for each release)
/t[ype] i586|x64
Specification of installation type (optional)
i586 - 32 bit (default)
x64 - 64 bit
/j[install] 0|1
Specification of the JRE to be used by J/Install (optional)
0 - no change (default)
1 - change
/p[robase] 0|1
Specification of JRE to be used by ProBase (optional)
0 - no change (default)
1 - change
/r[eboot] 0|1
Specification if a reboot has to be carried out after update (optional)
0 - no reboot (default)
1 - reboot

Example 4-8 Sample call

[Link] /folder "c:\jre" /version 7u9 /static 1 /jinstall 1 /probase 1

Document version: 002 Reference and Using – User Guide 213

Installing ProClassic with J/Install
J/Install

Return values
Return value Meaning
0 Successful calling and processing
1 Invalid call parameter
2 JRE setup (jre-<version>-windows-<type>.exe) does not exist
3 Failed JRE installation
4 Error while copying the J/Install JRE
5 File %PCE_HOME%\bin\[Link] does not exist
6 Error while writing file %PCE_HOME%\bin\[Link]
7 Error while writing file %PCE_HOME%\bin\[Link]

Administrator rights required

Since most system or software changes require administrative rights,
JreUpdate should be called by a user who owns already administrative
rights.
If the current user does not have sufficient rights, JreUpdate can be
started with an administrator identity using PCRunAs (siehe "Running
programs under a different user" on page 1-26).

Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction

Policy Files
If the JCE of the used JRE shall support unlimited key lengths, the content
of file UnlimitedJCEPolicyJDK<familie>.zip has to be unpacked to
folder <folder>\UnlimitedJCEPolicyJDK<familie> .

214 Reference and Using – User Guide Document version: 002

Index

J/Install
Index Symbols optional 2-119
{CurrentSource}, placeholder 2-120 attributes, J/Install commands 2-53, 2-55, 2-56, 2-
*.properties, J/Install 1-16, 1-20 86, 2-91, 2-110, 2-121, 2-122, 2-123, 2-133, 2-135, 2-
%JINSTALL_JAVAHOME% 1-9 136, 2-137, 2-140, 2-142, 2-145, 2-147, 2-159, 2-160, 2-
%JINSTALL_ROOT% 1-9 162, 2-163, 2-164, 2-165, 2-166, 2-168, 2-169, 2-170
Autologon, set for Windows 2-83
A automatic installation 1-2–1-7
addressing
ini files 2-174 B
PARAC files 2-174 Boot logo, changing 2-147
PC/E files 2-174
properties 2-177 C
registry data 2-178 call, J/Install 1-10
XML files 2-179 cecking conditions
addressing rules 2-177 ChecksumCheck 2-60
administration rights, checking of 2-76 DateTimeCheck 2-61
AskUser, parameters 2-53 DriveCheck 2-62
Attribute FileExists 2-63
description 2-109 IsFalse 2-64
ignoreerror 2-109 IsTrue 2-65
attribute, KeepDefine file TokenExists 2-74
name 2-97 UserIsAdmin 2-76
recursive 2-97 ValueCheck 2-77
attribute, KeepValue ValueExists 2-79
file 2-98 VariableExists 2-81
merge 2-98 checking conditions
path 2-98 IsValidPassword 2-66
type 2-98 MemoryCheck 2-68
attributes RegistryKeyExists 2-71
description 2-53, 2-55, 2-56, 2-58, 2-83, 2-84, 2- RestartCheck 2-72
86, 2-88, 2-89, 2-90, 2-91, 2-94, 2-101, 2- StringCheck 2-73
102, 2-103, 2-110, 2-113, 2-114, 2-117, 2- TextFileCheck 2-73
119, 2-121, 2-122, 2-123, 2-125, 2-126, 2- checking values see ValueCheck, checking condi-
128, 2-129, 2-132, 2-133, 2-135, 2-136, 2- tions 2-77
137, 2-140, 2-142, 2-145, 2-147, 2-148, 2- checksum checking for conditional execution of
159, 2-160, 2-162, 2-163, 2-164, 2-165, 2- commands 2-60
166, 2-168, 2-169, 2-170 ChecksumCheck, checking conditions 2-60
fallback 2-56, 2-86, 2-88, 2-90, 2-91, 2-101, 2-119, command definition, extern 2-114
2-137, 2-142, 2-147, 2-169, 2-170 Command execution (conditional), with J/Install 2-
ignoreerror 2-53, 2-55, 2-56, 2-58, 2-83, 2-84, 2- 58
86, 2-88, 2-89, 2-90, 2-91, 2-94, 2-101, 2- Compress, parameters 2-56
102, 2-103, 2-110, 2-113, 2-114, 2-117, 2- Condition, parameters 2-58
119, 2-121, 2-122, 2-123, 2-125, 2-126, 2- Conditional connection. 2-58
128, 2-129, 2-132, 2-133, 2-135, 2-136, 2- Conditional execution of commands, checking
137, 2-140, 2-142, 2-145, 2-147, 2-148, 2- conditions 2-58
159, 2-160, 2-162, 2-163, 2-164, 2-165, 2- ConfAutologon, parameters, 2-83
166, 2-168, 2-169, 2-170 configuration, J/Launch installation 1-24
operator 2-58 ConfNonAdmin, parameters 2-84

Document version: 002 Reference and Using – User Guide 215

Index
J/Install

control file, exiting 2-113 F

control file, J/Install 1-13 Fallback, parameters 2-117
control file, stopping with error 2-109 Fallback, Registry backup 2-117
CopyFile, parameter 2-86 file attributes, keep 2-87, 2-92, 2-120
copying files, with J/Install 2-86 file checking for conditional execution of com-
CreateDir, parameters, 2-88 mands 2-63
CreateList, parameters 2-89 file settings, J/Install 1-16
CreateShortcut, parameters 2-90 file, renaming 2-86
creating directories, with J/Install 2-88 FileExists, checking conditions 2-63
creating file lists, with J/Install 2-89 files, deleting 2-101
creating shortcuts, with J/Install 2-90 files, registering 2-159
folder settings, J/Install 1-16
D fonts, registering with J/Install 2-159
data access, via paths 2-174 formats, for dates
data addressing 2-174 currencies 2-172
data medium request with J/Install 2-119 Date 2-173
date check, for conditional execution of com- numbers 2-172
mands 2-61 percentage 2-172
DateTimeCheck, checking conditions 2-61 formats, in search patterns 2-172
Decompress, parameters 2-91
Decompressing files, with J/Install 2-91 G
defining environment variables, J/Install 2-46 GetSource, parameters 2-119
defining Java System Properties, J/Install 2-46
defining user variables, J/Install 2-46 I
Definition, parameters 2-94 import, parameters 2-125
Delete, parameters 2-101 INF files, import 2-125
DeleteRegistryKey, parameters 2-102 INI file, value change with J/Install 2-142
Dialog, parameters 2-103 installation process control 2-50
directories, deleting 2-101 installation recording 1-14
DLLs, registering 2-159 installation, predefined automatic see J/Launch in-
drive check, for conditional execution of com- stallation
mands 2-62 IsFalse, checking conditions 2-64
DriveCheck, checking conditions 2-62 IsTrue, checking conditions 2-65
IsValidPassword, checking condition 2-66
E
element selection, in XML files 2-179 J
environment variable see ValueCheck, checking J/Install 1-2
conditions call parameters 1-10
environment variable, modifying 2-133 configuration 1-1, 1-10
environment variables control file 1-13
JINSTALL_JAVAHOME 1-9 Variables 2-46
JINSTALL_ROOT 1-9 general attributes
Exception, parameters 2-109 description 2-53, 2-55, 2-56, 2-86, 2-91, 2-
Execute, parameters 2-110 110, 2-121, 2-122, 2-123, 2-133, 2-
Exit, parameters 2-113 135, 2-136, 2-137, 2-140, 2-142, 2-
Expressions, regular 2-171 145, 2-147, 2-159, 2-160, 2-162, 2-
Extern, parameters 2-114 163, 2-164, 2-165, 2-166, 2-168, 2-
external command, specifying 2-114 169, 2-170

216 Reference and Using – User Guide Document version: 002

Index

J/Install
ignoreerror 2-53, 2-55, 2-56, 2-86, 2-91, 2- Script 2-162
110, 2-121, 2-122, 2-123, 2-133, 2- SetVariable 2-163
135, 2-136, 2-137, 2-140, 2-142, 2- ShowMessage 2-164
145, 2-147, 2-159, 2-160, 2-162, 2- ShowTextFile 2-165
163, 2-164, 2-165, 2-166, 2-168, 2- TuneOs 2-166
169, 2-170 Wait 2-168
parameters 1-16, 1-20 WriteLog 2-169
process control 2-50 WriteVersion 2-170
variable definition 2-46 J/Install scripts, running 2-162
J/Install command J/Install, logging 1-28
AskUser 2-53 J/Launch installation 1-24
CheckPassword 2-55 JAR files
Compress 2-56 compressing see compressing files, with J/In-
Condition 2-58 stall
ConfAutologon 2-83 decompressing see decompressing files, with
ConfNonAdmin 2-84 J/Install
CopyFile 2-86 [Link] 1-14
CreateDir 2-88 [Link] 1-16
CreateList 2-89 [Link] see configuration, J/Launch in-
CreateShortcut 2-90 stallation
Decompress 2-91 JRE, installation types 2-126
Definition 2-94 Jre, parameters 2-126
Delete 2-101 JRE, settings for installation 4-193
DeleteRegistryKey 2-102 JRE, updating 4-213
Dialog 2-103
Exception 2-109 K
Execute 2-110 Keep, parameters 2-128
Exit 2-113 keeping data, specify 2-94
Extern 2-114
Fallback 2-117 L
GetSource 2-119 logging installation see writing installation log en-
GetTextFile 2-121 tries, with J/Install
GetValue 2-123 logging, installation 1-14
Import 2-125 loop types 2-129
Jre 2-126 Loop, parameters 2-129
Keep 2-128 LoopEnd, parameters 2-132
Loop 2-129 loops
LoopEnd 2-132 conditional 2-129
ModifyEnvironmentVariable 2-133 elements 2-129
ModifyPendingFile 2-135 ending 2-132
ModifyString 2-136 endless 2-129
ModifyTextFile 2-137 linewise 2-129
ModifyToken 2-140 specified times 2-129
ModifyValue 2-142 starting 2-129
ModifyVariable 2-145 token list 2-129
OsBootLogo 2-147
ProClassic 2-148
Restart 2-159, 2-160
M
memory, checking availability 2-68

Document version: 002 Reference and Using – User Guide 217

Index
J/Install

MemoryCheck, checking conditions 2-68 CopyType 2-120

ModifyEnvironmentVariable, parameters, 2-133 Destination 2-56, 2-86, 2-91
ModifyPendingFile, parameters 2-135 Domain 2-160
ModifyString, parameters 2-136 Duration 2-168
ModifyTextFile, parameter 2-137 Encoding 2-169
ModifyToken, parameters 2-140 Entry 2-169
ModifyValue, parameter 2-142 ErrorCode 2-110
ModifyVariable, parameters, 2-145 ErrorFile 2-110
ErrorLogFileContentToAdd 2-110
O ErrorLogFileContentToAddEncoding 2-110
OCX files, registering 2-159 File 2-103, 2-114, 2-125, 2-147, 2-148, 2-159, 2-
OpenJDK, installing 2-126 166, 2-169, 2-170
Oracle JREs, installing 2-126 Folder 2-117, 2-126, 2-128, 2-148
OsBootLogo, parameters, 2-147 Group 2-84
Index 2-163
P LogFile 2-110
package checks, running 1-21 LogFileContentToAddEncoding 2-111
package installation, with J/Install 1-21 LogFileEncoding 2-110
Parameter value change, with J/Install 2-142, 2-145 LogFileToAdd 2-111
parameters Mode 2-160
CaseSensitive 2-138 MultiDisk 2-120
Delimiter 2-134, 2-143 Name 2-46, 2-86, 2-88, 2-101, 2-102, 2-170
Destination 2-135 Output 2-111
Encoding 2-138 OverWrite 2-57
File 2-137, 2-142 Parameters 2-111
FileToAdd 2-138 Password 2-55, 2-160
FileToAddEncoding 2-138 PendingFileHandling 2-111
Index 2-145 PostAction 2-125
Line 2-138 Prefix 2-114, 2-148
Mode 2-133, 2-135, 2-137, 2-143, 2-145 Program 2-110
Name 2-133, 2-145 Recursive 2-57, 2-86
Occurence 2-138 ResultFile 2-89, 2-93
Path 2-143 Shortcut 2-90
Pattern 2-145 Source 2-56, 2-86, 2-89, 2-91
Search 2-133, 2-138, 2-143 Static 2-126
Source 2-135 SuccessCode 2-111
Type 2-142, 2-145 SuccessFile 2-111
Unit 2-145 TagFile 2-120
User 2-134 TagFileContent 2-120
Value 2-133, 2-138, 2-143, 2-145 TagFolder 2-120
parameters, J/Install TagLabelContent 2-120
AddLogFileContent 2-169 TailFile 2-111
AddLogFileContentEncoding 2-169 TailFileEncoding 2-111
AddVariables 2-169 Target 2-90
Code 2-101, 2-113 Task 2-114
CopyDestination 2-119 Text 2-109, 2-113, 2-119, 2-168
CopyRecursive 2-119 Type 2-87, 2-92, 2-103, 2-117, 2-125, 2-126, 2-128,
CopySource 2-120 2-148, 2-159, 2-160

218 Reference and Using – User Guide Document version: 002

Index

J/Install
UnattendParameter 2-111 GetValue 2-123
Username 2-160 Import 2-125
Value 2-46 Jre 2-126
Value (starting from version 3.7) 2-170 Keep 2-128
Value (up to version 3.6) 2-170 LoopEnd 2-132
Variable 2-111, 2-119, 2-126 ModifyEnvironmentVariable 2-133
Version 2-126 ModifyPendingFile 2-135
Wait 2-112 ModifyString 2-136
WaitFile 2-112 ModifyTextFile 2-137
parameters, J/Launch ModifyToken 2-140
NoWaitDlg 1-24 ModifyValue 2-142
Parameter 1-24 ModifyVariable 2-145
Parameter. 1-24 OsBootLogo 2-147
Program 1-24 ProClassic 2-148
WaitDlgMessage 1-24 Register 2-159
WaitDlgTerminatingWindowCaption 1-24 Restart 2-160
password, checking against policy 2-66 Script 2-162
Patch files, with J/Install 2-56 SetVariable 2-163
pattern, apply for 2-172 ShowMessage 2-164
Patterns, for regular expressions 2-171 ShowTextFile 2-165
PC/E file, value change with J/Install 2-142 TuneOs 2-166
PCRunAs, chaning user 1-26 Wait 2-168
Popup dialog, displaying 2-164 WriteLog 2-169
Process control, command WriteVersion 2-170
GetTextFile 2-121 processing, stopping with forced error message 2-
Loop 2-129 109
Process control, commands 2-50 ProClassic, installing applications 2-148
AskUser 2-53 product version settings, for J/Install 1-20
CheckPassword 2-55 properties for [Link] 1-16
Compress 2-56 properties for [Link] 1-20
Condition 2-58 Property file, value change with J/Install 2-142
ConfAutologon 2-83
ConfNonAdmin 2-84 R
CopyFile 2-86 Recognition of patterns 2-171
CreateDir 2-88 Register, parameters 2-159
CreateList 2-89 Registry data, addressing 2-174
CreateShortcut 2-90 Registry files, import 2-125
Decompress 2-91 Registry Keys, deleting 2-102
Definition 2-94 Registry, value change with J/Install 2-142
Delete 2-101 RegistryKeyExists, checking condition 2-71
DeleteRegistryKey 2-102 Regular expression see Expression, regular
Dialog 2-103 Restart, parameters 2-160
Exception 2-109 RestartCheck, checking condition 2-72
Execute 2-110
Exit 2-113 S
Extern 2-114 search patterns, using 2-172
Fallback 2-117 Starting programs, with J/Install 2-110
GetSource 2-119 StringCheck, checking conditions 2-73

Document version: 002 Reference and Using – User Guide 219

Index
J/Install

Strings, compare 2-64, 2-65, 2-73, 2-136 writing installation log entries, with J/Install 2-169
substrings, assigning as values 2-163 writing version entries, with J/Install 2-170
system logon, with J/Install 2-160
X
T XML files, accessing 2-179
text file, displaying 2-165 XPath 2-179
text line, reading 2-121
text lines, check for existence 2-73 Z
text, changing with J/Install 2-137 ZIP files
TextFileCheck, checking conditions 2-73 compressing see compressing files, with J/In-
time check, for conditional execution of com- stall
mands 2-61 decompressing see decompressing files, with
timeout, with J/Install 2-168 J/Install
TokenExists, checking conditions 2-74
tool, JreUpdate 4-213
TuneOS, parameters, 2-166

U
update, JRE 4-213
user settings, perform 2-166
user, changing with PCRunAs 1-26
UserIsAdmin, checking conditions 2-76

V
Value change, for configuration parameters 2-142
Value change, for variables 2-145
Value, check existence 2-74, 2-79
ValueCheck, checking conditions 2-77
ValueExists, checking conditions 2-79
variable types 2-46
Variable, check existence 2-81
variable, internal, J/Install 2-46
Variable, set 2-123, 2-163
VariableExists, checking conditions 2-81
variables
access 2-46
control file 2-46
variables, internal 1-16
version formatting, J/Install 1-13
version settings, J/Install 1-20
version, internal formatting 1-13
[Link] 1-20

W
Wait, Parameter 2-168
wildcards, using 2-91
WriteLog, parameter 2-169
WriteVersion, parameter 2-170

220 Reference and Using – User Guide Document version: 002

Pc3 Service Manual
100% (1)
Pc3 Service Manual
15 pages
Diebold Nixdorf BEETLE Express 15 Operating Manual
No ratings yet
Diebold Nixdorf BEETLE Express 15 Operating Manual
35 pages
Advanced Function Dispenser Operating Guide TP 820714 001F
No ratings yet
Advanced Function Dispenser Operating Guide TP 820714 001F
45 pages
RPSW User's Guide
No ratings yet
RPSW User's Guide
180 pages
ND77 UserManual
No ratings yet
ND77 UserManual
63 pages
Banknote Handling Machine Tests
No ratings yet
Banknote Handling Machine Tests
41 pages
CCDM
100% (1)
CCDM
336 pages
Bulletin-SCPM Feeder Belts
No ratings yet
Bulletin-SCPM Feeder Belts
4 pages
Procash/Ndc V3.0/00 Proconsult/Ndc V3.0/00: User Guide
100% (1)
Procash/Ndc V3.0/00 Proconsult/Ndc V3.0/00: User Guide
438 pages
Messages RM3
No ratings yet
Messages RM3
84 pages
DN GlobalCatalog2016
No ratings yet
DN GlobalCatalog2016
1 page
Opteva 740 Operating Guide TP 820896 001F
No ratings yet
Opteva 740 Operating Guide TP 820896 001F
74 pages
NCR SS14 Information
No ratings yet
NCR SS14 Information
2 pages
Euro Diebold Opteva 328 177528r00
No ratings yet
Euro Diebold Opteva 328 177528r00
4 pages
USERMANUAL
No ratings yet
USERMANUAL
46 pages
UCDM Interface Specification 1.0
No ratings yet
UCDM Interface Specification 1.0
32 pages
Migrate Transactions, Maintain Customer Service: Diebold Nixdorf CS 2070 Multifunction Lobby Intelligent Deposit System
No ratings yet
Migrate Transactions, Maintain Customer Service: Diebold Nixdorf CS 2070 Multifunction Lobby Intelligent Deposit System
2 pages
Translated Version of Wincor PC 2100 Xe
No ratings yet
Translated Version of Wincor PC 2100 Xe
440 pages
Cineo C4040
100% (1)
Cineo C4040
406 pages
Diebold Nixdorf BEETLE Multi Interface Hub
No ratings yet
Diebold Nixdorf BEETLE Multi Interface Hub
36 pages
S2 Media Dispense Module
No ratings yet
S2 Media Dispense Module
7 pages
Terminal Programming SP4 2015
100% (1)
Terminal Programming SP4 2015
683 pages
INVENTORY 7/1/2019: 340 Camarillo Ranch RD Camarillo CA 93012 805-388-3455
100% (2)
INVENTORY 7/1/2019: 340 Camarillo Ranch RD Camarillo CA 93012 805-388-3455
73 pages
Ecs q67h2 Ad q65h2 Ad h67h2 Ad
No ratings yet
Ecs q67h2 Ad q65h2 Ad h67h2 Ad
44 pages
SHA-1 Deprecation and Migration To TR34
No ratings yet
SHA-1 Deprecation and Migration To TR34
8 pages
SS 22e PDF
100% (1)
SS 22e PDF
2 pages
SM 1500xeusb e 112081a1
50% (2)
SM 1500xeusb e 112081a1
692 pages
66e User Instructions PDF
No ratings yet
66e User Instructions PDF
4 pages
TechFlash - Sagem EPP Multiple Power Fail Security Lockout Feature 100506
No ratings yet
TechFlash - Sagem EPP Multiple Power Fail Security Lockout Feature 100506
2 pages
NCR Selfserv 27: Attr Act Customers With An Exceptional Atm Experience
No ratings yet
NCR Selfserv 27: Attr Act Customers With An Exceptional Atm Experience
2 pages
Crypta - Quick Start Guide
100% (1)
Crypta - Quick Start Guide
4 pages
Custom PPF
No ratings yet
Custom PPF
28 pages
CDM8240 Cash Dispensing Module Manual
No ratings yet
CDM8240 Cash Dispensing Module Manual
11 pages
Hyosung Tns Mx5700 490 KG Bts
No ratings yet
Hyosung Tns Mx5700 490 KG Bts
2 pages
NLX-ATX Motherboards
No ratings yet
NLX-ATX Motherboards
72 pages
5600 Install
No ratings yet
5600 Install
27 pages
CINEO - C2060 Datasheet EN
No ratings yet
CINEO - C2060 Datasheet EN
2 pages
Installation Manual
No ratings yet
Installation Manual
90 pages
7167 Parts Identification
No ratings yet
7167 Parts Identification
42 pages
Duplos
No ratings yet
Duplos
10 pages
Order Scheduler For Jabil
No ratings yet
Order Scheduler For Jabil
11 pages
TP30 Statement Printer Operator Manual 01750333701A EN
100% (2)
TP30 Statement Printer Operator Manual 01750333701A EN
61 pages
CODE ERROR Hyosung MX 5600
No ratings yet
CODE ERROR Hyosung MX 5600
34 pages
Skimming Protection Parts List
100% (1)
Skimming Protection Parts List
6 pages
DN Series Printer Manuals and Specs
100% (1)
DN Series Printer Manuals and Specs
3 pages
Detailed NCR APTRA Service Guide
No ratings yet
Detailed NCR APTRA Service Guide
3 pages
663X Samms Manual
100% (2)
663X Samms Manual
996 pages
Hitachi Becomes First To Deploy 10000 Cash Recycling Machines
No ratings yet
Hitachi Becomes First To Deploy 10000 Cash Recycling Machines
4 pages
DN Globalcatalog Systemsfinancial August2016 v01 en
No ratings yet
DN Globalcatalog Systemsfinancial August2016 v01 en
1 page
Service Manual
100% (1)
Service Manual
734 pages
The Fujitsu F53: Multi Cassette Media Dispenser
No ratings yet
The Fujitsu F53: Multi Cassette Media Dispenser
2 pages
NCR 56xx Personas Diagnostic Notebook
100% (1)
NCR 56xx Personas Diagnostic Notebook
270 pages
Replace Rm4 BNR Movem Controller Board: Guidelines Dn200V BPD Aceh - Diebold Nixdorf Indonesia - Technical Support
No ratings yet
Replace Rm4 BNR Movem Controller Board: Guidelines Dn200V BPD Aceh - Diebold Nixdorf Indonesia - Technical Support
5 pages
Technical Bulletin - CMDV4 Security Pairing
No ratings yet
Technical Bulletin - CMDV4 Security Pairing
4 pages
05 UR Error Code Specification R12actualizado
No ratings yet
05 UR Error Code Specification R12actualizado
553 pages
Configuring MEI Edge 5.x
No ratings yet
Configuring MEI Edge 5.x
3 pages
Translated Version of Wincor PC 2100 Xe
No ratings yet
Translated Version of Wincor PC 2100 Xe
440 pages
13 UR Adjustment Manual R01
No ratings yet
13 UR Adjustment Manual R01
80 pages
CINEO C2550 - Englisch - 20110308
100% (1)
CINEO C2550 - Englisch - 20110308
2 pages
Ancillaries II User Manual
No ratings yet
Ancillaries II User Manual
44 pages
DN Series System Technology Overview Presentation Americas 20230728
100% (1)
DN Series System Technology Overview Presentation Americas 20230728
247 pages
DN Series Pitch Deck
No ratings yet
DN Series Pitch Deck
70 pages
DN Series 450V Product Card
No ratings yet
DN Series 450V Product Card
2 pages
Prosetup 33 en
0% (1)
Prosetup 33 en
63 pages
Baby Names From Nakshatra
No ratings yet
Baby Names From Nakshatra
2 pages
EOL - List - Home - V5.0
No ratings yet
EOL - List - Home - V5.0
78 pages
NozzleBlockIssue UL L4260-05PowerCleaning
No ratings yet
NozzleBlockIssue UL L4260-05PowerCleaning
2 pages
Software Testing Laboratory Course 21ISL66
No ratings yet
Software Testing Laboratory Course 21ISL66
49 pages
Drift To Remember
No ratings yet
Drift To Remember
37 pages
MT07 User Manual
No ratings yet
MT07 User Manual
15 pages
IDX5315 - Al Shafar Invest Palm Jumeirah - TSSR - V1.1
No ratings yet
IDX5315 - Al Shafar Invest Palm Jumeirah - TSSR - V1.1
19 pages
Maths Booklet 3 - Answers
No ratings yet
Maths Booklet 3 - Answers
5 pages
Northwind Data Warehouse Creation Script
No ratings yet
Northwind Data Warehouse Creation Script
8 pages
IT Department Book List
No ratings yet
IT Department Book List
4 pages
Digimon X-Antibody Update Log
No ratings yet
Digimon X-Antibody Update Log
32 pages
TEM045V User Manual - MTEM045V-R02-0720
No ratings yet
TEM045V User Manual - MTEM045V-R02-0720
66 pages
Ai&Ml Lab
No ratings yet
Ai&Ml Lab
63 pages
Cool Reaper
No ratings yet
Cool Reaper
34 pages
E - Business - Unit-4
No ratings yet
E - Business - Unit-4
31 pages
AZ 140T00A ENU Powerpoint 01
No ratings yet
AZ 140T00A ENU Powerpoint 01
22 pages
FlashSystem - Distributed RAID - 2021-Jul-01
No ratings yet
FlashSystem - Distributed RAID - 2021-Jul-01
9 pages
Bachelor of Information Technology (Hons)
No ratings yet
Bachelor of Information Technology (Hons)
2 pages
Mission Expert CE U500 Manual (En) Lab-N 110723 Carol
No ratings yet
Mission Expert CE U500 Manual (En) Lab-N 110723 Carol
61 pages
EDPM Multiple Choice Topic by Topic Test
100% (5)
EDPM Multiple Choice Topic by Topic Test
12 pages
Kode Barang
No ratings yet
Kode Barang
16 pages
Soft Computing: Lecture Notes
100% (2)
Soft Computing: Lecture Notes
100 pages
Cybersecurity Internship Application
No ratings yet
Cybersecurity Internship Application
1 page
Jetson Agx Orindatasheet Update Module Series 2379600 v2
No ratings yet
Jetson Agx Orindatasheet Update Module Series 2379600 v2
2 pages
Electronics 12 01333
No ratings yet
Electronics 12 01333
42 pages
Understanding UNIX System Calls
No ratings yet
Understanding UNIX System Calls
2 pages
SVM Hands-On Problem
No ratings yet
SVM Hands-On Problem
7 pages
A Step-By-Step Guide To Trinity Digital Examinations
No ratings yet
A Step-By-Step Guide To Trinity Digital Examinations
20 pages
Berachain - DevOps Engineer
No ratings yet
Berachain - DevOps Engineer
1 page
Cbse Board Practical Examination-2024-25 (Information Technology)
No ratings yet
Cbse Board Practical Examination-2024-25 (Information Technology)
1 page