Adobe 38000382 JRun Guide - Page 87

Using the migration tool, Using Base64 encoder, Using the Web Server Configuration tool

Get Adobe 38000382 - Macromedia JRun - Mac PDF manuals and user guides
UPC - 718659575946
View all Adobe 38000382 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 87 highlights

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: %> migration jrun3.x_root where jrun3.x_root is the root directory of a JRun 3.1 installation. 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 = 'danger' Encoded = 'ZGFuZ2Vy' Decoded = 'danger' The Base64 class also provides public encode and decode methods that you can invoke 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. Command-line tools 73

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
Command-line tools
73
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:
%>
migration
jrun3.x_root
where
jrun3.x_root
is the root directory of a JRun 3.1 installation.
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
= 'danger'
Encoded = 'ZGFuZ2Vy'
Decoded = 'danger'
The
Base64
class also provides public
encode
and
decode
methods that you can invoke
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
.