We're trying to figure out how Luminis maps the data that it gets from Banner for inserting into the Sun LDAP.
- We can see that Banner simply populates event tables based on triggering activity.
- It looks like Luminis uses a jdbc connection with the integmgr user to pull the data out of those tables and process them.
What I'm noticing is that Banner provides more data to Luminis than what Luminis actually puts in the LDAP. For instance, Banner provides address information (Street, Locality, Region, etc.), and it looks like Luminis sees the data (see the datapipeline-audit.log). However, Luminis does not put this data into the LDAP like it does the display name, pdsrole and so forth.
I'm guessing that there must be some configuration file that tells Luminis what data to put into the LDAP and where to put it into the LDAP. I thought I had found that file with personDirectory.xml.
In the Luminis IV Administration Guide there is a section on Importing User Attributes into Luminis. It begins on page 333 and goes for about 25 pages and references personDirectory.xml. I'm hoping that someone can help us know if this is even the right place to look.
This is our biggest technical challenge at the moment, and we would appreciate any help. We need to pass some extra data from Banner to the Luminis LDAP that will then get synched to other LDAP's. If anyone could point us in the right direction, we would be very grateful.
Take care.
mark
Comments
personDirectory.xml
I have no idea where the information you are looking for might reside (very likely internal to one of the jar files), but personDirectory.xml has a different purpose. It is used to define the person attributes for portal users. By default it defines a number of attributes that are pulled from the Luminis LDAP. There are instructions in the admin guide for adding attributes from other sources such as other LDAP trees or JDBC databases. One reason I know this cannot be the correct location for the information you are looking for is that the information has to contain how to map other event types like sections.
I was coming to that conclusion
There just didn't seem to be enough information in that file, but I hadn't found a good alternative yet. I'm hoping someone will know and share with me. I'm not so keen on systematically unjaring file after file looking for the right one. My real fear would be unjaring everything and still not finding it.
personDirectory.xml
Hi Mark,
I'm in the Importing User Attributes boat as well. personDirectory.xml is where you set up the link to get data out of Banner. I'd be willing to send you my version which documents our changes (need email address or way to post it here). I've also written a PL*Sql function on the Banner side (called in personDirectory.xml) which has immutable id as the argument and returns the luminis login id which we store in gobtpac_external_id. With gobtpac_pidm we can join to many tables in Banner to get attributes for a luminis user.
My problem is getting a dynamic drop down list on the luminis side when selecting user attributes in creating a targeted audience.
Here is my question to Sungard:
For the LDAP user attributes there is a drop down box that is dynamically created (like for majors) when building a targeted audience. It doesn't seem to work the same way with user attributes from Banner.
I set up a Banner attribute for campus code, making the "values" area in my attributeCampusConfig bean the same as attributeAcademicMajoorConfig. The comment in attributeAcademicMajorConfig is:
And they are. I would like to know how to code the config bean for my campus code attribute (Banner RDB atttribute) so that a drop down box of campus codes will be created dynamically when setting up a targeted audience. There is no drop down box for this one.
---------------------------------------------------------------------------------------------------------
Here is Sungard's reply:
In case of
com.pipeline.uportal.persondir.AcademicMajorAttributeConfig is a predefined class (extends ReferencePersonAttributeConfig)
which retrieves a map of (key,value) for Majors from LDAP.
If you want to dynamically retrieve values for bean “attributeCampusConfig” then you would require to define your own custom class.
Example:
public class CampusAttributeConfig extends ReferencePersonAttributeConfig
{
public CampusAttributeConfig()
{
super();
}
public Map getValues()
{
// code to retrieve map(key,value) for attributeCampusConfig from
// RDB goes here..
};
}
Let me know if you have any further questions.
-------------------------------------------------------------------------------------------------------
Mark, or anybody, do you have sample java code that connects to Banner and retrieves data?
Thanks,
Dean
personDirectory.xml
My previous post is missing this comment:
Also, the 'Importing User Attributes' section of the administrator guide has errors. There is a set of corrections that can be found on the Sungard site or I can send it.
Dean
Missing for a reason I suppose
Since html/xml comments don't show in these posts. The comment is:
Major code values will be dynamically retrieved
my contact information
Hi, Dave,
You can reach me at mhardman@harford.edu. I'll be away from email for a little over a week, so I may not respond immediately.
Thanks for what you have posted.
Take care.
mark