UConn Oracle Exadata - Perform basic functions with Boomi

Owned by Lara Juenger, created
Last updated: Sept 10, 2023
4 min read

The administrator of the subaccount needs to configure the Database V2 connector to access the correct certificates, proper jar files and proper wallet files before you can interact with a database that resides on UConn’s Oracle Exadata instances. The instructions for configuration are found here.

This article is intended for individuals who have a Boomi Associate Integration Developer Certification. If you do not know how to complete an action like “add a message shape”, please complete the recommended trainings.

This article is also intended for individuals with a good understanding of SQL and relational databases. Familiarity with sql queries, inserts, updates and deletes is necessary to configure and use the Database V2 connector with Oracle Exadata at UConn

The September 2023 Runtime release included several important changes to the Database V2 connector. These specifically added better null handling for updates. Check back soon for updated guides on how to best use this new functionality.

 Instructions

SELECT from an Oracle Table

  1. In a working directory create a new component of type Process

  2. Ideally there are existing connections to Oracle Exadata that were configured by your account administrator for you to us. Here is an example of the IDGarden Identities Oracle Database V2 Connector. Instructions for creating the connector are found in the UConn Boomi Administration SharePoint. Here is an example:

  3. In your start shape select No Data

  4. Add a Database V2 Connector to the Start Shape. In the example below the IDGarden Identities Oracle Database V2 Connector is selected as the Connection. Set the Action to GET. Click the green plus in the Operation to create a new Operation

  5. On the New Connector Operation window click Import.

  6. Select an atom that has firewall access to the exadata instance, leave the Get Operation Type as Dynamic Get. Click Next

  7. On the Object Type drop down select the table or view you are trying to query. Click Next.

  8. On the Database V2 Import Wizard window click Next.

  9. The import wizard creates JSON Request and Response profiles. If your project team has standards for naming that are different then the default names supplied, click the yellow pencil to edit and rename the profiles. In the example here, Database V2 NAME (TABLE) GET Request is renamed to NAME GET Request.

  10. After any renaming required to adhere to project standards, remove the WHERE clause in the SQL Query and click Save and Close. (To run this in test mode, you must set the Max Rows value to 99)

  11. Add a stop shape and save the new process

     

  1. Click Test in the upper right corner of the process pallet.

  2. Pick the Test Atom Cloud (TAC) available in your subaccount and click OK. An example shown here is the generic Test-Atom-Cloud for the mail UConn account.

  3. The process will execute in test mode, and you will see each step get a green halo as it completes successfully. You will see a success message when it is done.

  4. Go to the Test Results panel at the bottom of the screen. Go to the Shape Source Data tab and click on the page icon to see one of the records pulled from the database in the Document Viewer.

 

 Related articles