User: mulder
Date: 00/09/14 17:59:55
Modified: manual config.html index.html warning.html
Added: manual start_stop.html
Log:
Filled out Configuration section.
Added a topic on stopping and starting jBoss.
Revision Changes Path
1.2 +121 -0 jbossweb/manual/config.html
Index: config.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/config.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- config.html 2000/09/14 18:28:35 1.1
+++ config.html 2000/09/15 00:59:54 1.2
@@ -5,5 +5,126 @@
</head>
<body>
<h1 ALIGN="CENTER">jBoss 2.0: Basic Configuration</h1>
+ <p>jBoss ships preconfigured, so there's nothing you need to do to
+ get it up and running with the test beans. However, you will
+ likely need to make minor configuration changes to support your
+ specific applications. This section gives an overview of the
+ configuration files and directories. The
+ <a HREF="adv_config.html">Advanced Configuration</a> section gives
+ detailed instructions for specific configuration changes you may
+ require. The Appendix contains <a HREF="dtds.html">DTDs</a> for
+ the configuration files, which gives the exact information.</p>
+
+ <h2><a NAME="dirs">Important Directories</a></h2>
+ <p>The directory names given here are all relative to the directory
+ you installed jBoss into.</p>
+
+ <h3><a NAME="exes">Executables</a></h3>
+ <p>Executables are located in the <strong>bin</strong> directory.
+ Using the Batch (Windows) or Shell (UNIX) scripts here, you
+ can start the server or run the test bean client. You can also
+ run the EJX deployment descriptor editor by double-clicking on it
+ (if your platform supports that) or issuing the command<br>
+ <code>java -jar ejx.jar</code></p>
+
+ <h3><a NAME="conf">Configuration</a></h3>
+ <p>Configuration files are located in the <strong>conf</strong>
+ directory. These files configure the server as a whole, so the
+ settings here will be the same for all EJBs.</p>
+
+ <h3><a NAME="libs">Libraries</a></h3>
+ <p>Java libraries are located in the <strong>lib</strong> directory.
+ They should use either the ZIP or JAR format. All libraries in
+ this directory will automatically be added to the server
+ classpath. Again, this should only be used for libraries which
+ need to be available to all EJBs; there are alternatives for
+ libraries that should be available to individual EJB JARs
+ (see <a HREF="BROKENLINK">The Manifest File</a> in the
+ Deploying section).</p>
+
+ <h3><a NAME="ejbs">EJBs</a></h3>
+ <p>EJB JARs you want to deploy go in the <strong>deploy</strong>
+ directory. If the server is running, they will be deployed
+ automatically. If you delete a JAR it will be undeployed, and
+ if you update it it will be redeployed.</p>
+
+ <h3><a NAME="client">Client Libraries</a></h3>
+ <p>Libraries required for clients are in the <strong>client</strong>
+ directory. A typical client requires
+ <code>jboss-client.jar</code>, <code>jnp-client.jar</code>,
+ <code>ejb.jar</code>, and <code>jta-spec1_0_1.jar</code>.
+ If you client is not running JDK 1.3, it will require
+ <code>jndi.jar</code> as well.</p>
+
+ <h2><a NAME="files">Configuration Files</a></h2>
+ <p>There are a number of configuration files for jBoss. The
+ contents of each are give here, though you should refer to
+ the <a HREF="adv_config.html">Advanced Configuration</a> section
+ and the <a HREF="dtds.html">DTDs</a> section of the Appendix for
+ details on the specific settings.</p>
+ <table BORDER="1">
+ <tr><th>File Name</th><th>Purpose</th></tr>
+ <tr>
+ <td>jboss.conf</td>
+ <td>Lists server components that should be loaded. Each must
+ be a JMX MBean.</td>
+ </tr>
+ <tr>
+ <td>jboss.jcml</td>
+ <td>Lists configuration parameters for the server components
+ loaded in jboss.conf.</td>
+ </tr>
+ <tr>
+ <td>jboss.properties</td>
+ <td>Provides parameters to the Java runtime (the entries here
+ become system properties)</td>
+ </tr>
+ <tr>
+ <td>jboss.dependencies</td>
+ <td>Lists dependencies between the MBeans loaded in jboss.conf,
+ so they can be loaded and stopped in the correct order.</td>
+ </tr>
+ <tr>
+ <td>jnp.properties</td>
+ <td>Lists properties for the JNDI server implementation.</td>
+ </tr>
+ <tr>
+ <td>jndi.properties</td>
+ <td>Lists properties for the JNDI client implementation. You
+ can achieve the same thing by hardcoding the properties,
+ passing them on the command line, or putting this file on the
+ client classpath. We recommend putting this on the classpath
+ since it is easiest to use and easiest to change. You have to
+ hardcode the properties if you want to look up beans on more
+ than one server, though.</td>
+ </tr>
+ <tr>
+ <td>server.policy</td>
+ <td>The default security policy for the jBoss server.
+ Currently, this is set to allow all permissions. In a future
+ release it will be locked down more.</td>
+ </tr>
+ </table>
+
+ <h2><a NAME="remote">Clients on Remote Machines</a></h2>
+ <p>The default configuration assumes client will run on the same
+ machine as the jBoss server. While often appropriate for servlet
+ and JSP clients, you need to make minor changes to support remote
+ clients.</p>
+ <ol>
+ <li>Change jboss.properties. The properties
+ <code>java.rmi.server.useLocalHostName</code> and
+ <code>java.rmi.server.hostname</code> should either both be
+ commented out, or useLocalHostName should be set to
+ <code>true</code> and hostname should be set to the host
+ name of your server (the name you want your clients to use,
+ if your server has more than one).</li>
+ <li>Set the JNDI properties for your clients appropriately. If
+ you choose to put jndi.properties on the client classpath
+ (which is recommended), you should change the value for
+ <code>java.naming.provider.url</code> to the host name of your
+ server (again, the name you want your clients to use).</li>
+ </ol>
+
</body>
</html>
1.3 +13 -8 jbossweb/manual/index.html
Index: index.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/index.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.html 2000/09/14 21:46:20 1.2
+++ index.html 2000/09/15 00:59:55 1.3
@@ -27,14 +27,14 @@
<p CLASS="tc2"><a CLASS="plain" HREF="install.html#mac">Macintosh</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="install.html#other">Other
Platforms</a></p>
<p CLASS="tc1"><a CLASS="plain" HREF="config.html">Basic Configuration</a></p>
- <p CLASS="tc2">Important Directories</p>
- <p CLASS="tc3">Executables</p>
- <p CLASS="tc3">Configuration</p>
- <p CLASS="tc3">Libraries</p>
- <p CLASS="tc3">EJBs</p>
- <p CLASS="tc3">Client Libraries</p>
- <p CLASS="tc2">Configuration Files</p>
- <p CLASS="tc2">Clients on Remote Machines</p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="config.html#dirs">Important
Directories</a></p>
+ <p CLASS="tc3"><a CLASS="plain"
HREF="config.html#exes">Executables</a></p>
+ <p CLASS="tc3"><a CLASS="plain"
HREF="config.html#conf">Configuration</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="config.html#libs">Libraries</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="config.html#ejbs">EJBs</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="config.html#client">Client
Libraries</a></p>
+ <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>
@@ -49,6 +49,10 @@
<p CLASS="tc2">Dynamic Classloading for Clients</p>
<p CLASS="tc2">Custom MBeans</p>
<p CLASS="tc2">Third-Party Products</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>
+ <p CLASS="tc2">Stopping via the Management Interface</p>
<p CLASS="tc1"><a CLASS="plain" HREF="developing.html">Writing EJBs</a></p>
<p CLASS="tc2">jBoss Supports EJB 1.1</p>
<p CLASS="tc2">Entity Beans</p>
@@ -70,6 +74,7 @@
<p CLASS="tc5">The JAWS Deployment Descriptor</p>
<p CLASS="tc4">Using EJX to Edit Deployment Descriptors</p>
<p CLASS="tc4">Editing Deployment Descriptors By Hand</p>
+ <p CLASS="tc3">The Manifest File</p>
<p CLASS="tc2">Deploying Your EJB JAR</p>
<p CLASS="tc2">Deployment Failures</p>
<p CLASS="tc3">Strange File Names</p>
1.3 +2 -1 jbossweb/manual/warning.html
Index: warning.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/warning.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- warning.html 2000/09/14 21:46:20 1.2
+++ warning.html 2000/09/15 00:59:55 1.3
@@ -35,7 +35,8 @@
</li>
<li>Basic Configuration
<ul>
- <li>This section must be written</li>
+ <li>Do jboss.properties entries really become System
+ properties?</li>
</ul>
</li>
<li>Advanced Configuration
1.1 jbossweb/manual/start_stop.html
Index: start_stop.html
===================================================================
<html>
<head>
<title>jBoss 2.0: Starting & Stopping jBoss</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
<h1 ALIGN="CENTER">jBoss 2.0: Starting & Stopping jBoss</h1>
</body>
</html>
