Diebold Nixdorf PROBASE is an integrated software solution that provides a comprehensive suite of capabilities designed to help you manage your business more efficiently and securely.
Here's a quick overview of some of the key features and possible use cases for PROBASE:
- Integrated teller automation: PROBASE offers a range of teller automation solutions, including cash dispensing, check processing, and account maintenance, to help you streamline your branch operations and improve customer service.
- Self-service banking: PROBASE provides a variety of self-service banking options, such as ATMs, kiosks, and mobile banking, to give your customers 24/7 access to their accounts and the ability to conduct transactions conveniently and securely.
Diebold Nixdorf PROBASE is an integrated software solution that provides a comprehensive suite of capabilities designed to help you manage your business more efficiently and securely.
Here's a quick overview of some of the key features and possible use cases for PROBASE:
- Integrated teller automation: PROBASE offers a range of teller automation solutions, including cash dispensing, check processing, and account maintenance, to help you streamline your branch operations and improve customer service.
- Self-service banking: PROBASE provides a variety of self-service banking options, such as ATMs, kiosks, and mobile banking, to give your customers 24/7 access to their accounts and the ability to conduct transactions conveniently and securely.
Page | 1
Application Configuration Utility User’s Guide
Revision 1.8, February 13th 2019
Contents
Introduction ............................................................................................................................................................................ 2
Application Configuration Utility ........................................................................................................................................ 2
What’s New in ACU 5.x ....................................................................................................................................................... 2
Operation ................................................................................................................................................................................ 2
Main Page ........................................................................................................................................................................... 2
Local service not running / Connect to host ....................................................................................................................... 4
Application Menu / Quick Access Toolbar ...................................................................................................................... 5
Configuration Page .............................................................................................................................................................. 5
Errors loading configuration page................................................................................................................................... 7
Saving Configuration ........................................................................................................................................................... 7
Errors while saving .......................................................................................................................................................... 7
Error after saving............................................................................................................................................................. 8
Appendix A ............................................................................................................................................................................ 10
Command Line Parameters ............................................................................................................................................... 10
Command List ................................................................................................................................................................... 10
Export Data ................................................................................................................................................................... 10
Export Configuration ..................................................................................................................................................... 10
Export Module .............................................................................................................................................................. 11
Run ................................................................................................................................................................................ 11
Import Data ................................................................................................................................................................... 12
Import File ..................................................................................................................................................................... 12
Defaults ......................................................................................................................................................................... 12
Synchronize ................................................................................................................................................................... 13
Return values for Commands ........................................................................................................................................... 13
Return values ................................................................................................................................................................ 13
Page | 2
Introduction
Application Configuration Utility
Application Configuration Utility (ACU) is a system configuration utility. ACU provides an integrated, terminal centralized
configuration of the entire ATM software stack and 3rd party software. This Utility is the main touch point to configure
the whole system. It is used to configure individual or combined Diebold Nixdorf software deliverables.
What’s New in ACU 5.x
The architecture for the ACU user interface was changed to a client server implementation. A service is running and
taking request from the user interface client, either remote or local. Command line operations are still running as stand-
alone. Command line operations are not available on remote clients.
An install is provided for terminals which includes the client and server. There is an additional install for desktops which
delivers only the client portion, this is meant for users to connect remotely to terminals from their desktops.
Additionally,
• .NET Microsoft Frameworks 4.5.1 was adopted on this version.
• User interface was updated to Windows Presentation Frameworks
• Remote access to configure terminals was introduced
Operation
Main Page
When ACU starts the client is automatically connected to the local service and main menu is presented. This is, if the
service is running (see Local service not running).
Page | 3
The following menu options are available on the Home tab:
Save: Save all pending changes in all modules loaded. This menu option becomes enabled when connected to a
server.
Discard Changes: Discard all changes in all modules loaded. This menu option becomes enabled when connected
to a server.
Mode: Mode selection. Application View (default) or System View for advanced users.
Configuration pages are divided by groups depending on the applications installed. These groups can be expanded or
collapsed for easy navigation. Some of the groups may be hidden depending on the selected view, either System or
Application mode.
The status bar at the bottom indicates the selected view mode and the connection status.
On the main page you can type a filter which displays only items that match description. Just enter text and hit enter or
select the filter icon . To remove filter just click the clear filter icon .
Page | 4
The following options are available on the System tab:
Import/Export: Open the Import/Export pane. This option is available only when connected to a local service.
Password: Open the system passwords pane. This option is available only when connected to a local service.
Networking: Open the networking pane. This option is available only when connected to a local service.
Help: Displays the help files available for the system. The “Application Configuration Utility” option displays this
document. Other options may be available depending on modules installed.
Local service not running / Connect to host
If the local service is not running when client starts, the connection page will be displayed
Page | 5
In this page users can type an IP address or computer name to connect and configure remote terminals. From ACU
v5.3.4 and above you can also use a port number in the form {ip address}:{port number} For local configuration you can
use localhost or 127.0.0.1.
To start local service select Start Local Service from the Application Menu. The service will start and the client will be
connected automatically.
If you are connecting to remote server and need to provide credentials you can check the Connect using different
credentials box and additional fields will be displayed; type user name and password. If a domain name needs to be
specified you can format the user name as {domain}\{user name}.
IMPORTANT for remote connections:
a. You can use only log in credentials of administrator users.
b. The date and time on both local and remote computers must be accurate.
c. Remote servers can’t have the UAC activated.
d. The listening TCP port was changed in ACU v5.3.4 from 8001 to 7451. If port is not specified, the ACU v5.3.4 will
try to connect to port 7451 by default.
Application Menu / Quick Access Toolbar
The Application Menu displays the available menu options and is activated by clicking at the Application Menu icon .
The following options are available:
Start Local Service: Starts or stops the local Windows service that handles configuration requests. If the user is
connected to local service and the service is stopped, the connection page is displayed again.
Exit: Close the tool
Configuration Page
When a configuration page is selected the configuration panel is displayed with all items to configure. The breadcrumbs
bar shows the depth level. You can click any item on the breadcrumb bar to navigate between screens. Home will take
you to main menu screen.
Page | 6
Changes in configuration are sent to the server immediately but these are committed until the Save button is clicked. If
an error is found during configuration the interface will show the error. You can hover the mouse over the error icon to
see more details.
If you make changes in configuration that result in an error you will get a notification when trying to exit
the screen. In such case you can chose to exit the screen or stay on the screen and fix the errors. It is
recommended to always fix the errors, depending on the validation rules some configurations may be
allowed to be saved with errors, causing problem in the system.
You can click on hyperlinks to display help tips for each configuration item, when available. To close the help bar you can
click again on same item or collapse the bar with the arrow icon.
Page | 7
Errors loading configuration page
If errors are caught while loading the schema, a red bar will be displayed on the bottom of the panel. The hyperlink will
display a popup window with the list of errors. The errors on this list are only for the loaded configuration panel and any
dependencies.
Saving Configuration
Errors while saving
Before changes are sent to server the information is validated. If errors are found the Save button shows a warning
overlay and a page displays the list of modules with error
Page | 8
Clicking on the module description hyperlink will open the configuration module where the error occurred. To return to
the error page users can click the Save button again.
Although is not recommended, user can click the Save Anyway button to commit changes to the server without fixing
the errors.
Error after saving
If errors are returned by the server after saving changes, a notification will be displayed on the main window status bar.
The hyperlink will display a popup window with the list of errors. This list of errors contains errors for all modules
processed during save.
Page | 9
Page | 10
Appendix A
Command Line Parameters
The command is asynchronous, it is recommended to run from scripts using the START command with the /wait
argument.
Up to Agilis Configuration Utility 4.12 the AgilisConfigurationUtility.exe application was used for both the command line
and the user interface. Starting from Agilis Configuration Utility 5.0 the user interface was separated as
AgilisConfigurationUtilitiRemote.exe, the command line utility is still the same AgilisConfigurationUtility.exe.
Command List
Export Data
Save only XML instances to a folder selected by the user. The user can choose what applications to export. This
command is used mainly to export data that will be imported back into a live terminal, that terminal will already have
the other files required for the Configuration Utility to function properly (i.e. all the schema files and all the System.xml
files)
Command Line:
>AgilisConfigurationUtility.exe -exportdata -app:agilisxv -app:ixxfs -path:"c:\temp"
Argument
Description
app
(optional)
An application. This application id will be the same as the id found in the system.xml file for each
application.
If this parameter is missing, then all applications will be exported.
If a root application is exported then all merge modules below it will be exported as well (e.g. Agilis
91x XV, and all extended apps will be exported for /app:agilisxv)
path
The output path. The folder will be created if necessary. The folder must be empty; if older files are
left then the export may not reflect the actual state of the ATM.
If this parameters is missing, the current folder will be the target
IgnoreMissingRegistryValues
This option applies only to elements whos location is defined by the registry codec. If used, the
export will not create a empty instance of the element in the target file if the registry entry is missing
IgnoreMissingValues
Same as IgnoreMissingRegistryValues but applies to all codecs
Export Configuration
The functionality is the same as Export Data, except that the XSD schema files are saved along with the XML instances, in
the same location. And the System.xml files will be exported and the directory structure of configuration information
will be preserved in order to be able to display the configuration information in an offline mode. This command line
option is mainly used to export configuration files that will be moved to an offline pc/laptop
Command Line:
Page | 11
>AgilisConfigurationUtility.exe -exportconfig -app:agilisxv -app:ixxfs -path:"c:\temp"
Argument
Description
app
(optional)
An application. This application id will be the same as the id found in the system.xml file for each application.
If this parameter is missing, then all applications will be exported.
If a root application is exported then all merge modules below it will be exported as well (e.g. Agilis ix XV, and all
extended apps will be exported for /app:agilisxv)
path
The output path. The folder will be created if necessary. The folder must be empty; if older files are left then the export
may not reflect the actual state of the ATM.
If this parameters is missing, the current folder will be the target
signxml
(optional)
Starting with ACU version 5.3.0 the exported XML files can be signed using the certificate on the ValiTech
token. Token must be inserted and authenticated. Certificate must be valid.
Export Module
Save only XML instances to a folder selected by the user. The user can choose what modules to export. This command is
used mainly to export single modules that will be imported back into a live terminal, that terminal will already have the
other files required for the Configuration Utility to function properly (i.e. all the schema files and all the System.xml files)
Command Line:
>AgilisConfigurationUtility.exe -exportmodule -module:iqc -module:iqe -
path:"c:\target\modules"
Argument
Description
module
A module namespace. This module namespace will be the same as the environment variable defined in the system.xml
file.
path
The output path. The folder will be created if necessary. The folder must be empty; if older files are left then the export
may not reflect the actual state of the ATM.
Run
This command is used to execute rules in a schema. Currently used by the factory preload process to run rules and set
initial values based on installed devices.
All modified schemas will be saved.
Command Line:
>AgilisConfigurationUtility.exe -run -path:"c:\schemas" -module:factory -loadenvironment
Argument
Description
Page | 12
module
A module namespace. This module namespace will be the same as the file name in the input folder.
More than one module may be specified using the 'module' parameter.
path
The input path where the schemas exist.
All dependent schemas must be in the same folder, otherwise these will not be found. If an external module
must be specified and cannot be copied, then a system.xml file may be created in the source path to declare
environment variables which point to schemas in other location (if environment is set as relative file, then it will
be relative to the location of ACU binary).
loadenvironment
Indicates that all system.xml files in the system will be loaded to declare the variables in the <environment>
section (see System Files). This must be used when your schema makes references to other schemas on the
system.
The system.xml files are read from the Applications folder in the directory where ACU was executed, or from the
path indicated in [HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Agilis Configuration Utility\AppDir] when this
value exists.
Import Data
Command Line:
> AgilisConfigurationUtility.exe -importdata -path:"c:\temp"
Argument
Description
path
The input path.
If this parameters is missing, the current folder will be the source
Import File
This command would only import one xml file for one module, this would be used in case of a hotfix and/or a CSD if
configuration for one module needs to be updated.
Command Line:
> AgilisConfigurationUtility.exe -importfile -file:"name.xml" -path:"c:\temp"
Argument
Description
file
Xml file that's properly formatted for import( generated from exporting data)
Path
The input path.
If this parameters is missing, the current folder will be the source
Defaults
Set values to default and save
Command Line:
Page | 13
> AgilisConfigurationUtility.exe -defaults -app:agilisxv -module:rprth
Argument
Description
app
(optional)
An application. This application id will be the same as the id found in the system.xml file for each application.
This parameter may have multiple occurrences
-app:ixxfs -app:agilisxv
Defaults will be set to these applications in addition to the list of modules
If a root application is indicated then all merge modules below it will be set to default as well (e.g. Agilis 91x XV, and all
extended apps will be set to default for /app:agilisxv)
module
(optional)
This parameter may have multiple occurrences
-module:rprth -module:rprim
Defaults will be set to this module in addition to the list of applications
If no default is defined for an element, then it won't be set. If not argument are defined then nothing will be done.
Synchronize
Load all modules, execute rules and save
Command Line:
> AgilisConfigurationUtility.exe -synchronize -app:agilisxv
Argument
Description
app
(optional)
An application. This application id will be the same as the id found in the system.xml file for each application.
This parameter may have multiple occurrences
-app:ixxfs -app:agilisxv
If no app is indicated, then all will be loaded
If a root application is synchronized then all merge modules below it will be exported as well (e.g. Agilis 91x XV, and all
extended apps will be exported for /app:agilisxv)
Return values for Commands
Return values
Returned values for the command line are
Value
Description
Page | 14
0
No errors. The command line value was executed successfully
1
Warnings. The command line value was executed successfully but the data has validation errors or warnings
2
Error. Arguments for the command line are missing.
Serious I/O errors while saving data
For Import:
- The user is not administrator
- Target folder does not exist
- Target folder is empty
For Default/Synchornize
- The user is not administrator
-
1
-
2
-
3
-
4
-
5
-
6
-
7
-
8
-
9
-
10
-
11
-
12
-
13
-
14
Diebold Nixdorf PROBASE is an integrated software solution that provides a comprehensive suite of capabilities designed to help you manage your business more efficiently and securely.
Here's a quick overview of some of the key features and possible use cases for PROBASE:
- Integrated teller automation: PROBASE offers a range of teller automation solutions, including cash dispensing, check processing, and account maintenance, to help you streamline your branch operations and improve customer service.
- Self-service banking: PROBASE provides a variety of self-service banking options, such as ATMs, kiosks, and mobile banking, to give your customers 24/7 access to their accounts and the ability to conduct transactions conveniently and securely.
Ask a question and I''ll find the answer in the document
Finding information in a document is now easier with AI
Other documents
-
Parallels Plesk Panel 10.4 User guide
-
Wiley 978-0-470-93920-8 Datasheet
-
VMware ESXI vCenter Server 6.5 User guide
-
VMware ESXI ESXI 6.0 User guide
-
Oracle Oracle Database B10772-01 User manual
-
Optimus XELLIP SERV MAX User manual
-
Novell ZENworks Linux Management 6.6.2 Administration Guide
-
IBM Universal Remote Version 5 User manual
-
Enfocus PowerSwitch 10, VL Level B, 3-5u, Ele Specification
-
