THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Miscellaneous
- OFBiz's Data File Tools Some tips from Jacopo
- How to use EntityWhereString A tip from GrimTim
- How to troubleshoot SQL errors A tip from Chris Lombardi
- Tips for View Entities A tip from SkipDever
- How to connect to an External Database A tip from Adrian Crum
- How to save customised data for import as demo data A tip from Raj Saini
- Is it possible to delete products, categories or catalogs that are no longer needed?
- MySQL
- Oracle
...
Have a look at framework/appserver/README file. You might be also interested by Run OFBiz under outside Application Servers (WASCE 2.0.0.1, Geronimo 2.0.3, Tomcat 5.5 and 6, JBoss 4.2.2)
| Anchor | ||||
|---|---|---|---|---|
|
...
- If you are not interested in posting accounting transactions to the GL then you can disable (i.e. comment out) the first eca rule in accounting/servicedef/secas_ledger.xml
Code Block <eca service="createAcctgTransAndEntries" event="commit"> <condition field-name="acctgTransId" operator="is-not-empty"/> <action service="postAcctgTrans" mode="sync"/> </eca> - Configure an Error Journal to post there the accounting transactions that are incomplete (you will find a lot of posts about this if you search in the archives)
| Anchor | ||||
|---|---|---|---|---|
|
Is it possible to delete products, categories or catalogs that are no longer needed?
This question has been already asked many times. You should find more information in Nabble
The main idea is that in OFBiz we don't delete but use end dates to mark obsolescence.
Four main reasons :
- Data are still there in case of audit
- Disk space should not a be problem
- DB indexes are managing quite well huge data volumes.
- Easier with all entities associations
If you really need to do it, think about these 4 points before...