Factory Configuration
FILES
In production a number of files are initially loaded onto the JNIOR and
specifically into the /flash file area. The file system in general is
stored within a battery-backed Static Random Access Memory (SRAM). There
are two exceptions to this. One is the /flash folder and all of its contents.
This information is stored within a Flash Memory component. This is not
dependent on the battery and therefore considered a bit more permanent. The
other exception is the /temp area which is temporary and therefore stored
in the larger general-purpose Heap memory. There is also the /etc folder
which is read-only and contains the runtime. It is actually in processor ROM.
On a JNIOR you may observe files with the
DIR or
LS command. The files that
you find outside of the /flash folder are actually generated by the JNIOR.
These are typically log files. The /flash folder is pre-loaded in production
and may contain the following files:
/flash/cksums.bat
-----------------
This is a batch program that creates a
CKSUMS command for use at the
command line. This reports checksum and digest calculations for
the content of files. This is useful in validating content against the
published checksum or digest information calculated from the original
files.
This is a good example of how to create a custom command using the
PHP-like scripting language that is unique to JANOS.
/flash/ftp.jar
--------------
The JNIOR supports a built-in File Transfer Protocol (FTP) server
allowing you to upload and download files from the unit using FTP from
a PC for instance. The ftp.jar application program allows you to use
FTP from the command line as a client. Using this command on the JNIOR
you can go to remote FTP servers and get or put files. This might be
useful in pulling (or pushing) a file from one JNIOR to another.
/flash/JBakup.jar
-----------------
The JBakup utility extends logging for periods much longer than can be
accommodated by the standard .LOG file and its .LOG.BAK backup. This
program can be run in the background and on the quarter hour it will
detect newly updated .LOG.BAK files and combine their content into a
compressed library stored in the /flash/baks folder. Depending on activity
levels this could preserve log data for many months.
/flash/jnior.ini
----------------
This is generated by the JNIOR once it is up and running. The jnior.ini
file is a backup for the
Registry . In general one should not edit or
overwrite this file.
/flash/manifest.json
--------------------
The
MANIFEST -U command creates a reference point for the file system.
This essentially is a database of checksum/digest information for all
of the files. In production a target version of this file is uploaded
and MANIFEST is used to verify the file set. This detects any missing
files or any upload errors even if only a single bit is in error. It is
employed initially as a quality control function.
/flash/manpages.zip
-------------------
This contains the extended Help information available with the
HELP
command. Its content is what generates this book.
/flash/ModbusServer.jar
-----------------------
MODBUS is a protocol that may be used to communicate with the JNIOR.
If needed this protocol can be enabled through the WebUI on the
Configuration tab Applications page. It can also be started by setting
a Registry /Run key.
/flash/SerialControl.jar
------------------------
Serial Control Plus runs on the JNIOR and allows the user to interact with
the JNIOR I/O via the serial port or the Ethernet port using simple
ASCII commands. The user can control the relay outputs (on, off, pulse)
and receive the status of the digital inputs and relay outputs (on, off)
along with counters via the serial port or Ethernet port. The application
is enabled using the WebUI on the Configuration tab Applications page.
/flash/SerialEthernet.jar
-------------------------
Serial-to-Ethernet acts as a converter between a Serial device connected
to the JNIOR and a remote application communicating with the JNIOR. The
connection made using Serial-to-Ethernet is bi-directional allowing
information to travel both ways. The application is enabled using the
WebUI on the Configuration tab Applications page.
/flash/SlaveService.jar
-----------------------
The Slaving service when running can be configured to cause an input or
output on one JNIOR to reflect the input or output on another. This can
be used to extend a remote signal through the network. The application
is enabled using the WebUI on the Configuration tab Applications page.
/flash/SNMP.jar
---------------
The Simple Network Management Protocol (SNMP) can be enabled through the
WebUI on the Configuration tab Applications page. SNMP can be used to
manage the JNIOR remotely. Variables can be defined which will be monitored
or controlled in a manner consistent with other SNMP enabled devices.
/flash/www/config.zip
---------------------
This contains the entire WebUI (default JNIOR website) which is served
directly from this one file. This forms a virtual /config folder for
the WebServer.
/flash/www/Bundled.zip
----------------------
This contains the configuration pages for the Slaving application and as
well as that needed by the other applications that may be activated
on the JNIOR.
To find out more about these applications and others available for the JNIOR
visit the INTEG website or contact Technical Support for an overview.
SEE ALSO
HELP Topics:
DIR,
CKSUMS,
REGISTRY,
MANIFEST
[/flash/manpages/manpages.hlp:909]