jbilling comes with a bunch of database initialization files to run it on various vendors, including Oracle. Still, there are some issues running jbilling on Oracle. Start by reading the findings of 'mtnlti' in this thread: http://www.jbilling.com/?q=node/30

He (or she) lists a bunch of errors initializing the database. Start by installing Oracle (you can download a trial from Oracle itself) and reproducing these errors.

Next, edit jbilling-schema.xml fixing the naming problems and regenerate the init files by running the ant task 'db'. Try again to initialize oracle.
Now you have to propagate any table/column renaming to the code: entity beans and sql files. See the above thread where I mention the location of these files.

Now the tricky part. The file EntitySignup.java (package com.sapienter.jbilling.tools) is probably the only one not to use entity beans to access many tables. The problem is how it manages dates. It passes a date as a string in format 'yyyy-mm-dd', which is not portable to many RDBMS (works fine with postgresql and hypersonic). We need to change the logic of this class to use java.sql.Date objects instead.

Once all this is done, you should be able to initialize Oracle, create your first company, and then login and use jbilling normally. An important guide to read to understand all these instructions is this: http://www.jbilling.com/?q=node/57/&pl=pr After this task is done, I hope to change Oracle from red to yellow :)

This was completed in this revision.