Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

verifier(1m) [debian man page]

verifier(1M)                                                Application Server Utility                                                verifier(1M)

NAME
verifier - validates the J2EE Deployment Descriptors against application server DTDs SYNOPSIS
verifier [-v] [-d destination_directory] [-r [a|w|f]] jar_filename Use the verifier utility to validate the J2EE deployment descriptors and the Sun ONE 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_ver- ified.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: o a sets output reporting level to display all results (default) o w sets output reporting level to display warning and failure results o 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. 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. asadmin(1M) Sun Java System Application Server March 2004 verifier(1M)

Check Out this Related Man Page

appclient(1M)						    Application Server Utility						     appclient(1M)

NAME
appclient - launches the Application Client Container and invokes the client application packaged in the application JAR file SYNOPSIS
appclient -client client_application_jar [-mainclass client_application_main_classname|-name display_name] [-xml sun-acc.xml file] [-tex- tauth] [-user username] [-password password] Use the appclient command to launch the application client container and invoke a client application that is packaged in an application JAR file. The application client jar file is psecified and created during deployment either by the deploytool or by using the asadmin deploy command. The application client container is a set of java classes, libraries and other files that are required to execute a first-tier application client program on a Java Virtual Machine (JVM). The application client container communicates with the Application Server using RMI-IIOP. The client.jar that is retrieved after deploying an application , should be passed with the -client option while running the appclient utility. The -mainclass and -name options are optional for a single client application. For multiple client applications use either the -classname option or the- name option. -client required; the name and location for the client application jar file. The application client JAR file is specified and created during deployment, either by the deploytool or by the asadmin deploy command. -mainclass optional; the full classname of the main client application main() method that will be invoked by the Application Client Container. Used for a single client application. By default, uses the class specified in the client jar. The class name must be the full name. For example, com.sun.test.AppClient -name optional; the display name for the client application. Used for multiple client applications. By default, the dis- play name is specified in the client jar application-client.xml file which is identified by the display-name attribute. -xml optional if using the default domain and instance, otherwise it is required; identifies the name and location of the client configuration XML file. If not specified, defaults to the value of $AS_ACC_CONFIG identified in asenv.conf file. -textauth optional; used to specify using text format authentication when authentication is needed. Example 1: Using the appclient command appclient -client appserv/bin/myclientapp.jar -mainclass com.sun.test.TestAppClient -xml sun-acc.xml scott sample Where: appserv/bin/myclientapp.jar is the full path for the client application .jar file, com.sun.text.TestAppClient is the full Java pack- age name of the main client application, scott and sample are arguments to pass to the application, and sun-acc.xml is the name of the client configuration XML file. If sun-acc.xml is not in the current directory, you must give the absolute path location; otherwise the rel- ative path is used. The relative path is relative to the directory where the command is being executed. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ package-appclient(1M), asadmin(1M) Sun Java System Application Server March 2004 appclient(1M)
Man Page

Featured Tech Videos