WAS v8.5 > End-to-end paths > EJB applications

Implement EJB applications that use timers

In WebSphere Application Server, the EJB Timer Service implements EJB Timers as a new Scheduler Service task. By default, an internal (or pre-configured) scheduler instance is used to manage those tasks, and they are persisted to an Apache Derby database associated with the server process. Creation and cancellation of Timer objects are transactional and persistent. That is, if a Timer object is created within a transaction and that transaction is later rolled back, the Timer object's creation is rolled back as well. Similar rules apply to the cancellation of a Timer object. Timer objects also survive across application server shutdowns and restarts. We can also manage the EJB timer service for a specific EJB container

1. Migrate enterprise bean code to the supported specification.

   Subtopics...

   • Migrating enterprise bean code to the supported specification

   
   

2. Develop enterprise beans for the timer service.

   In WebSphere Application Server, the EJB Timer Service implements EJB Timers as a new kind of Scheduler Service task. By default, an internal (or pre-configured) scheduler instance is used to manage those tasks, and they are persisted to a Apache Derby database associated with the server process.

   Subtopics...

   • Develop enterprise beans
     
   • Develop entity beans
     
   • Create timers using the EJB timer service for enterprise beans
     

   
   

3. Assemble EJB modules for enterprise bean applications.

   Assemble an EJB module to contain enterprise beans and related code artifacts. Group web components, client code, and resource adapter code in separate modules. After the EJB module is assembled, install it as a stand-alone application or combine it with other modules into an enterprise application.

   Subtopics...

   • Deploy EJB modules
     

   
   

4. Deploy the EJB modules.

   When you deploy an EJB module, you install that module on a server that has been configured to support deployed modules. Assemble EJB modules assemble one or more web modules, and assemble them into a Java™ EE application.

   Subtopics...

   • Assemble EJB modules
     

   
   

5. Administer timer services.

   We can manage the EJB timer service for a specific EJB container through the WebSphere Application Server dmgr console. There are two ways to configure the timer service to share the same database across multiple servers.

   Subtopics...

   • Manage EJB containers
     
   • Administer session beans
     
   • Configure a timer service
     

   
   

6. Secure EJB 3 applications.

   We can protect enterprise bean methods by assigning security roles to them. Before you assign security roles, you need to know which EJB methods need protecting and how to protect them.

   Subtopics...

   • Secure Enterprise JavaBeans applications
     

   
   

7. Tune EJB applications.

   If we use applications that affect the size of the EJB container cache, it is possible the performance of the applications can be impacted by an incorrect size setting. It is important to know that entity beans are not supported in an EJB 3.0 module. One of the steps in tuning custom EJB container to optimum performance levels is to fine-tune the EJB cache.

   Subtopics...

   • Tune Enterprise JavaBeans applications
     

   
   

8. Troubleshoot EJB 3.x applications.

   Use these troubleshooting tips for problems related to accessing enterprise beans.

   Subtopics...

   • Troubleshooting Enterprise JavaBeans applications
     

+

Search Tips   |   Advanced Search