6.1.2 OBRH (Standalone) of OBDX setup
This topic provides information on OBRH (Standalone) of OBDX setup.
Figure 6-1 OBRH (Standalone) of OBDX setup
Following properties needs to be updated from the screen for OBRH (Standalone) of OBDX setup from the following location:
Table 6-2 System Configuration > Entity Specific > Framework
| Property Id | Property_Value ( Default_value) |
|---|---|
| OBRH Token Endpoint Authentication Type | APIKEY |
| OBRH Service URL For Service Calls | cmc-obrh-services/route/dispatch |
| OBRH Service Context URL | http://${OBRH_HOST_IP}:${OBRH_HOST_PORT} (Replace this with actual host and port) |
| Application connection host | OBDX_HOST_IP |
| Application connection port | OBDX_HOST_PORT |
| OBRH Service Consumer Name | OBDX_TRUNK |
Note:
In case of OBRH/OBDX cluster, a load balancer must be deployed and that host/port must be configured in above queriesOHS Configurations
In obdx.conf from installer. Check proxy pass values and note that order is maintained. /digx must be below /digx-cmc, /digx-sms. If using location/locationMatch tag for digx, remove proxy pass for /digx and move /digx-cmc, /digx-sms above location/locationMatch tag.
Note:
Cluster is not required for /digx-cmc, /digx-sms as they are used for OBRH/ML maintenances only.In below entries replace host and ports as –
17004 – OBRH MS
17005 – OHS port
Figure 6-3 Example 2. With location for OBDX
Parent topic: Configurations for connecting to OBRH


