The article also discussed Epicor’s accompanying “Protect, Extend, and Converge” strategy for providing customers with a migration path choice on their own timetable and convenience. The article then continued on by digging deeper and explaining a number of enabling technologies and concepts within Epicor 9, starting with Epicor BPM (Business Process Management).
Part 2 of this blog series analyzes the major enabling concepts and technologies within the product, such as Epicor ICE 2.0, which is based on Epicor True SOA™, and includes the Epicor Everywhere Framework™. The article also digs deeper into the suite’s built-in business intelligence (BI) and enterprise performance management (EPM) capabilities.
ICE, ICE, Baby…
Let me step back here a bit, and start from the statement that Epicor ICE (Internet Component Environment) is the vendor’s overall agile and collaborative technology architecture blueprint. As said in Part 1, the framework leverages C#.NET- and Progress OpenEdge-based business logic.
Epicor ICE provides an adaptable foundation that can change as customers’ businesses change. The idea is to help align enterprise software with the business, make integration straightforward, and deliver ever-more business productivity. Epicor ICE was also devised with the idea of reducing the cost and complexity of technology adoption by being ready for business users from the word go.
For its part, Epicor True SOA™ is the architectural approach that Epicor ICE 2.0 offers; it is part of Epicor ICE and the technical model for Epicor 9. In other words, Epicor ICE is based on what the vendor refers to as “true SOA,” and applies the moniker for the following two main reasons:
1. The applications themselves are built with granular business services (or components and entities) that interact with one another and are then exposed using extensible markup language (XML) and Web services. Components can be easily configured and orchestrated using the Epicor BPM tools mentioned in Part 1, without requiring IT staff or coding, in a way that survives upgrades and avoids product version lock.
2. Epicor ICE is not just about service-oriented architecture (SOA) on the server side, but is also SOA for the client-side user experience (UX) design. The entire user interface (UI) is captured in XML metadata and the ICE tools allow users to easily customize and personalize the UI and run both a smart (rich) client and a browser-agnostic Web client from the same metadata (including users’ customizations and personalizations, which are stored in “layers” in the metadata).
Part 2 of this blog series analyzes the major enabling concepts and technologies within the product, such as Epicor ICE 2.0, which is based on Epicor True SOA™, and includes the Epicor Everywhere Framework™. The article also digs deeper into the suite’s built-in business intelligence (BI) and enterprise performance management (EPM) capabilities.
ICE, ICE, Baby…
Let me step back here a bit, and start from the statement that Epicor ICE (Internet Component Environment) is the vendor’s overall agile and collaborative technology architecture blueprint. As said in Part 1, the framework leverages C#.NET- and Progress OpenEdge-based business logic.
Epicor ICE provides an adaptable foundation that can change as customers’ businesses change. The idea is to help align enterprise software with the business, make integration straightforward, and deliver ever-more business productivity. Epicor ICE was also devised with the idea of reducing the cost and complexity of technology adoption by being ready for business users from the word go.
For its part, Epicor True SOA™ is the architectural approach that Epicor ICE 2.0 offers; it is part of Epicor ICE and the technical model for Epicor 9. In other words, Epicor ICE is based on what the vendor refers to as “true SOA,” and applies the moniker for the following two main reasons:
1. The applications themselves are built with granular business services (or components and entities) that interact with one another and are then exposed using extensible markup language (XML) and Web services. Components can be easily configured and orchestrated using the Epicor BPM tools mentioned in Part 1, without requiring IT staff or coding, in a way that survives upgrades and avoids product version lock.
2. Epicor ICE is not just about service-oriented architecture (SOA) on the server side, but is also SOA for the client-side user experience (UX) design. The entire user interface (UI) is captured in XML metadata and the ICE tools allow users to easily customize and personalize the UI and run both a smart (rich) client and a browser-agnostic Web client from the same metadata (including users’ customizations and personalizations, which are stored in “layers” in the metadata).
No comments:
Post a Comment