Java EE and .NET Interoperability: Integration Strategies, Patterns, and Best Practices [Paperback]

Marina Fisher (Author), Ray Lai (Author), Sonu Sharma (Author), Laurence Moroney (Author)

Book Description

ISBN-10: 0131472232 | ISBN-13: 978-0131472235 | Publication Date: May 1, 2006 | Edition: 1

 “It’s a fact the .NET and Java platforms exist in the enterprise with many touch points. Developers are very eager for information and examples on how the two environments can coexist. This book reflects our interoperability collaboration with Sun and provides best practices for using Web services to bridge .NET and Java applications.”

—DAN’L LEWIN

corporate vice-president,

Developer & Platform Evangelism, Microsoft Corp.

 

“This book is a developer handbook for implementing interoperable applications and services. It includes actionable strategies for developers and best practices from the field experience.”

—GREG PAPADOPOULOS

chief technology officer, Sun Microsystems

 

“A comprehensive, practical guide to developing applications that cross the Java EE .NET boundary.”

—BILL SMITH

director business alliances, Sun Microsystems

 

“Efficient, effective interoperability between Java EE and .NET is a crucial element in the IT architecture of large enterprises and is vital to running a successful business. This book takes interoperability to the next level, far beyond the cold coexistence of systems, by describing effective strategies that allow you to achieve true interoperability while reducing complexity in your applications and your data center. Additionally, it provides examples and practical advice on how to achieve this new level of interoperability and covers in depth all of the options available from bridging, to porting, to platform unification. The costs that this can save you, from management, maintenance and server consolidation are very significant.”

—YAACOV COHEN

chief executive officer, Mainsoft

 

“A complete and up-to-date coverage of Java EE .NET security interoperability standards and related specifications.”

—HUBERT A. LE VAN GONG

architect, Sun Microsystems, and the

coauthor of “Web SSO MEX Specification”

 

Evolving Web services standards and technologies offer limited interoperability when it comes to security, management, and other important application characteristics. Successful interoperability solutions require comprehensive integration strategies that go beyond simple connections. The capability to mitigate security and reliability risks and transactional support is critical to interoperability.

 

Java EE and .NET Interoperability addresses issues encountered during the integration process, such as a diverse technology set, incompatible APIs, and disparate environment maintenance. The experienced authors outline strategies, approaches, and best practices, including messaging, Web services, and integration-related frameworks and patterns. The book also introduces readers to Service Oriented Architecture (SOA), the building block for scalable and reliable enterprise integration solutions.

 

This indispensable book provides the Java EE and .NET developer community with multiple strategies to integrate between Java EE and .NET platforms that save developers time and effort. Applying proven interoperability solutions significantly reduces the application development cycle. Coverage includes

·         Effective Java EE–.NET integration strategies and best practices

·         Detailed enterprise coverage, as well as standalone Java EE component integration with .NET

·         SOA as a building block for Java EE–.NET interoperability

·         Interoperability security issues and risk mitigation

·         Managing reliability, availability, and scalability for Web services built on Java EE and .NET

·         The latest interoperability standards and specifications, including Web SSO MEX and WS-Management

·         Current interoperability technologies, such as Windows Communication Foundation, WSE 3.0, JAX-WS, and Enterprise Service Bus

Editorial Reviews

About the Author

MARINA FISHER is a staff engineer at Sun Microsystems. As a Sun Certified Enterprise Architect for Java EE, she provides Sun’s Fortune 500 customers with assistance in architecting, designing, implementing, and deploying large-scale enterprise applications. Her background spans across financial, retail, manufacturing, and other sectors, with emphasis on Service Oriented Architecture (SOA), interoperability, and application security.

 

RAY LAI, a principal engineer from Sun Microsystems Chief Technologist’s Office, specializes in financial services and SOA solutions. He has developed and architected enterprise applications for leading multinational companies around the globe. He is also the author of the book, J2EE Platform Web Services, and coauthored Core Security Patterns. His current technology focus includes application security and JSF/AJAX-style prototyping.

 

SONU SHARMA is an engagement manager with Client Solutions Organization at Sun Microsystems Inc. Sonu specializes in managing, architecting, and implementing scalable, reliable, and high-performance business critical enterprise applications using Java EE and XML Web Service technologies for Sun’s Fortune 500 customers. Prior to working at Sun, Sonu has worked on architecting, designing, and building enterprise solutions in the fields of e-commerce, banking, and insurance.

 

LAURENCE MORONEY is the director for technology evangelism for Mainsoft where he is responsible for sharing and shaping their unified .NET and Java EE architecture to enable and empower interoperability. Prior to Mainsoft he worked as a Senior Architect in the Reuters CTO office where he worked on research into Web Services Interoperability, Social Computing, and Trading Networks. Author of several books on Web Services and .NET, as well as dozens of technology articles, Laurence is based in Sammamish, Washington.

 

Excerpt. © Reprinted by permission. All rights reserved.

Introduction: Achieving Interoperability

Business Challenges

It 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 shown that they offer exceptional runtime characteristics. Technologies such as Enterprise Java Beans (EJB) are designed with the characteristics of security, scalability, manageability, and performance in mind and are particularly useful in large-scale systems that serve large numbers of users.

However, getting an effective data center implementation of a product that utilizes these two sets of assets is a difficult process. Development management has often had to choose between the productivity of the .NET environment and the runtime characteristics of the Java EE platform. Having a "best of both worlds" solution was difficult given that there were few easy or cheap ways to get products running on these platforms to talk to each other effectively.

Consider the example of a company whose system is the result of several mergers and acquisitions and has an array of databases implemented on different technologies—diverse hardware for applications; different runtime platforms; and applications of varying architectures. Integrating this system would be a very challenging process indeed.

Enter Web services—abstract entities that encapsulate business processes and expose them via a standard interface. The underlying implementation doesn't matter! In the example just mentioned, each system's data retrieval layer can wrap itself in a Web service so that it exposes a standard interface. Then the development manager who wants to use his junior staff who are great at quickly putting together ASP.NET or JSP pages has an ideal opportunity to make the most of Web services technology and build a front end that can consume these Web services via proxies. It should be easy, but it isn't.

Why? Because while standards may be, well, standard—different implementers of software that uses these standards and allows you to build software that exposes these standards have done it in slightly different ways. These different ways mean that not everything that is wrapped with a Web service can talk cleanly to everything else that knows how to talk to a Web service. This interoperability is not as simple as it should be.

This, then, gives rise to a book such as this one in your hands. Armed with the knowledge that you'll gain from reading this book, you'll be able to go forth into your development team or data center and either solve interoperability problems you're having or, better still, design a system that doesn't suffer from interoperability problems.

Technology for Interoperability

There are several technology solutions for interoperability covered in this book. The first and most obvious one is Web services, whereby you can wrap your business entities in a standards-based layer so that their technology implementation is abstracted. Therefore, anything that interacts with this layer doesn't need to know about the technology that drives it and should interoperate cleanly. It's a powerful and compelling methodology, but it is not without its drawbacks. It is challenged in two main areas—diverse support for standards and performance. Strategies for handling these are used throughout the book.

A well-known and well-used methodology for integration and interoperability is the use of a messaging platform. This is where communication between layers is done through simple messages passed through managed queues. Technologies such as JMS, MQSeries, and MSMQ are examples of this. They can make for a very powerful and very performant interoperability layer, particularly where there are real-time requirements.

Another technology, platform unification, allows for clean interoperability between .NET and Java EE applications. With this concept the runtime layer is unified, and application developers for one language can deploy their applications to the runtime traditionally used by another. For example .NET developers can rehost their applications on Java EE. As such, the .NET and Java EE applications don't need to go through a separate layer to talk to each other—they are on the same platform and can talk cleanly. Interoperability doesn't just have to happen at the application layer; it can also take place on the resource tier. With new technologies allowing more and more business logic to be driven closer to the database, interoperability problems may also be solved. As the application layers get thinner, the easier it is for them to communicate with each other.

Structure of the Book

This book covers two main constituents of any Java EE–.NET integration. The first one pertains to the integration type such as synchronous or asynchronous, outlining how individual Java and .NET components can integrate using their diverse technology set. The second constituent relates to the quality of service requirements, such as security, reliability, and scalability, essential to meet a Service Level Agreement (SLA) across the heterogeneous enterprise environment. If you take a closer look at the book structure, you'll notice that the book represents a catalog of integration strategies that adheres to the following format:

• Strategy Name The strategy has a unique name that reflects its objective.

• Problem space Each strategy aims to address a specific Java EE–.NET interoperability problem. Asynchronous reliable integration is an example of such a problem.

• Solution This part of the strategy details a strategy design and outlines technology choices.

• Benefits and Limitations Any interoperability strategy has its pros and cons that are highlighted here. For example, ease of maintenance or scalability are common benefits of some of the strategies.

• Related Patterns Industry patterns such as Core J2EE Patterns are used throughout this book to bring those that are familiar to you into the scope of Java EE–.NET integration. Are there similar resources in the .NET space?

• Example Throughout the book,...

Product Details

• Paperback: 648 pages
• Publisher: Prentice Hall; 1 edition (May 1, 2006)
• Language: English
• ISBN-10: 0131472232
• ISBN-13: 978-0131472235
• Product Dimensions: 9.2 x 7.4 x 1.2 inches
• Shipping Weight: 2 pounds
• Average Customer Review: 3.3 out of 5 stars  See all reviews (3 customer reviews)
• Amazon Best Sellers Rank: #2,238,879 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

7 of 9 people found the following review helpful:

3.0 out of 5 stars Not detailed enough and poor examples, May 23, 2006

By 

Desmond Kehoe "Des" (Denver, CO) - See all my reviews

This review is from: Java EE and .NET Interoperability: Integration Strategies, Patterns, and Best Practices (Paperback)

The first couple of chapters are OK. Thereafter I found the integration concepts and strategies half done and hardly complete. The code examples are not commented at all. I noticed the code would work only on sun application server and the configuration details are not discussed are missing. I tried to deploy the code example using websphere 6 it did'nt run at all. The chapters in part3 and part4 are more of theoretical coverage and kind of standards work in progress. In comparison, I like Application Interoperability - Patterns and Best Practices from Microsoft Press over this book. This book did'nt help me at all.

3 of 4 people found the following review helpful:

4.0 out of 5 stars Good information for the right audience..., May 21, 2006

By 

Thomas Duff "Duffbert" (Portland, OR United States) - See all my reviews
(VINE VOICE)    (TOP 500 REVIEWER)    (HALL OF FAME REVIEWER)    (REAL NAME)   

This review is from: Java EE and .NET Interoperability: Integration Strategies, Patterns, and Best Practices (Paperback)

As much as Microsoft might want you to be an all-.NET shop, the reality of the enterprise computing environment is that both .NET and Java will be used in some way, shape, or form. If you're a developer or architect responsible for integrating platforms, this book could help you out... Java EE and .NET Interoperability : Integration Strategies, Patterns, and Best Practices by Marina Fisher, Ray Lai, Sonu Sharma, and Laurence Moroney.

Contents:
Part 1 - Java EE .NET Interoperability: Java EE Platform Interoperability Essentials; .NET Platform Interoperability Essentials
Part 2- Synchronous Integration Solutions: Exploring Synchronous Integration; Web Services for Synchronous Integration; .NET Remoting for Synchronous Integration; Resource Tier Synchronous Integration
Part 3 - Asynchronous Integration Solutions: Exploring Asynchronous Integration; Asynchronous Web Services Integration; Messaging; Resource Tier Asynchronous Integration
Part 4 - Addressing Quality of Service Requirements: Addressing Quality of Services; Managing Distributed Transactions; Java EE .NET Security Interoperability; Java EE .NET Reliability, Availability, and Scalability; Managing Java EE .NET Interoperability Applications
Part 5 - Implementation: Migrating .NET Applications to Java
Index

The book is targeted towards developers as well as architects and managers responsible for these types of projects. The focus and approach tends more towards the practical, "here's one way to do it" methodology. There's no hesitation to suggest third-party frameworks and applications to help you accomplish something, as well as providing enough code to allow the reader to get a feel for how it all fits together. It's not a comprehensive approach to every last thing you need to know, but if you're charged with platform integration, this will give you the practical foundation you'll need to start examining the options available to you.

Given the right needs and the right audience, it'll offer value to the reader...

3 of 5 people found the following review helpful:

3.0 out of 5 stars Not deep enough and poor examples., June 30, 2006

By 

J Philbin (Dallas, TX) - See all my reviews

This review is from: Java EE and .NET Interoperability: Integration Strategies, Patterns, and Best Practices (Paperback)

This book covers many topics, unfortunately it does not go into great detail and less than a hello world example. I am confused and don't know what the authors really mean about interoperbility with this book. The content is a bit vague and poorly written. The examples are hardly usable and the best practices sections does'nt make sense. Some of the topics covered have nothing to do with interoperability, they are integration topics. If you are really looking integration guidance, choose Enterprise Integration Patterns by Gregor Houpe et all.