There is quite a bit of value in bringing your Lawson S3 LDAP or other LDAP data into Smart Notes. Once it’s in an infoset, you can use the data in other Smart Notes for bursting, delivery, etc. We actually use it as an auditing tool for security changes. We build infosets on the Lawson security data and check for new keys each day. This assures the auditors that any changes we make are through the established change control process. Building an LDAP infoset is actually quite simple, but maddeningly hard if you don’t know some of the specifics. Gary Garner from Lawson was the one who originally showed me how to do it. The examples below are of a simple infoset that we use for bursting.
- The user id and password should be for a user that has the ability to query the LDAP directly and is not an ID set up in the Lawson Security Admin tool (although it might be).
- Provider URL is the URL to your LDAP with the port number. I believe the standard port is 389. Your LDAP administrator should be able to provide this.
- Enter the Context Factory exactly as you see it here.
- See below for Search Base.
- Unless you are familiar with LDAP searches, you’ll probably want to leave the Query string as I have it here. There are several good web resources for LDAP search if you’re not getting the results you want.
Keep in mind that the Lawson LDAP was designed by someone who either never wanted anyone to be able to use it or they didn’t actually know how LDAP works. I’m sure they had a reason for designing they way they did, and I’m pretty sure it’s a bad reason. But I digress…
The Search base follows the LDAP search standards. The full path can be determined by using a tool like JXPlorer. Note that the path is in reverse order from the way you descend the tree.
After you click next, you will need to add the field mappings. I would recommend that you do NOT allow SN to auto create the fields. The source name (highlighted) should correspond to the attribute name you see in JXPlorer. Once upon a time when dealing with an LDAP source, if the name didn’t match the source name it caused issues. We continue to do that and I can’t comment as to whether it has been fixed. In this case, we’re bringing in the user’s RMID (cn), Full Name and Email.
Here’s a screen shot of the Attributes in JXPlorer.
(For those who are wondering – yes the first four entries here correspond to the Query string in the first screen shot.)
If you want to be able to query the data set using a SQL tool, Crystal reports, etc you should check the box indicating that it’s a large infoset when you save it. This will create a table called INFOSET_NNNN in the LawsonSN database where NNNN is the id of the infoset. The fields in the table for this example will be COLUMN0 (id), COLUMN1 (name), COLUMN2 (email).