|
 |
 |
 |
|
|
 |
|
|
Mastering IBM VisualAge for Java |
Duration: 4 days |
|
|
Java developers |
|
Experience with Java is a prerequisite for this course. Exposure to Servlets and Java Server Pages (JSP) is recommended. |
|
|
Description |
This 4 day course covers everything a Java developer needs to know to become a hyper productive VisualAge programmer. IBM VisualAge for Java Enterprise Edition is a very powerful, complex development environment, yet it is often underutilized in practice. This course has a goal to demystify VisualAge and enable developers to effectively use the tools and dramatically improve speed and quality of development of enterprise applications.
The participants will learn the techniques and best practices in using the tools for development of web-based, standalone, and server side applications. Besides examining the program development tools, the course explains the team development with VisualAge and goes through practices of collaborative development with a shared repository. Through the numerous examples and exercises, the developers will gain proficiency with the tools and reinforce the best practices of Java development.
Practical labs represent 70% of this course. |
|
Objectives |
This hands-on
course demystifies VisualAge for Java Enterprise Edition and enables
developers to increase their productivity by using rich set of
tools from the development environment.
On completion
of this course, students will be able to:
- Efficiently
develop software using VisualAge for Java Enterprise Edition
- Use version
control system on the projects
- Participate
in the team development with a shared repository
- Reduce the
development and debugging time by using the debugger
- Develop Servlets,
Java Server Pages and EJBs in the VisualAge for Java
- Use object-relational
database mapping tools
- Develop faster
using visual composition tools
- Use XML tools
from the VisualAge
- Apply best
practices of Java development through VisualAge
|
|
Course Outline |
VisualAge Integrated
Development Environment
- Repository
- Workspace
- Resource files
- Scrapbook
- Customizing VisualAge
for Java
Creating Programs
and Program Elements
- Solutions
- Projects
- Applications
and Applets
- Methods
and Fields
- Servlets
and Java Server Pages
- Additional
VisualAge Functions
- Reorganizing
Programs
- Exporting
Code
Version Control
in VisualAge
- Editions and Versions
- Managing Editions
- Comparing Editions
- Merging Editions
- Releasing Editions
- Scratch Editions
- Versioning and
Resource Files
Team Development
- Collaborative
Development
- Team Client/Server
Configuration
- Repository Server
(EMSRV)
- Ownership and
Team Roles
- Team Development
Scenarios
- External Version
Control
- Best Practices
in Team Development
Debugging in VisualAge
- Debugging Actions
and Breakpoints
- Configuring Conditional
Breakpoints
- Configuring Exceptions
- Code Modifications
While Debugging
- Evaluating Expressions
- Generating Class
Trace
WebSphere Test
Environment (WTE)
- WebSphere Test
Environment Architecture
- Servlets and JSP
in WebSphere Test Environment
- Using Services
in WTE
- Creating and Configuring
Web Applications
- Creating and Configuring
Data Sources
|
|
EJB Development
Environment
- EJB Overview
- Associations and
Inheritance
- Mapping to Databases
- Editions and Versioning
- Team Development
and EJB
Object Persistence
- Persistence Framework
Overview
- Persistence Builder
Tools
- Defining Object
Models, Schemas and Data Store Maps
- Application Organization
and Persistence Builder
- Managing Persistent
Objects
- Object Persistence
and EJB
Visual Composition
- Concepts of Visual
Programming
- Java Classes and
Java Beans
- Connections
- Visual, Nonvisual
and Composite Beans
- Visual Composition
of Beans
- Component Palettes
- Property Sheets
- Layout Managers
- Best Practices
in Visual Composition
XML Support in
VisualAge for Java
- XML Generator
- IBM XML Parsers
- UML Integration
Through XMI Toolkit
External Tool
Integration
- Setting Up Components
for Integration
- Setting Up Integration
Tools
- Managing Components
for Integration
- Tool Integrator
API
- Remote Tool Integration
Case Study
|
|
|
|