We have a MySQL database backend that is accessed through our website
using Apache Tomcat that was set up before I came on board here. I am
just familiar enough with this setup to be dangerous.
Our problem is that whenever our users attempt to logon to the database
this morning they get this error message:
org.keel.services.authentication.mad.LoginHelper: singraham:Unable to
access LDAP server at occadb Reason: occadb:389
I am sure that my actions last Friday have contributed to this problem
but I need some help on tracking down where I can fix this problem. On
Friday I demoted an old Windows 2000 Advanced Server from serving as a
Domain Controller for our domain. I have a Windows 2003 server that was
also serving as DC along with the now demoted server. I have been
informed by the web application developer that this has caused this
failure as he believes there was a line of code that was pointing to
this old DC to acquire the logon information. However, he cannot recall
where this file is or what it was called. I have been informed that
there is a line in one of the configuration files for our website that
needs to direct to the new DC for our domain and that once that line is
changed to redirect to the new DC we will be able to logon.
I have been searching for any configuration files in our web application
that would have the specific line directing to the "now incorrect" DC.
Can anyone provide me with information on where this configuration file
may reside? What its name, location, path could be? Is there a
standard location in a Tomcat environment where this type of
configuration file may be?
The web application is running on Apache Tomcat 5.5.15 on a Redhat AS 3
server.
Thanks in advance for any assistance.
Steve
