[OO Tip] How to integrate PostgreSQL JDBC driver to open PostgreSQL DB
How to integrate PostgreSQL JDBC driver to open PostgreSQL database (DB) and answer these questions:
- What steps need to be performed to include the PostgreSQL JDBC jar file into Operations Orchestration (OO) so that PostgreSQL databases can be opened?
- Where in the directory structure should the jar file be placed?
- Are there any configuration changes required to enable this driver?
OO directory path and instructions documented in the description of Structured Query Language (SQL) Query operation (/Library/Operations/Databases/JDBC/SQL Query). Please see notes below:
- By default, this operation supports Oracle, MSSql, Sybase and DB2.
- To enable MySQL support, the Java Database Connectivity (JDBC) drivers would need to be added to the %ICONCLUDE_HOME%\RAS\Java\Default\webapp\WEB-INF\lib directory and then update the SQLDBType selection list with the appropriate setting (MySQL).
- To enable Netcool support, add the JDBC driver to the %ICONCLUDE_HOME%\RAS\Java\Default\webapp\WEB-INF\lib directory and then update the SQLDBType selection list with the appropriate setting (Netcool). The JDBC driver is included with Netcool (not Operations Orchestration), and is named jconn2.jar or jconn3.jar, depending on the Netcool version.
- Does not support columns of type LOB.
If you want to use a custom JDBC driver then you must have the library installed as noted above.
Also, you will need add two new inputs to the operation:
dbClass - the classname of the JDBC driver to use
dbURL - the url required to load up the driver and make your connection
For Windows authentication, the domain must be specified in dbURL and dbClass must point to a MSSQL driver. If user and password are present in dbURL, those will be used for authentication together with the domain and not the values from the Username/Password inputs. The username must not be in the form domain\username, since the domain is specified separately in dbURL.
For Sql authentication, the domain must not be specified in dbURL.
Direct link to the document here:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.