Preface

This document describes developing Java Naming and Directory Interface (JNDI) API for Oracle WebLogic Server 19c.

Audience

This document is written for application developers who want to design, develop, configure, and manage applications using the Java Platform, Enterprise Edition (Java EE) and want to use the JNDI API to provide a unified interface to multiple naming and directory services in their enterprise. It is assumed that readers know JNDI and the Java programming language.

It is assumed that readers knows the JNDI API and the Java programming language.

Parent topic: Preface

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Accessible Access to Oracle Support

Oracle customers who have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Parent topic: Preface

Related Documentation

For additional information on JNDI, see the following documentation:

BEA-000001 to BEA-2194843 in Error Messages provides a list of all WebLogic Server error messages, including JNDI subsystem messages.
Communications in a Cluster in Administering Clusters for Oracle WebLogic Server provides information on the cluster-wide JNDI tree.
Oracle WebLogic Server Administration Console Online Help contains sections that describe how to add or modify security roles and policies on a JNDI Binding node, Root Content node, or Context node.

Parent topic: Preface

Examples for the Web Application Developer

In addition to this document, Oracle provides examples for software developers within the context of the Avitek Medical Records Application (MedRec) sample application, as well as JNDI code examples.

Parent topic: Related Documentation

Avitek Medical Records Application (MedRec)

MedRec is an end-to-end sample Java EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application provides a framework for patients, doctors, and administrators to manage patient data using a variety of different clients.

MedRec demonstrates WebLogic Server and Java EE features, and highlights Oracle-recommended best practices. MedRec is optionally installed with the WebLogic Server installation. You can start MedRec from the ORACLE_HOME\user_projects\domains\medrec directory, where ORACLE_HOME is the directory you specified as Oracle Home when you installed Oracle WebLogic Server. For more information about sample applications, see Sample Applications and Code Examples in Understanding Oracle WebLogic Server.

Parent topic: Examples for the Web Application Developer

JNDI Examples in the WebLogic Server Distribution

WebLogic Server optionally installs API code examples in the ORACLE_HOME\wlserver\samples\server directory, where ORACLE_HOME represents the Oracle Home directory for your WebLogic Server installation. For more information about the WebLogic Server code examples, see Sample Applications and Code Examples in Understanding Oracle WebLogic Server.

Parent topic: Examples for the Web Application Developer

New and Changed WebLogic Server Features

For a comprehensive listing of the new WebLogic Server features introduced in this release, see What's New in Oracle WebLogic Server 12.2.1.3.0.

Parent topic: Related Documentation

Diversity and Inclusion

Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.

Parent topic: Preface

Conventions

The following text conventions are used in this document:

Convention	Meaning
boldface	Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic	Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
`monospace`	Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Parent topic: Preface