|
Home > Archive > WebSphere Portal Server > January 2004 > WPS 4.2.1 Collaboration Center - Directory Connector Application
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
WPS 4.2.1 Collaboration Center - Directory Connector Application
|
|
| kdefty 2004-01-19, 2:55 pm |
| I apparently have the Collaboration Center successfully
installed and all the verification steps checked out.
Now I've run into a roadblock configuring components!
After launching the Directory Connector Application ...
http://{hostname}/PFDirectoryConnector/ConfigWelcome.action
... then try to import the sample configuration file
(PFSampleConnection.xml) I get the status area error
message ...
"The file you imported does not have the required XML
structure. Parser error: Datatype error: In element
'baseDN' : Value '' with length '0' is less than
minimum length facet of '1'.."
... this is to be expected because no baseDN or
hostURI is/has been specified. If I make a copy
of the file and specify valid hostURI & baseDN
and then attempt to import it, I get the status
area message of ...
"The file could not be imported. Make sure it
is not open in another application, then try
again"
... I have read all the docs, including section on
trouble shooting and everything appears to be
as it should be. I note that there is a known
problem where this may happen once the first
time you attempt to import a new connection
but I have tried this over a dozen times
now ... same result.
Any idea where to look for more detailed info,
as nothing seems to get logged anywhere I
can see.
Thanks & Cheers, ... Keith.
| |
| kdefty 2004-01-19, 2:55 pm |
| Sorted the problem ... bogus error message.
Found "java.sql.exception: ORA-01483: invalid length for
DATE or NUMBER bind variable" in server logs. Don't know
exactly why but this has something to do with what you have
defined in your PFConnection.xml for {exposedAttributes},
Suspect limit on the total number of {exposedAttribute}'s
but shouldn't be as being stored in blob ( by the way we
are using oracle & iplanet ). Or something specific to a
particular to one of the {exposedAttribute} elements.
Anyway, the sample PFConnection.xml wouldn't load, even
with all the correct connection info .. until I hacked
out some of the aforementioned {exposedAttribute}'s.
Now I'm stuck trying to validate successfully ( getting
null pointer exception in logs ) on the field mapping
for what I've now finally managed to import.
Cheers, ... Keith.
|
|
|
|
|