| |
Back
to BOOK PAGE
Table of ContentsPreface Chapter 1: The Mantra of SOA Chapter 2: Web Services and SOA Chapter 3: Web Service Implementations Chapter 4: Data and Services—All Roads Lead to Enterprise Service Bus Chapter 5: Traditional Integration Technology Chapter 6: Goals We Can Achieve with SOA Index
- Chapter 1: The Mantra of SOA
- Architecture
- Application Architecture
- Client-Server Architecture
- 1-Tier Application
- 2-Tier Application
- 3-Tier Application
- N-Tier application
- Enterprise Computing or Architecture
- Business
- Application
- Information
- Technical
- The Design
- Security
- Administration
- EA for Managers
- EA for Developers
- Analogy of SOA
- Web Services for SOA
- 'Orientation' of Web Services
- Chapter 2: Web Services and SOA
- The SOA Approach
- XML—Advantages and Disadvantages
- Introduction to Web Services, RESTful Services, and Other Transport with XML
- Basic SOA With XML Over HTTP Protocol
- A Basic Java Implementation of POX-over-HTTP
- REST—Exploiting the HTTP Protocol
- SOAP
- RPC and Document Based-WS: How to Communicate, Pros and Cons of the Two Approach
- RPC / Literal
- Document / Literal
- Document / Literal Wrapped
- Why We Should Use Doc-WS?
- The RPC Inheritance
- The Document-Oriented Way
- Implementations: JAX-WS 2, Axis2, Spring-WS, and XFire/CXF 2.0
- JAX-WS 2
- Axis 2
- Spring-WS
- XFire / CXF
- Chapter 3: Web Service Implementations
- Web Service Using JAX-WS 2.0
- JAX-WS 2.0—A Primer
- Web Service Implementation in Java SE 6
- Code Server and Client
- Run the Server and Client
- Web Service Implementation in Java EE Server
- Install and Start the Server
- Code Server and Client
- Run the Server and Client
- Web Service Using Apache Axis
- Contract-First versus Contract-Last
- Web Service Implementation in Axis
- Code Server and Client
- Run the Server and Client
- Web Service Using Spring
- Spring-WS—A Primer
- Web Service Implementation in Spring
- Code Server and Client
- web.xml
- Run the Server and Client
- Web Service Using XFire
- Web Service Implementation in XFire
- Code Server and Client
- Run the Server and Client
- Chapter 4: Data and Services—All Roads Lead to Enterprise Service Bus
- JDO
- Why JDO?
- JPOX—Java Persistent Objects
- JDO Sample Using JPOX
- BDOM for the Sample
- Code BDOM Entities for JDO
- Build and Run the JDO Sample
- Data Services
- Service Data Objects
- Why SDO?
- SDO Architecture
- Apache Tuscany SDO
- SDO Sample Using Tuscany SDO
- Code the Sample Artifacts
- Build and Run the SDO Sample
- Service Component Architecture
- What is SCA?
- Apache Tuscany SCA Java
- SCA Sample Using Tuscany SCA Java
- Code the Sample Artifacts
- Build and Run the SCA Sample
- Message-Oriented Middleware
- What is MOM?
- Benefits of Using MOM
- Enterprise Service Bus
- EAI and ESB
- Java Business Integration
- OpenESB
- Chapter 5: Traditional Integration Technology
- Case Study #1—Based on EAI
- Customer Information
- Business Need
- Solution
- Hub and Spoke Architecture
- Goals Achieved
- Goal #1—Integration between Internal Business Processes and Business Partners
- Goal #2—Avoid Duplicity
- Goal #3—Achieve Re-Usability, Flexibility, and Scalability
- Goal #4—Platform Independence
- Goal #5—Setting up Messaging Exchange
- Goal #6—Less Manual Intervention
- Goal #7—Cost Effective
- EAI Drawbacks
- Proprietary Architecture
- Messaging Bottlenecks
- Tight Coupling
- Non-Flexible Architecture
- Manpower
- Case Study #2—Based on SOA
- Step One—Defining Organization Assets
- Step Two—Generate Services
- Information is eXtensible
- Information Represented in Textual Form
- Information is Structured
- Platform Independency
- Step Three—Model
- Co-relation of Events
- Co-relation of Services and Information
- Step Four—Integrate
- ESB—Enterprise Service Bus
- Goals Achieved
- Goal #1—Proprietary Architecture
- Goal #2—Eliminating Messaging Bottlenecks
- Goal #3—Loose Coupling of Applications
- Goal #4—Flexible Architecture
- Goal #5—Return On Investment (ROI)
Back to BOOK PAGE
| |
|