Specifications

Configuration 2- 13
• Dates can be used in transaction IDs to help ensure unique IDs. If they are used, they are expressed as
an 8-digit number; this is set by the TransactionIDBarcodeDateFormat property in the domain.properties
file. The only valid values for this property are no value and yyyyMMdd . The date format does not vary
from one locale to another.
• You can set the transaction sequence start number in the database.
• When you enter a transaction ID manually, the trailing date is optional.
Changing Transaction ID Lengths
To change ID lengths, edit the values in the Transaction ID section of the \360store\domain\config\
domain.properties
file in your source code control system. See “Understanding Transaction IDs” on
page 2-12 for more information on what these properties mean.
# Transaction ID
TransactionIDStoreIDLength=5
TransactionIDWorkstationIDLength=3
TransactionIDSequenceNumberLength=4
#TransactionIDBarcodeDateFormat=yyyyMMdd
TransactionIDBarcodeDateFormat=
TransactionIDSequenceNumberSkipZero=false
TransactionIDSequenceNumberMaximum=9999
Configuring RMI Time-outs
You can configure remote method invocation (RMI) time-outs at two levels:
• The JVM level (Linux installs only)
• The level of managers and technicians
If you are performing a Linux installation, configure the JVM as described in “Setting the RMI Time-out
for the JVM Under Linux,” below. If you determine that RMI connections are timing out, you can use
one of the other procedures in this section, “Setting the RMI Time-out for All Manager and Technician
Calls” on page 2-14 or “Setting the RMI Time-out for a Specific Technician” on page 2-14.