The OCS-Integration supports two ways of mapping between the OCS-Datamodel and the OpenNMS Requisition:
- default mapper (java classes that apply the mapping)
- script mapper (Apache-BSF compatible scripts that apply the mapping)
Both are independent mappers.
If the default mapping is not 100% suitable for the scenario the entire mapping has to be implemented manually in a script mapper fashion.
To improve that, the script-mapper should run after the default mapper was applied with the already prepared requisition. If no mapper is defined the script-mapper starts with an empty requisition. This post mapping script would have full access to the OCS-Datamodel and the already filled requisition. Minor changes from the default mapping like, a different foreignId or removing some assets would be way easier.