1. User's Guide
  2. Getting Started

4 Getting Started

Oracle® recommends that you review the topics in "Getting Started" before working with the system to ensure success with the tools and functions provided.

Accessibility Features

The following accessibility features are available in this release.

Keyboard Navigation

You can access GUI functionality using only the keyboard. Use the following keys to navigate:
  • Tab key: Move to the next control, such as a dynamic target menu, navigation tree, content pane, or tab in a page. Tab traverses the page left to right, top to bottom. Use Shift +Tab to move to the previous control.
  • F6 key: The tab key moves between controls, but does not move between controls after it has, for example, opened a widget toolbar in a Dashboard tile. Use F6 to set focus to the next control on these toolbars. Press again to remove focus.
  • Up and Down Arrow keys: Move to the previous or next item in the navigation tree, menu, or table. Down Arrow also opens a menu.
  • Left and Right Arrow keys: Collapse and expand an item in the navigation tree or a submenu.
  • Spacebar: Activate a control. For example, in a check box, spacebar toggles the state, checking or unchecking the box.
  • Enter: Activate a button.

Note:

Some functionality cannot be accessed through keyboard navigation.

Microsoft Screen Narration and Jaws

This product is compatible with common OS's screen reader programs.

Microsoft Magnifier

This product is compatible with common OS's screen magnifying features.

Configuring the Communications Broker for SDM

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.

Upgrade Error Messages

The implementation of SDM configuration support required an architectural change that invalidates former configuration objects called templates. As the Communications Broker development progresses, upgrades may generate unexpected results that need troubleshooting. The Communications Broker 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.