Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 55 views

    Vendor Architectures: The Client Tier - Either Browser Possibly With Java Applets or A Stand-Alone Java

    Uploaded by

    Neema Dev Bobeena
    The document discusses and compares the vendor architectures of .NET and J2EE. It describes how both include platform architectures with common language runtimes and virtual machines. It also explains their distributed architectures with multiple tiers like client, web, and data tiers supported by various APIs. Finally, it outlines how vendor architectures serve to position products, provide examples for user architectures, and help with marketing.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd

    Vendor Architectures: The Client Tier - Either Browser Possibly With Java Applets or A Stand-Alone Java

    Uploaded by

    Neema Dev Bobeena
    55 views4 pages
    The document discusses and compares the vendor architectures of .NET and J2EE. It describes how both include platform architectures with common language runtimes and virtual machines. It also explains their distributed architectures with multiple tiers like client, web, and data tiers supported by various APIs. Finally, it outlines how vendor architectures serve to position products, provide examples for user architectures, and help with marketing.

    Original Description:

    Middleware vendor architectures

    Original Title

    Vendor Architectures

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses and compares the vendor architectures of .NET and J2EE. It describes how both include platform architectures with common language runtimes and virtual machines. It also explains their distributed architectures with multiple tiers like client, web, and data tiers supported by various APIs. Finally, it outlines how vendor architectures serve to position products, provide examples for user architectures, and help with marketing.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    55 views4 pages

    Vendor Architectures: The Client Tier - Either Browser Possibly With Java Applets or A Stand-Alone Java

    Uploaded by

    Neema Dev Bobeena
    The document discusses and compares the vendor architectures of .NET and J2EE. It describes how both include platform architectures with common language runtimes and virtual machines. It also explains their distributed architectures with multiple tiers like client, web, and data tiers supported by various APIs. Finally, it outlines how vendor architectures serve to position products, provide examples for user architectures, and help with marketing.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    You are on page 1of 4

    Vendor Architectures The two vendor architectures that are grabbing the attention now are NET and

    Java2 Enterprise Edition (J2EE) from Microsoft and Sun respectively. Vendor architectures serve various functions, many of them to do with marketing and image building Vendor Platform Architectures Both .NET and J2EE include a platform architecture. Going up from the bottom, above the operating system in the Common Language runtime. The common language runtime defines how different components can be assembled at runtime and talk to each other. The J2EE platform has something very similar- the Java Virtual Machine (JVM). Many JVMs implement a Just In Time (JIT) compilation that turns the java byte code into machine code. In .NET, compilers create intermediate language, IL, and the .Net framework converts the IL into machine code runtime. Base class libraries are about accessing operating system facilities (eg. FileIO, time date) and other basic facilities (eg. Mathematical functions). ADO.Net is about database access. The XML class library provides routines for creating and reading XML messages and files. ASP.Net is about web access and windows forms is about using work station windows. .Net supports many languages, J2EE supports only Java a big advantage of .Net But J2EE runs on many more platforms than .Net which is a big advantage for J2EE

    Vendor Distributed Architectures J2EE consists of several tiers

    The client tier - either browser possibly with Java Applets or a stand-alone Java Program

    The Web Tier : A Web server running Java Server Pages (JSP) and Java Servlets. The Enterprise JavaBeans tier : an EJB container

    The Enterprise Information Systems tier : - a database or a connector to an older application for instance on a mainframe. Each tier supports a set of platform APIs. For instance, Java Message Service (JMS), which supports message queueing and Java Database Connectivity (JDBC) which supports remote database access are supported everywhere except in Java Applets. The common building blocks everywhere are Java Components.
    Java GUI Applications JDBC HTML DHTML XML JMS RMI -IIOP JNDI

    Presentati on

    JAVA SERVLET Web Container JDB C

    JSP

    Tier JMS RMI -IIOP JNDI JAVA MAIL

    Business logic EJB CONN Container JDB ECTOR C JMS RMI -IIOP JNDI

    JSP JAVA MAIL

    Data Tier

    Mainfr ame

    Data

    A distributed architecture using J2EE

    The .Net distributed architecture is very similar except that .NET components, not Java Components, are everywhere. Instead of JSP, there is ASP. Instead of EJB, .NET components can have COM+ like features by using .NET enterprise services

    VB

    C#

    C++

    J#

    Common Language Specification


    Asp.Net Web forms, Web Services

    Windows forms

    ADO.NET and XML Base Class Library Common Language Runtime Operating system

    .Net framework Using Vendor Architectures Vendor architectures serve a number of function and the three are positioning, strawman for user architectures and marketing. Positioning :

    The architecture diagram helps because the implication of putting some products into the same layer or inside another box is that they have some functions in common. For instance, the .NET diagram clearly shows that every user of .NET must have an operating system and a common language runtime. Also the implication of putting ASP.NET and windows forms as separate boxes but in one layer is that they are alternatives. The J2EE diagram is specific in another way; it shows how product map to tiers. A well presented architecture lets you see at a glance what elements you need to select to make a working system. Positioning helps both the vendor and the user identify whats missing in the current product portfolio, and architectures usually lead to vendors ensuring that either they or someone else is ready to fill in the gaps. Straw man for user target architecture: Architectures are used to tell users how functionality should be split, for instance, into layers such as presentation, business logic, and data. The purpose of this kind of layering is to tell developers how they should partition application functionality between the layers. Both .Net and J2EE architectures offer message queuing and transaction services. In J2EE, for instance, the EJB is a container and JMS is just a service. The implication is that EJB is essential and JMS might be useful if we happen to need it. Marketing: Architecture can provide a vision of the future. The architecture is saying : This is how we believe applications should be built and our tools are the best for the job. Using architecture, the vendor can show that it has a rich set of tools, it has thought through the development issues, it has a strategy it is working toward and above all, it is forward looking.

    You might also like