Faites confiance à votre formation en TI |
Oracle University reconnaît ExitCertified comme Partenaire en formation de l’année en Amérique du Nord.
ExitCertified renforce sa relation avec Red Hat en obtenant le statut de revendeur avancés.
Oracle University décerne à ExitCertified le prix de Qualité exceptionnelle des instructeurs.
ExitCertified en vedette dans le répertoire des Entrepreneurs dynamiques du 21e siècle.
ExitCertified est mis en candidature une troisième fois pour les prix de la Chambre de commerce.
ExitCertified élargit sa relation avec Apple en ajoutant la diffusion de formation agréée Mac OS à Phoenix, en Arizona.

 |
Mastering Core Web Services and SOA for J2EE (or JEE) Developers (TT7301) |
 |
|
| Format: Formation en classe avec formateur |
| Autres formats: |
|
|
|
 |
|
|
| |
Geared for experienced developers, Mastering Core Web Services and SOA for JEE Developers is a four day, lab-intensive web services training course that introduces developers to the core standards that enable Web Services and the fundamentals of Service Oriented Architectures (SOA). The course presents a clear portrait of how a service orientation can fundamentally change the dynamics of how software is developed and "lives" within an enterprise. |
|
|
|
|
|
|
 |
 |
 |
 |
Compétences acquises |
| |
Today's development environments are increasingly dominated by sophisticated tooling that makes the initial development of web services less arduous. The production-level implementation, deployment, and maintenance of web services are far more complex and demanding.
Mastering Core Web Services and SOA for J2EE (or JEE) Developers focuses on providing an understanding of the fundamental technologies used in web services. This understanding is critical to being able to diagnose, troubleshoot, tune, and perform other lifecycle activities.
Working in a dynamic, interactive discussion and hands-on programming environment, let by our expert web services education team, developers will learn to: |
| |
Understand and apply the basic concepts of SOA to the identification and design of web services
Understand and intelligently discuss Web Services and the core technologies involved
Understand and apply the basic concepts of SOA to the identification and design of web services
Appreciate the concept of layered services including orchestration
Understand and intelligently discuss Web Services and the core technologies involved
Design, develop, and deploy real-world J2EE Web Services
Expose existing Java components as XML Web Services
| |
Write Java components that access remote Web Services hosted by a third party
Read and understand a WSDL document
Parse, process, and respond to a SOAP message
Understand the concepts behind REST and implement a REST-based web service
Implement handlers to inject cross-cutting solutions for security, logging, auditing, and other needs
Work with WS-Security to protect content, resources, and other assets | |
 |
 |
 |
 |
Qui peut en profiter |
| |
This is an introductory to intermediate level web services training course, designed for Java developers and architects who need to identify, design, and implement web services. We will explore and apply the terminology, the specification, the processes and technologies specific to web services. |
 |
 |
 |
 |
Préalables |
| |
Students should have 1-2 years of working knowledge with Servlets and JSPs, and should be familiar with XML, Namespaces, and XML Schema. |
|
|
|
| |
 | Ce cours de qualité supérieure est donné par des formateurs certifiés.
Il y a une différence. Découvrez-la  |
|
 |
| Code: |
TT7301 |
| Format: |
Formation en classe avec formateur |
|
| Durée: |
4 days |
| Certifié par: |
Trivera |
|
| Frais d’inscription (CAD): 2,200$ |
|
 |
 |
|
 |
|
|
 | Ce cours n'est pas prévu à l'horaire pour l'instant. Si vous êtes intéressé à suivre ce cours, utilisez le lien ci-dessous pour demander une date. |
|
|
|


Mastering Core Web Services and SOA for J2EE (or JEE) Developers (TT7301) Contenu détaillé |
| |
| |
| Session: Introduction to SOA | - What is a Service?
-
SOA is Defined in Many Ways
-
Architectural Style: Common Framework
-
Loose Coupling: Spectrum of Options
-
Software Agents: Services
-
Interacting: Orchestrated
-
SOA is Not Revolutionary
-
What is the Difference Between Services and SOA?
-
SOA - Business Perspective
-
SOA – Technical Perspective
-
SOA is Not …
-
Myths and Realities
-
SOA and Web Services
| |
| Lesson: SOA: The Business Proposition | - Dealing with Change - Motivation for SOA
-
Typical Software Project
-
Typical Software Projects – Why?
-
Business Logic Gets Replicated Over Time
-
Unique Interfaces Build Up Over Time
-
Unique Technologies Build Up Over Time
-
Unique Data Representations Build Up Over Time
-
What are Implications of Each of These Issues?
-
Service Model
-
Service Consumer
-
Service Bus
-
Commonality is Critical Element of SOA
-
Where are We Leveraging That Commonality?
-
Service Provider
-
Business Process: OpenCheckingAcct
-
How Does SOA Address Replication of Logic?
-
How Does SOA Address Unique Interfaces?
-
How Does SOA Address Unique Technologies?
-
How Does SOA Address Unique Data Schemas?
-
How Does SOA Help Deal with Change?
-
Leverage SOA to Empower Customers
-
Leverage SOA to Empower Your Organization
-
Leverage SOA to Support for Strategic Growth and Change
-
Potential Benefits of SOA
-
The Benefits of a Well-Designed SOA
-
SOA Maturity Models Abound
-
Example: IBM’s SIMM
-
Incremental Adoption of SOA
| |
| Lesson: SOA: An Architectural Perspective | - Enterprise Application Layers
-
Application Layers at a Glance
-
Services and Their Formal Contracts
-
Services Should be Stateless
-
Objects, Components, and Services
-
What is a Legacy System?
-
The Challenge of Legacy Systems
-
Limitations Associated with Legacy Systems
| |
| Lesson: SOA: A Development Perspective | - Top-Down: Strategic Orientation
-
Bottom-up: Tactical Strategy
-
Lifecycle Phases
-
SOA Roles and Skills (Existing)
-
SOA Roles and Skills (New)
-
Business is the Starting Point
-
Service-Oriented Analysis and Design (SOAD)
-
Service-Oriented Analysis and Design Process
-
Service Identification
-
Service Modeling Guidelines
-
Model For Cross-Application Reuse
-
Preventing Boundary Logic Creep
-
Target A Balanced Model
| |
| Lesson: Service-Oriented Architecture | - Technical Principles
-
Logical Components of a SOA
-
Characteristics of a Good Service
-
Generic Nature of Services
-
Business Process-Driven Development
-
SOA Business Modeling
-
SOA Reference Architecture
-
Business Versus Application
-
Service Layers
-
Application Services
-
Functional Services
-
Business Process Services
-
Messaging
-
When is Messaging Used?
-
Two Messaging Models
-
More On Publish/Subscribe
-
Logical View of Publish/Subscribe
-
More On Point-to-Point (P2P)
-
Logical View of Point-To-Point
-
Message Servers
-
Messaging
-
SOAP
-
Common Framework: Addressing Cross-Cutting Concerns
-
Role and Uses of an Enterprise Service Bus
-
What Does the Enterprise Service Bus Do?
-
The Challenge of Handling Transactions
-
The Solution to Handling Transactions
-
Security
-
Governance and Compliance
-
Governance and Expertise
-
Governance and Service Lifecycle
-
Governance and Consumer/Provider Management
-
Challenge of Governance
| |
| Session: SOA Analysis and Design | | Lesson: Service-Oriented Analysis and Design Review | - Review of Lifecycle Phases
-
What is SOAD?
-
Service Identification
-
Service Specification
-
Results: Identification and Specification
-
Service Realization
-
SOA Reference Architecture
-
Results: Realization
-
Systematic Process to Achieving These Results
-
Challenge of Governance
| |
| Lesson: Service Realization | - SOAD Process: Where ARE we?
-
Service Realization
-
SOA Reference Architecture
-
Application Services
-
Functional Services
-
Business Process Services
-
Solving Problems Using Layers
-
Service Realization: Allocation
-
Service Realization: Asset Feasibility
-
Service Realization Decisions
-
Service Design Guidelines
-
Designing SOAs by Composition
| |
| Session: Path to Useful Web Services | | Lesson: Services via the Web | - Service Defined
-
SOA Defined
-
Organizational Framework
-
Technical Framework
-
Orchestration
-
Services vs. SOA
-
SOA in the past
-
What is new in SOA
-
Business impact/ROI
-
Myths/Reality
-
Adoption issues
-
Characteristics of a Good Service
-
Services and their Formal Contracts
-
Services Should be Stateless
-
Service Design Guidelines
-
SOA Anti-Patterns
| |
| Lesson: Web Services Overview | - Crossing Boundaries
-
What are Web Services?
-
Six Key Components
-
Web Services Characteristics
-
Web Services Architecturally
-
Technology Comparison
-
Architectural Perspective
-
Web Services Enable Decoupling
-
Many Web Services Challenges
-
Secure Services
-
Spec and Standard Evolution
-
Web Services Interoperability Organization
-
WS-I Has Many Deliverables
-
Basic Profile 1.0 Consists of:
-
Has > 100 Requirements and Suggestions
-
.NET Platform & .NET Web Services
-
Java and Web Services
-
Exercise: Web Services in Action
| |
| Lesson: Web Services, Java, and J2EE | - XML and Java APIs at a Glance
-
XML Signature
-
XML Digital Signatures
-
XML Encryption
-
JAXP
-
JAXB
-
JAX-WS
-
SAAJ
-
JAX-WSA and XWSS
-
Web Services APIs
-
Web Services for J2EE (JSR109)
-
J2EE and Web Services
-
Web Services Metadata
-
Web Services Stacks at a Glance
-
WSIT
-
Apache Axis2
-
JBossWS
-
JWSDP
-
WebSphere WS
-
Spring-WS
-
Key Features
| |
| Lesson: Web Services Quickstart | - What is WSIT?
-
WSIT Tool Support
-
How is WSIT Used?
-
Web Service Development with WSIT
-
Debugging Web Services
-
TCP/IP Monitors Provide View of Wire
-
Exercise: Implementing a Web Service
-
Exercise: Debugging Web Services
| |
| Session: Foundation - XML and Java | | Lesson : XML, Namespaces, & Schema | - What is XML?
-
XML Can Provide Application-Specific Information
-
Content: XML Document Syntax Rules
-
Structure: A Document Type Definition
-
XML Transformation to HTML
-
XML Separates Structure, Content and Format
-
TriveraTunes Purchase Order
-
Content as MarkUp
-
Tell Parser That Text is Data
-
Use Predefined Entities
-
Well-Formed and Valid XML Documents
-
Why Are These Definitions Important?
-
XML Namespaces
-
Name Collision – Example
-
Inter-Organization Name Collisions
-
W3C’s Solution: Namespaces
-
Uniform Resource Indicator
-
Declaring a Namespace
-
Namespace Scope
-
Parsers Use URI, Not the Alias
-
Default Namespace
-
Attributes and Namespaces
-
Example of Namespaces
-
Namespaces Best Practices
-
Benefits From Valid XML
-
W3C XML Schemas
-
Impacts of Schemas
-
General Form of an XML Schema
-
Elements, Attributes, and Types
-
Simple Schema and XML Document
-
Element Definitions
-
Corresponding XML Schema
-
Simple Types - Primitive Datatypes
-
Restricting Simple Types: Facets
-
Complex Types Bring More to Validation
-
Repetition Control
-
Restricting Simple Types
-
Complex Types Can be Derived
-
Derivation by Extension
-
Extension of Phone Number
-
Associating Schemas with XML Instances
-
Using XML Schema with Namespaces
-
Namespaces Provide Thread of Connection
-
Schema Defines a Target Namespace
-
XML Doc Uses Schema-Defined Namespace
-
schemaLocation Links Namespace to Location
-
Relating Schemas to XML
-
Exercise: Namespaces and Schemas
| |
| Lesson: XML in Java - JAXP and JAXB | - XML Parsers Are Complex and Powerful
-
Parsers Are Integral to XML Processing
-
Parsers and API’s
-
Parser Generates DOM, Then Hands to App
-
Parsing With a DTD or Schema
-
Many Options to Consider
-
XML and Java
-
Security Concerns Relative to Parsing
-
Bridging Application Data and XML
-
JAXP: Java API for XML Processing
-
JAXP and Transformations
-
Challenges to Mapping XML
-
Generating XML is Nondeterministic
-
JAXB: Binding XML to Java
-
JAXB 2.0 Incorporated Changes
-
JAXB 2.0 and Java Versions
-
Defining the Rules in JAXB
-
Turning Rules into Java Classes
-
Using the Generated Classes
-
Creating Content
-
Some JAXB Type Bindings
-
XML Schema for List of Items
-
Corresponding Class Interface
-
A Word About Validation…
-
Exercise: Working With JAXB
| |
| | | |

|