powered by Jive Software

AD accounts from a Linux server

I’‘m having issues getting the server setup to use the AD accounts off the W2K server we have. One question I have is, how do i run the admin tool if it always wants to run a setup, and it wants me to pick a datasource that is either one of the DB types, or embeded. If i’‘m wanting to use the AD, how does this relate? I’‘m pretty confused by this as I have searched a fair bit through the forum, and my settings don’'t seem different than other peoples who are working yet mines screwed. Thanks for any feedback.

More importantly when I try to startup, I see this error, which seems to be that it’'s not connecting to a data source.

2005.10.28 12:45:45 [org.jivesoftware.database.ConnectionPool.(XMPPServer.java:133)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.messenger.starter.ServerStarter.start(ServerStarter.java:82)

at org.jivesoftware.messenger.starter.ServerStarter.main(ServerStarter.java:46)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.install4j.runtime.Launcher.main(Unknown Source)

2005.10.28 12:45:45 org.jivesoftware.database.DefaultConnectionProvider.getConnection(DefaultConnect ionProvider.java:68) Warning: DbConnectionDefaultPool.getConnection() was called before the i

nternal pool has been initialized.

2005.10.28 12:45:45 org.jivesoftware.database.DbConnectionManager.getConnection(DbConnectionManager. java:107) WARNING: ConnectionManager.getConnection() failed to obtain a connection.

2005.10.28 12:45:45 org.jivesoftware.messenger.XMPPServer.verifyDataSource(XMPPServer.java:498) Database could not be accessed

java.lang.NullPointerException

at org.jivesoftware.messenger.XMPPServer.verifyDataSource(XMPPServer.java:488)

at org.jivesoftware.messenger.XMPPServer.start(XMPPServer.java:270)

at org.jivesoftware.messenger.XMPPServer.(XMPPServer.java:133)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.messenger.starter.ServerStarter.start(ServerStarter.java:82)

at org.jivesoftware.messenger.starter.ServerStarter.main(ServerStarter.java:46)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.install4j.runtime.Launcher.main(Unknown Source)

2005.10.28 12:45:45 org.jivesoftware.messenger.XMPPServer.start(XMPPServer.java:299)

java.lang.IllegalArgumentException: java.lang.NullPointerException

at org.jivesoftware.messenger.XMPPServer.verifyDataSource(XMPPServer.java:499)

at org.jivesoftware.messenger.XMPPServer.start(XMPPServer.java:270)

at org.jivesoftware.messenger.XMPPServer.

Hey Derrick,

Even if you’‘re using AD Messenger still needs to use a database to store things like properties and user rosters. I don’'t know what database people typically use when working with AD but if you already have a database (such as SQL Server) setup somewhere that you can use I would suggest using that, if not the embedded database works well, too.

Hope that helps,

Ryan

Hey Derrick,

Even if you’'re using AD Messenger still needs to use

a database to store things like properties and user

rosters. I don’'t know what database people typically

use when working with AD but if you already have a

database (such as SQL Server) setup somewhere that

you can use I would suggest using that, if not the

embedded database works well, too.

OK, makes sense. Does that then mean that the Jabber authentication is then being handled via that DB, or does it use the AD?

OK, makes sense. Does that then mean that the Jabber

authentication is then being handled via that DB, or

does it use the AD?

It will be handled by the AD, that’‘s what you’'re specifying when you configure the jive-messenger.xml file to use LdapUserProvider and LdapAuthProvider classes.

Cheers,

Ryan