The JMSL Numerical Library has a Java-based install. It requires that J2SE 1.4 or later be already installed.
Installation can be done in either command line mode or in GUI mode.
If Java is installed and autorun is active, then GUI mode installation
should start automatically.
If not, then
cd to the root directory of the installation CD and run
java -jar setup.jar
or, for command line mode,
java -jar setup.jar -cli
In both cases you will be prompted for input. The following items are required:
jmsl4.0/setup.jarcan be used to update the license manager configuration. See the License Manager documentation for instructions on configuring the license manager.
In the installation directory
jmsl4.0/libcontains the JAR files
jmsl.jar, contains the JMSL classes.
gallery.jar, and its auxillary file
sp500hst.jar, contain the JMSL Demo Gallery.
swing_look_and_feel_icons-1_0.jarcontains the Java Look and Feel Graphics Repository.
crimson.jarcontains the Apache Crimson 1.1.3 XML parser. This file is required only if the Chart XML features are being used with J2SE 1.3. Later versions of J2SE include an XML parser and so crimson.jar is not required.
jai_core.jarimplement the Java Advanced Imaging API.
servlet.jarimplements the Java Servlet API.
jmsl4.0/manualcontains the documentation. The documentation consists of Adobe's Acrobat Reader.
quickstartdirectory contains sample JMSL applications.
licensedirectory contains FLEXlm license manager files.
The look of charts depends on the fonts used. The fonts used by Java are installation dependent. Most JVM have a font.properties file that determines the fonts used. See here for more details.
where install is the directory in which JMSL has been installed, will print version information, assuming that
java -Dcom.imsl.license.path=license -jar install
javais in the execution path and license points to the license file. The license path argument can be omitted if the
license.datfile is in the current directory or if a license server is running on the local machine.
JMSL is a pure class library that has no special installation requirements
beyond those of any JAR
file. The requirement is that the Java Virtual Machine (JVM) be able to find
A few JMSL classes require additional JAR files. This section summarizes the
most important ways in which a JVM can find JAR files.
The CLASSPATH is a list of directories (containing class files) and JAR file
names. The entries in the CLASSPATH are separated by semicolons (";")
on Windows and by colons (":") on most other systems. Note that it
is not enough to include the directory containing the JAR files in the
each JAR file must be explicitly listed in the
The preferred method of setting the
CLASSPATH is as an argument to the
program with the
-classpath option . The command
line classpath overrides the environment classpath. See the
documentation for Windows,
for more details.
The classpath can also be set as an environment variable.
JAR files can be installed within a JDK or JRE as a
Extension and are loaded without being specified in the CLASSPATH.
To make JMSL an installed extension, copy
jmsl.jar into the
directory of the Java Runtime Environment.
Sometimes Java is installed several times on the same machine. Be careful that the extension is copied into the JRE that is being used.
In most web servers that support servlets, JAR files can be located in a web
WEB-INF/lib directory. There is usually no need to
adjust the web server's classpath to find this directory.
A Java application can define its own ClassLoader. This allows the application to use its own mechanism to locate and load classes.