My Oracle Support Banner

How Wallet Is Created in CN and How to Change the Port to a Different cm_api(11860)? (Doc ID 2994655.1)

Last updated on JANUARY 04, 2024

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


Qn1: The requirement is to create multiple Connection Manager (CM) pod:
cm (11960) for RODOD order and Rated Event Loader (REL) & eai_js
cm_api (11860) for PCRF orders & Web Services Manager (WSM) Tomcat
cm_batch (11963) for batch applications only

The integration from WSM Tomcat to Billing and Revenue Management (BRM) is using the with infranet.connection commented, so it will be using the connection details present in wallet to connect to CM.

- As part of helm install wallet is created with default cm port 11960. How wallet is created in Cloud Native (CN) and how to change the port to a different cm_api (11860)?
- Can multiple infranet.connection be supported in wallet to have rel, eai_js etc connect to 11960 and WSM Tomcat to connect to 11860?
- If explicit specify infranet.connection in WSM Tomcat, then the password will be visible and it will be in violation of security.
Qn2: Please help to understand the arguments that used in below entry point which modifies the wallet to change infranet.connection:

$JAVA_HOME/bin/java -cp $PIN_HOME/jars/oraclepki.jar:$PIN_HOME/BRMActions.jar 9 $PIN_HOME/wallet/client $CLIENT_WALLET_PASSWORD OMS_SCHEMA_PASSWORD $brm_password cm 11960 SYS_PASSWD OMS_SCHEMA_USERNAME OMS_DB_ALIAS 1


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.