Summary

This article describes the process to configure InfoBurst to use a custom Oracle connection using ORA_Managed.config and an alias. With an alias configured, a Database Connection or Repository connection can use the alias instead of standard connection string. A Database Connection or Repository connection that uses a connection string will still function after completing this process.

Requirements

This process involves use of custom application .config files and a customized ORA_Managed.config file. These files will be overwritten during an InfoBurst update. If you are using these customized files, then you must back them up before an update. See InfoBurst Update below for details.

Configure ORA_Managed

• Locate file ORA_Managed.config located in the InfoBurst application root folder (default = C:\Program Files\InfoSol\InfoBurst)
• Update the file with any required connection(s) (dataSources)
• Consult your Oracle DBA for details about editing ORA_Managed.config

Example

Highlighted entry is custom where alias ORATest can be used in Database Connection or Repository connection.

<oracle.manageddataaccess.client>

    <version number="*">

      <dataSources>

        <dataSource alias="SampleDataSource"

            descriptor="(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ORCL))) "/>

        <dataSource alias="ORATest"

            descriptor="(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle19)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=xe))) "/>

      </dataSources>

      <settings>

      </settings>

    </version>

</oracle.manageddataaccess.client>

Update Config Files