Packinglist.xml is a file that describes an application within
the HXP file.
PACKING LIST FORMAT.
< XML Header >
< Application
Title = " … "
UniqueName="..."
Version
= " … "
Release Date = " … "
Icon = "File"
Company = " … "
DestinationDir = " … "
Main = "MainFile "
MainAttributes = "…"
DependencyList="..."
<Files>
< File
URL = " …"
Size = " …"
MD5 = " ... "
SHA1 = " ... "
Date
= " …"
Compression = "Y" or "N"
Uncompress ="Y" or "N"
UserName = "…."
Password = "…."
>
</File>
…
<File
…/>
</Files>
<StartUp
CommandLine = " … ">
</StartUp>
</Application>
TAGS AND ATTRIBUTES
< Application> Tag attributes:
Title: This is the application Title. Also this is the name associated to the application in the Shell.
UniqueName:The Application Name is used by Application Manager to compare names in the dependency list. An application may not have a dependency list but its name may be listed in another application’s dependency list. The Application Name is used by Application Manager to uniquely identify an application. No two applications will have the same name. This field can contain maximum 128 characters.
Version:
This is the application version number. This number should be displayed during
uploading. This is information for the User/Help desk.
ReleaseDate:
This is the application release date. This is information for the User/Help
desk. The format should be according to ISO 8601 standard.
Icon:
This is an icon file name. This icon file is used in Term Master and
Terminal Shell to depict the application. The attribute value is a file name
described as one of the File Tag.
Company:
This is the company name of the application. This name will be used as a top
destination directory that is located above the Application destination
directory. It can also be used together with the Company Program Key for
secure downloading.
DestinationDir:
This is the destination application directory that should be under the company
directory (Second level directory).
Main: Program file name to run the application. The Shell calls this file.
MainAttr: This field contains the attributes for the current application. It can contain the following attributes:
|
Attribute |
Value |
Description |
|
Desktop Application |
0 |
The application will appear on the main desktop screen (Shell). The icon will be used to depict the application.
|
|
No Desktop Application |
1 |
The application will be downloaded and used for other applications. It will not appear on the desktop screen.
|
|
Auto-Launch Desktop Application |
2 |
Desktop application is automatically launched after a successfull download.
|
|
Auto-Launch Application |
3 |
This attribute describes the applications that need to be launched in memory automatically after being successfully downloaded by the Application Manager. |
|
System application |
4 |
Application Manager program |
DependencyList: The Dependency List is used by Application Manager to start the listed application (and any applications that the listed applications are dependent on) before starting the target application. This field can contain 512 characters maximum.
<Files> Tag attributes:
File: This Tag describes a file that belongs to the Application. This Tag contains a list of attributes distinguishing the file.
URL: Full (Absolute) URL to the resource file (file can be compressed if compression Tag is "Y"). Example: http://manifests/[TerminalID]/somefile.ext Currently domain names present in the URL are not accepted. Request Manager will never serve requests for Absolute Path Files (this may create a severe security risk). Request Manager will provide the root directory for file storage and all application files will be located in that directory sub-tree. If a request for a file from the root of the hard drive were allowed, a path to password files would became clear. Therefore, no servers have such a possibility by default (IIS = wwwroot, ftproot, etc.). Access to Term-Master will is protected by a secure certificate, but when one certificate for one POS is discredited, another layer of protection will keep all system stable and safe. It is applied and is up to the user to get files from another server, either FTP or HTTP, but it will be done through another server with it's own security.
MD5: 128-bit message digest value of the file. This attribute is used by the Terminal to compare to what is already present in the Terminal File System. If this value differs then this file will be downloaded and replace the one that currently is present in the File System. This parameter works together with the size to check if it is necessary to update this file.
SHA1: Another digest value of the file.
Size: File size in bytes. This attribute is used by the Terminal to compare to what is already present in the File System. It is used together with the Checksum and Date to check if it is necessary to update this file.
Date: Date of the file in YYYYMMDD format.
Compression: File is sent in compressed format ("Y" or "N")
Uncompress: File is to be stored uncompressed in terminal file system ("Y" or "N")
UserName: This field is used for FTP server connections as the user name to login to the server.
Password:
This field is used for FTP server connections as the password to login to the
server.
<StartUp> Tag attributes:
Command Line: This is the command line executed when the Application runs.