Initializing an AD Connector via the API - ibm.software.network.directory-integrator

Message from discussion Initializing an AD Connector via the API

Russell G

View profile

More options 30 June, 22:25

Newsgroups: ibm.software.network.directory-integrator

From: Russell G <russell.goldst...@gmail.com>

Date: Tue, 30 Jun 2009 14:25:31 -0700 (PDT)

Local: Tues 30 June 2009 22:25

Subject: Re: Initializing an AD Connector via the API

  Reply to author
  |
  Forward | Print | View thread
  | Show original
  | Report this message | Find messages by this author
  

On Jun 30, 2:53 pm, Russell G <russell.goldst...@gmail.com> wrote:

> Hello,
> I am working with TDI 7.0 and had previously had an issue with
> initializing an AD Connector via the API that was resolved with Fix
> Pack 1. I am now receiving a different error, as follows:

> java.lang.Exception: sysstore.getJdbcDriver().null

> I am setting the following parameters when initializing:
> ldapUsername
> ldapPassword
> ldapSearchBase
> ldapSearchFilter
> startAt
> iteratorStateKey

> What would be the cause of this error? Also, in solution.properties,
> the following are set relating to the cloudscape DB:

> com.ibm.di.store.database=jdbc:derby://localhost:1527//opt/IBM/TDI/
> V7.0/TDISysStore;create=true
> com.ibm.di.store.jdbc.driver=org.apache.derby.jdbc.ClientDriver
> com.ibm.di.store.jdbc.urlprefix=jdbc:derby://localhost:1527/
> com.ibm.di.store.jdbc.user=APP
> {protect}-com.ibm.di.store.jdbc.password= (password here)

> Any help would be greatly appreciated.

> Thank you,
> Russell Goldstein

You may disregard the message above; the issue was that the
iteratorStateKey was set and trying to find the system properties when
there was none. Thank you anyway.

Reply to author Forward