Manage Backends in Your Visual Application

Backends define servers that your visual application can access. You can view and manage the backends available to your application on the Backends tab, which you access from the Services tab in the Navigator.

The following image shows the built-in Integration Applications (ICS), Oracle Cloud Applications, and Process Applications backends, which have been defined in the tenant-level catalog:

Description of the illustration backends.png

The administrator for this Visual Builder instance has configured the Oracle Cloud Applications backend to connect to an Oracle Cloud Applications instance that provides access to the three child backends shown under the top-level backend: Enterprise Resource Planning Supply Chain, Sales and Service, and Human Capital Management. You can create custom backends to map to other types of servers, either by providing an OpenAPI/Swagger file or by pointing to the URL of a custom Oracle ADF Describe.

If a backend hasn't been defined for your Visual Builder instance or you want to override the settings for your Visual Builder instance and create a catalog just for a particular application, use the Services tab to create a new backend or edit an existing backend.

For each backend, you can use the following tabs to view and edit the backend's details:

Tab	Description
Overview	Displays the name and type of the backend (which can be Integration Applications, Oracle Cloud Applications, Process Applications, or a custom backend). You can use the + Service Connection button to create a service connection based on the backend. Note: The Process backend is not used to define service connections. It is used only when you access Process-related tasks in Visual Builder. See Work with Business Processes. If any service connections have been defined for the backend, they'll be listed below the + Service Connection button. Dynamic service connections, which are defined in the catalog.json file, are automatically loaded and displayed below the button. Static services can be loaded by selecting the Load more related connections link, after which all openapi3.json files will be loaded and parsed, locating all services connections that were defined from the backend.
Servers	Displays the servers associated with the backend and includes the instance URL and the application profile associated with the instance. You can add, edit, or remove backend servers. You may have one or more servers if the backend is hosted on different instances. You use the Add Server button to add new servers where you specify details such as: The application profile to associate with the server Headers Security and connection details
Headers	Displays the static headers defined for the backend at the server level. You can add and edit headers in the tab.
Source	Displays the description of the backend stored in the tenant-level catalog.json file. If you override the tenant-level definition, this file shows the contents of the application-level catalog from the services/catalog.json file. You can edit the entries in the Source tab, if you want.

Note:

If you do not see any services in your catalog after confirming the URL and authentication method are correct, contact your administrator to confirm that you have the proper credentials and that your user role is authorized to access services from the backend instance.