Selection of application servers

Question

Recently, much of application is being covered with J2EE/WAS Servers like weblogic.
But in ACID heavy big database transactions in large telecom company's customer and billing database,
I wonder which is better selection between was and tuxedo(TP).
for SOA and Service Bus integration, WAS may be mandatory
but for oltp transaction, I wonder which is better between
the following options
option1, WAS(Presentation) + TP(biz logicfor big oltp transaction)
Option2, WAS only(Preseantation + j2EE/EJB,Bizlogic)

Answer 1

Hi Chanyoung,
With regards to references for using a web server or J2EE app server (your was?) and a TPM, that would be something you would need to work through your BEA account team. We have many customers in many industries using a combination of J2EE and TPMs and as I think I mentioned before, this is the recommendation that Gartner made in a report a year or two ago.
As for examples of failed web server only solutions, that will be harder to get as failures often don't see the light of day. Perhaps others reading this can contribute some examples.
I have read nothing that indicates TPMs will be relegated to the dust pile of outdated technologies. TPMs have a long history of providing highly scalable and highly reliable infrastructure for building and deploying applications. J2EE app servers such as WLS are catching up, but still don't provide the reliability and scalability of TPMs. When they do, other considerations as I mentioned earlier will still come into play as to which solution to choose.
I see TPMs playing a valuable role in OLTP for the foreseeable future. Things like an ESB focus on a different problem. TPMs host your business services and provide your application infrastructure. ESBs provide service infrastructure that allows you to more easily and flexibly utilize the business services built on TPMs and other application infrastructures.
Regards,
Todd Little
BEA Tuxedo Engineering