they are not related. olap has to do with data mining of what ever you want it is meant for reporting. http://en.wikipedia.org/wiki/OLAP_cube
Tenant has to do with multiple separate DBs using the same code base. Mike sent the following on 6/26/2012 9:10 AM:
Here is something that has always bugged me about the OFBiz setup, and I was hoping that an OFBiz old-timer can please explain why the above databases, by default, are configured as separate databases. I can see, in theory, why TENANT is separate. In the entityengine.xml, olap and tenant are separate databases. Is there any reason why the tables configured by these two databases, during initial deployment, can't be incorporated into the main ofbiz database? OLAP tables: public | currency_dimension | table | bigfish public | date_dimension | table | bigfish public | inventory_item_fact | table | bigfish public | product_dimension | table | bigfish public | sales_invoice_item_fact | table | bigfish public | sales_order_item_fact | table | bigfish TENANT tables: public | tenant | table | bigfish public | tenant_data_source | table | bigfish The reason I ask is when you are configuring the DB as external to the running OFBiz java process (not 127.0.0.1, and NOT derby), you now have to create and maintain 3 databases if you want to externalize the DB. I would rather just have to worry about a single database to replicate and backup. The multi-tenant feature of OFBiz is rather an advanced feature that most folks are not going to use, and in the event of going that route (multi-tenant), I could then externalize this database if necessary. Regarding OLAP, and why it is defined as a separate database is a real mystery to me. Can anyone please explain why it MAY be dangerous to merge the above tables into the main OFBiz database? Thanks
