SSP Application Structure in SuiteCommerce and SuiteScript

TL;DR Opening

SSP applications are integral to creating dynamic web content for SuiteCommerce. They use SuiteScript to run server-side logic, providing a robust foundation for customizing web stores.

What is SSP?

SuiteScript Server Pages (SSP) serve as a custom web application platform designed for building applications within Commerce web stores. By leveraging SSP, developers can create front-end pages that execute server-side SuiteScript for generating dynamic content, similar to the JavaServer Pages (JSP) technology but tailored for SuiteScript.

Key Components of SSP Applications

An SSP application is structured around the following components:

• .ssp Files: These files handle the front-end display and can generate a variety of website elements, from banners to full web pages. They distinctly manage presentation and dynamic content generation while interacting with backend services.
• .ss Files: Dedicated to backend logic, these files handle server-side operations and are usually structured with one file per service.

Entry Points for SSP Applications

Entry points, or touch points, dictate how users interact with an SSP application. These are defined differently based on the version of SuiteScript being utilized:

• SuiteScript 1.0: Multiple entry points can be defined as 'Supported Touch Points' on the application record, such as View Homepage or Log In. Each of these corresponds to a specific area of the web store.
• SuiteScript 2.0: A single default SSP file acts as the entry point, which simplifies the interface for end-users and developers alike.

Organizing SSP Applications

All files associated with an SSP application are grouped by the publisher and stored together in a Web Site Hosting files folder within the NetSuite file cabinet. This organization facilitates easy management and access of resources.

Hosting and Customization

Both Site Builder and Commerce websites can utilize the SSP feature. This allows for a cohesive experience where assets of the Commerce web store can be bundled and customized via SSP applications. Developers can link their SSP applications directly to their websites.

Important Considerations

When developing SSP applications, keep in mind:

• You cannot mix SuiteScript 1.0 and SuiteScript 2.0 files within the same SSP application.
• SSP applications utilize AJAX calls for dynamic interactions.
• All SuiteScript 1.0 SSP applications can be viewed without requiring a user login, while SuiteScript 2.0 applications must be deployed to a domain before being accessible.

Summary of Functionality

In summary, SSP applications provide a versatile way to enhance Commerce web stores through tailored web elements and seamless dynamic content. Developers can efficiently manage these applications for diverse user touch points, enabling a highly customizable eCommerce experience.

Who This Affects

The information in this article is relevant for:

• Developers: Who are tasked with building and managing SSP applications.
• Web Administrators: Required to deploy and maintain SSP applications.
• E-commerce Managers: Interested in customizing customer experiences on their web stores.

Key Takeaways

• SSP applications utilize both .ssp and .ss files for dynamic web functionality.
• The entry point methodology differs by SuiteScript version, impacting how applications are structured.
• SuiteScript 1.0 applications allow non-logged users, while SuiteScript 2.0 needs explicit deployment for access.

Source: This article is based on Oracle's official NetSuite documentation.