33 lines
1.4 KiB
HTML
33 lines
1.4 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
<html>
|
||
|
<head>
|
||
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
||
|
<title>Use JNDI</title>
|
||
|
</head>
|
||
|
|
||
|
<BODY>
|
||
|
<!-- Java sync-link -->
|
||
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
||
|
<h4><a name="jndiuse"></a>Use JNDI</h4>
|
||
|
|
||
|
<p>You can use the JNDI API to support the Java components you deploy on WebSphere Application Server- Express. Specifically, you use the JNDI API to locate and refer to resources such as data sources and JavaMail sessions within a distributed computing environment.</p>
|
||
|
|
||
|
<p>The process of using JNDI to access enterprise-level Java components involves these steps:</p>
|
||
|
<p>
|
||
|
<ol>
|
||
|
<li><p><a href="jndicntx.htm">Obtain the initial JNDI context for the component</a>
|
||
|
<br>This topic describes how to obtain an initial JNDI context that contains the resource (a Java object).</p></li>
|
||
|
<li><p><a href="jndilkup.htm">Use JNDI to look up Java components</a>
|
||
|
<br>This topic explains how to look up resources such as data sources and JavaMail sessions.</p></li>
|
||
|
</ol>
|
||
|
</p>
|
||
|
|
||
|
<p>After you have completed these steps, you can use the enterprise resource (such as a data source) in your code exactly as you would if Java object had been available locally.</p>
|
||
|
|
||
|
|
||
|
</body>
|
||
|
</html>
|