This chapter describes how to map custom server names to names patterns required by Oracle Communications Service Controller.
Processing Domain server names must use this format:
For Signaling Servers: ssu_
server_number. For example, the following names are valid: ssu_1, ssu_2, ssu_3
.
For Processing Servers: pn_
server_number. For example, the following names are valid: pn_1, pn_2, pn_3
.
During the installation, if you specified custom server names that do not follow these patterns, you need to map each custom server name to a name that follows the standard format as described above.
You map server names using ServersMBean.
Figure 6-1 shows the ServersMBean hierarchy. ServersMBean might contain multiple instances of ServerMBean. Each instance of ServerMBean represents a single server whose name you want to map.
To map a custom server name to a Service Controller standard name:
Create an instance of ServerMBean by invoking the following operation of ServersMBean:
ObjectName createServer()
Set the ManagedServerName attribute of ServerMBean to the custom server name that you specified during the installation.
Set the SbServerName attribute of ServerMBean to a standard Service Controller name.
See "Servers MBean" and "Server MBean" for more information.
ServersMBean is a root MBean for configuration of mapping between custom names that you specify for Signaling and Processing Servers and server names that follow the patterns required by Service Controller.
Specifies a name of the mapping configuration
Specifies a maximum number of servers whose names are to be mapped
Using ServerMBean, you can map a custom name of one server to a server name which follows the pattern required by Service Controller.
Specifies the custom server name that you specified during server installation.
Specifies a name that follows the pattern required by Service Controller.
Specifies a unique ID that the server uses when generating TCAP messages. The ID must be unique across all domains.