Prepare Database Server

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

Recommendation

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