Xml data type is not supported at Account collector. Is there any custom solutions to be able to read account data from xml?
On the other side, xml data type is supported at Entitlement collector. However, only custom attributes are shown. It means that we can not provide relation between Account and Entitlement or relation between App Role Ent. and Resource Action Ent.
We expect to see below relation(key) attributes.
- account collector
- Community Thread
- Data Collection
- entitlement collector
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
You would need to change the XML to a CSV and use the Database template. This can be achieved by using an XML transform process i.e. xsltproc
This means that you have to define the transform file specifically for the XML file that is being referenced.
A few questions:
- What is the software the XML is coming from?
- Can a CSV be output instead?
- Where is the XML file being stored? (On the Via L&G server or elsewhere)
Thank you for response. Xml is coming from target system. Most Probably, they can not export csv. It is stored in Rsa server.
According to response, we need to parse xml file with custom solution.
You could try storing the xml file in a CLOB in the Oracle database in a custom table and extract the data with an Aveksa DB collector with XMLTABLE/XMLTYPE functionality from Oracle.
Do you know what the target application is?
If there is no other option except transforming the XML to CSV, xsltproc is on the Via L&G server.
You would need to create the XSL specifically for the XML structure being returned. I'd have to see the XML structure to give you some ideas about the XSL format.
You'd then have to create a cron job to do the transform i.e.
xsltproc -o <full file path to target CSV> <full file path to XSL> <full file path to XML>
This is similar to our standard integration approach. We use informatica to load an XML BLOB to a custom database table, and then we collect from the BLOB. By using this approach, Informatica is able to implement a wide variety of data validations to ensure we don't get erroneous data.