Print  
Gray star Gray star Gray star Gray star Gray star --Not rated--
458 Visits 6 Comments
Created
Barney Barnes Barney Barnes
Sep 29, 2009 9:04 AM
Kablink Component
  • -- select one --

hi all
i have a problem. i have an install which we have been using now since t2 beta testing and has a lot of data on it. as its the development server we dont want to use this for production as it has all sorts in it, and as always, a nice clean vanilla install is the way forward for our user base.
the vanilla build is of course where i want to migrate the data from the dev server.
now i thought a complete restore of the database and copy of the /var/opt/novell/teaming folder would be enough to migrate across but it hasnt worked.
i want to be careful what i move across as the data is beta code and dont want any bad files being carryed across.
also, if i try to load the full license on the beta server as to remove the beta license, then the system bombs out. tomcat is working but no page displayed.

any ideas what this might be as i have now tried all sorts of methods but none get me anywhere would be great.
please ask for any logs etc that may be needed and ill upload them when requested.
look forward to hearing from you.

regards

barneyb :-)
__________________
Barney Barnes
SysAdmin
Beaverbrooks Organic Technology Department

Workflow
Process State Action
Discussion workflow Active
This entry is currently active
Attachments(0)
Entry History
Tags
  
Replies
Thumbnail Image
Brent McConnell Brent McConnell
Sep 29, 2009 10:23 AM

The difference that may be giving you problems was that the default zone changed from liferay.com to kablink.  If you installed a fresh copy of Kablink the default zone in zone.cfg.xml will be kablink NOT liferay.com.  The data you are importing is likely liferay.com.  Let me know if that's not the case and we'll figure something else out.
Thumbnail Image
Marcel Ramaker Marcel Ramaker
Sep 29, 2009 5:00 PM

Barney,

Why not update your dev server to 2.0 first and then move the data to the production environment. Copy your installer.xml and use the upgrade option?

I've done it this way and works fine.
Thumbnail Image
Nathan B Jensen Nathan B Jensen
Sep 29, 2009 5:20 PM
Modified by
Nathan B Jensen Nathan B Jensen
Sep 29, 2009 7:04 PM

If you are installing onto a new server then trying to copy files over from a 1.0.x version you may run into the problem Brent described.

A brand new install will set the default zone name to kablink, while an upgrade will try to maintain liferay.com. 


You can move forward, and keep kablink as the zone name by doing the following:
The zone.cfg.xml and zone-ext.cfg.xml should have the new default zone name of kablink like Jong described above.
1.  Update two database tables with the new zone name (use the below commands)
a.  update SS_ZoneInfo set zoneName='kablink' where zoneName='liferay.com';
b.  update SS_Forums set name='kablink' where name='liferay.com';
2.  Rename all liferay.com directories where your data directories are located, there are several.
Or you can stay with the old zone name by doing the followin:
1. Edit the zone-ext.cfg.xml which overrides the default zone.cfg.xml and change the name back to liferay.com
2. Edit the installer.xml and change the zoneName back to liferay.com,  this will prevent problems if you do a reconfigure in the future.
<Install type="1" version="0.0" product="OpenSource" zoneName="liferay.com" />
Thumbnail Image
Barney Barnes Barney Barnes
Oct 8, 2009 11:08 AM

hi guys

i think there is a bit of confusion. i have a clean t2 install for production, and i have a dev install of t2. i want to move the dev data onto the

clean install. v1 of teaming doesnt come into it at all. is it not possible to share the same database for both dev install and production install? this would be great

if possible. i havent done anything yet so i will try all ideas on a vm install.

 

look forward to your responses as always :-)

 

cheers

 

bb
Thumbnail Image
Nathan B Jensen Nathan B Jensen
Oct 8, 2009 11:32 AM
Modified by
Nathan B Jensen Nathan B Jensen
Oct 8, 2009 11:47 AM

It was just after T2 Beta 5 that we renamed the default zone name.  A fresh Install will have a default zone name of kablink while your T2 Beta 5 will have a default zone name  liferay.com. So if you look in your T2 Beta 5 directory structure where you files are stored you will notice the liferay.com folders.

So if you backup your db from the beta and restore it to T2 and then  copy your file structure straight across.  Then perform the fix I previously outlined for the default zone name.

 

 

 
Thumbnail Image
Barney Barnes Barney Barnes
Oct 30, 2009 5:16 PM

many thanks nathan. thats cleard it for me. pheew. nightmare over ;-) cheers dude
Skip Footer Toolbar
Permalink