Re: How should new committers handle backporting?
I mean contributors don't need to backport (COMMIT) patches from OFBiz trunk to OFBiz branches... Jacques Le 21/05/2015 09:33, Pierre Smits a écrit : Please remember that committers are contributors with privileges. So wouldn't it concern them? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, May 21, 2015 at 9:21 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: I don't think contributors are really concerned, will you handle the wiki update? Jacques Le 19/05/2015 15:52, Michael Brohl a écrit : +1, very helpful, just trying it out. Maybe https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices would be a better place, or we would add a link to one of the pages. Michael Brohl ecomify GmbH www.ecomify.de Am 19.05.15 um 15:38 schrieb Jacques Le Roux: Maybe we should add it at https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities ? Jacques Le 19/05/2015 14:19, Pranay Pandey a écrit : Thanks Jacopo, its a good OFBiz Committers Guide. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ skype: pranay.pandey cell: +91 982.603.5576 On Tue, May 19, 2015 at 10:52 AM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: Hi Christian, On May 19, 2015, at 3:37 AM, Christian Carlow christian.car...@gmail.com wrote: Should committers download the entire ofbiz repository to help with backporting? it is easier if you keep the trunk and the release branches in different svn folders (i.e. different checkouts); for example: mkdir ofbiz cd ofbiz svn co https://svn.apache.org/repos/asf/ofbiz/trunk trunk svn co https://svn.apache.org/repos/asf/ofbiz/branches/release14.12 release14.12 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release13.07 release13.07 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release12.04 release12.04 svn co https://svn.apache.org/repos/asf/ofbiz/site/ website you will end up with the following folder layout: ofbiz/ ofbiz/trunk ofbiz/release14.12 ofbiz/release13.07 ofbiz/release12.04 ofbiz/website Then you can setup, with your favorite IDE, one project for each. Is there a standard procedure new committers should follow for backporting? Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 1) commit the fix to trunk and note down the commit id; e.g. rev 12345 2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12 3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345 4) run the tests with: ./tools/mergefromtrunk.sh/bat test 5) it is also a good idea to start the instance and test manually 6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort 6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit I was going to test my new committer privilege by applying my OFBIZ-6387.patch. Should I apply it to the release branches also? That is probably not a bug but it is a small change and could be a good chance to practice with the above process, so please do if you like. Regards, Jacopo
Re: How should new committers handle backporting?
Yes, that's right. I'll handle the update on the Wiki, place it on the committers page you suggested and see if I can place a link on the other page when it fits. Michael Am 21.05.15 um 09:53 schrieb Jacques Le Roux: I mean contributors don't need to backport (COMMIT) patches from OFBiz trunk to OFBiz branches... Jacques Le 21/05/2015 09:33, Pierre Smits a écrit : Please remember that committers are contributors with privileges. So wouldn't it concern them? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, May 21, 2015 at 9:21 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: I don't think contributors are really concerned, will you handle the wiki update? Jacques Le 19/05/2015 15:52, Michael Brohl a écrit : +1, very helpful, just trying it out. Maybe https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices would be a better place, or we would add a link to one of the pages. Michael Brohl ecomify GmbH www.ecomify.de Am 19.05.15 um 15:38 schrieb Jacques Le Roux: Maybe we should add it at https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities ? Jacques Le 19/05/2015 14:19, Pranay Pandey a écrit : Thanks Jacopo, its a good OFBiz Committers Guide. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ skype: pranay.pandey cell: +91 982.603.5576 On Tue, May 19, 2015 at 10:52 AM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: Hi Christian, On May 19, 2015, at 3:37 AM, Christian Carlow christian.car...@gmail.com wrote: Should committers download the entire ofbiz repository to help with backporting? it is easier if you keep the trunk and the release branches in different svn folders (i.e. different checkouts); for example: mkdir ofbiz cd ofbiz svn co https://svn.apache.org/repos/asf/ofbiz/trunk trunk svn co https://svn.apache.org/repos/asf/ofbiz/branches/release14.12 release14.12 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release13.07 release13.07 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release12.04 release12.04 svn co https://svn.apache.org/repos/asf/ofbiz/site/ website you will end up with the following folder layout: ofbiz/ ofbiz/trunk ofbiz/release14.12 ofbiz/release13.07 ofbiz/release12.04 ofbiz/website Then you can setup, with your favorite IDE, one project for each. Is there a standard procedure new committers should follow for backporting? Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 1) commit the fix to trunk and note down the commit id; e.g. rev 12345 2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12 3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345 4) run the tests with: ./tools/mergefromtrunk.sh/bat test 5) it is also a good idea to start the instance and test manually 6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort 6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit I was going to test my new committer privilege by applying my OFBIZ-6387.patch. Should I apply it to the release branches also? That is probably not a bug but it is a small change and could be a good chance to practice with the above process, so please do if you like. Regards, Jacopo smime.p7s Description: S/MIME Cryptographic Signature
Re: How should new committers handle backporting?
I don't think contributors are really concerned, will you handle the wiki update? Jacques Le 19/05/2015 15:52, Michael Brohl a écrit : +1, very helpful, just trying it out. Maybe https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices would be a better place, or we would add a link to one of the pages. Michael Brohl ecomify GmbH www.ecomify.de Am 19.05.15 um 15:38 schrieb Jacques Le Roux: Maybe we should add it at https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities ? Jacques Le 19/05/2015 14:19, Pranay Pandey a écrit : Thanks Jacopo, its a good OFBiz Committers Guide. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ skype: pranay.pandey cell: +91 982.603.5576 On Tue, May 19, 2015 at 10:52 AM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: Hi Christian, On May 19, 2015, at 3:37 AM, Christian Carlow christian.car...@gmail.com wrote: Should committers download the entire ofbiz repository to help with backporting? it is easier if you keep the trunk and the release branches in different svn folders (i.e. different checkouts); for example: mkdir ofbiz cd ofbiz svn co https://svn.apache.org/repos/asf/ofbiz/trunk trunk svn co https://svn.apache.org/repos/asf/ofbiz/branches/release14.12 release14.12 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release13.07 release13.07 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release12.04 release12.04 svn co https://svn.apache.org/repos/asf/ofbiz/site/ website you will end up with the following folder layout: ofbiz/ ofbiz/trunk ofbiz/release14.12 ofbiz/release13.07 ofbiz/release12.04 ofbiz/website Then you can setup, with your favorite IDE, one project for each. Is there a standard procedure new committers should follow for backporting? Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 1) commit the fix to trunk and note down the commit id; e.g. rev 12345 2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12 3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345 4) run the tests with: ./tools/mergefromtrunk.sh/bat test 5) it is also a good idea to start the instance and test manually 6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort 6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit I was going to test my new committer privilege by applying my OFBIZ-6387.patch. Should I apply it to the release branches also? That is probably not a bug but it is a small change and could be a good chance to practice with the above process, so please do if you like. Regards, Jacopo
Re: How should new committers handle backporting?
Please remember that committers are contributors with privileges. So wouldn't it concern them? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, May 21, 2015 at 9:21 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: I don't think contributors are really concerned, will you handle the wiki update? Jacques Le 19/05/2015 15:52, Michael Brohl a écrit : +1, very helpful, just trying it out. Maybe https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Contributors+Best+Practices would be a better place, or we would add a link to one of the pages. Michael Brohl ecomify GmbH www.ecomify.de Am 19.05.15 um 15:38 schrieb Jacques Le Roux: Maybe we should add it at https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Committers+Roles+and+Responsibilities ? Jacques Le 19/05/2015 14:19, Pranay Pandey a écrit : Thanks Jacopo, its a good OFBiz Committers Guide. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ skype: pranay.pandey cell: +91 982.603.5576 On Tue, May 19, 2015 at 10:52 AM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: Hi Christian, On May 19, 2015, at 3:37 AM, Christian Carlow christian.car...@gmail.com wrote: Should committers download the entire ofbiz repository to help with backporting? it is easier if you keep the trunk and the release branches in different svn folders (i.e. different checkouts); for example: mkdir ofbiz cd ofbiz svn co https://svn.apache.org/repos/asf/ofbiz/trunk trunk svn co https://svn.apache.org/repos/asf/ofbiz/branches/release14.12 release14.12 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release13.07 release13.07 svn co https://svn.apache.org/repos/asf/ofbiz/branches/release12.04 release12.04 svn co https://svn.apache.org/repos/asf/ofbiz/site/ website you will end up with the following folder layout: ofbiz/ ofbiz/trunk ofbiz/release14.12 ofbiz/release13.07 ofbiz/release12.04 ofbiz/website Then you can setup, with your favorite IDE, one project for each. Is there a standard procedure new committers should follow for backporting? Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 1) commit the fix to trunk and note down the commit id; e.g. rev 12345 2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12 3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345 4) run the tests with: ./tools/mergefromtrunk.sh/bat test 5) it is also a good idea to start the instance and test manually 6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort 6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit I was going to test my new committer privilege by applying my OFBIZ-6387.patch. Should I apply it to the release branches also? That is probably not a bug but it is a small change and could be a good chance to practice with the above process, so please do if you like. Regards, Jacopo
Re: Multi-Tenant with MySQL or Postgress - Working?
Hi Fernando. Multi-tenancy has been around since prior r12.x. And is working with both PostgreSQL and MySQL. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, May 21, 2015 at 4:34 AM, FGomez fgo...@mail.com wrote: Hi All, I wanted to know if anyone has Multi-tenant running in production (or dev) with more then 3 tenants/clients with PostgreSql or mySql DBs? With v13.07 or v14.12 ( I believe the domain on the script is only available with the 'ant create-tenant' on v14.12 only). Thanks you for the feedback. Regards, Fernando
Re: Multi-Tenant with MySQL or Postgress - Working?
More accurately multi-tenancy has been introduced in trunk in February 2010 and has been continuously improved since. It works with all the DBMSs you can fiund in the EntityEngine.xml file. The number of tenants depends on the material resources, not the code. It's not a solution to scale above thousands tough (you need a DB by tenant...) This limitation comes with the obvious advantages of having separated DBs. You can find details about these advantages on the Net, notably when it comes to backups things and guarantee access separation... Jacques Le 21/05/2015 07:59, Pierre Smits a écrit : Hi Fernando. Multi-tenancy has been around since prior r12.x. And is working with both PostgreSQL and MySQL. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, May 21, 2015 at 4:34 AM, FGomez fgo...@mail.com wrote: Hi All, I wanted to know if anyone has Multi-tenant running in production (or dev) with more then 3 tenants/clients with PostgreSql or mySql DBs? With v13.07 or v14.12 ( I believe the domain on the script is only available with the 'ant create-tenant' on v14.12 only). Thanks you for the feedback. Regards, Fernando
Re: Using OFBiz with DB2 for i (AS400) database
I propose we copy those params into EntityEngine.xml (with a comment about Since version V7R1 (AS/400, db2)) Could you please confirm you did not cross issues later Robert? We would need also to download the JDBC driver with Ant+Ivy... Jacques Le 14/04/2015 13:37, robertpic a écrit : FYI We have installed Apache Ofbiz on Debian 7 (Wheezy) and use DB2 for i AS/400 as database. Since version V7R1 (AS/400, db2) there is no need for an own fieldtype.xml - just use the derby-fieldtypes like this: datasource name=devdb2 helper-class=org.ofbiz.entity.datasource.GenericHelperDAO schema-name=OFBIZ field-type-name=derby check-on-start=true add-missing-on-start=true use-pk-constraint-names=false use-indices-unique=false alias-view-columns=false use-order-by-nulls=true offset-style=fetch read-data reader-name=tenant/ read-data reader-name=seed/ read-data reader-name=seed-initial/ read-data reader-name=demo/ read-data reader-name=ext/ read-data reader-name=ext-test/ read-data reader-name=ext-demo/ inline-jdbc jdbc-driver=com.ibm.as400.access.AS400JDBCDriver jdbc-uri=jdbc:as400:192.168.1.10;prompt=false;libraries=ofbiz;lazy close=true;translate binary=true jdbc-username=OFBIZUSR jdbc-password=*** isolation-level=ReadCommitted pool-minsize=2 pool-maxsize=250 time-between-eviction-runs-millis=60/ /datasource I've copied the jdbc parms (lazy close...) from my hibernate projects. I'll check this later. The demo and our first steps running without problems. Important: - You have the create the schemas manually. (Gabriel wrote this already) - the codepage of the user (in my case OFBIZUSR) is used for the create table (CCSID) -- actually we use an ebcdic codepage, this allow green screen programs to access the data with native database commands -- View this message in context: http://ofbiz.135035.n4.nabble.com/Using-OFBiz-with-DB2-for-i-AS400-database-tp4650633p4666589.html Sent from the OFBiz - User mailing list archive at Nabble.com.
Re: Using OFBiz with DB2 for i (AS400) database
Jacques Le Roux wrote I propose we copy those params into EntityEngine.xml (with a comment about Since version V7R1 (AS/400, db2)) I wrote since V7R1, because our AS/400 has V7R1 installed. I've checked the docs and find out, that DOUBLE should work at least at version V6R1. I could not test it, but the docs say DOUBLE is ok. Note: Only the fieldtype is problem in early releases. All other stuff (JDBC parameters...) should be the same in all releases. Jacques Le Roux wrote Could you please confirm you did not cross issues later Robert? We have not any problems so far. FLOAT and DOUBLE mean the same for DB2/AS400. I have to say: We don't use any ERP functions and the ecommerce-project is on an early stage (~ 15 products). But i have not any problems with float/double in may other projects. Jacques Le Roux wrote We would need also to download the JDBC driver with Ant+Ivy... I'm not sure about Ant+Ivy. There is an open source version of the jdbc driver at sourceforge: http://sourceforge.net/projects/jt400/ About our project: Actually we try to migrate our existing 40.000 products (online-catalog) http://online.odoerfer.com/OdKatalog/ into OfBiz. But we have also to record the 30.000 ERP-only producs. So I expect a Go-Live between Q4/2015 - Q1/2016. -- View this message in context: http://ofbiz.135035.n4.nabble.com/Using-OFBiz-with-DB2-for-i-AS400-database-tp4650633p4668827.html Sent from the OFBiz - User mailing list archive at Nabble.com.
Re: Ofbiz search engine
Hi Tom, I’ve seen a solution for this with a combination of OFBiz and solr using the Tika library to index document contents. See here: https://tika.apache.org This could be a nice todo in addition to the not yet finished solr integration issue OFBIZ-5042, maybe I will investigate it a bit in the near future... Regards, Martin Becker ecomify GmbH www.ecomify.de Am 20.05.2015 um 21:49 schrieb Tom Running runningt...@gmail.com: Taher and Jacques, Thank you for the information. I am wondering if anyone has attempt to integrate such features to Ofbiz? Love to hear and share your opinion. -T On Mon, May 18, 2015 at 1:58 PM, Taher Alkhateeb slidingfilame...@gmail.com wrote: Hi Tom, I believe what you are looking for is a very custom solution that does not come out of the box with OFBiz. I think you should take a look at apache POI (http://poi.apache.org/) and apache lucene (https://lucene.apache.org/). Together you can use both solutions to access microsoft documents and index them for searching. Another workaround is to integrate with a document management system that supports indexed search of binary documents. There are many open source solutions out there that live on the JVM. Regards, - Original Message - From: Tom Running runningt...@gmail.com To: user@ofbiz.apache.org Sent: Monday, 18 May, 2015 8:32:48 PM Subject: Ofbiz search engine Can Ofbiz be use for the following requirement? How can I go about achieving this with Ofbiz? I have a folder with Microsoft Word and pdf document format. Can I leveraging Ofbiz to search the contents of these documents, find it then allow to view it? Search and find key words that exist or matched for each document then map that to that document for view. FYI, I posted this question before but some how I can not find it. So, I repost it again. Thanks, -T
Re: Using OFBiz with DB2 for i (AS400) database
Thanks Robert, I will document on this basis Jacques Le 21/05/2015 14:35, robertpic a écrit : Jacques Le Roux wrote I propose we copy those params into EntityEngine.xml (with a comment about Since version V7R1 (AS/400, db2)) I wrote since V7R1, because our AS/400 has V7R1 installed. I've checked the docs and find out, that DOUBLE should work at least at version V6R1. I could not test it, but the docs say DOUBLE is ok. Note: Only the fieldtype is problem in early releases. All other stuff (JDBC parameters...) should be the same in all releases. Jacques Le Roux wrote Could you please confirm you did not cross issues later Robert? We have not any problems so far. FLOAT and DOUBLE mean the same for DB2/AS400. I have to say: We don't use any ERP functions and the ecommerce-project is on an early stage (~ 15 products). But i have not any problems with float/double in may other projects. Jacques Le Roux wrote We would need also to download the JDBC driver with Ant+Ivy... I'm not sure about Ant+Ivy. There is an open source version of the jdbc driver at sourceforge: http://sourceforge.net/projects/jt400/ About our project: Actually we try to migrate our existing 40.000 products (online-catalog) http://online.odoerfer.com/OdKatalog/ into OfBiz. But we have also to record the 30.000 ERP-only producs. So I expect a Go-Live between Q4/2015 - Q1/2016. -- View this message in context: http://ofbiz.135035.n4.nabble.com/Using-OFBiz-with-DB2-for-i-AS400-database-tp4650633p4668827.html Sent from the OFBiz - User mailing list archive at Nabble.com.
Re: [DISCUSSION] OFBiz End User Wiki Documentation
http://blogs.atlassian.com/2010/11/technical_writing_wiki_single_source_publishing/ Great summary of how to use Confluence in an environment that includes a number of source formats and desired output. I use DITA for software docs and like the way that it integrates with Eclipse/STS. Ron On 21/05/2015 1:22 PM, Todd Thorner wrote: The key to minimizing effort is single-sourcing. That is the business requirement (maybe), now the community must settle on appropriate technologies. My opinion is that DocBook is obsolete. One non-committer vote for DITA. On 15-05-21 09:59 AM, Sharan-F wrote: Hi Everyone i'd like to put forward another proposal for discussion around the project End User Documentation. We know that we have incomplete documentation and need an active strategy to complete it. The help itself can be divided it into two distinct areas 1. Online / in Application Help *(NOTE*: A discussion for this has been started in another thread) 2. User Documentation on the Wiki * User Documentation on the Wiki * Our current End User Documentation is fragmented (End User Docs, Requirements and Designs, Wiki) and mixed in with various other documentation on the Wiki. Attempts have been made to create the documentation but the level of information required has been varied and unclear. Confluence is the Apache tool for managing wiki but it does have its limits that have caused frustration in the past. *Proposal* Our community surveys show that we don't have a lot of typical 'End Users' in our Community Base. The users that we do have are more 'Key Users' or 'Application Experts'. What I mean here is that they are users that understand their own business flows and are interested in knowing how to setup OFBiz for their business. Rather than be focussed on End Users – I think this documentation could be focussed on the 'Key Users' and giving them the information they need to configure or setup OFBiz for a business. As a possible guide it could contain the following: - business process flows - use cases - application guide (details and steps for implementing the process flow) - configuration instructions - tips and tricks - glossary - details about data loading (e.g seed or production data) *Key Benefit* Our user documentation has a clear purpose rather than trying to fulfill mulitple different roles Once again these are my initial thoughts so am very happy (and keen) to get feedback from the community (especially user) about this. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/DISCUSSION-OFBiz-End-User-Wiki-Documentation-tp4668872.html Sent from the OFBiz - User mailing list archive at Nabble.com. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
Re: Multi-Tenant with MySQL or Postgress - Working?
Jacques, Pierre and Arum Thanks for the technical answer. I agreed with the advantages of a DB per Tenant and the scalability of the HW infrastructure underneath . Hence the maintenance and support issues. I test with v14.12 and advise. Regards, Fernando Le 2015-05-21 03:09, Jacques Le Roux a écrit : More accurately multi-tenancy has been introduced in trunk in February 2010 and has been continuously improved since. It works with all the DBMSs you can fiund in the EntityEngine.xml file. The number of tenants depends on the material resources, not the code. It's not a solution to scale above thousands tough (you need a DB by tenant...) This limitation comes with the obvious advantages of having separated DBs. You can find details about these advantages on the Net, notably when it comes to backups things and guarantee access separation... Jacques Le 21/05/2015 07:59, Pierre Smits a écrit : Hi Fernando. Multi-tenancy has been around since prior r12.x. And is working with both PostgreSQL and MySQL. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, May 21, 2015 at 4:34 AM, FGomez fgo...@mail.com wrote: Hi All, I wanted to know if anyone has Multi-tenant running in production (or dev) with more then 3 tenants/clients with PostgreSql or mySql DBs? With v13.07 or v14.12 ( I believe the domain on the script is only available with the 'ant create-tenant' on v14.12 only). Thanks you for the feedback. Regards, Fernando
Catalog/Product Image Upload
Hi Folks, I've been looking at production setup for OFBiz and the one issue I'm getting stuck with is how to get uploaded catalog/product images distributed across all the servers in a LB/HA setup. I've looked at rsync, lsyncd, csync2, NFS, GlusterFS. I'm just wondering if anyone has any experience with any of these in production and can offer a recommendation? Maybe I'm missing a trick and there's a much easier way to get OFBiz to push files to all servers, and avoid a single-point-of-failure. Many thanks in advance. Jason
Re: Multi-Tenant with MySQL or Postgress - Working?
Thanks, Fernando, I look forward to overcoming a bit more of my ignorance by way of e-following your progress. On 15-05-21 08:20 AM, FGomez wrote: Jacques, Pierre and Arum Thanks for the technical answer. I agreed with the advantages of a DB per Tenant and the scalability of the HW infrastructure underneath . Hence the maintenance and support issues. I test with v14.12 and advise. Regards, Fernando Le 2015-05-21 03:09, Jacques Le Roux a écrit : More accurately multi-tenancy has been introduced in trunk in February 2010 and has been continuously improved since. It works with all the DBMSs you can fiund in the EntityEngine.xml file. The number of tenants depends on the material resources, not the code. It's not a solution to scale above thousands tough (you need a DB by tenant...) This limitation comes with the obvious advantages of having separated DBs. You can find details about these advantages on the Net, notably when it comes to backups things and guarantee access separation... Jacques Le 21/05/2015 07:59, Pierre Smits a écrit : Hi Fernando. Multi-tenancy has been around since prior r12.x. And is working with both PostgreSQL and MySQL. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Thu, May 21, 2015 at 4:34 AM, FGomez fgo...@mail.com wrote: Hi All, I wanted to know if anyone has Multi-tenant running in production (or dev) with more then 3 tenants/clients with PostgreSql or mySql DBs? With v13.07 or v14.12 ( I believe the domain on the script is only available with the 'ant create-tenant' on v14.12 only). Thanks you for the feedback. Regards, Fernando
Re: Catalog/Product Image Upload
I think you are looking for the ofbizContentUrl Freemarker macro. The idea is to put the static resources on a content server to get the resources from this unique server. Of course having LB/HA and rather a cluster for the content server is recommended... Jacques Le 21/05/2015 15:34, Jason RJ a écrit : Hi Folks, I've been looking at production setup for OFBiz and the one issue I'm getting stuck with is how to get uploaded catalog/product images distributed across all the servers in a LB/HA setup. I've looked at rsync, lsyncd, csync2, NFS, GlusterFS. I'm just wondering if anyone has any experience with any of these in production and can offer a recommendation? Maybe I'm missing a trick and there's a much easier way to get OFBiz to push files to all servers, and avoid a single-point-of-failure. Many thanks in advance. Jason
[DISCUSSION] OFBiz Online Documentation
I'd like to put forward a proposal for discussion around the project End User Documentation. We know that we have incomplete documentation and need an active strategy to complete it. The help itself can be divided it into two distinct areas 1. Online / in Application Help 2. User Documentation on the Wiki (NOTE: I will be starting another discussion thread around this) * Online / In Application Help* This is the help that appears when someone using OFBiz clicks the help icon. It is contextual and normally related to a screen that the user is on. It can describe what a screen is used for, the data to be entered or the use of a key, button or icon. Screens and menus can be changed so it needs to be flexible and customisable. Our current online help has been implemented using Docbook and the OFBiz CMS. I don't think that this currently works well because - it is too hard to keep up to date as each change needs to be submitted as a patch - you need to understand and create the new data items for the CMS for each page of documentation - existing items need to be linked into the correct place in the document hierarchy - the docbook implementation isn't complete and there are a lot standard tags that cannot be used *Proposal* We know that we have had limited contributions to the online help system and currently this has been significantly reduced. If we could make the online help more accessible to our community to update this could stimulate more interest in it. Rather than trying to maintain the online help as if it were code – could it be treated differently to allow a wider range of people to provide updates. As an example, I would like to find out if all the data from the online help : - could be extracted - imported into a more document oriented/friendly editing environment or application - updated by community members (who could be given access to create / update / edit details) - changes would be reviewed and approved - once approved the changes could be committed / the help could be re-imported back into OFBiz or just delivered as a separate package that could be easily loaded back into OFBiz *Potential Benefits* - Community Members could work and update it easily - Reviews could be done before the documents are accepted - Different languages could be supported - We could have versions of help for different OFBiz versions These are my initial thoughts so I'm happy to get any feedback or alternative suggestions for how we could solve our existing problems. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/DISCUSSION-OFBiz-Online-Documentation-tp4668869.html Sent from the OFBiz - User mailing list archive at Nabble.com.
[MARKETING] OFBiz Marketing Roadmap and Strategy
Hi All A while ago I created a Draft Marketing and Communications Roadmap on the wiki https://cwiki.apache.org/confluence/display/OFBIZ/Draft+Marketing+and+Communication+Roadmap https://cwiki.apache.org/confluence/display/OFBIZ/Draft+Marketing+and+Communication+Roadmap The main tasks identified at the time were as follows: 1. Manage OFBiz Product branding and brand re-alignment 2. Develop strategy to encourage more business users 3. Review and Update OFBiz website (technical and business focus) 4. Setup an online Demo tailored for business users 5. Develop a set of common generic marketing material (integrator independent) 6. Events and Conferences We have already done some work on regarding the branding and brand re-alignment, events (Apachecon) and also social media (Twitter, Blogging) but I'd really like to get things moving in other areas too so will be happy to get feedback (and hopefully participation) particularly from this mailing list on these topics. We will also be looking for people to help with general project and community marketing activities as follows: - Authors - to write marketing content - Proofreaders / Editors - to review drafts and improve them - Graphic Artists / Designers - to design graphics and layout - Website Designers - to help re-design OFBiz website - Translators - to take documents and translate them into other languages - Wikipedia Authors - to create, review and update wikipedia related content - Social Media - to help promote and create awareness on social media - Speakers - to present or deliver OFBiz related talks at conferences or Open Source events so if you'd like to volunteer for any of the roles, please add your name to the table on the wiki page. One of the areas I'd really like to start with is a review and potential re-design of our main website so I will be starting a range of discussion threads so please watch out for them). Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/MARKETING-OFBiz-Marketing-Roadmap-and-Strategy-tp4668867.html Sent from the OFBiz - User mailing list archive at Nabble.com.
Re: [DISCUSSION] OFBiz Online Documentation
I'm willing to pitch in, but as I stated in a message earlier today I'm still rather ignorant about OFBiz (I've had zero free time to take the figurative plunge). First and foremost for documentation: single-sourcing and DITA/DocBook. Discuss ... On 15-05-21 09:45 AM, Sharan-F wrote: I'd like to put forward a proposal for discussion around the project End User Documentation. We know that we have incomplete documentation and need an active strategy to complete it. The help itself can be divided it into two distinct areas 1. Online / in Application Help 2. User Documentation on the Wiki (NOTE: I will be starting another discussion thread around this) * Online / In Application Help* This is the help that appears when someone using OFBiz clicks the help icon. It is contextual and normally related to a screen that the user is on. It can describe what a screen is used for, the data to be entered or the use of a key, button or icon. Screens and menus can be changed so it needs to be flexible and customisable. Our current online help has been implemented using Docbook and the OFBiz CMS. I don't think that this currently works well because - it is too hard to keep up to date as each change needs to be submitted as a patch - you need to understand and create the new data items for the CMS for each page of documentation - existing items need to be linked into the correct place in the document hierarchy - the docbook implementation isn't complete and there are a lot standard tags that cannot be used *Proposal* We know that we have had limited contributions to the online help system and currently this has been significantly reduced. If we could make the online help more accessible to our community to update this could stimulate more interest in it. Rather than trying to maintain the online help as if it were code – could it be treated differently to allow a wider range of people to provide updates. As an example, I would like to find out if all the data from the online help : - could be extracted - imported into a more document oriented/friendly editing environment or application - updated by community members (who could be given access to create / update / edit details) - changes would be reviewed and approved - once approved the changes could be committed / the help could be re-imported back into OFBiz or just delivered as a separate package that could be easily loaded back into OFBiz *Potential Benefits* - Community Members could work and update it easily - Reviews could be done before the documents are accepted - Different languages could be supported - We could have versions of help for different OFBiz versions These are my initial thoughts so I'm happy to get any feedback or alternative suggestions for how we could solve our existing problems. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/DISCUSSION-OFBiz-Online-Documentation-tp4668869.html Sent from the OFBiz - User mailing list archive at Nabble.com.
[DISCUSSION] OFBiz End User Wiki Documentation
Hi Everyone i'd like to put forward another proposal for discussion around the project End User Documentation. We know that we have incomplete documentation and need an active strategy to complete it. The help itself can be divided it into two distinct areas 1. Online / in Application Help *(NOTE*: A discussion for this has been started in another thread) 2. User Documentation on the Wiki * User Documentation on the Wiki * Our current End User Documentation is fragmented (End User Docs, Requirements and Designs, Wiki) and mixed in with various other documentation on the Wiki. Attempts have been made to create the documentation but the level of information required has been varied and unclear. Confluence is the Apache tool for managing wiki but it does have its limits that have caused frustration in the past. *Proposal* Our community surveys show that we don't have a lot of typical 'End Users' in our Community Base. The users that we do have are more 'Key Users' or 'Application Experts'. What I mean here is that they are users that understand their own business flows and are interested in knowing how to setup OFBiz for their business. Rather than be focussed on End Users – I think this documentation could be focussed on the 'Key Users' and giving them the information they need to configure or setup OFBiz for a business. As a possible guide it could contain the following: - business process flows - use cases - application guide (details and steps for implementing the process flow) - configuration instructions - tips and tricks - glossary - details about data loading (e.g seed or production data) *Key Benefit* Our user documentation has a clear purpose rather than trying to fulfill mulitple different roles Once again these are my initial thoughts so am very happy (and keen) to get feedback from the community (especially user) about this. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/DISCUSSION-OFBiz-End-User-Wiki-Documentation-tp4668872.html Sent from the OFBiz - User mailing list archive at Nabble.com.
Re: [DISCUSSION] OFBiz End User Wiki Documentation
The key to minimizing effort is single-sourcing. That is the business requirement (maybe), now the community must settle on appropriate technologies. My opinion is that DocBook is obsolete. One non-committer vote for DITA. On 15-05-21 09:59 AM, Sharan-F wrote: Hi Everyone i'd like to put forward another proposal for discussion around the project End User Documentation. We know that we have incomplete documentation and need an active strategy to complete it. The help itself can be divided it into two distinct areas 1. Online / in Application Help *(NOTE*: A discussion for this has been started in another thread) 2. User Documentation on the Wiki * User Documentation on the Wiki * Our current End User Documentation is fragmented (End User Docs, Requirements and Designs, Wiki) and mixed in with various other documentation on the Wiki. Attempts have been made to create the documentation but the level of information required has been varied and unclear. Confluence is the Apache tool for managing wiki but it does have its limits that have caused frustration in the past. *Proposal* Our community surveys show that we don't have a lot of typical 'End Users' in our Community Base. The users that we do have are more 'Key Users' or 'Application Experts'. What I mean here is that they are users that understand their own business flows and are interested in knowing how to setup OFBiz for their business. Rather than be focussed on End Users – I think this documentation could be focussed on the 'Key Users' and giving them the information they need to configure or setup OFBiz for a business. As a possible guide it could contain the following: - business process flows - use cases - application guide (details and steps for implementing the process flow) - configuration instructions - tips and tricks - glossary - details about data loading (e.g seed or production data) *Key Benefit* Our user documentation has a clear purpose rather than trying to fulfill mulitple different roles Once again these are my initial thoughts so am very happy (and keen) to get feedback from the community (especially user) about this. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/DISCUSSION-OFBiz-End-User-Wiki-Documentation-tp4668872.html Sent from the OFBiz - User mailing list archive at Nabble.com.
