Best Practices for Deploying TWiki Software on GlassFish Application Server Using LRW

Tags

Operating Systems Solaris Solaris BigAdmin RSS Best Practices for Deploying TWiki Software on GlassFish Application Server Using LRW

06-03-2009

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

Best Practices for Deploying TWiki Software on GlassFish Application Server Using LRW

This Sun BluePrints article describes best practices in deploying TWiki software on Sun's open source GlassFish application server. Utilizing the Java technology long-running Web process (LRWP) protocol and running on the Solaris Operating System (OS), the platform can run up to twice the speed of Apache HTTP Server software implementations running on the Solaris OS. The result is reduced system overhead and the ability to accommodate greater numbers of users.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

difference between oracle glassfish and glassfish opensource

questions. What's basically the difference between if I use the opensource and oracle glassfish (the one that requires license for production use)? Is there an evaluation period for the latter? Pls advise

LEARN ABOUT DEBIAN

protoc

PROTOC(1)						     protocol buffer compiler							 PROTOC(1)

NAME

       protoc - compile protocol buffer description files

SYNOPSIS

       protoc [--cpp_out=OUT_DIR] [--java_out=OUT_DIR] [--python_out=OUT_DIR] [-IPATH | --proto-path=PATH] PROTO_FILE

       protoc {-h | --help}

       protoc --version

DESCRIPTION

       protoc is a compiler for protocol buffers definitions files. It can can generate C++, Java and Python source code for the classes defined
       in PROTO_FILE.

OPTIONS

       -IPATH, --proto_path=PATH
	   Specify the directory in which to search for imports. May be specified multiple times; directories will be searched in order. If not
	   given, the current working directory is used.

       --cpp_out=OUT_DIR
	   Enable generation of C++ bindings and store them in OUT_DIR.

       --java_out=OUT_DIR
	   Enable generation of Java bindings and store them in OUT_DIR.

       --python_out=OUT_DIR
	   Enable generation of Python bindings and store them in OUT_DIR.

       -h, --help
	   Show summary of options.

       --version
	   Show version of program.

       Note that at least one of the --cpp_out, --java_out and --python_out options must be given (otherwise the program has nothing to do). It's
       also possible to specify more than one.

BUGS

       The program currently exits with code 255 for all errors, which makes it hard to differentiante from scripts the actual error.

       The upstreams BTS can be found at http://code.google.com/p/protobuf/issues/list.

SEE ALSO

       More documentation about protocol buffers syntax and APIs is available online at
       http://code.google.com/apis/protocolbuffers/docs/overview.html.

AUTHOR

       Iustin Pop <iusty@k1024.org>
	   Wrote this manpage for the Debian system.

COPYRIGHT

       Copyright (C) 2007 Iustin Pop

       This manual page was written for the Debian system (but may be used by others).

       Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or (at
       your option) any later version published by the Free Software Foundation.

       On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.

protobuf 2.0.2							    2008-10-04								 PROTOC(1)

Solaris BigAdmin RSS