README revision baf15352a4774619a416d0c0b567ed834d349513
d6fa26d0adaec6c910115be34fe7a5a5f402c14fMark AndrewsSample 1 - One-Way XML -> Internal Repository
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein---------------------------------------------
32098293b78922a5fbd10906afa28624820d3756Tinderbox UserCopyright (c) 2012 ForgeRock AS
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThis work is licensed under a Creative Commons Attribution-
5347c0fcb04eaea19d9f39795646239f487c6207Tinderbox UserNonCommercial-NoDerivs 3.0 Unported License. See
5347c0fcb04eaea19d9f39795646239f487c6207Tinderbox Userhttp://creativecommons.org/licenses/by-nc-nd/3.0/
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThe documentation at http://openidm.forgerock.org/doc/install-guide/index.html#chap-sample
d6fa26d0adaec6c910115be34fe7a5a5f402c14fMark Andrewsdescribes how to get started with this sample.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThe sample demonstrates reconciliation between the OpenIDM internal
cd32f419a8a5432fbb139f56ee73cbf68b9350ccTinderbox Userrepository and an external XML file, with data flowing from the XML
fd2597f75693a2279fdf588bd40dfe2407c42028Tinderbox Userfile into the internal repository.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThe configuration files used in this sample are as follows:
cd32f419a8a5432fbb139f56ee73cbf68b9350ccTinderbox User* samples/sample1/conf/provisioner.openicf-xml.json shows the XML connector configuration.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein* samples/sample1/conf/schedule-reconcile_systemXmlAccounts_managedUser.json includes a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein schedule configuration you can use to run reconciliation periodically.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein* samples/sample1/conf/sync.json describes how identities in the XML file source map to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein identities in the internal repository target.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinData for this sample is stored in samples/sample1/data/xmlConnectorData.xml. The initial
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinXML file contains two identities.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinTo run the sample, start OpenIDM with the configuration for sample 1:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinInitiate a reconciliation operation over the REST interface, as follows:
fd2597f75693a2279fdf588bd40dfe2407c42028Tinderbox User$ curl --header "X-OpenIDM-Username: openidm-admin" --header "Content-type: application/json" --header "X-OpenIDM-Password: openidm-admin" --request POST "http://localhost:8080/openidm/recon?_action=recon&mapping=systemXmlfileAccounts_managedUser"
fd2597f75693a2279fdf588bd40dfe2407c42028Tinderbox UserAlternatively, edit samples/sample1/conf/schedule-reconcile_systemXmlAccounts_managedUser.json
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Huntto enable scheduled reconciliation:
fd2597f75693a2279fdf588bd40dfe2407c42028Tinderbox User "enabled" : true,
14a656f94b1fd0ababd84a772228dfa52276ba15Evan HuntThe following curl command requests all identifiers in OpenIDM's internal
14a656f94b1fd0ababd84a772228dfa52276ba15Evan Huntrepository. Use it to see the results after reconciliation for example.
33c9436ef1a43d3c0fc3d9be9b4b0509daa83223Tinderbox User$ curl --header "X-OpenIDM-Username: openidm-admin" --header "X-OpenIDM-Password: openidm-admin" "http://localhost:8080/openidm/managed/user/?_queryId=query-all-ids"