web server - Borland Technical Publications

Using the iastool command-line tools
Option
-args
-javac_args
Description
Specifies any arguments that are needed by the file. For details,
see VisiBroker for Java Developer’s Guide.
Specifies any Java compiler arguments that are needed by the
JAR file.
Example
The following example shows how to generate a manually deployable module client
JAR file from each of the EJB JAR files: proj1.jar, proj2.jar, and proj3.jar into the
EJB JAR myproj.jar.
iastool -genclient -jars proj1.jar,proj2.jar,proj3.jar -target myproj.jar
gendeployable
Use this tool to create a manually deployable server-side module. Server-side
deployable JAR files are archives (EAR, WAR, or JAR beans only) that have been
compiled to resolve all external code references by using stubs and are, therefore,
ready for deployment.
For example, first use gendeployable to create the server-side deployable JAR file on a
local machine, then use the deploy tool to copy and load it on the hub. The hub is
advised of the presence of the new JAR file and loads it automatically. Using the
command-line tools lets you script a creation and deployment to several servers quite
simply. You can also manually copy the server-side deployable JAR file to the correct
location on each hub, but this requires restarting each hub to cause it to be recognized
and loaded.
Syntax
-gendeployable -src -target [-cp ]
[-args ] [-javac_args ]
Default Output
The default output returns nothing to standard output (stdout).
Options
The following table describes the options available when using the gendeployable tool.
Option
-src
-target
-cp
-args
-javac_args
Description
Specifies the JAR file (or the directory of an expanded JAR) that
you want to use to generate a new deployable JAR file. The full or
relative path to the JAR file must be specified. There is no default.
Specifies the deployable JAR files to be generated on the
localhost. The full or relative path to the JAR files must be
specified. There is no default.
Specifies the classpath containing the class dependencies of the
JAR file for which you want to generate a client JAR file. The
default is none.
Specifies any arguments that are needed by the file. For details,
see VisiBroker for Java Developer’s Guide.
Specifies any Java compiler arguments that are needed by the JAR
file.
Example
The following example shows how to generate a server-side deployable module JAR
file for proj1.jar into the file server-side.jar.
300 BES Developer’s Guide