Table of Contents
Advertisement
Using the migration tool
JRun provides a migration tool for moving JRun 3.x servers and configuration settings to
JRun 4. Although you can deploy JRun 3.x J2EE modules in JRun 4 without using the
migration tool, the tool exports many of the settings on which modules depend.
You can invoke the migration tool from the command line in the jrun_root/bin directory.
The migrate tool uses the following command-line syntax:
After successfully running the migration tool, open the jrun_root/migration.html file in a
web browser. The migration.html page is a migration activity report that indicates what
the tool successfully migrated and what it could not migrate.
For more information on using the migration tool, see Installing JRun.
Using Base64 encoder
The Base64 utility takes a string returns its base 64 encoded value. This encoding is used
by web browsers when authenticating users with BASIC authentication. It is not a secure
encoding mechanism, but is widely used for obfuscating nonsensitive data.
The Base64 utility is in the jrunx.util package. It uses the following syntax:
%> java [-classpath classpath] jrunx.util.Base64 string
For example:
%>java -classpath .;c:/jrun4/lib/jrun.jar jrunx.util.Base64 danger
This example returns the following to the standard output:
Input
Encoded = 'ZGFuZ2Vy'
Decoded = 'danger'
The
with an instance of the class. For more information, see the JRun Javadocs.
Using the Web Server Configuration tool
You use the Web Server Configuration tool to connect JRun to your external web server.
The Web Server Configuration tool is implemented in the executable JAR file
wsconfig.jar. It is in the jrunx.connectorinstaller package.
The Web Server Configuration tool uses the following syntax:
%> java -jar jrun_root/lib/wsconfig.jar [options]
To use a property file for options, use the following syntax:
%> java -jar jrun_root/lib/wsconfig.jar -f property-file
The property file contains tags that are equivalents of command-line options. This is
commonly used by OEMs and ISVs who do not want to expose JRun to their customers.
For more information on using the Web Server Configuration tool command-line
options, see Installing JRun.
%>
migration jrun3.x_root
where jrun3.x_root is the root directory of a JRun 3.1 installation.
= 'danger'
class also provides public
Base64
and
methods that you can invoke
encode
decode
Command-line tools
73
Advertisement
Table of Contents
