Developing integration solutions using XML, JMS, and Message Driven Bean with BEA WebLogic Server 6.0 Developers Course Syllabus

Audience:

This course is the third in a series of three five-day J2EE developer courses offered by Aurora Information Systems, Inc. This technical course is intended for Java programmers, Java architects, and system designers who will be developing integration solutions using J2EE technologies and BEA WebLogic Server 6.0.

Covered J2EE Specifications:

JMS1.0.2.
EJB 2.0 (Message Driven Bean)

Course Objectives:

Upon completion of this Aurora Information Systems course, students will be able to design and develop Enterprise applications using the following technologies:

• JMS
• EJB (Message Driven Bean)
• XML and Wireless technologies

Students will be able to discuss real-world design objectives and pitfalls, and they will have built a real-world integration solution using JMS, MDB, and XML in the lab exercises.

Prerequisites:

• Java Programming Skill and understanding of Object Oriented Design concepts.
• Experience using JDBC for connectivity to databases.
• Basic understanding of Internet based applications.
• Familiarity with EJB, Servlets and JSPs programming.

Course Contents

This section will discuss different types of application architectures and the differences between monolithic, client/server, and n-tier architectures. This is followed by a discussion on the role of J2EE for creating n-tier Web based applications. All of the J2EE components are briefly described. JMS is discussed in detail in the following sections.

This is a lecture and lab section where students are introduced to the BEA WebLogic application server. This section teaches about important property files, console screens, and utilities that are required to administer WebLogic Server 6.0.

This section provides a good introduction to XML and its use in the B2B application environment, via lecture and lab exercises. Students will be taught the importance of XML using real world examples.

This section teaches important topics like well-formed XML, Cascading style sheets (CSS), XSLT, Document Object Model (DOM), Simple API for XML (SAX), XML/database integration schemas, and Document Type Definitions (DTDs). Namespaces will also be discussed.

JNDI is one of the important components for developing Enterprise based applications. The JNDI implementation in BEA WebLogic server, and the JNDI APIs that will be used to bind and lookup objects, are discussed in detail.

JDBC connection pooling allows Enterprise applications to share database connection resources. This section also discusses how database connection pooling is handled using BEA WebLogic Server.

Throughout this course, students will develop a full-blown integration and content management solution for a B2B application. This section of the course will explain the architecture and design that is going to be used and what can be expected from this application. This will provide a very good idea of what will be achieved in the following sections. By explaining the architecture at this early stage, students will be able to relate the subsequent discussions on different technologies to this demo application. From this point onwards all lab exercises will focus on building this demo application.

In this section, students are introduced to the Java Message Service. The differences between RPC and asynchronous messaging will be discussed. A lab will be completed by the students showing the usage of JMS APIs and the anatomy of JMS messages.

The Publish-and-Subscribe messaging model will be analyzed. This section will include a discussion on durable subscriptions and publishing the messages persistently.

Like the previous section, this section will analyze the Point-to-Point messaging model and will include discussions on dynamic queues and load balancing.

Global transactions that span more than one resource are absolutely required in today’s n-tier, distributed applications. In this section, students are introduced to the X/Open XA model and to the ACID properties of a transaction. This section includes a discussion about how we can enable transactions to achieve guaranteed messaging.

This section focuses on the EJB architecture and its implementation in BEA WebLogic server.
Note: To prepare for this section and the rest of the course, it is suggested that the student already have some knowledge of EJB development. If you do not already have this knowledge, may we suggest attending the Aurora Information Systems J2EE EJB 2.0 course.

The EJB 2.0 specification has integrated EJB and JMS tightly. Message Driven Beans will be discussed in detail. In the lab exercise, students will implement Message Driven Beans for the demo application.

In this section, students are introduced to wireless technologies such as WAP, WML, gateway servers, etc. Included is a discussion on XSLT transformation to support multiple client types.

Students will implement Servlet and JSP clients to generate HTML and WML for the JMS demo application. Students will deploy the entire demo application in the BEA WebLogic server, and XML messages will be used to demonstrate the application’s capabilities.

Note: Students are not explicitly taught about Session/Entity EJBs. Please see our J2EE EJB 2.0 developers course.