jmk
script with the command
make jmk
.
jmk
. Emacs users
should issue this command using M-x compile
.
simpserv.jar
, sax.jar
,
xp.jar
, simpserv.props
, and
simpserv.sh
. The servinstall.sh
script does
the copy for you.
simpserv.props
into
simpserv.properties
and use this file for local
modifications. The file contains comments suggesting some of the
available options.
passwords.properties
.
_profile.xml
andone m
<user>_acl.xml
, where <user> is the name of
the account. Make these the default by renaming them to
notifier_profile.xml
and notifier_acl.xml
respectively. We found that users expect to see some empty groups
when they first log into the system. The file
notifier_profile.xml
can be used to provide the initial
set of empty groups.
simp.jar
, sax.jar
, xp.jar
,
simp.props
, makefile.jmk
,
simp/simplauncher.jar
, simp/simp.sh
, and
simp/install.sh
. The webinstall.sh
script
does the copy for you.
simp.props
into
simp.properties
and use this file for local
modifications. Change the simp.path
line to a semicolon
separated list of URIs that access the files:
simp.jar
, sax.jar
, and
xp.jar
.
simplauncher.zip
with the command make
or
jmk
.
index.html
and text.css
and edit them to fit your needs.
In our environment, we trust the web server that distributes JAR files. In addition, we assume clients connect to the web server via a network that permits rapid client downloads when the cached client is out of date.
You can build a system that only uses JAR files installed on
the client. When creating simplauncher.zip
, remove the
simp.path
line in simp.properties
and add
simp.jar
, sax.jar
, and xp.jar
to simplauncher.zip
. Start the launcher with all the
needed JAR files in the Java class path. For example, a Unix version
of the command to start the launcher follows.
java -cp simp.jar:xp.jar:sax.jar \ org.mitre.simp.launcher.SimpLauncher