Re: Best Practice for iSeries Data Access -- WDSCI-L

David

You are on the right track when using DAO in your integration layer. Although, you have some other persistency mechanism, such as ORM, JDO and EJB's, but I would stick with DAO's. When using connection pools I would use JNDI to handle lookup.

Some urls to start with:

Database access
http://daoexamples.sourceforge.net/
http://jakarta.apache.org/struts/faqs/database.html

Patterns
http://java.sun.com/blueprints/corej2eepatterns/Patterns/index.html
http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html
http://www.patternscentral.com/index.php
http://www.theserverside.com/
http://martinfowler.com/books.html#eaa

Struts (if you are using this framework)
http://jakarta.apache.org/struts/index.html
http://jakarta.apache.org/struts/userGuide/index.html
http://www.mail-archive.com/struts-user%40jakarta.apache.org/

/Peter

David Kelly wrote:

Hello, I'm researching best practice for iSeries EIS data access from a Model 2 framework. I believe it would behoove me to have a pool of connections to my iSeries DB ready for web traffic, rather than performing them for each request. I'm confused with all the literature referencing DTO & DAO I am finding when reviewing the RedBooks found via a connection factory search. At my front controller Action Servlet init(), I thought I would prepare a data base connection pool for latter use in the Servlets' doGet/doPost method. I planned to insert my specific code in doGet/doPost to log stats about my form by HttpServletRequest.getParameter("session"), which I would be updating in subsequent pages. I'm hoping I can retrieve the session and use it as a key in my iSeries tracking file, any tips appreciated. The forwarding pages would be determined via ActionForward returned from my Action class. Any URL's or recommending reading would be appreciated. I'm currently finding stuff like JCA, resource adaptors. Is this the location I should dig in with my research? It's certainly a fun course of discovery learning Java and the different frameworks available. In RPG, we rarely name our design patterns, it sure helps when communicating ideas to have a common syntax for these designs. The more I play with the Java, the more I learn how much more I need to learn. This keeps it fresh and exciting. Thanks to all for years of sharing of ideas and tips. David Kelly
_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) mailing 
list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.