Skip Headers
Oracle® Communications Service Broker Configuration Guide
Release 5.0

Part Number E15182-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

21 Configuring SM-PME

The following sections describe how to configure SM-PME using the Service Broker Administration Console and Java MBeans:

Configuring SM-PME with the Administration Console

This section describes how to configure the SM-PME using the Service Broker Administration Console.

To access the SM-PME Configuration screen:

  1. In the Domain Navigation pane, select OCSB > Processing Tier > Supplementary Modules. The list of currently deployed supplementary modules is displayed.

  2. In the list of the deployed modules, select the module instance that you want to configure. The module instance configuration screen is displayed in the Configuration pane.

    The configuration screen of the SM-PME contains the parameters described in Table 21-1.

Table 21-1 SM-PME Parameters

Name Type Description

Mapping File Name


Specifies the path of the parameter mapping file.

For more information on the format of an SM-PME mapping file, see

Default Handling on Mapping Error


Specifies whether SM-PME releases or continues a session when the mapping engine fails.

Possible values:

  • Continue Session

  • Release Session

Default value: Release Session

Mapping Error Response


Specifies the SAL error response code that SM-PME returns when the mapping engine fails.

The error response code is regarded only when Default Handling on Mapping Error is set to Release Session.

Default value: 487

Understanding the SM-PME Mapping File

Application servers may impose format requirements on the messages they receive from Service Broker. This might include limitations to the structure or contents of message headers or bodies.

The SM-PME enables you to transform a structure and contents of headers and body of SAL messages generated by Service Broker to a structure and format required by an application server that receives the message. For example, you can transform a XER representation of IN messages to make CAMEL FurnishChargingInformation to fit the format required by an application server.

The OE can send a message to the SM-PME at any point of service orchestration as defined in the orchestration logic.

You can transform a structure and contents of headers and body generated by Service Broker by coding an XSL stylesheet. An XSL stylesheet must be wrapped into an XML file, known as SM-PME mapping file, that has the following structure:

      <Content-Type>type of content of a Service Broker message</Content-Type>
            <![CDATA[<xsl:stylesheet  version="1.0"xmlns:xsl="">
            XSL transformation

For example, the following SM-PME mapping file transforms a CAP phase 4 message. In this example, an XSL stylesheet parses the InitialDP message generated by Service Broker and changes the value of the Service Key parameter to 17. The rest of the message and parameters of this message remain unchanged.

<?xml version="1.0" encoding="UTF-8"?>
         <xsl:stylesheet version="1.0"    xmlns:xsl="">
            <xsl:template match="text()" />

            <xsl:template match="/Cap4">

            <xsl:template match="initialDP">
                  <xsl:copy-of select="node()[(name()!='serviceKey')]" />

Configuring SM-PME with Java MBeans

Service Broker provides the PmeMBean that enables you to configure the SM-PME through JMX. This section contains reference information on PmeMBean.


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.


PmeMBean enables you to configure the SM-PME.

Factory Method

Created automatically


For more information on these attributes, see Table 21-1.