Connecting VBCS to ADF Business Components

When you encounter ADF Business Components

Older Oracle SaaS applications and some Oracle E-Business Suite extensions expose their data layer through ADF Business Components (ADF BC) — a Java EE data binding framework. While modern Fusion applications provide REST APIs, some modules (particularly in HCM and certain Finance areas) still use ADF service interfaces.

Connection options in VBCS

VBCS can connect to ADF BC services in two ways:

Option 1: ADF Business Component service type in VBCS service connections — VBCS has native support for ADF BC, allowing you to browse service catalogs and generate bindings automatically.

Option 2: Via REST facade through OIC — expose the ADF BC data through an OIC integration that calls ADF services and re-exposes them as REST. VBCS then calls the OIC REST endpoint. This is more work upfront but creates a cleaner, REST-standard interface.

Setting up an ADF BC service connection

In VBCS, create a new service connection of type “ADF Business Component”:

1. Enter the ADF service URL (typically ending in .svc)
2. VBCS introspects the service and lists available View Objects and their operations
3. Select the View Objects your application needs
4. VBCS generates typed binding interfaces for each

CRUD operations on ADF View Objects

ADF BC service connections support standard CRUD:

• findByKey — fetch a specific record by primary key
• findByViewCriteria — fetch records matching filter criteria
• createRow — insert a new record
• updateRow — modify an existing record
• deleteRow — delete a record

Map these to your VBCS action chains for data operations.

Limitations compared to REST

ADF BC connections are more brittle than REST:

• Service WSDL changes require refreshing the service connection and may break existing bindings
• Bulk operations are not as straightforward as REST batch endpoints
• Error messages from ADF services are often verbose and not user-friendly — wrap them before displaying

When to prefer the OIC REST facade

If you have more than 3-4 ADF BC operations in your VBCS application, the maintenance overhead of managing ADF service connections directly often exceeds the cost of building an OIC integration layer. The REST facade also positions you better for future migration when the underlying module adds REST API support.