User: kunle
Date: 01/04/05 03:06:33
Modified: src/docs howtojetty.xml howtomssql.xml
Log:
- general tidy-up
Revision Changes Path
1.2 +65 -80 manual/src/docs/howtojetty.xml
Index: howtojetty.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/docs/howtojetty.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- howtojetty.xml 2001/03/30 02:30:43 1.1
+++ howtojetty.xml 2001/04/05 10:06:16 1.2
@@ -9,6 +9,7 @@
<surname>Odutola</surname>
</author>
<email>[EMAIL PROTECTED]</email>
+ 29 March 2001
</para>
<para>
<author>
@@ -105,24 +106,23 @@
If this is the case with you or, if you have any
further comments or suggestions about this document or
JBoss-Jetty then please do one or more of the
following:
<itemizedlist>
- <listitem>
- <para>
+ <listitem>
+ <para>
Join the <ulink
url="http://www.jboss.org/newsite/business/list.html">JBoss Mailing List</ulink>
if your comments or suggestions are
relevant to JBoss.
</para>
- </listitem>
- <listitem>
- <para>
+ </listitem>
+ <listitem>
+ <para>
Join the <ulink
url="http://jetty.mortbay.com/jetty/mailingLists.html">Jetty Mailing List</ulink>
if your comments or suggestions are
relevant to Jetty.
</para>
- </listitem>
+ </listitem>
</itemizedlist>
You will then be able to contribute to the production
of this document and the development of JBoss-Jetty.
</para>
</section>
</section>
-
<section id="howto-jbossjetty-requirements">
<title>Check JBoss-Jetty system requirements</title>
<para>
@@ -131,21 +131,21 @@
the following:
</para>
<itemizedlist>
- <listitem>
- <para>
- <link
linkend="howto-jbossjetty-requirements-hardware">Server Hardware specification</link>
- </para>
- </listitem>
- <listitem>
- <para>
- <link
linkend="howto-jbossjetty-requirements-java">Java Platform version</link>
- </para>
- </listitem>
- <listitem>
- <para>
- <link
linkend="howto-jbossjetty-requirements-database">Database Server integration
(optional)</link>
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <link
linkend="howto-jbossjetty-requirements-hardware">Server Hardware specification</link>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <link
linkend="howto-jbossjetty-requirements-java">Java Platform version</link>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <link
linkend="howto-jbossjetty-requirements-database">Database Server integration
(optional)</link>
+ </para>
+ </listitem>
</itemizedlist>
<section id="howto-jbossjetty-requirements-hardware">
<title>Check Server Hardware specification</title>
@@ -238,22 +238,22 @@
<itemizedlist>
<listitem>
<para>
- <xref
linkend="jdbc"></xref> for basic information on configuring JBoss-Jetty to use
+ <xref linkend="jdbc"/>
for basic information on configuring JBoss-Jetty to use
a database server.
</para>
</listitem>
<listitem>
<para>
- <xref
linkend="cmp"></xref> for more information on Container Managed Persistence using
+ <xref linkend="cmp"/>
for more information on Container Managed Persistence using
a database server
</para>
</listitem>
<listitem>
<para>
- <xref
linkend="howto"></xref> for documents addressing the configuration of specific RDBMS
+ <xref
linkend="howto"/> for documents addressing the configuration of specific RDBMS
</para>
</listitem>
- </itemizedlist>
+ </itemizedlist>
</para>
</note>
</section>
@@ -293,20 +293,16 @@
</row>
<row>
<entry>
- <programlisting>
- <![CDATA[
+
<programlisting><![CDATA[
mkdir C:\JavaApps\jboss-jetty
chdir C:\JavaApps\jboss-jetty
- ]]>
- </programlisting>
+ ]]></programlisting>
</entry>
<entry>
- <programlisting>
- <![CDATA[
+
<programlisting><![CDATA[
md /usr/bin/jboss-jetty
cd /usr/bin/jboss-jetty
- ]]>
- </programlisting>
+ ]]></programlisting>
</entry>
</row>
</tbody>
@@ -321,7 +317,8 @@
form of the command to extract the files is:
</para>
<para>
- <computeroutput>jar xvf
<replaceable>jBoss-archive-filename</replaceable></computeroutput>
+ <computeroutput>jar xvf
<replaceable>jBoss-archive-filename</replaceable>
+ </computeroutput>
</para>
<para>
As an example, let's say you have a JBoss-Jetty binary
distribution archive named
@@ -338,20 +335,16 @@
</row>
<row>
<entry>
- <programlisting>
- <![CDATA[
+
<programlisting><![CDATA[
chdir C:\JavaApps\jboss-jetty
jar xvf C:\Packages\jboss-jetty.zip
- ]]>
- </programlisting>
+ ]]></programlisting>
</entry>
<entry>
- <programlisting>
- <![CDATA[
+
<programlisting><![CDATA[
cd /usr/bin/jboss-jetty
jar xvf ~/packages/jboss-jetty.zip
- ]]>
- </programlisting>
+ ]]></programlisting>
</entry>
</row>
</tbody>
@@ -378,34 +371,30 @@
carefully designed to start JBoss-Jetty. So, to start the
JBoss-Jetty application server suite, use the
<filename>run_with_jetty</filename> command as shown below:
</para>
- <informaltable>
- <tgroup cols="2" align="center" colsep="0" rowsep="0">
- <tbody>
- <row>
- <entry>Windows 95/98, Windows
NT or Windows 2000</entry>
- <entry>Linux, Solaris and
other Unixes</entry>
- </row>
- <row>
- <entry>
- <programlisting>
- <![CDATA[
+ <informaltable>
+ <tgroup cols="2" align="center" colsep="0" rowsep="0">
+ <tbody>
+ <row>
+ <entry>Windows 95/98, Windows NT or
Windows 2000</entry>
+ <entry>Linux, Solaris and other
Unixes</entry>
+ </row>
+ <row>
+ <entry>
+ <programlisting><![CDATA[
chdir C:\JavaApps\jboss-jetty
run_with_jetty
- ]]>
- </programlisting>
- </entry>
- <entry>
- <programlisting>
- <![CDATA[
+ ]]></programlisting>
+ </entry>
+ <entry>
+ <programlisting><![CDATA[
cd /usr/bin/jboss-jetty
./run_with_jetty
- ]]>
- </programlisting>
- </entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
+ ]]></programlisting>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
<para>
When JBoss-Jetty is started, it should respond with about
three to fours screens of console messages. None of the
messages should be an error message. This is entirely normal.
In addition, JBoss-Jetty is preconfigured with an
@@ -436,7 +425,7 @@
some sample files that are normally
supplied with Jetty.
</para>
</listitem>
- </itemizedlist>
+ </itemizedlist>
</para>
<para>
Now that you've seen how to start JBoss-Jetty and hopefully verified
that all is well, you should also know that
@@ -455,14 +444,14 @@
</para>
<section>
<title>Deploy a JSP-only web app with JBoss-Jetty</title>
- <para>
+ <para>
In this section you will learn the basics of
deploying an application composed entirely of
<filename>.jsp</filename> files with
JBoss-Jetty. You will create and deploy an application named
<filename>hello</filename>. You will also
create a <filename>sample.jsp</filename> within
<filename>hello</filename> that will be
accessible as <filename>http://localhost/hello/sample.jsp</filename>
on the computer running JBoss-Jetty. For other
computers, just replace <filename>localhost</filename> with
the computer's IP name or address.
- </para>
+ </para>
<orderedlist>
<listitem>
<para>
@@ -474,15 +463,13 @@
<para>
Add the following lines before
<prompt><![CDATA[</configure>]]></prompt>. These lines create an
application called hello and configure
it's deployment directory to be <filename>helloapp</filename>:
- <programlisting>
- <![CDATA[
+ <programlisting><![CDATA[
<Call name="addWebApplication">
<Arg>/hello/*</Arg>
<Arg><SystemProperty name="jetty.home" default="."/>/webapps/helloapp/</Arg>
<Arg><SystemProperty name="jetty.home" default="."/>/etc/webdefault.xml/</Arg>
</Call>
- ]]>
- </programlisting>
+ ]]></programlisting>
</para>
</listitem>
<listitem>
@@ -519,7 +506,7 @@
it's output is displayed in your
browser.
</para>
</listitem>
- </orderedlist>
+ </orderedlist>
<para>
The <filename>sample.jsp</filename> file was compiled
by default because you used
<filename>/etc/webdefault.xml</filename> as the third
argument of the <filename>addWebApplication</filename>
@@ -530,17 +517,15 @@
<para>
If you want to add more jsp-files, just drop them in
the <filename>helloapp</filename> directory and do as
you did with <filename>sample.jsp</filename>
previously.
- </para>
+ </para>
</section>
</section>
<section id="howto-jbossjetty-configure">
<title>Configure your JBoss-Jetty installation</title>
- <para>
- </para>
+ <para/>
</section>
<section id="howto-jbossjetty-trouble">
<title>JBoss-Jetty troubleshooting tips</title>
- <para>
- </para>
+ <para/>
</section>
</section>
1.7 +18 -15 manual/src/docs/howtomssql.xml
Index: howtomssql.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/docs/howtomssql.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- howtomssql.xml 2001/03/30 18:50:45 1.6
+++ howtomssql.xml 2001/04/05 10:06:32 1.7
@@ -9,6 +9,7 @@
<surname>Odutola</surname>
</author>
<email>[EMAIL PROTECTED]</email>
+ 29 March 2001
</para>
<para>
<author>
@@ -50,7 +51,7 @@
Pure Java J2EE application servers and the ultra-high performance
Microsoft
SQL Server RDBMS offers you a J2EE development and deployment
environment
on the Windows platform with superior performance, good return on
investment
- (ROI) and substantially reduced time to market (TTM) compared to
other J2EE
+ (ROI) and substantially reduced time to market (RTTM) compared to
other J2EE
application suites and RDBMS solutions on the Windows platform.
</para>
<section id="howto-mssql-intro-menu">
@@ -172,7 +173,8 @@
</table>
<note>
<para>
- <superscript>*</superscript> The Sun JBDC-ODBC Bridge
driver is NOT recommended for serious J2EE development or deployment</para>
+ <superscript>*</superscript> The Sun JBDC-ODBC Bridge
driver and the FreeTDS JDBC driver (at least in their
+ current form in April 2001) are NOT recommended for
serious J2EE development or deployment</para>
</note>
<para>
For the remainder of this document, the Sun JDBC-ODBC bridge,
the Merant DataDirect Connect JDBC 2.0 Client
@@ -297,7 +299,7 @@
like it to use this driver. Add an entry for the
driver to the list of drivers that JBoss loads at
startup. This list is stored in the
<filename>jboss.jcml</filename> file. The file can be found in
<filename>%JBOSS_HOME%/conf/</filename>
-
<replaceable><config-name></replaceable>.
+ <replaceable><config-name></replaceable>.
For a standard distribution of JBoss,
<replaceable><config-name></replaceable> is
<filename>default</filename> whilst for the
JBoss-Jetty it is <filename>jetty</filename>.
The entry should be a single, continuous list of
comma-separated JDBC driver names.
@@ -536,7 +538,7 @@
that JBoss loads at startup. This list is stored in
the <filename>jbdc.drivers</filename> entry in the
<filename>jboss.properties</filename> file. The
<filename>jboss.properties</filename> file can be
found in <filename>%JBOSS_HOME%/conf/</filename>
-
<replaceable><config-name></replaceable>.
+ <replaceable><config-name></replaceable>.
For a standard distribution of JBoss,
<replaceable><config-name></replaceable> is
<filename>default</filename> whilst for the
JBoss-Jetty it is <filename>jetty</filename>. The
<filename>jbdc.drivers</filename> entry should be a
single, continuous string of JDBC driver names
@@ -598,7 +600,7 @@
At this point, you know that the driver is correctly
installed. You will now set up a connection pool
that your EJBeans can connect to. Add an MLET entry
into the <filename>jboss.conf</filename> file as
shown below. The file can be found in
<filename>%JBOSS_HOME%/conf/</filename>
- <replaceable><config-name></replaceable>.
+ <replaceable><config-name></replaceable>.
</para>
<para>
For this tutorial, you will create a connection pool
named <replaceable>SQLServerPool</replaceable> as
@@ -606,7 +608,7 @@
driver's <filename>XADataSource</filename> classname.
If your driver doesn't support
<filename>XADataSource</filename> use
<filename>org.jboss.minerva.xa.XADataSourceImpl</filename> instead.
</para>
- <itemizedlist>
+ <itemizedlist>
<listitem>
<para>
Connection pool MLET declaration for
Sun JDBC-ODBC bridge driver
@@ -656,7 +658,8 @@
for the pool like <envar>LoggingEnabled</envar>). Tell
your pool how to connect to your
database server by adding an MBEAN entry into the
<filename>jboss.jcml</filename> file as
shown below. The file can be found in
-
<filename>%JBOSS_HOME%/conf/</filename><replaceable><config-name></replaceable>.
+ <filename>%JBOSS_HOME%/conf/</filename>
+ <replaceable><config-name></replaceable>.
</para>
<itemizedlist>
<listitem>
@@ -785,15 +788,13 @@
Change the default settings in the
<filename>standardjaws.xml</filename> file in
<filename>%JBOSS_HOME%/conf</filename>
directly. This is useful in environments like mine where all
unused applications and files - such as
HypersonicSQL & InstantDB - are removed from the servers.
- default settings
<filename>standardjaws.xml</filename> as shown below:
</para>
<para>
To change your default datasource and datatype
mapping, make the following highlighted changes to your
<filename>standardjaws.xml</filename> file.
</para>
<informalexample>
- <programlisting>
- <![CDATA[
+ <programlisting><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<jaws>
]]>
@@ -808,15 +809,15 @@
<itemizedlist>
<listitem>
<para>
- <xref linkend="jaws"></xref> for
further information on configuring JAWS (aka JBossCMP).
+ <xref linkend="jaws"/> for further
information on configuring JAWS (aka JBossCMP).
</para>
</listitem>
<listitem>
<para>
- <xref linkend="cmp"></xref> for useful
information on CMP development & deployment with JBoss.
+ <xref linkend="cmp"/> for useful
information on CMP development & deployment with JBoss.
</para>
</listitem>
- </itemizedlist>
+ </itemizedlist>
</para>
</section>
<section id="howto-mssql-trouble">
@@ -862,12 +863,14 @@
[InstantDB] Started
[DefaultDS] Starting
[DefaultDS] XA Connection pool DefaultDS bound to java:/DefaultDS
-[DefaultDS] Started[SQLServerPool] Starting
+[DefaultDS] Started
+[SQLServerPool] Starting
[SQLServerPool] XA Connection pool SQLServerPool bound to java:/SQLServerPool
</programlisting>
</informalexample>
<para>
- Check that your JDBC driver is loaded correctly. If
not then see <xref linkend="howto-mssql-trouble-driverload"/>
+ Check that your JDBC driver is loaded correctly. If
not then see
+ <xref linkend="howto-mssql-trouble-driverload"/>
for possible clues. If your JDBC driver is loading
correctly then this error indicates that JBoss is unable
to communicate with your database server.
</para>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
