sun.com | docs.sun.com |  | How To Buy | My Sun | Worldwide Sites |

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Application Server Utility | verifier(1M)

- NAME
- SYNOPSIS
- DESCRIPTION
- OPTIONS
- EXAMPLES
- SEE ALSO

## NAME

| verifier - validates the J2EE Deployment Descriptors against application server DTDs

## SYNOPSIS

| `verifier` [-v] [-d destination_directory] [-r [a|w|f] ] `jar_filename`

## DESCRIPTION

| Use the `verifier` utility to validate the J2EE deployment descriptors and the Application Server specific deployment descriptors. If the application is not J2EE compliant, an error message is printed. When you run the `verifier` utility, two results files are created in XML and TXT format. The location where the files are created can be configured using the -d option. The directory specified as the destination directory for result files should exist. If no directory is specified, the result files are created in the current directory. Result files are named as jar_filename`_verified.xml` and jar_filename`_verified.txt` The XML file has various sections that are dynamically generated depending on what kind of application or module is being verified. The root tag is `static-verification` which may contain the tags `application, ejb, web, appclient, connector, other, error` and `failure-count`. The tags are self explanatory and are present depending on the type of module being verified. For example, an EAR file containing a web and EJB module will contain the tags `application, ejb, web, other,` and `failure-count.` If the verifier ran successfully, a result code of 0 is returned. A non-zero error code is returned if the verifier failed to run.

## OPTIONS

| -v verbose debugging is turned on. -d identifies where the result files get placed. -r identifies the reporting level defined as one of the following: a sets output reporting level to display all results (default) w sets output reporting level to display warning and failure results f sets output reporting level to display only failure results jar_filename name of the ear/war/jar file to perform static verification on. The results of verification are placed in two files jar_filename`_verified.xml` and jar_filename`_verified.txt` in the destination directory.

## EXAMPLES

| Example 1. Using `verifier` in the Verbose Mode
    example% verifier -v -d /verifier-results -rf sample.ear
Where -v runs the verifier in verbose mode, -d specifies the destination directory, and -rf displays only the failures. The results are stored in `/verifier-results/sample.ear_verified.xml` and `/verifier-results/sample.ear_verified.txt.`

## SEE ALSO

| `asadmin`(1M)

| Go To Top | Last Changed April 2004

Company Info | Contact | Copyright 2003 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.