Publish Sites

Bring a Site Online or Take It Offline

When a site is online, users with proper access can view it with a standard web browser at a designated address (URL). When a site is offline, the site isn’t available for public viewing. You can view the site only in Oracle Content Management.

Before you can bring a site online, it must have been published. To publish the site, see Publish Site Changes.

The status icon on the right shows whether the site is online or offline:

If the site has never been published before, you see a dash (-).
If the site is online, you see .
If the site is offline, you see .

For information on who can access an online or offline site, see Understand Site Security.

To change the status of a site, you must be the site owner or have the manager role, or, if site governance is enabled, site administrators can change the status of any site regardless of whether or not the site is shared with them.

On the Sites page, select the site from the list.
To bring a site online or take it offline, choose Bring Online or Take Offline in the right-click menu. You can also click in the site tile to bring a site online, or click in the site tile to bring a site offline.
You’re prompted to confirm your choice.

When you bring a site online, a fully rendered HTML version of the site is created and copied to the hosting location in Oracle Cloud. An online site shows its URL below the site name. The format of the default URL is:

https://service_name.identity_domain.sites.oraclecloud.com/site_name

When you take a site offline, the site and its folders and files are removed from the hosting location in Oracle Cloud.

Publish Site Changes

To publish site changes, you must be the site owner or have the manager role.

Keep in the mind the following when you publish site changes:

When you publish changes to a site that's online, any committed changes are immediately visible to anyone with access to the site.
When you publish changes to a site, you can publish all assets targeted to the site's channel or just the assets that are used on the site pages, including recommendations. For example, if you publish all the assets targeted to the site's channel and the site includes a list that references content items that aren't directly part of the site, the referenced assets will also be published.
When you republish a site that has already been published, you can choose to republish only auxiliary files, such as a custom controller file or redirects, specific pages you select, or the entire site.
When you republish a site that has already been published, you can choose to publish site detail pages with assets, so that if site compilation is enabled, static HTML pages will also be generated and published.
When you publish changes to a multilingual site, only the translations for languages defined in the site’s associated localization policy will be published.
If translations have previously been published for languages that are no longer defined in the site’s associated localization policy, the translated content will be removed from the published site.
If you delete a page from a multilingual site, the translated pages will also be deleted when the site is published.

To publish site changes, select it and in the right-click menu or actions bar, choose Publish if this is the first time the site is being published, or Republish if the site has been published before. If republishing, you can select to republish the whole site, just pages you select, or just the auxiliary files. For example, if you configured the site with RSS feeds, redirects, or a custom controller file, you can publish them to the site runtime independently from publishing the whole site.
1. If republishing auxiliary files, select Publish Site Auxiliary Files from the Republish menu, choose what auxiliary files you want to publish, then click Publish.
2. If republishing individual pages, select Publish Site Pages, then choose the site pages you want to publish. Enable Show Updated Pages to list only those site pages that have been updated. If site compilation is enabled, static HTML pages will also be generated and published.
3. If republishing detail pages, select Publish Detail Pages with Assets, then click Select next to the detail pages with assets to publish. Navigate to and select the assets to include then click OK to add them. Click Publish. If site compilation is enabled, static HTML pages will also be generated and published.
4. If publishing or republishing the whole site, select whether to publish the site and all assets targeted to the site's publishing channel, or publish the site and all assets added to the site's pages.
By default, Oracle Content Management validates that all site strings and assets have the required approvals and translations. You won’t be able to publish the site if you don’t have the translations that are required by the site’s associated localization policy, if the assets aren’t marked as translated, or if an asset requires approval, but isn’t marked as approved. If Show site validation screen is enabled, a validation panel is displayed listing the assets and pages in the site that have any problems with validation. Expand items to see more details. If there are issues, correct them and then try to publish again. If all items are valid, click Publish.

If you want to see the full validation report, including assets that are ready for publication, enable Show complete validation report. Requesting a complete validation report can increase validation time. If you select Show issues only, the validation screen will show site pages and assets with Not Ready or Informational status only. This would speed up the time to render the validation screen.

Whether you accept the default validation or request a full validation report, if your site uses a large number of assets the validation process can take a long time to complete. For example, a site with 30,000 assets may take up to an hour to validate, and you won't be able to click Publish until it is done. Disable Show site validation screen to allow Oracle Content Management to automatically publish the site when the validation process has finished successfully. If for some reason the site doesn't validate successfully, a notification showing the reason is displayed on the Sites page and you can take the appropriate steps to correct any issues.
If your site isn’t already online (), you need to bring it online to make the site available to users.

View Site Publishing Job Details

You can view a list of publishing jobs by selecting View Jobs on the Sites page. Each job entry details the name and status of a job, when it was published and by whom. Click in the Publish Log or Content Log column to download a log file in JSON format.