User's Manual Part 3

PERFORMING DOWNLOADS
Direct Application Downloads
84 OMNI 3600 REFERENCE MANUAL
6
**VERIFYING FILES**
C
HECK CERTIFICATE
(FILENAME.CRT)
**A
UTHENTIC**
or else
--- FAILED ---
When the download is complete, the terminal restarts automatically. The
file authentication module on the receiving terminal begins to check for new
certificate files (*.crt) and signature files (*.p7s) included in the download.
These special files then process, one at a time; certificates are processed
first, then signature files.
When the file authentication module is invoked, the status display informs
you of the progress of the file authentication process. If file authentication
succeeds for a specific certificate, the “
AUTHENTIC” message displays
directly below the certificate filename. If file authentication fails for a
specific certificate, the “
FAILED” message displays for five seconds below
the filename and the terminal beeps three times, allowing you to note which
certificate failed to authenticate.
The authentication process then continues to the next certificate until all
new certificates are authenticated.
7 **VERIFYING FILES**
COMPARE SIGNATURE
FILENAME
.P7S
FILENAME
.OUT
**AUTHENTIC**
or else
--- FAILED ---
The file authentication module proceeds to authenticate any new signature
files downloaded with the OS files.
When the signature file authentication routine starts, the status display
shown at left informs you of the progress of the authentication process.
If file authentication succeeds for a specific signature file, the “
AUTHENTIC
message displays directly below the filename of the signature file. If file
authentication fails for a specific signature file, the “
FAILED” message
displays for five seconds below the filename and the terminal beeps three
times, allowing you to note which signature file failed to authenticate. The
authentication process then proceeds to the next signature file until all
signature files are validated.
When all new signature files are authenticated, the terminal restarts and
the application specified in the *GO variable or the default application in
Group 1, executes and starts running on the terminal.
8 (Application Prompt)
or
DOWNLOAD NEEDED
If the downloaded application successfully authenticated, the
corresponding application prompt or logo displays on restart.
The terminal can now process transactions.
Note: The message DOWNLOAD NEEDED appears if:
The *GO variable is not set.
*GO does not specify an application is present.
The application did not authenticate (invalid or missing *.p7s file).
The application uses shared libraries that are missing or were not
authenticated (invalid or missing *.p7s files).
Note: If one or more executables in the application fail to successfully
authenticate, the application may not run. If the application
attempts to access an unauthenticated executable or library, it
may crash. You must then repeat the direct download procedure
using the correct certificates and/or signature files.
Table 15 Direct Application Download Procedure (continued)
Step Display Action