Web Logic Portal comes with an evaluation license of Pointbase RDBMS for now.
Especially with WebLogic Portal most people use their own RDBMS like Oracle, MySQL, SQL Server etc. In that case you have to specify or reconfigure WebLogic about the location of the database objects.
* During the domain creation process they will give you an option to specify the database configuration information for all the datasources that portal require like p13nDataSource, portalDataSource, cgDataSource etc. In the subsequent screen of the configuration wizard they will give you an option to run the DB scripts to create your database objects if the user configured for the datasources in the previous screen is setup with right permissions. More information about this process can be found here. The following screen shot show the a sample JDBC Datasource configuration screen from the configuration wizard.
With WebLogic Portal 10.3.2, the point to note when you are configuring a non-Pointbase database a problem comes when you run the server it does not start
Error should be like this
<> <Test "SELECT COUNT(*) FROM SYSTABLES" set up for pool "p13nDataSource" failed with exception: "java.sql.SQLSyntaxErrorException: [OWLS][Sybase JDBC Driver][Sybase]SYSTABLES not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
It is a known bug called “WebLogic Portal Configuration Wizard Bug”.
Workaround is to change the connection test sql clause in the WebLogic Server Console as follows:
1. In the “domain structure” panel go to Domain > Services > JDBC > DataSources.
2. Click each data source name, then the “connection pool” tab, and then “Advanced” at the bottom of the page.
In the “Test Table Name” text box, change the sql clause according to the type of db:
Oracle: SQL SELECT 1 FROM DUAL
DB2: SQL SELECT COUNT(*) FROM SYSIBM.SYSTABLES
MS SQL Server: SQL SELECT COUNT(*) FROM sysobjects
Sybase: SQL SELECT COUNT(*) FROM sysobjects
My Sql: SQL SELECT 1
Pointbase: No change.