Deployer's Guide

Target audience

The target audience for this guide is the deployer. The deployer is responsible for the deployment of Enterprise Beans and their containers in the EJB server.

The deployer may customize the Enterprise Bean in order to adapt it to the specific operational environment.

Deployment process description

The input of the deployer is an ejb-jar file provided by the bean provider. The deployment process consists of: The following sections describe the deployment process without customization, then the deployment process with customization. The person responsible for the deployment process will make use of several tools provided with the platform, GenIC, GenDD and DumpDD.

Deployment process without customization

    The deployer can work directly with the ejb-jar file It is supposed that the JOnAS product is correctly installed (in a directory JONAS_ROOT), and that the PATH environment variable is correctly set.
     

Deployment process with customization

It is typically the case that the deployer wants to adapt the bean to the local environment. The deployer may intend to read the attribute setting in the Enterprise Bean's deployment descriptor in order to modify the values of the Enterprise Bean's environment properties.

In the first version of the product there is no graphical tool to update a deployment descriptor. There are two tools, GenDD and DumpDD, the former is able to generate a serialized deployment descriptor from a textual description, the latter is able to generate a textual description in a file from a serialized deployment descriptor.

Example:

Suppose that the ejb-jar file is named "eb.jar" and contains a serialized deployment descriptor in which the deployer intends to change the name of the database table used to handle the persistence of the AccountImpl bean (see examples/src/eb).