Databases Reference
In-Depth Information
Enabling SSL for BAM
Internally, BAM uses RMI for communications between different components.
By default, RMI communications in WebLogic Server use the
t3
protocol, an
optimized protocol for transporting data between the WebLogic Server compon-
ents. For example, BAM Active Data Cache communicates with internal JMS
topics using RMI through the
t3
protocol. BAM web applications invoke BAM
Active Data Cache APIs through RMI (t3) as well.
To enable SSL for these internal communications, BAM in-
troduces a parameter called
BAMServerEnableSSO
, which
can only be manually configured in the
BAMCommonCon-
fig.xml
file. With SSL enabled, the communication protocol
becomes
t3s
.
To set up this parameter, add the following configuration in the
<BAM_Domain>
/config/fmwconfig/servers/<BAM_Server>/applications/
oracle-bam_11.1.1/config/BAMCommonConfig.xml
file, where
<BAM_Domain> is the WebLogic domain name of the Managed Server for BAM,
and
<BAM_Server>
is the name of the Managed Server.
<BAMServerEnableSSO>true</BAMServerEnableSSO>
Note that you have to restart the Managed Server for BAM to make the change
take effect.
