Enterprise Financial Information Delivery System Design And Security Implementation

With the development of information technology and the process of enterprise information delivery system, enterprises more and more depend on the enterprise information delivery system. While the enterprise information delivery system improves the information delivery across multi areas and departments, as well as the efficiency of the enterprise, it also cuts the cost of enterprises. But, the development of a high security enterprise information delivery system is not as easy as we expect. Especially for those corporations of special area, such as bank, financial corporation and so on, the security of the enterprise information system is the key feature. Any failure of enterprise application system will cause inestimable damage.This paper will open a research to address the issues for constructing the enterprise information delivery system based on a case study with SSZUTC. Utilizing the J2EE architecture and core design patterns, design and implement an enterprise information delivery system. And also introduce the security implementation based on SiteMinder/LDAP security framework, with security integration on authentication, authorization and Single Sign-On, with Actuate Report Server and so on.In the system architecture design, based on the MVC framework, many core J2EE design patterns are used in the system, such as, in the presentation tier, context object design pattern, front-end filter design pattern, in business tier, proxy design pattern, service factory design pattern, and singleton design pattern, in resource integration tier, data access object (DAO) design pattern. In the system architecture, the security integration is implemented based on SiteMinder/LDAP, Actuate Report Server Security Extension (RSSE) and Actuate Active Portal Security Extension (APSE).Besides, the conclusion section also discusses the security improvement suggestion base on the user and administrator training to prevent the security issues, except for technical factors, and also some suggestion for mutual authentication and building a high performance and open scalable reporting framework.