Only for developers - or rather ofbiz enthusiasts

WebShop/UnderDevelopment/OfBiz/TestCases lists the functionality we use. Also a tutorial for ofbiz users.

[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

Ofbiz steps

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):

 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"/>

Ofbiz via Apache

Since IP address (and sometimes even domain names) are a limited resource, and stupidly configured firewalls/proxies often refuse to access https://domain...:8443/ (https through port 8443 or actually any other ports than 443), it is desirable to connect to the application server that is behind an Apache server. The apache connects to the container (which is by default catalina tomcat).

The sites-enabled/site... (or httpd.conf) trick is:

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/*">
# WARNING!!!!!!!! /ofbiz/* is hell to make work,
# the webapps config in ofbiz is for martians
# instead make separate Location entries /party/*  /partymgr/* /order/* ...
# that point to same worker. Ugly? It works.
                JkUriSet worker ajp13:localhost:8010
# beware that ajp13:localhost:8010 is just a reference (key)
# to an entry in workers2.properties file !


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)

self-registration of new parties

Because of the work-effort module, it would be nice if

Shopkeepers, please update your stock ASAP

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.

Article master

Jason will

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:

More on migration to ofbiz WebShop

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).

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 must not be public :-) I wiped the standard passwords of course.