Configure Real-Time Data Integration With Oracle Autonomous Database

The Applications page acts as a single page to configure and view all applications in Oracle Field Service.

Users can use the Applications page to create new applications to transfer data to their Oracle Autonomous Database instances. Also, users can configure real-time data transmission for Oracle Field Service entities. The data is transferred to the Oracle Autonomous Database instances when the events corresponding to the entities are triggered in the Oracle Field Service system.
Note: By default, the Daily Extract option is available in the Applications page and you can click the option to view the daily extract configurations.

To complete real-time data integration:

  1. Log in to Oracle Field Service Manage interface.
  2. Click Configuration, Applications.
  3. In the Applications page, click Add Application to configure a new application.
    The Add Application dialog box for an Oracle Autonomous Database application is displayed.
    This screenshot shows the Add Application dialog box for an Oracle Autonomous Database application.
  4. Select Oracle Autonomous Database from the Application Type drop-down list and enter the details in the following fields:
    1. Application Name: Type a name for the Oracle Autonomous Database application.
    2. URL: Type the URL of the ORDS endpoint in the following format: https://<node-ip-address>. Make sure that the access rule ora_p2_httpssl is enabled in Oracle Autonomous Database. For more information, see the Oracle Database Cloud Service documentation.
    3. Alias: Type the schema alias for the ORDS-enabled schema.

      If you are connecting to a Pluggable Database (PDB), use the format: <PDB_Name>/<schema_name>.

      If you are not connecting to a PDB, use the format: <schema_name>.

      Prerequisite: You must REST enable the Oracle database schema on which you want to use the REST Enabled SQL service. To REST enable the Oracle Database schema, you can use SQL Developer or the PL/SQL API. For more information, see the Oracle Database Cloud Service documentation.

    4. User Name: Type the name of the ORDS user with roles: SQL developer or Oracle database schema name. For more information, see the Oracle Database Cloud Service documentation.
      Before using the REST Enabled SQL service, you must authenticate against the Oracle database schema on which you want to run the SQL statements. Following types of authentications are available:
      • First Party Authentication (Basic Authentication): For this authentication, create a user in ORDS with the SQL Developer role. This ORDS user will be able to run SQL for any Oracle database schema that is REST-enabled.
      • Schema Authentication: For this authentication, use the Oracle database schema name in uppercase and the Oracle database schema password (for example, HR and HRPassword). This user type wiill be able to run SQL for the specified schema.
    5. Password: Type the ORDS user's password with SQL Developer role or the Oracle database schema password
    6. Confirm Password: Retype the password.
  5. Click Add.
    After a successful channel is created using ORDS, the Applications page shows the Oracle Autonomous Database application. You can add, delete and modify application configurations from the Applications page provided, you must have the permission to access such applications.
  6. Click the Oracle Autonomous Database application to configure it:
    1. Click Add New to create a new entity.
    2. In the Add configuration dialog box, specify the required details:
    3. Entity: Select a list of Oracle Field Service fields that you want to view.
    4. Table Name: Enter the table name that you want to create in the new application.
    5. Data Transfer: Select one of the following options:
      • Once Daily: Data is transferred to the Oracle Autonomous Database instance once in a day as per the daily extraction period configured in the system.

      • Real-time: Data transfer from Oracle Field Service to Oracle Autonomous Database occurs in near real time.

    6. Click Submit.
      The entity is added to the channel with the specified details.
  7. To add fields to the entity, click the Properties icon corresponding to that row and select Fields from the drop down menu.

    This image shows the Properties icon drop-down menu option to configure fields:

    This image shows Properties icon drop-down menu.

  8. Click the Plus icon and select the required field that you want to add to the entity.
  9. Click Add and Click OK.
    The selected fields are added as columns to the corresponding tables in the Oracle Autonomous Database instance.

Results:

After you add a new application:
  • The Applications page displays the updated list of applications.

  • Monitoring data or information displayed in the Applications page is reset every day (24 hours).

  • The data processing and transmission depends on the volume of data stored. You may expect a delay in transferring big volumes of data for real-time data transfer. Also, the daily transmission is initiated as per the daily extraction period.

  • The data transfer for the entities, namely, Activity, Inventory, ActivityLink, Resources, Users, and Route entities is not started immediately when the user opts for real-time data transfer.

    The real-time data transfer for the entities is initiated only from the next day after the first run of the daily extraction process is completed.

Consider the following configurations for the new application:
  • Chat Fields and Chat Message Fields entities are configured.

  • Real-time data transfer method is selected.

  • The Oracle Field Service instance is connected to the application instance.

Note that the total number of chat messages and total number of helpdesk messages are displayed in that instance. If a user logs in to the Oracle Field Service instance and sends a helpdesk chat request, then the total number of chat messages and total number of helpdesk messages are incremented in the instance. However, if a one-to-one chat is initiated between the users then the total number of chat messages is incremented in the instance.