1. Building Responsive Applications with Visual Builder Studio
  2. Manage Applications
  3. Preview, Share, and Deploy Visual Applications
  4. Specify a Custom App URL

Specify a Custom App URL

Sometimes it’s not appropriate to use the default URL that VB Studio generates for your application. For example, if you’re building an application for your customers, you can use a custom domain for the application to shield customers from the details of your server’s host and domain name.

To use a custom domain for your application, your Visual Builder instance service administrator must configure your instance to support the custom domain. To do this, they’ll need to open a service request with Oracle Support to set up the URL redirection. They’ll also need to protect your Visual Builder instance with Oracle Cloud Web Application Firewall. For more information about the configuration tasks to support custom domains, see Configure Support for a Custom Domain in Administering Oracle Visual Builder Generation 2.

After the visual application is deployed, the web application and the business object APIs can be accessed directly using the custom domain. You can also access web applications deployed as PWAs.

Note that only one custom domain can be mapped to a visual application, and it can only be used to access one web application in the visual application. To ensure that the correct web application is loaded when using a custom domain, your visual application must contain only one web application.

Multiple custom domains can be used in an instance, but each must be mapped to a different visual application. For example, if the visual application myvisualapp1 is mapped to the subdomain mysubdomain1, if you want to map mysubdomain2 to an application it must be mapped to a different visual application (for example, myvisualapp2).

To map a custom domain to a visual application:

  1. In the visual application's header, click the Menu option in the upper right corner.
  2. Click Settings.
  3. In the Settings editor's Applications tab, enter the custom domain you want to use in the Vanity URL field. The domain must be a complete URL and use a valid form, for example, https://foo.example.org.

After you've set the vanity URL, it's important you work with the visual app using its custom domain. For example, if the app's vanity URL is https://foo.example.org, access it in a browser at https://foo.example.org/ic/builder, then proceed to share and deploy the app.

Note:

Working with a vanity app from a non-vanity host can cause issues when you try to access the deployed app, so make sure you access the Designer using the app's custom domain.

After you deploy the visual application, a visitor can enter the custom domain (for example, https://foo.example.org) in the browser to open the web application. The URL will not contain any additional path parameters because the app is loaded as the root domain.