- 1 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 2 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 3 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 4 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
- 5 Docker Reaches Across Universes at Dockercon EU
ATG Offers Dynamo on BEA WebLogic
If all goes as planned, ATG will offer Dynamo customers and partners the flexibility to develop and deploy ATG applications that run on Dynamo and other leading J2EE application servers, including BEA WebLogic Server.ATG Monday released ATG Dynamo for BEA WebLogic Server. With this release, ATG makes strides toward fulfilling the application server strategy it outlined last summer.
ATG first announced plans to deploy its entire application suite on the leading J2EE Web application servers in July 2001.
BEA WebLogic Server is the first third-party application server to be supported by ATG (although last September the company announced it would deploy Dynamo on IBM's WebSphere Application Server). WebLogic works with ATG Dynamo version 5.6, ATG Enterprise Portal, and Enterprise Commerce Suites to enable enterprises to optimize their infrastructure investments with advanced application deployment and support.
Participants in the beta test program included Charles Schwab, KPMG Germany, and Hoffman LaRoche.
"Our customers want to fully utilize their existing infrastructure investments while deploying advanced e-business applications," said Joe Chung, co-founder and chairman of ATG. "BEA WebLogic customers now have the flexibility to do this by running our online CRM applications on their BEA infrastructure."
Rauline Ochs, senior vice president of worldwide strategic alliances for BEA added, "The availability of ATG applications on BEA WebLogic illustrates how customers can build, extend, and integrate all of their e-business applications on BEA WebLogic. The alliance is another effort to provide our customers with best-of-breed solutions for a total e-business solution."
Reprinted from ServerWatch