JNDI Java Naming Directory Interface JNDI is an API specified in Java that provides naming and directory functionality to applications written in Java.

Slides:



Advertisements
Similar presentations
J0 1 Marco Ronchetti - Basi di Dati Web e Distribuite – Laurea Specialistica in Informatica – Università di Trento.
Advertisements

1 Arne J. Berre 1 SINTEF Telecom and Informatics.
Lecture plan Information retrieval (from week 11)
Approaches to EJB Replication. Overview J2EE architecture –EJB, components, services Replication –Clustering, container, application Conclusions –Advantages.
An architecture for webb applications, J2EE
Introduction to Java 2 Enterprise Edition About myself –Neutrinos, Cancer Research, IT Applications Today’s topic: J2EE –Context –Advantages –Components.
Introduction to Enterprise JavaBeans. Integrating Software Development Server-side Component Model Distributed Object Architecture –CORBA –DCOM –Java.
1 Build a Web Application on J2EE. 2 J2EE Scenario Client – Web Server – EIS Resources Client – Web Server – EIS Resources Client – Application Server.
Basics of JNDI Alessio Bechini June Naming and Directory Services: Rationale A fundamental element in every application is the capability to find.
J2EE vs..NET Tom Tong. Enterprise Application 1 distributed 2 multiple-platform 3 critical 4 performance 5 security 6 multiple-data sources.
JMS Java Message Service Instructor Professor: Charles Tappert By Student: Amr Fouda.
J2EE vs..NET Nigam Patel. Topics Background –Web Services, J2EE and.NET Similarities Differences Conclusion –Pros and Con (J2EE and.NET)
Enterprise Programming By J Pearce. Enterprise Software Sales HR Inventory Customer Support Shipping.
Nikolaos Korfiatis The Java 2 Enterprise Edition Platform Dept. of Management & Technology-Athens University of Economics and Business Java 2 Platform.
E-business Architecture.NET vs J2EE Judith Molka-Danielsen Feb.27, 2004.
CS6320 – J2EE L. Grewe MOTIVATION: E-commerce and Enterprise Computing Models Four models for e-commerce and enterprise computing: Four models for e-commerce.
EJB Overview Celsina Bignoli Distributed Business Applications Server DB Client DB Server DB.
Distributed Multitiered Applications The J2EE platform uses a multitiered distributed application model. Application logic is divided into components 1.
J2EE /.NET Liz Farricker Whitney Mayoras Patrick Bailey.
卓越計劃進度報告 JNDI Java Naming and Directory Interface 網際網路實驗室 報告人 潘燕弘.
Enterprise Java Beans CS-422. Application Servers In the late 1980s and though the mid 1990s a number of corporations (Broadvision, Netscape…) marketed.
HTTP client wide area network (Internet) HTTP proxy HTTP server HTTP gateway firewall HTTP tunnel Copyright Springer Verlag Berlin Heidelberg 2004.
Ing. Ignacio Roqueta ARTech GeneXus and J2EE.
Corso di Formazione Sodalia “Enterprise Java Beans” JNDI Java Naming and Directory Interface.
Talarian Proprietary Talarian’s New JMS Offering and Sun Partnership.
Enterprise Computing COSC 617 Jeff Schmitt September 7,2006.
Enterprise JavaBeans EJB Container Services. EJB container Enterprise JavaBeans are deployed in an EJB container within the application server EJB container.
CS 493/693: Distributed Systems Programming V. “Juggy” Jagannathan CSEE, West Virginia University March 21, 2005.
© D. Wong  Indexes  JDBC  JDBC in J2EE (Java 2 Enterprise Edition)
Entity Java Beans Jorg Janke Open Source ERP & CRM.
Enterprise Java Beans Part I Kyungmin Cho 2001/04/10.
Replication & EJB Graham Morgan. EJB goals Ease development of applications –Hide low-level details such as transactions. Provide framework defining the.
Enterprise Java Bean Matt. 2 J2EE 3 J2EE Overview.
Enterprise JavaBeans. What is EJB? l An EJB is a specialized, non-visual JavaBean that runs on a server. l EJB technology supports application development.
Introduction to J2EE Architecture Portions by Kunal Mehta.
TDDD05 EJB Lab (Part of slides reused from Mikhail’s) Lu Li
Java-Based Middleware IT 490 Stan Senesy IT Program NJIT.
第十四章 J2EE 入门 Introduction What is J2EE ?
Enterprise Java v120131Intro to JavaEE1 Java EE 5 TM Introduction.
Enterprise Java Beans Java for the Enterprise Server-based platform for Enterprise Applications Designed for “medium-to-large scale business, enterprise-wide.
Topic : JNDI Kaster Nurmukan. JNDI2(c)CDAC(Formerly NCST) What is JNDI? Naming and Directory Services Naming Concepts Issues JNDI Architecture Programming.
Middleware Technology (J2EE/EJB) RMI-IIOP/JNDI. 2 Distributed Objects EJB components are based on distributed objects. A distributed object can be called.
Java Naming and Directory Interfaces. A naming service is an entity that performs the following tasks:  It associates names with objects. Similar to.
J2EE Overview ver 1.0Page 1 © Wipro Technologies Talent Transformation J2EE Overview.
Ch 2 – Application Assembly and Deployment COSC 617 Jeff Schmitt September 14, 2006.
JBoss at Work Databases and JBoss Chapter 4 Jeff Schmitt October 26, 2006.
Databases JDBC (Java Database Connectivity) –Thin clients – servlet,JavaServer Pages (JSP) –Thick clients – RMI to remote databases –most recommended way.
1 Java EE Programming Enterprise JavaBeans. 2 Topics J2EE Overview Enterprise JavaBeans Overview Enterprise Entity Beans Case Study How to build them.
Java Naming and Directory Interface Matt. 2 What is JNDI.
UNIT III - JDBC JDBC Overview – JDBC implementation – Connection class – Statements - Catching Database Results, handling database Queries. Networking–
Assignment of JAVA id : BSSE-F10-M-10-JAVA1 Overview of J2EE/Session 2/Slide 1 of 38.
Enterprise JavaBeans 3.0. What is EJB 3.0 -Reusable server-side component framework-technology -Designed to support building demanding enterprise – level.
Basics of JDBC Session 14.
Introduction to EJB. What is an EJB ?  An enterprise java bean is a server-side component that encapsulates the business logic of an application. By.
1 Distributed System using J2EE. 2 What is J2EE?  J2EE (Java2 Enterprise Edition) offers a suite of software specification to design, develop, assemble.
Introduction to EJB. What is an EJB ?  An enterprise java bean is a server-side component that encapsulates the business logic of an application. By.
Alan L. Batongbacal CS 4244 / 01 Nov 2000
Java Naming and Directory Interface. Contents Naming and directory services JNDI RMI Conclusion.
EJB. Introduction Enterprise Java Beans is a specification for creating server- side scalable, transactional, multi-user secure enterprise-level applications.
R EMAINING TOPICS IN JDBC Sagun Dhakhwa. O VERVIEW Introduction to JDBC API Types of JDBC Drivers Introduction to ODBC.
J2EE Lecture 10: EJB 3.0 Overview
J2EE Platform Overview (Application Architecture)
Introduction to J2EE Architecture
Java Messaging Service (JMS)
Web-Services-based Systems Architecture, Design and Implementation
Introduction to Enterprise JavaBean
Understanding and Designing with EJB
Computer Based Adaptive Testing
Introduction of Week 11 Return assignment 9-1 Collect assignment 10-1
Knowledge Byte In this section, you will learn about:
Presentation transcript:

JNDI

Java Naming Directory Interface

JNDI is an API specified in Java that provides naming and directory functionality to applications written in Java. JNDI was developed by Sun as a regular or standard extension to Java programming Language JNDI is designed especially for Java by using Java’s object model.

JNDI is used by Java applications can store and retrieve named Java objects of any type. JNDI provides methods for performing standard directory operations. Examples: Associating attributes with objects and searching for objects using their attributes.

JNDI is defined independent of any specific naming or directory service implementation. JNDI enables Java applications to access different, naming and directory services using a common API. Different naming and directory service proider can be plugged in seamlessly behind the common API.

The common API allows Java applications to take advantage of information in a variety of existing naming and directory services, and allows Java applications to coexist with legacy applications and systems. Examples: such as LDAP, NDS, DNS, and NIS(YP).

JNDI Architecture

JNDI has three layers and exposes two interfaces: an API for Java clients and servers to use and a Service Providers Interface (SPI) for vendors who provide JNDI services. The Naming Manager layer maps each JNDI call to a service provider.

The standardization of these two interfaces makes the service provider almost transparent to the Java application code. Clients can use the JNDI API to bind and lookup over a wide range of naming services.

How Does JNDI Services Work Each JNDI service vendor is free to implement the set of naming and directory services. They choose to support in their own way.

All of the names in a naming system comprise the system’s namespace. The naming systems use their own naming conventions. A naming convention defines atomic names, which can’t be divided, and compound names, conglomerates of atomic names that organize similar names in the same namespace.

Using JNDI as a tool, the Java application developer can build new powerful and portable applications that not only take advantage of Java’s object model but are also well integrated with the environment in which they are deployed. Example of where JNDI is used: –JMS -Java Messaging Service –JDBC -Java Database Connectivity package –EJB - Enterprise Java Beans