Hello xMatters community/experts,
I recently joined Chase and working on the AlarmPoint implementation enhancements. I just wanted to share my approach to the problem and how consistent it is with the xMatter's future releases.
The problem:
I noticed that we (Chase) used AJAX in saving and retrieving information from custom message panels (JSP). This information is something saved into our database schema, not into AP database. In this process, we started to experience browser freeze and we narrowed it down to Saving information as the implementation does a AJAX (either synchronous or asynchronous ajax) before submitting to AlarmPoint.
We spend a few man days in tyring to go around and address Ajax-based save. However, I felt it is kind of road-block as we see that Browser (IE 8.0), freezes for 2 to 8 minutes on HTTP Send call before releasing the request.
Solution:
In a quest to work out an alternative, I investigated the application architecture and figured out that we could use Servlet Filter into cocoon application as a pre-processing method to save the data before forwarding the request to ProcessCustomMessage.do action.
This is working great.
Question:
Now, I know that when we upgrade AP, we need to make sure this is consistent and manually back-up our changes and put them back.
However, what do you guys think about this approach?
NOTE: If you need any implementation details further, I can provide.