Connect to separate JDBC from Provisioning Plan

We have an application that is looking to automate some provisioning tasks through IdentityNow where we have a read-only connection to one database with a master table, but the application team is needing us to connect to a separate database to insert data into a staging table where they have a process that performs actions based on the information provided from master table and action to be taken(username, actionId, actionDate). This second database does not have the information from the master table for us to just connect there and have one connection.
Does anyone have experience handling this? Is it possible to connect to second database from provisioning plan?

Hi Aaron,
You have few options but nevertheless you need to be aware that it’s actualy quite complex solution and mostly depends on what kind of database engine you are using in the application.

The most important is that you need to decide if you want to solve problem on the DB side or on IDN side. I have a suspicion that to fix it on DB would be a bit easier.

As an example - if you are using eg. Oracle you can use DB Link with the View created on the master table of DB1 to display it in Read Only mode in DB2 as a View. Then that means you can just make connection to DB2.

Second option would be to create your own connector which is capable of handling 2 jdbc connections in paralell.

There are most probably more options to go but you would need to provide some more details especially what kind of DB you are using,

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.