1. User's Guide
  2. Getting Started
  3. Configuring the OECB for SDM

Configuring the OECB for SDM

You can perform configuration and fault management on the Oracle Enterprise Communications Broker (OECB) and OECB groups using the Oracle Communications Session Delivery Manager (SDM). 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 OECB also provides you with the ability to establish consistent configuration management across multiple OECB deployments.

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

To configure the OECB 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 OECB negotiates a TLS connection with SDM. You must reboot your OECB after configuring ACP over TLS.

To support this management, the OECB generates an XSD file that specifies its configurable attributes. Using this XSD, SDM determines the configurable and non-configurable attributes on the OECB 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 OECB you can configure with SDM.

Upgrade Error Messages

The implementation of SDM configuration support required an architectural change that invalidates former configuration objects called templates. As the OECB development progresses, upgrades may generate unexpected results that need troubleshooting. The OECB logs the following applicable error messages, printed in log.web, when an error is observed during upgrade process and may present you with next steps while troubleshooting an upgrade:

  • "Could not create new object for <xmlName>” Displayed when error occurs while creating new xmlElement.
  • "Could not set attribute <attribute>:<reason>" Displayed when error occurs while setting an attribute in the new xmlElement.
  • "Could not delete service for <templateName>, Reason - <reason>" Displayed when service instance deletion on specified template fails.
  • "Could not delete for <templateName>, Reason - <reason>" Displayed when profile instance deletion on specified template fails.
  • "Could not delete template <templateName>, Reason - <reason>" Displayed when template deletion on specified template fails.