RE: Enterprise Java

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

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

Honestly, I am the middle man here.

Web service: We want a middle tier to use SOAP (or whatever it's called) to
and from our web server. The java web service would communicate with the
System i, MS SQL and other required databases. This way we only have one
hole through the DMZ to a specific server (if we can even do that).

We are in the planning stages on this and are first determining if we should
do RPG, Java, or .NET. The web developer said he would like to use Enterpise
java beans and didn't think the JVM on i5/OS supported it without the
full-blown WebSphere App. Server. I thought it would and we could just
install JBoss to make use of them.

On 5/3/07, Joe Sam Shirah <joe_sam@xxxxxxxxxxxxx> wrote:

Hi Mike,

I think there are opportunities for miscommunication here. "Web
service" means something specific to most Java developers and that's
something substantially different from just accessing multiple databases.

Secondly, your answer really doesn't tell us anything about the
"enterprise" needs of your application(s.) So we can't really say if
just a web container like Tomcat or Jetty is sufficient or if you need
something that supplies more services. There are a lot of options
around.

"persistent data connections" doesn't sound like a very good idea
at first, but that's essentially what connection pools provide, and
you should probably look to using those regardless of whether you use
a web or J(2)EE container. There are also a number of other factors
that contribute to database related performance beyond just connection
persistence.


Joe Sam

Joe Sam Shirah - http://www.conceptgo.com
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International? http://www.jguru.com/faq/I18N
Que Java400? http://www.jguru.com/faq/Java400


----- Original Message -----
From: "Mike" <koldark@xxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400"
<java400-l@xxxxxxxxxxxx>
Sent: Thursday, May 03, 2007 3:01 PM
Subject: Re: Enterprise Java

The lead web developer wants to use persistent data connections to
databases. This web service would grab data from MS SQL, the System
i,

and

untold # of other databases for use on the main City website. So
speed

is

the key here.

On 5/3/07, Pete Helgren <Pete@xxxxxxxxxx> wrote:

Mike,

It depends what you mean by "Enterprise Java web service". WAS

Express

(included with i5/OS) and WAS CE (Community Edition), a free
implementation of the Geronimo project, would be IBM supported
alternatives as well. JBOSS would work as well. Tomcat could also

fill

the bill. A bit more about about your application might be helpful.

Pete Helgren

Mike wrote:

We are looking at the possibility of a Enterprise Java web
service

for

communication between the public web server and all internal

databases.

We

would like to avoid purchasing the full WebSphere Application
Server

as

was

wondering if using JBoss would work?

--
Mike Wills
http://www.linkedin.com/in/mikewills
Blog - http://mikewills.name
Podcasts - http://podcastmike.com
--

--
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list To post a message email:
JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/java400-l.

--
Mike Wills
http://www.linkedin.com/in/mikewills
Blog - http://mikewills.name
Podcasts - http://podcastmike.com
--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.