Adobe 38000382 JRun Guide - Page 91

JRun executables, The JRun executables provide the following benefits

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 91 highlights

JRun executables JRun includes executable files in the jrun_root/bin directory that point to executable JAR files in the jrun_root/lib directory. These executable files replace batch files and scripts that used to launch JRun processes. The JRun executables provide the following benefits: • Ease of use You do not have to use the jar command to launch the executable JAR files from the command line. Instead, you enter only the name of the JAR file. • Descriptive names The process names reflect the name of the executable. Formerly, the batch files resultant process were all named java or javaw. • Centralized JVM settings The executables use the jvm.config file in the jrun_root/bin directory for the virtual machine settings. Use this file to change the java.args, classpath, or other JVM-related settings for the JRun executables. • Standard access method Add the bin directory to your system path so that you can access all JRun tools. The following table describes the executable JAR files in the jrun_root/bin directory: JAR file name GUI sniffer.jar Yes jrun.jar Yes jrunwizard.jar Yes jrun-wizardinstaller.jar Yes wsconfig.jar Yes xmlscript.jar No Description Starts the TCPMonitor utility. For more information on using the TCPMonitor utility with JRun, see JRun Programmer's Guide. The TCPMonitor is an open-source utility that is part of the Axis project. For source code and full TCPMonitor documentation, see http://xml.apache.org/axis/index.html. If you launch this file without any arguments, the executable starts the JRun Launcher utility that lets you start, stop, and restart JRun servers. For more information on using the jrun tool, see "Using the jrun command" on page 74. Starts the JRun Enterprise Deployment Wizard that automates the deployment of EJBs. For more information on using the JRun Enterprise Deployment Wizard, see the online help. Installs the JRun Enterprise Deployment Wizard. For more information on using the JRun Enterprise Deployment Wizard, see the online help. Starts the Web Server Configuration tool that connects JRun to external web servers. XPath-based XML scripting utility that lets you execute a subset of XPath statements on XML files. For more information on using the xmlscript utility, see "Using XMLScript" on page 75. JRun executables 77

  • 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
JRun executables
77
JRun executables
JRun includes executable files in the
jrun_root
/bin directory that point to executable JAR
files in the
jrun_root
/lib directory. These executable files replace batch files and scripts
that used to launch JRun processes.
The JRun executables provide the following benefits:
•
Ease of use
You do not have to use the jar command to launch the executable JAR
files from the command line. Instead, you enter only the name of the JAR file.
•
Descriptive names
The process names reflect the name of the executable.
Formerly, the batch files resultant process were all named java or javaw.
•
Centralized JVM settings
The executables use the jvm.config file in the
jrun_root
/bin directory for the virtual machine settings. Use this file to change the
java.args, classpath, or other JVM-related settings for the JRun executables.
•
Standard access method
Add the bin directory to your system path so that you
can access all JRun tools.
The following table describes the executable JAR files in the
jrun_root
/bin directory:
JAR file name
GUI
Description
sniffer.jar
Yes
Starts the TCPMonitor utility.
For more information on using the TCPMonitor utility with
JRun, see
JRun Programmer’s Guide
.
The TCPMonitor is an open-source utility that is part of the
Axis project. For source code and full TCPMonitor
jrun.jar
Yes
If you launch this file without any arguments, the executable
starts the JRun Launcher utility that lets you start, stop, and
restart JRun servers.
For more information on using the jrun tool, see
“Using the
jrun command” on page 74
.
jrunwizard.jar
Yes
Starts the JRun Enterprise Deployment Wizard that
automates the deployment of EJBs.
For more information on using the JRun Enterprise
Deployment Wizard, see the online help.
jrun-wizardinstaller.jar
Yes
Installs the JRun Enterprise Deployment Wizard.
For more information on using the JRun Enterprise
Deployment Wizard, see the online help.
wsconfig.jar
Yes
Starts the Web Server Configuration tool that connects
JRun to external web servers.
xmlscript.jar
No
XPath-based XML scripting utility that lets you execute a
subset of XPath statements on XML files.
For more information on using the xmlscript utility, see
“Using XMLScript” on page 75
.