URL Root Configuration for SSP Applications in NetSuite

The URL root for an SSP (SuiteScript Platform) application defines the base path leading to the application's assets. This path not only helps in organizing your application's resources but also ensures that asset requests are effectively routed.

What is the URL Root?

The URL root serves as the base URL from which all assets of an SSP application are accessed. It typically comprises the application publisher and application name. For instance, an SSP application named NextGenSite with the publisher SCA-NextGen will have a default URL root structured as: /SCA-NextGen/NextGenSite/.

Components of the URL Root

• Application Publisher: This is the entity that creates the SSP application. Each application must be uniquely named across all NetSuite accounts. By default, it aligns with your NetSuite account name.
• Application Name: This designates the folder containing all application assets including scripts, libraries, and images.

Note: If you are creating or modifying SSP applications using SuiteCloud Development Framework (SDF), utilize the SuiteApp application ID for your publisher name.

Flexible Configuration

NetSuite permits significant customization of the URL root beyond just the default publisher and application name. You can insert additional path components for improved organization and clarity. Ensure to follow these guidelines when creating your URL root:

• Allowable characters: letters, digits, dashes (-), and underscores (_).
• Forbidden characters: any others than those specified above.

It’s advised to have at least one distinct path component to differentiate SSP application assets from other root assets.

Unique URL Roots

Since Aconcagua and subsequent releases of SuiteCommerce and SuiteCommerce Advanced, it is crucial for each SSP application to have a unique URL root. Using identical URL roots across multiple SSP applications can cause operational confusion regarding which application is responsible for processing requests. If duplicate URL roots exist, consider the precedence sequence; this will determine which SSP application will handle incoming requests first.

Accessing Application Assets

To access assets for testing, navigate directly to the URL pointing to the application's entry script. For example:

http://www.example.com/SCA-NextGen/NextGenSite/index.ssp

Permissions Required

Ensure that you have SuiteScript permission to access and modify SSP application records within your NetSuite environment.

Creating Application Publishers and Folders

You can create an application publisher and an application folder when setting up the SSP application record or beforehand through the Web Site Hosting Files Folder in the File Cabinet. For additional guidance:

• Application Publisher Creation: Refer to guidelines for [View and Add Application Publishers].
• Application Folder Creation: See the documentation for [Create an SSP Application Folder].

Key Takeaways

• The URL root defines the access path for SSP application assets in NetSuite.
• It should include unique identifiers to avoid confusion among multiple applications.
• Follow character guidelines strictly when configuring the URL root.
• Always ensure adequate permissions are set for application access.
• Organization and clarity in URL structure enhance asset management and retrieval.