Locating Application Server Downloads and Documentation
This article lists all Sun GlassFish Enterprise Server and Sun Java System Application Server releases and corresponding documentation. This article aims to help users find the appropriate documentation for their version of application server. This article also provides information about the upgrade paths available for various application server releases.
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Hi,
I am working on a Tru64 Unix server.
I need to know what all applications are running on that server.
how should i do it...
Is getting the list of process through ps -ef, the right approach..
Please let me know.. (4 Replies)
If you have documents of preconfigured Solaris server with all tuned improvements..
This is all about how it is released, as first example. It must contain ready instructions to setup server from scratch in a case of global system crash
mb some FS tunings (i.e. log fs, var fs) mb some ready... (1 Reply)
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)