It's not a secret anymore!
The moose likes JDBC and Relational Databases and the fly likes J2EE application in production environment Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "J2EE application in production environment" Watch "J2EE application in production environment" New topic
Author

J2EE application in production environment

jay roy
Ranch Hand

Joined: Nov 16, 2006
Posts: 145
hi guys

Not sure if this a good place to ask this question.

I am working on a J2EE application in production environment. In my j2ee websphere applicaiton server i have deployed a ear file.

I have a clustered environemnt where i have three websphere application

servers set up in cluster.The three applcation servers are named server1, server2, and
server3.
All three application servers have their own jvm and all three application servers
use a common database.
now say there is a common record in database which is accessed by three users user1, user2 and user3
and the three users are served by server1 , server2 and server3 respectively.
After user1, user2 and user3 have accessed the record, if user1 updates the record, i
want user2 and user3 to be able to see the updated record (as updated by user1).

Can anyone tell me what could be a solution to this problem.

thanks
J
Paul Clapham
Sheriff

Joined: Oct 14, 2005
Posts: 19728
    
  10

I think it doesn't really matter that these are web applications, does it? Your question is mainly about how, after one user updates a record, other users can find out about that and see the updated version, right? So let's move it over to the JDBC forum.
Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

Pushing updated from a database to another application is not a simple thing. Will all your clients be likely to update the record? Could you get away with optimistic locking?


JavaRanch FAQ HowToAskQuestionsOnJavaRanch
 
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
 
subject: J2EE application in production environment
 
It's not a secret anymore!