Custom Role Processing between Banner and Luminis through LDI
Just some quick notes on Custom Role Processing through LDI. Hope it will help somebody....
INB: Define the new role on GTVSQRU INB: Create select statement for the new role on GORRSQL (ensure to return only distinct pidms) Portal: Update pds.roles.external with configman in Luminis ldap: Lookup current roles with: configman -g pds.roles.external Create a roles file with the following content, and all your institutions roles appended: pds.roles.external = Alumni,...., newrole import the roles.txt file into ldap with: configman -i roles.txt create a new accessgroup as the portal admin: Access Groups -> New (mixed case, space replaced with an '_') restart luminis INB: Synchronize (ICGORODM) a person that would have the custom role. Lookup person in portal admin to verify role assignment.

another caveat
you may also want to run gurirol to populate the gorirol table. this table should be populated automatically, but i have had to run the process to make updates to the table. icgorldi appears to pull from this table and not actively run the selects in gorrsql.
Can't find the table: gorirol
I can't seem to find the table you refer to. Has it the correct spelling?
ps: I'm not running the extract: icgorldi though, I'm running on demand synchronization for the person through icgorodm (by sct id)
it should be there
the table is general.gorirol. the job to populate the table is gurirol. i'm looking at it now on banner 7.3. it was there in 7.2 as well.
intcomp version behind...
I understand now, we are still on INTCOMP 7.1
Banner Version?
Is this Banner 7 specific or can us lowly Banner 6 schools take advantage of this as well?
--Tony
banner 7
this is a banner 7 enhancement. custom roles in banner 6 requires major modification to the baseline product.
Thanks!
Thank you for posting this... just what I was looking for!
I was getting "Attempt to set invalid role(s)" error messages after the message would come over from Banner to Luminis.
I was missing the step of adding the Access Group with the same name as the Custom Role name.
Custom Role messaging is now working great!
BTW, changes with configman only requires a web server restart [on our Win2000 Luminis box: ~/bin/rc/70-webserver stop; ~/bin/rc/70-webserver start], not a full Luminis services restart.
Thanks again!
Ginny Lee...Colorado School of Mines
No, thank YOU!
I just got caught by this same error. Because of your post I was able to get past it. Thanks so much!