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 documentation, see http://xml.apache.org/axis/index.html.

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".

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.

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".

java2wsdl.jar

No

Generates a WSDL document for a Java interface or class that you use as the basis for a web service.

For more information on using the java2wsdl utility, see "Using Java2WSDL".

wsdl2java.jar

No

Generates web service proxy and skeleton code based on information in a web service WSDL document.

For more information on using the wsdl2java utility, see "Using WSDL2Java".

migrate.jar

No

Migrates JRun 3.x applications and settings into JRun 4.

For more information on using the migrate utility, see "Using the migration tool".

jspc.jar

No

Compiles Java source code into bytecode.

For more information on using the JSPC command-line tool, see "Using the JSPC tool".

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 documentation, see http://xml.apache.org/axis/index.html.
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".
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.
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".
java2wsdl.jar	No	Generates a WSDL document for a Java interface or class that you use as the basis for a web service. For more information on using the java2wsdl utility, see "Using Java2WSDL".
wsdl2java.jar	No	Generates web service proxy and skeleton code based on information in a web service WSDL document. For more information on using the wsdl2java utility, see "Using WSDL2Java".
migrate.jar	No	Migrates JRun 3.x applications and settings into JRun 4. For more information on using the migrate utility, see "Using the migration tool".
jspc.jar	No	Compiles Java source code into bytecode. For more information on using the JSPC command-line tool, see "Using the JSPC tool".

Executable JAR files contain the Main-Class parameter in the manifest file. This parameter points the JVM to your JAR file's main class and it's main method.

Depending on the function of the executable JAR file, you can launch them in different ways. The following table describes how you can invoke these tools:

Type of JAR file

To invoke

Executable JAR files that launch GUIs

Double-click the desktop icon of the JAR file.

or

Double-click the JAR file's executable equivalent in the jrun_root/bin directory.

For each executable JAR file, there is a file with the same name in the jrun_root\bin directory.

In a Windows environment, these files are *.exe files, where the * is the name of the JAR file (for example, sniffer.exe, launcher.exe, and jrunwizard.exe).

On UNIX, these files are binary files with the same name as the JAR file (minus the .jar extension).

You can rename any one of these EXE or binary files to the name of any executable JAR file to launch that JAR file.

All executable JAR files

Use the java command on the command line; for example:
%> java -jar jar_file

Type of JAR file	To invoke
Executable JAR files that launch GUIs	Double-click the desktop icon of the JAR file. or Double-click the JAR file's executable equivalent in the jrun_root/bin directory. For each executable JAR file, there is a file with the same name in the jrun_root\bin directory. In a Windows environment, these files are .exe files, where the is the name of the JAR file (for example, sniffer.exe, launcher.exe, and jrunwizard.exe). On UNIX, these files are binary files with the same name as the JAR file (minus the .jar extension). You can rename any one of these EXE or binary files to the name of any executable JAR file to launch that JAR file.
All executable JAR files	Use the java command on the command line; for example: %> java -jar jar_file

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/jrun/4/JRun_SDK_Guide/apis5.htm

JRun SDK Guide
JRun APIs