Commit 79e7c839 authored by nobody's avatar nobody

This commit was manufactured by cvs2svn to create branch

'unlabeled-1.10.2'.
parent 272793bf
# The "checkoutlist" file is used to support additional version controlled
# administrative files in $CVSROOT/CVSROOT, such as template files.
#
# The first entry on a line is a filename which will be checked out from
# the corresponding RCS file in the $CVSROOT/CVSROOT directory.
# The remainder of the line is an error message to use if the file cannot
# be checked out.
#
# File format:
#
# [<whitespace>]<filename><whitespace><error message><end-of-line>
#
# comment lines begin with '#'
# The "commitinfo" file is used to control pre-commit checks.
# The filter on the right is invoked with the repository and a list
# of files to check. A non-zero exit of the filter program will
# cause the commit to be aborted.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# Set this to "no" if pserver shouldn't check system users/passwords
#SystemAuth=no
# Put CVS lock files in this directory rather than directly in the repository.
#LockDir=/var/lock/cvs
# Set `TopLevelAdmin' to `yes' to create a CVS directory at the top
# level of the new working directory when using the `cvs checkout'
# command.
#TopLevelAdmin=no
# Set `LogHistory' to `all' or `TOFEWGCMAR' to log all transactions to the
# history file, or a subset as needed (ie `TMAR' logs all write operations)
#LogHistory=TOFEWGCMAR
# This file affects handling of files based on their names.
#
# The -t/-f options allow one to treat directories of files
# as a single file, or to transform a file in other ways on
# its way in and out of CVS.
#
# The -m option specifies whether CVS attempts to merge files.
#
# The -k option specifies keyword expansion (e.g. -kb for binary).
#
# Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers)
#
# wildcard [option value][option value]...
#
# where option is one of
# -f from cvs filter value: path to filter
# -t to cvs filter value: path to filter
# -m update methodology value: MERGE or COPY
# -k expansion mode value: b, o, kkv, &c
#
# and value is a single-quote delimited value.
# For example:
#*.gif -k 'b'
# The "editinfo" file is used to allow verification of logging
# information. It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure. Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
# Making sure that the entered bug-id number is correct.
# Validating that the code that was reviewed is indeed the code being
# checked in (using the bug-id number or a seperate review
# number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported. There can be only one entry that matches a given
# repository.
# The "loginfo" file controls where "cvs commit" log information
# is sent. The first entry on a line is a regular expression which must match
# the directory that the change is being made to, relative to the
# $CVSROOT. If a match is found, then the remainder of the line is a filter
# program that should expect log information on its standard input.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name ALL appears as a regular expression it is always used
# in addition to the first matching regex or DEFAULT.
#
# You may specify a format string as part of the
# filter. The string is composed of a `%' followed
# by a single format character, or followed by a set of format
# characters surrounded by `{' and `}' as separators. The format
# characters are:
#
# s = file name
# V = old version number (pre-checkin)
# v = new version number (post-checkin)
#
# For example:
#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
# or
#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
# Three different line formats are valid:
# key -a aliases...
# key [options] directory
# key [options] directory files...
#
# Where "options" are composed of:
# -i prog Run "prog" on "cvs commit" from top-level of module.
# -o prog Run "prog" on "cvs checkout" of module.
# -e prog Run "prog" on "cvs export" of module.
# -t prog Run "prog" on "cvs rtag" of module.
# -u prog Run "prog" on "cvs update" of module.
# -d dir Place module in directory "dir" instead of module name.
# -l Top-level directory only -- do not recurse.
#
# NOTE: If you change any of the "Run" options above, you'll have to
# release and re-checkout any working directories of these modules.
#
# And "directory" is a path to a directory relative to $CVSROOT.
#
# The "-a" option specifies an alias. An alias is interpreted as if
# everything on the right of the "-a" had been typed on the command line.
#
# You can encode a module within a module by using the special '&'
# character to interpose another module into the current module. This
# can be useful for creating a module that consists of many directories
# spread out over the entire source repository.
# The "notify" file controls where notifications from watches set by
# "cvs watch add" or "cvs edit" are sent. The first entry on a line is
# a regular expression which is tested against the directory that the
# change is being made to, relative to the $CVSROOT. If it matches,
# then the remainder of the line is a filter program that should contain
# one occurrence of %s for the user to notify, and information on its
# standard input.
#
# "ALL" or "DEFAULT" can be used in place of the regular expression.
#
# For example:
#ALL mail %s -s "CVS notification"
# The "rcsinfo" file is used to control templates with which the editor
# is invoked on commit and import.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being made to, relative to the
# $CVSROOT. For the first match that is found, then the remainder of the
# line is the name of the file that contains the template.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# The "taginfo" file is used to control pre-tag checks.
# The filter on the right is invoked with the following arguments:
#
# $1 -- tagname
# $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d
# $3 -- repository
# $4-> file revision [file revision ...]
#
# A non-zero exit of the filter program will cause the tag to be aborted.
#
# The first entry on a line is a regular expression which is tested
# against the directory that the change is being committed to, relative
# to the $CVSROOT. For the first match that is found, then the remainder
# of the line is the name of the filter to run.
#
# If the repository name does not match any of the regular expressions in this
# file, the "DEFAULT" line is used, if it is specified.
#
# If the name "ALL" appears as a regular expression it is always used
# in addition to the first matching regex or "DEFAULT".
# The "verifymsg" file is used to allow verification of logging
# information. It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure. Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
# Making sure that the entered bug-id number is correct.
# Validating that the code that was reviewed is indeed the code being
# checked in (using the bug-id number or a seperate review
# number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported. There can be only one entry that matches a given
# repository.
######################
# JORAM Installation #
######################
You must have a proper Ant environment to compile JORAM
(see <http://jakarta.apache.org/ant/manual/install.html>).
In the src/ directory, type:
$ ant -projecthelp
to have a list of available Ant targets for JORAM
$ ant
will create a new shipment of JORAM with all the needed libraries to use it
in ship/lib/ (default target is ship.joram)
$ ant javadoc
to generate Javadoc
$ ant clean
to clean all generated files
###########################
# JORAM Samples and Demos #
###########################
You can find samples of JORAM in the samples/ directory.
See samples/src/README for more information.
<!-- a3config.dtd
Copyright (C) 1996 - 2000 BULL
Copyright (C) 1996 - 2000 INRIA
The contents of this file are subject to the Joram Public License,
as defined by the file JORAM_LICENSE.TXT
You may not use this file except in compliance with the License.
You may obtain a copy of the License on the Objectweb web site
(www.objectweb.org).
Software distributed under the License is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for
the specific terms governing rights and limitations under the License.
The Original Code is Joram, including the java packages fr.dyade.aaa.agent,
fr.dyade.aaa.util, fr.dyade.aaa.ip, fr.dyade.aaa.mom, and fr.dyade.aaa.joram,
released May 24, 2000.
The Initial Developer of the Original Code is Dyade. The Original Code and
portions created by Dyade are Copyright Bull and Copyright INRIA.
All Rights Reserved.
-->
<!ELEMENT config (domain | server | transient | property)*>
<!ATTLIST config name CDATA "default">
<!ELEMENT domain EMPTY>
<!ATTLIST domain
name CDATA #REQUIRED
network CDATA "fr.dyade.aaa.agent.SingleCnxNetwork">
<!ELEMENT server (network | service | property)*>
<!ATTLIST server
id CDATA #REQUIRED
name CDATA ""
hostname CDATA #REQUIRED>
<!ELEMENT transient (service | property)*>
<!ATTLIST transient
id CDATA #REQUIRED
name CDATA ""
hostname CDATA #REQUIRED
server CDATA #REQUIRED>
<!ELEMENT network EMPTY>
<!ATTLIST network
domain CDATA "local"
port CDATA #REQUIRED>
<!ELEMENT service EMPTY>
<!ATTLIST service
class CDATA #REQUIRED
args CDATA "">
<!ELEMENT property EMPTY>
<!ATTLIST property
name CDATA #REQUIRED
value CDATA #REQUIRED>
#############
# Appenders #
#############
# local is set to be a FileAppender wich output in file server#{$}.audit
# log4j.appender.local=org.apache.log4j.FileAppender
# # local appender file should not be defined, it is defined in
# # AgentServer depending of server id -> server#0.audit, etc.
# # log4j.appender.local.File=System.out
# log4j.appender.local.layout=org.apache.log4j.PatternLayout
# log4j.appender.local.layout.ConversionPattern=[%t] %-5p %c %x - %m%n
# tty is set to be a FileAppender which outputs to System.out.
log4j.appender.tty=org.apache.log4j.FileAppender
log4j.appender.tty.File=System.out
log4j.appender.tty.layout=org.apache.log4j.PatternLayout
log4j.appender.tty.layout.ConversionPattern=[%t] %-5p %c %x - %m%n
log4j.appender.tty.Threshold=DEBUG
#########################
# Factory of Categories #
#########################
log4j.categoryFactory=org.objectweb.util.monolog.wrapper.log4j.MonologCategoryFactory
########################
# Configure Categories #
########################
log4j.rootCategory=ERROR, tty
# log4j.category.fr.dyade.aaa.agent.Agent=WARN
# log4j.category.fr.dyade.aaa.agent.Engine=DEBUG
# log4j.category.fr.dyade.aaa.agent.Service=DEBUG
# log4j.category.fr.dyade.aaa.mom.Destination=DEBUG
# log4j.category.fr.dyade.aaa.mom.Proxy=DEBUG
# log4j.category.fr.dyade.aaa.jndi=DEBUG
<?xml version="1.0"?>
<!DOCTYPE config SYSTEM "a3config.dtd">
<config>
<domain name="D1"/>
<server id="0" name="S0" hostname="localhost">
<network domain="D1" port="16301"/>
<service class="fr.dyade.aaa.mom.proxies.ConnectionFactory" args="16010"/>
<service class="fr.dyade.aaa.jndi.ProxyContext" args="16400"/>
<service class="fr.dyade.aaa.ns.NameService"/>
<service class="fr.dyade.aaa.task.Scheduler"/>
</server>
</config>
<?xml version="1.0"?>
<!DOCTYPE config SYSTEM "a3config.dtd">
<config>
<domain name="D1"/>
<server id="0" name="S0" hostname="localhost">
<network domain="D1" port="16301"/>
<service class="fr.dyade.aaa.mom.proxies.ConnectionFactory" args="16010"/>
<service class="fr.dyade.aaa.jndi.ProxyContext" args="16400"/>
<service class="fr.dyade.aaa.ns.NameService"/>
<service class="fr.dyade.aaa.task.Scheduler"/>
</server>
</config>
#############
# Appenders #
#############
# local is set to be a FileAppender wich output in file server#{$}.audit
# log4j.appender.local=org.apache.log4j.FileAppender
# # local appender file should not be defined, it is defined in
# # AgentServer depending of server id -> server#0.audit, etc.
# # log4j.appender.local.File=System.out
# log4j.appender.local.layout=org.apache.log4j.PatternLayout
# log4j.appender.local.layout.ConversionPattern=[%t] %-5p %c %x - %m%n
# tty is set to be a FileAppender which outputs to System.out.
log4j.appender.tty=org.apache.log4j.FileAppender
log4j.appender.tty.File=System.out
log4j.appender.tty.layout=org.apache.log4j.PatternLayout
log4j.appender.tty.layout.ConversionPattern=[%t] %-5p %c %x - %m%n
log4j.appender.tty.Threshold=DEBUG
#########################
# Factory of Categories #
#########################
log4j.categoryFactory=org.objectweb.util.monolog.wrapper.log4j.MonologCategoryFactory
########################
# Configure Categories #
########################
log4j.rootCategory=ERROR, tty
# log4j.category.fr.dyade.aaa.joram.Admin=DEBUG
# log4j.category.fr.dyade.aaa.joram.Client=DEBUG
<?xml version="1.0"?>
<!DOCTYPE config SYSTEM "a3config.dtd">
<config>
<domain name="D1"/>
<server id="0" name="S0" hostname="localhost">
<network domain="D1" port="16301"/>
<service class="fr.dyade.aaa.mom.proxies.ConnectionFactory" args="16010"/>
<service class="fr.dyade.aaa.jndi.ProxyContext" args="16400"/>
<service class="fr.dyade.aaa.ns.NameService"/>
<service class="fr.dyade.aaa.task.Scheduler"/>
</server>
<server id="1" name="S1" hostname="localhost">
<network domain="D1" port="16302"/>
<service class="fr.dyade.aaa.mom.proxies.ConnectionFactory" args="16011"/>
<service class="fr.dyade.aaa.task.Scheduler"/>
</server>
<server id="2" name="S2" hostname="localhost">
<network domain="D1" port="16303"/>
<service class="fr.dyade.aaa.mom.proxies.ConnectionFactory" args="16012"/>
<service class="fr.dyade.aaa.task.Scheduler"/>
</server>
</config>
java.naming.factory.initial fr.dyade.aaa.jndi.NamingContextFactory
java.naming.factory.host localhost
java.naming.factory.port 16400
<?xml version="1.0" ?>
<!DOCTYPE article SYSTEM "/usr/share/sgml/docbook/dtd/4.2.cr1/docbook.dtd">
<article class="whitepaper">
<articleinfo>
<author>
<firstname>Jeff</firstname>
<surname>Mesnil</surname>
<affiliation>
<address><email>jmesnil@inrialpes.fr</email></address>
</affiliation>
</author>
<title>JORAM Administration</title>
<revhistory>
<revision>
<revnumber>0.1</revnumber>
<date>2002-05-24</date>
<revremark>first draft</revremark>
</revision>
</revhistory>
<abstract>
<simpara>Describes JORAM administration.</simpara>
</abstract>
</articleinfo>
<abstract>
<para>JORAM is an Open Source JMS server. The administration step
of JMS has been deliberately kept away from specifications due
to the wide range of existing MOM products. Thus, there are no
standard way to administrate JMS. The aim of this paper is to
describe how this will be done in JORAM. It first states
the requirements for JORAM administration, then it defines the
main interfaces of it. Next it shows the internal architecture of
administration in JORAM and finally describes the tools used to
interact with it.</para>
</abstract>
<sect1>
<title>Requirements</title>
<abstract>
<para>JORAM needs a new Administration process. The aim of this
section is to describe what we mean by JORAM administration,
what we expect from it and what we do not.</para>
</abstract>
<sect2>
<title>Administration</title>
<para>TODO (what do we mean by "administration",
difference/comparison with monitoring/management)</para>
</sect2>
<sect2>
<title>What Administration include</title>
<sect3>
<title>Connection to a server</title>
<para>JORAM administration should be able to
<itemizedlist>
<listitem>
<simpara><emphasis role="strong">connect to a
server</emphasis> given a server URL and a
login/password to authenticate the
administrator</simpara>
</listitem>
<listitem>
<simpara><emphasis
role="strong">disconnect</emphasis>
from a previously connected server</simpara>
</listitem>
</itemizedlist>
</para>
</sect3>
<sect3>
<title>Users actions</title>
<para>Once connected to a server, an administrator may
<itemizedlist>
<listitem>
<simpara><emphasis
role="strong">create/retrieve/delete</emphasis> a
<emphasis role="strong">user</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">test
existence</emphasis> of a given <emphasis
role="strong">user</emphasis></simpara>
</listitem>
</itemizedlist>
</para>
</sect3>
<sect3>
<title>Destination actions</title>
<itemizedlist>
<listitem>
<simpara><emphasis
role="strong">create/retrieve/delete</emphasis> a
<emphasis role="strong">queue</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis
role="strong">create/retrieve/delete</emphasis> a
<emphasis role="strong">topic</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis
role="strong">get names</emphasis> of all
<emphasis role="strong">queues</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis
role="strong">get names</emphasis> of all
<emphasis role="strong">topics</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis
role="strong">get names</emphasis> of all
<emphasis role="strong">destinations</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">test existence</emphasis>
of a given <emphasis role="strong">destination</emphasis></simpara>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Destination factories actions</title>
<itemizedlist>
<listitem>
<simpara><emphasis
role="strong">create/retrieve/delete</emphasis> a
<emphasis role="strong">queue connection
factories</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis
role="strong">create/retrieve/delete</emphasis> a
<emphasis role="strong">topic connection
factories</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">get names</emphasis> of
all <emphasis role="strong">queue connection
factories</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">get names</emphasis> of
all <emphasis role="strong">topic connection
factories</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">get names</emphasis> of
all <emphasis role="strong">destination connection
factories</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">test existence</emphasis> of
a <emphasis role="strong">destination connection
factory</emphasis></simpara>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Rights actions</title>
<itemizedlist>
<listitem>
<simpara><emphasis role="strong">set/unset read</emphasis> right
for a given <emphasis role="strong">user</emphasis>
on a given <emphasis role="strong">destination</emphasis> </simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">set/unset read</emphasis> right
on a given <emphasis
role="strong">destination</emphasis> for all
users</simpara>
</listitem>
<listitem>
<simpara><emphasis
role="strong">test read</emphasis> right for a given
<emphasis role="strong">user</emphasis> on a given
<emphasis role="strong">destination</emphasis></simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">set/unset write</emphasis> right
for a given <emphasis role="strong">user</emphasis>
on a given <emphasis role="strong">destination</emphasis></simpara>