___  
 / _ \ 
/ /_\ \
|  _  |
| | | |
\_| |_/
       
       

 ___   
|  _`\ 
| (_) )
| ,  / 
| |\ \ 
(_) (_)
       
       

         
### ##   
 ### ##  
 ##  ##  
 ##  ##  
 ### ##  
 ## ##   
###      

         
         
  ####   
 ##  ##  
 ##  ##  
 ##  ##  
  ####   
         

 _______ 
(  ___  )
| (   ) |
| |   | |
| |   | |
| | /\| |
| (_\ \ |
(____\/_)
         

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
'''Only for developers - or rather ofbiz enthusiasts''' WebShop/UnderDevelopment/OfBiz/TestCases lists the functionality we use. [http://www.6speed.org/vems/web/ofbiz_screenshot.png Screenshot] of OfBiz running on my laptop. Apache/Tomcat/OfBiz running on my laptop MaxDB running on my garage computer Mozilla running on my livingroom computer Progress was MUCH slower than I wanted, but the best part is it's running all together with Apache and Tomcat, and to sweeten the deal, I finally understand it! -Jason Now to populate the DB with all the products... and keep a '''good system of categories'''. ---- '''should I install a local ofbiz on my home system?''' Only if you plan to play with versions, features, upgrades, etc. It's '''very easy (takes 15 mins besides some svn download time)''' if * JAVA * ant * svn * and postgres are no problem * and mem >=512MByte. ---- '''Ofbiz steps''' * [http://svn.ofbiz.org/ get the uptodate code via svn] * ''ant'' compile it * the rest is compatible with the [http://www.ofbiz.org/docs/setup.html basic procedures] that uses the old prebuilt binary release and [http://ofbizwiki.go-integral.com/Wiki.jsp?page=RelationalDatabases ofbiz wiki] helps you set up postgresql (create database and user). * point it to the database (instead of the default in-memory demo database system). Do it manually, or see my patch below: in the ofbiz dir run patch -p1 </opt/ofbiz-postgres.patch * decide if you run it over existing database or start from empty DB and import dir with XML-s exported from previous version, or there is sample-data with gizmos (some silly products) and also minimal sample data without gizmos (this is only very necessary data, such as types, and priviledges). * start it up. Note that since startup can take 2 minutes. These are just notes, check the ofbiz.org docs. I'll help if you run into problems. The original configuration refers to derby database, you want to change it to postgres (maybe maxdb or oracle, but '''not''' mysql): <code> cat /opt/ofbiz-postgres.patch --- ofbiz-old/components/entity/config/entityengine.xml 2004-10-21 03:14:27.000000000 +0200 +++ ofbiz/components/entity/config/entityengine.xml 2004-10-21 10:59:02.000000000 +0200 @@ -33,4 +33,4 @@ <delegator name="default" entity-model-reader="main" entity-group-reader="main" entity-eca-reader="main" distributed-cache-clear-enabled="false"> - <group-map group-name="org.ofbiz" datasource-name="localderby"/> + <group-map group-name="org.ofbiz" datasource-name="localpostgres"/> </delegator> </code> ---- '''Ofbiz and Tomcat side by side''' On the biztest machine I just stopped tomcat so ofbiz can run. However, I cannot do that on the new (faster CPU + mem + network!!), production machine. I changed port 8009 to 18009 in ''base/config/ofbiz-containers...whatever.xml'' but it still has a ''cannot bind'' error when trying to listen. (I'm not very familier with these, is it IIOP or ??) Suggestions? Anyone got it running on same host as Tomcat ? I wouldn't mind if apache2 was used as frontend (although the 443 port is still not occupied). It is also possible to deploy parts in existing Tomcat - if that helps. * I will provide instructions for this. Please make ''diff -U 4'' or alike format patches so the config changes can be applied easily. No need for too much wording * target machine: apache2; 1099, 2000 and 8009 and 8443 are free now. Actually, even 443 is free for now, but both http public interface and 443 admin interface must go through apache2. postgresql is set up with default config. ** We only will use 80,443,and 8009 (80 and 443 for Apache2, 8009 for Tomcat) Please avoid 8009 if possible, I propose 8010 (but OK if hard to avoid). Is there a workers2.properties file somewhere? Usually where httpd.conf is. Not sure what is needed. I thought about this: <code> cat /etc/apache2/sites-enabled/biz.x-dsl.hu NameVirtualHost * <VirtualHost *> ServerAdmin info@x-dsl.hu DocumentRoot /var/www/biz.x-dsl.hu ServerName biz.x-dsl.hu ServerAlias biztest.x-dsl.hu ErrorLog /var/log/apache2/biz.x-dsl.hu.err TransferLog /var/log/apache2/biz.x-dsl.hu.log ErrorDocument 404 /404.htm <Location "/ofbiz/*"> JkUriSet worker ajp13:127.0.0.1:8010 </Location> </VirtualHost> </code> The machine is Debian of course. Assume /opt/ofbiz is a symlink to an uptodate svn ofbiz checked out & compiled. ---- '''Mass registration of products''' Everything is so nice with the XML formats and import-export tools in webtools. Also check entity-data maintenance, where every attribute can be viewed or changed (with the right permissions, but we use fulladmin now) * inventory is a bit problem, I have to understand inventory data at least before next migration (for now we type in again). ---- '''self-registration of new parties''' Because of the work-effort module, it would be nice if * anyone could sign up himself (with no special rights of course). * Maybe make their own facility as well (that they can manage). * we would grant them any added rights for the given facilities and categories (or only possible to all products or none?) ---- '''Shopkeepers, please update your stock ASAP''' * I made warehouses and usernames for sly, jorgen, jason. I send pw privately. Shopkeepers have fulladmin rights for now so they can play with features. * Jason's girlfriend entered most sold products (the facade needs to be made nicer, so we can switch to ofbiz as our new shop) * my girlfriend entered most subassemblies used for genboard v3 manufacturing (so we see exactly what to order - although not yet connected with bin/categories.pl) * get familiar with ofbiz * '''please register your inventory''' (endplates, boxes, etc...) * registering (create new) inventory is easiest when going from (catalog => vems catalog => given product => inventory). It's one more click than I think it should be, acceptable. Use ''found'' as reason for inventory change. When going from facility (warehouse), the ID of the product needs to be typed. * QOH is the real quantity (on hand) * ATP is what can yet be promised. Eg. if I have 10 (whatever product) QOH, but 2 are scheduled to be transferred to Jason, and 1 is promised to a customer through a channel that ofbiz aint know about, ATP=10-2-1=7 * registering a postal address (party => contact => new) wouldn't hurt (also telephone, email) After some practicing, you'll find that ofbiz is very intuitive. We use products, facility, inventory, party and inventory transfer. We'll use more and more features, like work effort management, manufacturing, and who knows.. Let me know if you have problems. * https://biztest.x-dsl.hu:8443/catalog/control/main is the test system and * https://biz.x-dsl.hu/catalog/control/main is the '''production instance''' * ... add your instances (at least name; URL optional) '''Speed''' - after moved from my home PC to a machine with superior network connection (and some free RAM). Speed improved. The earlier 512 MByte system (with poor network connectivity) was tight for an SAP-like system with DB + application + webserver + girlfriend using it as a desktop. Speed will be even better once we use the apache not the internal webserver. ---- '''Article master''' Jason will * refine (create when necessary) products * categorize them * start to set up store * update all the East Coast Inventory. It seems like [http://ofbizwiki.go-integral.com/Wiki.jsp?page=InventoryMovementLog inventory] can be entered, but the summary report does not show up good (only when you click edit and see each inventory variance). I thought that you planned to do the article master on your (garage?) machine and import into the system through XML (or through the !EntitySync gizmo that I couldn't fully understand yet). If you run into foreign key exceptions (likely with the category because of the parent category key) you can drop all foreign keys, import, than recreate fk (takes 1.5 minutes each). ---- '''Migration from current shop to ofbiz''' I expect the following advantages: * proper track of inventory without manual adjustments * splitting order to more than 1 packs to match reality (when part comes from US and other from EU) * split IBAN, ikobo, check and money order payment options properly * apply some extra fee on paypal payments to cover some losses from the activity of paypal dirty tricks department ---- '''User rights in the test sys''' I think we want to import products (and most data) into the test systems, but not the users. It's fine to have some shared usernames for testing (or same users but different passwords). The passwords shouldn't be public :-) I wiped the standard passwords of course. ---- '''Ofbiz upgrade''' I'm thinking of setting oscommerce (current shop) stock to all 10000 at the time of the stock update, so ofbiz stock-adjustments can take that into account later (somehow). * [http://ofbizwiki.go-integral.com/Wiki.jsp?page=UsingEntitySynchronization EntitySync] configuration questions in ofbiz wiki. Anyone knows how entity-sync could be set up? We really want to have 3 ofbiz instances (HOSM, HOST and for now one BOS) with entity-synchronization. It is also possible to have manual procedures temporarily for cloning Product and productcategory info from HOSM to BOS. * finish the ofbiz products and categorizations, copying from oscommerce (done by MembersPage/RichardBarrington) * check ofbiz payment module: moneybooker * check ofbiz payment module: ikobo * check ofbiz payment module: paypal (with extra fee for PaypalStealsYourMoney !!) * migrate oscommerce customers: optional (they can simply re-register; the passwords would be hard to transfer if crypt-function is not identical). * migrate oscommerce orders: no way! WebShop/UnderDevelopment/OfBiz/VersionUpgrade
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.