Sterling Web Store Customization Mustgather

1. Configure Environment

• Describe the problem you’re facing, with specific error message or query.
• Describe the steps to reproduce the problem, if possible please provide the step by step simulation with screen shots.
• Share implementation details for any UEs configured. Are there any UI based customizations done? If so, provide the details.
• Set the WUFAll along with the VERBOSE logs for the APIs in question.

Here's a video on how to set a verbose trace for an API.

2. Reproduce Problem and Capture Data

• Login to Sterling Web Store after clearing cookies and browser cache. Choose About > Help. Take a screen print (this screen illustrates version information including the fix pack details). Also capture the version and fix pack details from App Console.
• Collect the following details as you reproduce the problem –
• WUFAll verbose as well as verbose trace for all APIs in question.
• Launch the browser debugger and capture the error messages, if any, under error console. Take screenshot.
• Provide information on the actual and expected behavior with these steps.
• If the issue is related to difference in the actual and expected output from a mashup, get the API name, input and output template from that mashup’s definition and invoke the same API using APITester and compare the outputs. Are there any differences? If yes, the issue could be with Web Store implementation. Proceed further on this mustgather.
• If however, no difference is found, this may not be an issue due to customization but could be related to the way the underlying Foundation API works. In such case, refer to Sterling OMS mustgather, instead.
• If simulation requires extensive customization, zip your extensions directory, after removing other redundant code and retaining only relevant files related to the issue which might help in quick replication.
• In case some documentation was referred which led to the belief of feature not working as expected, provide reference to the same.
• Capture all screen shots from simulation.

3. Collect Data

• Gather environment level details:
• Collect all files and compress to one file using the PMR number such as 12345.999.000.zip
• If the compressed file is less than 5M then send via Ecurep e-mail @ sterling_support@ecurep.ibm.com
• If the compressed file is greater than 5M then send via Ecurep FTP
• Please see below section "Submitting Data to IBM Support" for more details.

---

To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:

• Service Request (SR)
• E-Mail
• FTP to the Enhanced Customer Data Repository (ECuRep)
• If the compressed file is less than 5M then send via Ecurep e-mail @ sterling_support@ecurep.ibm.com and enter the following in the subject line PMR 12345.999.000.zip
• If the compressed file is greater than 5M then send to Ecurep via FTP
• Please see below section "Submitting Data to IBM Support" for more details.