APM Scenarios for SCIS

The following scenarios are a guide to using Application Performance Management (APM) results to improve SuiteCommerce InStore (SCIS) performance:

• Scenario A – Excessive time for a User Event Script

• Scenario B – Excessive time for a Workflow

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

• Scenario D – Excessive time for the SCIS & Others area

To view performance in APM:

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

2. Set filters to review the area of interest, such as a Date Range or Location that experienced a peak in the number of transactions. For more information, see SuiteCommerce InStore Performance Diagnostics.

3. Click Refresh.

4. Click an Action tile to display a time-duration graph covering the Date Range.

5. Point to the graph and click a point of interest to open the Action History. The history 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

• 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 workflows that run with the script to determine if they are the source of excessive runtimes.

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

   • If yes, contact the bundle owner and ask if the script is required to run 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 running in the SCIS WebApplication or Payment PostBack contexts.

To exclude a script by an SCIS execution context:

1. To exclude a script by an 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

The Custom Client Script URL Request run times display in a table after you navigate to Action > Graph > Action History Details. The table lists the total duration of each request.

To resolve the scenario:

1. Determine whether a user event script, workflow, or custom client script URL request is causing the excessively long times shown.

2. After you investigate, open a case with NetSuite Customer Support. Customer Support can review the script and recommend the appropriate actions. When creating the case, include the following:

   • 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 consumed by the SCIS application, including associated SuiteScript processing , displays in a table after you navigate to Action > Graph > Action History Details. The table lists the total duration of each request.

To resolve the scenario:

1. Determine whether a user event script, workflow, or custom client script URL request is causing the excessively long times shown.

2. If none of these processes are the cause, open a case with NetSuite Customer Support. Customer Support can review the application times and recommend the appropriate actions. When creating the case, include the following:

   • APM Action Tile name

   • Date and time from Action History Detail page

   • Log ID

   • Sample of duration times

Related Topics

• Application Performance Management (APM) for Commerce
• APM for Commerce Terminology
• APM for Commerce Prerequisites
• Installing APM for Commerce Features
• Granting Access to APM for Commerce Features
• APM for Commerce Dashboards
• APM for Commerce Action Performance
• APM Scenarios for SuiteCommerce

General Notices