To make your IBM experience better, this blog shares some tips 'n' tricks that you can use while working on Commerce on Cloud product
- Mention the environment where you experience the problem - Production, Pre-Prod, QA or Development. If possible keep the server hostname/IP address handy. This will help the Support or AppDelivery engineer quickly access the server and associated diagnostic data such as logs
- For sporadic problems in applications ensure that you capture the timestamp of the problem occurrence. This is crucial for Support or AppDelivery engineer to backtrack to the exact problem period in the logs and makes diagnosis faster. Note that with 17.4, UrbanCode Deploy(UCD) self serve process allows users to generate thread dumps from Application Server, Agent and Integration servers. This can be an invaluable diagnostic aid for situations like hang, slowness, crash, memory leaks, CPU spikes etc. Famiiarise the process before raising a PMR.
- Clearly state the business impact. Business impact is not the problem statement but rather due to the problem in place how does the overall business running on CoC gets impacted. Clearly mention any impending deadlines, revenue impact, business outages so that the right attention is attracted at IBM at a very early stage