Mike, If you're using a SQL repository, there's nothing to move, just make sure your final config.xml includes the correct references to the db.
If you're using a file based repository, I think you can just copy over the "var" folder. -Chris > -----Original Message----- > From: Mike Danifo [mailto:[EMAIL PROTECTED] > Sent: Saturday, February 22, 2003 11:01 AM > To: 'James Users List' > Subject: RE: updating my james version > > > Noel- > How about: > > migrating exsiting users > migrating existing emails > > ? > > -Mike > > > > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Friday, February 21, 2003 1:11 PM > To: James Users List > Subject: RE: updating my james version > > > Chris, > > In my case, I just did: > > - install james-2.1.2 into /opt/james-2.1.2 > - open current and new config.xml > - view color coded difference (good tools help) > - merge changes > (in my case, a couple of lines) > - delete environment.xml and assembly.xml > (I wanted the new versions) > - service james stop > - change /opt/james symlink to reference /opt/james-2.1.2 > - mv /opt/james-2.1/apps/james /opt/james/apps > - service james start > > That was it. > > --- Noel > > -----Original Message----- > From: chris schild [mailto:[EMAIL PROTECTED] > Sent: Friday, February 21, 2003 12:37 > To: James Users List > Subject: Re: updating my james version > > > Same situation i.e. newbie what do I do. Did a quick search on > upgrading didn't find much. Hopefully that is good... I am using mysql > on a win2k box. I am installing using the binary. Is it as simple as: > - copying the old directory. > - uninstalling james. > - installing the new binary. > - configuring the config.xml with the old information. > - (re)starting james.. > > That it? > > Anything someone would recommend on backing up before the upgrade? Or > is just copying the directory a good enough backup? > > > > > ----- Original Message ----- > From: "Mike Danifo" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, February 20, 2003 10:26 PM > Subject: updating my james version > > > > Hello, > > given the recent announcements about new james versions, I thought I'd > > > ask this question. It may seem like an obvious question to james > > veterans, but as a newbie, I just have to ask: > > > > what is typically involved in updating a version of james? can I get > > away with just copying over the config.xml and/or environment.xml from > > > the older version? do I have to manually replicate the changes in > > these 2 files from one version to the next? > > > > I have a pretty basic setup, so I don't have to worry about any sql > > auth stuff, etc. > > > > thanks > > > > -Mike > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
