The RDBMS is necessary for the management of data related to transactions, events, monitoring of services performed in the environment WMB. Apart from it, its related to the management of the data associated with different Framework components such as Enricher, Lookup-Registry. The RDBMS also provides necessary interfaces and API that are exposed in the form of stored procedures to facilitate the management of data from WMB
Responsibilities
Master tables to be used during the Initial Setup of the Services – Stores list of applications, default time out response of these applications, default status code responses obtained for these applications
Master tables to be used during the Design Phase of the Services – Stores information regarding the List of Service Providers and its associated services to be invoked, Translation Information of Messages for integrating with the Service Providers.
Master tables to be used during the Development Phase of the Services – Information regarding the CONTROLLER, FMG and its mapping to generate the orchestration of the Services.
Transactional Tables to store the information related to the functioning of Framework components - Auditing, Monitoring, Tx. Manager LOGGER.
The following diagram illustrates the dependence of each of the tables in the RDBMS with the stage is used
Database Design
The following sections describe each of these tables and their associated
responsibilities. Master tables are named with "_MST_" and transaction tables and are named with "_TRAN_".
Initial Setup Tables
Application Portfolio Management
TBL_MST_APPLICATION Master table of all applications TBL_MST_APPLICATION_TIMEOUT Master table of all applications with
default timeout value when role is consumer and service provider TBL_MST_APPLICATION_STATUS_DEFAULT Master table of all applications with
default status code for error/success TBL_MST_REF_ERROR_CODE Master table with registers related to
different error codes in WMB.
Design Phase Tables
Data Translation , Error Translation
TBL_MST_DOMAIN Master tables to store the list of Domains – Types of message data for translation
TBL_MST_TRANSLATION Master table to store the mapping between domains and the combination of its values across various consumers and service providers
TBL_MST_TRANSLATION_ERROR Master table to store the combination of error codes across various consumers and service providers
Registration of Service Providers
TBL_MST_LEGACY_REGISTRY Master table to configure the various Services exposed by the Service Providers – Virtualization of services Configuration of REVERSE
TBL_MST_REV_CONFIG Master table to configure fields necessary to store for
REVERSO/ROLLBACK Development Phase Tables
Service Orchestration and Service Governance in WMB TBL_MST_CONTROLLER_REGISTRY Master table to register all
CONTROLLERS
TBL_MST_FMG_REGISTRY Master table to register all FMG’s TBL_MST_ORCHESTRATOR Master table to register Orchestration
details – map between CONTROLLER and FMG
Execution Phase Tables
Transaction tables
TBL_TRAN_AUDITORIO Transaction table to store Auditing Component meta-data
TBL_TRAN_AUDITORIO_DTL Transaction table to store Auditing Component message transaction-data TBL_TRAN_MONITOREO Transaction table to store Monitoring
Component meta-data
TBL_TRAN_REV_ORIG_TRANSACTION Transaction table to store Original
Transaction data to recover for REVERSO/ROLLBACK
TBL_TRAN_REV_STATUS_LOG Transaction table to store the status of REVERSO/ROLLBACK execution.
Relationship model in the RDBMS
Database Stored Procedure
List of RDBMS Stored Procedure with the WMB Components
Package Procedure Responsibilities
PKG_ESB_AUDITLOG SP_TRAN_SAVE_AUDITORIA Auditing Component – Registration of Auditing Events SP_GET_DUPLICACY_RESPONSE Auditing
Component – Checks of Duplicacy of Requests PKG_ESB_ERRORLOG SP_TRAN_SAVE_MONITOREO Saves the Error
Events of Monitoring Components PKG_ESB_LOOKUP_REGISTRY PRC_GET_ORCHESTRATION_MA
P
Used by Lookup Registry to generate the Orchestration information
PRC_GET_APPLICATION_MAP Lookup Registry SP_ADD_REVERSE_STATUS To manage the
status of the
Mapping of WMB and Data Base Framework components
Below is the table showing the relationship between the various components of the Framework of WMB and its associated RDBMS components
Component of WMB RDBMS component
Enricher TBL_MST_DOMAIN
TBL_MST_TRANSLATION
TBL_MST_TRANSLATION_ERROR TBL_MST_APPLICATION
Lookup-Registry TBL_MST_APPLICATION
TBL_MST_APPLICATION_TIMEOUT
TBL_MST_APPLICATION_STATUS_DEFAULT TBL_MST_CONTROLLER_REGISTRY
TBL_MST_FMG_REGISTRY
TBL_MST_LEGACY_SERVICES_REGISTRY TBL_MST_ORCHESTRATOR
Auditing TBL_TRAN_AUDITORIO
TBL_TRAN_AUDITORIO_DTL
Monitoring TBL_TRAN_MONITOREO
Tx.Manager - AGENT TBL_MST_LEGACY_SERVICES_REGISTRY TBL_MST_REV_CONFIG
TBL_TRAN_REV_ORIG_TRANSACTION Tx.Manager - CONFIG MGR TBL_MST_REV_CONFIG
Tx.Manager - ROLLBACK EXECUTOR
TBL_TRAN_REV_ORIG_TRANSACTION TBL_TRAN_REV_STATUS_LOG
TCS and Banco de Bogotá Architecture team must jointly work together to define and publish the processes related to the maintenance of the data stored in the RDBMS tables. It is highly
recommended to have transactional data purged or recycled to another Database/Data warehouse for review and audit for future. Strategies related to the identification of the objects of RDBMS tables must be resolved to achieve this task.