ONEWEB requires a relational database. It has 2 parts, one for the configuration and another for the transaction data. ONEWEB configuration schemas and application transaction schema can be on separate instances or can be on the same instance depending on your design.
Supported Databases - Given below are the supported database servers
Oracle 11g or later PostgreSQL 9.6. MySQL 5.6 or later DB2 10.5 or later MS SQL Server 2012 or later MariaDB 10.1.22 or later Tibero 6.0 or later
Schemas - ONEWEB requires 9 database schemas for ONEWEB configuration data and 2 schemas for your transaction data
The ONEWEB configuration data schemas are as follows: eaf_master - To store AppDesigner configuration data erp_oneweb - To store AppDesigner transaction data. ONEWEB can use any schema name. This is only a sample name. pd - To store ProcessDesigner
mfd - To store Microflow configurations page - To store PageDesigner configurations bpm - To store Process transaction data asp - To store AppSpace configurations dpc2 - To store Deployment Center configurations iam2 - To store User data and Authorization data for IAM dashboard_widget - To store the widget dashboard configurations survey_rabbit - For storing survey configurations
Tablespaces - We recommend separating table space by at least one schema per one table space.
For best practice we also recommend separating table space for data and table space for index to get the best performance. You fine tune such by following these techniques:
Separate table space for transaction data table and index data table. Separate table space by following the data size of the table. Place table space file in different physical disk.
Data Files - Data File is a physical file of the Table space. One table space needs to have at least one Data File. For designing the Data File please consult your DBA.