List of Figures
Table of content
Chapter 1: Microsoft .NET and J2EE Fundamentals
Figure 1.1: Configuring the Server Role in Windows Server 2003.
Figure 1.2: Enabling FrontPage Server Extensions and ASP.NET in Windows Server 2003.
Chapter 2: Business Requirements for Interoperability
Figure 2.1: Technology-aligned development for a J2EE-specific application or service.
Figure 2.2: Technology-aligned development for a .NET-specific application or service.
Figure 2.3: Replacing the JSP and Servlets presentation tier with one created in ASP.NET.
Figure 2.4: Utilizing a .NET application or service within an existing J2EE infrastructure.
Figure 2.5: A new application or service based on the .NET platform.
Figure 2.6: Interoperability from reusing existing business tier components within a new .NET application.
Figure 2.7: An application written for the J2EE platform.
Figure 2.8: Introduction of a new .NET application with different presentation and business tiers.
Figure 2.9: Both applications share the data at the resource tier.
Figure 2.10: Both applications share a message queue at the resource tier.
Figure 2.11: Point-to-point interoperability between a .NET application and a J2EE application.
Figure 2.12: Resource tier interoperability between a .NET and J2EE application.
Chapter 3: Exchanging Data Between .NET and Java
Figure 3.1: Requirement for a new ASP.NET presentation tier for an existing J2EE application.
Figure 3.2: Requirement for a new ASP.NET presentation tier for an existing J2EE application.
Figure 3.3: Creating a new project in Visual Studio .NET.
Figure 3.4: Adding an XML Schema to a project in Visual Studio .NET.
Figure 3.5: The new XSD document in Visual Studio .NET.
Figure 3.6: The
type in the XSD.
Figure 3.7: Viewing the XSD document in Visual Studio .NET.
Figure 3.8: Adding the
data type to the XSD document.
Figure 3.9: Setting the properties for the array type.
Figure 3.10: Adding the
type to the schema.
Figure 3.11: Completing the schema.
Chapter 4: Connectivity with .NET Remoting
Figure 4.1: .NET Remoting using channels and formatters.
Figure 4.2: Passing by reference with .NET Remoting.
Figure 4.3: Using Ja.NET to call a remote .NET server object.
Figure 4.4: A Java client calling a .NET remoted object.
Figure 4.5: The GenJava wizard.
Figure 4.6: Setting the location and output directory.
Figure 4.7: A successful generation of the proxies.
Figure 4.8: Using the Janetor configuration tool.
Figure 4.9: Configuring the activation mode, URI, and channel format.
Figure 4.10: .NET client calling a Java object hosted by Ja.NET TCP server.
Figure 4.11: The GenNet tool.
Figure 4.12: Adding classes to generate .NET proxies.
Figure 4.13: Entering the name and output directory for the .NET proxies.
Figure 4.14: Successful generation of the .NET proxies.
Figure 4.15: Setting the activation mode, URI, and assembly name.
Figure 4.16: Using ILDASM to investigate the contents of the generated assembly.
Figure 4.17: Java client calling a .NET server component, hosted by IIS.
Figure 4.18: Creating an IIS Virtual Directory.
Figure 4.19: Setting the directory location for the virtual directory.
Figure 4.20: Setting the activation mode, URI, and channel format for the client.
Figure 4.21: Using the Authentication tab to set credentials for the exposed component.
Figure 4.22: An event written to the Windows Event Log.
Figure 4.23: Setting the ports in the SOAP Trace Utility.
Figure 4.24: Setting the activation mode, URI, and channel format.
Figure 4.25: Examining the output from the SOAP Trace Utility.
Figure 4.26: Examining the output from the SOAP Trace Utility.
Figure 4.27: .NET client to EJB, hosted by J2EE application server with simulated database access.
Figure 4.28: Setting the Java classes for the exposed EJB.
Figure 4.29: Setting the assembly and output directory for the .NET client proxies.
Figure 4.30: Setting the activation mode, URI, and assembly name for the client.
Figure 4.31: Setting the EJB context to expose the EJBs via a Ja.NET WAR file.
Figure 4.32: Configuring the Web application archive to be exported.
Figure 4.33: Java client to .NET object, hosted by Component Services on Windows Server 2003.
Figure 4.34: Using the Component Services administration tool to examine the deployed component.
Figure 4.35: Using the Component Services administration tool to examine the deployed component.
Figure 4.36: Using Microsoft Internet Explorer to test the SOAP VRoot.
Figure 4.37: Setting the .NET assembly and output directory for the Java proxies.
Figure 4.38: Setting the activation mode, URI, and channel format.
Chapter 5: Connectivity with XML Web Services, Part 1
Figure 5.1: The five components of a Web service.
Figure 5.2: Point-to-point interoperability.
Figure 5.3: Extending point-to-point interoperability to the client.
Figure 5.4: Creating a new ASP.NET Web service in Visual Studio .NET.
Figure 5.5: A new Web service in Visual Studio .NET.
Figure 5.6: Viewing the StockService.asmx file in Visual Studio .NET.
Figure 5.7: Creating a new virtual directory in IIS.
Figure 5.8: Setting the Web site content directory for the .NET Web service.
Figure 5.9: The Web service presentation interface.
Figure 5.10: Viewing the XML output from the invoked Web service.
Figure 5.11: Viewing the WSDL document in Microsoft Internet Explorer.
Figure 5.12: Working with the .NET client in Visual Studio .NET.
Figure 5.13: Browsing for Web services within Visual Studio .NET.
Figure 5.14: Viewing the StockService Web reference.
Figure 5.15: Viewing the WSDL document generated by GLUE.
Chapter 6: Connectivity with XML Web Services, Part 2
Figure 6.1: Using GLUE for EJB deployment.
Figure 6.2: Using the Component Services administration tool.
Figure 6.3: Setting the authentication properties for a virtual directory in IIS.
Figure 6.4: Editing the authentication methods for a virtual directory.
Figure 6.5: Transferring data from an LDAP directory to an Active Directory using LDAP replication methods.
Figure 6.6: Adjusting the authentication methods for the virtual directory.
Figure 6.7: Selecting UDDI Services to install on Windows Server 2003.
Figure 6.8: Selecting SSL encryption for the UDDI Services site.
Figure 6.9: Specifying a site name for the UDDI Services site.
Figure 6.10: Setting self-registration for UDDI Services.
Figure 6.11: The Microsoft UDDI Publish Wizard.
Figure 6.12: Specifying a publishing URL for the UDDI site.
Figure 6.13: Setting the name for the new provider, Woodgrove Bank.
Figure 6.14: Creating a new service to purchase stocks.
Figure 6.15: Setting the interface description and WSDL file URL.
Figure 6.16: Selecting the existing provider.
Figure 6.17: Entering the Web service details for the Sell Stocks service.
Figure 6.18: Interface definition for the Sell Stocks service.
Figure 6.19: Using the Web user interface for UDDI Services.
Figure 6.20: Entering the provider name for searches.
Figure 6.21: Search results from UDDI Services.
Figure 6.22: Browsing services available from a provider.
Figure 6.23: Navigating to the binding of a provider.
Figure 6.24: Viewing details of the service.
Figure 6.25: Scenario for the final sample.
Figure 6.26: The home page of the Woodgrove Bank sample.
Figure 6.27: The Buy Stocks page and the UDDI inquiry URL.
Figure 6.28: List of recommendations returned by the Buy Stocks .NET Web service.
Figure 6.29: Selecting a stock to purchase.
Figure 6.30: Viewing the purchase in the Windows Event Log.
Figure 6.31: Selecting the recommendations for stocks to sell.
Figure 6.32: Selecting and processing a stock to sell, using the Java Web service.
Chapter 7: Creating a Shared Database
Figure 7.1: Configuring the SQL Server security properties.
Figure 7.2: Processing the dbscript.sql in Query Analyzer.
Figure 7.3: Creating a database that's shared between .NET and J2EE.
Figure 7.4: Use of the DAO pattern in a shared database environment.
Figure 7.5: A DAO implementation with notifications between the .NET and J2EE tiers.
Figure 7.6: The DAO being used to notify the Windows Forms application of a new addition to the database.
Figure 7.7: The .NET sample client, showing a Windows Form with a record summary.
Figure 7.8: The .NET sample client, showing an updated number of records.
Figure 7.9: The updated operation for the two DAO layers .
Chapter 8: Asynchronous Interoperability, Part 1: Introduction and MSMQ
Figure 8.1: The asynchronous .NET Windows Forms sample.
Figure 8.2: The result, returned back to the client.
Figure 8.3: The Windows Forms client running asynchronously.
Figure 8.4: Installing MSMQ on Windows Server 2003.
Figure 8.5: Options for installing MSMQ on Windows Server 2003.
Figure 8.6: Administering MSMQ through the Computer Management interface.
Figure 8.7: Creating a new, nontransactional queue in MSMQ.
Figure 8.8: Viewing the queues in the MSMQ administration interface.
Figure 8.9: A new stock purchase shown in the MSMQ queue.
Figure 8.10: The body of the stock purchase message.
Figure 8.11: How a JMS provider for MSMQ would be used.
Figure 8.12: How a potential HTTP SRMP client for MSMQ would be used.
Figure 8.13: How a Java-to-COM bridge can be used to access MSMQ from a Java client.
Figure 8.14: Accessing MSMQ using a custom Web service API.
Figure 8.15: Error when trying to expose a
through Web services.
Figure 8.16: Configuring the MSMQInterop virtual directory for authentication.
Figure 8.17: The deployed MSMQInterop Web service.
Figure 8.18: Client and queue configuration in the first sample.
Figure 8.19: Enabling the ASP.NET account to access the queues in the extended sample.
Figure 8.20: The deployed Web service, MSMQInteropExt.
Figure 8.21: The Windows Forms sample application, which monitors the stock purchases and sales.
Figure 8.22: The .NET stock monitor, asynchronously receiving incoming records from the Java client.
Figure 8.23: A request from Alice to purchase $1 million worth of shares.
Figure 8.24: The acknowledgment for the purchase never reaches Alice.
Figure 8.25: Thinking that the send failed, Alice's client software resends the purchase.
Figure 8.26: Alice adds unique message IDs to help avoid duplication.
Figure 8.27: Creating a transactional queue in MSMQ.
Figure 8.28: Dealing with transactional state using Web services.
Figure 8.29: Web services polling approach used in the previous MSMQ transaction example.
Figure 8.30: What's required for a true callback notification.
Chapter 9: Asynchronous Interoperability, Part 2: WebSphere MQ
Figure 9.1: Starting the evaluation installation of WebSphere MQ 5.3.
Figure 9.2: Selecting all the installation options for WebSphere MQ.
Figure 9.3: The WebSphere MQ Explorer administration tool.
Figure 9.4: Creating a new queue manager and making it the default.
Figure 9.5: Setting the logging options for the queue manager.
Figure 9.6: Creating a TCP/IP listener for the queue manager.
Figure 9.7: Viewing the new queue manager in WebSphere MQ Explorer.
Figure 9.8: Creating a new queue named LOCAL.STOCKPURCHASES.
Figure 9.9: Viewing these queues in the WebSphere MQ Explorer.
Figure 9.10: Creating and sending a test message for one of the queues.
Figure 9.11: Configuration for the supplied WebSphere MQ sample code.
Figure 9.12: Viewing the message in WebSphere MQ Explorer.
Figure 9.13: A typical JMS model showing the specification and vendor integration.
Figure 9.14: Setup required for the sample code to show a JMS client accessing WebSphere MQ.
Figure 9.15: A JMS message, as shown in WebSphere MQ Explorer.
Figure 9.16: A pub/sub model showing publishers, topics, and subscribers.
Figure 9.17: An EJB 2.0 MDB component, invoked by a JMS topic.
Figure 9.18: An EJB 2.0 MDB component, invoked by a JMS topic and calling a .NET Web service.
Figure 9.19: The .NET Web service confirms the purchase via the event log.
Figure 9.20: JMS support in GLUE and interoperability with WebSphere MQ.
Figure 9.21: Asynchronous call styles between the services using GLUE's support for JMS.
Chapter 10: Asynchronous Interoperability, Part 3: Bridging with Host Integration Server
Figure 10.1: Example environment required to run the MSMQ- MQSeries bridge sample.
Figure 10.2: Installing the required MSMQ components for the bridge.
Figure 10.3: Installing the required WebSphere MQ client component for the bridge.
Figure 10.4: Installing the required Host Integration Server 2000 componentsthe bridge itself.
Figure 10.5: Creating the new foreign site in Active Directory.
Figure 10.6: Creating the new foreign computera reference to the WebSphere queue manager.
Figure 10.7: Correctly setting the security to allow the bridge to open the connector queue.
Figure 10.8: Configuring the MSMQ routing link in Active Directory.
Figure 10.9: Configuring the site gates in Active Directory.
Figure 10.10: Adding the foreign site to the MSMQ-MQSeries bridge.
Figure 10.11: Logical representation of how the queues will be configured.
Figure 10.12: Creating the local stock sales sample queue in MSMQ.
Figure 10.13: The Active Directory Users And Computers administration tool, showing the foreign site queue.
Figure 10.14: Using the MSMQ-MQSeries Bridge Manager.
Figure 10.15: Defining the channel properties for the connection to the WebSphere MQ server.
Figure 10.16: Correctly setting the address details for the WebSphere MQ server.
Figure 10.17: Creating and configuring the CN properties for the bridge.
Figure 10.18: A view of the four message pipes within the MSMQ- MQSeries Bridge Manager.
Figure 10.19: The objects created by importing the scripts on the WebSphere MQ server.
Figure 10.20: Creating the local stock sales remote definition on the WebSphere MQ server.
Figure 10.21: The two message pipes running within the MSMQ- MQSeries Bridge Manager.
Chapter 11: Asynchronous Interoperability, Part 4: BizTalk Server
Figure 11.1: Starting the BizTalk Server 2004 Configuration Wizard.
Figure 11.2: Setting the Windows accounts for access control.
Figure 11.3: Specifying the database locations for BizTalk Server.
Figure 11.4: Defining the Microsoft Windows NT Service configurations.
Figure 11.5: Launching the Host Creation Wizard.
Figure 11.6: Setting the host name and user group settings.
Figure 11.7: Setting the isolated host name and user group settings.
Figure 11.8: The sample stock processes orchestration running on BizTalk Server 2004.
Figure 11.9: Creating the new virtual directory for the buy stocks Web service.
Figure 11.10: Specifying the location of the Web service files.
Figure 11.11: Creating the virtual directory for the .NET pricing Web service.
Figure 11.12: The orchestration designer, as shown in Visual Studio .NET 2003.
Figure 11.13: The incoming order port within the orchestration.
Figure 11.14: The outgoing port to the .NET pricing Web service.
Figure 11.15: The list of Web references used by the BizTalk Server project.
Figure 11.16: The Decision shape, used to branch based on the value of the order.
Figure 11.17: The call to the Java-based naming Web service.
Figure 11.18: The Decision shape used to determine whether the process is a purchase or sale.
Figure 11.19: A transform showing the mapping between an order and outgoing request.
Figure 11.20: The final, late-bound outgoing port.
Figure 11.21: Viewing the BizTalk Explorer within Visual Studio .NET.
Figure 11.22: Adding a new incoming port.
Figure 11.23: Configuring the details for the incoming port.
Figure 11.24: Setting the folder properties for the FILE transport.
Figure 11.25: Configuring the details for the new Receive Location.
Figure 11.26: Creating a new send port.
Figure 11.27: Configuring the destination for the FILE transport.
Figure 11.28: Completing the configuration of the outgoing port.
Figure 11.29: Setting the properties for the outgoing port.
Figure 11.30: Launching the BizTalk Deployment Wizard and selecting an action.
Figure 11.31: Selecting the BizTalk Server database to perform the deployment.
Figure 11.32: Specifying the location of the BizTalk Server assembly and bindings file.
Figure 11.33: Checking the binding properties for the orchestration.
Figure 11.34: Checking the host properties for the orchestration.
Figure 11.35: Selecting dependencies and starting the orchestration.
Figure 11.36: The final confirmation of the order generated by the orchestration.
Chapter 12: Presentation Tier Interoperability
Figure 12.1: Replacing the J2EE presentation tier with ASP.NET.
Figure 12.2: A presentation tier consisting of JSP, Servlets, and ASP.NET pages.
Figure 12.3: Layout of a Web portal consisting of many integrated parts .
Figure 12.4: Using the Query Analyzer to configure the shared session state database.
Figure 12.5: Creating a new virtual directory for the test client.
Figure 12.6: Specifying the directory for the shared session state test client.
Figure 12.7: Viewing the Servlet standalone.
Figure 12.8: Viewing the Servlet, presented within an ASP.NET page.
Figure 12.9: The Servlet displays additional information based on values in the shared session state for the Northwind Traders company.
Figure 12.10: The Servlet running outside the ASP.NET page, but with the shared session context.
Figure 12.11: A JSP page that displays the values in shared session.
Figure 12.12: Output from
SELECT * FROM REGISTRATION
Figure 12.13: Output from
SELECT * FROM OBJECT_LOOKUP
Figure 12.14: Output from
SELECT * FROM OBJECT
Figure 12.15: Database schema used for the shared session state database table.
Figure 12.16: Using a shared session API for both the JSP and ASP.NET presentation tiers.
Figure 12.17: Incoming HTTP page request for the ASP.NET presentation tier.
Figure 12.18: Incoming request is redirected to a registration JSP.
Figure 12.19: Intercepting Servlet filter creates a new session in the shared session database.
Figure 12.20: After registration, request is redirected to the original page.
Figure 12.21: Once a shared session has been created, other requests are treated normally.
Figure 12.22: The registration process in the opposite direction.
Figure 12.23: Running the shared session state performance test.
Figure 12.24: Using forms authentication to display a login.aspx page for ASP.NET.
Figure 12.25: Authentication also applies for the Servlet hosted within the ASP.NET page.
Chapter 13: Web Services Interoperability, Part 1: Security
Figure 13.1: Point-to-point security using HTTPS (also applies to HTTP Authentication).
Figure 13.2: Point-to-point security using transport security and an intermediary.
Figure 13.3: Point-to-point security showing secure and insecure transports.
Figure 13.4: Creating the .NET WS-Security Authentication virtual directory.
Figure 13.5: Setting the path for the virtual directory.
Figure 13.6: Validating the secure purchase recommendation operation.
Figure 13.7: Disabling the Show Friendly HTTP Error Messages setting in Internet Explorer.
Figure 13.8: Selecting a certificate to sign the Web services request.
Figure 13.9: Validating the Web service with Internet Explorer.
Chapter 14: Web Services Interoperability, Part 2: Sending Binary Data
Figure 14.1: How the sample code is used to send attachments from a Java client to .NET.
Figure 14.2: Creating the virtual directory required for the .NET Web service.
Figure 14.3: Specifying the directory for the .NET Web service.
Figure 14.4: The Microsoft Word document that will be exchanged.
Chapter 15: Web Services Interoperability, Part 3: Routing
Figure 15.1: Message flow using sender, intermediaries, and an endpoint.
Figure 15.2: Message request and flow for sample code.
Figure 15.3: Message response and flow for sample code.
Figure 15.4: Testing the Pricing Web service by using Microsoft Internet Explorer.
Figure 15.5: Current route used by the sample code.
Figure 15.6: How WS-Referral can dynamically set the route by using the referralCache.config file.
Table of content
Microsoft .NET and J2EE Interoperability Toolkit (Pro-Developer)
BUY ON AMAZON
Interprocess Communications in Linux: The Nooks and Crannies
Key Terms and Concepts
Key Terms and Concepts
Message Queue Operations
C.4. Some RPC Examples
Microsoft Windows Server 2003(c) TCP/IP Protocols and Services (c) Technical Reference
Local Area Network (LAN) Technologies
Point-to-Point Protocol (PPP)
Transmission Control Protocol (TCP) Data Flow
File and Printer Sharing
Virtual Private Networks (VPNs)
File System Forensic Analysis
The Big Picture
Sap Bw: a Step By Step Guide for Bw 2.0
Using BW Monitor
Managing User Authorization
Replicating R/3 DataSources
Section B.3. Memory Management
Quantitative Methods in Project Management
Introduction to Probability and Statistics for Projects
Organizing and Estimating the Work
Quantitative Time Management
Special Topics in Quantitative Management
Quantitative Methods in Project Contracts
.NET-A Complete Development Cycle
Choosing a Software Development Model
GDI+ Graphics Extensions
Implementing Dynamically Loadable Image Postprocessing Plugins
flylib.com © 2008-2017.
If you may any questions please contact us: firstname.lastname@example.org
to find out more.