Contact Us 1-800-596-4880
  1. Homepage
  2. NetSuite Connector (10.0)

  3. Using Anypoint Studio to Configure NetSuite Connector

All Connectors

Using Anypoint Studio to Configure NetSuite Connector

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and configuration files.

To add and configure a connector in Studio:

  1. Create a Mule project.

  2. Add the connector to your Mule project.

  3. Configure an input source for the connector’s flow.

  4. Add a connector operation to the flow.

  5. Configure a global element for the connector.

If you are new to configuring connectors in Studio, see Using Anypoint Studio to Configure a Connector. If, after reading this topic, you need additional information about the connector fields, see NetSuite Reference.

Create a Mule Project

In Studio, create a new Mule project in which to add and configure the connector:

  1. In Studio, select File > New > Mule Project.

  2. Enter a name for your Mule project and click Finish.

Add the Connector to Your Mule Project

Add NetSuite Connector to your Mule project to automatically populate the XML code with the connector’s namespace and schema location and add the required dependencies to the project’s pom.xml file:

  1. In the Mule Palette view, click (X) Search in Exchange.

  2. In Add Modules to Project, type netsuite in the search field.

  3. Click the connector name in Available modules.

  4. Click Add.

  5. Click Finish.

Adding a connector to a Mule project in Studio does not make that connector available to other projects in your Studio workspace.

Configure an Input Source

An input source initiates a flow when a specified condition is met. You can configure one of these input sources to use with NetSuite:

  • HTTP Listener, which initiates a flow each time it receives a request on the configured host and port

  • Scheduler, which initiates a flow when a time-based condition is met

For example, to configure HTTP Listener, follow these steps:

  1. In the Mule Palette view, select HTTP > Listener.

  2. Drag Listener to the Studio canvas.

  3. On the Listener configuration screen, optionally change the value of the Display Name field.

  4. Specify a value for the Path field.

  5. Click the plus sign (+) next to the Connector configuration field to configure a global element that can be used by all instances of HTTP Listener in the app.

  6. On the General tab, specify connection information.

  7. On the TLS tab, optionally specify TLS information.

  8. On the Advanced tab, optionally specify reconnection information, including a reconnection strategy.

  9. Click Test Connection to confirm that Mule can connect with the specific server.

  10. Click OK.

Add a Connector Operation to the Flow

When you add a connector operation to your flow, you immediately define a specific operation for that connector to perform.

To add an operation for NetSuite, follow these steps:

  1. In the Mule Palette view, select NetSuite and then select the desired operation.

  2. Drag the operation onto the Studio canvas to the right of the input source.

Configure a Global Element for the Connector

When you configure a connector, it’s best to configure a global element that all instances of that connector in the app can use. Configuring a global element requires you to provide the authentication credentials the connector uses to access the target NetSuite system.

To configure the global element for NetSuite Connector, follow these steps:

  1. Select the name of the connector in the Studio canvas.

  2. In the configuration screen for the operation, click the plus sign (+) next to the Connector configuration field to access the global element configuration fields.

  3. On the General tab, select an authentication mechanism and configure it as described:

    • Request-Based Authentication

    • Token Authentication

      To configure NetSuite authentication, you must have the account ID for SuiteTalk NetSuite Web Services, which you can find within the NetSuite sandbox UI under Setup > Integration > Web Service Preferences.

  4. On the Advanced tab, optionally specify reconnection information, including a reconnection strategy.

  5. Click Test Connection to confirm that Mule can connect with the specified server.

  6. Click OK.

Request-Based Authentication

Use this strategy to send user credentials in the SOAP header of each request instead of authenticating to NetSuite by invoking login.

request based authentication

+

Parameter Description

Name

Name for the configuration to reference in subsequent configurations of NetSuite Connector instances

Email

Email used to log in to the NetSuite UI

Password

Corresponding password to log in to the NetSuite UI

Account

Account ID for SuiteTalk NetSuite Web Services

Role Id

Role ID for the user in SuiteTalk, which determines the processor privileges

Application Id

Application ID corresponding to the integration record to use

Token Authentication

With token authentication, you authenticate by using either a consumer key and token ID or by using secret pairs, which are established within the NetSuite environment.

The following screenshot shows an example of configuring token authentication:

request based authentication

+

Parameter Description

Consumer Key

Consumer key value for the token-based authentication-enabled integration record to use

Consumer Secret

Consumer secret value for the token-based authentication-enabled integration record to use

Token ID

Token ID that represents the unique combination of a user and an integration record that is generated within the NetSuite environment

Token Secret

Respective token secret for the user and an integration record pair

Account

Account ID for SuiteTalk NetSuite Web Services

Signature algorithm

Type of HMAC signature algorithm

Next Steps

After configuring Studio, see the Examples topic for more configuration ideas.

See Also

Back to top
View on GitHub