web server - Borland Technical Publications

Executing iastool command-line tools from a script file
Options
The following table describes the options available when using the verify tool.
Option
-src
-role
-nowarn
-strict
-classpath
Description
Specifies the JAR file (or the directory of an
expanded JAR) that you want to verify. The full or
relative path to the file must be specified. There is
no default.
Specifies the level of error checking to perform:
■
■
DEVELOPER
ASSEMBLER
■ DEPLOYER (default)
For details, see the role descriptions above.
Specifies that the tool should only report errors that
preclude deployment and not report warnings.
Specifies that the tool should report the most
minute inconsistencies, many of which do not
affect the overall integrity of the application.
Specifies the search path for application classes
and resources. To enter more than one directory,
ZIP, or JAR file entry, separate each entry with a
semicolon (;).
Example
The following example performs a developer level verification of the JAR file soapclient.jar
located in the c:\examples\soap directory:
-verify -src c:\examples\soap\soap-client.jar -role DEVELOPER
Executing iastool command-line tools from a script file
Several iastool utility tools require that you supply login information (realm, username,
and password). You may, however, want to run iastool commands from a script file,
but doing so would expose the realm, username, password information to anyone who
has access to the script file. There are two methods you can use to protect this
information:
■
“Piping a file to the iastool utility” on page 321
■
“Passing a file to the iastool utility” on page 322
Piping a file to the iastool utility
The following example shows how to ping a hub named east1 by piping the file
mylogin.txt (located in the default Borland Deployment Platform installation directory)
to the iastool utility:
iastool -ping -hub east1 < c:\BES\mylogin.txt
where the file mylogin.txt contains three lines that correspond to what you would enter
for the realm, username, and password:
2
username
password
322 BES Developer’s Guide