WebSphere and .NET Coexistence /
This IBM Redbooks publication explores the different coexistence scenarios for the WebSphere and .NET platforms. This book is a good source of information for solution designers and developers, application integrators and developers who wish to integrate solutions on the WebSphere and .NET platforms...
Saved in:
| Online Access: |
Full text (MCPHS users only) |
|---|---|
| Other Authors: | |
| Format: | Electronic eBook |
| Language: | English |
| Published: |
[White Plains, N.Y.] :
IBM,
2004
|
| Edition: | 1st ed. |
| Series: | IBM redbooks.
|
| Subjects: | |
| Local Note: | ProQuest Ebook Central |
Table of Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Introduction
- Chapter 1. J2EE introduction
- 1.1 Architecture
- 1.1.1 Overall architecture
- 1.1.2 Layer technologies (application architecture)
- 1.1.3 Standard support
- 1.1.4 Platform support
- 1.1.5 Programming languages
- 1.1.6 Deployment units
- 1.1.7 Runtime execution environment
- 1.1.8 Life cycle management
- 1.1.9 Remote object discovery
- 1.1.10 Remote Method Invocation
- 1.1.11 Web Services
- 1.1.12 Transaction management
- 1.1.13 Security
- 1.1.14 Load balancing and failover
- 1.1.15 Application logging
- 1.2 Development
- 1.2.1 Writing a Java application using a text editor
- 1.2.2 WebSphere Studio Application Developer (IDE)
- 1.3 Testing
- 1.3.1 WebSphere Studio Application Developer
- 1.4 Deployment
- 1.4.1 Packaging J2EE applications
- 1.4.2 Deploying the packaged applications
- 1.5 Runtime
- 1.5.1 WebSphere Application Server
- 1.6 Administration
- Chapter 2. .NET introduction
- 2.1 Architecture
- 2.1.1 Overall architecture
- 2.1.2 Layered services (application architecture)
- 2.1.3 Standard support
- 2.1.4 Platform support
- 2.1.5 Programming languages
- 2.1.6 Deployment units
- 2.1.7 Runtime execution environment
- 2.1.8 Life cycle management
- 2.1.9 Remote object discovery
- 2.1.10 Remote invocation
- 2.1.11 Web Services
- 2.1.12 Transaction management
- 2.1.13 Security
- 2.1.14 Load balancing and failover
- 2.1.15 Application logging
- 2.1.16 Versioning
- 2.2 Development
- 2.2.1 Writing a C# application using text editor
- 2.2.2 Microsoft Visual Studio .NET (IDE)
- 2.2.3 Source code management
- 2.3 Testing
- 2.3.1 Debugging and unit testing
- 2.3.2 Performance and load testing
- 2.4 Deployment
- 2.5 Runtime.
- 2.6 Administration
- Chapter 3. An architectural model for coexistent applications
- 3.1 Coexisting heterogeneous technologies
- 3.1.1 Layered application model
- 3.1.2 Concentric layered application model
- 3.1.3 Bridging layers and address spaces
- 3.1.4 Interoperation layer abstraction
- 3.1.5 Summary
- Part 2 Scenarios
- Chapter 4. Technical coexistence scenarios
- 4.1 Introduction
- 4.2 Fundamental interaction classifications
- 4.2.1 Stateful synchronous interaction
- 4.2.2 Stateless synchronous interaction
- 4.2.3 Stateless asynchronous interaction
- 4.2.4 Stateful asynchronous interaction
- 4.2.5 RPC interface style
- 4.2.6 Document interface style
- 4.2.7 Argument by value paradigm
- 4.2.8 Argument by reference paradigm
- 4.2.9 Distributed object architecture
- 4.2.10 Message Oriented Architecture
- 4.2.11 Service-oriented architecture
- 4.2.12 Conclusions and recommendations
- 4.3 Layer interaction classifications
- 4.3.1 Interaction case a: client logic to client logic
- 4.3.2 Interaction case b: client logic to presentation logic
- 4.3.3 Interaction case c: client logic to business logic
- 4.3.4 Interaction case d: presentation logic to presentation logic
- 4.3.5 Interaction case e: presentation logic to business logic
- 4.3.6 Interaction case f: business logic to business logic
- 4.3.7 Interaction case g: business logic to resource
- 4.3.8 Interaction case h: resource to resource
- 4.3.9 Conclusion and recommendations
- 4.4 Technical solution mapping
- 4.4.1 Stateful synchronous integration solution candidates
- 4.4.2 Stateless synchronous integration solution candidates
- 4.4.3 Stateful asynchronous integration solution candidates
- 4.4.4 Other potential candidate technical solutions (to be proven)
- 4.4.5 Some last resource integration technologies
- Chapter 5. Scenario: Asynchronous.
- 5.1 Problem definition
- 5.1.1 Description of the problem
- 5.1.2 Considerations
- 5.2 Solution model
- 5.2.1 A solution to the problem
- 5.2.2 Simple scenario details
- 5.2.3 .NET consumer to WebSphere service provider
- 5.2.4 WebSphere consumer to .NET service provider
- Chapter 6. Scenario: Synchronous stateful
- 6.1 Problem definition
- 6.1.1 Description of the problem
- 6.1.2 Considerations
- 6.1.3 Constraints
- 6.1.4 Recommendations
- 6.2 Solution model using the ActiveX Bridge
- 6.2.1 A solution to the problem
- 6.2.2 Simple scenario details
- 6.3 Solution model using the Interface Tool for Java
- Chapter 7. Scenario: Synchronous stateless (WebSphere producer and .NET consumer)
- 7.1 Problem definition
- 7.1.1 Description of the problem
- 7.1.2 Considerations
- 7.2 Solution model
- 7.2.1 A solution to the problem
- 7.2.2 Service provider
- 7.2.3 Service consumer
- 7.3 Extended solution
- 7.4 Recommendations
- Chapter 8. Scenario: Synchronous stateless (WebSphere consumer and .NET producer)
- 8.1 Solution model
- 8.1.1 A solution to the problem
- 8.1.2 Service provider
- 8.1.3 Service consumer
- 8.1.4 Test
- 8.2 Extended solution model
- Chapter 9. Scenario: Web interoperability
- 9.1 Introduction
- 9.2 Shared presentation components
- 9.2.1 Configuring Microsoft IIS for shared presentation
- 9.3 Session state interoperability
- 9.3.1 Problem definition
- 9.3.2 WebSphere Application Server session management
- 9.3.3 Microsoft .NET session management
- 9.3.4 Considerations
- 9.3.5 Recommendations
- 9.4 Data propagation
- 9.4.1 Problem definition
- 9.4.2 Description of the problem
- 9.4.3 Considerations
- 9.4.4 Solution model
- 9.4.5 URL redirection implementation
- 9.4.6 Form-based propagation implementation
- 9.4.7 Recommendations
- 9.5 Integrated security
- 9.5.1 WebSphere security.
- 9.5.2 .NET security
- 9.5.3 Integrating authentication
- 9.5.4 Integrating authorization
- Part 3 Guidelines
- Chapter 10. Supporting technologies
- 10.1 Web Services
- 10.1.1 Technologies for Web Services
- 10.2 Client applications
- 10.2.1 Web browser
- 10.2.2 J2EE clients
- 10.2.3 Windows .NET clients
- 10.3 Server pages
- 10.3.1 Servlets and JSPs
- 10.3.2 ASP.NET
- 10.4 Distributed components
- 10.4.1 EJBs
- 10.4.2 .NET Remoting
- 10.5 Database access
- 10.5.1 EJBs
- 10.5.2 JDBC
- 10.5.3 ADO.NET
- 10.6 Messaging middleware
- 10.7 Back-end integration
- 10.7.1 J2C
- 10.7.2 .NET
- 10.8 Other integration technologies
- 10.8.1 ActiveX Bridge
- 10.8.2 IBM Interface Tool for Java
- Chapter 11. Quality of service considerations
- 11.1 Scalability
- 11.1.1 WebSphere
- 11.1.2 .NET
- 11.2 Performance
- 11.2.1 WebSphere
- 11.2.2 .NET
- 11.3 Availability
- 11.3.1 WebSphere
- 11.3.2 .NET
- 11.4 Security
- 11.4.1 WebSphere
- 11.4.2 .NET
- 11.5 Transactionality
- 11.5.1 WebSphere
- 11.5.2 .NET
- 11.6 Manageability
- 11.6.1 WebSphere
- 11.6.2 .NET
- 11.7 Maintainability
- 11.7.1 WebSphere
- 11.7.2 .NET
- 11.8 Portability
- 11.8.1 WebSphere
- 11.8.2 .NET
- 11.9 Web Services
- Part 4 Appendixes
- Appendix A. Lotus Domino and .NET coexistence
- A.1 Web Services integration
- A.1.1 Domino provider, .NET consumer
- A.1.2 .NET service provider, Domino service consumer
- A.2 Using the COM interface
- A.2.1 Domino as a COM server, .NET as a client
- 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
- Abbreviations and acronyms
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.
