You are on page 1of 32

WebMaster Configuration/Logs/Support AS@R 2.6 - Sec.

Web 8

Sections WebMaster 8, 8a, 8b, 8c, 8d, 8e

Contents Sections

Configurations 8

Diagnostic / Logs 8a

Login Support 8b

End-of-Day Support / Troubleshooting 8c

DCUPDate Support 8d

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 1 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

WebMaster Section 8 Configurations

Contents Page

WebMaster System Configuration .................................................................................................... 3


File: mtxwm.properties ........................................................................................................................ 3
Navigator Properties ......................................................................................................................... 5
File navigator.properties...................................................................................................................... 5
Help System...................................................................................................................................... 6
File: help.properties ............................................................................................................................. 6
Parameter Maintenance Properties .................................................................................................. 6
File: param_maint.properties............................................................................................................... 6
LookUp Maintenance Properties....................................................................................................... 10
File: lu_maint.properties ................................................................................................................... 10
Login Properties ................................................................................................................................ 11
File: login.properties ......................................................................................................................... 11
End-of-Day Report Configuration...................................................................................................... 12
File: eod.properties........................................................................................................................... 12
Core End-of-Day configuration ......................................................................................................... 16
File: core.properties.......................................................................................................................... 16
Report Configuration ......................................................................................................................... 17
File: report.properties ....................................................................................................................... 17
Money Function Properties ............................................................................................................... 19
File: money.properties ...................................................................................................................... 19
News Function Properties................................................................................................................. 20
File: newsproperties ......................................................................................................................... 20
Applet Configuration.......................................................................................................................... 21
File: applet.properties ........................................................................................................................ 21
Applet GUI Configuration .................................................................................................................. 21
File: appletgui.properties ................................................................................................................... 21
End-of-Day (Core) Login Controller .................................................................................................. 22
File: controller.properties................................................................................................................... 22
Data Storage Controller ................................................................................................................... 22
File: datastore.properties................................................................................................................... 22
Data Capture Update Controller ....................................................................................................... 23
File: dcupdate.properties................................................................................................................... 23
Electronic Journal Configuration File ................................................................................................ 26
File: ej.properties ............................................................................................................................... 26
INIT Properties .................................................................................................................................. 27
File: init.properties ............................................................................................................................. 27
Print Framework Coniguration file..................................................................................................... 28
File: print.properties........................................................................................................................... 28
Retention Coniguration file................................................................................................................ 29
File: retention.properties.................................................................................................................... 29
Version Properties............................................................................................................................. 31
File: version.properties ...................................................................................................................... 31
POS Cluster Monitor Configuration File............................................................................................ 32
File: watch.properties ........................................................................................................................ 32

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 2 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

WebMaster System Configuration

File: mtxwm.properties
All general system properties of the WebMaster are stored in the mtxwm.properties file.

File name: mtxwm.properties


Location: <Drive>:\web\mtxwm\conf\

Database
For the database access a JDBC driver, a database path (URL), a database user (with
SELECT,INSERT,UPDATE,DELETE permission) and the user password have to be declared here.
The timeout parameter defines the time in seconds the JDBC driver will wait until it reports a timeout
error while connecting to the database.

db.driver=com.microsoft.jdbc.sqlserver.SQLServerDriver
The JDBC driver to be used
db.url=jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=MTX;Select
Method=cursor
The name of the datasource
db.user=mtxadmin The database user
db.password=mtxadmin The password of the database user
db.timeout=30 The timeout in seconds
db.connections=10 The number of database connections initially opened by
the Webmasters connection pool.
db.odbc=MTX The ODBC datasource name of the WebMaster
database.

Paths
The paths point to special resources in the WebMaster environment. There are two different path
types: virtual and physical. Virtual paths are used by the clients to access internet resources of the
WebMaster, physical paths are used by servlets to access the file system on the Web Server.

Attention: the "/" at the end (and sometimes at the beginning) of the paths are mandatory

appl.base=/MtxWM/ virtual - Virtual root of the WebMaster.


cscript.path=scripts/ virtual - Client side scripts (relative to virual root).
servlet.path=servlet/ virtual - All servlets (relative to virtual root).
image.path=images/ virtual - Images used for HTML pages (relative to virtual
root).
css.path=style/MTXStd01.css virtual - The concrete stylesheet used for HTML pages
(relative to virtual root)

local.base=./mtxwm/ physical - The physical path of the WebMaster's root


directory on the Web Server's file system.
log.path=./mtxwm/logs/ physical - Log files

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 3 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

gm.path=./mtxwm/gm/ physical - Cobol Grandmaster subsystem. This entry will be


removed as soon as no Cobol module is used
anymore.
help.path=./mtxwm/help/ physical - Directory for help files

Currency, Date And Time Formats


Currency Format:
The currency properties describe the look and feel of displayed amounts. They are valid for all
currency except the number of decimal places and the currency symbol. These properties are only
valid for the local / home currency. For foreign currencies these properties are taken from the AS@R
parameters.

Some WebMaster functions do not support grouping (e.g. financial report: it is designed to be able to
be printed as 40 column report).

It is not allowed to use the same character as decimal and grouping separator.

format.currency.pattern_without_symbol="#\,##0.00;-#\,##0.00"
The format how an amount should be displayed if no
currency symbol is wanted.

format.currency.pattern="#\,##0.00 S;-#\,##0.00 S"


Two decimals, grouping with three digits, sign in front
of amount, currency symbol after the amount
separated by a blank
format.currency.decimal="\," Use comma as decimal separator.
format.currency.grouping="." User a dot as grouping separator.
format.currency.symbol="USD " Use the string "USD" as currency symbol

Date And Time Format:


format.date.pattern="m/d/yy" 1st month with at least one digit, separated the day by
nd
a slash symbol; 2 day with at least one digit, separated from the year
by a slash symbol; 3rd two-digit year (e.g. 99 for 1999, 02 for 2002)
format.date.pattern.extended="EEEE\, d. mmmm yyyy"
Same as format.date.pattern but with additional possible
patterns. The example results in a date like Monday, 3. February
2002.
format.time.pattern="h:mm:ss t" 1st hour in 12-hour format, separated from the
minutes by a colon; 2nd minutes with two digit (e.g. 07, 35), separated
from the seconds by a colon; 3rd seconds with two digits, separated
from the AM / PM marker by a blank; 4th the AM / PM marker

DDQ Date Pattern


ddq.datePattern=dd.mm - The pattern which is used in date type demographic questions.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 4 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Misc. Systemproperties

locale.country The given locale is set as default locale for


the VM. It will affect GUI components that
display locale dependant values (e.g. date).
See Java documentation of java.util.Locale
for possible values that can be set as
language / country.
locale.language see locale.country
server.codepage=cp437 Codepage / character set used by Server
maintenance.language= If set to TRUE all missing texts will be added
automatically to the DB (default is FALSE)
storeminder=TRUE Only for demo: fire StoreMinder event
ticker.interval=20 The inteval in seconds of the WebMaster
ticker. It is used for frequent system
functions.
ticker.news.enable=TRUE Check frequently for not yet confirmed
messages.
system.service.sequential.version=2 System flag for service request handling - DO
NOT CHANGE

Navigator Properties
File navigator.properties

navigator.button.mainmenu.visible=TRUE Visibility flag for 'main menu' shortcut button


navigator.button.mainmenu.url=/MtxWM/servlet/TermInfoServlet
Jumpback URL for "main menu"-button
navigator.font.name= Font used for button labels
navigator.font.size= Font size used for button labels
navigator.font.style= Font style for button labels (BOLD and ITALIC possible; write
"BOLD | ITALIC" to use both styles)
navigator.minbuttons=9 Minimum number of buttons displayed
navigator.button.back.visible.additional=FALSE
Display 'back' buttons as standard menu button (TRUE) or not
(FALSE)
navigator.info.menu.title=TRUE
Display the title of the current menu (TRUE) or not (FALSE).

navigator.path.absolute=TRUE
Interpret any path entered into the shortcut field of the
navigator as absolute (TRUE) or relative (FALSE) path.
Relative means that the path is performed from the current
menu. Absolute means that the path is always performed
from the Webmasters root menu, no matter what menu is
currently displayed.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 5 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Help System
File: help.properties
The help system is currently not available. Please do not change the values of any help system
property.

Parameter Maintenance Properties


File: param_maint.properties

Configuration Details

Overview

export.dir.posserver
export directory for transmission to the pos server

export.dir.posserver.ctlfile
name of the control file that will be for synchronization with the pos server

export.dir.default
the basic directory for generation of flat files during the flat file export function

export.dir.default.ctlfile
name of the flat file export control file for synchronization with external applications distributing the flat
files

export.eod.suppress
controlling of the export functionality during the End of Day process

export.eod.timeoffset
Parameter export is performed during eod, this value will be used to calculate the time when a system
day should be considered to be over

export.gui.yearrange.before
configuration of export gui (selection of export date) number of years before and

export.gui.yearrange.after
after the current year

export.eod.preview.future
number of days to look into the future for export date selection, the values are added to the eod date
when the export is performed, every change date in the database that is in the period will be offered
as a possible export date

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 6 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

export.file.<name>
file that will be exported

export.file.S_SLMXXX.ORG
export.file.S_REGXXX.ORG
export.file.S_PLUSIN.DAT
export.file.S_PLUREF.DAT
export.file.S_PLUCRD.DAT
export.file.S_PLURCD.DAT
export.file.S_CTLXXX.ORG
export.file.S_ACTXXX.ORG
export.file.P_REGPAR.DAT
export.file.P_REGMOD.DAT
export.file.P_REGDDQ.DAT
export.file.M_LANXXX.ORG

transfer.dir.export
directory where transfer files should be placed after creation

transfer.dir.import
directory where the transfer import tool should look for files

Option Details

Export options

export.dir.posserver
The directory name given will be used by export directory for transmission to the pos server if flat files
are created at store level the generated flat files. The flat files will be placed in this directory. The
delimiter must be set UNIX like.

export.dir.posserver =./mtxwm/gm/hoc/org

export.dir.posserver.ctlfile
The name is given will be use as name the for the control file that will be created in the given
directory. If no name is given or the option missing the control file will not created. The delimiter must
be set UNIX like.

export.dir.posserver.ctlfile=ASRPARAM.CTL

export.dir.default
The flat files that are exported for lower organizational units are placed in this directory. A
subdirectory with the number of the OrgUnit is created for every store during the export function.

Example:
export.dir.default=./mtxwm/parexport
If flat files are exported for OrgUnit 4, these will be stored in a directory named ./mtxwm/parexport/4.
The directory will be created if not found.

export.dir.default.ctlfile
The name is given will be used for a naming of the control file that will be created in the given
directory If no name is given or the option missing the control file will not created. The delimiter must
be set UNIX like.

export.dir.default.ctlfile=export.ctl

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 7 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

export.eod.suppress
This parameter is used during the calling of the export function during the End of Day process. It
indicate if the should be a flat file creation/generation during the End of Day. If the value is set to 0,
the flat files will be created, the value 1 indicates the no flat files will be created.

export.eod.suppress=0

export.eod.timeoffset
This parameter will be used when parameter export is performed during End of Day (depends on
the export.eod.suppress). This value will be used to calculate the time when a system day should be
considered to be over. The value sets the number of hours before/after midnight. Remark: positive
offsets are also allowed (after midnight).

Example:

export.eod.timeoffset=-4
TRUE date: 12.8. | 13.8.
time: ----------------20:00------------24:00-------------
Date for EXPORT: 12.8. | 13.8.

export.gui.yearrange.before / export.gui.yearrange.after
These options will be used by the user interface (client side component) configuration of export
function. It will be used to determine which dates the user can select of export function. The date
controls the values that are stored in the flat file (see concept document)
number of years before and after the current year

export.gui.yearrange.before=-1
export.gui.yearrange.after=1

export.eod.preview.future
This option indicates the number of days to look into the future for export date selection. The values
are added to the End of Day date when the export is performed. Every change date in the database
that is in the period will be offered as a possible export date.

export.eod.preview.future=10

export.file.<name>
The file name is given by name will be exported, if the value is set to "1". Any other values or
missing entries will suppress export of file. If creation/generation a new flat file is needed, there must
be an entry with its file name and the value 1 otherwise the file will not be created.

export.file.S_SLMXXX.ORG=1
export.file.S_REGXXX.ORG=1
export.file.S_PLUSIN.DAT=1
export.file.S_PLUREF.DAT=1
export.file.S_PLUCRD.DAT=1
export.file.S_PLURCD.DAT=1
export.file.S_CTLXXX.ORG=1
export.file.S_ACTXXX.ORG=1
export.file.P_REGPAR.DAT=1
export.file.P_REGMOD.DAT=1
export.file.P_REGDDQ.DAT=1
export.file.M_LANXXX.ORG=1

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 8 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Transfer options
transfer.dir.export
The option offers the directory where transfer files should be found after creation.

transfer.dir.export=./mtxwm/partransfer/export

transfer.dir.export.<OrgUnitId>

This entry indicates a special directory for the OrgUnit owning the given OrgUnitId.

transfer.dir.import
The option offers the directory where the transfer import tool should look for files.

transfer.dir.import=./mtxwm/partransfer/import

transfer.dir.import.<OrgUnitId>
This entry indicates a special directory for the OrgUnit owning the given OrgUnitId.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 9 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

LookUp Maintenance Properties

File: lu_maint.properties
This is the configuration file for the WebMaster lookup maintenance modules.

File name: lu_maint.properties


Location: <Drive>:\web\mtxwm\conf\

Miscellaneous

dp.enabled=FALSE TRUE if the Digital Promotions functionality is available.

LU-ID-Search Components

idsearch.item.pagesize=5000 The number of records which are contained in a page of


the item search component (must be at least 1).

idsearch.item.cachesize=3 The number of pages which are cached by the item


search component (must be at least 1).

Promotions Maintenance
The promotions maintenance is used to manipulate promotion points and promotion variable. If the
Digital Promotions module is not available some of the values are hidden (i.e. not editable).

promoMaintenance.campaign.editable=FALSE
Set to TRUE if the user can enter the campaign no. during
the maintenance; FALSE if the default campaign no.
should always be used. The default campaign no. is
stored in the property dp.campaign.default.

promoMaintenance.campaign.default=0000
The default campaign no. which is used if the user cannot
enter the no. (see property dp.campaign.editable).

promoMaintenance.showExisting=TRUE
Set to TRUE if the current total points of the selected
points type or the current total amount of the selected
variable should be displayed.

promoMaintenance.variables.list=99990,99991,99992
A comma-separated list of variable IDs. Valid IDs are
positive numbers in the range from 0 to 99999. The
preconfigured IDs are dummy values. Please configure
your valid IDs.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 10 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Login Properties

File: login.properties
This is the configuration file for the WebMaster login modules.

File name: login.properties


Location: <Drive>:\web\mtxwm\conf\

Common To All Modules

login.defaultModule=LoginCTL This is the login module used by default if the


corresponding servlet parameter CLASS is not specified.
The LoginCTL and be replaced by LoginName for a
different login procedure.

LoginCTL is requires the following login:


User No. and Secret No. e.g. 80101
Password: - e.g. office

LoginName is using the following login:


User name: - e.g. G. Willig (from S_CTLxxx.ORG file)
Password: - e.g. office

login.offline=FALSE If set to TRUE no error message will inform the user that the
POS Server was offline during login. Some other services like
sending missing IDC to POS Server will be disabled, too.
Logging will not write communication exceptions caused by
login. Use this flag if no POS Server is installed (e.g. in
headquarters).

development.server=934 This property can be used in a development environment to


allow several POS Servers be configured in the database. It
specifies which of the configured POS Server is used by the
WebMaster's auto-logout service.

Module Specific Properties


The template "<module>" in the description of the following properties must be replaced by the name
of a specific login module (e.g. LoginCTL).

<module>.selectTerminal=1
0 / false = use dynamic terminals
1 / true = allows selection of a user-defined terminal

<module>.hideUserNo=0
0 / false = entered digits of user no. and secret no. are displayed as digits
1 / true = entered digits of user no. and secret no. are displayed as '*' (like passwords)

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 11 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

End-of-Day Report Configuration

File: eod.properties
The EoD application is configured via the eod.properties file.

File name: eod.properties


Location: <Drive>:\web\mtxwm\conf\

MODULES
server.primary.timeout=10
server.backup.timeout=10 Defines the time in which the backup server has to perform its
day-change. Otherwise the EoD is interrupted.
ptd.ACT=TRUE
ptd.REG=TRUE
ptd.SLM=TRUE
ptd.DPT=TRUE
ptd.CKR=TRUE
ptd.duration=10

automatic.execution=FALSE (EOD runs automatically)


means EOD runs not automatically. If value is true EOD starts and finishes automatically. The
user can not press start or exit button.

automatic.execution.restart=FALSE (Behaviour in case of aborting)


means if EOD is aborted and runs automatically (automatic.execution=TRUE) the start button
is now visible and must be pressed. If value is true the EOD start button is not visible and
EOD starts again automatically.

automatic.logout=TRUE (Automatic logout)


means EOD finishes automatically. It is possible to press the exit button, but it is not
necessary.

automatic.logout.timeout=5 (logout after configurable time)


means after 5 minutes EOD finishes, logout is made automatically (that is only working if
automatic.logout=TRUE is set)

VIEW
view.tryconnect.counter=10 (Delay for getting new core results)
0,01 seconds waits the thread on controller view before asking for new results (1000 = 1s).
Do not change this value.

view.trylogout.counter=20 (Logout counter)


view.trylogout.counter=20 means the controller tries to logout 20 times (that is necessary in case of
temporarily inactivity of Core). Do not change this value.

view.moduleprocessing.exitbutton.enabled=FALSE (Exit button enabled/disabled)


means the exit button is disabled during module processing.. The button can not be disabled
during evaluation part.

view.button.informterminals.enabled=FALSE (Inform button visible/invisible)


means the inform button is not visible and terminals can not be informed about logout.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 12 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

view.button.declaredefect.enabled=TRUE (Declare defect button visible/invisible)


view.button.declaredefect.enabled=FALSE means the declare defect button is not visible.
Terminals can not be defectly declared.

view.button.logout.webterminals.enabled=TRUE (Logout webclients button visible/invisible)


view.button.logout.webterminals.enabled=FALSE means the logout webclients button is not
visible. Web terminals can not be automatically logged out.

spoolfile.must.print=FALSE (print Spool file)


means spoolfile has not to print. If value is true the spoolfile must print and EOD can not run
without printing.

Default size of eod applet


view.width=775
view.height=625
That is the applet size. It is not recommended to change these values. The GUI is generated
for this size.

Stop Core / JRE stop/start after completion


In order to activate possible software updates and to clean up the Java environment, the WebServer
has to be stopped (=TRUE).

If the terminal which starts the EoD is in a different domain than the WebServer, this has to be set to
FALSE. The WebServer cannot be stopped within this routine.

completion.shutdown=TRUE (Shutdown after finishing) TRUE or FALSE


means after a completed EOD a shutdown process is proceeded. This process can be a
batch file (see next point)

completion.call.file.name=mtxwm\\gm\\sh\\WMUPD1.BAT (Call shutdown batch file)


means after a completed EOD the given file is called (thats only possible, if
completion.shutdown=TRUE).

Reports included in End-of-Day


Determines if a report participates at EoD or not.

Standard reports:
=============
EodReportLAN: LAN Status Report
EodReportACT: Hourly Activity Report
EodReportREG: Financial Report
EodReportSLM: Sales Person Report
EodReportDPT: Department Report
EodReportCKR: Checker Report
EodReportRCC: Reset Control Counters Report
EodReportESA: Employee Sales Report
EodReportMFR: Money Function Report

A report will participate at EoD in case it is added to the following line:

report.classes=EodReportLAN;EodReportACT;EodReportREG;
EodReportCKR;EodReportSLM;EodReportDPT;EodReportMFR;EodReportRCC;
EodReportESA;

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 13 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Report definition as total, by terminal, by terminal groups


Determines if a report is created by using data from all terminals, one specified terminal or terminals
belonging to a group.

Terminal selection
=======================================================
# TOTAL: Generate a report by using all terminals
# TERMINALS: Generate a report for each active terminal
# GROUPS: Generate a report for each group

terminal.selection.ACT=TOTAL Hourly Activity Report


terminal.selection.REG=TOTAL Financial Report
terminal.selection.SLM=TOTAL Sales Person Rep
terminal.selection.DPT=TOTAL Department Report

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 14 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Totals displayed / printed with zero value


Determines if zero values are displayed / printed or not.

TRUE: Line is displayed even it has only zero values


FALSE: Line is only showed when all values are not zero

display.zero.values.SLM=FALSE Sales Person Report


display.zero.values.DPT=FALSE Department Report
display.zero.values.RCC=FALSE Reset Control Counters Report

Report Framework related properties

module.ReportFrameworkModule.reports= a semicolon separated list of reports


printed during Eod

module.CrystalReportsCleanUp.tables= a semicolon separated list of tables


emptied during Eod

IDC Source
IDC.source=HOCIDC HOCIDC: IDCs are retrieved from the HOCIDC.001 file
DATABASE: IDCs are retrieved from the database

Old IDC Update


module.idcupdate.alwaysenabled=FALSE
If set to TRUE the Eod module of old IDC update is always
executed no matter if the old IDC Update is configured to run
during the day or the new DC Update. If set to a different
value or not set at all, the Eod module of the old IDC Update
is only executed if the old IDC Update is configured to run
during the day.

Print of Spool file


spoolfile.must.print=FALSE Spool file has to print or not with FALSE / TRUE

Limited Controller
core.controller.limited.port=9799
core.view.port=9800
core.host=localhost
core.serialization=STANDARD

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 15 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Core End-of-Day configuration

File: core.properties

core.controller.standard.port=9798 The port to which a controller must connect


core.controller.limited.channels=5 The number of limited channels that can be
connected to the EOD are one time
core.controller.limited.port=9799
core.database.connections=5 The number of database connections which
are allocated by the connection pool

core.eval.delay=2 Time in seconds of the delay between two


evaluation steps.

core.eval.generation.update=TRUE Blocks EOD in case of unprocessed


generations

core.eval.Signal.pos.blocksize How many terminals should be grouped in


one block for End-of-Day information;
e.g. required for terminals with EFT.

core.eval.Signal.pos.timeout The elapsed time until the wait-for-finalization


procedure for the terminal group is released.

core.eval.SettlementEvaluation.verify A check will be performed for settled /


unsettled cashiers.

core.generations=006 The number of generations that are kept by


the core (log files etc.)

core.host=ASR25-PC2 The computer name on which the EoD is


running.

core.output.processor.classes=; Class name


These classes process data before being
sent to the view.

core.serialization=STANDARD DO NOT MODIFY


core.view.channels=2 The maximum number of views
core.logging.debug Setting this entry to TRUE will create more
informations within the CoreStatus.log file.

core.view.port=9800 The port number to which a view must


connect

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 16 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Report Configuration

File: report.properties
This is the configuration file for the WebMaster (Reports).

File name: report.properties


Location: <Drive>:\web\mtxwm\conf\

Totals displayed / printed with zero value


Determines if zero values are displayed / printed or not.

TRUE: Line is displayed even it has only zero values


FALSE: Line is only shown when all values are not zero

display.zero.values.SLM=FALSE Salesperson
display.zero.values.DPT=FALSE Department
display.zero.values.RCC=FALSE Reset Control Counter

Financial Report - Proficiency total block displayed / printed


Determines if this block is displayed / printed or not.

Financial Report - Proficiency (TRUE/FALSE)

display.proficiency.REG=TRUE

Checker Report - Proficiency total block displayed / printed


Determines if this block is displayed / printed or not.

Checker Report - Proficiency (TRUE/FALSE)

display.proficiency.CKR=TRUE

Department Report - totals displayed / printed with structure symbol *


Determines if this symbol is show.

Department symbol (default=*)

department.symbol=*

Checker List - Display of secret number

A user needs at least this security level to


access certain report functions

security.level=3

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 17 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Log/Status files
Determines which log/status files will be displayed for selection. Do not add the .log/.status
extension.
CoreStatus.log : Information about a running EoD
maintain.log : Information about parameter maintenance
WM.log : General informations about the running system
Eod.status : EoD status informations
Init.status : Init status informations

files.log=EodStatus;maintain;WM;CoreStatus;
files.status=Eod;Init;EodStep;

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 18 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Money Function Properties

File: money.properties
This is the configuration file for the WebMaster money functions.

File name: money.properties


Location: <Drive>:\web\mtxwm\conf\

Checker Functions

The properties of the checker functions are stored in the file money.properties in the properties
folder. All properties in this file which are related to the checker functions start with the prefix
checker..

checker.default The properties in this branch are used as default values.


They can be overwritten by properties in function specific
branches.
checker.default.dialog.main
Properties for the main dialog (tender selection dialog)
checker.default.dialog.main.accountability
Display the accountability columns (1) or not (0)
checker.default.dialog.main.difference
Display the difference columns (1) or not (0)
checker.default.dialog.main.totalAmount
Display the total amount field (1) or not (0)
checker.default.dialog.main.totalDifference
Display the total difference field (1) or not (0)
checker.default.dialog.denomination.show
Hide (0) or show (1) the input fields for the denominations. If
the fields are hidden, input can only be done into the variable
amount field of the dialog.
checker.loan.dialog.main.accountability

The overwriting, function specific branches have the same structure / properties as the default
branch. These branches need not to overwrite all properties of the default branch. It is possible for
them to overwrite only some of the default properties. The difference of those branches to the default
branch is the prefix. The prefix checker.default is replaced by the function specific prefix.

The following table shows the function specific prefixes:

Checker Function Prefix


loan checker.loan
pickup checker.pickup
float checker.float
media count checker.mediacount

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 19 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

News Function Properties

File: newsproperties
This is the configuration file for the WebMaster (news).

File name: news.properties


Location: <Drive>:\web\mtxwm\conf\

monitor.check.delay=4 Timer setup in seconds for monitor check

count.predefinedMsg=10 Count of predefined messages in the table


newsmessage in DB
readtable.userno=TRUE User number is in readtable - TRUE or FALSE
readtable.username=TRUE User name is in readtable TRUE or FALSE

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 20 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Applet Configuration

File: applet.properties
(version ASR_GCA02.001)

default size of the applets


applets.width=600
applets.height=400

applets.javaVersion=1.3.1,1.3.1_20
comma separated list of the accepted JRE versions
(e.g. 1.3.0, 1.3.0_01, 1.3.1, 1.4.2_03)

applets.javaMimeType=application/x-java-applet;version=1.3.1
mime type of the ASR applets

applets.cabVersion=1,3,1,20 version of the installation file that is used if a client has no


JRE yet or needs an update

applets.checkForJavaFamily=FALSE
enable the Java 1.3.1 family feature check of the Java plugin
(if enabled, a Java version which supports the family tag for
Java 1.3.1, must be installed on all browser PCs)

Applet GUI Configuration

File: appletgui.properties

Color.??? default Color definition for assigning in GUI color section (hexadecimal)

Color.White=FFFFFF
Color.Red=FF0000
Color.Green=00FF00
Color.DarkGreen=64C666
Color.Blue=0000FF
Color.Black=000000
Color.BrightGray=B6B6B6

GUIColor.??? Assignment of Colors to GUI elements

GUIColor.TableHeaderBackgroundColor=Blue
GUIColor.TableHeaderForegroundColor=White
GUIColor.OKButtonBackgroundColor=BrightGray
GUIColor.OKButtonForegroundColor=Black
GUIColor.CancelButtonBackgroundColor=BrightGray
GUIColor.CancelButtonForegroundColor=Black
GUIColor.HeadlineBackgroundColor=Blue
GUIColor.HeadlineForegroundColor=White

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 21 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

GUIColor ??? eod init color

GUIColor.EodInitTableHeaderReadyBackgroundColor=Blue
GUIColor.EodInitTableHeaderReadyForegroundColor=White
GUIColor.EodInitTableHeaderInEodBackgroundColor=DarkGreen
GUIColor.EodInitTableHeaderInEodForegroundColor=White
GUIColor.EodInitTableHeaderNotReadyBackgroundColor=Red
GUIColor.EodInitTableHeaderNotReadyForegroundColor=White

End-of-Day (Core) Login Controller


File: controller.properties

eod.user=801 user who started eod


eod.terminal=800 eod terminal
eod.server=999 eod pos server
eod.store=1234 eod store number
controller.terminal.timeout=5 time out on terminal evaluation in minutes
controller.core.connection.timeout=2 time out if core can not connected
controller.logout.counter=20 logout counter

Data Storage Controller


File: datastore.properties

Do not change any property in this file.


It is the configuration file for the WebMasters persistent framework.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 22 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Data Capture Update Controller


File: dcupdate.properties

Start-up settings

dcupdate.class=com.ncr.mtx.dcupdate.app.DcUpdateServiceController
class loading DCUpdate application
dcupdate.enable=true true means enable, false means disabled

Settings for Database connection parameters


db.driver=com.microsoft.jdbc.sqlserver.SQLServerDriver
db.url=jdbc:microsoft:sqlserver://COUMPTER_NAME; SelectMethod=cursor
db.user=mtxadmin
db.password=mtxadmin
db.connections=2
db.timeout=30

DC Update terminals
dcupdate.terminal=888 terminal number assigned to DCUpdate application
(reference to M_LANXXX.ORG file)

Settings for IDC / JRN data import sizes


IDCReader parameters:
IDCReader.maxTransactions=1000 maximum number of transactions to read at once into
the memory
IDCReader.maxRecords=5000 maximum number of records to read at once into the
memory

JRNReader parameters:
JRNReader.maxTransactions=1000 maximum number of transactions to read at once into
the memory
JRNReader.maxRecords=5000 maximum number of records to read at once into the
memory

Journal Import after IDC Import


Normally JRN and IDC import are executed in separate processes.
JRN import with IDC, this means the Journal will be imported only if Item Data Capture is requested
by the server.
Thus the performance is acceptable, but it will not import the Journal if the IDC was already imported.
This function will not be used in the future.

jrn.import.after.idc=false

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 23 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Setting for reading data from the POS server


idcwait=7 IDC WAIT for next polling in millis (7 secs..)
jrnwait=11 JRN WAIT for next polling in millis (eg 12 secs..)
eodwait=10 EOD WAIT for next polling in millis (eg. 10 secs )
eod.on.lan=true true = EOD check on LAN report.
false = EOD signal must be recognized by
E-message from server

dcu.timeout=40 Re-try for each terminal ( dcu.timeout /total


terminals). This is checked only during EOD request.
When there are 10 active terminals, each terminal
polled 40/10 = 4 times

dcupdate.init.password=88888 This password is checked against dcupdate


initialization of current data. It is not considered if
user enters super user password 99999

dcupdate.logging.mode=INFO logging mode, valid values can be INFO / DEBUG

Setting for IDC parsers


max.records=1500 Parser' cache limits as number of records read from
DB. This function will not be used in the future.

max.transactions=50 Parser' cache limits as number transaction read from


DB. This function will not be used in future.

Parsers Settings with DCUpdate application


standard.parsers=2
standard.parser.1=com.ncr.mtx.dcupdate.idc.parser.PlsParser
standard.parser.2=com.ncr.mtx.dcupdate.idc.parser.ClsParser

Setting for the Cache class for each parser defined above (Mandatory)
com.ncr.mtx.dcupdate.idc.parser.PlsParser=com.ncr.mtx.dcupdate.idc.parser.cache.PlsParserCache
com.ncr.mtx.dcupdate.idc.parser.ClsParser=com.ncr.mtx.dcupdate.idc.parser.cache.ClsParserCache

Settings effective during EOD request


dcupdate.eod.timeout=120 dcupdate server timeout during EOD, considered
when all terminals are ready for EOD

jrnwait.during.eod=3 dcupdate JRN scheduler during EOD in seconds


idcwait.during.eod=2 dcupdate IDC scheduler during EOD in seconds
parsing.during.eod=true always should be true
eod.message=false true A dialog message appears to inform EOD
status for DCUpdate
false no dialog appears

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 24 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Setting for debug information


debug setting ..
#log.debug=false

debug setting for stand alone app logging..


#cmd.debug=true

Network settings for DCUpdate to run as standalone


dcupdate.hostname=localhost
dcupdate.port=7887

Customer specific settings


customer.parsers=2 3. Expense Parser,
4. Loan Parser,
5. Any new customer specific, please configure it for
its class and cache class

Hoc Import parameters settings ( Importing old Generations)

hocimport.class=com.ncr.mtx.dcupdate.hoc.HocImportServiceLauncher
import class, loaded by java runtime

hocimport.path=file://ASRSRV/Server/safe
HOCIDC & HOCJRN files path

hocimport.generation=002 generation number, must be same as extension of


HOC files

hocimport.idc.parsing=true parsing during hocimport. Recomemded this setting


to true

hocimport.loadingdelay=5 Delay for hoc import launch via webmaster during


EOD

hocimport.eod.timestamp= This is considered only if generation is other than


001, e.g. eod=20040404111101

NOTE : Above 6 properties are not considered during EOD, because 001 generation is default,
This is also true, when HocImport is launched by the GUI application

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 25 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Electronic Journal Configuration File


File: ej.properties

page.size: Determines the number of receipts/transactions


within a block.

page.memory: Determines the maximum number of pages held in


memory. Any attempt to exceed this limit fails
because of the replace strategy (A specified block
will be replaced by the one newly loaded).

page.strategy: Defines the strategy on how to insert or remove a


page from memory.

keys.strategy.class=com.ncr.asr.wm.feature.ej.client.KeysStrategy
keys.strategy.page.size=300
keys.strategy.page.memory=70

receipts.strategy.class=com.ncr.asr.wm.feature.ej.client.DefaultStrategy
receipts.strategy.page.size=100
receipts.strategy.page.memory=10
receipts.text.hightlight.enable=TRUE

details.strategy.class=com.ncr.asr.wm.feature.ej.client.DefaultStrategy
details.strategy.page.size=1
details.strategy.page.memory=100

statistics.strategy.class=com.ncr.asr.wm.feature.ej.client.StatisticsStrategy
statistics.strategy.page.size=1
statistics.strategy.page.memory=1

Note:
.class : A strategy class determines the behavior on how a quantity of data is being loaded to
memory.
.size : The number of elements within a page (e.g. Number of receipts)
.memory : The maximum number of pages within memory

Do not modify: panel.selection.model / panel.selection.view:

panel.selection.model=com.ncr.asr.wm.feature.ej.client.ModelSelection
panel.selection.view=com.ncr.asr.wm.feature.ej.client.EJViewSelection

Terminal restrictions
# ALL 001..899 Restricts the terminal selection to a certain set of
terminals. This option has no effect in case the user
has selected some terminals explicitly.
# POS 001..799
# TERMINALS 800..899

restriction.search.terminals=POS

Templates which are used by the printing framework.


template.receipt=EJDataLevel
template.detail=EJDataDetail

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 26 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Default sort order of the keys. If a field has no entry, then it will be ignored.
sort.default.<field_id>.priority : P(1) > P(2) > P(3) > ...... > P(n)
sort.default.<field_id>.direction : "ASC" for asceding order / "DSC" for descending order

sort.default.type.priority=
sort.default.type.direction=

sort.default.terminal.priority=3
sort.default.terminal.direction=ASC

sort.default.cashier.priority=
sort.default.cashier.direction=

sort.default.transaction.priority=2
sort.default.transaction.direction=DSC

sort.default.timestamp.priority=1
sort.default.timestamp.direction=DSC

sort.default.total.priority=
sort.default.total.direction=

Column header sorting


This is allowed by pressing on of the column headers. The direction will
toggle between ascending and descending order.

sort.column.enable=TRUE

INIT Properties
File: init.properties
path=./mtxwm/eodreports/;./mtxwm/gm/lan/;./mtxwm/gm/old/;./mtxwm/logs/;./mtxwm/tmp/;./mtxwm/saf
e/;./mtxwm/tmp/;

server.primary.timeout=5

server.backup.timeout=10 Defines the time in which the backup server has to perform its
INIT. Otherwise the INIT will be interrupted.

INIT will remove all files from the specified directories.

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 27 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Print Framework Coniguration file


File: print.properties
Report properties

The root path of the report framework


report.dir=report

The sub path which contains the archived reports


report.archive=archive

The sub path which contains the temporary reports


report.temp=temp

The sub path which contains the report properties


report.properties=properties

The root path of the print framework


printframe.dir=printframe

The sub path which contains the archived print reports


printframe.archive=archive

The sub path which contains the temporary print reports


printframe.temp=temp

The sub path which contains the print report properties


printframe.properties=properties

Specifies whether the toolbar should be shown in the view


pdf.toolbar=no

Commands with the actual path are added during installation


The following lines are for information only:

printcmd.pdf=C:\Program Files\Adobe\Acrobat 5.0\Reader\AcroRd32.exe /p /h <file>


printcmd.txt=C:\WINDOWS\system32\notepad.exe /p <file>

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 28 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Retention Coniguration file


File: retention.properties
Property file for the retention of data. The data will be kept for last 90 days
in case of IDC and JRN data
Add the table name by comma separated for the deletion.
The naming convention should be like retention.[app].table=[table1, table2, etc..]

DCUpdate rentention IDC tables.


retention.idc.duration=90
retention.idc.tables=EODIDC_A, EODIDC_B, EODIDC_D, EODIDC_E, EODIDC_G, EODIDC_I,
EODIDC_J, EODIDC_L, EODIDC_X,
EODIDC_Unknown, EODIDC_P, EODIDC_Q,
EODIDC_M, EODIDC_N, EODIDC_O, EODIDC_C,
EODIDC_V, EODIDC_R, EODIDC_H, EODIDC_F,
EODIDC_T, EODIDC_S, EODIDC_W, EODIDC,
TransactionParseTable, EODTransaction,
DailyIdcTransaction

DCUpdate rentention JRN tables.


retention.jrn.duration=90
retention.jrn.tables=EJRTransactionData, DailyEJRTransaction

MTX database retention tables


duration 0 means delete no data, -1 delete full tables
retention.mtx.duration=90
retention.mtx.tables=IDC, EJR

PTD tables for retention (These tables are from MTX database)
retention.ptd.duration=90
retention.ptd.tables=PLS, PLS_Article, PLS_MixMatch, PLS_Department, CLS, CLS_Promotion,
EODACT, EodDPT, EODLAN, EODREG,
EODCKR, EODCKRSELECTION, EODDATE,
SalesArticle, SalesDepartment, SalesMixMatch,
CustomerSales, CustomerPromotion

hmr retention properties, keep data for 4 weeks only SNYC with Division Properties

retention.hmr.tables=

MessageList
retention.hmr.duration=28
retention.hmr.archivedir=/mailbox/archive/

DB list for the retention, after deletion


retention.db.list=ASR_IDCBase, ASR_IDC1, ASR_JRN, MTX

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 29 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Special retention based on table and its criteria:


This is based upon EOD/Eoddate/EODID/CreationDate as criteria, otherwise table will be ignored
The configuration must be done like [retention].[dbname].[tablename]=[duration] use dbname like for
MTX database : mtx
IDC database : idc
JRN database : jrn

Example: If we want to keep Table 'YYY' data for '90' days and table 'XXX' for 40 days
retention.mtx.YYY=90
retention.mtx.XXX=40
Here any table can be configured for the deletion

This is the number of days for which the archived files must be kept from current date.
The relative path of the archived folder. The base path is taken from WebMaster

Re-indexing after number of days


retention.reindex.afterdays=7

This controls the retention via SQL statements. This is only way to generalize this approach.
The definition should be in the following pattern:
Note: For nested query, the where clause must take care, if any of the other tables are selected
and if they are filled with qualified names.

retention.withsql.[dbname].[tableName]=[full where clause starting with WHERE and more


condition(s) ]
dbname must be mtx / idc / jrn

This SQL part will be directly executed, so definition must be compilable & executable.
Inside the nested SQL, full qualified name should be given. eg: MTX..StoreMemo for table
StoreMemo

retention.withsql.mtx.StoreMemoDetail=WHERE MemoNumber IN (SELECT MemoNumber FROM


MTX..StoreMemo WHERE CONVERT(datetime,
substring(PostedDate, 1, 8), 112) <= getDate()-90)
retention.withsql.mtx.StoreMemo=WHERE CONVERT(datetime, substring(PostedDate, 1, 8), 112)
<= getDate()-90

Deletes the data from this table older than 1 year


Example of payroll tables clean up
#retention.withsql.mtx.PayrHour=WHERE PH_LOGNUM IN ( SELECT PM_LOGNUM FROM
MTX..PAYRMSTR WHERE PM_FinalDateTime <=
getDate()-400 )
#retention.withsql.mtx.PayrTime=WHERE PT_LOGNUM IN ( SELECT PM_LOGNUM FROM
MTX..PAYRMSTR WHERE PM_FinalDateTime <=
getDate()-400 )
#retention.withsql.mtx.PayrMstr=WHERE PM_FinalDateTime <= getDate()-400

Define following pattern for the deletion of directories that are kept temporary
retention.dir.[name]=path of directory
retention.dir.[name].keepdays=number of days for which the files are kept

DO NOT CHANGE THIS PROPERTY


retention.dir.tomcatlogs=../../logs/
retention.dir.tomcatlogs.keepdays=10

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 30 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

Configure the keep-days. Empty value means, this folder will be skipped
Examples:

retention.dir.reportarchive2=/report/archive/item_move
retention.dir.reportarchive2.keepdays=366

retention.dir.reportarchive3=/report/archive/elec_tenders
retention.dir.reportarchive3.keepdays=90

retention.dir.reportarchive4=/report/archive/item_update
retention.dir.reportarchive4.keepdays=366

retention.dir.reportarchive10=/report/archive/cashier_tot
retention.dir.reportarchive10.keepdays=90

retention.dir.reportarchive12=/report/archive/flashsales
retention.dir.reportarchive12.keepdays=

retention.dir.reportarchive13=/report/archive/exception
retention.dir.reportarchive13.keepdays=366

retention.dir.reportarchive14=/report/archive/sales
retention.dir.reportarchive14.keepdays=731

retention.dir.reportarchive15=/report/archive/hour_sales
retention.dir.reportarchive15.keepdays=366

retention.dir.reportarchive16=/report/archive/cashierbal
retention.dir.reportarchive16.keepdays=366

Delete the webmaster logs


These logs are normally cleared during End-of-Day, but in case of any un-deleted logs found older
than [keepdays] will be deleted.

retention.dir.webmasterlogs=/logs/
retention.dir.webmasterlogs.keepdays=10

Version Properties
File: version.properties
This property contains the information when the CD was built including the state of the software.

release=ASR 2.5
country=emea
customer=Custom NONE
distribution=stable
label=L041019_050100_ASR.25_Custom_NONE
builddate=041019_050100

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 31 - 32


WebMaster Configuration/Logs/Support AS@R 2.6 - Sec. Web 8

POS Cluster Monitor Configuration File


File: watch.properties
# Polltimer=5000 Time used by the applet to poll for update

The time an assigned terminal will be available to the corresponding applet is 15 minutes
WatchDog.init=900000

The time a communication will stay alive without new (update) requests is one minute
WatchDog=60000

***Copyright NCR GmbH AUGSBURG*** 5/9/2008 Page 32 - 32