Collecting MustGather data for Sterling order history issues

Prepare the following MustGather information before you call IBM Support to help with Sterling order history issues.

Procedure

1. Configure the following trace string in the Transaction server Docker container.

   *=info:com.ibm.commerce.foundation.*=all: com.ibm.commerce.inventory.*=all: com.ibm.websphere.commerce.WC_INVENTORY=all

   For information about how to set trace strings, see Configure logging for the Transaction Server.

2. Reproduce the problem.

   Record the specific steps that we used to reproduce the problem and any details that might be relevant.

3. Collect the following files from the Transaction server Docker container.

   • /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/config/com.ibm.commerce.inventory.external/wc-component-client.xml

   • /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/config/com.ibm.commerce.order/wc-admin-component.xml

   • /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/config/com.ibm.commerce.order-ext/wc-admin-component.xml

   • /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/config/wc-server.xml

   • /opt/WebSphere/AppServer/profiles/default/logs/server1/*.*

   • Sterling_installDir/logs/

   • Sterling_profileDir/logs/server/

4. Run the following database queries to collect the necessary information from the database (output results in CSV format).

   SELECT * FROM TRANSPORT
   SELECT * FROM CSEDITATT
   SELECT * FROM ISEDITATT
   SELECT * FROM PROFILE
   SELECT * FROM MSGSTORE
   SELECT * FROM ORDER WHERE ORDER_ID = <order_id>
   SELECT * FROM ORDSTAT WHERE ORDER_ID = <order_id>