| Oracle® Communications Service Broker Processing Domain Configuration Guide Release 6.0 Part Number E23525-02 |
|
|
View PDF |
| Oracle® Communications Service Broker Processing Domain Configuration Guide Release 6.0 Part Number E23525-02 |
|
|
View PDF |
The following sections describe how to configure IM-OCF PCP using the Service Broker Administration Console and Java MBeans.
This section describes how to configure IM-OCF PCP module instances using the Service Broker Administration Console.
To access the IM-OCF PCP Configuration screen:
In the domain navigation pane, expand OCSB.
Expand Processing Tier.
Select Interworking Modules.
A list of currently deployed Interworking Modules is displayed.
From the module list, select the module instance that you want to configure.
The IM-OCF PCP configuration pane contains the subtabs described in Table 27-1.
Table 27-1 IM-OCF PCP Configuration Subtabs
| Subtab | Description |
|---|---|
|
Call Handling |
Enables you to define how the IM-OCF PCP handles calls. See "Configuring Call Handling Parameters" for more information. |
|
Diameter Credit Control Application |
Enables you to configure parameters specific to the IM-OCF PCP DCCA interface. See "Configuring Diameter Credit Control Application Parameters" for more information. |
|
Async Announcement Manager |
Enables you to set up how IM-OCF PCP triggers the MRF to play announcements. See "Configuring Asynchronous Announcement Manager Parameters" for more information. |
|
Monitoring |
Enables you to define how Runtime MBeans and notifications should operate. See "Configuring Monitoring Parameters" for more information. |
|
Degraded Mode |
Enables you to set up how a session is charged when an online charging server is not available. See "Configuring the Degraded Mode" for more information. |
|
Ro PCP Mediation |
Enables you to define how IM-OCF PCP translates Ro messages to PCP messages and communicates with BRM applications. See "Configuring Ro PCP Mediation" for more information. |
The Call Handling tab enables you to set up how IM-OCF PCP handles sessions. Table 27-2 describes configuration parameters in the General subtab.
Table 27-2 IM-OCF PCP Call Handling General Parameters
| Name | Type | Description |
|---|---|---|
|
Event Handling |
STRING |
Specifies which mode of Ro operation IM-OCF PCP uses to support event-based charging. Possible values:
Default value: ECUR |
|
Termination-Cause AVP on SAL BYE |
STRING |
Specifies how to set a CCR Termination-Cause AVP when session is disconnected by an internal Service Broker SAL BYE message. Possible values:
Default value: DIAMETER_LOGOUT |
|
Termination-Cause AVP on SAL CANCEL |
STRING |
Specifies how to set a CCR Termination-Cause AVP when session is disconnected by an internal Service Broker SAL CANCEL message. Possible values:
Default value: DIAMETER_SERVICE_NOT_PROVIDED |
|
Termination-Cause AVP on SAL Final Error Response |
STRING |
Specifies how to set a CCR Termination-Cause AVP when session is disconnected by an internal Service Broker SAL final error response message. Possible values:
Default value: DIAMETER_SERVICE_NOT_PROVIDED |
The Diameter Credit Control Application tab enables you to configure parameters related to the IM-OCF PCP Diameter Credit Control Application (DCCA) interface. The Diameter Credit Control Application tab contains subtabs described in Table 27-3.
Table 27-3 IM-OCF PCP Diameter Credit Control Application Subtabs
| Subtab | Description |
|---|---|
|
AVPs |
Enables you to specify Attribute-Value Pairs (AVPs) to be set in CCRs. See "Configuring AVPs" for more information. |
|
General |
Enables you to set up a DCCA dialect and enables monitor call duration. See "Configuring General Parameters" for more information. |
The AVPs subtab enables you to specify Attribute-Value Pairs (AVPs) to be set in CCRs. Table 27-4 describes the AVPs that you can specify.
Table 27-4 IM-OCF PCP DCCA AVPs Subtab Parameters
| Name | Type | Description |
|---|---|---|
|
Destination-Host AVP |
STRING |
Specifies the value to set in a CCR Destination-Host AVP. The Destination-Host AVP combined with the Destination-Realm AVP defines a Diameter destination node that communicates with the IM-OCF PCP. The IM-OCF PCP sends messages to the address you specify for the Diameter destination node. An alternative way to specify a Diameter destination node is to set the Destination-Realm AVP field with an alias of a Diameter destination node, which you define in the Diameter SSU Outbound Destination. See "Configuring Outbound Destinations" in the Signaling Domain Configuration Guide for more information. In this case, the Destination-Host AVP is ignored. |
|
Destination-Realm AVP |
STRING |
Specifies the value to set in a CCR Destination-Realm AVP. The Destination-Realm AVP combined with the Destination-Host AVP defines a Diameter destination node that communicates with the IM-OCF PCP.The IM-OCF PCP sends messages to the address you specify for the Diameter destination node. An alternative way to specify a Diameter destination node is to set the Destination-Realm AVP field with an alias of a Diameter destination node, which you define in the Diameter SSU Outbound Destination. See "Configuring Outbound Destinations" in the Signaling Domain Configuration Guide for more information. In this case, the Destination-Host AVP is ignored. |
|
Service-Context-Id AVP |
STRING |
Specifies the value to set in a CCR Service-Context-Id AVP. Default value: 32260@3gpp.org |
|
User-Name AVP |
STRING |
Specifies the value to set in a CCR User-Name AVP. |
|
Ro Node-Functionality AVP |
INT |
Specifies the value to set in a CCR Node-Functionality AVP. Possible values:
Default value: 6 |
The General subtab enables you to set up a DCCA dialect and enable monitor call duration. Table 27-5 describes the parameters you can configure.
You can set up IM-OCF PCP to trigger an MRF to play announcements. Using the Async Announcement Manager tab, you can specify the alias of the MRF that plays announcements. In addition, you set up the rules that define the announcement to be played and the way how the MRF plays this announcement. For example, you can define that the MRF plays an announcement to a calling party when the time granted for the call is over, and the mobile subscriber is located in the home network.
You set up the Announcement Manager by configuring parameters on the subtabs described in Table 27-6.
Table 27-6 IM-OCF PCP Async Announcement Manager Subtabs
| Subtab | Description |
|---|---|
|
General |
Enables you to specify the alias of the MRF that plays announcements. See "Configuring General Parameters" for more information. |
|
Async Announcements |
Enables you to set up the rules that define announcements to be played as well as to specify how the MRF plays these announcements. See "Configuring Async Announcements" for more information. |
The General subtab enables you to specify the alias of the MRF that plays announcements. Table 27-7 describes the parameter you can configure.
The Async Announcements subtab enables you to set up rules for playing announcements. In addition, you set up the rules that define the announcement to be played and the way how the MRF plays this announcement.
The subtab contains the table in which each row represents a single rule. Table 27-8 describes the parameters you can configure.
Table 27-8 Async Announcement Manager Announcements Parameters
| Name | Type | Description |
|---|---|---|
|
Name |
STRING |
Specifies the unique identifier of the rule. |
|
Enabled |
BOOL |
Specifies whether or not the announcement is enabled. Possible values:
Default value: TRUE |
|
Reason Type |
STRING |
Specifies the parameter that IM-OCF PCP checks in the CCA message received from the online charging server. When the value of the specified parameter matches the range that you defined using the Lower Limit and Upper Limit parameters, IM-OCF PCP triggers the MRF to play the announcement. Possible values:
Default value: ANY Note: When you set Reason Type to ANY, IM-OCF PCP always triggers the MRF to play the announcement. |
|
Lower Limit |
INT |
Specifies the lower limit of the range for the parameter that you specified in Reason Type. When the value of the specified parameter is greater than the value set in Lower Limit and less than the value set in Upper Limit, IM-OCF PCP triggers the MRF to play the announcement. To configure IM-OCF PCP to trigger the MRF to play the announcement, regardless of the value of the lower limit, set this parameter to -1. Note: IM-OCF PCP does not use the Lower Limit parameter if you set Reason Type to ANY. |
|
Upper Limit |
INT |
Specifies the upper limit of the range for the parameter that you specified in Reason Type. When the value of the specified parameter is greater than the value set in Lower Limit and less than the value set in Upper Limit, IM-OCF PCP triggers the MRF to play the announcement. To configure IM-OCF PCP to trigger the MRF to play the announcement, regardless of the value of the upper limit, set this parameter to -1. Note: IM-OCF PCP does not use the Upper Limit parameter if you set Reason Type to ANY. |
|
Network |
STRING |
Specifies the location of the mobile subscriber required for triggering the MRF to play the announcement. Possible values:
Alternatively, you can specify the ID of a specific MSC that serves the mobile subscriber. |
|
Service Side |
STRING |
Specifies the IM-OCF PCP's service side required for triggering the MRF to play the announcement. Possible values:
Default value: BOTH |
|
Call State |
STRING |
Specifies the call state when IM-OCF PCP triggers the MRF to play the announcement. Possible values:
Default value: PRECALL |
|
Priority |
INT |
Specifies the order in which the MRF plays different announcement when the conditions of multiple rules are met. Default value: 0 |
|
Announcement Code |
INT |
Specifies the identifier of the announcement that the MRF plays. Default value: 0 |
|
Threshold |
INT |
Specifies how much time, in seconds, prior to the end of quota, IM-OCF PCP triggers the MRF to play the announcement. IM-OCF PCP uses the Threshold parameter only for the announcements whose Call State parameter is set to MIDCALL. Default value: 0 Note: Setting the Threshold parameter to any positive value when Call State set to PRECALL or POSTCALL causes an error. |
The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-OCF PCP. For more information about configuring monitoring, see "Configuring Monitoring with the Administration Console".
In Online Mediation Solution Controller, Service Broker relies upon an external online charging server (OCS) to apply charges for the use of network services.
When an online charging server is unavailable, IM-OCF PCP switches to the special mode known as degraded mode. This mode enables IM-OCF PCP to continue a session and charge a mobile subscriber during the time when the charging server is temporarily unavailable.
To check the availability of the charging server, every time when IM-OCF PCP sends an accounting request to the charging server, IM-OCF PCP waits a specified period of time for a response from the server. If the server does not respond, IM-OCF PCP switches to the degraded mode.
After IM-OCF PCP switched to the degraded mode, IM-OCF PCP handles the session in this mode until the session is terminated even if the online charging server becomes available. However, when the charging server becomes available, IM-OCF PCP sends to the server charging information gathered during the session.
In the degraded mode, IM-OCF PCP communicates with the Service Broker local charging server. The local online charging server imitates the work of an external charging server. This means that the local charging server can receive Credit Control Requests (CCRs) from, and send Credit Control Answers (CCAs) to, IM-OCF PCP.
To gather this information, IM-OCF PCP writes Charging Data Records (CDRs). IM-OCF PCP replays the CDRs to the online charging server after this server becomes available again. Then the server actually charges the mobile subscriber.
For more information, see the discussion on administrating the degraded mode in Oracle Communications Service Broker Online Mediation Controller Implementation Guide.
You use the Degraded Mode tab to configure the parameters of this mode as described in Table 27-9.
Table 27-9 Degraded Mode Parameters
| Name | Type | Description |
|---|---|---|
|
On OCF Failure |
STRING |
Specifies the behavior of IM-OCF Ro when the OCF fails. Possible values:
Default value: USE_LOCAL_REFUSE |
|
CDR Mode |
STRING |
Specifies how IM-OCF PCP writes CDRs. Possible options:
Default value: NORMAL |
|
CDR Writer Impl |
STRING |
Specifies the full path of the bundle that implements the CDR writer functionality. This is a preset parameter. Do NOT change the value of this parameter. |
|
CDR Writer Service |
STRING |
Specifies the full path of the CDR writer service. This is a preset parameter. Do NOT change the value of this parameter. |
|
Degraded Mode Timer |
INT |
Specifies the period of time, in milliseconds, that IM-OCF PCP waits for a response from the online charging server. If the online charging server does not respond within the specified period of time, IM-OCF PCP switches to the degraded mode. |
|
Local-OCF Alias |
STRING |
Specifies the alias of the local online charging server. This alias is mapped to the destination host and destination realm of the local online charging server as defined in the configuration of Diameter SSU outbound routing rules. For more information, see the discussion on configuring outbound destinations in Diameter SSUs in Oracle Communications Service Broker Signaling Domain Configuration Guide. |
|
Local-OCF External Protocol |
STRING |
Specifies the protocol that IM-OCF PCP uses to communicate with the local online charging server. |
|
Degraded Mode Error Codes |
STRING |
Specifies the error codes that trigger IM-OCF Ro to enable the degraded mode. You can type several error codes separated by comma. |
IM-OCF PCP translates Ro messages to PCP messages and communicates with BRM applications using the Ro PCP mediator.
You set up the mediator by configuring parameters on the subtabs described in Table 27-10.
Table 27-10 Ro PCP Mediation Subtabs
| Subtab | Description |
|---|---|
|
General |
Enables you to define how IM-OCF PCP communicates with BRM applications. See "Configuring General Parameters" for more information. |
|
SSU PCP Alias Resolver |
Enables you to configure the resolution mechanism that routes requests based on the value of an AVP inside the request. See "Configuring SSU PCP Alias Resolver" for more information. |
|
Service types |
Enables you to set up mapping between Diameter Ro Service-Identifier AVP and BRM service types. See "Configuring Service Types" for more information. |
|
Opcode mapping |
Enables you to map new Diameter Ro requests to BRM PCM operation codes. See "Configuring Opcode Mapping" for more information. |
|
Degraded Mode |
Enables you to specify the error codes and response codes to trigger IM-OCF PCP to process a request in the degraded mode. See "Configuring the Degraded Mode" for more information. |
Using the General subtab, you define how IM-OCF PCP communicates with BRM applications. Table 27-11 describes the parameters that you can configure.
Table 27-11 Ro to PCP Mediation General Parameters
| Name | Type | Description |
|---|---|---|
|
Client Program Name |
String |
The name representing IM-OCF PCP as a BRM client application when accessing BRM. Default value: Matrix |
|
Object Type |
String |
Always set this value to gsm. |
|
Default Opcode Timeout |
Integer |
The time to allow for a charging requests to execute before it is considered to have timed out. Given in seconds. |
|
Reservation Expiration Time |
Integer |
The time BRM applications keeps reservation objects before they release them. Given in milliseconds. Default value: 86400000 (24 hours) See "About Creating Reservations" in the chapter "Reserving Resources for Concurrent Network Sessions" in Oracle Communications Billing and Revenue Management Configuring and Collecting Payments. |
IM-OCF PCP routes outgoing PCP requests through connection pools that you create. For more information, see the discussion on creating BRM connection pools in Oracle Communications Service Broker Online Mediation Controller Implementation Guide.
By default, IM-OCF PCP routes requests through all connection pools in a round-robin fashion. However, you can also enable a resolution mechanism that routes requests based on the value of an AVP inside the request. In this case, the value of the AVP is resolved into a connection pool. The value of the AVP needs to match the alias of a destination BRM application, that is the alias of a PCP network entity configured in the PCP SSU.
Table 27-12 describes the parameters that you can configure.
Table 27-12 SSU PCP Alias Resolver Parameters
| Name | Type | Description |
|---|---|---|
|
Enable SSU PCP Alias Resolution |
Boolean |
Specifies whether to enable the connection pool resolution mechanism or not. Possible values:
Default value: false |
|
AVP Code |
Integer |
The code of the AVP based on which value the connection pool resolution is done. Default value: 283 (Destination-Realm AVP) |
|
AVP Vendor ID |
Integer |
The vendor ID of the AVP you entered in AVP Code. Default value: 0 |
Using the Service types tab, you set up mapping between Diameter Ro Service-Identifier AVP and BRM service types. Table 27-13 describes the parameters that you can configure.
Table 27-13 Ro to PCP Mediation Service Types Parameters
| Name | Type | Description |
|---|---|---|
|
Service Identifier |
Integer |
The Diameter Ro service identifier to be mapped to BRM service type |
|
Service Type |
String |
The BRM service type to use for the corresponding Diameter Ro service id. For example, service/telco/gsm/sms |
|
Default Service Type |
Boolean |
Set to:
|
Using the Opcode mapping tab, you map new Diameter Ro requests to BRM PCM operation codes.
To map new Diameter Ro requests to BRM PCM operation codes:
In the Opcode mapping tab, in the navigation tree, select the type of Diameter request that you want to add mapping for.
Click the Plus (+) button at the bottom of the navigation tree area. A new AVP node is added.
In the AVP tab in the right hand pane, enter the following fields for the AVP that you want to map:
AVP Code
AVP Vendor ID
AVP Value
Click the Add Opcode Mapping button. The Mapping tab appears.
In the Mapping tab, set the following fields as described:
In the Processor Class field, enter name of the name of the processor class implementing the mapping that you are currently configuring.
In the Opcode ID and Opcode Flag fields, enter the BRM operation code and operation flag.
In the Opcode Timeout field, enter the time to allow for the BRM operation to execute before it is considered to have timed out. Given in milliseconds.
Using the Degraded Mode tab, you can specify the error codes and response codes to trigger IM-OCF PCP to process a request in the degraded mode. Table 27-14 describes the parameters that you can configure.
Table 27-14 Rf to PCP Degraded Mode Parameters
| Name | Type | Description |
|---|---|---|
|
BRM error codes |
STRING |
Specifies the error codes that trigger IM-OCF PCP to handle the request in the degraded mode. You can enter multiple error codes separated by comma. |
|
Result code |
STRING |
Specifies the result code that the mediator should generate to trigger IM-OCF PCP o handle the request in the degraded mode. |
Service Broker provides a set of MBeans that provide attributes and operations for configuring the IM-OCF PCP through JMX. Figure 27-1 shows the hierarchy of the IM-OCF PCP MBeans.
The following sections provide reference information for the IM-OCF PCP configuration MBeans.
Note:
MBeans described in this guide may include additional advanced attributes, which are not described in the guide. Advanced attributes are reserved for internal use. Do not change these attributes.The following MBeans are common for all components of Service Broker and described in "Configuring Monitoring with Java MBeans":
MonitoringGeneralMBean
ThresholdCrossedNotificationRulesMBean
ThresholdCrossedNotificationRuleMBean
StateChangedNotificationRulesMBean
StateChangedNotificationRuleMBean
ImocfpcpMBean is a root MBean for the IM-OCF PCP configuration.
Created automatically
None
ObjectName getCallHandling()
Gets a reference to the instance of CallHandlingMBean
ObjectName getDiameterCreditControlApplicationAvps()
Gets a reference to the instance of DiameterCreditControlApplicationAvpsMBean
ObjectName getDiameterCreditControlApplicationGeneral()
Gets a reference to the instance of DiameterCreditControlApplicationGeneralMBean
ObjectName getMonitoringGeneral()
Gets a reference to the instance of MonitoringGeneralMBean
ObjectName getThresholdCrossedNotificationRules()
Gets a reference to the instance of ThresholdCrossedNotificationRulesMBean
ObjectName getStateChangedNotificationRules()
Gets a reference to the instance of StateChangedNotificationRulesMBean
CallHandlingMBean enables you to configure how a call is handled.
Created automatically
EventHandling
TerminationCauseAvpOnSalBye
TerminationCauseAvpOnSalCancel
TerminationCauseAvpOnSalFinalErrorResponse
For more information on these attributes, see Table 27-2.
None
DiameterCreditControlApplicationAvpsMBean enables you to specify Attribute-Value Pairs (AVPs) to be set in CCRs.
Created automatically
DestinationHostAvp
DestinationRealmAvp
ServiceContextIdAvp
UserNameAvp
RoNodeFunctionalityAvp
For more information on these attributes, see Table 27-4.
None
DiameterCreditControlApplicationGeneralMBean enables you to set up a DCCA dialect and enable monitor call duration.
Created automatically
DccaDialect
For more information on these attributes, see Table 27-5.
None
DegradedModeMBeanMBean enables you to configure how IM-OCF Ro operates in the degraded mode.
com.convergin:Type=DiameterCreditControlApplicationAvps,Version=MBean_Version,Location=AdminServer,Name=IMOCF.Instance_Name
Created automatically
OnOCFFailure
CDRMode
CDRWriterImpl
CDRWriterService
DegradedModeTimer
LocalOCFAlias
ExternalProtocol
Degraded Mode Error Codes
For more information on these attributes, see Table 27-9.
None
AsyncAnnouncementManagerGeneralMBean enables you to specify the alias of the MRF that IM-OCF Ro triggers to play announcements. Each instance of IM-OCF Ro can trigger only one instance of the MRF.
com.convergin:Type=AsyncAnnouncementManagerGeneral,Version=MBean_Version,Location=AdminServer,Name=IMOCF.Instance_Name
Created automatically.
MrfAlias
For more information about this attribute, see Table 27-7.
None
AnnouncementInfoTableMBean enables you to manage rules for playing announcements. Each rule defines conditions and the announcement that the MRF plays, if these conditions are met.
Each rule is represented by an instance of AnnouncementInfoMBean. You need to create a separate instance of AnnouncementInfoMBean for each rule.
com.convergin:Type=AnnouncementInfoTable,Version=MBean_Version,Location=AdminServer,Name=IMOCF.Instance_Name
Created automatically.
None
ObjectName createAnnouncementInfo()
Creates an instance of AnnouncementInfoMBean.
void destroyAnnouncementInfo
Destroys an instance of AnnouncementInfoMBean.
ObjectName lookupAnnouncementInfo
Returns the reference to a specified instance of AnnouncementInfoMBean.
AnnouncementInfo enables you to set up parameters of a rule for playing announcements. A rule defines conditions and the announcement that the MRF plays, if these conditions are met. In addition, rules determine how the MRF plays the announcement.
You need to create a separate instance of AnnouncementInfoMBean for each rule.
com.convergin:Type=AnnouncementInfo,Version=MBean_Version,Location=AdminServer,Name=Announcement_Name
AnnouncementInfoTable.createAnnouncementInfo()
Enabled
ReasonType
ReasonFrom
ReasonTo
Network
ServiceSide
CallState
Priority
AnnouncementCode
Threshold
For more information about these attributes, see Table 27-8.
None
pcp-mediator-configMBean is the root MBean that you use to configure the Ro PCP mediator.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config
Created automatically.
None
void addReservation_expiration_time()
Creates an instance of reservation_expiration_timeMBean.
void removeReservation_expiration_time()
Destroys an instance of reservation_expiration_timeMBean.
void addOpcode_mapping()
Creates an instance of opcode_mappingMBean.
void removeOpcode_mapping()
Destroys an instance of opcode_mappingMBean.
void addHost_station_id()
Creates an instance of host_station_idMBean.
void removeHost_station_id()
Destroys an instance of host_station_idMBean.
Using brm-client-program-nameMBean, you specify the name that represents IM-OCF PCP as a BRM client application when accessing BRM.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=brm-client-program-name
Created automatically.
brm-client-program-name
For more information about this attribute, see Table 27-11.
None
Using brm-object-typeMBean, you specify the object type. Always set this value to gsm.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=brm-object-type
Created automatically.
brm-object-type
For more information about this attribute, see Table 27-11.
None
Using ccr-timeoutMBean, you specify the time, in seconds, to allow for a charging requests to execute before it is considered to have timed out.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=ccr-timeout
Created automatically.
ccr-timeout
For more information about this attribute, see Table 27-11.
None
Using reservation-expiration-timeMBean, you specify the time, in seconds, to allow for a charging requests to execute before it is considered to have timed out.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=reservation-expiration-time
Created automatically.
reservation-expiration-time
For more information about this attribute, see Table 27-11.
None
Using ssu-pcp-alias-resolveMBean, you can configure the resolution mechanism that routes requests based on the value of an AVP inside the request. In this case, the value of the AVP is resolved into a connection pool. The value of the AVP needs to match the alias of a destination BRM application, that is the alias of a PCP network entity configured in the PCP SSU.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=ssupcp-alias-resolve
Created automatically.
None
None
Using avp-codeMBean, you specify the code of the AVP based on which value the connection pool resolution is done.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=ssupcp-alias-resolve,name2=avp-code
Created automatically.
avp-code
For more information about this attribute, see Table 27-12.
None
Using enabledMBean, you specify whether or not to enable the connection pool resolution mechanism.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=ssupcp-alias-resolve,name2=enabled
Created automatically.
enabled
For more information about this attribute, see Table 27-12.
None
Using vendor-idMBean, you specify the vendor ID of the AVP you entered in AVP Code.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=ssupcp-alias-resolve,name2=vendor-id
Created automatically.
vendor-id
For more information about this attribute, see Table 27-12.
None
service-typesMBean is the root MBean for setting up mapping between Diameter Ro Service-Identifier AVP and BRM service types.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=service-types
Created automatically.
None
void addService()
Creates an instance of serviceMBean.
void removeService(ind ServiceID)
Destroys an instance of serviceMBean.
Using serviceMBean, you can specify parameters of a single service.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=service-types,name2=service[0]
Created automatically.
None
void cloneIt()
Clones the current instance of serviceMBean.
void addDefault()
Creates an instance of defaultMBean.
void removeDefault()
Destroys an instance of defaultMBean.
Using defaultMBean, you specify whether the service defined in serviceMBean should be used as a default value.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=service-types,name2=service[0],name3=default
Created automatically
default
For more information about this attribute, see Table 27-13.
None
Using idMBean, you specify the Diameter Ro service identifier to be mapped to BRM service type.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=service-types,name2=service[0],name3=id
Created automatically.
id
For more information about this attribute, see Table 27-13.
None
Using typeMBean, you specify the BRM service type to use for the corresponding Diameter Ro service id.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=service-types,name2=service[0],name3=type
Created automatically.
type
For more information about this attribute, see Table 27-13.
None
opcode-mappingMBean is the root MBean for mapping new Diameter Ro requests to BRM PCM operation codes.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=opcode-mapping
Created automatically.
None
void addCmd()
Creates an instance of cmdMBean.
void removeCmd(int CmdID)
Destroys an instance of cmdMBean.
cmdMBean is the root MBean for configuring the mapping between AVPs and BRM PCM opcodes.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=opcode-mapping,name2=cmd[0]
opcode-mapping.addCmd()
code
void cloneIt()
Clones the current instance of cmdMBean.
void addAvp()
Creates an instance of avpMBean.
void removeAvp(int AvpID)
Destroys an instance of avpMBean.
void addOpcode()
Creates an instance of opcodeMBean.
void removeOpcode()
Destroys an instance of opcodeMBean.
Using avpMBean, you specify the AVP that you want to map to a BRM PCM operation code.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=opcode-mapping,name2=cmd[0],name3=avp[0]
cmd.addAvp()
avpCode
vendorId
value
For more information about these attributes, see "Configuring Opcode Mapping".
void cloneIt()
Clones the current instance of avpMBean.
void addAvp()
Creates an instance of avpMBean.
void removeAvp(int AvpID)
Destroys an instance of avpMBean.
void addOpcode()
Creates an instance of opcodeMBean.
void removeOpcode()
Destroys an instance of opcodeMBean.
Using opcodeMBean, you specify the BRM PCM operation code to which you want to map an AVP.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=opcode-mapping,name2=cmd[0],name3=avp[0],name4=opcode
avp.addOpcode()
None
void addProcessor_class()
Creates an instance of processor_classMBean.
void removeProcessor_class()
Destroys an instance of processor_classMBean.
void addId()
Creates an instance of idMBean.
void removeId()
Destroys an instance of idMBean.
void addFlag()
Creates an instance of flagMBean.
void removeFlag()
Destroys an instance of flagMBean.
void addTimeout()
Creates an instance of timeoutMBean.
void removeTimeout()
Destroys an instance of timeoutMBean.
Using flagMBean, you specify the BRM opcode flag.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=opcode-mapping,name2=cmd[0],name3=avp[0],name4=opcode,name5=flag
opcode.addFlag()
flag
For more information about this attribute, see "Configuring Opcode Mapping".
None
Using idMBean, you specify the BRM opcode ID.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=opcode-mapping,name2=cmd[0],name3=avp[0],name4=opcode,name5=id
opcode.addId()
id
For more information about this attribute, see "Configuring Opcode Mapping".
None
Using processor-classMBean, you specify the processor class to be used for handling opcode input and output mapping.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=opcode-mapping,name2=cmd[0],name3=avp[0],name4=opcode,name5=processor-class
opcode.addProcessor_class()
processor-class
For more information about this attribute, see "Configuring Opcode Mapping".
None
Using timeoutMBean, you specify the maximum period of time, in milliseconds, that IM-OCF PCP waits for the BRM opcode results.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=opcode-mapping,name2=cmd[0],name3=avp[0],name4=opcode,name5=timeout
opcode.addTimeout()
timeout
For more information about this attribute, see "Configuring Opcode Mapping".
None
degraded-modeMBean is the root MBean for specifying the error codes and response codes to trigger IM-OCF PCP to process a request in the degraded mode.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=degraded-mode
Created automatically.
None
None
Using brm-error-codesMBean, you specify the error codes that trigger IM-OCF PCP to handle the request in the degraded mode. You can provide multiple error codes separated by comma.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=degraded-mode,name2=brm-error-codes
Created automatically.
brm-error-codes
For more information about this attribute, see Table 27-14.
None
Using result-codeMBean, you specify the result code that the mediator should generate to trigger IM-OCF PCP o handle the request in the degraded mode.
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2ro,version=MBean_Version.SNAPSHOT,name0=pcp-mediator-config, name1=degraded-mode,name2=result-code
Created automatically.
result-code
For more information about this attribute, see Table 27-14.
None
|
 Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
