To plan your database configuration, you need to know which databases must be configured and be in place in order to use the software. You also need to know which components of ONEWEB you will use and their associated databases, the tasks required for administering the databases and the security privileges of the database system that you are using.


Database creation is the mandatory first step so that you can connect the data source when you deploy the ONEWEB archives.

Databases and their associated feature name.

Product

Schema

A2M

eaf_master

IAM2

iam2


AppDesigner & App Runtime

erp_oneweb

eaf_master

Process Designer & PD Monitor & Microflow

pd

Process Runtime & Microflow Runtime

bpm

AppSpace

appSpace

Page Designer

page

Page Runtime

NA

Avocodo

public

Dashboard


Survey Rabbit

survey_rabbit

Scheduler


Recommendation

  • Separate tablespaces for each application
    • This make sure issue with one tablespace does not impact the second application.
    • Tablespace can be taken offline without impacting all application instead of the one that has datafiles in it.


  • Table and indexes must be maintained in separate tablespaces
    • This is a typical implementation in production systems.


  • Properly name data files that are part of tablespace
    • Easily readable convention EAF_MASTER_data_01.datafile , BPM_data01.datafile