WebSphere and .NET interoperability using Web services
IBM and Microsoft are strong supporters of the Web Services Interoperability Organization’s (WS-I) efforts to make building solutions using software from different suppliers a reality. In this IBM Redbooks publication, we take a practical look at building a solution with IBM WebSphere and Microsoft...
| Otros Autores: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Research Triangle Park, N.C. :
IBM Corp., International Technical Support Organization
c2005.
|
| Edición: | 1st ed |
| Colección: | IBM redbooks.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009626891506719 |
Tabla de Contenidos:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. Introduction
- 1.1 Background of this book
- 1.1.1 The scenario
- 1.1.2 Use of Web services
- 1.1.3 Other approaches to interoperability
- 1.1.4 WS-I
- 1.1.5 Audience
- 1.1.6 Terminology
- Part 1 Introduction to Web services
- Chapter 2. SOAP primer
- 2.1 What is SOAP?
- 2.2 SOAP components
- 2.3 What is in a SOAP message?
- 2.3.1 Headers
- 2.3.2 Body
- 2.3.3 Fault
- 2.4 Message styles
- 2.4.1 RPC-Style
- 2.4.2 Document-Style
- 2.4.3 Document/Wrapped
- 2.5 SOAP interaction styles
- 2.5.1 Request-response
- 2.5.2 One-way
- 2.6 SOAP implementations over Http:
- 2.6.1 Microsoft .Net SOAP request over Http
- 2.6.2 IBM WebSphere Application Server SOAP request over Http:
- 2.7 Summary: Salient interoperability features of SOAP
- Chapter 3. WSDL primer
- 3.1 Structure of WSDL definitions
- 3.2 Examples of WSDL definitions
- 3.2.1 Document/Literal Style
- 3.2.2 RPC/Literal Style
- 3.3 Future considerations
- 3.4 Summary: salient interoperability features of WSDL
- Chapter 4. Web services primer
- 4.1 Web services concepts
- 4.1.1 What is a Web service?
- 4.1.2 Web services technologies
- 4.1.3 Web service properties
- 4.2 Web services and component architectures
- 4.2.1 Choosing between Web services and software components
- 4.3 Service-Oriented Architecture
- 4.3.1 Components of a Service-Oriented Architecture
- 4.3.2 Services and Web services
- 4.4 Web services and the Enterprise Service Bus
- 4.4.1 Transparency
- 4.4.2 Interoperability
- 4.4.3 Unified service discovery and addressing
- 4.4.4 Coexistence
- 4.4.5 Single point of control
- 4.4.6 Security
- 4.4.7 Robustness
- 4.4.8 Scalability
- 4.4.9 Problem determination.
- 4.4.10 Conclusions: Web services, the ESB and service buses
- 4.5 Summary
- Part 2 Web services interoperability
- Chapter 5. Business scenarios
- 5.1 Business scenarios overview
- 5.2 Mergers and Acquisitions
- 5.2.1 Business goals
- 5.2.2 Solution context
- 5.2.3 Current IT infrastructure
- 5.2.4 Technical constraints
- 5.2.5 Solution level design
- 5.2.6 Technical approach
- 5.2.7 Target IT infrastructure
- 5.3 External claims assessor management
- 5.3.1 Business goals
- 5.3.2 Solution context
- 5.3.3 Current IT infrastructure
- 5.3.4 Technical constraints
- 5.3.5 Solution level design
- 5.3.6 Technical approach
- 5.3.7 Target IT infrastructure
- 5.4 Summary
- Chapter 6. Interoperability patterns
- 6.1 The Patterns for e-business layered asset model
- 6.2 SOA approach and Patterns for e-business
- 6.2.1 Business::Self-Service pattern
- 6.2.2 Extended Enterprise business pattern
- 6.2.3 Discussion of patterns and Web services
- 6.3 Applying Interoperability patterns
- 6.3.1 Mergers and Acquisitions scenario
- 6.4 Summary
- 6.5 Where to find more information
- Chapter 7. Web services roadmap
- 7.1 Introduction
- 7.2 List of Web services specifications
- 7.3 Summary of the Web services architecture stack
- 7.3.1 Foundations
- 7.3.2 Messaging
- 7.3.3 Security
- 7.3.4 Transacted
- 7.3.5 Meta-data
- 7.3.6 Resources
- 7.3.7 Composition
- 7.3.8 Management
- 7.3.9 Provisioning
- 7.3.10 WS-I
- 7.4 Summary
- Chapter 8. Web service specifications
- 8.1 Web service Interoperability Organization (WS-I)
- 8.2 WS-I Basic Profile 1.0
- 8.2.1 Basic Profile 1.0 for WebSphere
- 8.2.2 Basic Profile 1.0 for Microsoft .Net
- 8.2.3 Summary
- 8.3 Interoperability standards: addressing
- 8.3.1 Insurance example
- 8.3.2 Summary
- 8.4 Security
- 8.4.1 Why do we need more security specifications?.
- 8.4.2 WS-Security 2004
- 8.4.3 WS-I Security Profile
- 8.4.4 Summary
- 8.5 WS-Coordination
- 8.6 WS-Transactions
- 8.6.1 WS-Transaction in a WebSphere environment
- 8.6.2 WS transaction in a Microsoft .Net environment
- 8.7 Reliable messaging
- 8.7.1 What is WS-ReliableMessaging?
- 8.7.2 The three legged handshake protocol
- 8.7.3 WS-ReliableMessaging Protocol
- 8.7.4 Reliable messaging requirements
- 8.8 SOAP/JMS and SOAP/MQ
- 8.8.1 Interoperability of SOAP/JMS and SOAP/MQ
- Chapter 9. Web services in Microsoft .Net and WebSphere
- 9.1 Microsoft .Net architecture
- 9.1.1 Microsoft .Net Web service application architecture
- 9.1.2 Developing software using Microsoft Visual Studio .Net 2003
- 9.1.3 Microsoft secure Web services implementation
- 9.2 WebSphere Java 2 Enterprise Edition architecture
- 9.2.1 Java 2 Enterprise Edition Web service architecture
- 9.2.2 Developing J2EE applications using WebSphere Studio Application Developer
- 9.2.3 IBM secure Web services implementation
- 9.2.4 Summary
- Chapter 10. Deploying Web services
- 10.1 Overview
- 10.1.1 Web services publishing
- 10.2 WebSphere Web services deployment model
- 10.2.1 Web Services Gateway
- 10.2.2 IBM UDDI registry
- 10.2.3 Deployment architecture
- 10.3 Microsoft .Net Web service deployment model
- 10.3.1 Microsoft UDDI registry
- 10.3.2 Deployment architecture
- 10.4 Summary
- Part 3 Claims scenario
- Chapter 11. Designing the scenarios
- 11.1 Mergers and Acquisitions scenario
- 11.1.1 Use cases overview
- 11.1.2 Actors
- 11.1.3 Use case 001: Register claim
- 11.1.4 Realizing the use case
- 11.2 External Claims Assessors scenario
- 11.2.1 Use cases overview
- 11.2.2 Actors
- 11.2.3 Use case 002: Manage external claim assessors
- 11.2.4 Realizing the use case
- 11.3 Claim applications: table schema.
- 11.4 XML schema data types as common denominator
- 11.4.1 Data type mapping
- 11.4.2 SOAP message for registerClaim()
- 11.4.3 SOAP message for findCustomer()
- 11.4.4 SOAP exception for findCustomer()
- 11.5 Summary
- Chapter 12. Building the claims scenario
- 12.1 Building the scenario for WebSphere
- 12.1.1 Problem definition
- 12.1.2 Solution
- 12.1.3 Import Enterprise JavaBeans
- 12.1.4 Test imported Enterprise JavaBeans
- 12.1.5 Create a Web service from Enterprise JavaBeans
- 12.1.6 Test the created Web service
- 12.1.7 Deploy the created Web service
- 12.2 Building the scenario for Windows Server 2003
- 12.2.1 Prerequisites to run the Web service application
- 12.2.2 Create the Web Service
- 12.2.3 Import the existing classes
- 12.2.4 Build the Web service
- 12.2.5 Microsoft Internet Information Services (IIS)
- 12.2.6 Create Microsoft .Net Test Client
- 12.2.7 Summary
- 12.3 Building the Web services clients
- 12.3.1 Web service client for the WebSphere Web service
- 12.3.2 Web service client for the Microsoft .Net Web service
- 12.3.3 Microsoft .Net
- 12.3.4 Differences between the two Web services and conclusions
- Chapter 13. Web service interoperability implementation guidance
- 13.1 Web service interoperability guidance
- 13.2 WebSphere client
- 13.3 WebSphere Web service
- 13.4 Microsoft .Net client
- 13.5 Summary
- Part 4 Appendixes
- Appendix A. Installation and setup
- Installation planning for the WebSphere environment
- WebSphere Application Server V5.1.1.1 requirements
- Installing WebSphere Application Server 5.1.1.1
- Installation of Application Developer 5.1.2
- Installation planning for the Microsoft .Net environment
- Appendix B. Additional material
- Locating the Web material
- Using the Web material
- System requirements for downloading and running the Web material.
- How to use the Web material
- Related publications
- IBM Redbooks
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Abbreviations and acronyms
- Index
- Back cover.
