This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
I have two system running on two seperate JVM's and two seperate App Servers(both are weblogic 6.1),the important functionality is on both the system there is a cache program which holds data in HashMap but both are shairing the same database.. So for commuincating with both the cache or synchronize the cache as changes happen at any end should be reflected at another end, currently I am using http call to notify the change at one end so accordingly another program removes the old values and when next request comes it refreshes the data. This is all happening in current scenario.... This complete thing is in Java programs so now I want only one cache for both the servers which will share the same database. So Client want to use J2EE means ur EJB feature so what kind of bean is useful for this scenario..? On which server it needs to be deployed or will there be any server clustering? And how the notification process for synchronization of changes in database will happen...? Throw some ideas.....
so now I want only one cache for both the servers which will share the same database.
It'll still be "two" caches if there are two server instances. Although, you could count a clustered environment as having only one cache because you're not the one who needs to synchronize it...
So Client want to use J2EE means ur EJB feature so what kind of bean is useful for this scenario..?
That would be entity beans.
On which server it needs to be deployed or will there be any server clustering?
If you want the two servers' caches to be synched, you'll have to cluster them. In that case, you'll deploy stuff on the "admin" server, which will in turn handle deploying the same stuff on the "managed" servers.
And how the notification process for synchronization of changes in database will happen...?
If you mean how will your application know when someone has manually added a row into the database using a command-line tool, it won't.