Getting to Postgres through the Java Integration Suite
By John Clingan on Nov 23, 2005
The conversion of the database was seamless, I simply re-ran my "create table" and "insert" scripts to re-populate the database with dummy data. Sorry, nothing of substance to share with you on the database conversion side. I'm a Postgres newbie, and it sure felt like it. RTFM. That's what I did. Nope, no substance to that thought either.
On the Java Integration Suite (JIS) side of the equation, the conversion was seamless. No code modified. I just updated about 9 properties (driver name, connect string, etc) across 2 property sheets. That was it. OK, I fat-fingered the driver name and it took me a bit of time to debug. After I figured that out, it was pretty darn smooth. This was all done on my laptop (the test system).
I am only partially done converting the real demo. Postgres is installed with the data imported. I still have to update the JDBC properties on the test system. Once the live upgrade to Nevada build 27a is done on my laptop, I'll boot the petri dish. eDesigner, the JIS development environment, requires Windows. I've told every ex-SeeBeyond employee about this, and I am sure the message has been heard. They just have quite a bit on their plate, so I'll patiently wait. I bet there is a way to update the properties from the command line, but I have yet to read that FM.
FYI, I downloaded Postgres from Blastwave. Supposedly the Sun Update Center either has Postgres or will have it soon. I don't use the Sun Update Center simply because I run Nevada. If anyone knows if the Sun Update Center works with Nevada, let me know. I haven't tried yet.