Join now to ask questions and share information with your peers.
Dear members,
If you have not done it yet, take a few minutes to complete your profile on Community with your title (<job title> at <company name>) and a few words about yourself. This will strongly help the other members to know your background and understand more your use cases and expectations!
When following the documentation on declaring REST Clients1, it is mentioned that the Response Output Value Selector corresponds to "a JSON Path1, starting from the root of the response payload and pointing to a single value in the payload".
To help find the desired JSON Path you may follow these steps :
Matching performance is a complex issue. There could be many causes that lead to unsatisfactory integration job processing times, including poorly optimized match rules that perform too many fuzzy-matching comparisons or logic bugs that ensure your integration jobs will simply never finish.
Assuming your data volumes are large and you've got adequate hardware allocated to xDM (memory, storage specs for the application server and database), if you've optimized and feel confident that there's no more to be gained by tweaking match rules, here are steps you can try to speed up your integration jobs.
These steps are very technical and... (More)
When reloading data, you can delete the existing data by truncating tables. Attached are sample scripts you can use to generate the truncate statements that you then execute. The attached scripts cover Oracle, PostgreSQL, and MS SQL Server.
In the sample script, you must specify the data location. You can also specify the entity name if you are only truncating data from a specific entity.
Getting Started
Knowledge Base
Events
