Question

I m 试图利用像样的编码与矿石数据库连接:

public static Connection getConnection() throws ClassNotFoundException {
    Class.forName("oracle.jdbc.driver.OracleDriver");
    Properties env = new Properties();
    //env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
    env.put(Context.PROVIDER_URL, "ldap://192.168.1.1:389/o=myo,dc=mydc,dc=us");
    Connection connection = null;

    try {
        InitialContext context = new InitialContext(env);
        DataSource dataSource = (DataSource) context.lookup("jdbc/DataSource");
        connection = dataSource.getConnection();
    } catch (NamingException e) {
        e.printStackTrace();
    } catch (SQLException e) {
        e.printStackTrace();
    }

    return connection;
}

但它始终不例外:

javax.naming.InvalidNameException: jdbc: [LDAP: error code 34 - invalid DN]; remaining name  jdbc/DataSource

哪里,以及怎样才能具体指出:jdbc/DataSource?

I m confused as I was given a working project using codes similar as above but nowhere tells what DataSource is. I m wondering if jdbc/DataSource should be a DN in LDAP, but I find nothing seem relavent in my given ldap data. Sorry if that question is stupid or not make sense, i m new to that all stuff.

感谢!

Answer 1

经过几个星期的研究,最后找到了以下解决办法。如果其他人面临同样的问题,希望会有所帮助。

我将网上应用程序从Web Sphere转至Tomcat,用户从网上星座的名录连接起来。 Tomcat没有这种目录,但它可以具体说明,在服务器上,xml/context.xml/web.xml,但我从未能够做到! 因此,我的解决办法是使用档案目录:

public static Connection getConnection() throws ClassNotFoundException {
    Class.forName("oracle.jdbc.driver.OracleDriver");
    Properties env = new Properties();

    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.fscontext.RefFSContextFactory");
    env.put(Context.PROVIDER_URL, "file:/C://JNDI");

    Connection connection = null;

    try {
        InitialContext context = new InitialContext(env);
        DataSource dataSource = (DataSource) context.lookup("jdbc/DataSource");
        connection = dataSource.getConnection();
    } catch (NamingException e) {
        e.printStackTrace();
    } catch (SQLException e) {
        e.printStackTrace();
    }

    return connection;
}

仅仅修改了两条电线,并做了罚款。但是,为创建基于档案的目录做了一些准备工作,这里是建立一个文件C:JNDI具有约束力的方案。

public static void main(String args[]) throws SQLException, NamingException {

    Context ctx = null;
    try {
        Properties prop = new Properties();
        prop.setProperty(Context.INITIAL_CONTEXT_FACTORY,
                "com.sun.jndi.fscontext.RefFSContextFactory");
        prop.setProperty(Context.PROVIDER_URL, "file:/C:/JNDI");
        ctx = new InitialContext(prop);

        OracleDataSource ds = new OracleDataSource();
        ds.setDriverType("thin");
        ds.setServerName("123.123.123.123");
        ds.setPortNumber(1521);
        ds.setDatabaseName("xe");
        ds.setUser("username");
        ds.setPassword("password");
        ctx.bind("jdbc/DataSource", ds);

    } catch (NamingException ne) {
        System.err.println(ne.getMessage());

        ne.printStackTrace();
    }

}

使其在我的生产网目和测试目录中发挥作用,即只使用不同的INITIAL_CONTEXT_FACTORY环境取决于财产档案。

感谢奥拉夫的极大帮助!

Answer 2

Got this from :

Error: Error in bind from LDAP source: [LDAP: error code 34 - invalid DN] javax.naming.InvalidNameException

Cause: This is caused by a bad prefix specified in the Settings tab, on most LDAP/AD systems. This could mean you did not specify a prefix at all, which means the LDAP/AD server did not receive a full DN from CPS or that you did not specify a correct prefix, such as CN instead of UID, which results in the LDAP/AD server not receiving a correct DN from CPS. Can also be caused by a missing comma at the beginning of the suffix or an extra comma at the end of the suffix. This error could also mean the authentication type is incorrect.

Answer 3

如果您的法典在网上发挥作用,我会猜测,大街区可能位于大街:jndi-lookup。您能否研究“jee:jndi-lookup/jdbc/DataSource”或“java:comp/env/jdbc/DataSource”?

您应尝试一名全球倡议名录浏览器,以浏览你的开放式区域行动方案目录,以了解贵国数据来源的定义。

友情链接