We don't have a native SAP connector. However, here is an example you
can use to test SAP. This is a real example we are using at a customer
site but has been scrubbed so I could share it with you all.

The basics of this are the following:

- Create an iDoc from SAP you can reuse. (just take a test idoc you've
used before and you can change the names, ids, etc. to make it unique)

The test will look like this:
- Use winscp (or any other scp command) to copy it to the IDM server
where the SAP driver is running via the execute connector.
- Let the driver process the iDoc as normal.
- Assert the various user objects, p objects, etc. are where they should
be in eDir.

This will allow you to have almost full test coverage of SAP. The only
thing I know of so far you wouldn't be able to test is the SAP logic
that creates the iDoc. But this would still if you 90% plus coverage
and is pretty easy to implement.

Here is a link to the sample test and sample batch files we used:

'SAP-Validator-Example' (http://tinyurl.com/popltoc)

This same concept can be used for testing Google drivers and others.

Let me know if you have any questions.

kgividen's Profile: https://forums.netiq.com/member.php?userid=4528
View this thread: https://forums.netiq.com/showthread.php?t=47819