Chapter 2. EJB Engine

Table of Contents

2.1. Overview
2.2. Major Functions
2.3. EJB Engine Directory Structure
2.4. EJB Engine Configuration
2.4.1. Configuring Basic EJB Options
2.4.2. Configuring Active Management
2.4.3. Configuring Timer Service
2.5. System Log Configuration
2.6. Controlling and Monitoring of EJB Engine
2.7. EJB EngineTuning
2.7.1. Tuning Engine Resolution
2.7.2. Fast Deploy
2.7.3. Configuring System Log for Maximum Performance
2.7.4. Not Using Active Management
2.7.5. Using the HTTP Invoke Mode

This chapter describes basic knowledge of the EJB engine. It also describes the top-level concepts of JEUS EJB, such as its structure, configuration, operation, monitoring, and tuning.

The JEUS EJB engine provides a runtime environment for EJB. The term EJB Container used in the EJB standard is equivalent to the term EJB engine that will be used throughout this manual. For more information about EJB modules and EJB deployment, refer to "Chapter 3. EJB Module" and "Chapter 4. Common Characteristics of EJB".

The following explains major functions of the EJB engine.

  • Main EJB Engine Settings

    The main configuration file for the EJB engines is <ejb-engine> in domain.xml.

    More information will be discussed in "2.4. EJB Engine Configuration".

  • EJB Engine Logging

    Logs can be written on MSs according to the setting in domain.xml, but a user can also keep a separate EJB engine log (jeus.ejb). Even if a separate EJB engine log is used, the EJB engine log is also recorded in the MS log .

    When a file handler is configured in the log handler, the log file is created using the specified file name. It is also possible to display any log messages using a console handler. Normally, in this case, the log messages will be displayed on the command screen, where the MS was started, through the pipe.

    Note

    A user-generated user handler can also be registered. For more information, refer to JEUS Server Guide. "Chapter 8. Logging".

The following figure shows directories and files used to manage EJB engines.


Basic directories are the same as "1.3.1. Directory Structure". Main directories used by an EJB engine are as follows:

bin

Contains the tool for managing EJB engines.

EJB Engine Management ToolDescription
appcompilerCreates classes necessary to deploy EJB, compiles and fast deploys the classes
jeusadminUsed to control and monitor an EJB engine.

domains/<domain name>/servers/<server name>/logs

The directory where the log files of EJB engine are stored. If a separate file handler is specified, a separate file will be created, otherwise, the setting in the server log configuration file will be followed.

This section explains how to configure EJB engines using the WebAdmin.

EJB engine configuration using the WebAdmin is divided into three sections as follows. The specified settings are stored in the domain.xml file, located in the JEUS_HOME/domains/<domain name>/config directory.

  • Basic

  • Active Management

  • Timer Service

The following example configures the basic settings of the EJB engine using the WebAdmin.

  1. Click [Servers] on the left pane to go to the Server List page. Select a server from the list to go to the Server page. Select an EJB Engine to configure the basic settings in [Engine] > [Ejb Engine] > [Basic].

  2. Click [Lock & Edit] to change to the edit mode.

  3. Configure the basic EJB engine options and then click [OK].


    The following table describes the configuration items of Basic Option and Advanced Option by section.

  4. Click [Apply Changes] to dynamically apply the changes.

Active Management setting consists of the engine restart and email notification options. Engine restart condition is determined according to the maximum number of blocked EJB threads allowed before the EJB engine is restarted.

The following example configures the Active Management setting of an EJB engine using the WebAdmin.

  1. Click [Servers] on the left pane to go to the Server List page. Select a server from the list to go to the Server page. Select an EJB Engine to configure its Active Management setting in [Engine] > [Ejb Engine] > [Active Management].

  2. Click [Lock & Edit] to change to the edit mode.

  3. Configure the Active Management options and then click [OK].


    The following table describes the configuration items of Basic Option and Advanced Option by section.

  4. Click [Apply Changes] to dynamically apply the changes.

System logging and user logging for the EJB engine are configured using the following WebAdmin menus.

System logging and user logging of the EJB engine are configured in the JEUSMain.xml file.

  • Configuring System Logging

    Go to [Servers] > Select a server > [Basic] > [System Logging].

  • Configuring User Logging

    Go to [Servers] > Select a server > [Basic] > [User Logging].

These are common configurations applied not only to the EJB engine but also to all the other engines. Refer to the JEUS Server Guide. "Chapter 8. Logging".

Controlling the EJB engine is identical to controlling any other kind of JEUS engine (e.g., the Servlet and JMS engines).You may use either the console tool or WebAdmin.

Monitoring is essentially gathering runtime data and status information about a particular EJB engine. The following describes how to control and monitor EJB engines using the WebAdmin.

  • Controlling EJB engines

    Click [Servers] on the left pane to go to the Server List page. Select a server from the list to go to the Server page. Select the EJB engine to monitor in [Engine] > [Ejb Engine]

  • Monitoring EJB engines

    Click [RUNTIME INFO] in WebAdmin. Select an EJB engine to monitor in the same way as for controlling an EJB engine.

There are a number of configuration settings that can be tweaked to increase the overall performance of individual JEUS EJB engines. In this section, we will briefly touch the following performance-related settings of the EJB engine.

The following are required for tuning purposes.

  • Tuning the resolution setting

  • Using the fast-deploy feature

  • Setting up the system log for optimal performance

  • Not using Active Management

  • Using the HTTP invoke mode

Note

For more information or tips about the EJBMain.xml file, refer to "11. domain.xml EJB Engine Configuration" section of the JEUS XML Reference. In the XML/Schema, those names marked with 'P' are related to performance.