2 Manage Instance Settings

After a Visual Builder instance is created, users with the role of Visual Builder Administrator can manage and set global options for applications in the instance and create associations between the instance and other services.

Manage Applications in the Service Instance

An Oracle Visual Builder administrator can manage any application in the service instance and does not need to be a team member to see an application on the Home page. Administrators can perform all the tasks of a developer, including adding and removing team members, and opening, staging and publishing applications.

The Home page displays a list of the applications in the service instance. Developers can only see and manage an application when they are a member of the application’s team. Administrators can select the Administered by me checkbox next to the Status dropdown list if they want the list of applications to include all the applications in the instance, even the applications where they are not a team member. The checkbox is not visible to developers who do not have the role of administrator.



Note:

On the Home page for classic applications, administrators can select the Applications I administer checkbox in the Filter by pane to display the applications where they are not a team member.


Description of admin-homepage1.png follows
Description of the illustration admin-homepage1.png

Access Instance Settings

Administrators can access a page for managing the instance’s global settings. The settings page contains panels for configuring security settings, specifying Access Denied messages and specifying Oracle Process Cloud Service details.

You can access the instance settings page from any Visual Builder page, but the steps for opening the page will depend on if you are developing visual applications or classic applications.

To open an instance’s settings page:

  1. Click Home in the Visual Builder title bar to open the main menu.
  2. Click Settings in the main menu.

    If you are developing visual applications, open the main navigation pane on the Home page and select Settings.


    Description of admin-settings-menu.png follows
    Description of the illustration admin-settings-menu.png

    If you are developing classic applications, select Administer Visual Builder in the Administration Options menu and then click Global Settings.


    Description of admin-options-menu.png follows
    Description of the illustration admin-options-menu.png
The settings available for the instance are grouped on the page. Description of admin-instance-tenant-settings-oic.png follows
Description of the illustration admin-instance-tenant-settings-oic.png

Configure Security Options for Applications

Administrators can use the Security panel in the Tenant Settings page to require authentication for all applications in the instance.

When an administrator enables the Allow only secure applications to be created option, all published and staged applications in the instance will require user authentication. When the option is enabled, users must be assigned a role by the identity domain administrator and log in to access the applications in the instance. When the option is not enabled, applications can be created that allow access to anonymous users.

When an application has the default security settings, any user with a valid login can access the pages in an application. A developer can modify the default security settings to define the roles that can access applications, pages and components.

When the secure application option is enabled, an administrator can enable the Only Visual Builder Users can access secure applications option so that only Visual Builder users (those assigned the default Service User role) can access the staged and published applications in the instance. For example, this allows you to configure security so that users assigned the Visual Builder Developer role can access the designer, but can’t access the published application and data because they are not assigned the Visual Builder Service User role.

An administrator can also use IDCS roles when configuring the instance's security so that a user's access is limited to just the secure applications. Users assigned the selected IDCS role would be able to access the applications, but would be prevented from accessing Visual Builder or Oracle Integration Cloud resources external to the application, such as other OIC integrations.

To configure the security options for all applications in the instance:

  1. Open the instance’s Tenant Settings page.
  2. In the Security panel, enable Allow only secure applications to be created.

    Anonymous users can’t access the applications when this secure applications option is enabled.

  3. Select the Only Visual Builder Users can access secure applications option if you want to allow only Visual Builder users (users assigned the Service User role) access to the applications.

    To change the users allowed to access the application to those assigned a specific IDCS role instead of those assigned the default Service User role, select the IDCS role in the dropdown list under Allow access to application to users in role. This option is only available when both of the other security options are enabled.


    Description of admin-settings-security.png follows
    Description of the illustration admin-settings-security.png
  4. Specify what users denied access to the secure application will see:
    1. Enter the URL you want the users redirected to when they can't access the app.
    2. Enter an Access Denied message that they will see when denied access to a page in the app.

Assign Roles for Users to Access an Application

Administrators must assign roles to users, so they have the permissions required to access Visual Builder applications.

Privileges associated with a user role determine what tasks users assigned those roles can perform. See What Users Can Do in Visual Builder by Role.

To assign roles to users: See this:
For Oracle Integration Add Users, Groups, and Roles for an Existing Instance in Administering Oracle Integration
For Oracle Integration, Generation 2 Configuring Access to Oracle Integration Instances in Provisioning and Administering Oracle Integration and Oracle Integration for SaaS, Generation 2

Set Page Messages for Access Denied Errors

Administrators can use the instance’s settings page to specify a URL that users are navigated to when they are denied access to an application or page.

Authenticated users might see an Access Denied page or message when they attempt to access an application or page in an application that their user role is not permitted to access. Administrators can set the default page or message that users see when they are denied access to an application or page. Access Denied messages that are set at the application level in the General Settings of an application will override messages set in the instance’s settings page. The default Access Denied page and message is used if the message options in this panel are not set.

To specify an Access Denied page or message for applications in the instance:

  1. Open the instance’s settings page.
  2. In the Security panel, type a URL that users are directed to when denied access to an application.

    The URL that you specify is used as the Access Denied page for all applications in the instance and should be accessible to users who are not logged in.


    Description of admin-settings-messages.png follows
    Description of the illustration admin-settings-messages.png

    Note:

    If you are configuring settings for classic applications, the Access Denied settings are set in the Messages panel.
  3. Type the message that you want users to see when they are denied access to a page.

    The message that you enter will be displayed in the Access Denied page for all applications in the instance except for those where a message was set at the application level in the application’s General Settings page.

Allow Other Domains Access to Services

Use the Global Settings page to specify the domains that are permitted to interact with services in your instance.

Cross-Origin Resource Sharing (CORS) is a mechanism that enables you to specify the domains that are allowed to exchange data with applications in your instance. By default, incoming requests from domains not on your instance’s list of allowed origins are blocked from accessing application resources.

To add a domain to the list of allowed origins:

  1. Open the instance’s settings page.
  2. In the Allowed Origins panel, click New Origin and type the URL of the domain that you want to allow. Click Submit.

    The Allowed Origins panel lists all origins that are permitted to retrieve information from the instance.


    Description of admin-settings-origins.png follows
    Description of the illustration admin-settings-origins.png

Switch to Your Own Oracle DB Instance

The database provisioned with your Visual Builder instance is used to store data for your business objects and your app's metadata, but this database has a 5GB limit and you can't access the data in the objects using regular SQL.

If the 5GB limit is insufficient for your tenant schema, you can configure your instance to use an Oracle DB instance that has more space instead of the default database. You can connect to an Oracle DBaaS or Autonomous Transaction Processing (ATP) database instance. Using an ATP database will give you more space and direct SQL access to the objects VB creates. You can also use a Free Forever Oracle ATP, which provides 20GB of storage for free.

To use a different Oracle DB instance, you use a wizard in the Tenant Settings to create a connection to the database instance and export the applications stored in the tenant's current database.

If you decide to use JDBC to connect to your DBaaS instance, you must include the privileges required to enable the ADMIN user to create a tenant schema. The following SQL shows the grants that are needed:

CREATE USER [adminuser] IDENTIFIED BY [password];
GRANT CONNECT, RESOURCE, DBA TO [adminuser];

GRANT SELECT ON SYS.DBA_PROFILES TO [adminuser] WITH GRANT OPTION;
GRANT SELECT ON SYS.DBA_USERS TO [adminuser] WITH GRANT OPTION;
GRANT SELECT ON SYS.DBA_DATA_FILES TO [adminuser] WITH GRANT OPTION;
GRANT SELECT ON SYS.DBA_SEGMENTS TO [adminuser] WITH GRANT OPTION;

If you decide to use ATP, you'll need to include the wallet.zip file in the wizard in addition to the connection info. You might want to create a new ATP ADMIN user with the correct admin privileges. The following SQL statement shows how to create a second ATP ADMIN user in SQL*Plus or SQL Developer.

DROP USER [adminuser] CASCADE;
CREATE USER [adminuser] IDENTIFIED BY [password];
GRANT CREATE USER, ALTER USER, DROP USER, CREATE PROFILE TO [adminuser] WITH ADMIN OPTION;
GRANT CONNECT TO [adminuser] WITH ADMIN OPTION;
GRANT RESOURCE TO [adminuser] WITH ADMIN OPTION;
GRANT CREATE SEQUENCE, CREATE OPERATOR, CREATE SESSION,ALTER SESSION, CREATE PROCEDURE, CREATE VIEW, CREATE JOB,CREATE DIMENSION,CREATE INDEXTYPE,CREATE TYPE,CREATE TRIGGER,CREATE TABLE,CREATE PROFILE TO [adminuser] WITH ADMIN OPTION;
GRANT UNLIMITED TABLESPACE TO [adminuser] WITH ADMIN OPTION;
GRANT SELECT ON SYS.DBA_PROFILES TO [adminuser] WITH GRANT OPTION;
GRANT SELECT ON SYS.DBA_USERS TO [adminuser] WITH GRANT OPTION;
GRANT SELECT ON SYS.DBA_DATA_FILES TO [adminuser] WITH GRANT OPTION;
GRANT SELECT ON SYS.DBA_SEGMENTS TO [adminuser] WITH GRANT OPTION;

In the wizard you need to select and export all the applications in your instance that you want to keep. After confirming that your instance is using the new database instance, you must import the exported applications into Visual Builder to save them in the new database instance.

Note:

If you have live applications already on the instance before migration, make sure to backup the data in their business objects using the export options in the Visual Builder data manager. You'll then be able to import that data back into the new apps you'll create from the application archives you export in the wizard.

To switch to a different Oracle DB instance:

  1. Open the instance’s Tenant Settings page.
  2. Click Use Different Database in the Tenant Database panel to open the Change Tenant Database wizard.

    In the Change Tenant Database wizard you supply the details for the connection to your Oracle DB instance.



  3. Select a Connection Type in the drop-down list.

    You can connect to your Oracle DB instance using either JDBC or an ATP Cloud Wallet.

  4. Provide the details for connecting to your database. Click Next.

    The details you need to provide will depend upon the type of connection you selected.

  5. Select all the applications that you want to export. Click Finish.

    You must select and export all the applications that you want to keep. Any applications that are not exported will be lost.



    When you click Finish, the applications that you selected are downloaded to your local file system. Exported application archives include the details about the application's user roles, and they will be available when you re-import your app into the new database.

Visual Builder automatically manages the schemas and tables it uses for apps and business objects in your new DB, so you don't need to do anything further.

If you would like to access the business objects using SQL, you'll find that VB creates users/schemas with names that start with VB_ followed by randomly generated strings. By examining the data dictionary you'll be able to find the users that represent specific apps. Note that you'll see separate schemas for dev, stage, and published instances of an app. The schemas for the dev and test instances will be re-created with different names with every new version of the app that you create. If you want to prevent the schema name for a published app from changing, when you publish new versions of the app you should choose the option to not replace the data.

Reset an Expired Password or ATP Wallet for Your Oracle DB Instance

If you switch to use your own Oracle DB instance and the credentials you use to access the instance expire, you can renew the expired credentials using the Update Tenant Database Connection dialog.

To regenerate the expired values, you need to provide the ADMIN user credentials that you provided when you first switched to your own Oracle DB instance. Visual Builder uses the ADMIN user credentials to generate new Visual Builder tenant credentials to replace the expired credentials. Visual Builder does not store the ADMIN user credentials that you supply.

To reset expired credentials:

  1. Open the General tab of the instance’s Tenant Settings page.
  2. In the Tenant Database field, click the Edit icon to open the Update Tenant Database Connection wizard.
  3. In the Update Tenant Database Connection wizard, supply the ADMIN user credentials that Visual Builder will use to reset the expired credentials for your Oracle DB instance.
  4. Click Finish.

Add a Connection to Oracle Cloud Applications

The list of REST services in the service catalog of a visual application is retrieved from an Oracle Cloud Applications backend service. Specify the instance URL of the Oracle Cloud Applications backend service in the Tenant Settings page.

All visual applications in the tenant will use the Oracle Cloud Applications instance URL specified in Tenant Settings, but a visual application can be configured to use a different Oracle Cloud Applications backend service by specifying a different instance URL in the Backends tab (which you access from the Navigator's Services tab). The tenant-level backend configuration is ignored if you or a visual application developer configures a different Oracle Cloud Applications backend service in a visual application’s Backends tab.

The authentication choices available to configure a tenant-level Oracle Cloud Applications backend are:
  • Oracle Cloud Account: Needs federation between Oracle Cloud Applications and Visual Builder.
  • Propagate Current User Identity: Same as Oracle Cloud Applications. That is, it needs federation between Oracle Cloud Applications and Visual Builder.
  • None: This assumes your Oracle Cloud Applications REST API can be called without any authentication, which is not usually the case.

If the necessary prerequisites for setting a tenant-level Oracle Cloud Applications backend service are not available, then a visual application developer can set up a backend service at the visual application level where more options are available. Another option is for you (the service administrator) to configure the Oracle Cloud Applications backend with None and let the visual application developer override the authentication setting at the visual application level.

To specify an Oracle Cloud Applications service for the tenant:

  1. Open the instance’s Tenant Settings page.
  2. In the Services tab, click Create Backend, then choose Oracle Cloud Applications in the Create Backend dialog.

    Description of admin-settings-fa-url.png follows
    Description of the illustration admin-settings-fa-url.png

    When specifying the URL in the Tenant Settings, you (the service administrator) only need to provide the instance URL of the Oracle Cloud Applications backend service to retrieve the list of services.

  3. In the dialog, type the Server URL of the backend service, and configure other settings, such as security, as needed.
  4. (Optional) After you configure settings for the backend, add headers to the backend.
    Backend headers that you add will be applicable for any service connection to this backend, irrespective of the server or application profile that is used.
  5. Click Create.

    Visual Builder automatically discovers the interfaceCatalogs endpoint of the Oracle Cloud Applications backend, which retrieves the list of services and their metadata. This endpoint is typically in the form:

    https://<My Oracle Cloud Applications Instance URL >

    This endpoint is publicly accessible without any authentication.

    If there is a problem creating the connection, verify the instance URL of the Oracle Cloud Applications instance.

Create a Child Backend

You can create child backends to extend the functionality provided by the top-level Oracle Cloud Applications or custom backend registered to your Visual Builder instance.

Let's say your instance's Oracle Cloud Applications backend connects to an Oracle Cloud Applications instance that provides access to these service catalogs: Enterprise Resource Planning Supply Chain, Sales and Service, and Human Capital Management. Now if you want to access another catalog (say, Search), you can create a child backend to access the search service.

A child backend inherits the parent backend's definition, which you can override as required. Its server URL is derived from the top-level backend, with vb-catalog://backends/ as the base URL. Continuing the Oracle Cloud Applications example, the Sales and Service child backend adds to the top-level Oracle Cloud Applications backend and has vb-catalog://backends/fa/crmRestApi/resources as its server URL.

Child backends can be created only for the Oracle Cloud Applications backend and custom backends that use a OpenAPI/Swagger service specification.

  • To create a child backend for the Oracle Cloud Applications backend:
    1. Open the instance’s Tenant Settings page.
    2. In the Services tab, click the + sign for the top-level Oracle Cloud Applications backend:
    3. Select Custom ADF Describe to create a backend with an ADF Describe URL. For backends not having a Describe URL, select Custom.
    4. Enter a name and description for the child backend. Optionally, add static headers.
    5. Click Next.
    6. Enter the instance URL for the child backend (for example, vb-catalog://backends/fa/applcoreApi/search/). The child backend's URL will usually start with vb-catalog://backends/oracle-cloud-app-BackendId.

      Tip:

      To see the complete URL that the backend resolves to, click the Detach icon (Detach icon).
    7. Enter other settings, such as security and headers.
    8. Click Create.
  • To create a child backend for a top-level custom backend:
    1. Open the instance’s Tenant Settings page.
    2. In the Services tab, click the + sign for a top-level custom backend:
    3. Enter a name and description for the child backend. Optionally, add static headers.
    4. Click Next.
    5. Enter the instance URL for the child backend (for example, vb-catalog://backends/demo/newdemo). You can click the Detach icon to see the complete URL that the backend resolves to.
    6. Enter other settings, such as security and headers.
    7. Click Create.

Add a Connection to a Custom Backend

You can create your own backend to map to a custom server other than the Oracle Integration, Process, and Oracle Cloud Applications backend services. You can create a custom backend with a free-form URL, or create a custom ADF backend when you know the Describe URL that points to an ADF Describe service.

To add a connection to a custom backend:

  1. Open the instance’s Tenant Settings page.
  2. In the Services tab, click Create Backend.
  3. In the Create Backend wizard, select the type of backend you want to create:
    • To create a backend with a free-form URL, click Custom.
    • To create a backend with the Describe URL of an ADF service, click Custom ADF Describe. Use this option only when your custom ADF Describe endpoint does not have any child backends.
  4. In the Name field, enter a name and description for the custom backend.
  5. Add headers to the backend. Backend headers that you add will be applicable for any service connection to this backend, irrespective of the server or application profile that is used.
  6. Click Next.
  7. Enter the instance URL for the custom backend, configure other settings, such as security, and click Create.

Manage Self-signed Certificates

Administrators can use the Certificates page to upload and manage the self-signed certificates used by the instance to enable inbound and outbound SSL communications to a service’s REST APIs

When creating connections to REST services that use self-signed certificates, you might need to add an API’s certificate to your Visual Builder instance to validate SSL connections to that service. You can use the Certificates page to upload and remove certificate files (.pem)  for services. Uploading a service’s certificate file to the keystore will allow all applications in the instance to communicate with that service. The Certificates page displays a list of certificates that have been added. You can click the Delete button in a row to remove the certificate.

To upload a self-signed certificate:

  1. Open the Visual Builder main menu and click Certificates.

    The Certificates page displays a list of the certificates already uploaded to the instance.


    Description of admin-certificates-page.png follows
    Description of the illustration admin-certificates-page.png
  2. Click Upload to open the Upload Certificate dialog box.

    You use the Upload Certificate dialog box to create an alias for the certificate and upload the service’s certificate file from your local system.


    Description of admin-certificates-upload.png follows
    Description of the illustration admin-certificates-upload.png
  3. Type the alias in the Certificate Alias Name field.

    The alias is used to identify the certificate in the table in the Certificates page. The Certificate Type dropdown list is read-only because only Trust Certificates are supported.

  4. Drag the certificate file from your local system into the upload target area, or click the upload target area to browse your local system.
  5. Click Upload to add the certificate to the service keystore.

Manage Your Component Exchange

If your team develops custom components for visual applications and want the components to be available to all users in the Visual Builder Components tab, you'll need to first set up a component exchange. This chapter tells you how to set up the Component Exchange in Visual Builder.

What is a Component Exchange?

A component exchange is a repository of custom components available in VB Studio. You can use these components in your visual applications, such as web components and application templates. Many of the components provided by Oracle can be installed from a component exchange.

To integrate a component exchange with a Visual Builder instance, you provide the exchange's URL and credentials in the Tenant Settings. The exchange can be a private exchange in a VB Studio project or one of the exchanges maintained by Oracle.

If your organization develops or uses proprietary components, these components can be published to a private exchange hosted by a VB Studio project. For example, if you have a web component designed to be used in applications in your tenant, you can set up your own exchange and use it to distribute the component to developers in the tenant. Additionally, components provided by Oracle are automatically available from all private component exchanges.

Oracle maintains two component exchanges containing components validated by Oracle that are publicly available to all developers. If you don't have a private exchange but you want to give developers access to these Oracle components, you can add one of the following exchanges maintained by Oracle. If your instance is in the US, use the following details.

If your instance is in Europe, use the following details.

About Component Exchanges Hosted in VB Studio Projects

A VB Studio project can host a secure component exchange to store and distribute components only available to developers in the instance.

Each VB Studio project includes the component exchange 'compcatalog', which is the service used to access components stored in the project. The compcatalog service is provisioned by default with each project. Any project can be used to host an exchange if storage is enabled for the VB Studio instance. Component developers can use the service's APIs to publish components to the exchange.

To integrate a private exchange in a VB Studio project with a Visual Builder instance, an administrator specifies the URL for the project's compcatalog service and the credentials for a user that can access the project. The credentials used to connect to the exchange must be an owner or member of the VB Studio project hosting the exchange. All developers in the tenant use these credentials to connect to the exchange to get the components and application templates they want to use in their projects.

The URL for the project's compcatalog service has the following form: https://<hostname>/<org_id>/s/<project_id>/compcatalog/0.2.0/

In the URL, "compcatalog" is the exchange service and "0.2.0" is the API version of the service.

To determine the URL for the compcatalog service, you need to know the following details about the VB Studio project:

  • <hostname>. This is the VB Studio server where the project is hosted.
  • <org_id>. This is the organization (tenant) name.
  • <project_id>. This is a project identifier unique to the tenant. This is not the same as the project display name entered by the project owner and is not displayed in the VB Studio UI.

If you do not know the <project_id> for the project hosting the exchange, you can get it from the Git or Maven configuration, or by using the VB Studio Projects API. The following table describes how to get the <project_id>.

Method Steps
From a Git or Maven configuration
  1. In VB Studio, open the project and locate the Repositories tab on the project's Home Page.
  2. Expand the the Git or Maven section and copy the repository URL.

The Git repository URL will be similar to the following: https://{user_id}@{hostname}/{org_id}/s/my-org_testproject_5/scm/my-repo.git

The Maven repository URL will be similar to the following: http://{hostname}/{org_id}/s/my-org_testproject_5/maven/

In these examples, "my-org_testproject_5" is the project identifier. In this case, the URL for the 'compcatalog' service will be similar to https://{hostname}/my-org/s/my-org_testproject_5/compcatalog/0.2.0/

Using VB Studio Projects API

If you know the name of the project sharing your exchange instance, you can get the project metadata using a REST call to the VB Studio API.

For example, you can use cURL to send a REST call similar to the following:

curl -X GET -u '{username}:{password}'https://{hostname}/{org_id}/api/v2/projects/info/name:TestProject

The return should be similar to the following:

[
  {
    "organization":"my-org",
    "identifier":"my-org_testproject_5",
    "name":"TestProject",
    "urlId":"testproject",
    "description":null,
    "accessibility":"PRIVATE",
    "template":false,
    "state":"READY",
    "locked":false,
    "relation":{"membership":"OWNER","favorite":false}
  }
]

In this example, the identifier property in the return is the project identifier that is needed for the "compcatalog" service URL.

Add a Connection to a Component Exchange

When an instance is integrated with a component exchange, all developers using the instance can access and install components stored there.

After an exchange is added to the instance, all developers can use the Components tab in the Navigator to install and manage the components from the exchange that they want to use in their applications. When creating an application in the Create Application wizard, developers can also select any of the application templates that have been published to the exchange.

To add a connection to the Component Exchange:

  1. Open the instance’s Tenant Settings page.
  2. In the Component Exchange panel, enter the URL and credentials for the component exchange.

    Description of admin-settings-componentexchange.png follows
    Description of the illustration admin-settings-componentexchange.png

    If you are adding a connection to a private component exchange, it is recommended that the credentials you provide are for an administrator who is a member of the VB Studio project hosting the exchange or the project owner.

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 to your instance. A custom domain is a customer-provided hostname and domain (FQDN) created by adding a subdomain to your domain. After configuring your instance 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 for a visual application:

  • Configure the custom URL for your Oracle Integration Generation 2 instance, using the instructions in Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration and Oracle Integration for SaaS, Generation 2.

    Note:

    Custom URLs are supported on Oracle Integration instances (but only if you're on Generation 2), as well as on Oracle Visual Builder instances.

    Depending on whether you're on Oracle Integration Generation 2, Visual Builder, or a Visual Builder instance that was provisioned as part of a SaaS order, the process for enabling custom URLs varies. If you are using a Visual Builder instance, use the instructions in Configure Support for a Custom Domain in Administering Oracle Visual Builder.

  • Set the custom domain in the visual application's Settings editor and publish the app. See Specify a Custom App URL in Developing Applications with Oracle Visual Builder in Oracle Integration.

Note:

You can configure only one custom domain for each Oracle Integration Generation 2 instance.

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 other limitations:

  • A custom domain can only access a published app. It will not work for apps that are only staged.
  • If you publish a different web app in your 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 and configuring a different custom domain and visual application.
  • 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.
  • Mobile and PWA apps are not supported at this time. Custom domains can only be used for web apps.