Comments on: Writing to Access Databases http://psst0101.wordpress.com/2008/07/29/writing-to-access-databases/ Just Trying to Remember and Share What I Learn at Work Sat, 19 Dec 2009 05:29:25 +0000 http://wordpress.com/ hourly 1 By: Jim Marion http://psst0101.wordpress.com/2008/07/29/writing-to-access-databases/#comment-762 Jim Marion Thu, 31 Jul 2008 17:22:29 +0000 http://psst0101.wordpress.com/?p=128#comment-762 This is a very good post demonstrating how to use JDBC from PeopleCode. Since you are using a JDBC driver, you don't actually have to have Microsft Access installed on the app server. You just need to have the JDBC driver in your classpath ($PS_HOME/class or %PS_HOME%\class). Another alternative is to use JDBC in a Custom Target Connector created using the Integration Broker SDK. A very handy target connector would be a JDBCTargetConnector. The advantage of using Integration Broker over a plain PeopleCode/Java solution is that it would allow you to send the contents of delivered PeopleSoft integration points to a non-PeopleSoft database, like a Microsoft Access database. This is a very good post demonstrating how to use JDBC from PeopleCode. Since you are using a JDBC driver, you don’t actually have to have Microsft Access installed on the app server. You just need to have the JDBC driver in your classpath ($PS_HOME/class or %PS_HOME%\class).

Another alternative is to use JDBC in a Custom Target Connector created using the Integration Broker SDK. A very handy target connector would be a JDBCTargetConnector. The advantage of using Integration Broker over a plain PeopleCode/Java solution is that it would allow you to send the contents of delivered PeopleSoft integration points to a non-PeopleSoft database, like a Microsoft Access database.

]]>