User: mulder
Date: 00/09/15 18:42:10
Modified: manual adv_config.html index.html warning.html
Log:
Add advanced configuration section.
Revision Changes Path
1.2 +445 -0 jbossweb/manual/adv_config.html
Index: adv_config.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/adv_config.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- adv_config.html 2000/09/14 18:28:35 1.1
+++ adv_config.html 2000/09/16 01:42:10 1.2
@@ -5,5 +5,450 @@
</head>
<body>
<h1 ALIGN="CENTER">jBoss 2.0: Advanced Configuration</h1>
+ <p>This section describes the configuration changes you might need
+ to make to support your application. It is still not
+ comprehensive, though. The final authority on what's possible
+ is the <a HREF="dtds">DTD Section</a> in the Appendix.</p>
+
+ <h2><a NAME="datasources">Data Sources</a></h2>
+ <p>One of the most common requirements is to create one or more
+ data sources for your EJBs. You must create a data source for
+ CMP entity beans, and it is the recommended way to interact with
+ a database for BMP entity beans and session beans.</p>
+ <p>jBoss data source provide database connection pooling. This
+ means that when your application closes a connection, it is not
+ <em>really</em> closed, just returned to the "ready" state. The
+ next time your application requests a database connection, it may
+ reuse the same connection. This saves you the overhead of opening
+ new database connections for every request, and since normal web
+ applications use connections very often but for a very short
+ period of time, the savings can be significant. However, there
+ are some new issues raised such as the fact that a database
+ connection that is left unused in the pool for a long period of
+ time may timeout. The jBoss pools have a number of configuration
+ parameters to address issues like this.</p>
+
+ <h3><a NAME="supported">Supported Databases</a></h3>
+ <p>jBoss supports any database with a JDBC driver. We recommend
+ pure java drivers (type 3 or type 4), and specifically suggest
+ you <em>do not</em> use the JDBC-ODBC bridge (type 1).</p>
+
+ <h4><a NAME="cmp">Mappings Available for CMP Entities</a></h4>
+ <p>If we have not worked with a database product before we may need
+ to work with you to generate a type mapping if you plan to use
+ container managed persistence. The currently available mappings
+ include PostgreSQL, InstantDB, Hypersonic SQL, PointBase, Oracle,
+ SOLID, mySQL, MS SQLSERVER, and DB2/400. If you would like to
+ support CMP for another DBMS, or have a working mapping to share,
+ please contact the jBoss
+ <a HREF="http://www.jboss.org/mailing.htm">Mailing List</a>.</p>
+
+ <h3><a NAME="installing">Installing JDBC Drivers</a></h3>
+ <p>To install a JDBC driver, it must be distributed as one or more
+ ZIP or JAR files. You should copy those files to the
+ <strong>lib/ext</strong> directory under your jBoss installation
+ directory. In addition, you need to change one line in the file
+ <code>jboss.conf</code> located in the <strong>conf</strong>
+ directory. Find the property named <code>jdbc.drivers</code>, and
+ add your product's driver class name to the list of drivers. The
+ drivers in the list should be separated by commas. Here's an
+ example line, listing drivers for Oracle and Sybase:</p>
+<pre>
+jdbc.drivers=oracle.jdbc.driver.OracleDriver,com.sybase.jdbc2.jdbc.SybDriver
+</pre>
+ <p>The next time you start jBoss, you should see output like the
+ following listing each driver that was loaded. If instead you
+ see an error for the driver (also shown below), make sure that
+ you installed the required ZIPs and/or JARs to the
+ <strong>lib/ext</strong> directory.</p>
+<pre>
+[JDBC] Loaded JDBC-driver:oracle.jdbc.driver.OracleDriver
+[JDBC] Could not load driver:com.sybase.jdbc2.jdbc.SybDriver
+</pre>
+
+ <h3><a NAME="pools">Creating DB Connection Pools</a></h3>
+ <p>Once your JDBC driver is installed, you can add one or more
+ connection pools that use it. Any number of EJBs may share one
+ connection pool, but you may want to create multiple pools for
+ a number of reasons. For example, you may want a dedicated pool
+ for an application that requires very high reponse time, while
+ other applications share a pool of limited size.</p>
+ <p>To add a pool, you need to add sections to
+ <code>jboss.conf</code> and <code>jboss.jcml</code>, both of
+ which can be found in the <strong>conf</strong> directory.</p>
+
+ <h4><a NAME="jdbc2">The JDBC 2.0 Optional Package</a></h4>
+ <p>Before we configure the pool, we need to take a brief detour into
+ specifications. The JDBC API distributed with JDKs 1.1 through
+ 1.3 defines a transaction for every connection. It is not
+ possible to have more than one connection in a transaction, or to
+ use a single connection for more than one transaction at a
+ time.</p>
+ <p>Though perfectly adequate for normal use, this falls short of the
+ functionality mandated by the J2EE specification for enterprise
+ applications. In the J2EE environment, beans are allowed to use
+ multiple data source, which may include messaging services,
+ legacy systems, and other non-database sources. Further, all work
+ against all data sources can be committed or rolled back together.
+ This means that a EJBs must be able to use more than one data
+ source per transaction, and in particular more than one connection
+ per transaction.</p>
+ <p>Thus was born the JDBC 2.0 Optional Package (the API formerly
+ known as the JDBC 2.0 Standard Extension). This API defines
+ the javax.sql package, including interfaces such as DataSource,
+ XADataSource, and XAConnection. Some drivers support this
+ already, though most do not. And some that do support it do not
+ do a very good job yet (some Oracle implementations, in
+ particular, neglect important event notifications).</p>
+ <p>You must determine whether your driver supports the JDBC 2.0
+ Optional Package in order to configure jBoss appropriately. If it
+ does not, jBoss will simulate it so that your EJBs will operate
+ appropriately, but there are two important restrictions:</p>
+ <ol>
+ <li>If you request more than one connection from a DataSource in
+ the context of the same transaction, jBoss will return the same
+ connection every time. This is so changes made by one bean will
+ be visible to other beans operating in the same
+ transaction.</li>
+ <li>The connections cannot determine ahead of time whether it is
+ <em>possible</em> for them to commit, so they cannot participate
+ fully in the two-phase commit protocol used to commit multiple
+ data sources. This means that if there's a problem with one of
+ the data sources, some may commit and others may rollback. This
+ is why we want all DB vendors to fully support the JDBC 2.0
+ Optional Package.</li>
+ </ol>
+
+ <h4><a NAME="changes">Configuration File Changes</a></h4>
+ <p>First, you need to add a section to <code>jboss.conf</code> for
+ each pool. This declares a JMX service (an MBean) for the the
+ pool. There's a sample below. It does not matter where in the
+ file you add these lines; the startup order is not dependent on
+ the order of services in the file. You should make the following
+ changes to customize your pool:</p>
+ <ul>
+ <li>In the first line, you should replace
+ "<code>vendor.jar</code>" with the name of the ZIPs or JARs you
+ added to the <strong>lib/ext</strong> directory when you
+ configured the driver.</li>
+ <li>Enter the name you want to use for this pool instead of
+ "<code>PoolName</code>" for the first argument.</li>
+ <li>If your driver supports the JDBC 2.0 Optional Package, you
+ should use the class name of the vendor's XADataSource
+ implementation for the second argument. Otherwise, use the
+ jBoss class name shown.</li>
+ </ul>
+<pre>
+<MLET CODE="org.jboss.jdbc.XADataSourceLoader"
ARCHIVE="jboss.jar,<b>vendor.jar</b>" CODEBASE="../lib/ext/">
+ <ARG TYPE="java.lang.String" VALUE="<b>PoolName</b>">
+ <ARG TYPE="java.lang.String"
VALUE="<b>org.jboss.minerva.xa.XADataSourceImpl</b>">
+</MLET>
+</pre>
+
+ <p>Second, you must add a section to <code>jboss.jcml</code> for
+ each pool. This declares all the parameters for the pool, such as
+ the size, username and password to use, etc. The parameters will
+ be covered in detail next. The block you need to add is shown
+ below. You only need to add lines for the parameters you want to
+ override - anything you want to leave as the default you can omit.
+ jBoss will add all those lines in when it runs, so you can see the
+ default values. The example below is a simple configuration with
+ only the JDBC URL, user name, and password. The one thing you
+ need to change besides the parameter names and values is the pool
+ name in the first line:</p>
+<pre>
+<mbean name="DefaultDomain:service=XADataSource,name=<b>PoolName</b>">
+ <attribute
name="<b>URL</b>"><b>jdbc:oracle:thin:@serverhostname:1521:ORCL</b></attribute>
+ <attribute name="<b>JDBCUser</b>"><b>scott</b></attribute>
+ <attribute name="<b>Password</b>"><b>tiger</b></attribute>
+</mbean>
+</pre>
+
+ <h4><a NAME="params">Connection Pool Parameters</a></h4>
+ <p>Here is the list of possible parameters. Again, after you run
+ jBoss once with your new pool, it will add entries for all of
+ these to jboss.conf, using the default values for anything you
+ didn't specify.</p>
+ <table BORDER="1">
+ <caption><font SIZE="+1">Connection Pool Parameters</font></caption>
+ <tr><th>Name</th><th>Value</th><th>Default</th></tr>
+ <tr>
+ <td>URL</td>
+ <td>The JDBC URL used to connect to the data source.</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td>JDBCUser</td>
+ <td>The user name used to connect to the data source.</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td>Password</td>
+ <td>The password used to connect to the data source.</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td>Properties</td>
+ <td>Any properties required to connect to the data source. This
+ should be expressed in a String of the form
+ <code>name=value;name=value;name=value...</code>.</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td>MinSize</td>
+ <td>The minimum size of the pool. The pool always starts with
+ one instance, but if shrinking is enabled the pool will
+ never fall below this size. It has no effect if shrinking
+ is not enabled.</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>MaxSize</td>
+ <td>The maximum size of the pool. Once the pool has grown to
+ hold this number of instances, it will not add any more
+ instances. If one of the pooled instances is available when
+ a request comes in, it will be returned. If none of the pooled
+ instances are available, the pool will either block until an
+ instance is available, or return null (see the Blocking
+ parameter). If you set this to zero, the pool size will be
+ unlimited.</td>
+ <td>0</td>
+ </tr>
+ <tr>
+ <td>Blocking</td>
+ <td>Controls the behavior of the pool when all the connections
+ are in use. If set to <strong>true</strong>, then a client
+ that requests a connection will wait until one is available.
+ If set to <strong>false</strong>, then the pool will return
+ null immediately (and the client may retry).</td>
+ <td>false</td>
+ </tr>
+ <tr>
+ <td>LoggingEnabled</td>
+ <td>Whether the pool should record activity to the jBoss log.
+ This includes events like connections being checked out and
+ returned. It is generally only useful for troubleshooting
+ purposes (to find a connection leak, etc.).</td>
+ <td>false</td>
+ </tr>
+ <tr>
+ <td>GCEnabled</td>
+ <td>Whether the pool should check for connections that have
+ not been returned to the pool after a long period of time.
+ This would catch things like a client that disconnects
+ suddenly without closing database connections gracefully,
+ or queries that take an unexpectedly long time to run. This
+ is not generally useful in an EJB environment.</td>
+ <td>false</td>
+ </tr>
+ <tr>
+ <td>GCMinIdleTime</td>
+ <td>If garbage collection is enabled, the amount of time (in
+ milliseconds) that must pass before a connection in use is
+ garbage collected - forcibly returned to the pool.</td>
+ <td>1200000 (20m)</td>
+ </tr>
+ <tr>
+ <td>GCInterval</td>
+ <td>How often garbage collection and shrinking should run (in
+ milliseconds), if they are enabled.</td>
+ <td>120000 (2m)</td>
+ </tr>
+ <tr>
+ <td>ShrinkingEnabled</td>
+ <td>Whether the pool should close idle connections. This
+ prevents the pool from keeping a large number of connections
+ open indefinitely after a spike in activity. There is no
+ guarantee about when a particular connection will be closed,
+ only that the pool size will be reduced and only connections
+ idle for a long time will be removed.</td>
+ <td>false</td>
+ </tr>
+ <tr>
+ <td>ShrinkPercent</td>
+ <td>Sets the percent of idle connections to close, as a fraction
+ between 0 and 1 (though there is a minimum of 1 connection if
+ are eligible). If set to 1, all connections idle for more
+ than the specified time will be closed. If set to 0, only 1
+ connection will be released each time (if there's one that's
+ been idle long enough).</td>
+ <td>0.33</td>
+ </tr>
+ <tr>
+ <td>ShrinkMinIdleTime"</td>
+ <td>Set the minimum idle time (in milliseconds) before a
+ connection is eligible for shrinking.</td>
+ <td>600000 (10m)</td>
+ </tr>
+ <tr>
+ <td>TimestampUsed</td>
+ <td>Sets whether object clients can update the last used time.
+ If so, the last used time will be updated for significant
+ actions (executing a query, navigating on a ResultSet, etc.).
+ If not, the last used time will only be updated when the
+ object is given to a client and returned to the pool. This
+ time is important if shrinking or garbage collection are
+ enabled (particularly the latter).</td>
+ <td>false</td>
+ </tr>
+ </table>
+
+ <h2><a NAME="logging">Logging</a></h2>
+ <p>jBoss has a configurable logging system. You can adjust both
+ the content that is logged and the destination of the log
+ output.</p>
+
+ <h3><a NAME="limiting">Limiting Log Output</a></h3>
+ <p>The logging parameters are set in <code>jboss.conf</code>. The
+ logging entry looks like this:</p>
+<pre>
+<MLET CODE = "org.jboss.logging.ConsoleLogging" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
+ <ARG TYPE="java.lang.String"
VALUE="<b>Information,Debug,Warning,Error</b>">
+ <ARG TYPE="java.lang.String" VALUE="[{2}] {4}">
+</MLET>
+</pre>
+ <p>To limit the log output, you can remove any of the four
+ categories (Information, Debug, Warning, and Error). If you want
+ to eliminate logging output altogether, remove the whole MLET
+ entry from the file.</p>
+
+ <h3><a NAME="dest">Logging to File, GUI, DB, etc.</a></h3>
+ <p>There are three logging implementations provided with jBoss. The
+ default logs to the console. The alternatives log to a file or
+ to a Swing-based monitor app. You can write your own logging
+ implementation to log to a database, JMS queue, or other source
+ if you like. The settings for Console Logging are shown in the
+ example above. To configure file or GUI logging, read on...</p>
+
+ <h4><a NAME="file">Configuring File Logging</a></h4>
+ <p>For file logging, add an entry to jboss.conf that looks like
+ this:</p>
+<pre>
+<MLET CODE = "org.jboss.logging.FileLogging" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
+ <ARG TYPE="java.lang.String" VALUE="Information,Debug,Warning,Error">
+ <ARG TYPE="java.lang.String" VALUE="[{2}] {4}">
+ <ARG TYPE="java.lang.String" VALUE="">
+ <ARG TYPE="java.lang.String" VALUE="<b>FileName</b>">
+</MLET>
+</pre>
+ <p>You should substitute the name of the log file in the last
+ argument line above. Also, in order for the log directory to be
+ identified properly, this entry must come after an entry
+ that looks like this:</p>
+<pre>
+<MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
+ <ARG TYPE="java.lang.String" VALUE="../../log/">
+</MLET>
+</pre>
+ <p>Finally, if you want to change the output file later, you will
+ need to update the file name both here and in
+ <code>jboss.jcml</code>. Since it is both set at startup (so the
+ initial output is logged) and able to be set dynamically via the
+ management interface, the file name appears in both locations.
+ However, you do not need to include the parameter in
+ <code>jboss.jcml</code> when you first switch to file logging,
+ because it will populate the correct default filename for you
+ automatically.</p>
+
+ <h4><a NAME="gui">Configuring GUI Logging</a></h4>
+ <p>For GUI logging, add an entry to jboss.conf that looks like
+ this:</p>
+<pre>
+<MLET CODE = "org.jboss.logging.ViewerLogging" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
+</MLET>
+</pre>
+
+ <h2><a NAME="jms">Configuring JMS</a></h2>
+ <p><i>This section is forthcoming.</i></p>
+
+ <h2><a NAME="ports">Changing Defalt Port Assignments</a></h2>
+ <p>jBoss uses three ports, by default. The JNDI server listens on
+ port 1099 for JNDI requests, the management interface listens on
+ port 8082 for JMX requests, and the RMI server listens on port
+ 1083 for RMI requests. If you change any of the ports, you must
+ restart the jBoss server for the changes to take effect.</p>
+ <p>To change the JNDI port, edit the file
+ <code>jnp.properties</code> in the <strong>conf</strong>
+ directory. Change the line <code>jnp.port</code> to the port you
+ want to use. You must also change you client configuration to
+ use the new port. You need to change the parameter
+ <code>java.naming.provider.url</code> to use the form
+ <code>server:port</code> instead of just <code>server</code>.
+ This may be in the file jndi.properties on the classpath, or
+ set on the command line or in the code for you client.</p>
+ <p>To change the JMX port, change the following entry in
+ <code>jboss.jcml</code> in the <strong>conf</strong> directory.
+ You would then have to change the port appropriately in your JMX
+ client, or when you go to the web management interface.</p>
+<pre>
+ <mbean name="Adaptor:name=html">
+ <attribute name="MaxActiveClientCount">10</attribute>
+ <attribute name="Parser" />
+ <attribute name="Port"><b>8082</b></attribute>
+ </mbean>
+</pre>
+ <p>To change the RMI port, change the following entry in
+ <code>jboss.jcml</code> in the <strong>conf</strong> directory.
+ To change it for clients, uncomment and change the
+ <code>java.rmi.server.codebase</code> entry in the
+ <code>jboss.properties</code> file in the <strong>conf</strong>
+ directory.</p>
+<pre>
+ <mbean name="DefaultDomain:service=Webserver">
+ <attribute name="Port"><b>8083</b></attribute>
+ </mbean>
+</pre>
+
+ <h2><a NAME="dynamic">Dynamic Classloading for Clients</a></h2>
+ <p>Normally, a client must have a number of JARs available. These
+ can be found in the <code>client</code> directory. However, you
+ can also have the client dynamically download the required classes
+ from the server. In order to do this, all you need to do is
+ install a security manager! Of course, your security manager
+ must allow network access to the server and class loading.
+ Also, if you're not running JDK 1.3 or greater, you'll still need
+ the <code>jndi.jar</code> file, so you can make the initial
+ contact with the server.</p>
+
+ <h2><a NAME="custom">Custom MBeans</a></h2>
+ <p>If you want to add services to the jBoss server, the best way
+ to do that is to write your own JMX MBeans. Then they can be
+ loaded in <code>jboss.conf</code> and configured in
+ <code>jboss.jcml</code> like the existing MBeans. The best way
+ for your EJBs to access your new services is to make them
+ accessible via JNDI.</p>
+ <p>The easiest way to proceed is to subclass
+ <code>org.jboss.util.ServiceMBean</code> and
+ <code>org.jboss.util.ServiceMBeanSupport</code>, so your service
+ will receive startService and stopService calls. You should
+ declare a constructor with minimal parameters, and then include
+ accessor methods for your important properties. If you declare
+ them in you MBean interface, they will show up in
+ <code>jboss.jcml</code> and you can configure the properties
+ there. Then the sequence of calls is to the constructor, to all
+ the accessor methods, and finally to startService.</p>
+ <p>If your service depends on other services being loaded first
+ (such as the logger, JNDI server, etc.) you should add entries to
+ jboss.dependencies to declare as much. The services are always
+ constructed in the order they're listed in
+ <code>jboss.conf</code>, but there's not a guaranteed order for
+ calling <code>startService</code> on the various MBeans. However,
+ it is guaranteed to be consistant with the dependencies declared
+ in <code>jboss.dependencies</code>.</p>
+
+ <h2><a NAME="third">Third-Party Products</a></h2>
+ <p>jBoss already integrates with a number of third-party products
+ (see <a HREF="third_party.html">Third-Party Software</a>). If you
+ are using a product that is not yet supported, your integration
+ strategy will depend on the nature of the product. But again,
+ where possible, the best way to implement the service is as a
+ JMX MBean. If necessary (like for persistance managers), you may
+ need to hook in at a lower level. In that case, you may need to
+ specify configuration information in an XML file for each EJB JAR,
+ depending on whether the configuration should be at the bean level
+ or at the server level.</p>
+ <p>If you integrate a new product with jBoss, please let us know on
+ the jBoss <a HREF="http://www.jboss.org/mailing.htm">Mailing
+ List</a>.</p>
</body>
</html>
1.4 +18 -13 jbossweb/manual/index.html
Index: index.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/index.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index.html 2000/09/15 00:59:55 1.3
+++ index.html 2000/09/16 01:42:10 1.4
@@ -36,19 +36,24 @@
<p CLASS="tc2"><a CLASS="plain" HREF="config.html#files">Configuration
Files</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="config.html#remote">Clients on Remote
Machines</a></p>
<p CLASS="tc1"><a CLASS="plain" HREF="adv_config.html">Advanced
Configuration</a></p>
- <p CLASS="tc2">Data Sources</p>
- <p CLASS="tc3">Supported Databases</p>
- <p CLASS="tc3">Installing JDBC Drivers</p>
- <p CLASS="tc3">Creating DB Connection Pools</p>
- <p CLASS="tc4">Connection Pool Parameters</p>
- <p CLASS="tc2">Logging</p>
- <p CLASS="tc3">Limiting Log Output</p>
- <p CLASS="tc3">Logging to File, GUI, DB, etc.</p>
- <p CLASS="tc2">JMS</p>
- <p CLASS="tc2">Changing Default Port Assignments</p>
- <p CLASS="tc2">Dynamic Classloading for Clients</p>
- <p CLASS="tc2">Custom MBeans</p>
- <p CLASS="tc2">Third-Party Products</p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#datasources">Data
Sources</a></p>
+ <p CLASS="tc3"><a CLASS="plain"
HREF="adv_config.html#supported">Supported Databases</a></p>
+ <p CLASS="tc4"><a CLASS="plain" HREF="adv_config.html#cmp">Mappings
Available for CMP Entities</a></p>
+ <p CLASS="tc3"><a CLASS="plain"
HREF="adv_config.html#installing">Installing JDBC Drivers</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="adv_config.html#pools">Creating DB
Connection Pools</a></p>
+ <p CLASS="tc4"><a CLASS="plain" HREF="adv_config.html#jdbc2">The JDBC
2.0 Optional Package</a></p>
+ <p CLASS="tc4"><a CLASS="plain"
HREF="adv_config.html#changes">Configuration File Changes</a></p>
+ <p CLASS="tc4"><a CLASS="plain"
HREF="adv_config.html#params">Connection Pool Parameters</a></p>
+ <p CLASS="tc2"><a CLASS="plain"
HREF="adv_config.html#logging">Logging</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="adv_config.html#limiting">Limiting
Log Output</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="adv_config.html#dest">Logging to
File, GUI, DB, etc.</a></p>
+ <p CLASS="tc4"><a CLASS="plain" HREF="adv_config.html#file">Configuring
File Logging</a></p>
+ <p CLASS="tc4"><a CLASS="plain" HREF="adv_config.html#gui">Configuring
GUI Logging</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#jms">JMS</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#ports">Changing
Default Port Assignments</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#dynamic">Dynamic
Classloading for Clients</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#custom">Custom
MBeans</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#third">Third-Party
Products</a></p>
<p CLASS="tc1"><a CLASS="plain" HREF="start_stop.html">Starting &
Stopping jBoss</a></p>
<p CLASS="tc2">Starting from the Command Line</p>
<p CLASS="tc2">Stopping from the Command Line</p>
1.4 +9 -1 jbossweb/manual/warning.html
Index: warning.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/warning.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- warning.html 2000/09/15 00:59:55 1.3
+++ warning.html 2000/09/16 01:42:10 1.4
@@ -41,7 +41,15 @@
</li>
<li>Advanced Configuration
<ul>
- <li>This section must be written</li>
+ <li>Need JMS Configuration</li>
+ <li>Need to try dynamic classloading to verify directions
+ and get an exact procedure with security policy settings
+ that are required.</li>
+ <li>Confirm java.naming.provider.url=server:port syntax
+ for changing the JNP port.</li>
+ <li>If you change the port for the webserver on 8083, confirm
+ that clients can access it by changing the java.rmi.server.codebase
+ in jboss.properties.</li>
</ul>
</li>
<li>Writing EJBs
