<?xml version="1.0" encoding="UTF-8"?>
<section version="5.0" 
         xmlns="http://docbook.org/ns/docbook" 
         xmlns:xlink="http://www.w3.org/1999/xlink" 
         xmlns:xi="http://www.w3.org/2001/XInclude" 
         xmlns:svg="http://www.w3.org/2000/svg" 
         xmlns:mml="http://www.w3.org/1998/Math/MathML" 
         xmlns:html="http://www.w3.org/1999/xhtml" 
         xmlns:db="http://docbook.org/ns/docbook" 
         xml:lang="en"
         xml:id="deploy.principes">

  <info><title>The deployment and installation of Enterprise Beans</title></info>
      
      <para>
        This guide assumes that the Enterprise Bean provider followed the Enterprise Beans Programmer's Guide and packaged the beans's classes together with the deployment descriptors in a ejb-jar file. To deploy un-packed Enterprise Beans, refer to 
        <link xlink:href="configuration_guide.html#config.ejb">
          Configuring EJB Container service
        </link>
        . 
      </para>
      <para>
        To deploy the Enterprise Beans in JOnAS, the deployer must add the interposition classes interfacing the EJB components with the services provided by the JOnAS application server. 
         The 
        <link xlink:href="command_guide.html">
          GenIC
        </link>
         tool supplied in the JOnAS distribution provides the capability of generating interposition classes and updating the ejb-jar file. 
         The application deployer may also need to customize the deployment descriptors in order to adapt it to a specific operational environment. This must be done before using GenIC.
      </para>
      <para>
        The deployer may choose to deploy the Enterprise Beans as stand-alone application components, in which case the ejb-jar must be installed in the 
        <code>
          $JONAS_ROOT/ejbjars
        </code>
         directory. The deployer may also choose to include them in war or ear packaging, which is presented in the following sections.
      </para>
    </section>