Runtime access to your integrations will use the custom endpoint with no redirection. For all other access points—design-time, Visual Builder, Process Automation—you still access the custom endpoint, but the custom endpoint then redirects to the appropriate URL.

Be aware of the following:

• Associating a custom endpoint with your Oracle Integration instance doesn't affect the original instance URL. You can access your instance using the custom endpoint URL or the original instance URL.
• If you're using the Oracle NetSuite Adapter, the adapter's TBA Authorization Flow security policy won't work with custom endpoints for Oracle Integration.
• An API gateway doesn't redirect access points such as design-time, Visual Builder, and Process Automation. If you use an API gateway for your instance, you'll need to access these resources using the original URLs. See Manage Oracle Integration Endpoints Using API Gateway.

You can create the following types of custom endpoints for an Oracle Integration instance:

• Oracle-managed custom endpoint

  If you use this option, Oracle procures and manages the public certificate for your host name.

• Customer-managed custom endpoint

  This option is appropriate if you want to use your own load balancer. However, be aware that, with this option, you are responsible for keeping your certificate up to date. If you let your certificate expire, any applications that use the custom endpoint will fail.

If you want to switch from a customer-managed custom endpoint to an Oracle-managed custom endpoint, or vice versa, you need to delete your existing custom endpoint, complete the prerequisites for the new type of custom endpoint, and then create the new custom endpoint.