Oracle Banking Routing Hub VM Arguments

17 Oracle Banking Routing Hub VM Arguments

This topic provides information about Oracle Banking Routing Hub VM arguments.

Common Core Managed Server

Table 17-1 CMC-OBRH-SERVICE

Parameters	Default	Values
cmc-obrh-services.server.port	-	<SERVER_PORT>
cmc-obrh-services.server.port	-	<SERVER_PORT>
obrh.db.jndi	-	<CMNCORE_JNDI>
cmc-obrh-services.oic.secretStore.url	-	<OIC_SECRET_STORE_URL>
cmc-obrh-services.audit.retention.days	-	<AUDIT_RETENTION_POLICY_DAYS>
cmc-obrh-services.audit.retention.archival	-	Y / N (Y for archiving and N for purging)

Table 17-2 Enable and configure connection pooling for REST calls

Parameters	Default	Values
obrh.rest.connectionpool.enabled	false	true / false
obrh.rest.connectionpool.totalConnectionCount	20	<POOL_TOTAL_CONN_COUNT>
obrh.rest.connectionpool.maxConnectionCountPerRoute	2	<POOL_MAX_CONN_PER_ROUTE>
obrh.rest.connectionpool.timeToLive.ms	-1	<POOL_TTL>

Table 17-3 Receive routing failure mail notification via plato-alerts-management-service

Parameter	Default	Values
obrh.alerts.enabled	false	true / false

Table 17-4 Change approach for auditing

Parameters	Default	Values
obrh.audit.type	DEFAULT	DEFAULT / KAFKA / JMS / LOG / OFF For KAFKA option, cmc-obrh-kafka-consumer service needs to be deployed. For JMS option, cmc-obrh-jms-consumer service needs to be deployed.

Parameters

Default

Values

obrh.audit.type

DEFAULT

DEFAULT / KAFKA / JMS / LOG / OFF

For KAFKA option, cmc-obrh-kafka-consumer service needs to be deployed.

For JMS option, cmc-obrh-jms-consumer service needs to be deployed.

Table 17-5 Overwrite the customization that is not part of configuration json

Parameters	Default	Values
obrh.import.overwrite	false	true / false

Table 17-6 Use Custom Keystore and Truststore for HTTPS scheme

Parameters	Default	Values
obrh.keystore.password.encoded	-	true / false (true, if password is base 64 encoded)
obrh.truststore.path	-	<TRUSTSTORE_PATH>
obrh.truststore.password	-	<TRUSTSTORE_PASSWORD>
obrh.usekeystore	-	true / false (true, if keystore is required along with truststore)
obrh.keystore.path	-	<KEYSTORE_PATH>
obrh.keystore.password	-	<KEYSTORE_PASSWORD>
obrh.keystore.alias	-	<KEYSTORE_ALIAS_LIST>
obrh.keystore.aliaspassword	-	<KEYSTORE_ALIAS_PASSWORD_LIST>
obrh.ssl.protocol	TLS	TLS / TLSv1 / TLSv1.1 / TLSv1.2

Table 17-7 For tomcat deployment

Parameters	Default	Values
obrh.server.isJavaEE	true	true / false (false for tomcat)
obrh.taskexecutor.corepoolsize	50	<CORE_POOLSIZE>
obrh.taskexecutor.maxpoolsize	50	<MAX_POOLSIZE>
obrh.taskexecutor.queuecapacity	100	<QUEUE_CAPACITY>

Set Proxy settings for HTTPS: As per the Java Networking documentation, HTTPS protocol handler will use the same as the http handler (i.e. http.nonProxyHosts). But in case of Weblogic, http.nonProxyHosts will not work for some reason. So, use https non proxy host argument (i.e. https.nonProxyHosts).

Table 17-8 Set Proxy settings for HTTPS

Parameters	Default	Values
https.proxyHost	-	<PROXY_HOST_NAME>
https.proxyPort	-	<PROXY_PORT>
https.nonProxyHosts	-	<NON_PROXY_HOST_LIST>
http.nonProxyHosts	-	<NON_PROXY_HOST_LIST>

Table 17-9 Set logger level

Parameters	Default	Values
plato.service.logging.level	-	<LOG_LEVEL>

This property will enforce WebLogic Server to use SUN SSL implementation (javax package) rather than the WebLogic one.

Table 17-10 Support SSL based SOAP provider calls in weblogic environment

Parameters	Default	Values
UseSunHttpHandler	-	true

Table 17-11 CMC-OBRH-KAFKA-CONSUMER

Parameters	Default	Values
cmc-obrh-kafka-consumer.server.port	-	<SERVER_PORT>
obrh.audit.id-generator	UUID	UUID / SNOWFLAKE

Table 17-12 CMC-OBRH-JMS-CONSUMER

Parameters	Default	Values
cmc-obrh-jms-consumer.server.port	-	<SERVER_PORT>
cmc-obrh-jms-consumer.connectionFactory	-	<JMS_CONN_FACTORY_JNDI>
cmc-obrh-jms-consumer.queue	-	<JMS_CONN_QUEUE_JNDI>

Table 17-13 Change ID generator

Parameters	Default	Values
obrh.audit.id-generator	UUID	UUID / SNOWFLAKE

Plato Core Managed Server

Oracle Banking Routing Hub is using Multipart for Import feature. By default, spring supports max 1MB file size and 10MB request size for Multipart.

To import bigger files,

plato-api-gateway.multipart.max-file-size=<MAX_FILE_SIZE> (default is 200MB)
plato-api-gateway.multipart.max-request-size=<MAX_REQUEST_SIZE> (default is 200MB)

Note:

-1 for no size constraint

Example,

plato-api-gateway.multipart.max-file-size=-1
plato-api-gateway.multipart.max-request-size=-1