TeamSite upgrade to 7.4.1 & database server change

Hi ,

I am upgrading our current (7.3.1) TeamSite installation to latest one (7.4.1 Update 1). Our DBAs wanted me to use a new database Server location for the upgraded teamSite installation. There is no change in database type , both are oracle.

Will I be able to change database location while upgrading ? Do the upgrade versions of installation GUI allowes me to change the Database Server location? Or is the database change needs to be handled as a pre-installation task where I need to create the database name , username & password? And these details needs to be provided either at installation phase or as a post-installation step (manually editing database.properties for commonservices & running build sql.create for SitePublisher) ? I am aware of the need to encrypt the passord . As we have only SitePublisher & we don't use LS display services , I am only concerned about the database used by sitepublisher & commonservices.

Has anybody gone through this recently? Anything to watch out in above approach ?

Regards,

Mike

TS 7.3.1 >> TS7.4.1

RHEL 5.3

Find more posts tagged with

Comments

Rick Poulin

If your DBAs are going to require new schemas, then the same policy should apply at the OS level -- you should provision new servers and do a fresh install there, and then move your content store over. In this scenario, the installer would ask for new DB locations as you'd expect, and you would properly isolate version changes to the schema which appears to be the intention of your DBAs.

It sounds like you're upgrading in place though, which does not account for changing databases. In this scenario, you can only adjust the DB references either before or after the upgrade (which actually defeats the purpose of having new schemas) and the process will be manual and error-prone, so I wouldn't recommend it.

MikeMiracle

Hi rpoulin,

Thanks a lot for responding quickly. We don't use database at all in our implementation. We don't have any database deployments & we don't use LiveSite Runtime. Our DBAs are not responsible for TeamSite. They just want to move the database to another machines as it is not their core responsibility. The databse is used internally by TeamSite for CommonServices & SitePublisher functionality.

I was under the impression that I can change the db server after upgrading by following ways.

For Common services , Edit CommonServices/config/private/database.properties
For SitePublisher , Navigate to ts-home/local/config/lib/content_center/
livesite_customer_src.
and run build sql.create.development

What is your opinion ? Do you still suggest a new installation ?

Rick Poulin

There are additional locations for database configuration (including, for example, a jboss-ds.xml file within the Application Container). It's certainly possible to track them all down, but I think you'd find it becomes a tedious process of trial+error. More to the point, it completely defeats the purpose of starting with fresh databases for your new install.

As a general rule, I would always recommend a fresh install on new servers anyway. It's a lot cleaner and it provides an opportunity to make sure you have a firm grasp of the code you're porting to the new server and allows you to discard any garbage that is no longer in use. In-place installs are typically much more error-prone in general, and adding a DB relocation at the same time just makes the process that much more complex.

Like I said, doing the manual adjustment is certainly possible. But take the easier path if you can.