Create Your Oracle Content Management Instance

To create your Oracle Content Management instance you must be the primary account administrator or the account administrator must have set up your user account with the proper permissions.

To create your Oracle Content Management instance:

  1. If you're not already in the Oracle Cloud Console, navigate to it by returning to the window or signing in to Oracle Cloud.
  2. Make sure that the region that's selected in the menu in the top right of the Oracle Cloud Console is the one in which you want to create your instance.
  3. Click Navigation menu icon , click Developer Services, then, under Content Management, click Instances. This opens the Content Management Instances page.
  4. In the Compartment menu on the left, make sure you've selected the compartment you're using for Oracle Content Management.

    The compartment you created may not be available to you immediately. If you don’t see it, try again a little later.

  5. Click Create Instance.
  6. Enter the following information:
    Field Description
    Instance Name Specify a unique name for your service instance. If you intend to create multiple instances, make sure your instance name makes clear what the instance will be used for. If you specify a name that already exists, the system displays an error and the instance is not created.
    Description Optionally, enter a description of the instance.
    Compartment This is the compartment you previously selected. If you need to, you can change it.
    Notification Email Make sure this is the email address to which you want provisioning status updates to be sent.
    License Type Choose the type of license you want to use for this instance:
    • Premium Edition: Subscribe to a new full-featured Oracle Content Management license.
    • BYOL License*: Use your existing Oracle WebCenter Middleware license (BYOL).
    • Starter Edition: Subscribe to a feature-limited edition of Oracle Content Management.

    * The BYOL license type bills for assets at a discounted rate compared to an new Oracle Content Management license. To qualify for an Oracle Content Management BYOL license type your company must already own a qualifying on-premise WebCenter product license that is current on support maintenance. For more information please refer to the Oracle PaaS and IaaS Universal Credits Service Descriptions for a description of which WebCenter products qualify for BYOL licensing and for the conversion ratios for WebCenter processor licenses.

    License Options Optionally, enable additional license options. Enabling any of these options will add additional billing charges to your instance. Refer to your prepaid subscription contract or your Universal Credit contract for additional costs.
    • Advanced Hosting (not available for Starter Edition)—Advanced hosting configures an instance to use a dedicated Autonomous Transactional Database. Enabling this feature also allows the instance to support additional instance options such as disaster recovery (described below). To enable advanced hosting, select Advanced Hosting.


      You can't disable this option after the instance has been created.
    • Sales Accelerator—Oracle Sales Accelerator provides a one-stop shop for sales enablement content. It allows you to readily access a wide variety of information and resources that make selling your products and services easier.

      If you purchased an Oracle Sales Accelerator subscription, select Sales Accelerator.

    • Sauce VideoSauce Video is the video creation platform for teams. It provides a fast, easy, and affordable way to create video together anywhere, anytime.

      To enable Sauce Video for your instance, select Video Creation Platform.


      • If you're an Oracle SaaS customer, you must have purchased a Sauce Video subscription to see this option.
      • All Sauce Video Creation Platform data is stored in London, UK.
  7. If you need to enter additional details (for example, if you're creating a non-primary instance), click Show Advanced Options, and enter the following information:
    Field Description
    Instance Type (not supported in Starter Edition) By default, the instance type is primary (for example, your production instance). You must have at least one primary instance. If this instance is a non-primary instance (for example, for development or testing), select Non-Primary in the drop-down list. Primary and non-primary instances are billed at different rates.

    If this is a non-primary instance, you might want to include a tag to specify what the instance is used for.

    Upgrade Schedule (not supported in Starter Edition) Control whether your instance is upgraded immediately (as soon as a new release of Oracle Content Management is available) or on a delayed schedule (one release behind the latest release). For example, let's assume you have stage (non-primary) and production (primary) instances. You would set your stage instance to upgrade immediately and your production instance as delayed upgrade. This allows you to test the upgrade on the stage instance, making sure it doesn't interfere with any sites you've deployed. If you find any issues, you can report them to Oracle Support so they can be fixed before the upgrade is applied to your production instance.

    If you want to use this feature, but you don't see it, contact Oracle Support.

    Select one of the following options:

    • Upgrade immediately: Upgrade this instance as soon as a new release of Oracle Content Management is available.
    • Delay upgrade: Delay the upgrade of this instance, so that it is one release behind the latest release of Oracle Content Management.

    Once you create this instance, you can't change this setting.

    Instance Access Type (not supported in Starter Edition) Control whether your instance is accessible by public internet or through a dedicated private connection using Oracle Cloud Infrastructure FastConnect.

    If you want to use this feature, but you don't see it, contact Oracle Support.

    Select one of the following options:

    • Public: Select this option if you want your instance to be viewed over public internet.
    • Private: If you want to create a private instance that can be viewed only within your intranet, and you completed the prerequisite steps to set up Oracle Cloud Infrastructure FastConnect, select this option.

    Once you create this instance, you can't change this setting.

    Disaster Recovery (not available for Starter Edition) You must enable Advanced Hosting before you can select this option. Disaster recovery provides a full-stack orchestration of the service that includes comprehensive disaster recovery failover capabilities for all layers of the Oracle Content Management application stack, including the Oracle Content Management application tiers, database, search index, and object storage.
    Tags Optionally, add tags to categorize this instance with metadata. You can then filter your list of instances by tag.
  8. Click Create Instance.


If the creation of your service instance is not successful, contact Oracle Support.

After creating your Oracle Content Management instance, you're brought to the Content Management Instances page, where you'll see the status of your instance. The instance will take some time to be provisioned, and the page will update automatically to show the current status. The Oracle Content Management instance will be created in the region and compartment you selected, with the tags you entered, and an email will be sent to the notification email address you provided to let you know when the service instance is successfully created. When the instance is successfully created, you can click the instance name to view the details, then click Open Instance to open the Oracle Content Management web interface.

If you're an Oracle SaaS customer and you selected the Sales Accelerator license option, the required Sales Accelerator repository, publishing channel, taxonomies, and asset types are created along with your instance.

Required Compartment and Policies

During instance creation, there is a compartment and several policies that are automatically created. These are required for your instance to work properly. Do not delete them.

  • OCE_Internal_Storage_Policy—This policy allows Oracle Content Management to access object storage. It's automatically created and added to the root compartment and therefore applies to all compartments in the root compartment, including any new compartment you created for Oracle Content Management.
  • OCMIntegration compartment—This compartment is used for integration with OCI Vision and OCI Speech.
  • speechservice_auth_policy—This policy is used for letting Oracle Content Management make API calls to OCI Speech via service-to-service authentication.
  • aivisionprod_integration_policy—This policy is used for Oracle Content Management integration with OCI Vision and OCI Document Understanding.
  • mediaservices_integration_policy—This policy is used for Oracle Content Management integration with OCI Digital Media Services.
  • speechservice_integration_policy—This policy is used for Oracle Content Management integration with OCI Speech.

What to Do Next

After your service instance is successfully created, set up users and groups using IAM, or, if you installed Sales Accelerator, continue with the Sales Accelerator configuration, starting with customizing content categories.