Document Management System (DMS) and Machine Learning System (e.g. NLP) are deployed on a single common core server and are commonly accessed by both OBDX and OBMA products.

Similarly, Machine Learning System (e.g. NLP) is a common core product with machine learning related functionalities, such as extracting data from image called as Natural Language Processing (NLP).

There are no issues in this scenario. OBDX will interact with common core by picking default configurations.

1. For Content transactions, OBDX will upload the document in DMS using default HOST IP and PORT (Variable Names in DIGX_FW_CONFIG_VAR_B - MO_HOST_IP, MO_HOST_PORT) and default Headers (Variable Names in DIGX_FW_CONFIG_ADAPTER_PROP_B with MO as HOST ID - MO_BRANCH_CODE, MO_APP_ID, MO_USER_ID, MO_ENTITY_ID).
2. For NLP transactions, OBDX will use the document ID received from DMS and send it to NLP system using default HOST IP and PORT (Variable Names in DIGX_FW_CONFIG_VAR_B - NLP_HOST_IP, NLP_HOST_PORT) and default Headers (Variable Names in DIGX_FW_CONFIG_ADAPTER_PROP_B with NLP as HOST ID - APP_ID, USER_ID, BRANCH_CODE, ENTITY_ID).

Now since DMS and NLP systems are installed on the same server, both can interact with each other’s DB and thus NLP system will be able to download the document from document ID received.

The problem arises in Complex Scenario.