1. Commerce
  2. System Management
  3. Application Performance Management (APM) for Commerce
  4. APM Scenarios for SCIS

APM Scenarios for SCIS

Use these scenarios as a guide for applying Application Performance Management (APM) results to boost SuiteCommerce InStore (SCIS) performance:

To view performance in APM:

  1. Go to Customization > SCIS Performance > SCIS Performance Diagnostics.

  2. Set filters for the area you want to review, like a Date Range or Location with a spike in transactions. For more information, see SuiteCommerce InStore Performance Diagnostics.

  3. Click Refresh.

  4. Click an Action tile to see a time-duration graph for your chosen Date Range.

  5. Hover over the graph and click a point of interest to open Action History, which shows a performance summary and Action History Detail tables.

Scenario A – Excessive time for a User Event Script

A user event script is taking an excessive amount of time.

Data in SCIS APM

  • Workflow run times appear in a table after you go to Action > Graph > Action History Details.

  • Use the Profiler Details links to investigate any events taking too long.

To resolve the scenario:

  1. Review workflows running with the script to see if they're causing long runtimes.

  2. Check if the script is from a third-party bundle.

    • If yes, contact the bundle owner and ask if it needs to run in the SCIS WebApplication or Payment PostBack contexts.

    • If the script isn't required in these SCIS contexts, use the Script Deployment page to exclude it from those contexts.

  3. Review customizations in your environment for possible issues.

    If a customization shouldn't run for SCIS, exclude the script from the WebApplication or Payment PostBack contexts using the Script Deployment page.

To exclude a script by an SCIS execution context:

  1. To exclude a script by SCIS execution context:

  2. Clear highlights for WebApplication and Payment PostBack.

  3. Click Save.

For more information, see Updating a Script Deployment.

Scenario B – Excessive time for a Workflow

A workflow running for a user event script is taking an excessive amount of time to complete.

Data in SCIS APM

  • The Workflow run times display in a table after you navigate to Action > Graph > Action History Details.

  • Use the links in the Profiler Details column to research an event with an excessive time.

To resolve the scenario:

  1. Review scripts that include the workflow to determine if they are the source of excessive runtimes.

  2. Determine if the workflow is from a third-party bundle script.

    • If yes, contact the bundle owner and ask if the script is required to execute in the SCIS WebApplication or Payment PostBack contexts.

    • If the script is not required in these SCIS contexts, use the Script Deployment page to exclude the script from those contexts.

  3. Review any customizations specific to your environment for potential problems.

    If the customization should not run for SCIS, use the Script Deployment page to exclude the script from executing in the SCIS WebApplication or Payment PostBack contexts.

To exclude a script by an SCIS execution context:

  1. Clear highlights for WebApplication and Payment PostBack.

  2. Click Save.

For more information, see Updating a Script Deployment.

Scenario C – Excessive time for a Custom Client Script URL Request

A custom client script URL request is taking an excessive amount of time.

Data in SCIS APM

Custom Client Script URL Request run times show up in a table after you go to Action > Graph > Action History Details, listing the total duration for each request.

To resolve the scenario:

  1. Figure out if a user event script, workflow, or custom client script URL request is causing the long durations.

  2. After you've checked, open a case with NetSuite Customer Support so they can review the script and suggest what to do. When you create the case, include:

    • APM Action Tile name

    • Date and time from Action History Detail page

    • Custom client script URL

    • Log ID

    • Sample of duration times

Scenario D – Excessive time for the SCIS & Others area

Excessively long times are showing for processes under the SCIS & Others area.

Data in SCIS APM

The time used by the SCIS application (including SuiteScript processing) is shown in a table after you go to Action > Graph > Action History Details, with the total duration for each request listed.

To resolve the scenario:

  1. Figure out if a user event script, workflow, or custom client script URL request is causing the delays.

  2. If none of these are the cause, open a case with NetSuite Customer Support so they can review the times and recommend next steps. When you create the case, include:

    • APM Action Tile name

    • Date and time from Action History Detail page

    • Log ID

    • Sample of duration times

Related Topics

General Notices