Replaced by set of courses 86115-86123

Course Code NGE86013

Contents

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

Screenshot

Description

This final course in the series teaches learners about transaction and security management. The transaction management sections cover the EJB semiautomated transaction management feature, container-managed transactions, bean-managed transactions and synchronization. The security management section addresses EJB architecture support for security management.

Audience

The intended audience for this course are system administrators, application developers, system analysts, software engineers, and programmers/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 concepts of EJB transactions and the types, advantages, and services provided by an EJB transaction.
• Identify the security threats and the mechanisms to counter them.
• Identify the security services, and the supporting features of security management for an EJB architecture.

Topics Include

Unit 1: EJB: Transaction

• Identify the situation in which a transaction is occurring.
• Identify the definition of a transaction.
• Identify the transaction property that is violated in a specified situation.
• Match various transaction participants with the tasks performed by them.
• Match the components of a transaction with the tasks performed by them.
• Match the problems that occur when multiple transactions simultaneously access a database with the situations in which they occur.
• Identify the transaction problem that is solved by a specified isolation level.
• Identify the situations in which distributed transactions are used.
• Label the process boxes in a flowchart with the steps involved in the two-phase commit approach used to manage distributed transactions.
• Sequence the steps to run a container-managed transaction.
• Match various transaction attribute values with the scopes that they provide to a business method.
• Identify the methods of the interfaces of the enterprise bean types for which the transaction attribute value must be specified.
• Identify the conditions in which a container-managed transaction rolls back.
• Match the methods of the UserTransaction interface used to manage a bean-managed transaction with their functions.
• Identify the scope provided to the various types of enterprise beans in a bean-managed transaction.
• Identify the functions of the SessionSynchronization interface.
• Match the methods of the SessionSynchronization interface with their functions.

Unit 2: EJB: Security

• Match security threats with the situations in which they occur in an enterprise environment.
• Match security identities with their features.
• Match the security attributes that are set in the deployment descriptor with their functions.
• Complete the code that is used to provide programmatic security logic to an enterprise application.
• Complete the security declaration of a specified role in the deployment descriptor of an enterprise application.
• Identify the situations in which secure authentication should be implemented in an enterprise environment.
• Complete the security declaration of a specified method permission in the deployment descriptor of an enterprise application.
• Match the entries in a deployment descriptor to declare method-driven authorization with the situations in which they are used.
• Identify the communication channel that is used in a specified situation.
• Identify the security-related services provided by the Enterprise Bean Provider.
• Identify the security-related services provided by an Application Assembler.
• Identify the security-related services provided by the Deployer.
• Identify the situations in which RMI should be implemented in an enterprise environment.
• Match RMI architectural entities with their functions.
• Identify the uses of object serialization.
• Identify the guidelines that are followed when implementing object serialization.
• Identify the guidelines for passing parameters by using Java RMI.
• Identify the underlying logic of the displayed piece of code that performs a step in RMI implementation.
• Match the security functions of an EJB container with the way in which they are implemented.
• Match security APIs with their functions.
• Identify the situations in which it is advantageous to merge RMI with CORBA.
• Sequence the steps that are performed to merge RMI with CORBA.
• Match the problems that arise when merging RMI and CORBA with their solutions.

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