This course will provide each participant with an in-depth and comprehensive understanding of the BEA Service-Oriented Architecture and event-driven environment. This course will focus on the integration of SOA components, defining external SOA components (Databases, Web services, EJBs, AquaLogic Service Bus, etc), development of Web services, using messaging-enabled services, utilization of JMS, depict the role of the AquaLogic Service Bus, using the message brokers, SOA security integration, building publisher and subscriber applications, durable and non-durable event processing, using adapter components, depict usage of BAM, BAM monitoring, development of SOA components using ALBPM Studio IDE and the deployment of client proxies.

All aspects of this class will incorporate the specific architecture of the BEA ALBPM SOA Suite to illustrate the implementation of these techniques.

Prerequisites

Each student should have a basic understanding of application development and design methodologies.

Class Format

Lecture and Lab

Audience

Targeted towards Business Process Developers, Programmers and Architects that need to understand how to develop and implement SOA and event-driven architectures in ALBPM.

Learning Objectives

After completing this course, the student should be able to:

• Understand the development and integration of external services (Java, .NET, Web Services, etc).
• Depict the integration of services in an event-driven environment
• Illustrate the integration of enterprise business processes
• Understand the deployment to AquaLogic Service Bus and accessing services deployed to the ALSB
• Demonstrate both the Publisher and Subscriber model types
• Illustrate the implementation of an ALSB Bus and a Message Broker
• Understand the role of sensors and notification services
• Incorporate human task functionality in a business process
• Demonstrate the incorporation of external resources (SQL, ALSB, Java, COM, .NET, SAP, etc)
• Depict security issues related to Web Services (SAML, SSO, encryption and digital signatures)
• Use of client specific adapters for accessing legacy components
• Demonstrate the usage of XSLT transformations between Web services
• Depict the integration of BAM into an SOA event architecture
• Demonstrate the client proxy components and their implementation