It is not required to use a database when installing the OSB if you do not use the OSB Reporting or the OWSM. This is stated in the 184.108.40.206 documentation. I cannot find the same statement in the 220.127.116.11 documentation but it is still true though.
You will get an error in the domain configuration wizard if you do not configure a JDBC data source:
CFGFWK-40006: The driver class listed below was not found in the product installation
The error can be ignored so just press OK.
When you try to start the Admin Server you will also get some errors:
<Critical> <JTA> <BEA-110482> <A logging last resource failed during initialization. The server cannot boot unless all configured logging last resources (LLRs) initialize. Failing reason: weblogic.common.resourcepool.ResourceSystemException: Cannot load driver class: org.apache.derby.jdbc.ClientDriver <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'wlsbjmsrpDataSource' due to error weblogic.application.ModuleException:
You can get around these errors by untarget the wlsbjmsrpDataSource data source. You can do this manually by editing the config.xml file:
You can also use WLST scripting.
Now you should be able to use the OSB 🙂
Default a Derby database is started automatic with the OSB. To prevent this edit the setDomainEnv.sh and change the DERBY_FLAG to false: