Maqsood Bhatti - iDENTITY

Looking at this article: https://www.netiq.com/communities/cool-solutions/how-start-idm-job-policy/ it shows you the complete recipe, except it does not show how to deal with dynamic argument values for the method itself; here is my version; I wanted to run this on the driver startup and wanted to let driver die if job execution did not succeed. 1. username must be "dotted" format; one can use parseDN; example: <token-parse-dn dest-dn-format="dot" src-dn-format="ldap">                         <token-local-variable name="local.sub.etp.resource.UserId"/>                     </token-parse-dn> 2. Jobname must be in "dotted" format too. 3. For more java lovers, one can dig into this: https://www.novell.com/documentation/developer/dirxml/dirxmlbk/api/com/novell/nds/dirxml/util/DxCommand.html < rule > < description > Schedule job on the startup </ description > < conditions

Always pain working with SOAP service and its handling of service response on Query(matching) for user to work with matching policies? Here is the quick wins; without reading  those long lengthy & boring useless SOAP driver blog series at netIQ forums; 1. Make sure you have mapped User class in the schema map with some service attributes 2. Make sure Input and Output policy is registered with all the namespaces you have in your request/response soap messages, example <policy xmlns:soap="http://www.w3.org/2003/05/soap-envelope" 3. I have added operation-data (which is being generated from the Output policy) as part of the SOAP query, but you can skip it if you do not need this. src-dn and association are important to indicate engine for building association.  Operation data will help you to identify operation type and you can carry actions according to it. Inject this on Output ( To support user matching) to send service request: < rule > &l