Index: openacs-4/packages/acs-authentication/www/doc/configure-batch-sync.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/configure-batch-sync.html,v diff -u -r1.1 -r1.2 --- openacs-4/packages/acs-authentication/www/doc/configure-batch-sync.html 31 Oct 2003 14:21:05 -0000 1.1 +++ openacs-4/packages/acs-authentication/www/doc/configure-batch-sync.html 19 Feb 2004 14:59:42 -0000 1.2 @@ -1,45 +1,40 @@ -Configure Batch Synchronization

Configure Batch Synchronization

  1. Browse to the authentication administration page, +Configure Batch Synchronization

    Configure Batch Synchronization

    1. Browse to the authentication administration page, http://yourserver/acs-admin/auth/ and choose an authority for batch sync.

    2. Set Batch sync enabled to Yes. Set GetDocument Implementation to HTTP GET. Set ProcessDocument Implementation to IMS Enterprise 1.1. These settings will cause OpenACS to attempt to retrieve via HTTP a list of users in XML format from a location we will specify in a few steps.

    3. Click OK.

    4. On the next page, click Configure on the GetDocument Implementation line.

    5. Enter either or both the IncrementalURL and SnapshotURL. These are the URLs which the external Authority will supply with XML files in IMS Enterprise 1.1 format.

    6. Configure your Authority (RADIUS server, etc) to supply XML files to the URLs IncrementalURL and SnapshotURL. A typical set of incremental file record - looks like:

      +            looks like:

      <?xml version="1.0" encoding="ISO-8859-1"?>
       <enterprise>
      -  <person recstatus = "1">  added person
      +  <properties>
      +    <datasource>FOO</datasource>
      +    <target>dotLRN</target>
      +    <type>DB Increment</type>
      +    <datetime>28-oct-2003#16:06:02</datetime>
      +  </properties>
      +  <person recstatus = "1">
           <sourcedid>
      -      <id>[username]</id>
      +      <source>FOO</source>
      +      <id>karlf</id>
           </sourcedid>
           <name>
      -      <family>[last_name]</family>
      -      <given>[first_names]</given>
      +      <n>
      +        <given>Karl</given>
      +        <family>Fritz</family>
      +        <prefix></prefix>
      +      </n>
           </name>
      -    <email>[email]</email>
      -    <url>[homepage_url]</url>
      +    <email>karlf@example.net</email>
         </person>
      -  <person recstatus = "2">    modified person
      +  <person recstatus = "2">    <!--modified person-->
           ...
         </person>
      -  <person recstatus = "3">    deleted person
      -    <sourcedid>
      -      <id>LL1</id>      only requires username
      -    </sourcedid>
      +  <person recstatus = "3">    <!--deleted person-->
      +  <sourcedid>
      +    <id>LL1</id>      <!--only requires username-->
      +  </sourcedid>
         </person>
      -</enterprise>

      A snapshot file is similar but doesn't have recstatus, - since it's not a delta but a list of valid records. -

      -<enterprise>
      -  <person>
      -    <sourcedid>
      -      <id>[username]</id>
      -    </sourcedid>
      -    <name>
      -      <family>[last_name]</family>
      -      <given>[first_names]</given>
      -    </name>
      -    <email>[email]</email>
      -    <url>[homepage_url]</url>
      -  </person>
      -  ...
       </enterprise>
      -

      (More information: Section�, “IMS Sync driver design”, The IMS 1.1 spec)

    View comments on this page at openacs.org
    +

    A snapshot file is similar but doesn't have recstatus, + since it's not a delta but a list of valid records. See the larger example in the design document for more details. +

    (More information: the section called “IMS Sync driver design”, The IMS 1.1 spec)

($Id$)
View comments on this page at openacs.org