2 options
WebSphere MQ solutions in a Microsoft .NET environment / Saida Davies ... [et al.].
- Format:
- Book
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Microsoft .NET.
- WebSphere.
- Physical Description:
- xviii, 342 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- Research Triangle Park, NC : IBM, International Technical Support Organization, 2004.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. Introduction
- Chapter 2. Overview
- 2.1 The aim
- 2.2 Technologies
- 2.2.1 .NET environment and C# programming language
- 2.2.2 J2EE
- 2.2.3 WebSphere MQ
- 2.2.4 WebSphere MQ classes for Microsoft .NET
- 2.2.5 What is SOAP?
- 2.2.6 WebSphere MQ Transport for SOAP
- 2.3 Usage scenarios
- 2.3.1 Usage scenarios: .NET application to .NET application
- 2.3.2 Usage scenarios: .NET application to J2EE application
- 2.3.3 Usage scenarios: .NET application to a .NET Web Service
- 2.3.4 Usage scenarios: .NET application to a J2EE Web Service
- Chapter 3. WebSphere MQ Transport for SOAP
- 3.1 What is WebSphere MQ transport for SOAP?
- 3.2 WebSphere MQ transport for SOAP Installation
- 3.2.1 Downloading WebSphere MQ transport for SOAP
- 3.2.2 Prerequisite software
- 3.2.3 Pre-installation
- 3.2.4 Installation
- 3.2.5 Running the demonstration programs
- 3.2.6 Re-registration to the Global Assembly Cache
- 3.2.7 Checking the WebSphere MQ transport for SOAP release level
- 3.3 SOAP formatting
- 3.3.1 How to specify RPC or Document style encoding
- 3.4 WebSphere MQ transport for SOAP application development
- 3.4.1 Client environment
- 3.5 WebSphere MQ transport for SOAP .NET deployment
- 3.5.1 WebSphere MQ URI Syntax
- 3.5.2 WebSphere MQ client connection options
- 3.5.3 Calling deployWMQService
- 3.6 WebSphere MQ transport for SOAP listener for .NET
- 3.6.1 Executing MQSoapHost
- 3.7 A simple example with a Microsoft .NET Web Service
- 3.7.1 Write the Web Service
- 3.7.2 Write the .NET ASMX service directive file
- 3.7.3 Deploying the Microsoft .NET service
- 3.7.4 Write the client application
- 3.7.5 Define the WebSphere MQ response queue.
- 3.7.6 Start the prepared Microsoft .NET listener
- 3.7.7 Test the service
- 3.7.8 Distributed test in WebSphere MQ client mode
- 3.7.9 Distributed test in WebSphere MQ server bindings mode
- 3.7.10 Distributed WebSphere MQ using MQ clustering
- 3.8 WebSphere MQ transport for SOAP with J2EE deployment
- 3.8.1 Deployment of J2EE Web Services
- 3.8.2 WebSphere MQ Transport for SOAP SimpleJMSListener
- 3.8.3 Executing SimpleJMSListener
- 3.9 A simple example with a J2EE Web Service
- 3.9.1 Write the Web Service
- 3.9.2 Deploy the service
- 3.9.3 Write the client application
- 3.9.4 Additional WebSphere MQ configuration
- 3.9.5 Start the prepared JMS listener
- 3.9.6 Test the service
- 3.9.7 Distributed test in WebSphere MQ server bindings mode
- 3.9.8 Distributed test in WebSphere MQ client mode
- 3.9.9 Distributed WebSphere MQ using MQ clustering
- 3.9.10 Service code use of external classes
- 3.10 Starting listeners with WebSphere MQ triggering
- 3.10.1 Using a different initiation queue
- 3.11 WebSphere MQ transport for SOAP and SSL
- 3.11.1 Simple demonstration with SSL
- 3.11.2 Use of SSLPeerName
- 3.12 Asynchronous invocation of Web Services
- 3.13 Current status and future plans
- Chapter 4. Business case scenario
- 4.1 Business domain
- 4.2 Business process
- 4.2.1 Use case 1: Account opening
- 4.2.2 Use case 2: Investment advisory
- 4.3 Non-functional requirements and assumptions
- Chapter 5. Solution design
- 5.1 Message flow
- 5.1.1 Use case 1: Account opening message flow
- 5.1.2 Use case 2: Investment advisory message flow
- 5.2 Server configuration
- 5.3 WebSphere MQ configuration
- Chapter 6. Environment setup
- 6.1 Software prerequisites
- 6.2 Installation
- 6.2.1 Installing WebSphere MQ
- 6.2.2 Installing WebSphere MQ classes for Microsoft .NET
- 6.2.3 Installing WebSphere MQ Transport for SOAP.
- 6.2.4 Installing Internet Information Services (IIS)
- 6.2.5 Installing Microsoft Visual Studio .NET
- 6.3 Environment Setup
- 6.3.1 Core systems overview
- Chapter 7. Messaging solution: .NET application to .NET application
- 7.1 Process overview
- 7.1.1 Scenario overview
- 7.2 System context
- 7.2.1 Interface definitions
- 7.3 Development
- 7.3.1 Adding the WebSphere MQ reference to the project
- 7.3.2 Bank service application (C#)
- 7.3.3 Credit check application
- 7.3.4 Credit check application C# snippet
- 7.3.5 Credit check application VB .NET snippet
- 7.4 Deployment
- 7.4.1 Deploying BSS
- 7.4.2 Deploying CCS
- 7.5 Testing
- 7.5.1 How to start BSS
- 7.5.2 How to start CCS
- 7.5.3 Test 1 pass known data
- 7.5.4 Test 2 pass unknown user
- Chapter 8. Messaging solution: .NET application to J2EE application
- 8.1 Process overview
- 8.1.1 Account opening
- 8.1.2 Investment advisory
- 8.2 System context
- 8.2.1 Bank service application
- 8.2.2 Investment advisory application
- 8.2.3 Customer profile application
- 8.2.4 Database
- 8.2.5 JMS administered objects
- 8.3 Development
- 8.3.1 Bank service application
- 8.3.2 Investment advisory application
- 8.3.3 Customer profile application
- 8.4 Deployment
- 8.4.1 Deploying BSS
- 8.4.2 Deploying CPS
- 8.5 Testing
- 8.6 Alternative solutions
- 8.6.1 WebSphere MQ classes for Microsoft .NETand WebSphere MQ classes for Java
- 8.6.2 Web Services
- 8.6.3 Bridge between WebSphere MQ and Microsoft Message Queuing (MSMQ)
- Chapter 9. Messaging solution: .NET client to .NET Web Services using WebSphere MQ SOAP transport
- 9.1 Process overview
- 9.2 System context
- 9.3 Development
- 9.3.1 .NET Web Service development
- 9.3.2 IAS Web Service solution
- 9.3.3 WebSphere MQ transport for SOAP deployment for IAS
- 9.3.4 BSS client.
- 9.3.5 BSS Web Application solution
- 9.4 Deployment
- 9.4.1 IAS Web Service deployment
- 9.4.2 WebSphere MQ queue setup and WebSphere MQ transport for SOAP deployment
- 9.4.3 BSS Web Application deployment
- 9.4.4 Securing the IAS Web Service
- 9.5 Testing
- 9.5.1 IAS Web Service testing using Microsoft Visual Studio .NET
- 9.5.2 BSS user interface testing
- Chapter 10. Messaging solution: .NET client to J2EE Web Services using WebSphere MQ SOAP transport
- 10.1 Process overview
- 10.2 System context
- 10.2.1 Interface definition
- 10.2.2 Service operation definition
- 10.2.3 XML data format
- 10.3 Development
- 10.3.1 Business logic implementation
- 10.3.2 Persistent storage
- 10.3.3 WebSphere MQ definition
- 10.3.4 Adding external classes to the CLASSPATH
- 10.4 Deployment
- 10.4.1 Runtime environment
- 10.4.2 ShareQuote service deployment
- 10.5 Testing
- 10.5.1 Calling the service from the IAS client
- 10.5.2 Test result
- 10.6 Solution discussion
- Chapter 11. System integration and functional test
- 11.1 Scope and objectives
- 11.2 System integration
- 11.2.1 Runtime environment
- 11.2.2 Test data
- 11.2.3 System build and deployment
- 11.2.4 System startup
- 11.3 Functional test
- 11.3.1 Entrance and exit criteria
- 11.3.2 Use case 1: Account opening
- 11.3.3 Use case 2: Investment advisory
- 11.4 Summary
- Chapter 12. Security
- 12.1 Security concepts
- 12.1.1 Security services
- 12.1.2 Security mechanisms
- 12.2 Planning the security services in use cases
- 12.2.1 Application layer security services
- 12.2.2 Transmission layer security services
- 12.3 Cryptographic concepts
- 12.3.1 Cryptography
- 12.3.2 Message digest
- 12.3.3 Digital signature
- 12.3.4 Digital certificate
- 12.3.5 Public Key Infrastructure (PKI)
- 12.4 Secure Sockets Layer (SSL) introduction.
- 12.4.1 Secure Sockets Layer(SSL) concepts
- 12.4.2 CipherSuites and CipherSpecs
- 12.5 WebSphere MQ SSL support
- 12.6 WebSphere MQ working with SSL on Windows
- 12.7 Deploy SSL support in use cases
- 12.7.1 Obtaining certificates
- 12.7.2 Deploying SSL support in CCS
- 12.7.3 Deploying SSL support in IAS
- 12.7.4 Deploying SSL support in BSS
- Chapter 13. Transactions
- 13.1 Local transactions
- 13.1.1 ACID properties of a transaction
- 13.1.2 Programming local transactions
- 13.2 Distributed transactions
- 13.2.1 Transaction support under Windows 2000
- 13.2.2 Programming distributed transactions: Credit Check Service
- 13.2.3 Microsoft Transaction Server: MTS and WebSphere MQ
- 13.3 Web Service transactions
- 13.3.1 .NET Web Services and transactions
- 13.3.2 Programming Web Services transaction in .NET environment
- 13.3.3 WS Transaction
- Chapter 14. Best practices
- 14.1 Coding standards
- 14.2 Hints and tips
- 14.2.1 XML style comments
- 14.2.2 XML processing in Java
- 14.2.3 SOAP processing in Java
- 14.2.4 XML element versus attribute
- 14.3 Common errors
- 14.4 Testing
- 14.4.1 Unit Testing with JUnit
- 14.4.2 Unit Testing with NUnit
- 14.4.3 Unit Testing with csUnit
- 14.5 Version management
- 14.5.1 ClearCase
- 14.5.2 Concurrent Versions System
- 14.5.3 Visual SourceSafe
- Appendix A. Scripts, source code and test data for YuBank
- WebSphere MQ Setup
- Use case 1
- Use case 2
- Appendix B. Additional material
- Locating the Web material
- Using the Web material
- System requirements for downloading the Web material
- How to use the Web material
- Glossary
- Abbreviations and acronyms
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.
- Notes:
- "January 2004."
- "This edition applies to Version 5, Release 3, Modification 0 of WebSphere MQ; WebSphere MQ Customer Service Diskette (CSD) 05; Microsoft Visual Studio .Net Professional 2003 with Microsoft Development Environment 2003 Version 7.1.3088 and Microsoft .Net Framework 1.1 Version 1.1.4322; Internet Information Services (IIS) Version 5; WebSphere MQ Transport for Soap, February 2003; and WebSphere MQ classes for .NET (amqmdnet.dll Version Resource 1.0.0.3)"--T.p. verso.
- "SG24-7012-00."
- Includes bibliographical references (p. 333-335) and index.
- OCLC:
- 137342273
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.