OFBI and multi-tenant What is

What is a multi-tenant?

&http://www.aliyun.com/zixun/aggregation/37954.html >nbsp;   multi-tenant refers to a principle in the software architecture, That is, running a separate software instance on a single server to serve multiple customer organizations (tenants). Multiple tenants are opposed to multiple instances, which refer to individual software instances (or hardware systems) that serve different customer organizations. In a multi-tenant architecture, a software application is designed to be a virtual partition of data and configuration, with each client organization using a custom virtual application instance. Multi-Tenant is also considered one of the essential attributes of cloud computing.

    Cloud computing is a marketing term for technology that provides computing, software, data access, and storage services that end users do not need to know about the physical location and configuration of the system that provides the service.

    Cloud describes a new expansion, consumption, and delivery model for internet-based IT services, which typically involves providing dynamically scalable and visualized resources. It is a by-product of easy access to remote computers provided by the Internet. This may be the form of a network tool, or a form that a user can access and use through a Web browser, as if the program were installed on this computer. The

    ofbiz supported multi-tenant

    multi-tenant was introduced in OFBiz 927271. Multi-Tenant is the ability to run separate data instances (tenants) from a single copy of OFBiz. Each data instance is saved in a separate database that is assigned to the tenant. The user specifies the tenant ID in the form of a login form to log in to a data instance. Multiple configurations must be made to use OFBiz multi-tenant. This includes the definition of tenant data in the "Tenantdatasouces" entity, mainly because "the advantage of multi-tenant is that tenants do not have to use the ' ant Run installation ... ' or the tools on other command lines to access the load data. There may be hundreds of people active in other tenant instances, so you don't want to shut down or start a server to do something like this, and it's very likely that you can avoid having an administrator responsible for loading custom data for the tenant. You want to be self-service, and this is the key to making it a database-driven (with a user interface so that users can put things in the relevant parts of the database), set property variables so that users can see the "Tenant ID" in the login form, The configuration in the entity engine and the entries in the Ofbiz-component.xml to load the data. There are several commands available to load the leaseHousehold data. You have to carefully define different reader to load the data. We have tenant-specific delegator and define delegator we must follow the naming rules for ofbiz multi-tenant documents. OOTB Demo Tenant configuration data is specified by Derby, but other data sources can also be configured like mysql,oracle. We can set up e-business applications to use specific tenant databases, however, you must configure Web.xml. Tenant data loading and other configuration settings should be managed through a database rather than a configuration file, so that we do not have to shut down the server if new tenants are added or we need to load custom data for any tenant. This place needs more improvement.

    multi-tenant is a good addition to the OFBiz feature list. Because of the multi-tenant feature, OFBiz can now be well used as SaaS and will work better with cloud computing.
 

(editor: Heritage)