|
|
Service Oriented
Architecture and Web Services This course provides a strong understanding of Service Oriented Architecture (SOA) and Web Services. It is an architectural course that paints a good, high-level picture of what SOA is and how it may be leveraged for solution integration across platforms. You will get an architectural overview of what SOA is, SOA’s association and relationship to Web Services, XML and its role in SOA, Security and Transaction considerations, among others. Each section introduces and explains a concept or technology, followed, as relevant and necessary, by an interactive coding section to help you understand the concept. You may then be given an opportunity to run lab exercises that reinforce the concepts and coding that you have just learned. Target Audience: §
Java
developers who wish to understand and implement SOA based enterprise solutions §
Technical
Architects who are planning on using SOA for enterprise solutions Prerequisites: Required
§
Basic knowledge of XML (Schema’s and XML document
instances; parsing) and HTTP (submitting browser based form data and
request to a Web Server using
the HTTP protocol; difference between GET and POST, etc.) Recommended §
Strong understanding of
Object-Oriented (OO) concepts and OO programming §
Distributed computing concepts
and architectures, such as Client-Server or 3/n-tier. §
Experience developing
server-side applications using any technology/language Course Objectives: At the end of this course,
attendees will be able to make architectural decisions regarding when it is
appropriate and when it is not appropriate to build/leverage SOA solutions. They will also be able to
implement SOA solutions using RESTful or Web Service
technologies, with a good understanding of each of these implementation
technologies. * What Service Oriented
Architectures are all about. * The relationship between
SOA’s and Web Services * Integration and
Interoperability of heterogeneous implementations * SOA and Business Process
Management * SOA and Message Exchange
Protocols (MEPs) * Security and Transaction
considerations Course Outline: §
What is a
Service and what is Service Oriented Architecture? o
Fundamental
concepts of SOA §
SOA’s defined §
Purpose and
need for SOA (Business Benefits) §
SOA Principles
§
Stateless and Stateful Services o
Benefits of
using SOA and technical considerations §
Technical
Benefits of SOA §
InterOp between
Disparate implementations – what are the §
J2EE and .NET interOp considerations §
SOA and Web
Services o
The Web
Service Platform and service Contracts §
Web Service
Platform and its elements §
Service
Contract elements and Principles §
Service level
Data Model §
Service level
communication and option §
WSDL, SOAP,
etc. §
Tools for
implementing Web Services §
Security and
Transactional considerations o
Integration
using SOA §
The §
More on J2EE
and .NET interOp. §
RESTful services o
REpresentational State
Transfer Architectural style o
Implementing
REST (Web) Services §
SOA and
multi-channel access o
Benefits of
Multi-channel access o
Architecture
for Multi-channel access §
Business
Processes and SOA o
Business
Process Management and Web Services o
Composing Web
Services o
Orchestration
and Choreography Specification §
SOA and Web Services
Security o
Threats and
Challenges o
Securing the
communication layer o
Message-level
security §
WS-Security §
SOA and Web
Services Transaction processing o
WS Transaction
specifications o
Protocols and
coordination §
Advanced
Messaging and Message Exchange Protocols (MEPs) o
Reliable
Messaging o
WS-Events and
WS-Notification o
Mobile clients Course Duration: §
This course
may be tailored for a four day or a five day offering. §
The four day
version spend less time on the SOA and Web Services section (topics such as WS-*,
including WS-security and WS-transaction will not be covered in as much depth
as in the five day session). §
In general,
the five day class will be more detail oriented compared to the four day class
which will be an overview. There will be more hands on labs in the five day
version than in the four day version | |
|
 |
 |
