Integrating APEX with Fusion Applications

Use Oracle APEX to build extensions to Fusion Applications.

About Oracle APEX and Fusion Applications Integration Requirements

Learn about requirements for integrating Oracle APEX with Fusion Applications.

Requirements for integrating Oracle APEX with Fusion Applications include:

• A Fusion Application subscription.

• An Autonomous AI Database with a workload type of Data Warehouse or Transactional Processing.

• SQLNet connections to an Oracle Database in the same tenancy. Note: Oracle APEX AI Application Generator (APEX Service) does not support Fusion Application integrations since APEX workloads do not include SQLNet connections.

About the Integration Process

Integrating APEX with Fusion Applications is a two-stage process:

1. Create a Connection - Run the Database Tools Fusion Integration Wizard to create a connection between the Oracle Fusion Applications instance and the database where APEX resides.

   See Integrating Oracle APEX with Fusion Applications in Oracle Cloud Infrastructure Documentation.

2. Create a Starter Sample Application - Run the Create Application Wizard in App Builder to create a starter sample application with pre-configured integration to the Oracle Fusion Applications instance. See Creating an Application with Integrations to Fusion Applications.

About the Fusion Integration Starter Application

Learn about the Create Fusion Integration starter application.

When you run the Create Application Wizard and select the Create Fusion Integration option, the wizard creates a starter application and completes the following database setup tasks:

• Remote Server - Creates a Remote Server at the workspace-level named according to the convention APEX_FA_FUSION_INSTANCE_REST_APIS where FUSION_INSTANCE is the System Name which can be found in your Fusion Applications Cloud Console. This Remote Server is pre-configured to reference the base URL of your Fusion REST API endpoints.

• Web Credential - Creates a Web Credential a name of the format APEX_FA_FUSION_INSTANCE_DBMS_CRED which utilizes Database Credentials created by the Database Tools Fusion Integration Wizard. This credential is used both by the pre-configured Authentication Scheme and by the sample REST Data Source.

  The Web Credential is configured with two named scopes, used for accessing different types of Fusion services. These reference the scope values substitution variables configured by the Database Tools Fusion Integration Wizard:

  • OAUTH - Used to authenticate against ADF web-service endpoints.

  • BOSS - Used when accessing Business Object Spectra Services endpoints.

• REST Data Sources - Creates three sample REST Data Sources:

  • HCM Self Details - References the Workspace-level Remote Server and Web Credentials to obtain details about the currently signed in user. The information obtained from this REST Data Source is displayed on page three of the generated application. You can study the setup of this Data Source in order to create your own for other Fusion REST API endpoints.

  • Common Features User Roles - Used during authentication to obtain addition information about the Fusion Applications roles assigned to a user. This endpoint is only accessible to users having certain Fusion Applications roles.

  • CX Common Service Tags - Demonstrates accessing a BOSS endpoint. Note that, in order for this Data Source to return valid information, the authenticated user requires the Fusion roles necessary to access the Customer Experience module of Oracle Fusion Applications. Data from this endpoint is displayed on page four of the generated application. You can study this Data Source to see how named scopes are used to access different types of Fusion web-service.

• Application Items - Creates Application Items named G_GIVEN_NAME, G_MIDDLE_NAME, G_FAMILY_NAME, G_LOCALE, G_ZONEINFO, G_EMAIL which are populated automatically during the authentication flow with information about the current user. This information is then displayed on the Home page of the generated application.

• Authentication Scheme - Creates a pre-configured Authentication Scheme with a name of the format APEX_FA_FUSION_INSTANCE_OAUTH. You can copy and subscribe to this Authentication Scheme in your other Fusion integrated applications to easily enable Single Sign-On in those apps too. This Authentication Scheme contains placeholders referencing configuration parameters set at the instance-level by the Database Tools Fusion Integration Wizard.

  If necessary, the Fusion Applications scope urn:opc:resource:multiresourcescope is added to the Authentication Scheme. This allows a single application to access multiple different types of Fusion REST service by using Named Scopes, which can be configured on REST Data Sources or passed as the Invocation Scope to the APEX_WEB_SERVICE APIs.

  Example code is included to populate the user’s Dynamic Groups based on the roles obtained during the authentication flow. If the current user has the necessary Fusion Applications roles then additional information about each role is obtained and stored in the FA_USER_ROLES Collection. The current user’s roles, along with any additional information obtained from Fusion Applications, is displayed on page three of the generated application.

• Authorization Scheme - Creates an example Authorization Scheme named Has IT Security Manager Role which demonstrates how to reference Fusion Applications roles which can then be applied to components within your APEX Application.

For more information, see:

• Establishing User Identity Through Authentication

• Providing Security Through Authorization

• Managing REST Data Sources

• Managing Remote Servers

• About Using Collections

• Managing Application Items

Creating an Application with Integrations to Fusion Applications

Create a starter application with pre-configured integrations to Fusion Applications.

Note: Before attempting this task, you must run the Database Tools, Integrate APEX with Fusion Applications Wizard. See About Oracle APEX and Fusion Applications Integration Requirements.

To create a starter application with pre-configured integration to an Oracle Fusion Applications instance:

1. On the Workspace home page, click the App Builder icon.

2. Click Create.

   The wizard prompts you to select a method of creating your application.

3. Click Create Fusion Integration.

   Note: If you have not created a connection between the Oracle Fusion Applications instance and the database where APEX resides, a warning message appears.

   The Create Fusion Integration page appears.

4. Configuration Options:

   1. Fusion Instance System Name - Select the Fusion instance with which you wish to integrate the new starter application. Only those Fusion instances that have been configured using the Database Tools integration wizard are available.

   2. Base URL for the REST APIs - The URL of your Fusion instance where the REST API endpoints can be found. Typically, the URL will be the https://my.host.name/ portion of the URL you use to access your Fusion application in your browser.

      Once you select a Fusion Instance System Name, the Base URL is calculated based upon information provided by the Database Tools integration wizard.

      If the information was not provided by the wizard, then the value is calculated based on Oracle OCI standards. As a best practice, Oracle recommends you verify that any provided value matches your environment.

      If that calculation is still incorrect, then enter a value manually.

   3. API Status - Once Base URL for the REST APIs is populated, APEX attempts to contact the server at the specified location. The status of that request displays here.

      If the server is contacted, this attribute displays:

      200-OK

      If any other status displays, there is a network configuration issue between APEX and the Fusion Applications instance. Although you can proceed and create a starter application, you may not be able to run the application until the issues are resolved.

      If the network configuration or URL is incorrect, then this check may take several minutes to complete.

      Tip: Possible issues include the incorrect configuration of ACLs or ACEs between APEX and the Fusion Applications instance. For more information, see Enabling Network Services in Oracle Database in Oracle APEX Installation Guide.

5. Advanced Settings - The wizard creates the following attributes in the starter application and pre-populates with default values.

   1. Application Name - Enter the name used to identify the application to developers.

   2. Application Alias - An alphanumeric identifier, unique within the workspace, for the application. This identifier appears in the URL used to access the application.

   3. Application ID - Enter a unique, numeric identifier for your application. This field contains an automatically generated identifier by default. Application IDs between 3000 to 9000 are reserved for internal use by Oracle APEX.

   Tip: You can override the default values to provide your own Application Name and Alias. Be cautious when overriding the Application ID since it must be unique within the entire APEX instance.

6. Click Create Application.

   The Create Application Wizard creates a starter application and completes a number of database setup tasks. See About the Fusion Integration Starter Application.