Switch Ingres instance on pitblade
From PTAGISWiki
Steps to reconfigure Weblogic to use a different Ingres installation on pitblade.
Contents |
Background
There is a complex chain of dependencies involved when a webapp like PTAGIS initiates a database query. This document describes the steps necessary to direct a webapp's query to an upgraded Ingres instance, while maintaining the existing instance.
Related documents:
Install new instance
The directions in Install Ingres client should be followed and then verified by using a sql command like this:
pitblade:HH:ingres: > sql ptagis3 INGRES TERMINAL MONITOR Copyright 2002 Computer Associates Intl, Inc. Ingres SPARC SOLARIS Version II 2.6/0207 (su4.us5/02) login Thu Feb 28 14:04:01 2008 continue * help\g Executing . . . Name Owner Type c_c_t_x1 pittag index cal2dat_xltn pittag table cea_coil_detail pittag view cea_coil_tally pittag table cea_invocation pittag table cea_mon_tally_by_coil_count pittag table cea_monitor pittag table cea_monitor_detail pittag view cea_monitor_summary pittag view
vnodes
The PTAGIS webapp relies on the following vnodes on pitblade:
- sockeye
- production
- blueback
These vnodes must exist and pass the connection test in netutil.
weblogic configuration
The startup script for weblogic must set II_SYSTEM and the class path. Here is an example:
### MN: custom ptagis classpath setup ### for the ingres jdbc driver II_SYSTEM=/dsk1/AdvIngres/ing26 #II_SYSTEM=/dsk1/AdvIngres/ing26/ingHH CLASSPATH=$II_SYSTEM/ingres/lib/edbc.jar:$CLASSPATH CLASSPATH=$II_SYSTEM/ingres/lib/iijdbc.jar:$CLASSPATH
Within the weblogic admin gui, the JDBC connection properties must be set appropriately for the Ingres instance. Specifically, the JDBC connection must either use EDBC or DAS. Here are the settings for each of these drivers:
DAS
URL: jdbc:ingres://localhost:II7/sockeye::ptagis3 driver class: com.ingres.jdbc.IngresDriver
EDBC (deprecated)
URL: jdbc:edbc://localhost:II7/sockeye::ptagis3 driver class: ca.edbc.jdbc.EdbcDriver
