To configure ONEWEB database you must follow the below steps.
Step1: Create Schema & role authorization. Use following details to create database schema on postgresql server. Create schema for ONEWEB Application by using SQL script. Execute: create_schema.sql Create role authorization for ONEWEB Application by using SQL script. Execute: create_role.sql Alter password to user role by using SQL script. Execute: alter_password.sql
Step2: Restricting database user permissions. Alter administrator's privilege and search_path on schema for each user. Alter privilege for ONEWEB Application by using SQL script. Execute: alter_priviledge.sql
Step3: Create table and initial data.
Schema
Create table, initial data
eaf_master
create table structure and insert initial data.
ONEWEB.AR.4.0.19.12.base.postgres.sql
iam2
create table structure and insert initial data
ONEWEB.IAM.4.0.19.12.base.postgres.sql
mfd
create table structure and insert initial data
ONEWEB.MFD.4.0.0.19.12.base.postgres.sql
pd
create table structure and insert initial data
ONEWEB.PD.4.0.0.19_12.base.postgres.sql
bpm
create table structure and insert initial data
ONEWEB.PR.4.0.0.19.12.base.postgres.sql
asp
create table structure and insert initial data
ONEWEB.ASP.4.0.19.12.base.postgres.sql
dpc2
Table structure created automatically when install app
page
create table structure and insert initial data
ONEWEB.PGD.4.0.19.12.base.postgres.sql
dashboard
create table structure and insert initial data
ONEWEB.DSHB.4.0.19.12.base.postgres.sql
Reference: https://www.postgresql.org/docs/9.3/tutorial-install.html
To plan your database configuration, you need to know which databases must be configured to use the software. You also need to know the following like which components of ONEWEB you will use and their associated databases, the tasks required for administering the databases, and the security privileges associated with the database system.
Database creation is the mandatory first step so that you can connect the data source when you deploy the ONEWEB archives.
Below is the list of database schemas and their associated component name in ONEWEB.
Product
Schema
A2M
eaf_master
IAM2
iam2
AppDesigner
Configuration schema - eaf_master
Transaction schema - Can be any schema name such as "erp_oneweb"
App Runtime
Transaction schema set in App Designer
Process Designer
pd
Microflow
mfd
PD Monitor
pd
Process Runtime
bpm
Microflow Runtime
NA
AppSpace
asp
Pipeline/ Deployment Center
dpc2
Page Designer
page
Page Runtime
NA
Dashboard
dashboard_widget
Survey Rabbit
survey_rabbit
Scheduler
NA
Separate table spaces for each application This makes sure that the issues with one table space do not impact the second application. Table space can be taken offline without impacting all applications instead of the one that has data files in it.
Table and indexes must be maintained in separate table spaces This is a typical implementation in production systems.
Properly name data files that are part of table space Easily readable convention EAF_MASTER_data_01.datafile , BPM_data01.datafile