ch02s03.html

详细介绍了jboss3.0的配置等

		    <a href="ch13s26.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch13s26.html" title="How to Integrate Custom Services via MBeans">the section called &#8220;How to Integrate Custom Services via MBeans&#8221;</a> for the details on how to
		    create an MBean that has dependencies on other MBeans.

		</p></li><li><p><a name="d0e829"></a><a name="jboss.dependencies-file"></a>
		    <tt>jboss.dependencies</tt>
		</p><p>
		    For reasons of simplicity and ease of configuration, the
		    DependencyManager of JBoss was deprecated in the 2.1
		    release, so this file is no longer used.
		</p><p>
		    Now all the MBeans listed in <tt>jboss.jcml</tt>
		    have <span class="emphasis"><i>vertical</i></span> dependency on each other.
		    For example, a JNDI provider is required for DataSource
		    wrappers because a DataSource wrapper needs to store a
		    reference to itself in JNDI; therefore, a JNDI provider
		    MBean has to be listed before the DataSource wrapper. See
		    <a href="ch13s26.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch13s26.html" title="How to Integrate Custom Services via MBeans">the section called &#8220;How to Integrate Custom Services via MBeans&#8221;</a> for the details of the
		    dependency mechanism.
		</p></li><li><p><a name="d0e847"></a><a name="jboss-auto-file"></a>
		    <tt>jboss-auto.jcml</tt>
		</p><p>
		    JBoss has the very powerful feature of being able to record
		    a runtime snapshot of all of its running MBeans, including
		    their attributes, and later reproduce that snapshot in
		    another JBoss instance.
		</p><p>
		    When such a snapshot is taken, it is recorded in XML format
		    in the <tt>jboss-auto.jcml</tt> file.
		</p><p>Consider the following scenario:</p><p>
		    The administrator takes a running JBoss instance, adds a few
		    MBeans, modifies attributes of other MBeans, saves the
		    configuration and finally gracefully shuts down JBoss.
		</p><p>
		    The next time that JBoss is started, all the dynamically
		    added Mbeans from the previous run are recreated and their
		    attributes set. JBoss also resets any other modified
		    attributes, regardless whether an MBean was added
		    dynamically (at runtime) or statically (through
		    <tt>jboss.jcml</tt>).
		</p><p>
		    You also have the option not taking runtime snapshots; to
		    do so, simply delete the
		    <tt>jboss-auto.jcml</tt> file before starting
		    JBoss, in which case JBoss will not record any of the
		    MBeans changes at runtime.
		</p><p>

		    <span class="emphasis"><i>
			Dependency between <tt>jboss.jcml</tt> and
			<tt>jboss-auto.jcml</tt>
		    </i></span>

		</p><p>

		    If while using the runtime snapshot feature there is a need
		    to remove an MBean listed in
		    <tt>jboss.jcml</tt>, you also have to remove it
		    from <tt>jboss-auto.jcml</tt>, if it appears
		    there, to achieve the desired effect. Do not remove the
		    entire <tt>jboss-auto.jcml</tt> file unless you
		    want to stop taking runtime snapshots; to remove
		    <span class="emphasis"><i>all</i></span> the MBeans, create a functionally
		    empty <tt>jboss-auto.jcml</tt> file, like this:

		    <pre class="programlisting">
			
&lt;?xml version="1.0" encoding="UTF-8"?&gt;

&lt;server&gt;
&lt;/server&gt;
			
		    </pre>

		</p></li><li><p><a name="d0e905"></a><a name="mail.properties-file"></a>
		    <tt>mail.properties</tt>
		</p><p>
		    Following the EJB specification, JBoss provides access to a
		    mail resource through the standard JavaMail APIs. This file
		    specifies properties of the mail provider, such as where to
		    find the SMTP and POP servers, as well as other mail-related
		    configuration settings.
		</p><p>
		    Note that you are allowed to specify multiple sets of
		    configurations by creating multiple
		    <tt>mail.properties</tt> files. All you have to
		    do is to specify additional MailService MBeans with
		    different <tt>ConfigurationFile</tt> attributes in
		    the <tt>jboss.jcml</tt> file. See
		    <a href="ch13s98.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch13s98.html" title="Using JavaMail in JBoss">the section called &#8220;Using JavaMail in JBoss&#8221;</a> for additional details.
		</p></li><li><p><a name="d0e926"></a><a name="jndi.properties-file"></a>
		    <tt>jnp.properties</tt> and
		    <tt>jndi.properties</tt>
		</p><p>
		    These two files are JNDI related. The first one contains
		    properties of JNP, the JNDI provider implementation in
		    JBoss, while the second specifies properties for JNDI
		    clients.
		</p><p>
		    JNDI clients can read properties listed in a
		    <tt>jndi.properties</tt> file as long as it
		    appears somewhere in their class path. This improves the
		    portability of the client program because it is not written
		    to operate in a particular configuration. Note that you have
		    to change the
		    <tt>java.naming.provider.url=localhost</tt>
		    property-value pair if you are using clients that reside on
		    a machine other than the JBoss server host itself.
		</p></li><li><p><a name="d0e945"></a><a name="standardjaws.xml-file"></a>
		    <tt>standardjaws.xml</tt>
		</p><p>
		    Represents a default configuration file for the JBoss CMP
		    engine. It contains the JNDI name of a default DataSource,
		    per database JDBC Object-SQL mappings, default CMP entity
		    beans settings, etc. See <a href="ch06.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch06.html" title="Chapter 6. Customizing JAWS">Chapter 6</a> for
		    additional details.
		</p></li><li><p><a name="d0e955"></a><tt>auth.conf</tt></p><p>
		    This file is a JAAS login module configuration file,
		    supported by the default
		    <tt>javax.security.auth.login.Configuration</tt>
		    implementation. It contains sample server side
		    authentication configurations that are applicable when using
		    JAAS based security. See <a href="ch09.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch09.html" title="Chapter 9. JBossSX Security Extension Framework">Chapter 9</a> for
		    additional details on the JBoss security
		    framework.
		</p></li><li><p><a name="d0e966"></a><tt>server.policy</tt></p><p>
		    The default Java2 security policy for the JBoss server.
		    Currently, this is set to an all-open configuration, but
		    it is unused because the JBoss server does not run with a
		    security manager by default. See
		    <a href="ch09.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch09.html" title="Chapter 9. JBossSX Security Extension Framework">Chapter 9</a> for a description of the JBoss
		    security framework.
		</p></li><li><p><a name="d0e974"></a><tt>standardjboss.xml</tt></p><p>
		    This file provides the default container configuration. The
		    use of this file is an advanced topic covered by
		    <a href="ch07.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch07.html" title="Chapter 7. Advanced container configuration : use of jboss.xml">Chapter 7</a>.
                </p></li></ul></div></div><table border="0" cellpadding="0" cellspacing="0" height="65"><tr height="65"><td rowspan="2"><img src="gbar.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/gbar.gif" width="432" height="79"></td><td rowspan="2" background="gbar.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/gbar.gif" width="100%" align="right" valign="top"><a href="index.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/index.html"><img src="doc.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/doc.gif" border="0"></a><a href="ch02.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch02.html"><img src="toc.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/toc.gif" border="0"></a><a href="ch02s02.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch02s02.html"><img src="prev.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/prev.gif" border="0"></a><a href="ch03.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch03.html"><img src="next.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/next.gif" border="0"></a></td></tr><tr></tr></table></body></html>