<commit_before><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<chapter id="jboss">
  <title>JBoss AS Crash Course</title>

  <para>The JBoss Application Server (AS7) is the foundation upon which
  TorqueBox is built. You can go a long way with TorqueBox without knowing
  anything about the administration of JBoss AS, but for advanced
  applications, it's worth knowing something about how AS is configured and
  extended. Feel free to skip this section if you're just getting started with
  TorqueBox, and use it as a reference later.</para>

  <section id="configuring-jboss">
    <title>Configuring</title>

    <para>JBoss folder structure now has expressive changes since previous
    releases, the most visible comes to folder structure and runtime modes:
    <emphasis role="bold">domain</emphasis> and <emphasis
    role="bold">standalone<emphasis>. In this release of Torquebox, just
    standalone mode is available, domain mode support will come to the next
    releases.</emphasis></emphasis></para>

    <para><emphasis role="bold"><emphasis role="bold"><emphasis>Now in JBoss,
    all server configuration profile is concentrated <emphasis>in</emphasis>
    <emphasis><filename>standalone/configuration</filename></emphasis><emphasis>
    path</emphasis> through </emphasis>standalone.xml<emphasis> file, making
    admin tasks more easier to maintenance.
    </emphasis></emphasis></emphasis></para>

    <para><mediaobject>
        <imageobject>
          <imagedata align="center" fileref="images/jboss-server.png"
                     format="PNG" />
        </imageobject>
      </mediaobject></para>

    <para>TorqueBox uses default mode from standalone runtime. A stock JBoss
    distribution will come with others, as you see above, custom profiles will
    come up in the next releases.</para>

    <para>Some libraries and config files are common to all server
    configurations. To conserve disk space, these are kept in the
    <filename>modules/</filename> directory. This is, in fact, where the
    TorqueBox deployers reside.</para>

    <para>All configuration profiles have a common structure, and usually
    include the following directories: <filename>conf/</filename>,
    <filename>lib/</filename>, <filename>deployers/</filename>, and
    <filename>deploy/</filename>. In general, it isn't a good idea to remove
    anything from these directories that you didn't put there yourself.</para>

    <para><mediaobject>
        <imageobject>
          <imagedata align="center" fileref="images/jboss-default.png"
                     format="PNG" />
        </imageobject>
      </mediaobject></para>

    <para>In addition, some directories are created automatically at runtime,
    as needed: <filename>tmp/</filename>, <filename>work/</filename>,
    <filename>data/</filename>, and <filename>log/</filename>. Though not
    typically necessary, you may safely delete these when the server is not
    running to clear its persistent state.</para>
  </section>

  <section id="running-jboss">
    <title>Running</title>

    <para>The <filename>$JBOSS_HOME/bin/</filename> directory contains the
    main JBoss entry point, <filename>standalone.sh</filename> (or
    <filename>standalone.bat</filename>), along with its config file,
    <filename>standalone.conf</filename>. Running the JBoss server is simple:
    <screen> <prompt>$</prompt> <command>$JBOSS_HOME/bin/standalone.sh</command> </screen></para>

    <para>Permanent runtime configuration of JBoss should go in
    <filename>bin/run.conf</filename>. For example, your application may
    require more memory (RAM) than the default allocated. Edit
    <filename>run.conf</filename> to increase the value of
    <option>-Xmx</option> to something reasonable.</para>

    <para>Though <xref linkend="capistrano-support" /> doesn't strictly
    require it, in production you may prefer to control JBoss via a Unix "init
    script", examples of which may be found in <filename>bin/</filename>. Feel
    free to tweak one for your particular OS.</para>
  </section>

  <section id="deploying-to-jboss">
    <title>Deploying</title>
<commit_msg>Fixing configuration file name, inside running section<commit_after><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<chapter id="jboss">
  <title>JBoss AS Crash Course</title>

  <para>The JBoss Application Server (AS7) is the foundation upon which
  TorqueBox is built. You can go a long way with TorqueBox without knowing
  anything about the administration of JBoss AS, but for advanced
  applications, it's worth knowing something about how AS is configured and
  extended. Feel free to skip this section if you're just getting started with
  TorqueBox, and use it as a reference later.</para>

  <section id="configuring-jboss">
    <title>Configuring</title>

    <para>JBoss folder structure now has expressive changes since previous
    releases, the most visible comes to folder structure and runtime modes:
    <emphasis role="bold">domain</emphasis> and <emphasis
    role="bold">standalone<emphasis>. In this release of Torquebox, just
    standalone mode is available, domain mode support will come to the next
    releases.</emphasis></emphasis></para>

    <para><emphasis role="bold"><emphasis role="bold"><emphasis>Now in JBoss,
    all server configuration profile is concentrated <emphasis>in</emphasis>
    <emphasis><filename>standalone/configuration</filename></emphasis><emphasis>
    path</emphasis> through </emphasis>standalone.xml<emphasis> file, making
    admin tasks more easier to maintenance.
    </emphasis></emphasis></emphasis></para>

    <para><mediaobject>
        <imageobject>
          <imagedata align="center" fileref="images/jboss-server.png"
                     format="PNG" />
        </imageobject>
      </mediaobject></para>

    <para>TorqueBox uses default mode from standalone runtime. A stock JBoss
    distribution will come with others, as you see above, custom profiles will
    come up in the next releases.</para>

    <para>Some libraries and config files are common to all server
    configurations. To conserve disk space, these are kept in the
    <filename>modules/</filename> directory. This is, in fact, where the
    TorqueBox deployers reside.</para>

    <para>All configuration profiles have a common structure, and usually
    include the following directories: <filename>conf/</filename>,
    <filename>lib/</filename>, <filename>deployers/</filename>, and
    <filename>deploy/</filename>. In general, it isn't a good idea to remove
    anything from these directories that you didn't put there yourself.</para>

    <para><mediaobject>
        <imageobject>
          <imagedata align="center" fileref="images/jboss-default.png"
                     format="PNG" />
        </imageobject>
      </mediaobject></para>

    <para>In addition, some directories are created automatically at runtime,
    as needed: <filename>tmp/</filename>, <filename>work/</filename>,
    <filename>data/</filename>, and <filename>log/</filename>. Though not
    typically necessary, you may safely delete these when the server is not
    running to clear its persistent state.</para>
  </section>

  <section id="running-jboss">
    <title>Running</title>

    <para>The <filename>$JBOSS_HOME/bin/</filename> directory contains the
    main JBoss entry point, <filename>standalone.sh</filename> (or
    <filename>standalone.bat</filename>), along with its config file,
    <filename>standalone.conf</filename>. Running the JBoss server is simple:
    <screen> <prompt>$</prompt> <command>$JBOSS_HOME/bin/standalone.sh</command> </screen></para>

    <para>Permanent runtime configuration of JBoss should go in
    <filename>bin/standalone.conf</filename>. For example, your application
    may require more memory (RAM) than the default allocated. Edit
    <filename>standalone.conf</filename> to increase the value of
    <option>-Xmx</option> to something reasonable.</para>

    <para>Though <xref linkend="capistrano-support" /> doesn't strictly
    require it, in production you may prefer to control JBoss via a Unix "init
    script", examples of which may be found in <filename>bin/</filename>. Feel
    free to tweak one for your particular OS.</para>
  </section>

  <section id="deploying-to-jboss">
    <title>Deploying</title>

{'fraction_non_alphanumeric': 0.1101764224792616, 'fraction_numerical': 0.0018693772636990303, 'mean_word_length': 3.8388920293951383, 'pattern_counts': {'":': 0, '<': 229, '<?xml version=': 2, '>': 229, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 6}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7375146', 'n_tokens_mistral': 2433, 'n_tokens_neox': 2272, 'n_words': 822}