RESTORATION OF DB TO TEST SHOULD NOT INCLUDE DATAHUB CONFIGURATION

Time when issue occurred:
We noticed it yesterday as we were testing for UAT. 

Affected module:
DATAHUB and Honeywell System

Detailed description of issue:

1. The issue is supposedly the datahub sending to UAT but it sends to our Middleware PROD. We also noticed that it happened since 17 June and above.

2. Please assist on this issue as soon as possible as we are testing some data in UAT.

First level investigation/troubleshooting taken:

Message Set - TM_BAS_CUSTOMER

Message Definition - TM_MESSAGELIST_CUSTOMER

Message Structure - TM_MESSAGELIST_CUSTOMER_STR

Message Parameter - TM_MESSAGELIST_CUSTOMER_VALUES

Message Key Configuration - TM_MESSAGE_CUSTOMER_KEY

Message Mapping - TM_MESSAGE_CUSTOMER

Message Interchange Table Definition – TM_STD_TABLE

Business Table JDBC Mapping - TM_STD_JDBC_MAPPING

Message JDBC Mapping - TM_STD_JDBC_MAPPING_CUST

Message Data Select SQL - TM_SEND_STD_TABLE

Message SQL Rules - TM_RULE_CUSTOMER_MESSAGEID_SQL

Message Business Rules - TM_RULE_CUSTOMER_MESSAGEID

Message Service – TM_DATAHUB_SERVICE

Message Timer - TC_TIMER_CUSTOMERMESSAGEID

Message File Exchange - TM_BAS_EDI_TRANSFER

Information Monitoring - MongoDB