Grouper Users - Open Discussion List

[Peter DiCamillo <>]

I'm in the process of doing an upgrade from Grouper 1.3 to Grouper 1.6.1 
using the first method.  I dumped some groups in 1.3.1 and restored them 
in 1.6.1 using -xmlimportold.  I dumped a stem immediately under the 
root using -name, and no other options.  I didn't use any options on the 
import command.

I found that group members of groups were not being restored.  I checked 
the dump and it looks fine, with correct entries for group members of 
groups.  The groups to be added as members already existed, but the log 
showed them not being found.  The problem seems to be in the restore 
program, XmlImporter.java, and this change fixed it for me:

 426c426,431
 <     return this._getSubjectById(id, type);
 ---
 >     if (type.equals("group")) {
 >       return this._getSubjectByIdentifier(idfr, type);
 >     }
 >     else {
 >       return this._getSubjectById(id, type);
 >     }

I wouldn't expect the restored group to have the same id as the original 
group (unlike people, who do have the same id), so I'm wondering how 
this was intended to work.

Peter

Chris Hyzer wrote:
> There are two upgrade methods:
>
> 1. Export XML, then import into the version you would like (in 1.6, the xml format changed, but you can still import the old with 
>
> ./gsh.sh -xmlimportold GrouperSystem export.xml
>
> However, Im not sure all the lastUpdated dates and minor stuff like that is 
> maintained.   Also not sure about group descriptions (this was fixed in some 
> version, not sure which).
>
> 2. Do all the individual upgrade steps.
>
> I went from 1.4 to 1.6 and did the individual steps.  It was time consuming 
> though.  If you want to give #1 a try, go for it, and check the data 
> afterwards...
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: 
>
>  
> [mailto:]
>  On Behalf Of Scott Koranda
> Sent: Thursday, August 19, 2010 3:55 PM
> To: 
>
> Subject: [grouper-users] upgrading from 1.4.2 to 1.6.1
>
> Hi,
>
> Is it possible to upgrade from Grouper 1.4.2 to 1.6.1 without
> stopping at 1.5.x?
>
> What would be the best strategy?
>
> (We are using MySQL as the backend)
>
> Thanks,
>
> Scott