on 06-05-2014 4:56 AM
Dear experts
in case of TM-EM integration, we know that initial creation of event handler happens with data extracted using application system extractors like expected event extractors, control / info parameter extractor & tracking id extractors.
In case, subsequent changes to the TM BO needs to update the event handler with new tracking IDs, parameters, changed expected event dates etc, should we handle it through AOT extractors or event messages?
It would be good to hear your opinions specifically in the below context:
1. With TM as the application system
2. Some events have already occurred and reported either from TM or from external systems.
3. When TM BO change should result in:
- adding new expected events
- changing the expected dates on existing expected events
- replacing an existing tracking id
- adding a new tracking id
- replacing an existing parameter
- adding a new parameter
Thanks in advance for your help.
Always use the Event Message to update the EH after it has been created. You don't want the performance burden on the Application side (TM) for all the relevance and extraction code and you don't need the same on the EM side for recreating the EH and reposting all existing events... It may be easier to do it the AOT way but it's better for the system to do it the hard way
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Kevin & Steffen. We will shift the code from AOT to Evt Type extractors then.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Event message
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.