This document discusses using JNBridgePro to enable cross-platform interoperability between Java and .NET applications within a single cloud. It provides examples of using JNBridgePro to allow .NET applications to access Java components and APIs, and vice versa, including accessing REST APIs, web services, and migrating applications between platforms like EC2 and Azure.

1. Cross-Platform Interoperability Within a Single Cloud Have .NET-based applications call Java components, or vice versa, within a single cloud instance. Java Application .NET Components .NET Application Java Components

2. Access REST-based API from .NET Application Acme Corporation has implemented a cloud service with an extensive REST-based API. Based on Acme’s target market, they’ve created a Java-based client library that encapsulates the REST-based services. Allied Widgets, Inc., a .NET-based enterprise, really wants to use Acme’s new service, and cannot wait for Acme to deliver .NET-based stubs, if indeed Acme ever will. Not having the experience or the desire to create their own .NET-based stubs, Allied Widgets uses JNBridgePro to bridge between their application and Acme’s Java-based stubs, which allows them to communicate with the REST service. Java Stubs .NET App Java Library Java App REST API

3. Access anyWeb Service from the Other Platform Needing to access NewsLine’s Java-based cloud service from their .NET-based consuming application, GetPost Corp. creates an interoperability layer with JNBridgePro that bridges between their application and the Java-based stubs that do know how to talk to the Java-based service. PostGet Inc. solved the same problem but in the opposite direction. Java Web Service Java Stubs .NET App SOAP or REST .NET Web Service .NET Stubs Java App SOAP or REST

4. Access anyWeb Service from the Other Platform Better yet, NewsLine decided to enable their .NET-based consumers to access NewsLine’s Java-based cloud service directly. NewsLine created a JNBridgePro interop layer, hosted it in their Java-based cloud, and made it downloadable and easily usable by the consumer, with configuration information already included. Java Web Service .NET App .NET Stubs

5. Move Presentation Layer from Java/EC2 to ASP.NET on Azure An e-commerce site is implemented using Java on EC2, as a three-tier architecture. The company wants to re-implement their presentation layer using ASP.NET, and move it over to Windows Azure to utilize some of its elasticity features. JNBridgePro links the new Azure-based presentation layer to the Java/EC2-based business logic layer. Presentation Business Logic Presentation Data EC2 Azure

6. Exchange Data with Trading Partner on Other Platform A Java-based enterprise needs to do business with a .NET-based trading partner that has a message broker service in the cloud that is .NET-centric. The Java-based enterprise uses JNBridgePro to create an adapter that allows them to link their Java-based software to the message-broker service. Java-based Enterprise .NET-based Trading Partner .NET Message Broker

7. Access Management APIs on Java-based and .NET-based Clouds Simple Software has developed a cloud management service for customers who run in multiple clouds, including Azure and EC2. The service provides a control and management dashboard, and Simple Software has chosen EC2 as their cloud platform. The Simple Cloud Service uses JNBridgePro to access the .NET-based management APIs in Azure clouds. Java Service .NET API Java API

8. Offer New Java-based Cloud Service using .NET-based Library Quatro Bank is creating a derivatives pricing service for traders around the world. The service is based in Java and runs on EC2. However, Quatro Bank has a considerable investment in a .NET-based derivatives pricing library, which contains business knowledge they cannot easily replace. Quatro Bank uses JNBridgePro to incorporate the crucial .NET library into their new Java-based trading service. Java .NET Pricing Library EC2

9. Implement Persistent Services to Migrate Legacy Applications Legacy applications that depend on data-persistence APIs cannot easily be migrated to platforms like Azure. With JNBridgePro, you can implement persistent services on a different cloud platform, and create an API to mimic the functionality of the non-existent legacy registry or file-system APIs. .NET Legacy App Database Service with Java API .NET API Azure EC2

10. Call APIs from Other Frameworks Some cloud-framework APIs, such as the Azure cloud drive API, are designed to only be called from cloud-based programs in that framework. JNBridgePro enables these APIs to be called from anywhere: on the ground in either platform, or from a different cloud on the other framework. Cloud Drive API Java Application Java App Azure EC2

11. Migrate Existing Integrated Systems to the Cloud Widget Warehouse has developed extensive in-house inventory applications that rely on both Java and .NET, and use JNBridgePro to integrate their disparate systems. Widget Warehouse now wants to take advantage of the elasticity offered by the cloud. They can migrate their existing Java-based and .NET-based components into the cloud, along with JNBridgePro. Just as on the ground, the Java and .NET components can run on the same servers or different servers, depending on need. .NET Java