Application Interoperability: Microsoft .NET and J2EE: Microsoft(r) .Net and J2ee (Patterns & Practices)

2017-07-07 02:10:07

Chapter 1: Introduction

Figure 1.1: J2EE and.NET equivalent components in an enterprise application environment
Figure 1.2: .NET Presentation tier linked to J2EE Business tier
Figure 1.3: Integrating .NET Business tier components into a J2EE architecture
Figure 1.4: Business tier to Data tier interoperability

Figure 4.1: A typical .NET Remoting implementation
Figure 4.2: Connecting Ja.NET to a VB.NET Server component
Figure 4.3: Connecting Ja.NET to a .NET component hosted on IIS
Figure 4.4: Connecting .NET Clients to an EJB using Ja.NET
Figure 4.5: Internal architecture of JNBridgePro Runtime Bridge
Figure 4.6: Java-side component in J2EE application server
Figure 4.7: Java-side component on the computer running the .NET Framework component
Figure 4.8: The five-layer model of the Web services stack
Figure 4.9: Typical architectural elements from a Web service
Figure 4.10: Web service client using a proxy class to communicate with a Web service

Figure 5.1: .NET Framework and J2EE applications sharing a common database
Figure 5.2: The Data Access Logic Components abstract the database code from the Business tier
Figure 5.3: Sharing Data Access Logic Components between .NET Framework and Java applications
Figure 5.4: Example of a message queuing application
Figure 5.5: Message Queuing enabling asynchronous interoperability between .NET Framework and Java applications
Figure 5.6: Accessing Message Queuing through a Java-to-COM bridge
Figure 5.7: Accessing MSMQ using a Web service interface
Figure 5.8: Handling a transaction using a Web service
Figure 5.9: Publish/Subscribe domain in the JMS specification
Figure 5.10: A .NET Framework client using the WebSphere MQ Classes for .NET to connect to WebSphere MQ
Figure 5.11: Using a runtime bridge to access WebSphere MQ JMS functionality from .NET Framework clients
Figure 5.12: Using the MSMQ-MQSeries Bridge in HIS 2000 to enable asynchronous interoperability

Figure 6.1: .NET Framework application architecture best practice design
Figure 6.2: Application architecture for .NET Framework version of XBikes
Figure 6.3: Application architecture for J2EE version of XBikes
Figure 6.4: Simple connection point example
Figure 6.5: Interoperability points in multi-tiered applications
Figure 6.6: Programmatic elements for point to point interoperability
Figure 6.7: Linking interoperability elements into a multi-tiered application
Figure 6.8: XBikes on J2EE Presentation and business tiers with interoperability elements added
Figure 6.9: XBikes on J2EE Business and Data tiers with interoperability elements added
Figure 6.10: XBikes on .NET Framework Presentation and Business tiers with interoperability elements added
Figure 6.11: XBikes on .NET Framework Business and Data tiers with interoperability elements added

Figure 7.1: Implementing a service interface and service fa ade to link the J2EE Business tier to the .NET Presentation tier
Figure 7.2: Interoperability adapters connecting the ASP.NET application to the service interface
Figure 7.3: Using the Data Helper class in a Web service
Figure 7.4: Web service proxy operation with .NET Framework applications

Figure 8.1: Implementing a .NET Framework service interface for the .NET Framework business service fa ade
Figure 8.2: Web service proxy operation with J2EE applications
Figure 8.3: Implementing a custom .NET Framework service interface for the .NET Framework business service fa ade

Figure 9.1: The role of service interfaces in asynchronous communications
Figure 9.2: The role of interoperability adapters in asynchronous communications
Figure 9.3: Logical representation of the MSMQ-MQSeries Bridge connecting MSMQ and MQ Series
Figure 9.4: The role of JNBridge in asynchronous communications
Figure 9.5: The role of Ja.NET in asynchronous communications