9780131472235

The definitive guide to patterns and strategies that solve the challenging problems with J2EE and .NET integration.

Marina Fisher is a staff engineer at Sun Microsystems Ray Lai is a principal engineer from Sun's Chief Technologist's Office and specializes in financial services and SOA solutions Sonu Sharma is an engagement manager with Client Solutions Organization at Sun Laurence Moroney is the director for technology evangelism for Mainsoft

Foreword	p. xxiii
Acknowledgments	p. xxv
About the Authors	p. xxvii
Introduction	p. xxix
Java EE .NET Interoperability	p. 1
Java EE Platform Interoperability Essentials	p. 3
Java EE Platform	p. 4
Java EE Architecture	p. 5
Interoperability Capabilities	p. 14
Summary	p. 19
References	p. 20
.NET Platform Interoperability Essentials	p. 21
Emergence of the .NET Platform	p. 21
The Common Language Infrastructure and Runtime	p. 22
The .NET Framework Class Library	p. 24
Integration Capabilities in the .NET Framework	p. 25
Interoperability Using Synchronous Web Services	p. 27
Interoperability Using Asynchronous Web Services	p. 28
Interoperability Using .NET Remoting	p. 29
Interoperability Using Messaging Technologies	p. 30
Other Technologies for Interoperability	p. 30
Interoperability Using Web Services Enhancements (WSE)	p. 32
Interoperability Using Windows Communication Foundation (WCF)	p. 33
Summary	p. 36
References	p. 37
Synchronous Integration Solutions	p. 39
Exploring Synchronous Integration	p. 41
Introduction	p. 41
Using Synchronous Integration	p. 43
Web Services for Synchronous Integration	p. 44
Interoperability Using Web Services	p. 45
.NET Remoting for Synchronous Integration	p. 46
Resource Tier Synchronous Integration	p. 46
Reference	p. 47
Web Services for Synchronous Integration	p. 49
Web Services Technology Overview	p. 49
Building Synchronous Web Services with .NET and Java EE	p. 58
Advanced Web Services Interoperability	p. 69
Advanced Web Services Technologies	p. 72
Best Practices and Pitfalls	p. 82
Summary	p. 90
References	p. 90
.NET Remoting for Synchronous Integration	p. 93
Introduction	p. 93
IIOP.NET for Java EE .NET Integration	p. 94
J-Integra for Java EE .NET Integration	p. 104
JNBridge for Java EE .NET Integration	p. 118
Summary	p. 131
Resource Tier Synchronous Integration	p. 133
Introduction	p. 133
Data Access Adapter Strategy	p. 148
Legacy Integration	p. 156
Summary	p. 158
References	p. 158
Asynchronous Integration Solutions	p. 163
Exploring Asynchronous Integration	p. 165
Overview	p. 165
Using Asynchronous Integration	p. 166
Asynchronous Web Services Integration	p. 169
Introduction	p. 169
Automatic Callback Strategy	p. 173
Implementing .NET Manufacturing System	p. 186
Response Polling Strategy	p. 220
Related Patterns	p. 235
Best Practices and Pitfalls	p. 238
Summary	p. 245
References	p. 246
Messaging	p. 247
Introduction	p. 247
Implementing Messaging in Java and .NET	p. 250
Bridging Strategy	p. 258
Adapter Strategy	p. 274
Web Services Messaging Strategy	p. 280
Internet E-Mail for Asynchronous Messaging	p. 300
Enterprise Service Bus	p. 313
References	p. 319
Resource Tier Asynchronous Integration	p. 323
Introduction	p. 323
Indirect Data Access Strategy	p. 326
Distributed Mediator Strategy	p. 328
Data Access Proxy Strategy	p. 332
Summary	p. 350
References	p. 350
Addressing Quality of Service Requirements	p. 353
Addressing Quality of Services	p. 355
Quality of Services-Core Issues	p. 355
Myths and Truths about Quality of Services	p. 357
Understanding the QoS Requirements	p. 358
Related Technologies and Standards	p. 364
Summary	p. 365
Managing Distributed Transactions	p. 367
Introduction	p. 367
Foundation of Transactional Integrity	p. 368
Java EE and .NET Transaction Support	p. 372
The .NET Transaction Support	p. 379
Transactional Interoperability Across Java EE and .NET	p. 384
Commercial Products	p. 395
Related Patterns	p. 396
Best Practices and Pitfalls	p. 398
Summary	p. 400
References	p. 400
Java EE .NET Security Interoperability	p. 403
Security by Default	p. 403
Java Security by Design	p. 405
.NET Security by Design	p. 410
Security for Interoperability	p. 414
Security Standards for Interoperability	p. 419
Secure Object Handler Strategy	p. 444
Secure Tracer Strategy	p. 475
Related Patterns	p. 479
Best Practices and Pitfalls	p. 480
Summary	p. 481
References	p. 482
Java EE .NET Reliability, Availability, and Scalability	p. 485
Java EE .NET Applications on Steroids	p. 485
Understanding the Current State of Technology	p. 489
Best Practices and Pitfalls	p. 505
Summary	p. 506
References	p. 507
Managing Java EE .NET Interoperability Applications	p. 509
Managing Mixed Java EE and .NET Environments	p. 510
ISO Management Elements in Java EE .NET Platforms	p. 514
Management Scenario	p. 517
Web Services Management Strategy	p. 519
Platform Unification Strategy	p. 527
Related Patterns	p. 534
Impact of Interoperability on Management	p. 542
Best Practices and Pitfalls	p. 548
Summary	p. 548
References	p. 550
Implementation	p. 555
Migrating .NET Applications to Java	p. 557
Introduction	p. 557
Porting Guidelines	p. 559
The Porting Scenario	p. 563
Building the Scenario Using Microsoft.NET	p. 564
Porting by Rewriting the Code in Java	p. 569
Porting Using Mainsoft's Visual Main Win for Java EE	p. 579
Summary	p. 585
References	p. 586
Index	p. 589
Table of Contents provided by Ingram. All Rights Reserved.

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

= 0) {slash = '\\';} else {slash = '/';}openLoc = figLoc.substring(0, figLoc.lastIndexOf(slash) + 1);while (pPage.substring(0,3) == '../') {openLoc = openLoc.substring(0, openLoc.lastIndexOf(slash, openLoc.length - 2)+ 1);pPage = pPage.substring(3, pPage.length + 1);}popUpWin =window.open('','popWin','resizable=1,scrollbars=1,location=0,toolbar=0,width=525,height=394');figDoc = popUpWin.document;zhtm= ' ' + pPage + ' ';zhtm += ' ';zhtm += ' ';zhtm += ' ';zhtm += '' + pPage.substring(pPage.lastIndexOf('/') + 1, pPage.length) + '';zhtm += ' ';figDoc.write(zhtm);figDoc.close();}// modified 3.1.99 RWE v4.1 --> Introduction: Achieving Interoperability Introduction: Achieving Interoperability Business ChallengesIt is a common trait for business to have large and diverse systems and a rare one for them to have unified systems. Be it through acquisitions, mergers, staff and policy turnover, or a hundred other reasons the fact remains--they have systems built in different languages, running on different software platforms, and targeting different hardware. Add on top of this the need for businesses to be increasingly more nimble--fueling a requirement for integrated, interoperating systems that can aggressively respond to business requirements coherently and quickly--and you have a major challenge facing businesses today.A few years ago the typical business data system was a simple, monolithic affair with business assets in a mainframe that were accessible via a tightly coupled user interface. Transfer of assets between domains was usually manual--for example the transfer of an order from a sales-facing system to a realization and delivery system was typically done by an operator keying in details of a printout from one system to the other. The operator herself was the interoperability layer.Over time as systems evolved, technologies evolved to allow networking and to automatically integrate across protocols such as CORBA. These, however, proved to be very difficult and expensive to develop and maintain.Today's landscape sees the data center split into two main deployment types. On one side is the Microsoft stack of products, covering everything except the hardware, from the operating system through the software platform to the application, with the Windows Server family and the .NET framework and runtime. Developers have a host of tools that allow them to develop and target this platform and can receive exceptional time to market and cost of development metrics. On the other side is the open family of Java EE software frameworks, which can run on a variety of hardware platforms and that run applications written with the Java language. With this it has been sh

Amazon no longer offers textbook rentals. We do!

Java EE and .NET Interoperability Integration Strategies, Patterns, and Best Practices

Java EE and .NET Interoperability Integration Strategies, Patterns, and Best Practices

0131472232

Summary

Author Biography

Table of Contents

Supplemental Materials

Excerpts

Write a Review