How to Use TiniHttpServer on Any Java System

Return to Index

As of version 0.6, TiniHttpServer can be used on any Java system. You can now develop and debug servlets on your PC, then deploy them to your TINI once you have them working. This greatly reduces the build/debug cycle time. With the 1-Wire API for Java and javax.comm, you can develop servlets that use serial and 1-wire resources on your favorite Java platform using you favorite development tools. These servlets can then be deployed to TINI with no source code modifications. This is starting to realize the write-once-run-anywhere promise of Java. Of course, this only works if your servlets do not need any TINI-specific functionality and do not use any Java functionality not available on TINI.

Make sure that you have all of the required items listed in the Using TiniHttpServer on non-TINI Platforms section of the System Requirements page.
Before running TiniHttpServer on a pure Java system, it must be built using the command ant pure. See How to Use Your Servlets with TiniHttpServer for more information on the build environment. Be sure to set the pure.onewire.jar property in build.properties correctly.
Edit the file run.bat (Windows) or run.sh (UNIX)
- Set the SERVLET_JAR variable to the full pathname of the JSDK 2.2 servlet.jar file.
- Set the ONEWIRE_JAR variable to the full pathname of the OneWireAPI.jar.
Use one of the following commands to run TiniHttpServer:

Windows: run

UNIX: run.sh

These scripts start TiniHttpServer using the local_server.properties file. See Configuring TiniHttpServer with Properties Files for more information. The local_server.properties file contains these properties:
- Server listens on port 8080. Access it using http://localhost:8080/.
- Document root is tini/docs.
- Server output is directed to the file tini/logs/server.log.
- The transfer log is directed to tini/logs/transfer.log.
- The servlet properties file is tini/etc/servlets.props.
See the local_server.properties file for full details.

Note: TiniServlet uses TINI-specific functionality. As a result, TiniServlet will not be available on non-TINI systems.