user manual

372 BES Developer’s Guide
Executing iastool command-line tools from a script file
Options
The following table describes the options available when using the verify tool.
Example
The following example performs a developer level verification of the JAR file
soap-client.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 373
■
“Passing a file to the iastool utility” on page 373
Option Description
-src <srcjar> Specifies the JAR file that you want to
verify. The full or relative path to the file
must be specified. There is no default.
-role <DEVELOPER|ASSEMBLER|DEPLOYER> Specifies the level of error checking to
perform:
■ DEVELOPER
■ ASSEMBLER
■ DEPLOYER (default)
For details, see the role descriptions
above.
-nowarn Specifies that the tool should only report
errors that preclude deployment and not
report warnings.
-strict Specifies that the tool should report the
most minute inconsistencies, many of
which do not affect the overall integrity of
the application.
-classpath <classpath> 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 (;).