After talking to our TSM he suggested that we look in the file below as well.
bb-odbc.ini
Regards
Hugh Dunlop
Middlesbrough College
________________________________
From: Blackboard/Courseinfo userslist on behalf of Beckett Paul Mr (ITCS)
Sent: Tue 5/15/2007 12:49
To: [log in to unmask]
Subject: Trouble cloning BB 6.3 production onto a test machine
Hi,
We are preparing for our 6.3 -> 7.1 upgrade; we are therefore cloning our production machine onto a test machine to test the upgrade process. The problem is the test machine still seems to be connecting to our production database. We would really appreciate any help / advice on this, as we need to resolve this urgently. I have outlined below what we have done:
We cloned our production webapp server onto a test server.
We copied the production DB into a new test instance.
We modified bb-config.properties, changing all references to the web-app host and the DB instance to the new ones.
We then ran PushConfigUpdates.sh .
When we started BB services on our test machine it formed one admin connection to our test DB instance, but lots of connections to the production DB instance.
Has anyone else encountered this? Any idea why it's happening? Where there any other config files or references in the DB that we should have changed?
Any help / advice will be very gratefully received.
Thanks,
Paul
**************************************************
DISCLAIMER:
Privileged/Confidential information may be contained in this message and may be subject to legal privilege.
Access to this e-mail by anyone other than the intended recipient is unauthorised. If you have received this email in error or are not the intended recipient (or responsible for delivery of the message to such a person), you may not use, copy, distribute or deliver to anyone this message (or any part of its contents ) or take any action in reliance on it. In such cases, you must destroy this message and notify the sender immediately.
Middlesbrough College employees are forbidden to make any sexual, racial or otherwise defamatory statements, infringe or authorise infringement of copyright or any other legal right within any communication. Any such communication is contrary to the College's Acceptable Use Policy and outside the scope of the employment of the individual concerned. The College will not accept any liability in respect of such a communication and the employee responsible will be personally liable for any damages or action arising.
No employee or agent is authorised to conclude any binding agreement on behalf of Middlesbrough College with another party via email without the express written authorisation from a senior member of staff from Middlesbrough College.
The views, opinions, conclusions and other information expressed in this email are not given or endorsed by Middlesbrough College unless otherwise indicated by an authorised representative independent of this message.
All reasonable precautions have been taken to ensure no viruses are present in this e-mail. The College does not accept responsibility for any loss or damage arising from the use of this e-mail or attachments. We recommend that you subject any such emails or attachments to your virus checking procedures prior to use.
**************************************************
|