Интеграция с другими приложениями > Адаптеры Info*Engine > JNDI Adapter Guide (Руководство по адаптеру JNDI) (на английском языке) > Installing and Configuring the JNDI Adapter > Testing the JNDI Installation
Testing the JNDI Installation
Use the following steps to test the JNDI installation:
1. Create a JNDI adapter LDAP entry to access a specific directory.
2. If your adapter is running out of process, start the adapter to listen for requests.
3. Resolve any error messages that appear when attempting to start the adapter.
The following table details the most common error messages that might appear when the adapter does not appear to start up correctly:
Error Message
Explanation and Action
Windows:
The name specified is not
recognized as an internal or
external command, operable
program or batch file.
UNIX:
java: not found
The Java executable cannot be found.
Option 1—Add the full path to your Java executable to your PATH environment variable.
Option 2—Add the full path to your Java executable to the startup script.
Unable to initialize threads:
cannot find class
java/lang/Thread
The Java executable is not able to find classes.zip or rt.jar file in its classpath.
Ensure the classpath is set and that the path and file name specified are correct.
Cannot find class
com.infoengine.Jndi
The Java executable cannot find the ieWeb.jar file in its classpath.
Ensure the classpath is set and that the path and file name specified are correct.
java.naming.factory.initial
was not set
The Java executable is not able to find a value for the java.naming.factory.initial property.
Ensure this property is set either in the startup script as a command-line option or in the adapter LDAP entry.
java.naming.provider.url
was not set
The Java executable is not able to find a value for the java.naming.provider.url property.
Ensure that this property is set either in the startup script as a command-line option or in the adapter LDAP entry.
4. Execute a JSP page that contains a JNDI webject.
5. Resolve any error messages that appear when attempting to any webjects.
Sometimes the adapter appears to have started correctly, but certain webjects appear to fail.
The following table details the most common error messages that are displayed when the adapter appears to be running properly but webjects appear to fail:
Error Message
Explanation and Action
java.lang.NoClassDefFoundError:
com/sun/JNDI/toolkit/
ComponentDirContext
Although the adapter appears to start properly, requests sent to the adapter fail and this message is displayed in the adapter startup window.
This error indicates the Java executable cannot find the providerutil.jar file in its classpath.
Ensure the classpath is set and the path and file name specified are correct.
DirContext error!
[Root exception isjava.lang.
ClassNotFoundException:
com.sun.JNDI.ldap.
LdapCtxFactory]javax.naming.
NoInitialContextException:
Although the adapter appears to start properly, requests sent to the adapter fail. No error messages are displayed in the adapter startup window, but this error appears as the STATUS of an action webject request.
This error indicates that it cannot instantiate the com.sun.JNDI.ldap.LdapCtxFactory class, meaning that the Java executable cannot find the ldap.jar file in its classpath.
Ensure the classpath is set and the path and file name specified are correct.
java.lang.NoClassDefFoundError:
javax/naming/directory/
InitialDirContext
Although the adapter appears to start properly, requests sent to the adapter fail and this message is displayed in the adapter startup window.
This error indicates the Java executable cannot find the JNDI JAR file in its classpath.
Ensure the classpath is set and the path and filename specified are correct.
Было ли это полезно?