共查询到17条相似文献,搜索用时 109 毫秒
1.
支持多类终端与服务定制的SaaS软件服务架构 总被引:2,自引:0,他引:2
由软件即服务(SaaS)模式中软件服务的概念与特点分析,可知现有的面向服务架构(SOA)不能完全支持软件服务的实现。此外,为了拓展软件服务的应用范围,实现多样化的服务,SaaS模式的软件服务必然要满足用户定制服务的需求,以及对多类用户终端的支持。通过对SOA的扩展,在其中引入了软件服务终端、软件服务端口、软件服务注册等模块,提出了一种支持多类终端与服务定制的SaaS软件服务架构,给出了该架构的结构与工作流程,并通过实验证明了该架构可以实现SaaS模式的软件服务,而且能够实现对上述功能需求的支持。 相似文献
2.
3.
随着计算机应用系统的飞速发展,应用环境、实现流程和组成模块日趋复杂,记录应用软件运行状态的日志功能越发重要。在分析了国际上主要日志系统功能的基础上,针对我们在开发大型遥感数据预处理系统过程中遇到的系统调试、过程追踪、状态记录等问题以及遥感数据处理的特点,提出并设计了一套完整的日志解决方案。该方案基于国际上通用的日志软件Log4J的系统架构,针对GHIPS系统特点,进行了必要的功能封装、数据库扩展等改进,设计了较为完整的适合GHIPS开发与运行要求的日志子系统。实验表明,该日志系统能够实现GHIPS所需的记录与追踪功能,同时可方便地实现日志的搜索、整理、报表生成等特殊要求。 相似文献
4.
在编程时,经常会使用到一些日志操作,在开发阶段,需要大量的调试语句,在开发完成时需要查找并移除。程序部署后,还经常会需要有一些维护调试和进行一些繁琐的日志工作。本文介绍了Log4J(LogForJava)的使用。Log4J用Java编写的优秀日志工具包。通过Log4J可以在不修改代码的情况下,方便、灵活地控制任意粒度的日志信息的开启或关闭,然后使用定制的格式,把日志信息输出到一个或多个需要的地方。 相似文献
5.
一种面向SaaS多租户的多层模型 总被引:1,自引:0,他引:1
SaaS(Software as a Service)伴随云计算而出现,它与传统软件的区别较大。根据SaaS软件的特点,提出支持SaaS软件成熟度的SaaS软件分层元模型,使用形式化方法对每一层进行建模描述。受面向对象Petri网(Object-Oriented Petri Nets,OOPN)和有色Petri网(Colored Petri Nets,CPN)思想的启发,提出面向服务网结构SOP(Service-Oriented Petri Nets)和CSOP(Colored Service-Oriented Petri Nets)。一方面,使用封装的库所元素代表服务,体现了服务对外不可见,且内部结构影响系统运行。另一方面,不同的颜色集代表不同租户请求,突出了SaaS多租户的特点。这不仅为复杂的SaaS软件建模提供了方法,还能够折叠系统变迁,压缩状态空间。最后,以一个 客户关系管理 (Customer Relationship Management,CRM)SaaS软件系统为例,验证了文中工作的可行性。 相似文献
6.
SaaS模式作为云计算模式之一,有着多租户且可配置的特点。SaaS模式较好地解决了软件架构在扩展能力与资源共享等方面存在的问题。在研究中以SaaS信息系统架构在数据存储层与访问控制层方面所进行的分析为基础,确定了多稀疏表和键值对结合的模型,探讨了该模型所具有的优势。该研究对优化我国信息系统架构有一定的参考作用。 相似文献
7.
针对中小企业资金缺乏、IT人才较少等问题,本文对传统软件向SaaS软件转型关键技术进行研究,提出了SaaS软件关键技术的解决方案以及七层架构模型。 相似文献
8.
对SaaS服务模式及IT资产管理的现状进行了一定的研究,然后将SaaS应用模式结合IT资产管理得到基于SaaS的IT资产管理系统。对系统架构、功能、安全方案和商业模式进行探讨,提出了实现SaaS模式下的IT资产管理系统的系统方案,该方案的目标是实现SaaS第三级成熟度模型,考虑用基于Rabin密码体制的一次性口令身份认证方案,并且部署在软件服务平台上。 相似文献
9.
10.
在编程时,经常会使用到一些日志操作,在开发阶段,需要大量的调试语句,在开发完成时需要查找并移除。程序部署后,还经常会需要有一些维护调试和进行一些繁琐的日志工作。本文介绍了Log4J(Log For Java)的使用。Log4J用JaVa编写的优秀日志工具包。通过Log4J可以在不修改代码的情况下,方便、灵活地控制任意粒度的日志信息的开启或关闭,然后使用定制的格式,把日志信息输出到一个或多个需要的地方。 相似文献
11.
SaaS模式作为云计算的一种形式,在互联网技术的发展和应用软件成熟的基础上,成为一种创新的软件应用模式。如何保证系统安全与设计高效安全的数据架构是决定SaaS应用成败的关键问题。本文将以基于SaaS的政务系统为业务依托,以数据库设计和系统安全、SoA为理论基础,提出STEG解决方案。此解决方案在SaaS软件中能很好的解决数据建模、系统安全和软件架构方面的问题,对SaaS下的软件研究具有深刻借鉴意义。 相似文献
12.
Software-as-a-service (SaaS) has received significant attention recently as one of three principal components of cloud computing, and it often deals with applications that run on top of a platform-as-a-service (PaaS) that in turn runs on top of infrastructure-as-a-service (IaaS). This paper provides an overview of SaaS including its architecture and major technical issues such as customization, multi-tenancy architecture, redun- dancy and recovery mechanisms, and scalability. Specifically, a SaaS system can have architecture relating to a database-oriented approach, middleware-oriented approach, service-oriented approach, or PaaS-oriented ap- proach. Various SaaS customization strategies can be used from light customization with manual coding to heavy customization where the SaaS system and its underlying PaaS systems are customized together. Multi-tenancy architecture is an important feature of a SaaS and various trade-offs including security isolation, performance, and engineering effort need to be considered. It is important for a SaaS system to have multi-level redundancy and recovery mechanisms, and the SaaS system needs to coordinate these with the underlying PaaS system. Finally, SaaS scalability mechanisms include a multi-level architecture with load balancers, automated data migration, and software design strategies. 相似文献
13.
Wei-Tek Tsai Yu Huang Qihong Shao Xiaoying Bai 《International Journal of Software and Informatics》2010,4(4):437-471
Software-as-as-Service (SaaS) is a new approach for developing software, and it is characterized by its multi-tenancy architecture and its ability to provide flexible customization to individual tenant. However, the multi-tenancy architecture and customization requirements introduce many new issues in software, such as database design, database
partition, scalability, recovery, and continuous testing. This paper proposes a hybrid test database design to support SaaS customization with two-layer database partitioning. The database is further extended with a new built-in redundancy with ontology so that the SaaS can recover from ontology, data or metadata failures. Furthermore, constraints in metadata can be used either as test cases or policies to support SaaS continuous testing and policy
enforcement. 相似文献
14.
基于SaaS的网络管理系统框架研究 总被引:1,自引:0,他引:1
在分析4种SaaS模式的基础上,提出一种"多租赁单位-单实例进程"的SaaS网管系统模式。围绕此模式,研究了SaaS网管系统的架构与软件框架,对系统的代理程序I、nternet接口、应用中心3部分进行了设计,给出了数据采集、异构传输、数据隔离、个性定制的解决方案。该框架被应用于某实际网管系统软件,系统软件运行于南通大学,为南通市环保局、南通市软件工程研究所等单位提供网络管理租赁服务。实例运行结果表明,它完全达到了预期设计目标,其模式、架构与解决方案是可行的。 相似文献
15.
Wei-Tek Tsai Guanqiu Qi Zhiqin Zhu 《International Journal of Software and Informatics》2013,7(1):63-84
Software-as-a-Service (SaaS) is a new software delivery model with Multi-Tenancy Architecture (MTA). An SaaS system is often mission critical as it often supports a large number of tenants, and each tenant supports a large number of users. This paper proposes a scalable index management algorithm based on B+ tree but with automated redundancy and recovery management as the tree maintains two copies of data. The redundancy and recovery management is done at the SaaS level as data are duplicated with tenant information rather than at the PaaS level where data are duplicated in chunks. Using this approach, an SaaS system can scale out or in based on the dynamic workload. This paper also uses tenant similarity measures to cluster tenants in a multi-level scalability architecture where similar tenants can be grouped together for effcient processing. The scalability mechanism also includes an automated migration strategies to enhance the SaaS performance. The proposed scheme with automated recovery and scalability has been simulated, the results show that the proposed algorithm can scale well with increasing workloads. 相似文献
16.
What's in a Name? Distinguishing between SaaS and SOA 总被引:1,自引:0,他引:1
Considerable confusion arises in distinguishing between software as a service (SaaS) and service-oriented architecture (SOA). Zachman's framework can help to try to make sense of the alphabet soup of Web services and utilities that form the basis for both SOA and SaaS. The difference between SaaS and SOA is that the former is a software-delivery model whereas the latter is a software-construction model. A better way to illuminate the differences between these two concepts is to use the well-known Zachman architectural model. In this article, we briefly examine the concepts of SaaS and SOA, followed by a brief history of software architectural models. We use the Zachman model to differentiate the two architectural approaches to building software. Because the Zachman model is so intuitive, the approach we take to describe the differences between SaaS and SOA works well even with non-IT professionals. 相似文献