<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://interopvendoralliance.org/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Intrinsyc</title><subtitle type="html" /><id>http://interopvendoralliance.org/blogs/intrinsyc/atom.aspx</id><link rel="alternate" type="text/html" href="http://interopvendoralliance.org/blogs/intrinsyc/default.aspx" /><link rel="self" type="application/atom+xml" href="http://interopvendoralliance.org/blogs/intrinsyc/atom.aspx" /><generator uri="http://communityserver.org" version="2.1.60803.893">Community Server</generator><updated>2007-01-05T15:24:00Z</updated><entry><title>J-Integra for Exchange</title><link rel="alternate" type="text/html" href="http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-for-Exchange.aspx" /><id>http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-for-Exchange.aspx</id><published>2007-01-05T21:14:00Z</published><updated>2007-01-05T21:14:00Z</updated><content type="html">&lt;h2&gt;Overview&lt;/h2&gt;
          &lt;p&gt;J-Integra for Exchange is a high performance middleware bridge that enables Java Exchange interoperability.
          Its pure Java implementation of the DCOM wire protocol allows you to access Exchange server objects
          such as folders, messages, contacts, tasks, and calendar items from Java clients.&lt;br /&gt;&lt;/p&gt;
          

          &lt;h2&gt;Point-to-Point Interoperability&lt;/h2&gt;


          &lt;p&gt;J-Integra for Exchange can be used for point-to-point integration scenarios where the
          Java application that needs to communicate with Exchange doesn&amp;#39;t need to plug into a common integration
          infrastructure (such as an ESB).&lt;/p&gt;&lt;p&gt;&lt;a href="http://j-integra.intrinsyc.com/products/exchange/architecture.html"&gt;&lt;img src="http://j-integra.intrinsyc.com/images/point2point_exchange_small.jpg" alt="J-Integra for Exchange Architecture Diagram" /&gt;
              &lt;br /&gt;click to enlarge&lt;/a&gt; &lt;/p&gt;&lt;p&gt;For more information, see &lt;a href="http://j-integra.intrinsyc.com/products/exchange/" target="_blank"&gt;http://j-integra.intrinsyc.com/products/exchange/&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;&lt;img src="http://interopvendoralliance.org/aggbug.aspx?PostID=239" width="1" height="1"&gt;</content><author><name>Intrinsyc</name><uri>http://interopvendoralliance.org/members/Intrinsyc.aspx</uri></author><category term="Solutions Guidance" scheme="http://interopvendoralliance.org/blogs/intrinsyc/archive/tags/Solutions+Guidance/default.aspx" /></entry><entry><title>J-Integra for COM</title><link rel="alternate" type="text/html" href="http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-for-COM.aspx" /><id>http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-for-COM.aspx</id><published>2007-01-05T21:14:00Z</published><updated>2007-01-05T21:14:00Z</updated><content type="html">&lt;h2&gt;Overview&lt;/h2&gt;
          &lt;p&gt;J-Integra for COM is a high performance middleware bridge that enables Java COM interoperability.
          Its pure Java implementation of the DCOM wire protocol allows you to access COM components
          from Java clients, and Java objects from COM clients.&lt;br /&gt;&lt;/p&gt;

          
          &lt;h2&gt;Point-to-Point Interoperability&lt;/h2&gt;

          &lt;p&gt;J-Integra for COM can be used for point-to-point integration scenarios where the two
          applications that need to communicate with each other don&amp;#39;t need to plug into a common integration
          infrastructure (such as an ESB). Example use case scenarios include:&lt;/p&gt;

          &lt;ul&gt;&lt;li&gt;Java desktop application invoking COM application&lt;/li&gt;&lt;li&gt;J2EE Server invoking COM application&lt;/li&gt;&lt;li&gt;VB/C++ client interaction with a J2EE Server&lt;/li&gt;&lt;li&gt;IIS/ASP interaction with a J2EE Server&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;a href="http://j-integra.intrinsyc.com/products/com/architecture.html"&gt;&lt;img src="http://j-integra.intrinsyc.com/images/point2point_com_small.jpg" alt="J-Integra for COM Architecture Diagram" /&gt;
              &lt;br /&gt;click to enlarge&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;For more information, see &lt;a href="http://j-integra.intrinsyc.com/products/com/" target="_blank"&gt;http://j-integra.intrinsyc.com/products/com/&lt;/a&gt;.&lt;br /&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://interopvendoralliance.org/aggbug.aspx?PostID=240" width="1" height="1"&gt;</content><author><name>Intrinsyc</name><uri>http://interopvendoralliance.org/members/Intrinsyc.aspx</uri></author><category term="Solutions Guidance" scheme="http://interopvendoralliance.org/blogs/intrinsyc/archive/tags/Solutions+Guidance/default.aspx" /></entry><entry><title>J-Integra for .NET</title><link rel="alternate" type="text/html" href="http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-for-.NET.aspx" /><id>http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-for-.NET.aspx</id><published>2007-01-05T21:12:00Z</published><updated>2007-01-05T21:12:00Z</updated><content type="html">&lt;h2&gt;Overview&lt;/h2&gt;
          &lt;p&gt;J-Integra for .NET is a high performance middleware bridge that enables Java .NET interoperability.
          Its pure Java implementation of Microsoft&amp;#39;s .NET Remoting distributed object wire protocol allows you
          to access .NET components from Java clients, and Java objects from .NET clients.&lt;/p&gt;

          &lt;p&gt;.NET Remoting combines the best aspects of newer distributed technologies (eg, Web Services) with
          the best aspects of older distributed technologies such as DCOM, CORBA and RMI. It is designed to be
          used in both tightly-coupled intranet environments (where COM/CORBA/RMI were previously used), and in
          loosely-coupled Internet environments. &lt;br /&gt;&lt;/p&gt;

          

          &lt;h2&gt;Point-to-Point Interoperability&lt;/h2&gt;

          &lt;p&gt;J-Integra for .NET can be used for point-to-point integration scenarios where the two
          applications that need to communicate with each other don&amp;#39;t need to plug into a common integration
          infrastructure (such as an ESB). Example use case scenarios include:&lt;/p&gt;

          &lt;ul&gt;&lt;li&gt;.NET client interaction with a J2EE Server&lt;/li&gt;&lt;li&gt;.NET client invoking Java desktop applications&lt;/li&gt;&lt;li&gt;.NET Server interaction with a J2EE Server&lt;/li&gt;&lt;li&gt;Java desktop applications invoking .NET Server&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;a href="http://j-integra.intrinsyc.com/products/net/architecture.html"&gt;&lt;img src="http://j-integra.intrinsyc.com/images/point2point_net_small.jpg" alt="J-Integra for .NET Architecture Diagram" /&gt;
              &lt;br /&gt;[Click to enlarge]&lt;/a&gt;&lt;/p&gt;&lt;p&gt;For more information, see &lt;a href="http://j-integra.intrinsyc.com/products/net/" target="_blank"&gt;http://j-integra.intrinsyc.com/products/net/&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;&lt;img src="http://interopvendoralliance.org/aggbug.aspx?PostID=238" width="1" height="1"&gt;</content><author><name>Intrinsyc</name><uri>http://interopvendoralliance.org/members/Intrinsyc.aspx</uri></author><category term="Solutions Guidance" scheme="http://interopvendoralliance.org/blogs/intrinsyc/archive/tags/Solutions+Guidance/default.aspx" /></entry><entry><title>J-Integra Espresso</title><link rel="alternate" type="text/html" href="http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-Espresso.aspx" /><id>http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-Espresso.aspx</id><published>2007-01-05T21:08:00Z</published><updated>2007-01-05T21:08:00Z</updated><content type="html">&lt;h2&gt;Overview&lt;/h2&gt;
          &lt;p&gt;J-Integra Espresso is a high performance middleware bridge that enables Java .NET Corba interoperability.
          It offers software developers a simple and flexible way of allowing applications built with
          &lt;strong&gt;Microsoft&amp;#39;s .NET framework&lt;/strong&gt; to interoperate with &lt;strong&gt;Java-based&lt;/strong&gt;
          and &lt;strong&gt;CORBA-based&lt;/strong&gt; systems without having to change existing
          systems or acquire additional hardware/software infrastructure.&lt;/p&gt;

          &lt;p&gt;J-Integra Espresso is a true CORBA solution for the Microsoft .NET framework. This ORB (Object Request Broker)
          has been written entirely as managed C# code and can therefore be accessed by all .NET languages (C#, ASP.NET, etc). &lt;br /&gt;&lt;/p&gt;

          
          &lt;h2&gt;Point-to-Point Interoperability&lt;/h2&gt;

          &lt;p&gt;J-Integra Espresso can be used for point-to-point integration scenarios where the two
          applications that need to communicate with each other don&amp;#39;t need to plug into a common integration
          infrastructure (such as an ESB). Example use case scenarios include:&lt;/p&gt;

          &lt;ul&gt;&lt;li&gt;.NET client interaction with a J2EE Server&lt;/li&gt;&lt;li&gt;.NET client invoking Java desktop applications&lt;/li&gt;&lt;li&gt;.NET Server interaction with a J2EE Server&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;a href="http://j-integra.intrinsyc.com/products/espresso/architecture.html"&gt;&lt;img src="http://j-integra.intrinsyc.com/images/point2point_espresso_small.jpg" alt="J-Integra Espresso Architecture Diagram" /&gt;
              &lt;br /&gt;click to enlarge&lt;/a&gt;&lt;/p&gt;&lt;p&gt;For more information, see &lt;a href="http://j-integra.intrinsyc.com/products/espresso/" target="_blank"&gt;http://j-integra.intrinsyc.com/products/espresso/.&lt;/a&gt;&lt;/p&gt;&lt;img src="http://interopvendoralliance.org/aggbug.aspx?PostID=237" width="1" height="1"&gt;</content><author><name>Intrinsyc</name><uri>http://interopvendoralliance.org/members/Intrinsyc.aspx</uri></author><category term="Solutions Guidance" scheme="http://interopvendoralliance.org/blogs/intrinsyc/archive/tags/Solutions+Guidance/default.aspx" /></entry><entry><title>Interoperability between Java and Microsoft</title><link rel="alternate" type="text/html" href="http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/Interoperability-between-Java-and-Microsoft.aspx" /><id>http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/Interoperability-between-Java-and-Microsoft.aspx</id><published>2007-01-05T21:00:00Z</published><updated>2007-01-05T21:00:00Z</updated><content type="html">&lt;p&gt;This white paper discusses the pros and cons of various interoperability solutions (i.e., the &amp;quot;buy vs build vs open source&amp;quot; dilemma).&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://j-integra.intrinsyc.com/pdfs/whitepaper_interop.pdf" target="_blank"&gt;http://j-integra.intrinsyc.com/pdfs/whitepaper_interop.pdf&amp;nbsp;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://interopvendoralliance.org/aggbug.aspx?PostID=236" width="1" height="1"&gt;</content><author><name>Intrinsyc</name><uri>http://interopvendoralliance.org/members/Intrinsyc.aspx</uri></author><category term="White Papers" scheme="http://interopvendoralliance.org/blogs/intrinsyc/archive/tags/White+Papers/default.aspx" /></entry><entry><title>Microsoft .NET to J2EE Interoperability Performance Analysis</title><link rel="alternate" type="text/html" href="http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/Microsoft-.NET-to-J2EE-Interoperability-Performance-Analysis.aspx" /><id>http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/Microsoft-.NET-to-J2EE-Interoperability-Performance-Analysis.aspx</id><published>2007-01-05T20:38:00Z</published><updated>2007-01-05T20:38:00Z</updated><content type="html">&lt;p&gt;This white paper analyzes the performance of different interoperability technologies in a typical heterogeneous business application integration context. Specifically, Enterprise java Beans (EJBs) are being accessed from .NET client software in various high load scenarios with simulated &amp;quot;real&amp;quot; business data.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="http://j-integra.intrinsyc.com/pdfs/whitepaper_performance_summary.pdf" target="_blank"&gt;http://j-integra.intrinsyc.com/pdfs/whitepaper_performance_summary.pdf&amp;nbsp;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://interopvendoralliance.org/aggbug.aspx?PostID=235" width="1" height="1"&gt;</content><author><name>Intrinsyc</name><uri>http://interopvendoralliance.org/members/Intrinsyc.aspx</uri></author><category term="White Papers" scheme="http://interopvendoralliance.org/blogs/intrinsyc/archive/tags/White+Papers/default.aspx" /></entry><entry><title>J-Integra Website</title><link rel="alternate" type="text/html" href="http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-Website.aspx" /><id>http://interopvendoralliance.org/blogs/intrinsyc/archive/2007/01/05/J_2D00_Integra-Website.aspx</id><published>2007-01-05T20:24:00Z</published><updated>2007-01-05T20:24:00Z</updated><content type="html">Please visit our website at &lt;a href="http://j-integra.intrinsyc.com" target="_blank" title="J-Integra Interoperability Solutions"&gt;http://j-integra.intrinsyc.com/&lt;/a&gt; for a complete overview of all our interoperability solutions, as well as free trial downloads, news, support, and contact information. &lt;br /&gt;&lt;img src="http://interopvendoralliance.org/aggbug.aspx?PostID=234" width="1" height="1"&gt;</content><author><name>Intrinsyc</name><uri>http://interopvendoralliance.org/members/Intrinsyc.aspx</uri></author><category term="News" scheme="http://interopvendoralliance.org/blogs/intrinsyc/archive/tags/News/default.aspx" /></entry></feed>