Skip to main content

Posts

Showing posts from 2019

How to convert any application-specific JSON to XDS format for NetIQ REST driver to consume

How to convert any application-specific JSON  to XDS format for NetIQ REST driver to consume See tip: MessageValueTextToNetIQ <rule> <description>Successfull poll-users command handler actions bases on trigger job;</description> <conditions> <and> <if-operation mode="regex" op="equal">status</if-operation> <if-xpath op="true">./driver-operation-data[@command="custom-IDM-JOB-GET-USERS"]</if-xpath> <if-local-variable mode="nocase" name="StatusValue" op="equal">200</if-local-variable> </and> </conditions> <actions> <do-trace-message> <arg-string> <token-text xml:space="preserve">poll-users completed successfully; </token-text> </arg-string> </do-trace-message> <do-set-local-variable name="StatusValue" sc

Submit multiple SOAP calls form one modify operation generated from subscriber command

Put this policy on output. <rule> <description>Update CostCenter SOAP doc</description> <comment name="author" xml:space="preserve">Maqsood Ali Bhatti</comment> <comment name="version" xml:space="preserve">5</comment> <comment name="lastchanged" xml:space="preserve">Sep 20, 2016</comment> <conditions> <and> <if-operation mode="regex" op="equal">modify</if-operation> <if-op-attr name="customCommand" op="changing" /> <if-op-attr mode="regex" name="customCommand" op="equal">updateCostCenter.*</if-op-attr> </and> </conditions> <actions> <!-- add operaiton data --> <do-for-each> <arg-node-set> <token-op-attr name="customComman