NetSuite Changelog
CommerceCustomizationConfigurationHow-To

Changing Site Management Tools HTML Hosting Root Configuration

Change the HTML Hosting Root for Site Management Tools to ensure content displays correctly by following key configuration steps.

·3 min read·View Oracle Docs

When you create a website in NetSuite, the HTML Hosting Root is set in the Website Setup record. Site Management Tools (SMT) rely on this same HTML Hosting Root for proper functionality and content display. Should you need to relocate your site to a different HTML hosting root, a new CMS SSP application must be created to maintain seamless operation.

Steps to Configure SMT with a Different HTML Hosting Root

To successfully reconfigure SMT to operate with a new HTML hosting root, follow these steps:

  1. Publish Unpublished Changes: Ensure all unpublished changes to your site are published to prevent any loss of updates. For more information on this process, consult the documentation on creating and publishing content in Site Management Tools.

  2. Copy the SSP Application:

    • Create the necessary directories in your file cabinet (e.g., Custom Hosting Root/SSP Applications).
    • Duplicate your existing SSP application into the newly created SSP Applications folder.
    • Establish a new SSP application record that points to this duplicated application. Refer to the guidelines on creating SuiteScript 1.0 SSP application records for assistance.

  3. Copy the CMS Folder: Transfer the NetSuite Inc. - CMS folder to the Custom Hosting Files/SSP Applications directory in your file cabinet. Note: The folder name must remain NetSuite Inc. - CMS—renaming it will cause issues.

  4. Create a New SSP Application Record:

    • Utilize the original SSP application as your template for creating this new record.
    • Name the application uniquely and provide a description that will clarify its purpose.
    • Set the Application Folder to Custom Hosting Root: /SSP Applications/NetSuite Inc. - CMS/CMS.
    • Specify the URL Root as /CMS.

  5. Modify the Website Setup Record: Alter the Default Hosting Root to point to Web Site Hosting Files: Custom Hosting Files.

  6. Link New SSP Application: Attach the new SSP application record to your website.

  7. Clear Website Cache: This is important to prevent cached versions from being displayed to visitors.

  8. Log into Site Management Tools: This step is crucial to start using the new setup.

  9. Publish Test Content: Add a simple text content to any page on your site and publish to ensure everything works correctly.

  10. Revert Test Content: Once you've confirmed proper functioning by checking the published content, remove this test content and publish the change again to clean up your site.

Important Considerations

  • Be vigilant about naming conventions for folders and applications as deviations can lead to functional disruptions in your site setup.
  • Frequent checks after publishing changes can prevent caching issues that may arise during switching of hosting roots.

Conclusion

Following these steps ensures that your Site Management Tools will continue to function effectively after changing the HTML hosting root, allowing for an uninterrupted user experience for your website visitors.

Related Topics

  • Site Management Tools Configuration
  • Site Management Tools Templates and Areas

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

Frequently Asked Questions (4)

Does changing the HTML Hosting Root affect existing SSP applications?
Yes, changing the HTML Hosting Root requires creating a new CMS SSP application to ensure the Site Management Tools function properly, as the application needs to point to the new HTML hosting structure.
What steps are necessary after copying the CMS folder to ensure proper functionality?
After copying the CMS folder, ensure it remains named 'NetSuite Inc. - CMS', create a new SSP application record pointing to this folder, and set the URL Root to '/CMS'.
Is there a specific order in which site configuration steps should be completed when altering the HTML Hosting Root?
Yes, follow the sequence: publish changes, duplicate the SSP application, copy CMS folder, create and link a new SSP application record, modify the Website Setup Record, clear the cache, log into Site Management Tools, and test with content publishing.
What precautions should be taken to prevent issues when reconciling Site Management Tools with a new HTML Hosting Root?
Ensure proper naming conventions are followed for folders and applications to avoid disruptions, and frequently check for caching issues by publishing changes regularly.
Source: Changing Site Management Tools to Use a Different Hosting Root — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Commerce

View all Commerce articles →