6 Configurations for OBRH Integration
This topic provides information on Configurations for OBRH Integration. Use the following guidelines to integrate with OBRH from the OBDX adapter.
To call OBRH endpoint from adapter, add entry of
OBRHEndPoint(com.ofss.digx.extxface.impl.endpoint.OBRHEndPoint)
against your "interfaceId" in digx_fw_config_all_b for Category id as "ExtXfaceConfig".
The "interfaceId" should be the unique service name defined in the OBRH for specific consumer.
To configure which serializer and deserializer should be called for your Request,
Add prop_id entry in digx_fw_config_all_b as "com.ofss.digx.extxface.impl.endpoint.
OBRHEndPoint_<interfaceId>" and prop_value, as which Serializer Deserializer should be used
(JSON or XML)
For JSON:
"com.ofss.digx.extxface.impl.endpoint.serde.JsonSerDe"
(this is the default class picked if no specific entry is
made)
For XML:
"com.ofss.digx.extxface.impl.endpoint.serde.XmlSerDe"
Category id is "ExtXfaceConfig".
OBRH is shipped with OBDX in standalone way only if customer does not have any OBMA product installed. For customers with OBMA installation, OBRH of that setup must only be used.
The following configurations are maintained for OBRH-OBDX integration.
1. DIGX_FW_CONFIG_ALL_B
| Category Id | Prop_id | Prop_Value ( Default_value) |
|---|---|---|
CredentialPropertyStore |
OBRH_USER_PASSWORD |
27753d4e463db94b64ab096facb916ff24670adfa0b5769ad9 |
authenticationConfig |
OBRH_ENCODING |
BASE64 (Sends
credentials in base 64) PLATO_ENCRYPTION (Encrypts
credentials) |
authenticationConfig |
OBRH_EXPIRYTIME |
${OBRH_EXPIRYTIME} |
authenticationConfig |
OBRH_TOKEN_PATH |
token |
ExtXfaceConfig |
com.ofss.digx.extxface.impl.endpoint.OBRHEndPoint_<interfaceId> |
com.ofss.digx.extxface.impl.endpoint.serde.JsonSerDe
( JSON is default value, you can SerDe you want
for this request)
|
ExtXfaceConfig |
<interfaceId> |
com.ofss.digx.extxface.impl.endpoint.OBRHEndPoint |
CredentialPropertyStore |
OBRH_USER_NAME |
OBDX |
2. DIGX_FW_CONFIG_VAR_B
| Prop_id | Prop_Value ( Default_value) | ENV_ID |
|---|---|---|
OBRH_HOST_IP |
OBDX |
|
OBRH_HOST_PORT |
7002 | OBDX |
OBRH_EXPIRYTIME |
300 | OBDX |
3.
DIGX_FW_CONFIG_ADAPTER_PROP_B
| HOST_ID | TRANSACTION_TYPE | PROP_ID | PROP_VALUE (Default_value) |
|---|---|---|---|
OBRH |
ALL |
APP_ID |
CMNCORE |
OBRH |
ALL |
USER_ID |
OBDX |
OBRH |
ALL |
BRANCH_CODE |
4 |
OBRH |
ALL |
SERVICE_CONSUMER |
OBDX |
OBRH |
ALL |
TOKEN_APP_ID |
SECSRV001 |
4.
DIGX_FW_CONFIG_ADAPTER_PROP_B
| Service Id | CONTEXT_URL | SERVICE_URL |
|---|---|---|
tokenOBRH |
http://${OBRH_HOST_IP}:${OBRH_HOST_PORT} |
api-gateway/platojwtauth |
serviceOBRH |
http://${OBRH_HOST_IP}:${OBRH_HOST_PORT} |
api-gateway/cmc-obrh-services/route/dispatch |
Apart from above predefined properties, we have
provision to add additional headers. Kindly add your
additional headers as a key-value pair in newly added
variable "headersMap" of
"com.ofss.digx.extxface.impl.dto.ExternalSystemRequest".
Refer OBRH User Manual for its usage.
- Configurations for connecting to OBRH
- FCUBS OBRH Configuration
This topic provides information on FCUBS OBRH Configuration. Execute the following script at OBDX digx database and restart the managed server.