Article
NetIQ Identity Manager: XPATH and the Four Contexts
by Geoffrey Carman
Well that is a silly title, but I was having a conversation with some people I was helping and as always a major stumbling block for getting started with Identity Manager (IDM) is how XPATH works, which should be understandable, but in an Identity Manager context it seems to confuse the heck out of people.This is actually fairly simple, once you understand a single concept: The default Current Context is the event node.
I have tried in most every XPATH article I write to focus on this issue since it is so important in the hopes that people looking for this kind of information will find one of the many attempts I have made in an attempt to tackle this major issue. They did update the docs a little bit to change this from a one line comment to a more useful example, but I wish they went further still. As a quick reference, since I so enjoy quoting myself, but in useful ways, if you are new to IDM and find this article, you may be interested in reading my article series on things newcomers to IDM always need to learn: Common Mistakes IDM Newcomers Make Part 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 & 11. I figured this was an easy way to tackle some of the harder issues:Then specific to XPATH, I would like to remind you of my other articles about XPATH:
Concepts:
- Some Thoughts on XPATH in Identity Manager
- XPATH and the Context Node
- XPATH and Math
- Using String Compares in XPATH Statements
- Another Attempt at Explaining the XPATH Context Node
- Example Walk Through of Using XPATH in Identity Manager
- Examples of Using XPATH in Identity Manager
Cool Tips:
- Using XPATH to Examine Association Values
- Cool Tricks Using XPATH Node Sets
- Using Global Configuration Values in XPATH
- Using XPATH to get the Position of a Node in a Node Set
- XPATH to do Schema Mapping Rule
- Using XPATH to Reproduce the Map Token
Read Geoffrey's article in the NetIQ Qmunity >
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 2389 reads


0