User: mulder
Date: 00/09/16 05:34:17
Modified: manual adv_config.html index.html intro.html
start_stop.html warning.html
Log:
Add the starting & stopping section.
Typo in the intro.
Add a section to advanced configuration on multiple jBoss servers on one
box.
Revision Changes Path
1.3 +12 -4 jbossweb/manual/adv_config.html
Index: adv_config.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/adv_config.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- adv_config.html 2000/09/16 01:42:10 1.2
+++ adv_config.html 2000/09/16 12:34:16 1.3
@@ -361,6 +361,17 @@
<h2><a NAME="jms">Configuring JMS</a></h2>
<p><i>This section is forthcoming.</i></p>
+ <h2><a NAME="multiple">Running Multiple jBoss Servers on One Machine</a></h2>
+ <p>It is possible to run jBoss more than once on the same machine.
+ You will have to set up multiple jBoss directory structures,
+ however - you cannot start it more than once from the same set
+ of files. Additionally, you will need to change all the default
+ ports on your second and subsequent servers. You may avoid some
+ of this if you elect to disable the management interface and
+ use a single JNDI server for all registration, but at a minimum
+ you need a separate port for the RMI server. Follow the
+ instructions below to change the default ports.<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
@@ -389,10 +400,7 @@
</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>
+ Your clients should use the new port automatically.</p>
<pre>
<mbean name="DefaultDomain:service=Webserver">
<attribute name="Port"><b>8083</b></attribute>
1.5 +5 -3 jbossweb/manual/index.html
Index: index.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/index.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.html 2000/09/16 01:42:10 1.4
+++ index.html 2000/09/16 12:34:16 1.5
@@ -50,14 +50,16 @@
<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#multiple">Running
Multiple jBoss Servers on One Machine</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>
- <p CLASS="tc2">Stopping via the Management Interface</p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="start_stop.html#start">Starting from
the Command Line</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="start_stop.html#console">Stopping
from the Console</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="start_stop.html#script">Stopping with
the Shutdown Script</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="start_stop.html#jmx">Stopping via the
Management Interface</a></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>
1.3 +1 -1 jbossweb/manual/intro.html
Index: intro.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/intro.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- intro.html 2000/09/14 21:46:20 1.2
+++ intro.html 2000/09/16 12:34:17 1.3
@@ -133,7 +133,7 @@
refer to <a HREF="architecture.html">jBoss Architecture</a> in the
Appendix.</p>
- <h3><a NAME="complete">Complete J2EE Soluctions</a></h3>
+ <h3><a NAME="complete">Complete J2EE Solutions</a></h3>
<p>According to the list above, for a complete J2EE solution you
need Servlets, JSPs, JavaMail, JavaBeans Activation Framework,
RMI-IIOP, and JDBC driver(s). jBoss works with a number of
1.2 +35 -0 jbossweb/manual/start_stop.html
Index: start_stop.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/start_stop.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- start_stop.html 2000/09/15 00:59:55 1.1
+++ start_stop.html 2000/09/16 12:34:17 1.2
@@ -5,5 +5,40 @@
</head>
<body>
<h1 ALIGN="CENTER">jBoss 2.0: Starting & Stopping jBoss</h1>
+
+ <h2><a NAME="start">Starting from the Command Line</a></h2>
+ <p>To start jBoss from the command line, use the
+ <code>run.bat</code> script on Windows or the
+ <code>run.sh</code> script on UNIX. The script needs to be run
+ from the <strong>bin</strong> directory, so if you set up a
+ Windows shortcut it should use that as the "Start in" directory.
+ On UNIX, you can't simply set up a symbolic link, you must create
+ a little script that changes to the bin directory and then
+ runs the startup script.</p>
+
+ <h2><a NAME="console">Stopping from the Console</a></h2>
+ <p>If you have a console window for jBoss, you can stop it by
+ hitting <code>Ctrl-C</code> in the console window. If you ran
+ jBoss under JDK 1.3 or greater, jBoss will shut down gracefully
+ when you hit <code>Ctrl-C</code>. Otherwise, it will terminate
+ abruptly, and you should use a different method to ensure a
+ graceful shutdown.</p>
+
+ <h2><a NAME="script">Stopping with the Shutdown Script</a></h2>
+ <p>To stop jBoss without using the console method, you can use
+ the <code>shutdown.bat</code> script on Windows or the
+ <code>shutdown.sh</code> script on UNIX. This will shut
+ jBoss down gracefully. If you have multiple jBoss instances
+ on you machine, you should create separate shutdown scripts
+ that include separate <code>jndi.properties</code> files on the
+ classpath.</p>
+ <p><i><b>Note:</b> The shutdown script is not yet in the current
+ jBoss builds!</i></p>
+
+ <h2><a NAME="jmx">Stopping via the Management Interface</a></h2>
+ <p>You can also shut down all the server components using the
+ jBoss management interface. See the
+ <a HREF="managing.html">Managing a Live jBoss Server</a> section
+ for more information.</p>
</body>
</html>
1.5 +13 -2 jbossweb/manual/warning.html
Index: warning.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/warning.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- warning.html 2000/09/16 01:42:10 1.4
+++ warning.html 2000/09/16 12:34:17 1.5
@@ -45,11 +45,22 @@
<li>Need to try dynamic classloading to verify directions
and get an exact procedure with security policy settings
that are required.</li>
+ <li>Confirm that multiple jBoss instances can use the same
+ JNP JNDI server. Upon reflection, this seems unlikely.</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>
+ that clients can access it automatically. Have verbal
+ confirmation, need to try.</li>
+ </ul>
+ </li>
+ <li>Starting & Stopping jBoss
+ <ul>
+ <li>Need to create the shutdown script.</li>
+ <li>Need to figure out and clarify whether you can actually
+ shut down jBoss via the management interface, or only
+ stop the EJBs/services leaving the original (now useless)
+ process running.</li>
</ul>
</li>
<li>Writing EJBs
