Architecting Oracle ATG Web Commerce for Maximum Availability
The scope of this paper is limited to the technical considerations involved with running a single Oracle ATG Web Commerce site from two or more separate physical data centers. All systems involved with servicing a customer's HTTP request will be discussed, from DNS to the network that connects database nodes. Auxiliary Oracle ATG Web Commerce applications, like Commerce Service Center and Content Administration will not be discussed. Special attention will be paid to Oracle ATG Web Commerce-related technologies but most of the topics of discussion are outside of the application tier. For most approaches, very few changes must be made to Oracle ATG Web Commerce.