E.piphany Strikes Deals With IBM and BEA Systems
Updated · Jan 15, 2003
Looking to meet customer demand for an open-standards based customer relationship management (CRM) solution, E.piphany Inc. , a San Mateo, Calif.-based provider of CRM software, today announced that it has entered into agreements to integrate IBM's WebSphere and BEA Systems' WebLogic J2EE application servers into the E.piphany E.6 platform.
According to E.piphany, the integration combines its CRM suite — which features integrated sales, marketing, service and analytic capabilities — with WebSphere and WebLogic servers to create an option for a single-source, J2EE-based CRM solution for businesses that want to standardize their IT environments on component-based architectures.
In addition to integrating IBM WebSphere into the E.piphany E.6 platform, E.piphany reports that it is furthering its commitment to component-based CRM by optimizing the E.piphany E.6 software suite for IBM's entire e-business infrastructure.
E.piphany said its component-based design E.6 software suite can be implemented as building blocks, allowing customers to purchase and deploy incrementally. Applications built on component-based architectures are designed to be able to communicate with other components, applications or external functionality via Web services.
By integrating the E.piphany E.6 platform with the industry's leading application servers, “we are able to give customers a single-source solution offering deployment flexibility and functional extensibility via J2EE standards and Web services,” said Phil Fernandez, executive vice president of products and marketing at E.piphany.
Fernandez said that unlike CRM providers who rely on proprietary application networks “today's news helps us extend our leadership in open-standards CRM while our competitors are left to struggle with architectural re-design issues around how to move to a component architecture.”
BEA Systems and IBM are listed by ASPnews Top 30 Service Enablers.
Do you have a comment or question about this article or the ASP industry in general? Speak out in the ASP Discussion Forum.