Replaced by set of courses 86115-86123

Course Code NGE86012

Contents

1. Contents
2. Description
3. Audience
4. Prerequisites
5. Objectives
6. Topics Include
7. Duration
8. Minimum Requirements
9. Media

Screenshot

Description

This second course teaches the functions of and differences between session and entity beans. It describes the life cycle for each of these beans and it teaches learners how to implement the beans in enterprise applications.

Audience

The target audiences for this course are System Administrators, Application Developers, System Analysts, Software Engineers, and Programmer/Analysts. Learners should be experienced with object-oriented design and the Java programming language. It would be helpful for learners to be familiar with distributed programming (multi-tier architecture), relational or object database programming, transactions, and component technology.

Prerequisites

(Currently no course prerequisite information)

Objective

• Identify the components of a session bean.
• Identify the life cycle and creation of the types of session bean.
• Identify the deployment of a Session bean.
• Identify how to develop and deploy an entity bean.

Topics Include

Unit 1: Session Bean

• Identify the features of a session bean.
• Match the session bean components with their functions.
• Identify the code for creating a session bean remote interface.
• Identify the code for creating a session bean home interface.
• Complete the code for creating a session bean class by selecting the appropriate lines of code.
• Sequence the stages in the life cycle of a stateless session bean.
• Complete the code for creating a stateless session bean by selecting the appropriate lines of code.
• Sequence the stages in the life cycle of a stateful session bean.
• Complete the code for creating a stateful session bean by selecting the appropriate lines of code.
• Deploy a stateful session bean by using Application Deployment Tool.
• Identify the situation in which a specified type of session bean is used.
• Identify the uses of the swapping mechanism.

Unit 2: Entity Bean

• Identify the features of an entity bean.
• Identify the advantages of using an entity bean instead of accessing a database directly.
• Sequence the methods that are invoked during the life cycle of an entity bean.
• Identify the situations in which reentrancy occurs in threads.
• Identify how a session bean interacts with an entity bean in a specified scenario.
• Match the components of entity beans with their functions.
• Complete the code for creating an entity bean remote interface by selecting the appropriate lines of code.
• Identify the code for creating an entity bean home interface.
• Complete the code for creating an entity bean class by selecting the appropriate lines of code.
• Complete the code for creating an entity bean primary key class by selecting the appropriate lines of code.
• Identify the features of container-managed persistence.
• Identify the code for developing the different components of a container-managed entity bean.
• Sequence the steps in which an EJB container accesses the internal data stored in a container-managed entity bean.
• Identify the situations in which bean-managed persistence is preferred to container-managed persistence.
• Identify the code for developing the methods of the bean class of bean-managed persistence.
• Complete the code to define finder methods in bean-managed persistence by selecting the appropriate code.

Duration

8

Minimum Requirements

The CDROM version of this course requires:

• At least a 486DX 33Mhz CPU.
• Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
• At least 8MB RAM.
• At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).
• At least a double speed CDROM drive.
• An MPC compliant sound card with attached speakers or headphones is recommended (Currently, only the CDROM version supports audio).

• At least a 486DX 33Mhz CPU.
• Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
• At least 8MB RAM and 22MB available hard disk space or file server space.
• At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).

Media