Manage websites

A website is the core entity of portals application. A portal application selects a single Website record, and this determines what portal entities – web pages, web files, web roles, content snippets, etc. – are applicable to this application.

With a website providing an application scope, multiple distinct portal applications can be connected to a single organization.

Note

Determination of which website record a given portal application is bound to is usually by the website's name, specified in the configuration of the portal deployment. However, it is also possible to control this by URL path prefix (see the descriptions of Parent Website and Partial URL under website attributes), or by domain, using website bindings.

Manage websites

Websites are created when you create a new portal. However, advanced website management can be performed from the Portal Management app.

Warning

When you delete a website record, data related to the website record in portal metadata entities, such as webpages and web links, is also deleted. This is generally the desired behavior, as it means an entire website and all its related data can be removed from an organization in a single operation.

  1. Open the Portal Management app.

  2. Go to Portals > Websites.

  3. To edit an existing website, select the website name.

  4. Enter or edit appropriate values in the fields.

  5. Select Save & Close.

Website attributes

Name Description
Name The descriptive name of the website. This field is required.
Primary Domain Name The primary domain name of the portal to which this website record will be added.
Parent Website The parent website of the website. This field can generally be ignored, except in certain advanced portal configurations in which a single portal application is bound to one master website at the application root path, with one or more child websites available at specific sub-paths.
Partial URL The root URL path segment for all URLs generated for portal entities related to this website.
For example, if a portal application is deployed to be available at the root of the domain example.com, and this attribute has no value, a request to http://example.com/ will render the Home web page of the application website (as the Home web page is required to have its Partial URL set to "/").
If this attribute is set to the value "my-website", the Home Web Page will instead have a URL of http://example.com/my-website/, and all pages in the website will have the same "/my-website/" path prefix.
In most portal configurations, this field can be ignored and left blank.
Partial URL values are used as URL path segments. As such, they should not contain illegal URL path characters, such as "?", "#", "!", "%". Since portal URLs are generated by joining together Partial URL values with slashes ("/"), they should also not generally contain slashes.
Recommended practice would be to restrict Partial URL values to letters, numbers, and hyphens or underscores. For example: "press-releases", "Users_Guide", "product1".

See also

Website bindings