RE: Enterprise Java

Unless you are expecting hundreds a second and have the hardware to
facilitate it, then a simple Tomcat/Axis/Servlet combo will suit you just
fine.

Aaron Bartell
http://mowyourlawn.com


-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Mike
Sent: Friday, May 04, 2007 9:11 AM
To: Java Programming on and around the iSeries / AS400
Subject: Re: Enterprise Java

On average? To start with, maybe several hits/day. As we roll out GIS
(Global Information System??) there will definitely be more. GIS involves
X/Y coordinates and overlays on maps for gathering information.

On 5/4/07, albartell <albartell@xxxxxxxxx> wrote:

EJB's are really meant for when you want to spread processing and HA
across multiple app servers/LPARs (as I understand them). If you
aren't doing that or don't have multiple servers then not much is
being gained outside of a good amount of EJB complexity. How many
transactions are you expecting per minute?

It sounds like a Java servlet with Axis running on Tomcat with
connections pooled is all that is warranted here. See how I configure
connection pooling with my Tomcat server below.

C:/Program Files/Apache Software Foundation/Tomcat
5.5/webapps/MyServletContext/META-INF/context.xml
<Context path="/MyServletContext" docBase="/MyServletContext"
debug="0" reloadable="false">
<Resource
name="jdbc/myresourcename"
auth="Container"
type="javax.sql.DataSource"
factory="
org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory"

maxActive="100"
maxIdle="30"
minIdle="10"
maxWait="15000"
username="myuser"
password="mypassword"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/mydbschema"
removeAbandoned="true"
removeAbandonedTimeout="300"
validationQuery="select 1"
logAbandoned="true"
testOnBorrow="true"
testOnReturn="true"
testWhileIdle="true"
/>
</Context>

HTH,
Aaron Bartell
http://mowyourlawn.com