Performance Tips for Network Resources

SuiteCommerce InStore (SCIS) administrators can make modifications to improve network performance in your SCIS environment. This topic lists a few tips that you should find helpful.

Use the Warming Up Service to keep the Server active

The warming up service keeps the NetSuite server “warm” while it is idle. The default is for the service to run every 10 minutes. If your store does not typically experience much idle time between making transactions, you should extend the warming up service interval to 30 or 40 minutes.

Extending the interval is especially important if you have several SCIS devices running at the same time. Having the service trigger every 10 minutes for multiple devices can have a negative impact on your server resources.

You configure the service interval by modifying the CustomConfiguration.js file.

            warmUp: {       
            //   warmUp : true,       
            //warmUpTime : 10 //in minutes    }, 

          

To adjust the Warming Up Service interval:

  1. Log into NetSuite as an administrator.

  2. Go to Documents > Files > File cabinet.

  3. Locate the CustomConfiguration.js file. In the index on the left, drill down to:

    Web Site Hosting Files > Live Hosting Files > SSP Applications > NetSuite Inc. - POS > SuiteCommerce InStore

  4. Click Edit for the file.

  5. Locate the warmUp: code section.

  6. Adjust the warmUpTime minutes.

  7. Save your changes.

Note:

Changing the interval to be less time, such as 1 minute, causes additional processing in the system that diminishes the purpose of the warm up service.

For more information, see Customizing the Configuration File.

If you do not use Client Scripts, clear the Execute Client Scripts option

The Execute Client Scripts setting on the SCIS Setting > Orders subtab enables the application to execute certain integration code as user event scripts. It is typically associated with using Avalara AvaTax.

Although the setting can improve performance under certain circumstances, it can also affect transaction-processing time. If you do not use Avalara, you should leave the Execute Client Scripts setting disabled.

Important:

Before clearing the check box, you might verify with Customer Support that your setup does not need the Execute Client Scripts option enabled.

To clear the Execute Client Scripts option:

  1. Log into NetSuite as an administrator.

  2. Go to Customization > Lists, Records, & Fields > Record Types.

  3. Scroll to SCIS Settings, and then click List in that row.

  4. Click Edit for the SCIS Settings record.

  5. Open the Order subtab.

  6. If the box is checked, clear the Execute Client Scripts box.

  7. Click Save.

For more information, see SCIS Settings for Orders.

Asynchronous Method for Adjusting the POS Status

When a payment or refund is made through a payment device, the transaction creates an Invoice record and changes the POS Status to Closed.

To ensure performance at the register, SCIS uses an asynchronous method to change the POS Status after the receipt becomes available. This method means that saved searches that include the POS Status might show a temporary status of Tendering for some transactions.

For purposes of ensuring the POS Status is correct, an asynchronous job runs every hour to adjust transactions that were not changed to Closed automatically. Support can set the job to run more frequently for your account, but be aware that additional job runs can have a negative impact on performance.

Note that the POS Status for transactions paid by cash and other tenders that do not use a payment device are not affected by the asynchronous method.

Related Topics

Performance Management and Tips for SCIS
Application Performance Management (APM) for SCIS
Performance Tips using NetSuite Settings
Performance Tips for using SCIS POS Devices
Performance Tips for Scripts and Workflows
Performance Tips for using Third-Party SuiteApps

General Notices