technojde
Member
Hi,
I have seen some posts here by other members wherein they have posted some steps re active-active enterprise server/app server. I am not convinced how this solution would work. my concerns are:
1> I believe JDE uses caching of tables/other info in their in-memory caches within all call object kernels. In a true active/active solution, the app request from the jas server to ent server would be agnostic (ie if you placed ACE/F5/virtual server as an interceptor between HTML server and Ent/app server). I'd also think all db requests are specific to a call object kernel so there should be a built in affinity between transaction req and one instance of the app server "cluster". I don't know how one would overcome that.
If DB triggers are used, what happens during upgrades (ie 812-->90)?
I have seen some posts here by other members wherein they have posted some steps re active-active enterprise server/app server. I am not convinced how this solution would work. my concerns are:
1> I believe JDE uses caching of tables/other info in their in-memory caches within all call object kernels. In a true active/active solution, the app request from the jas server to ent server would be agnostic (ie if you placed ACE/F5/virtual server as an interceptor between HTML server and Ent/app server). I'd also think all db requests are specific to a call object kernel so there should be a built in affinity between transaction req and one instance of the app server "cluster". I don't know how one would overcome that.
If DB triggers are used, what happens during upgrades (ie 812-->90)?