Configure Sites and Assets Settings

You can specify who can create, share, and use sites functionality, which lets users design, build, publish, and manage websites that are hosted in Oracle Cloud.

Sites functionality in Oracle Content and Experience unites content, collaboration, and creativity in one user interface. You can seamlessly grab and reuse content to build sites, your site content is kept under control, and shared content makes collaboration between and among groups easier than ever.

From the Sites and Assets page, you can perform the following actions:

Allow Sites to Be Created

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. Next to Allow sites to be created, select Enabled to allow your service users to create sites. When you enable the ability to create sites, you allow all users to create templates and sites.

    If you disable site creation, users can still see and work with templates and other folders in the hierarchy. Users can also still work with an existing site if the site is shared with them. They can view, edit, and manage the site, depending on their role.

    When you enable sites functionality, users have the ability to publish any content they have access to, including confidential information. You might want to limit your users to creating only secured sites, so that users have to sign in before they can see the site content. For even more security, you can limit site creation to administrators.

See Creating and Managing Sites in Building Sites with Oracle Content and Experience.

Enable Governance for Sites

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. Next to Enable governance for sites, select Enabled to simplify and accelerate site delivery for business users, who are not site administrators, while giving site administrators an easy way to control and track sites from a centralized location.

    With Governance enabled:

    • Developers can populate a template catalog with a set of site templates for the needs of different lines of business. They can apply policies regarding the type of security new sites must adhere to as well as whether new sites require approval.
    • Business users have the ability to rapidly request new sites with required approvals and automated provisioning,
    • Site administrators can manage all sites from one place regardless of who created and deployed the site. They can monitor site status and change status for any deployed site.
    See Understand Site Governance in Building Sites with Oracle Content and Experience.

Set Minimum Security for Online Sites

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. Next to Minimum security for online sites, choose one of the following options from the drop-down list:
    • Specific service users—Only selected service users (the default setting)

      Only authenticated users who are explicitly selected as members can access the published site. You can further limit the selected users to only Oracle Content and Experience users.

    • Specific cloud users—Only selected cloud users
    • Service users—All service users

      Only authenticated service users, standard users, or enterprise users can access secure sites. This excludes authenticated visitors.

    • Cloud users—All cloud users who can sign in to your domain.
    • Everyone—Anyone without signing in

    For information about specifying who can access public sites, see Changing Site Security in Building Sites with Oracle Content and Experience.

Allow Sharing of Sites and Themes

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. Next to Allow sharing of sites and themes from UI, select Enabled to allow users to share sites and themes with other Oracle Content and Experience users.

    If you disable sharing, users can still create and publish themes and sites. Users with the manager role for the theme or site (the owner or an administrator) can edit or publish the theme or site.

    If you disable sharing, users won't be able to share sites and themes through the user interface. It’s still possible to implement sharing of theme and site folders using the Oracle Cloud REST API for Content Management. See Developing for Oracle Content and Experience.

Limit Site, Template, or Component Creation to Site Administrators

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. Next to Only site administrators can create sites, select Enabled to restrict the ability to create sites to users with the site administrator application role.
  4. Next to Only site administrators can create templates, select Enabled to restrict the ability to create templates to users with the site administrator application role.
  5. Next to Only site administrators can create components, select Enabled to restrict the ability to create components to users with the site administrator application role.

Add Analytics Tracking Code to Sites

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. Optionally, add JavaScript tracking code to sites for web analytics tracking, making it easier to integrate with external analytics providers like Google, Adobe, or Oracle Infinity. Adding a snippet here will propagate it to all new sites and pages. You can also add the snippet to directly to individual sites or pages or customize the propagated snippet as necessary.

    Click Edit, then add a web analytics tracking snippet like the following one for Google Analytics:

    <!--Global site tag (gtag.js - Google Analytics -->
    <script async src="https://www.googletagmanager.com/gtag/js?id=UA-85172963-3"></script>
    <script>
    window.dataLayer = window.dataLayer || O:
    function gtag0{dataLayer.push(arguments);}
    gtag('js', new Date0;
    
    gtag('config', 'UA-85172963-3'):
    </script>

    Click Done, and then click Save.

    The tracking snippet here will be available in a site's settings, but a site manager must enable the snippet on the site, publish the change, and, if necessary, bring the site online before analytics are collected for that site. Site managers can also customize the snippet in the site settings or page settings.

    After the site manager publishes the site and brings it online, you can view the tracked analytics data on the vendor’s site, such as Google Analytics. If you used a snippet for Oracle Infinity analytics tracking, go to the Oracle Infinity home page and click Analytics to view the data and select or create reports.

Set Custom Cache Control Headers for Compiled Sites

If your company uses compiled sites, you can set custom cache control headers that will be used by default for any compiled sites created on your instance.

By default, compiled sites are cached on a user's browser for 300 seconds (5 minutes). However, you can change this default for your instance through the administrative settings. Site developers can also change the settings for a specific site in the site properties.

To change the default cache settings for compiled sites, perform the following steps:

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. To change the default cache settings for compiled sites, edit the values shown below in bold. Values are in seconds.
    Cache-Control: max-age=300
    Edge-Control: !no-store,max-age=2592000,downstream-ttl=1800
    • Cache-Control determines how long a page is cached on a user's browser. The default is 300 seconds (5 minutes).
    • Edge-Control is an Akamai-specific setting. If your instance doesn't use Akamai, this setting has no effect.
      • !no-store indicates that this setting should override the corresponding Akamai caching configuration for the property.
      • max-age determines how long Akamai should cache this page. The default is 2592000 seconds (30 days). During that time, Akamai will fulfill requests for the page without requesting the page from Oracle Content and Experience.
      • downstream-ttl tells Akamai to send a “Cache-Control: max-age” header with its response to client browsers, instructing those browsers to cache the page for the alotted time. The default is 1800 seconds (30 minutes).

    After changing the settings, click Save.

    To return to the default values, click Show defaults, and then click Save.

Set a Compilation Endpoint URL

If you're using a Site Compilation Service, you need to register the compilation endpoint URL with Oracle Content and Experience so that sites can be compiled when they're published.

For details on setting up the Site Compilation Service, see Set Up a Site Compilation Service in Integrating and Extending Oracle Content and Experience.

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. In the Compilation Endpoint URL box, enter the fully-qualified URL you want to be registered with the server.

Automatically Handle Expired Sites

If site governance is enabled, you can have expired sites automatically taken offline and even deleted.

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. Under Site Expiration, if you want sites to be taken offline automatically when they expire, enable Automatically take expired sites offline.
  4. If you also want expired sites to be deleted, enable Automatically delete expired sites, and enter the number of days you want to wait before they're deleted.

    You can see the list of deleted sites by clicking Sites in the navigation menu, then selecting Trash from the Sites menu.

See Understand Site Governance in Building Sites with Oracle Content and Experience.

Install Default Site Templates

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. If you want to install a set of default site templates to help your users get started building their own sites, click Install default site templates.

    This option installs the templates shipped with Oracle Content and Experience. If this is the first time you have installed the templates, new folders are created for the template, its associated theme, and any custom components included in the template. If these templates were installed previously, installing them again will overwrite the associated template, theme, and custom component files, including any sharing settings you have set. After you install the templates, share the templates with the intended users.

    Until you share a template, it can’t be used by anyone else. When you share a template with users for the first time, the associated theme and any associated custom components are automatically shared with the identified users, who are given the Downloader role for the theme and components to ensure that they are available if the users create sites from the template. Subsequent changes in the template to the role for one or more users do not update the sharing information for the associated theme or custom components.

Set Maximum Renditions Per Asset

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. Under Assets, configure the Maximum number of custom renditions per asset. The default is 20.

Set Maximum Video File Size

  1. After you sign in to the Oracle Content and Experience web application as an administrator, click System in the Administration area of the navigation menu.

  2. In the System Settings drop-down menu, choose Sites and Assets.
  3. Under Assets, configure the Maximum video file size (in MB). The default is 200 megabytes.

Enable Custom Sign-In

By default, Oracle Identity Cloud Service (IDCS) comes with an embedded sign-in page. IDCS provides a way of customizing the sign-in page. However, if you need to personalize the look and feel of the sign-in page beyond what the branding feature supports, IDCS provides an Authentication API that enables you to develop your own customized sign-in page.

Oracle Content and Experience provides a custom sign-in feature that enables you to use a site page as a custom sign-in page. Once configured, this will become the sign-in page for Oracle Content and Experience and all secure sites.

Note:

The custom sign-in feature is available only in Oracle Content and Experience instances that are running on Gen 2 Oracle Cloud Infrastructure (OCI) natively (that is, using Infrastructure Console to manage service instances).

The starter template comes with a sample sign-in page with a custom sign-in component to help you get started.
Starter template custom sign-in page

Steps to Use Custom Sign-In

Here’s an overview of what you need to do:

  1. Create a public site from the starter template.
  2. Use Site Builder to edit the site’s sign-in page.
  3. Publish the custom sign-in site and bring it online.
  4. Enable custom sign-in in the administrative user interface (described below).

Enable Custom Sign-In

After your site is published and online, you need to enable it for custom sign-in.

  1. If you’re not already signed in as a user that has access to the System administration, sign in to Oracle Content and Experience as an administrator.
  2. Click System in the Administration area of the navigation menu.
  3. In the System Settings drop-down menu, choose Sites and Assets.
  4. Under Custom Login Screen, click Enabled, select the site and page you created for custom login, and then click Save.

    Important:

    Make sure you select the correct page. If you sign out or your session ends, you won’t be able to sign in directly to Oracle Content and Experience again. You’ll need to sign in to Oracle Cloud, and then navigate to your Oracle Content and Experience instance. Then you can go back to the Sites and Assets page and correct the issue.

Once you configure the custom sign-in page, the associated site can’t be taken offline or unpublished.

You’ll probably want to inform your users that they’ll see a new sign-in page, so they don’t worry that it’s a phishing scheme or something similar.

Reset Custom Sign-In

You can reset the sign-in page to the one that comes out-of-the-box with Oracle Identity Cloud Service (IDCS) in the following ways:

  • From Oracle Content and Experience:
    1. If you’re not already signed in as a Service Administrator user (a user that has access to the System administration), sign in to Oracle Content and Experience as an administrator.
    2. Click System in the Administration area of the navigation menu.
    3. In the System Settings drop-down menu, choose Sites and Assets.
    4. Under Custom Login Screen, click Disabled, and then click Save.
  • If you can’t sign in to Oracle Content and Experience because the sign-in page was configured incorrectly, you can reset the sign-in page in one of two ways:
    • If you sign in to Oracle Cloud Infrastructure (OCI) using single sign-on (SSO), follow these steps to reset the sign-in page:
      1. Navigate to the Infrastructure Console. For example, the Ashburn datacenter console is as https://console.us-ashburn-1.oraclecloud.com/.

        Enter your tenant name, and click Continue.

      2. On the Sign In page, under Single Sign-On (SSO), make sure the appropriate identity provider is selected, and click Continue.
      3. On the IDCS sign-in page, enter the user name and password for the Service Administrator user (a user that has access to the System administration in Oracle Content and Experience), and click Sign In.
      4. In the Infrastructure Console, click Navigation menu icon to open the navigation menu, expand Application Integration, and click Content and Experience. This opens the Content and Experience Instances page.
        Infrastructure Console - Content and Experience option
      5. In the Compartment menu on the left, select the compartment for your Oracle Content and Experience instance.
        Content and Experience Instances page with Compartment selection

      6. Click your service instance to open it.
      7. Click Open Instance. This opens your Oracle Content and Experience instance without the need to sign in.
        Open Instance button

      8. Click System in the Administration area of the navigation menu.
      9. In the System Settings drop-down menu, choose Sites and Assets.
      10. Under Custom Login Screen, click Disabled, and then click Save.
  • If you don’t sign in to OCI using SSO, open a support ticket with Oracle Support to reset the sign-in page.