数据平台_Opentext__BOP_公司产品介绍.pptVIP

* * * Copyright ? 2013 Cordys Software B.V. All rights reserved. * * * * * * * * Chrome 1,2,3,4,5 FireFox 3, 3.5, 3.6 Safari 3, 4, 5 IE 8 Opera 10, 10.5, 10.6 * * * * * * * Cordys has implemented a document based transaction model, by using offline objects instead of statefull connections Native backend objects are transformed into statefull XML objects Objects are completely transferred to the service consumer (no virtual objects through proxies) Offline Objects can ‘live’ on their own Offline Objects do not need an application server to keep track of state and therefore provide a solution that is: - more scalable - higher-performing - less demanding in terms of hardware - much easier to apply fail-over (since providing status info to another apps server is not needed) Both .NET and J2EE are good platforms for developing and hosting business applications. Both support n-tier architectures via client- and server-side component models for assembling enterprise applications. This allows for use of either fat or thin user interfaces with both platforms. However, .NET and J2EE are far from identical, and each platform has distinct strengths. The primary strength of .NET is its use of multiple programming languages running on a single platform. This eliminates the programming language as a barrier for adoption. Further .NET strengths include ease of use and speed of development as programmers might be transitioning from COBOL or C. (In contrast, transitioning to Java usually takes greater skill in object orientation.) J2EE takes .NETs multiple programming-language/single-platform paradigm and turns it around: The primary strength of J2EE is its use of a single programming language capable of running on multiple platforms. This eliminates the platform as a barrier for adoption. Further J2EE strengths include vendor neutrality and the active involvement of a large, open-source community. From an integration standpoint, JDBC is actually more promising