SSL-Enabled BRM Fails To Start With AF_UNIX Socket
(Doc ID 2662062.1)
Last updated on JANUARY 03, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.2.0 and laterInformation in this document applies to any platform.
Goal
Q1:Customer installed Billing Revenue Management(BRM) 12.0.0.2.0 with Secure Sockets Layer (SSL) active and it works well, as they have a Connection Manager (CM) and Data Manager (DM) on the same machine and set cm/dm_oracle with AF_Unix. e.g
- cm.pinconf:
- cm dm_pointer 0.0.0.1 local ${PIN_HOME}/sys/dm/dm_port
- dm_oracle.pinconf
- dm dm_port <
- dm dm_local_socket_name ${PIN_HOME}/sys/dm_oracle/dm_port
If SSL is disabled the dm_port socket will work well, with ssl enable and the AF_UNIX configuration, cm not start,It throws the below error cm.pinlog
Solution
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
Goal |
Solution |
References |