User: mulder  
  Date: 00/10/18 11:07:43

  Modified:    manual   adv_config.html index.html warning.html
  Log:
   - Add Sybase DB Configuratoin
   - Add Security headers (no content to speak of yet)
   - Rewrite logging section to explain all the parameters
  
  Revision  Changes    Path
  1.12      +140 -36   jbossweb/manual/adv_config.html
  
  Index: adv_config.html
  ===================================================================
  RCS file: /products/cvs/ejboss/jbossweb/manual/adv_config.html,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- adv_config.html   2000/10/17 15:41:06     1.11
  +++ adv_config.html   2000/10/18 18:07:43     1.12
  @@ -339,8 +339,8 @@
   <pre>
       &lt;mbean name="DefaultDomain:service=XADataSource,name=<b>OracleDB</b>"&gt;
           &lt;attribute 
name="URL"&gt;jdbc:oracle:thin:@<b>host.domain.com</b>:1521:<b>instance</b>&lt;/attribute&gt;
  -        &lt;attribute name="Password"&gt;<b>scott</b>&lt;/attribute&gt;
  -        &lt;attribute name="JDBCUser"&gt;<b>tiger</b>&lt;/attribute&gt;
  +        &lt;attribute name="JDBCUser"&gt;<b>scott</b>&lt;/attribute&gt;
  +        &lt;attribute name="Password"&gt;<b>tiger</b>&lt;/attribute&gt;
       &lt;/mbean&gt;
   </pre>
             </li>
  @@ -420,19 +420,35 @@
           </ul>
         </li>
   
  -      <li>Sybase (<i>Forthcoming...</i>)
  +      <li>Sybase Adaptive Server Anywhere 6.x, Adaptive Server Enterprise 11.9.x, 
12.x
           <ul>
  -          <li>lib/ext: <a 
HREF="http://www.sybase.com/detail_list/1,3153,2282,00.html">unknown.jar</a></li>
  +          <li>You must install jConnect 5.2, including the stored procedures
  +            which are distributed with the jConnect package.  There are
  +         directions for this in the Installation Instructions chapter
  +         of the
  +         <a 
HREF="http://manuals.sybase.com/onlinebooks/group-jc/jcg0520e/jconnig/@Generic__BookView;cs=default;ts=default">jConnect
  +           for JDBC Installation Guide</a>.</li>
  +          <li>lib/ext: <a 
HREF="http://www.sybase.com/detail/1,3693,1009796,00.html">jconn2.jar</a></li>
         <li>jboss.properties
   <pre>
  +jdbc.drivers=com.sybase.jdbc2.jdbc.SybDriver
   </pre>
         </li>
         <li>jboss.conf
   <pre>
  +    &lt;MLET CODE="org.jboss.jdbc.XADataSourceLoader" ARCHIVE="jboss.jar" 
CODEBASE="../lib/ext/"&gt;
  +        &lt;ARG TYPE="java.lang.String" VALUE="<b>SybaseDB</b>"&gt;
  +        &lt;ARG TYPE="java.lang.String" 
VALUE="org.jboss.minerva.xa.XADataSourceImpl"&gt;
  +    &lt;/MLET&gt;
   </pre>
         </li>
         <li>jboss.jcml
   <pre>
  +    &lt;mbean name="DefaultDomain:service=XADataSource,name=<b>SybaseDB</b>"&gt;
  +        &lt;attribute 
name="URL"&gt;jdbc:sybase:Tds:<b>host.domain.com</b>:4100/<b>database</b>&lt;/attribute&gt;
  +        &lt;attribute name="Password"&gt;<b>password</b>&lt;/attribute&gt;
  +        &lt;attribute name="JDBCUser"&gt;<b>username</b>&lt;/attribute&gt;
  +    &lt;/mbean&gt;
   </pre>
         </li>
       </ul>
  @@ -489,35 +505,41 @@
       </ul>
   
   
  +    <h2><a NAME="security">Security</a></h2>
  +    <p>You can set users and roles in the jBoss server, and then use
  +      them to control access to your beans.  Currently, the only way
  +      to configure users and roles is to set up a table in a database,
  +      though there will be additional security implementations in a
  +      future release.</p>
  +
  +    <h3><a NAME="db-security">Configuring a Security Database</a></h3>
  +    <p><i>This section is forthcoming.</i></p>
  +
  +
       <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>
  +      output.  Currently there are 3 logging implementations
  +      included in jBoss - you can log to the console, to a file, or
  +      to a Swing GUI.  The logging system can easily support additional
  +      log destinations, such as a database or message queue.  By
  +      default, console and file logging are enabled.</p>
  +    <p>The first three sections show what the logging configuration
  +      looks like for each log destination.  Then the common parameters
  +      for console and file logging are described.</p>
  +
  +    <h3><a NAME="console">Console Logging</a></h3>
  +    <p>The console logging entry is in <code>jboss.conf</code> and
  +      looks like this:</p>
   <pre>
   &lt;MLET CODE = "org.jboss.logging.ConsoleLogging" ARCHIVE="jboss.jar" 
CODEBASE="../lib/ext/"&gt;
  -   &lt;ARG TYPE="java.lang.String" 
VALUE="<b>Information,Debug,Warning,Error</b>"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="Information,Debug,Warning,Error"&gt;
      &lt;ARG TYPE="java.lang.String" VALUE="[{2}] {4}"&gt;
   &lt;/MLET&gt;
   </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
  +    <h3><a NAME="file">File Logging</a></h3>
  +    <p>The file logging entry is in <code>jboss.conf</code> and looks like
         this:</p>
   <pre>
   &lt;MLET CODE = "org.jboss.logging.FileLogging" ARCHIVE="jboss.jar" 
CODEBASE="../lib/ext/"&gt;
  @@ -545,32 +567,114 @@
         <code>jboss.jcml</code> when you first switch to file logging,
         because it will populate the correct default filename for you
         automatically.</p>
  + 
       <p>Finally, if you want to append the output file at startup
         rather than to overwrite, you should add one more argument line 
  -      in jboss.conf:</p>
  +      to the entry:</p>
   <pre>
   &lt;MLET CODE = "org.jboss.logging.FileLogging" ARCHIVE="jboss.jar" 
CODEBASE="../lib/ext/"&gt;
      &lt;ARG TYPE="java.lang.String" VALUE="Information,Debug,Warning,Error"&gt;
  -   &lt;ARG TYPE="java.lang.String" VALUE="<b>{0,date,yyyy-MM-dd} 
{0,time,hh:mm:ss}</b> [{2}] {4}"&gt;
  -   &lt;ARG TYPE="java.lang.String" VALUE="<b>myBeanName1;myBeanName2</b>"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="[{2}] {4}"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE=""&gt;
      &lt;ARG TYPE="java.lang.String" VALUE="FileName"&gt;
  -   &lt;ARG TYPE="java.lang.Boolean" VALUE="<b>true</b>"&gt;
  +   <b>&lt;ARG TYPE="java.lang.Boolean" VALUE="true"&gt;</b>
   &lt;/MLET&gt;
   </pre>
  -    <p>In the second argument line above you can see an example
  -    of setting date and time formats for the log file.
  -    The third parameter may be used for filtering the log messages by their
  -    source. You can have multiple FileLogging entries with different 
  -    source filters.
  -    </p>
   
  -    <h4><a NAME="gui">Configuring GUI Logging</a></h4>
  +    <h3><a NAME="gui">GUI Logging</a></h3>
       <p>For GUI logging, add an entry to jboss.conf that looks like
  -      this:</p>
  +      this.  This type of logging does not accept as many parameters
  +      as the others, since you can manage the log entries via the
  +      GUI.  The only argument is the source filter (blank to show
  +      events from all sources).</p>
   <pre>
   &lt;MLET CODE = "org.jboss.logging.ViewerLogging" ARCHIVE="jboss.jar" 
CODEBASE="../lib/ext/"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE=""&gt;
  +&lt;/MLET&gt;
  +</pre>
  +
  +
  +    <h3><a NAME="formatting">Formatting Log Output</a></h3>
  +   <p>If you want to change the format of the log entries, you can
  +     use the following codes in the second parameter to file or
  +     console logging.  Any other character in the format string will
  +     be used verbatim.  The module and description are used by
  +     default.</p>
  +    <table border="1">
  +      <tr><th>Code</th><th>Description</th></tr>
  +      <tr>
  +        <td>{0,date,<b>yyyy-MM-dd</b>}</td>
  +        <td>The date of the message, where the last bit uses the
  +          syntax defined by SimpleDateFormat</td>
  +      </tr>
  +      <tr>
  +        <td>{0,time,<b>hh:mm:ss</b>}</td>
  +        <td>The time of the message, where the last bit uses the
  +          syntax defined by SimpleDateFormat</td>
  +      </tr>
  +      <tr>
  +        <td>{1}</td>
  +        <td>The sequence number of the message</td>
  +      </tr>
  +      <tr>
  +        <td>{2}</td>
  +        <td>The module that the message occured in</td>
  +      </tr>
  +      <tr>
  +        <td>{3}</td>
  +        <td>The type of the message</td>
  +      </tr>
  +      <tr>
  +        <td>{4}</td>
  +        <td>The description of the message</td>
  +      </tr>
  +    </table>
  +    <p>Here's an example of file logging that includes the date and
  +      time:</p>
  +<pre>
  +&lt;MLET CODE = "org.jboss.logging.FileLogging" ARCHIVE="jboss.jar" 
CODEBASE="../lib/ext/"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="Information,Debug,Warning,Error"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="<b>{0,date,yyyy-MM-dd} 
{0,time,hh:mm:ss}</b> [{2}] {4}"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE=""&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="FileName"&gt;
   &lt;/MLET&gt;
   </pre>
  +
  +    <h3><a NAME="limiting">Limiting Log Output</a></h3>
  +    <p>You can limit log output by severity for console logging,
  +      severity or source for file logging, or source for GUI logging.
  +      If you want to eliminate logging output altogether, remove the
  +      whole MLET entry from the <code>jboss.jcml</code> file.</p>
  +    <h4><a NAME="severity">By Severity</a></h4>
  +    <p>You can remove any of the four categories of log messages from
  +      the first parameter to console or file logging.  The available
  +      categories are Information, Debug, Warning, and Error.  Here's
  +      an example of console logging that shows only the most serious
  +      messages:</p>
  +<pre>
  +&lt;MLET CODE = "org.jboss.logging.ConsoleLogging" ARCHIVE="jboss.jar" 
CODEBASE="../lib/ext/"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="<b>Error</b>"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="[{2}] {4}"&gt;
  +&lt;/MLET&gt;
  +</pre>
  +    <h4><a NAME="source">By Source</a></h4>
  +    <p>The third parameter to file logging, or the only
  +      parameter for GUI logging, can be used to filter the log messages.
  +      If it is blank, all messages will be logged to this logger.
  +      If it has values (separated by semicolons), only messages whose
  +      module matches one of the values will be logged.  You can set
  +      up multiple file or GUI loggers with different filters, if you
  +      want to log messages from different beans to different files
  +      or windows.</p>
  +<pre>
  +&lt;MLET CODE = "org.jboss.logging.FileLogging" ARCHIVE="jboss.jar" 
CODEBASE="../lib/ext/"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="Information,Debug,Warning,Error"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="[{2}] {4}"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="<b>myBeanName1;myBeanName2</b>"&gt;
  +   &lt;ARG TYPE="java.lang.String" VALUE="FileName"&gt;
  +&lt;/MLET&gt;
  +</pre>
  +
   
       <h2><a NAME="jms">Configuring JMS</a></h2>
       <p><i>This section is forthcoming.</i></p>
  
  
  
  1.12      +8 -4      jbossweb/manual/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /products/cvs/ejboss/jbossweb/manual/index.html,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- index.html        2000/10/12 18:13:21     1.11
  +++ index.html        2000/10/18 18:07:43     1.12
  @@ -45,12 +45,16 @@
               <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="tc3"><a CLASS="plain" HREF="adv_config.html#poolex">Connection 
Pool Configuration Examples</a></p>
  -
  +        <p CLASS="tc2"><a CLASS="plain" 
HREF="adv_config.html#security">Security</a></p>
  +          <p CLASS="tc3"><a CLASS="plain" 
HREF="adv_config.html#db-security">Configuring a Security Database</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#console">Console 
Logging</a></p>
  +          <p CLASS="tc3"><a CLASS="plain" HREF="adv_config.html#file">File 
Logging</a></p>
  +          <p CLASS="tc3"><a CLASS="plain" HREF="adv_config.html#gui">GUI 
Logging</a></p>
  +          <p CLASS="tc3"><a CLASS="plain" 
HREF="adv_config.html#formatting">Formatting Log Output</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="tc4"><a CLASS="plain" HREF="adv_config.html#severity">By 
Severity</a></p>
  +            <p CLASS="tc4"><a CLASS="plain" HREF="adv_config.html#source">By 
Source</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>
  
  
  
  1.11      +3 -5      jbossweb/manual/warning.html
  
  Index: warning.html
  ===================================================================
  RCS file: /products/cvs/ejboss/jbossweb/manual/warning.html,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- warning.html      2000/10/10 04:18:30     1.10
  +++ warning.html      2000/10/18 18:07:43     1.11
  @@ -41,9 +41,10 @@
         </li>
         <li>Advanced Configuration
           <ul>
  +          <li>Need DB Security Configuration</li>
             <li>Need JMS Configuration</li>
  -       <li>Need specific configuration examples for DB/2, Sybase,
  -         PostgreSQL, and Interbase.</li>
  +       <li>Need specific configuration examples for DB/2 and
  +         Interbase.</li>
             <li>Need to try dynamic classloading to verify directions
               and get an exact procedure with security policy settings
               that are required.</li>
  @@ -115,9 +116,6 @@
           </ul>
         </li>
         <li>Examples
  -        <ul>
  -          <li>This section must be written</li>
  -        </ul>
         </li>
         <li>Troubleshooting
           <ul>
  
  
  

Reply via email to