starjavapos_win32-linux-macosx
---------------------------------------
StarJavaPOS - Java Web Start Usage
Description:
Java Web Start technology is now being shipped along
with the standard Java Runtime Environment and allows
for the easy creation of distributed applications.
Java Web Start applications are deployed to a standard
web server (i.e. Apache server) in the form of a
collection of JAR files, and a JNLP application
description file. Clients launch the application by
pointing their web browsers to the JNLP file on the
server, which then initiates its download and in turn
causes the startup of the Java Web Start application.
This readme describes the method of deploying an
an application that uses StarJavaPOS via the Java
Web Start mechanism.
Application Structure
A Java Web Start application that makes use of
StarJavaPOS must have the following minimum structure.
Rooted at http://www.your-server.com/some-path/
your-application.jnlp
jpos17-controls.jar
jcl.jar
starjavapos.jar
xercesImpl.jar
xml-apis.jar
javapos-registry.jar
star-linux-libs.jar
star-windows-libs.jar
star-mac-libs.jar
This distribution contains a sample JNLP (described
below), and all of the above listed JAR files (except
your-application.jar - you make that). The files
jpos17-controls.jar, jcl.jar, starjavapos.jar,
xercesImpl.jar, and xml-apis.jar are contained in this
distribution's root directory. The other JAR files
listed above are contained in this distribution's
java-web-start directory.
JNLP Application Description
Java Web Start applications are described in XML
by the JNLP format. A JNLP file contains all the
information needed to launch, download, and execute
the application.
This distribution contains the starjavapos.jnlp file.
This file describes the Java Web Start usage of the
POSPrinterExcerciser application that is embedded into
starjavapos.jar.
Please open the starjavapos.jnlp file in a text editor
and review its structure. Comments are included in this
file which should be sufficient to allow for you to
modify it for use with your own application.
JAR Signing
Java Web Start applications, by default, run within
the Java Runtime Environment's sandbox. This prevents
applications from accessing operations which have
the potential to cause harm.
StarJavaPOS requires access to your computer's
communications ports (i.e. serial port, parallel port,
USB port). Because of this, applications that use
StarJavaPOS via the Java Web Start mechanism must have
unrestricted access to the local machine.
Java Web Start allows applications to have unrestricted
access to the local machine if:
1. All JAR files comprising that application are
signed (process described below)
2. The <security><all-permissions/></security> tag
is contained in the application's JNLP file
(this tag is present in starjavapos.jnlp)
The process of signing JAR files allows the Java Runtime
Environment to verify that the JAR file has come from
an original source (you and your organization) and also
that the JAR file has not been modified since having been
signed. These two properties make it possible to safely
distribute applications via the Internet and Java Web Start.
To sign JAR files, the JDK contains two tools, keytool and
jarsigner. The keytool utility is used to generate
encrypted keys and key issuing requests. Once a key is
available, it can be used to sign JAR files by means of the
jarsigner application.
Keys can either be self-generated or can be prepared by a
well-known third-party such as Verasign or the Thawte Group.
Self-signed keys are convienent for testing during the
development phase of a project, but are not suitable for
actual deployments. When deploying a real application,
please obtain a key from Verasign, the Thawte Group, or
another such party.
The following steps can be used to self-sign your
application's JAR files.
Step 1 - make a keystore file:
keytool -genkey -keystore myKeyStoreFile -alias myname
Step 2 - make a self-signing certificate
keytool -selfcert -alias myname -keystore myKeyStoreFile
Step 3 - sign each JAR file (repeat this step for all JARs)
jarsigner -keystore myKeyStoreFile some-component.jar myname
Deployment
Once you have created your JNLP file and signed ALL JAR
files, you can deploy your application. This is as simple
as copying the JNLP file and all JAR files to your server
at the location specified in the JNLP file's codebase
attribute.
Modifying javapos-registry.jar
The JavaPOS JCL system reads the jpos.xml file for
system configuration information. In the Java Web Start
deployment scenario, the jpos.xml file is embedded into
the root directory of the javapos-registry.jar file.
If you need to modify your device's configuration, then
remake the javapos-registry.jar file by doing this:
jar -cf javapos-registry.jar jpos.xml
If you remake the javapos-registry.jar file, remember to
sign it again (with the same key) as described in the
process above.
Support Contact:
Please contact me, Albert Kennis at:
albert@star-m.jp
Provided to you by: AK INNOVATION
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.