1 / 19

EntireX and the J2EE and .NET Architectures

EntireX and the J2EE and .NET Architectures. Harald Nehring Product Marketing Manager , Software AG. Agenda. Why J2EE and .NET? Comparison of J2EE and .NET Application Servers and Middleware Scenarios. Why J2EE and .NET?  Model Choice. 100%.

corby
Download Presentation

EntireX and the J2EE and .NET Architectures

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EntireX and theJ2EE and .NET Architectures Harald Nehring Product Marketing Manager, Software AG

  2. Agenda • Why J2EE and .NET? • Comparison of J2EE and .NET • Application Servers and Middleware • Scenarios

  3. Why J2EE and .NET? Model Choice 100% Proprietary Vendor 4GL, AS/400 RPG, Mainframe COBOL, others 50% Microsoft.NET Microsoft DNA Java platforms 1998 1999 2000 2001 2002 2003 2004 2005 Source: Gartner 2001

  4. Why J2EE and .NET? Platform Choice Source: Gartner 2001

  5. Why J2EE and .NET? Language Choice Source: Gartner 2001

  6. J2EE and .NET Implications • Programming Model • Distribution and components • Presentation capabilities, thin/fat clients • Database access • Transaction coordination • Naming and security • Infrastructure • J2EE: application server software for Windows/UNIX/Mainframe • .NET: Windows OS (2K+) and .NET server software

  7. Similarities between J2EE and .NET

  8. Application Servers and MiddlewareThe Fortress Model CICS .NET J2EE NATURAL • Build fortresses on application servers • Trust system • Local transactions • Tight interaction • Use messengers between fortresses • Trust mediation • Global transactions • Loose coupling

  9. Application Servers and Middleware Inside the Fortress • Applications use application server services • Message desks relay documents to and from the outside world • Unified document formats, trans-mission proto-cols and service interfaces guar-antee smooth op-eration Gate Inbound and outbound message desks Applications and services

  10. Message Desk Messenger Message Desk Message Desk Message Desk Application Servers and MiddlewareAdded Value

  11. Message Desk EntireX Mediator Messenger Message Desk EntireX Mediator Message Desk EntireX Mediator Message Desk EntireX Mediator Application Servers and MiddlewareAdded Value with EntireX • Brokers between pro-gramming models • Brokers between trust models • Brokers between appli-cation platforms EntireX Communicator • Talks to the Web • Receives, validates, logs, enriches and for-wards XML documents • Manages Web services

  12. Bringing it Closer TogetherCurrent Capabilities • Java • Java wrapper component • Java API to Advanced Communications Interface (ACI) • XML wrapper Servlet incl. SOAP access and Tamino Server Extension generation • Application Server adapters • Application Server deployment of Mediator component • Microsoft • SOAP wrapper for .NET-compliant Web services • DCOM wrapper component • DCOM interface to ACI

  13. Bringing it Closer TogetherFuture Development • Java • EJB wrapper component • JMS programming API • JCA adapter API • JCA adapters as gateways • Microsoft • .NET wrapper component • .NET adapters as gateways

  14. J2EE Scenario RPC Service ACI Service Tamino IDL EntireX Java Wrapper XML Wrapper (e.g. SOAP) XML Sequence(Mediator) Java IDE Application Server J2EE Application Servlet Engine JavaMail Web Server Mail Server XML HTTP I*Net

  15. .NET Scenario OS/390 EntireX Windows VisualStudio.NET e.g. Natural IDL WSDL CUSTGETN … … C# e.g.Adabas Web Server ServletCUSTGETN

  16. Add a Web Reference…

  17. Load Web Services Description…

  18. Use the Web Service like a Component!

  19. Thank You!

More Related