J2EE: Distributed environment Containers, Persistance & Naming

J2EE Technologies
Web centric Programming
- Integration of servlets and JSP into enterprise applications.
Within an organization, or even when creating B2B links, clients may connect directly to business components in the shape of EJB over RMI or CORBA.

Maintaining the integrity of the data is provided by "Transactions and Persistence"

A Mode for Enterprise Computing
An n-tier, component-based, Web-friendly environment is needed.
What about detail - what specific functionality is needed to support such applications.

OMG,1989 formed specifications for Distributed Object Computing landscape, such as

  1. Common Object Request Broker Architecture(CORBA)
  2. the Internet Inter-Orb Protocol(IIOP) 
  3. and UML(unified modeling language)

A distributed component environment must provide "Containers" to manage the lifetime of components and assist in their deployment.

With RMI, a distributed leading mechanism is used.
With CORBA, there are lifecycle management services.
DCOM relies on objects controlling their own lifetimes.


Persistance

Storage of data for retrieval.
Example : ODMS and RDBMS

Naming

Distributed applications will be formed from components that reside on different machines.
Common Directory Object Services (COS) Naming Service
The COS naming service is widely used in Java-based distributed environments as a way of storing information about the location of remote objects.

X.500 - Storing Hierarchical information and an access protocol called the Directory Access Protocol(DAP).

LDAP - Lightweight version of X.500 that runs over TCP/IP

DNS - IP Internet Protocol that allows translation between hostnames and Internet addresses. DNS is used by all Internet clients such as Web Browsers.


Analytics