Connector Guides › Connectors Guide › Bulk Load Client › How the Bulk Load Client Works

How the Bulk Load Client Works

The relevant user and account information is extracted from the authoritative data source, (At this time, the data source is PeopleSoft.), in the form of an XML or CSV file. If the information is stored in an XML, the file is transformed to CSV format by the Bulk Load Client using XSL transformation. The resultant CSV file is then used by the Bulk Load Client to invoke the Bulk Loader task on CA Identity Manager. Based on the mapped admin tasks, users are created, modified, or deleted.

The following is an example of the Bulk Load Client cycle:

From the PeopleSoft machine

1. Extract either a full or delta dump of user records in the form of an XML file.
2. Create an XSLT template to convert the XML file into the standard CSV form that can be used by the Identity Manager Bulk Loader task.
3. Feed the XML file into CA Identity Manager Bulk Load Client, together with the XSLT template.

   Bulk Load Client will internally transform the XML file into CSV format required by the Identity Manager Bulk Loader task. You can either just write this CSV file to a disk file or use the CSV file to invoke the Bulk Loader task.

   Note: The resultant CSV file can be loaded in smaller chunks;

4. Bulk Load Client uses the CSV file to invoke the Bulk Loader task using the TEWS interface.

   If the CSV file has been broken up into smaller chunks, Bulk Load Client invokes the Bulk Loader task for each of the chunks. Subsequent chunks will be sent to the Bulk Loader task once the SOAP response from the previous request is received and the response indicates that the previous request was submitted successfully.

5. The SOAP response is logged to a file/written to the standard output.