--- schema_version: "1" id: dd9c91df0f0abc67b6271694ba32f2f35536122feef2c2dbf58e74654b25b211 title: Using Anypoint Studio to Configure NetSuite REST Connector 1.0 collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/netsuite-rest-connector/latest/netsuite-rest-connector-studio.md canonical_url: https://docs.mulesoft.com/netsuite-rest-connector/latest/netsuite-rest-connector-studio source_site: docs.mulesoft.com content_type: documentation content_hash: 57194a2d6d409dda9c99d2de8c03b7f66300ef5766c3f0a2e7c91950877798a3 description: MuleSoft Documentation Site release: "1.0" latest: true --- --- product: NetSuite REST Connector version: 1.0 is-latest-version: true --- # Using Anypoint Studio to Configure NetSuite REST Connector 1.0 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt 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](#create-mule-project). 2. [Add the connector to your Mule project](#add-connector-to-project). 3. [Configure a source for the connector’s flow](#configure-source). 4. [Add a connector operation to the flow](#add-connector-operation). 5. [Configure a global element for the connector](#configure-global-element). 6. [Configure the other connector fields](#configure-other-fields). When you run the connector, you can view the app log to check for problems in real time, as described in [View the App Log](#view-app-log). If you are new to configuring connectors in Studio, see [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio). If, after reading this topic, you need additional information about the connector fields, see the [NetSuite REST Connector Reference](https://docs.mulesoft.com/netsuite-rest-connector/latest/netsuite-rest-connector-reference). ## Create a Mule Project In Studio, create a new Mule project in which to add and configure Anypoint Connector for NetSuite REST (NetSuite REST 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 REST 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 **Mule Palette**, click **(X) Search in Exchange**. 2. In **Add Dependencies to Project**, type `netsuite rest` in the search field. 3. Click **NetSuite REST Connector** in **Available modules**. 4. Click **Add**. 5. Click **Finish**. Adding a connector to a Mule project in Studio doesn’t make that connector available to other projects in your Studio workspace. ## Configure a Source A source initiates a flow when a specified condition is met. You can configure one of these sources to use with NetSuite REST Connector: - **On New Object** Polls NetSuite for records of a specified type that were created since the last poll and emits an event for each one found. - **On Modified Object** Polls NetSuite for records of a specified type that were created or updated since the last poll and emits an event for each one found. - **On Deleted Object** Polls NetSuite for deleted-record metadata and emits an event for each deletion found. - **HTTP Listener** Initiates a flow each time it receives a request on the configured host and port. - **Scheduler** Initiates a flow when a time-based condition is met. For example, to configure an **HTTP > Listener** source, follow these steps: 1. In **Mule Palette**, 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 the **HTTP > Listener** source in the app. 6. On the **General** tab, specify the connection information for the connector. 7. On the **TLS** tab, optionally specify the TLS information for the connector. 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 specified server. 10. Click **OK**. ## Add a Connector Operation to the Flow When you add a connector operation to your flow, you are specifying an action for that connector to perform. To add an operation for NetSuite REST Connector: 1. In **Mule Palette**, select **NetSuite REST Connector** and then select the operation to add. 2. Drag the operation onto the Studio canvas, next to the source. ## Configure a Global Element for the Connector When you configure a connector, configure a global element that all instances of that connector in the app can use. Configuring a global element requires you to provide the connection settings that the connector requires to access NetSuite. To configure the global element for NetSuite REST Connector: 1. Select the operation in the Studio canvas. 2. In the **General** configuration screen for the operation, click the **Add** icon to access the global element configuration fields. 3. In the **General** tab, in **Connection**, configure the [OAuth 2.0 Client Credentials (JWT Bearer)](#oauth-client-credentials) connection. You can reference a configuration file that contains ANT-style property placeholders (recommended), or you can enter your connection settings in the global configuration properties. For information about the benefits of using property placeholders and how to configure them, refer to [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview). 4. In the **Advanced** tab, optionally specify reconnection information, including a reconnection strategy. 5. Click **Test Connection** to confirm that Mule can connect with NetSuite. 6. Click **OK**. ### OAuth 2.0 Client Credentials (JWT Bearer) Use the OAuth 2.0 client credentials connection to authenticate with a JWT bearer assertion signed by a private key that is registered against a certificate in NetSuite. Enter this information in the **General** tab of the **Global Element Properties** screen to configure the connection:
FieldUser Action

Name

Enter the configuration name.

Account ID

Enter the NetSuite account ID (for example, TSTDRV1234567 or 1234567_SB1).

Client ID

Enter the OAuth 2.0 client ID from the integration record in NetSuite.

Certificate ID

Enter the certificate ID (kid) registered in NetSuite for JWT signing.

Private Key (PEM)

Enter the PEM-encoded private key that matches the registered certificate. Supply this value through a secure property.

Signature Algorithm

Select the JWT signing algorithm: ES512 (recommended), ES256, ES384, PS256, PS384, or PS512. The algorithm must match the key type of the registered certificate.

Token Object Store

Optionally specify an object store for OAuth token persistence across cluster nodes. When unset, a persistent, config-name-keyed store is created automatically.

In the **Advanced** tab, you can optionally configure timeouts, maximum connections, a proxy, a concurrency management strategy for HTTP 429 and 503 responses, and reconnection behavior. ## Configure Additional Connector Fields After you configure a global element for the connector, configure the other required fields. The required fields vary depending on which connector operation you use. For detailed configuration information for each operation type, see [NetSuite REST Connector - Additional Configuration Information](https://docs.mulesoft.com/netsuite-rest-connector/latest/netsuite-rest-connector-additional-config). ## View the App Log To check for problems, you can view the app log as follows: - If you’re running the app from Anypoint Platform, the app log output is visible on the Anypoint Studio console window. - If you’re running the app using Mule from the command line, the app log output is visible in your operating system console. Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the app log in the default location `MULE_HOME/logs/.log`. You can configure the location of the log path in the app log file `log4j2.xml`. ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Using Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio) - [NetSuite REST Connector Reference](https://docs.mulesoft.com/netsuite-rest-connector/latest/netsuite-rest-connector-reference) - [Salesforce Help](https://help.salesforce.com)