Hey All,
Looking to see if I am doing something wrong with how I am handling output from an
IDM Job. Just started playing with them, so not sure I
understand the "best practices" for their use.

Here is what I have so far:

1. The Subscriber Trigger job is firing fine, - I am using an if "Xpath expression
true" to test for the trigger for a specific job. (I Plan on using a few jobs in
this driver) - basically :
(if-operation equal "trigger") = TRUE.
(if-xpath true
""/nds/input/trigger/operation-data/@source=Get_AD_lastLoginTimestamp"") = TRUE.

2. I have a Rule that runs when the trigger from a specific job is discovered - this
rule queries AD for the presence of and value of lastLogonTimeStamp (which is in
the filter and schema map!)

I get the output document back - which looks just fine to me. (It passes through
the Input Transform and converts the AD value to an eDir value just fine)

<nds dtdversion="1.1" ndsversion="8.7">
<product asn1id="" build="20080822_140000"
instance="\VIDVTREE\CUSTIDV\IDVDriverset\AD to IDV" version="3.5.4">AD</product>
<contact>Novell, Inc.</contact>
<instance class-name="User" event-id="0"
src-dn="CN=Last\,First,OU=Users,OU=SJPHX,OU=AZNV,OU=Re gional_Sites,DC=staging,DC=local">
<attr attr-name="JimClassLastADLogon">
<value type="time">1224094920</value>
<status event-id="0" level="success"/>

3. I am not having any luck getting the Driver to use this value ( <value
type="time">1224094920</value>) to populate the attribute in eDirectory. I have
tried to set it via policy directly and using XPath to get the value into a local
variable, but haven't got that working either. The issue seems to be in the trace
where it says:
"Submitting unknown event to subscriber shim." and

<status level="warning" text1="subscriber parse" type="driver-general"/>
<message>Command not recognized by driver</message>

The TID that I mention says that it is not an issue, but doesn't really say what
behavior the driver will use when encountering it. I've been able to set other
source attributes to a derived value in the Sub Event Transform.....

4. I saw somewhere that I can strip this Job's Trigger document out of the
Subscriber channel after I process it. I'm trying to figure out clean way to do
that. Anyone been able to do this for a specific job's trigger? I have the XML
doc, and assume that I can use the strip XPath expression directive.

Is this something I'm overlooking in my code, or a nuance about how Jobs work???