Tuning the Engine for J2EE Scenarios

Purpose

When running particular J2EE applications on the J2EE Engine, you can tune it to better fit the particular needs or your business scenario.

To configure the system for a particular business scenario, you must be aware of which server components the application uses. The configuration settings suggested here must be thoroughly tested before applying them on productive systems.

Implementation Considerations

The J2EE Engine may be tuned for a particular application deployed on the server. The architecture of the engine is component-based – that is, it comprises multiple services, libraries, and interfaces, which build up the middleware features of the server on top of the core system modules. For more information, see SAP J2EE Engine System Architecture.

This component-based approach enables you to choose those components that your application utilizes, and save resources by switching off some of the services that the application does not need.

This does not apply to the SAP Java Enterpise Runtime and the core services in the engine. The core services provide basic functions such as security, administration, logging, cluster communication, naming services, and so on. For core services the Core Service indicator in the Additional Info tab of the service in the Visual Administrator is enabled.

In addition, you can configure the components that your application needs to utilize the available resources optimally.

Features

This section provides recommendations for tuning the following J2EE Engine components:

·        Web Container

·        EJB Container

·        Remote communication with RMI-IIOP and RMI-P4

·        Database connectivity

·        JMS Provider

Note that the proper functioning of the applications on the J2EE Engine depends extensively on its proper design. Therefore, some of the sections that follow contain references to design- and development-time issues.