Tuning the deployment of EJB applications

When the product deploys an enterprise bean (EJB) application, it searches for remote EJB beans. You can reduce the deployment time of applications that contain many EJB JAR files by setting the IBM-Enable-Remote-EJB-List attribute to true, even if your application does not contain any remote EJB beans.

About this task

When the product deploys an application, it searches for remote EJB beans by reading the class files in EJB JAR files to find classes or super classes that implement the java.rmi.Remote interface. For large applications with many EJB JAR files, this search can cause a significant delay in the deployment of the application.

In version 9.0.5.7 and later, you can specify the IBM-Enable-Remote-EJB-List and IBM-Remote-EJB-List attributes in your MANIFEST.MF file to enable and specify a list of remote EJB beans. When these attributes are present, the product uses the specified list instead of searching through the EJB JAR files. Even if your application does not contain any remote EJB beans, you can override the search behavior and improve deployment times by setting the IBM-Enable-Remote-EJB-List attribute to true without specifying any remote EJB beans.

Procedure

Set the IBM-Enable-Remote-EJB-List attribute to true in the MANIFEST.MF file of the application EAR file.
If the application does not contain remote EJB beans, no further steps are needed.
In the following example, the application does not contain any remote EJB beans. To override the search behavior, enable the remote EJB list without specifying any remote EJB beans by adding the following attribute to the META-INF/MANIFEST.MF file of the application:
```
IBM-Enable-Remote-EJB-List = true
```
Optional: If the application contains remote EJB beans, set the IBM-Remote-EJB-List attribute to equal a comma-separated list of the remote EJB bean names.
In the following example, an application contains two remote EJB beans, which are named remoteEJB1 and remoteEJB2. To override the search behavior and specify a list of remote EJB beans, add the following attributes to the META-INF/MANIFEST.MF file of the application:
```
IBM-Enable-Remote-EJB-List = true
IBM-Remote-EJB-List = remoteEJB1, remoteEJB2
```

Results

When the product deploys your application, it uses the specified remote EJB beans instead of searching through EJB JAR files. If no remote EJB beans are specified, the product skips the search. Either condition can improve deployment times for your EJB applications.