I’ve been part of this client for the last seven-plus years. It’s been close to 70 to 80 continuous improvements we have delivered. The priority ones which we always shortlist are the recurring incidents or recurring issues, which came in the initial phase of the year when we took this entire landscape under our maintenance. One such incident I can recollect is with respect to performance tuning. We committed to our users 99.99% and above as the availability metrics for Sterling Integrator. This has acted as a high-availability system, but we treat it as mission-critical. When it comes to the commitment we give to users, we have to ensure the system is kept most stable. So, the majority of the problem was in the communication channels. Whenever we enabled additional logging for the communication channel, the system used to have hiccups. So we worked with the vendor, stating that the visibility channel framework needs to be changed because the moment we enable more logging, it literally brings the system down, or the system doesn’t work as it should. They took our input and delivered a better framework in their next releases, which helped us after upgrading to have that stability intact. As the system grows, we ensure to have performance tuning triggered and optimize the business process wherever required. For example, by default, Sterling Integrator business process will have full logging enabled. We took care of those things. Not all business processes or workflows require full logging enabled. Only a few critical ones require every step logs. For the rest, we categorized and reduced the logging for those workflows. That actually helped us to increase the IO overall from ten milliseconds to six milliseconds. That was a good achievement. Apart from that, in terms of queues, how we maintain the queues, how we defined all file queues across the critical business process is one thing we felt was done better. The threads we assign for the priority queues and the business processes were configured to those priority queues, whatever is critical, so that it gets high priority to allow the threads to process. So that queue thread Sterling was taken under the performance tuning. Apart from that, I think some of the best practices which IBM recommends is what we usually run through every year. We just have the health check done through IBM, and we just ensure that all the best practice recommendations are added in the system.
