| Oracle® Communications Service Broker Configuration Guide Release 5.0 Part Number E15182-01 |
|
|
View PDF |
| Oracle® Communications Service Broker Configuration Guide Release 5.0 Part Number E15182-01 |
|
|
View PDF |
This chapter provides a quick-step guide for the steps that you need to perform in order to configure the Service Broker:
Before you can start configuring Service Broker, make sure to follow the Service Broker post-installation instructions. See "Next Steps" in Oracle Communications Service Broker Installation Guide.
At this stage, you should have a Signaling and Processing Domains installed in your system, with respective Signaling and Processing servers installed.
The following are steps that you perform before configuring Service Broker:
Start the Administration Console. See "Starting the Stand-Alone Administration Console" or "Starting the Web Administration Console". This will also start both the configuration MBeans
If you choose to configure Service Broker using configuration scripts, start the Scripting Engine. See "Starting the Scripting Engine" in Oracle Communications Service Broker System Administrator's Guide for instructions.
To configure a Service Broker Signaling Domain, you need to perform the following steps in the following order:
To operate properly, Service Broker imposes certain requirements on naming servers in the Signaling Domain. If you want to specify your own names for Signaling Servers that do not follow these patterns, you need to map custom server names to names that follow the pattern required by Service Broker.
For more information, see "Mapping Custom Server Names to Service Broker Server Names".
A Signaling Server is a server deployed in the Signaling Domain.
Figure 2-1 shows the menu item in the Navigation pane that enables you to add Signaling Servers to the Signaling Domain.
For more information, see "Managing Domain Servers".
SSUs enable Service Broker to connect to SS7-based networks and IMS-based networks through standard software and hardware interfaces.
Depending on the type of signaling networks to which the servers in your domain connect, you need to configure a relevant type of the SSUs in your domain as follows:
Configure SSU SS7 TDM to enable Service Broker connectivity to a TDM-based SS7 network
Configure SSU SS7 SIGTRAN to enable Service Broker connectivity to a SIGTRAN SS7 network
Configure SSU SIP to enable Service Broker connectivity to a SIP network
Configure SSU Diameter to enable Service Broker connectivity to Diameter entities
Figure 2-2 shows the menu item in the Navigation pane that enables you to configure various types of SSUs.
For more information, see the following sections:
To configure a Service Broker Processing Domain, you need to perform the following steps in the following order:
To operate properly, Service Broker imposes certain requirements on naming servers in the Processing Domain. If you want to specify your own names for Processing Servers that do not follow these patterns, you need to map custom server names to names that follow the pattern required by Service Broker.
For more information, see "Mapping Custom Server Names to Service Broker Server Names".
A Processing Server is a server deployed in the Processing Domain. Figure 2-3 shows the menu item in the Navigation pane that enables you to add Processing Servers to the Processing Domain.
Note:
You can skip this step if you choose to perform preliminary configuration. See "Preliminary Configuration".IMs enable the OE to communicate with various application platforms and session control entities in the network. Figure 2-4 shows the menu item in the Navigation pane that enables you to add IMs to the Processing Domain.
For more information, see "Managing Interworking Modules".
Supplementary Modules facilitate and complement Service Broker solutions in specific deployments. Figure 2-5 shows the menu item in the Navigation pane that enables you to deploy the SMs.
For more information, see "Managing Supplementary Modules".
The OE routes service and charging requests that arrive from the network to one or more service platforms. The OE manages interactions between service platforms and session routing across applications. Figure 2-6 shows the menu item in the Navigation pane that enables you to configure the OE.
For more information, see "Configuring the Orchestration Engine".
After adding IMs to the Processing Domain (for more information, see "Deploying Service Broker Interworking Modules"), you can configure each of the added IM instances.
Figure 2-7 shows the menu item in the Navigation pane that enables you to configure the IMs.
For more information, see the following sections:
After adding Supplementary Modules to the Processing Domain (for more information, see "Deploying Supplementary Modules"), you can configure each of the added IM instances. Figure 2-8 shows the menu item in the Navigation pane that enables you to configure the IMs.
For more information, see the following sections:
Service Broker enables you to define how the Processing Tier communicates with the Signaling Tier. In addition, you can configure monitoring of the Processing Tier and set up the Service Broker overload protection mechanism.
Figure 2-9 shows the menu item in the Navigation pane that enables you to configure the Processing Tier.
For more information, see "Managing the Service Broker Processing Tier".
Service Broker allows you to perform full system configuration, immediately after completing Administration Console and Domain Configuration installation, and prior to setting up the domain servers.
You can use preliminary configuration to perform offline practice and analysis of various system configuration options and scenarios. Preliminary configuration is typically used during planning, development or test phases.
Before you start setting up the preliminary configuration, you have to remove the Processing Servers and Signaling Servers that the installation automatically setup.
Once you complete a domain preliminary configuration, you can add servers to the domain. New servers will obtain the preliminary configuration and work according to it.
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
