Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] XML Import Tool

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] XML Import Tool


Chronological Thread 
  • From: Jonathan Tellier <>
  • To: Chris Hyzer <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] XML Import Tool
  • Date: Thu, 7 Jun 2012 09:20:29 -0400

Ok, thanks for the info. I'll share my work if I happen to write a
general-purpose plugin to achieve what I'm trying to do :)

--jtellier


On Wed, Jun 6, 2012 at 4:41 PM, Chris Hyzer
<>
wrote:
> Eventually this type of thing can be done with the PSP, or now if you write
> a plugin.  But the XML - SQL - loader - Grouper sounds fine too...  you
> could also call a web service to replace the members of a group with a list
> and it will do the appropriate adds/removes...  lots of options :)
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: Jonathan Tellier
> [mailto:]
> Sent: Wednesday, June 06, 2012 4:18 PM
> To: Chris Hyzer
> Cc:
>
> Subject: Re: [grouper-users] XML Import Tool
>
> It would be ongoing. My goal is to replace Grouper's source of data (a
> DB, an LDAP, etc.) with an XML file. To put it more concretely, for
> instance, when deploying Grouper with the Grouper Installer, it's
> possible to load sample data from an HSQL DB. Well I'd like to swap
> that DB with an XML file. Once the data will be loaded into Grouper
> I'll provision it into some other destination, not back into the XML
> file. Is such a thing possible?
>
> If it's not possible, I can always write a script or something that
> would populate a DB with the data contained in my XML file. I would
> then do as you suggest, that is, load Grouper with the data contained
> in the DB. It's not that much of a problem for me, but I was wondering
> if I could skip this intermediate step.
>
> Thanks,
> --jtellier
>
>
> On Wed, Jun 6, 2012 at 4:02 PM, Chris Hyzer
> <>
> wrote:
>> Jonathan,
>>
>> The XML import/export is intended to be used for Grouper-to-Grouper
>> syncing...
>>
>> Can you give some more information about what you are trying to do?
>>
>> Is it a one time sync, or ongoing?
>>
>> Grouper does not manage subjects, though we have been discussing the
>> ability to provision subjects to other systems (TomZ is that true?  Is it
>> possible now?)
>>
>> Have you read about the Grouper Loader?  If this is an ongoing sync, you
>> could sync to a database (the memberships) and the loader can get them
>> from there.
>>
>> If it is one time, you could generate a GSH script and run that.
>>
>> Maybe we need to setup a conference call or maybe you could join the next
>> dev call in two weeks to discuss...
>>
>> Thanks,
>> Chris
>>
>> -----Original Message-----
>> From:
>>
>>
>> [mailto:]
>> On Behalf Of Jonathan Tellier
>> Sent: Wednesday, June 06, 2012 11:05 AM
>> To:
>>
>> Subject: [grouper-users] XML Import Tool
>>
>> Hello,
>>
>> I am currently evaluating the possibility of using XML files as a
>> source for subject and group data. This data will then provisioned to
>> another system. After reading about the XML Import/Export tool [1] and
>> after finding a sample XML import file [2] that is possibly outdated
>> (it was linked from an archived page), I've came to the conclusion
>> that what I'm trying to achieve is not possible. The doc about the XML
>> Import/Export tool specifies that the subjects must be resolvable
>> (i.e. present in one of my Grouper's source) and the sample XML file
>> does not contain any subject information. Is that the right conclusion
>> ? If not, where can I find a sample XML file that is not outdated (if
>> the file is outdated) and/or documentation describing the format that
>> such a file must have? Is my best bet to develop an XML connector that
>> could load subjects and groups data from XML files ?
>>
>> Thanks,
>> --jtellier
>>
>>
>> [1] https://spaces.internet2.edu/display/Grouper/Import-Export
>> [2]
>> https://spaces.internet2.edu/download/attachments/14517689/xml-tool-quickstart.xml?version=1&modificationDate=1150478649938



Archive powered by MHonArc 2.6.16.

Top of Page