Realtask DB
If you are a on-premise customer, Realtask would have been installed in your AWS Account, which includes Realtask Application DB (App Db), where all Users, Jobs, tasks and rest of the configuration is stored. This doc provides some details that would be useful to explore the DB for data extraction, backup or other purposes.
Connecting to DB
Realtask uses Postgres DB, typically created as RDS instance, but depending on your needs, you can use Heroku Postgres or independent instance. Gather the following information which is required to connect to db.
- Host Name This is the db server host name. Make sure you are connected to VPN or using bastion host to connect as db is typically installed in non-internet facing network
- Port Typically this value is 5432 for Postgres but can vary based on installation
- Database Postgres instance can host multiple databases. For RT typically we would have created a separate db with
naming convention
<prefix>_appsuite_appdb - Username Db Username
- Password Db Password
Now use your tool of choice to connect to DB. We recommend DbVisualizer, which has a Free version and is a great cross-platform way to connect to DB and other sources.
Schema
Here is the ER diagram showing important tables and how they are connected.
Tables
| Name | Description |
|---|---|
| tenant | This table stores multiple tenant records in multi-tenant deployments. It should have single record for single-tenant and on-premise deployments |
| users | This table stores all (both active and inactive) application users |
| user_group | Stores user groups |
| user_group_member | Stores users associated with a particular user group |
| env | Stores environment records |
| conn | Stores connections managed in Realtask, including Sfdc, Google and other connections |
| rt_job | Stores Realtask Jobs |
| rt_task | Stores Realtask Tasks |
| rt_run | Represents a single RT Job run. Task run details are included in the same record as structured Json |
| rt_run_stat | Stores summarized run stats for a Job |
JSON Columns
Realtask deals with complex information structure and many times makes use of Postgres Json columns. As you explore,
look for columns of type jsonb which stores Json blobs.
Here are some of the important Json columns.
| Table | Column | Description |
|---|---|---|
| options | Stores user configuration/options pertaining to a Job/Task etc | |
| settings | Stores server managed information pertaining to a Job/Task, typically run related information | |
| rt_job | run_stats | Stores last run stats like total records processed, successful, errors etc., |
| rt_job | sharing_details | Stores Sharing details for a Job |
| rt_job | run_info | Stores last run worker information like memory size, runtime container id etc., |
| rt_task | source | Stores Task source configuration |
| rt_task | target | Stores Task target configuration |
| rt_task | field_mapping | Stores Task field mapping configuration |
| rt_task | row_mapping | Stores Task row mapping configuration |
| rt_run | tasks | Stores Task level details in the Run |
| rt_run | stats | Stores run stats like total/success/error counts |
| rt_run | runtime_info | Stores runtime worker information |
| rt_run | params | Stores params information |