Configure Support for a Custom Domain

If you want your customers to see a different URL than the one generated by Visual Builder, you can map a custom domain, also called a vanity URL, to an app in your instance. A custom domain is a customer-provided hostname and domain (FQDN) created by adding a subdomain to your domain. After configuring an app to use a custom domain, app users accessing the app using the custom domain will not see the typical Oracle domain (for example, myvbinstance-accountname.builder.ocp.oraclecloud.com) in the URL, but instead would see something like mycustom.example.org.

To use a custom domain:

• Configure a custom endpoint in your Visual Builder instance, using the instructions in Create and Configure a Custom Endpoint.
• Select the custom endpoint in the visual application's Settings editor and publish the app. See Specify a Custom App URL in Developing Applications with Oracle Visual Builder.

Note:

Custom URLs are supported on Oracle Visual Builder instances, as well as on Oracle Integration instances. Depending on whether you're on Oracle Integration, Visual Builder, or a Visual Builder instance that was provisioned as part of a SaaS order, the process for enabling custom URLs varies. To enable a custom domain:

• For a Visual Builder Generation 2 instance, use the instructions in Create and Configure a Custom Endpoint.
• For a Visual Builder instance, where you have access to the OCI Console, you'll need to use the instructions in Configure Support for a Custom Domain in Administering Oracle Visual Builder in Oracle Integration 3.
• For a Visual Builder instance provisioned as part of a SaaS order, you might not have access to the OCI Console for configuring WAF. In this case, you'll need to use the instructions in Create Custom Domain for Visual Builder Instance Provisioned as Part of a SaaS Order in Administering Oracle Visual Builder in Oracle Integration 3.
• For a Visual Builder in Oracle Integration Generation 2 instance, use the instructions in Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration and Oracle Integration for SaaS, Generation 2.

After configuring a custom domain:

• Users can access a single web app by typing just the custom domain URL in the browser, for example, mycustom.example.org. The app is loaded from the custom domain root ("/"), and no additional path information or query parameters are required in the URL.
• http can be redirected to https, so if a user types "mycustom.example.com", this will resolve to https://mycustom.example.com, and load the default web app.
• For applications that contain business objects, the Business Object REST API can also use the custom domain configuration.
• Developers can access the Designer in Visual Builder using a custom domain.
• If you create and stage an application from a custom domain (https://mycustom.example.com/ic/builder/designer), you'll be automatically redirected to the custom domain (https://mycustom.example.com/ic/builder/rt/appid/version/...) when you open the app using a URL that isn't the application's custom domain (for example, your instance's URL https://servicename.oraclecloud.com/ic/builder/rt/appid/version/...).

Custom domains are also subject to some limitations:

• If the custom endpoint is selected as the Vanity URL in the application's Settings editor, after the app is published it can only be accessed from the custom domain root (for example, https://mycustom.example.com).
• If you publish a different web app in the same visual application, it immediately becomes the default app for the custom domain, and the previous web app will no longer be available at the custom domain.
• A custom domain can only be used to access one live app (in the visual application configured for the root URL). You can access other live apps in the same instance only by using the full Oracle Cloud URL, or by creating a different visual application and mapping it to a different custom domain.
• If a visual application contains more than one web app, only one of them can be accessed using the custom domain. It's not possible to specify which app in a visual application will be available at the custom domain because the domain is configured in the Settings for the visual application, not for individual web apps. If you are going to use a custom domain, it is recommended that the visual application only contain one web app to ensure that the correct app is loaded.