Managing NetSuite Concurrent Connections and ShipHawk Performance

As a NetSuite administrator, you can manage and monitor the number of concurrent connections your NetSuite implementation can use for integrating with other applications, including ShipHawk.

NetSuite limits the number of concurrent API connections that you are allowed based on your service tier. For more information, see NetSuite’s Concurrency Governance Cheat Sheet.

The number of concurrent connections (operations) available for an integration is an important consideration for overall performance. For ShipHawk, the more concurrent connections available, the faster ShipHawk can write back shipment information to NetSuite and update Item Fulfillment records.

In NetSuite, the number of concurrent connections is shown in the Account Concurrency Limit field, and also on the Concurrency Monitor and Integration Governance screens. You can now configure the number of concurrent connections ShipHawk will use with your NetSuite implementation in the Concurrency Rate Limit field. The Concurrency Rate Limit setting in ShipHawk must be less than or equal to the Account Concurrency Limit field in NetSuite.

Monitoring Concurrency Performance

You can view concurrency performance in NetSuite with the Concurrency Monitor, and review concurrency usage for integrations on the Integration Governance screen. For example, you might have a NetSuite Basic service tier that allows for five concurrent connections, or you might have a higher service tier that allows for more connections. As a NetSuite administrator, you need to identify the service tier that best meets your overall business and performance requirements.

Account Concurrency Limit in NetSuite

In NetSuite, the Account Concurrency Limit setting defines the number of concurrent operations that can be performed for each integration. For example, if your Account Concurrency Limit is set to three and you book five shipments in ShipHawk, NetSuite will only create the first three Item Fulfillment records simultaneously. The two remaining records will not be created until the first three records were successfully created.

To check the current value of the Account Concurrency Limit in NetSuite:

Select Setup > Integration > Integration Governance.
Note the Account Concurrency Limit field value. This value should be greater than or equal to the Concurrency Rate Limit value you can set in ShipHawk.

Rate Limiting in ShipHawk

On the ShipHawk web portal, you can specify the number of connections that ShipHawk uses to connect to NetSuite in the Concurrency Rate Limit field:

Select (Settings) > Integrations.
Click the NetSuite tile for NetSuite Manage Your Accounts.
Select Advanced tab and go to the Rate Limiting section:
In Concurrency Rate Limit, enter a value that is less than or equal to the Account Concurrency Limit in NetSuite.