You can perform configuration and fault management on the Communications Broker and groups using the Communications Broker. Fault management by SDM includes the handling of SNMP traps and logs. Configuration management is based on software version, with each version able to specify which elements you can configure with SDM. The use of SDM for Oracle Enterprise Communications Broker also provides you with the ability to establish consistent configuration management across multiple Oracle Enterprise Communications Broker deployments.

You must use the Transport Layer Security (TLS) protocol to secure the communications link between the Communications Broker and the Oracle Communications Session Delivery Manager (SDM). Note that the systems use Acme Control Protocol (ACP) for this messaging.

To configure the Oracle Enterprise Communications Broker to use TLS for this ACP messaging:

1. Configure a TLS profile. The tls-profile object is located under security, where you add certificates, select cipher lists, and specify the TLS version for each profile.
2. Configure the system-config element's acp-tls-profile parameter to specify this TLS profile.

   ORACLE# configure terminal
   ORACLE(configure)# system
   ORACLE(system)# system-config
   ORACLE(system-config)# acp-tls-profile

The acp-tls-profile parameter is empty by default, which means that ACP is disabled. When the acp-tls-profile parameter specifies a valid TLS profile, the Communications Broker negotiates a TLS connection with SDM. You must reboot your Communications Broker after configuring ACP over TLS.

To support this management, the Communications Broker generates an XSD file that specifies its configurable attributes. Using this XSD, SDM determines the configurable and non-configurable attributes on the Communications Broker and to determines what it can display on its configuration GUI.

See your software version's Release Notes for more information about which elements of the Communications Broker you can configure with SDM.