Is Your WebSphere Commerce Messaging Lost in Translation?
Roy.Leung 0600019YT3 Comment (1) Visits (4386)
In the past, there have been a few incoming problem records (PMRs) about messaging, such as why emails are not being sent, and why messages are being lost. So, I would like to spend some time talking about these common questions that I hear about messaging.
Messaging is not new in WebSphere Commerce. However, it has been evolved, from the XML message integration to later "simple" inbound web service. Essentially, debugging requires you to understand how the underlying process works and how to interpret tracing.
First of all, you have to understand if you are dealing with an inbound or an outbound message. An inbound messages refers to a message that feeds into WebSphere Commerce. An outbound message is the one that is sent out from WebSphere Commerce.
If you are dealing with an outbound message issue, a common question is: "Why are messages not being sent?"
Ask yourself, how are the messages created? Is the message generated by a customized command or an out-of-the-box (OOTB) command? If this is an OOTB command, enable WC_SERVER tracing (if it is a production environment, enable tracing during a non-peak hour) to see if the command is being run. It may also be helpful to enable component-specific tracing (such as WC_USER if this is a registration type email).
Since most messages are being sent by an OOTB command asynchronously by send
Another problem I see on occasion is that the same message is sent multiple times. One possibility for this is when these two conditions are met:
In this blog post, I have shared my thoughts on performing some problem determination for an outbound message issue. In a subsequent posts, I plan to discuss more about my experience with inbound messages and some general observations of messaging in WebSphere Commerce. In the near future, I also plan to discuss other areas in WebSphere Commerce, such as the catalog and component service.