Tuning Guide

Tuning Guide
SAP Convergent Charging (SAP CC 5.0)

Target Audience
System Administrators
Technical Consultants
PUBLIC
Document version: 1.4 – May 2019
SAP Convergent Charging 5.0 Tuning Guide (v1.4)
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document. You can find the
latest version at the following location: http://help.sap.com/cc50.
The following table provides an overview of the most important document changes.
Version Date Description
1.0 May 2017 Initial version (5.0 SP 0)
1.1 November 2017 First maintenance version (5.0 SP 1)
1.2 May 2018 Second maintenance version (5.0 SP 2)
1.3 November 2018 Third maintenance version (5.0 SP 3)
1.4 May 2019 Fourth maintenance version (5.0 SP 4)
May 2019 Public 2/150

Table of Contents
DOCUMENT HISTORY ...................................................................................................................... 2
TABLE OF CONTENTS ....................................................................................................................... 3
1 BEFORE YOU START.............................................................................................................. 10
About this Document............................................................................................................................. 10
Target Audience ..................................................................................................................................... 11
What's New in this Document ............................................................................................................... 11
What’s New in SP 4 ........................................................................................................................................... 11
What’s New in SP 3 ........................................................................................................................................... 11
What’s New in SP 2 ........................................................................................................................................... 11
What’s New in SP 1 ........................................................................................................................................... 11
What’s New in SP 0 ........................................................................................................................................... 12
Additional Information .......................................................................................................................... 12
Document Abbreviations ....................................................................................................................... 13
Document Definitions ............................................................................................................................ 13
Availability ......................................................................................................................................................... 13
Bandwidth ......................................................................................................................................................... 14
Benchmarking ................................................................................................................................................... 14
Business scenario .............................................................................................................................................. 14
Component ........................................................................................................................................................ 14
Configuring ........................................................................................................................................................ 14
Throughput........................................................................................................................................................ 14
Latency .............................................................................................................................................................. 14
Response time ................................................................................................................................................... 15
Scalability .......................................................................................................................................................... 15
Sizing ................................................................................................................................................................. 15
Tuning ............................................................................................................................................................... 15
SAP application ................................................................................................................................................. 15
SAPS................................................................................................................................................................... 16
2 SIZING SAP CONVERGENT CHARGING ....................................................................................... 17

Landscape recommendations ................................................................................................................ 17
Network recommendations ................................................................................................................... 18
OS recommendations ............................................................................................................................ 18
Disk recommendations .......................................................................................................................... 19
JVM recommendations .......................................................................................................................... 19
3 CONFIGURING SAP CONVERGENT CHARGING .............................................................................. 21
Configuring the SAP CC User Interfaces................................................................................................. 21
Configuring the desktop applications ................................................................................................................ 21
Keywords............................................................................................................................................................................................ 21
Preliminary Notes............................................................................................................................................................................... 21
Description ......................................................................................................................................................................................... 21
Configuring Core Tool......................................................................................................................................................................... 21
Configuring BART Tool........................................................................................................................................................................ 22
Configuring CAT Tool .......................................................................................................................................................................... 23
Configuring the web applications...................................................................................................................... 23
Keywords............................................................................................................................................................................................ 23

Description ......................................................................................................................................................................................... 23
Configuring Cockpit ............................................................................................................................................................................ 23
Configuring the command-line applications ..................................................................................................... 29
Keywords............................................................................................................................................................................................ 29
Description ......................................................................................................................................................................................... 30
Configuring Setup Tool ....................................................................................................................................................................... 30
Configuring Config Tool ...................................................................................................................................................................... 30
Configuring the Core Server system ...................................................................................................... 30
Allowance management ................................................................................................................................... 30
Keywords............................................................................................................................................................................................ 30
Preliminary notes ............................................................................................................................................................................... 30
Description ......................................................................................................................................................................................... 30
Allowances management with SAP CRM............................................................................................................................................ 30
Boot configuration file....................................................................................................................................... 31
Keywords............................................................................................................................................................................................ 31
Description ......................................................................................................................................................................................... 31
Configuration options ........................................................................................................................................................................ 31
Modifying the boot configuration file of an instance ......................................................................................................................... 32
Business data management .............................................................................................................................. 32
Keywords............................................................................................................................................................................................ 32
Description ......................................................................................................................................................................................... 33
Managing public holidays ................................................................................................................................................................... 33
Managing the currencies framework ................................................................................................................................................. 36
Managing the taxation framework ..................................................................................................................................................... 37
Catalog transport .............................................................................................................................................. 42
Keywords............................................................................................................................................................................................ 42
Description ......................................................................................................................................................................................... 42
Managing transport destinations ....................................................................................................................................................... 42
Scheduling transport requests operations ......................................................................................................................................... 43
Chargeable items charging process .................................................................................................................. 43
Keywords............................................................................................................................................................................................ 43
Description ......................................................................................................................................................................................... 44
Enabling the Session Database ........................................................................................................................................................... 44
Limiting the number of charging sessions .......................................................................................................................................... 44
Chargeable items recharging process ............................................................................................................... 45
Keywords............................................................................................................................................................................................ 45
Description ......................................................................................................................................................................................... 45
Configuring the retention period for counter snapshots.................................................................................................................... 45
Deactivating the recharging feature based on counter snapshots ..................................................................................................... 46
Communications channels ................................................................................................................................ 47
Keywords............................................................................................................................................................................................ 47
Description ......................................................................................................................................................................................... 47
Modifying the database communication settings .............................................................................................................................. 47
Enabling the UDP discovery mechanism ............................................................................................................................................ 47
Securing the communication channels .............................................................................................................................................. 48
Data cache management .................................................................................................................................. 48
Keywords............................................................................................................................................................................................ 48
Description ......................................................................................................................................................................................... 48
Determining the size of cached structures ......................................................................................................................................... 48
Modifying the size of cached structures............................................................................................................................................. 49
Modifying the accesses cache ............................................................................................................................................................ 50
Modifying the subscription cache ...................................................................................................................................................... 50
Modifying the session cache .............................................................................................................................................................. 50

Modifying the shared allowances cache ............................................................................................................................................ 50

Modifying the SQL statements cache ................................................................................................................................................. 51
Enabling the cache warmup mechanism ............................................................................................................................................ 51
Modifying the network data transfer mechanism .............................................................................................................................. 52
Refreshing the shared allowances cache............................................................................................................................................ 53
Data files generation ......................................................................................................................................... 54
Keywords............................................................................................................................................................................................ 54
Description ......................................................................................................................................................................................... 54
Modifying the data files processor ..................................................................................................................................................... 54
Modifying the version of data files generated by raters .................................................................................................................... 58
Enabling the file name sequencing for data files generated by raters ............................................................................................... 58
Enabling the line numbering for data files generated by raters ......................................................................................................... 59
Enabling the archive files cleaning for data files generated by raters ................................................................................................ 59
Enabling the pre-creation policy for data files generated by raters and bulkloaders ......................................................................... 60
Modifying the version of error files generated by bulkloaders .......................................................................................................... 60
Enabling the file name sequencing for error files generated by bulkloaders ..................................................................................... 60
Enabling the recording of file metadata ............................................................................................................................................. 61
Enabling the event date shifting mechanism for data files generated by raters ................................................................................ 61
Enabling the billable item validation for data files generated by raters ............................................................................................. 62
Data purging ..................................................................................................................................................... 62
Keywords............................................................................................................................................................................................ 62
Description ......................................................................................................................................................................................... 63
Configuring the allowances purge mechanism................................................................................................................................... 63
Configuring the file metadata purge mechanism ............................................................................................................................... 64
Configuring the product usage purge mechanism.............................................................................................................................. 64
Java Virtual Machine ......................................................................................................................................... 65
Keywords............................................................................................................................................................................................ 65
Description ......................................................................................................................................................................................... 65
JCo destinations................................................................................................................................................. 67
Keywords............................................................................................................................................................................................ 67
Description ......................................................................................................................................................................................... 68
Creating JCo destinations ................................................................................................................................................................... 69
Setting up the ERP reference system ................................................................................................................................................. 70
Logging and tracing .......................................................................................................................................... 70
Keywords............................................................................................................................................................................................ 70
Description ......................................................................................................................................................................................... 71
Modifying the logging and tracing policy ........................................................................................................................................... 72
Integrating SAP CC logs and traces with your Java application .......................................................................................................... 75
Master data management ................................................................................................................................ 75
Keywords............................................................................................................................................................................................ 75
Description ......................................................................................................................................................................................... 75
Configuring master data for the service provider .............................................................................................................................. 76
Configuring master data for the customers of the service provider ................................................................................................... 86
Notifications ...................................................................................................................................................... 88
Keywords............................................................................................................................................................................................ 88
Description ......................................................................................................................................................................................... 89
Available notifications ........................................................................................................................................................................ 89
Configuring the notification policy ..................................................................................................................................................... 91
Enabling the notification policy .......................................................................................................................................................... 95
Handling SAP CC notifications in your Java application ...................................................................................................................... 95
Startup configuration file .................................................................................................................................. 96
Keywords............................................................................................................................................................................................ 96


Description ......................................................................................................................................................................................... 96
Modifying a startup configuration file ................................................................................................................................................ 97
System and data auditing ................................................................................................................................. 97
Keywords............................................................................................................................................................................................ 97
Description ......................................................................................................................................................................................... 97
Measuring product usage................................................................................................................................................................... 97
Auditing master data and user operations ......................................................................................................................................... 99
Thread dump files generation ......................................................................................................................... 100
Keywords.......................................................................................................................................................................................... 100
Preliminary notes ............................................................................................................................................................................. 101
Description ....................................................................................................................................................................................... 101
Configuration options ...................................................................................................................................................................... 101
Modifying the generation of thread dump files ............................................................................................................................... 101
Third-party integration .................................................................................................................................... 102
Keywords.......................................................................................................................................................................................... 102
Description ....................................................................................................................................................................................... 102
Modifying the SAP SLD connection settings ..................................................................................................................................... 102
Users management ......................................................................................................................................... 102
Keywords.......................................................................................................................................................................................... 102
Description ....................................................................................................................................................................................... 103
Separating service and individual users ........................................................................................................................................... 103
Security policy for user passwords ................................................................................................................................................... 103
Managing working sessions within user interfaces .......................................................................................................................... 105
Creating users .................................................................................................................................................................................. 106
Resetting the emergency user.......................................................................................................................................................... 106
Configuring the BART Server system ................................................................................................... 106
Acquisition sessions and consolidation ........................................................................................................... 106
Keywords.......................................................................................................................................................................................... 106
Description ....................................................................................................................................................................................... 106
Modifying the acquisition and consolidation settings ...................................................................................................................... 106
Acquiring CDRs with the Java API ..................................................................................................................................................... 107
Acquiring CDRs with an IEC .............................................................................................................................................................. 108
BART Server configuration file ......................................................................................................................... 108
Keywords.......................................................................................................................................................................................... 108
Description ....................................................................................................................................................................................... 109
Modifying the BART Server configuration file .................................................................................................................................. 112
Communication channels ................................................................................................................................ 112
Keywords.......................................................................................................................................................................................... 112
Description ....................................................................................................................................................................................... 113
Modifying the database communication settings ............................................................................................................................ 113
Modifying the Core Server connection settings ............................................................................................................................... 113
Modifying the communication settings for acquisition and rerating operations ............................................................................. 113
Securing the communication channels ............................................................................................................................................ 114
Java Virtual Machine ....................................................................................................................................... 114
Keywords.......................................................................................................................................................................................... 114
Description ....................................................................................................................................................................................... 114
Logging and tracing ........................................................................................................................................ 114
Keywords.......................................................................................................................................................................................... 114
Description ....................................................................................................................................................................................... 114

Modifying the logging and tracing policy ......................................................................................................................................... 115

Magic Number Pattern.................................................................................................................................... 115
Keywords.......................................................................................................................................................................................... 115
Description ....................................................................................................................................................................................... 115
Setting up a pattern for magic numbers .......................................................................................................................................... 115
Monitoring and event broadcasting ................................................................................................................ 116
Keywords.......................................................................................................................................................................................... 116
Description ....................................................................................................................................................................................... 116
Modifying the monitoring settings ................................................................................................................................................... 117
Modifying the report file settings..................................................................................................................................................... 117
Rating sessions ................................................................................................................................................ 118
Keywords.......................................................................................................................................................................................... 118
Description ....................................................................................................................................................................................... 119
Modifying settings related to rating sessions management ............................................................................................................. 119
Rerating sessions ............................................................................................................................................. 119
Keywords.......................................................................................................................................................................................... 119
Description ....................................................................................................................................................................................... 119
Modifying settings related to rerating sessions management ......................................................................................................... 119
Keywords.......................................................................................................................................................................................... 120
Description ....................................................................................................................................................................................... 120
BART database ................................................................................................................................................ 120
Keywords.......................................................................................................................................................................................... 120
Description ....................................................................................................................................................................................... 120
Modifying the partitioning settings .................................................................................................................................................. 121
Configuring the Diameter Server system............................................................................................. 124
AVP dictionary ................................................................................................................................................. 124
Keywords.......................................................................................................................................................................................... 124
Description ....................................................................................................................................................................................... 124
Modifying the AVP dictionary .......................................................................................................................................................... 124
Communication Channels................................................................................................................................ 125
Keywords.......................................................................................................................................................................................... 125
Description ....................................................................................................................................................................................... 125
Securing the communication channels ............................................................................................................................................ 125
Diameter Server configuration file .................................................................................................................. 125
Keywords.......................................................................................................................................................................................... 125
Description ....................................................................................................................................................................................... 125
Modifying the Diameter Server configuration file ............................................................................................................................ 128
Java Virtual Machine ....................................................................................................................................... 128
Keywords.......................................................................................................................................................................................... 128
Description ....................................................................................................................................................................................... 128
Logging and tracing ........................................................................................................................................ 129
Keywords.......................................................................................................................................................................................... 129
Description ....................................................................................................................................................................................... 129
Modifying the logging settings of the Diameter Server .................................................................................................................... 130
Multiple services credit-control ....................................................................................................................... 130
Keywords.......................................................................................................................................................................................... 130

Description ....................................................................................................................................................................................... 131

Implementing MSCC......................................................................................................................................................................... 131
Service dictionary ............................................................................................................................................ 131
Keywords.......................................................................................................................................................................................... 131
Description ....................................................................................................................................................................................... 132
Modifying the service dictionary ...................................................................................................................................................... 132
Keywords.......................................................................................................................................................................................... 132
Description ....................................................................................................................................................................................... 132
Configuring the IEC system .................................................................................................................. 133
Scenario management .................................................................................................................................... 133
Keywords.......................................................................................................................................................................................... 133
Description ....................................................................................................................................................................................... 133
Specific actions ................................................................................................................................................ 133
Keywords.......................................................................................................................................................................................... 133
Description ....................................................................................................................................................................................... 133
4 TUNING SAP CONVERGENT CHARGING ....................................................................................135

Distributing partitions to guiders and raters using a smart mode ..................................................... 136
Keywords ......................................................................................................................................................... 136
See Also in SAP CC documentation .................................................................................................................. 136
Description ...................................................................................................................................................... 136
Activating the smart distribution mode .......................................................................................................... 136
Tuning the smart distribution mode ................................................................................................................ 138
Protecting raters and guiders against warmup overloading .......................................................................... 138
Modifying the table rollover policy for charging sessions ................................................................... 141
Keywords ......................................................................................................................................................... 141
Description ...................................................................................................................................................... 141
Enabling the table rollover mechanism ........................................................................................................... 141
Tuning the table rollover policy ....................................................................................................................... 141
5 MONITORING SAP CONVERGENT CHARGING .............................................................................143

Monitoring the file metadata .............................................................................................................. 144
Keywords ......................................................................................................................................................... 144
Description ...................................................................................................................................................... 144
Monitoring the unprocessed items.................................................................................................................. 144
Filtering the items ............................................................................................................................................................................ 144
Modifying the smart chart ............................................................................................................................................................... 145
Modifying the table .......................................................................................................................................................................... 145
Creating a variant ............................................................................................................................................................................. 145
6 TROUBLESHOOTING SAP CONVERGENT CHARGING ......................................................................146

Logs and traces .................................................................................................................................... 146
Troubleshooting JCo RFC communications ...................................................................................................... 146
TYPOGRAPHIC CONVENTIONS .........................................................................................................147

ICONS.......................................................................................................................................147
COPYRIGHTS ..............................................................................................................................148

Disclaimer ............................................................................................................................................ 149

1 Before You Start

About this Document
SAP Convergent Charging is made up with a set of Java-based software components that you can install within your
landscape to perform your business operations. For further information about the different software components,
refer to the “Architecture” section of the SAP Convergent Charging Application Help documentation.
These software components are grouped upon the following categories:
Server systems (Core Server, BART Server, Diameter Server and Import/Export Connector)
User interfaces (Cockpit, Core Tool, BART Tool, CAT Tool, Admin+, BART+, Setup Tool, BART Setup Tool, Config
Tool, HTTP Client and Message Client)
Databases (Core database, BART database and IEC database)
The following schema provides you with an overview of the interactions between the different software components
within an SAP CC landscape:
This Tuning Guide is an SAP document that contains:

Recommendations about the sizing of the different aspects of your landscape, such as:
Deployment strategy for the SAP CC instances
Network, disks and operating system specifications and requirements
JVM settings
Procedures for configuring some technical and business aspects of the different software components
Procedures for tuning some technical mechanisms used by the different software components

Orientations for troubleshooting problems using the mechanisms provided by SAP Convergent Charging
Target Audience
This guide is intended for the following audience:
System Administrators
Technical Consultants
What's New in this Document
What’s New in SP 4
As of SP 4, SAP Convergent Charging 5.0 provides you with:
The following new sections related to the configuration of the Core Server system:
Modifying the network data transfer mechanism
Modifications and enhancement of the following sections:
Boot configuration file
Configuring Cockpit
Distributing partitions to guiders and raters using a smart mode, that now contains a new procedure which
explains how to protect raters and guiders against possible overloading during warmup operations
Modifying the table rollover policy for charging sessions
Chargeable items charging process
Data files generation
Configuring Cockpit
Logging and tracing
Business data management, including the migrated content of the “Currencies and tax management” section
Master data management
JCo destinations
Third-party integration
The following new sections related to the troubleshooting of SAP CC:
Troubleshooting JCo RFC communications


System and data auditing
Configuring Cockpit
Data purging
The following new sections related to the configiguration of the Core Server system:
Currencies and tax management
Users management
The following new sections related to the configuration of the BART Server system:
Acquisition sessions and consolidation
BART Server configuration file
Java Virtual Machine
Communication channels
Logging and tracing
Magic Number Pattern
Monitoring and event broadcasting
BART database
The following new sections related to the configuration of the Diameter Server system:
Diameter Server configuration file
Communication Channels
Logging and tracing
Service dictionary
AVP dictionary
Multiple services credit-control
The following new monitoring procedures:
Monitoring the file metadata
As of SP 0, SAP Convergent Charging 5.0 provides you with an initial version of this documentation, that contains
reviewed and updated content of the following documentations:
Sizing and Tuning for SAP CC 4.0 and Later Releases
Partial content of the Configuration and Implementation Guide for SAP CC 4.1
In addition, this documentation provides you with a new “Tuning SAP Convergent Charging” section containing
procedures that can be used for adjusting settings of SAP CC.
Additional Information
For more information about specific topics, see the quick links as shown in the table below:
Content Quick Link
SAP CC documentation http://help.sap.com/cc50
NOTE

SAP CC is part of the SAP solution SAP Billing based on SAP Business Suite or SAP S/4
HANA. Consult the central solution information at the following address:
https://wiki.hybris.com/display/ybilling/Library
Related SAP notes http://support.sap.com/notes
Related release notes http://service.sap.com/public/releasenotes
Released platforms http://service.sap.com/platforms
SAP Solution Manager http://help.sap.com/solutionmanager
Document Abbreviations
The table below shows the list of abbreviations used throughout this document:
Abbreviation Meaning
CEA Capabilities-Exchanging-Answer (Diameter)
CER Capabilities-Exchanging-Request (Diameter)
CFS Clustered File System

CIF Charging output Integration Framework
CPU Central Processing Unit, also called Core
CRM Customer Relationship Management
DWA Device-Watchdog-Answer (Diameter)
DWR Device-Watchdog-Request (Diameter)
MSCC Multiple-Services Credit Control (Diameter)
NUMA Non-Uniform Memory Access

RDBMS Relational Database Management System
RIF Rerating Integration Framework
SAPS SAP Application Performance Standard
SAP MC SAP Management Console
SAP MMC SAP Microsoft Management Console
SSD Solid-State Drive
TIF Transaction Integration Framework
UDP User Datagram Protocol
Document Definitions
Availability
The availability of a system represents the probability that this system will work as expected during a processing
time, that thus characterizes its reliability. This probability is expressed using “nines” terms:
One-nine, which means that the system is available 90% of the time, and can be unavailable 36,5 days/year
Two-nines, which means that the system is available 99% of the time, and can be unavailable 3,65 days/year

Three-nines, which means that the system is available 99,9% of the time, and can be unavailable 8,76 hours/year
Four-nines, which means that the system is available 99,99% of the time, and can be unavailable 52,5 mins/year
Five-nines, which means that the system is available 99,999% of the time, and can be unavailable 31,5 sec/year
Bandwidth
Bandwidth represents a measurement of bit-rate related to available or consumed digital resources, expressed in
bits (or multiple of bits) per second (bit/s, kbit/s, Mbit/s, Gbit/s, and so on).
Benchmarking
Sizing information can be determined using SAP Standard Application Benchmarks (). Released for technology
partners, benchmarks provide basic sizing recommendations to customers by injecting a substantial load upon a
system during the testing of new hardware, system software components or RDBMS. All performance data relevant
to the system, user, and business applications are monitored during a benchmark run and can be used to compare
the benchmarked platforms.
For more information, refer to the following location: http://www.sap.com/benchmark.
Business scenario
From a microeconomic perspective, a business scenario is a cycle which consists of several different interconnected
logical processes in time. Typically, a business scenario includes several company departments and involves other
business partners. From a technical point of view, a business scenario needs at least one SAP application (SAP ERP,
SAP SCM, or others) for each cycle and perhaps other third party systems. A business scenario is a unit which can be
implemented separately and reflects the customer’s prospective course of business.
Component
A component is the smallest individual unit considered within the Solution Development Lifecycle. Components are
separately produced, delivered, installed, and maintained.
Configuring
Configuring a system consists in determining the relevant behavior for each element that is part of this system, in
order to provide technical or business functionalities and thus fit specific requirements.
Throughput
Taking part of a system productivity evaluation, the throughput represents the maximum rate of digital resources
that a system can process in a given time, that can be measured via benchmarking operations.
Latency
Taking part of a system productivity evaluation, the latency represents the time interval experienced by a system
between the incoming request and the provided response, that:
Characterizes the velocity of this system, and by extension its usability
Limits the throughput

Response time
Taking part of a system productivity evaluation, the response time represents the total amount of time that is taken
to respond to an incoming request. This total amount is the sum of the following elements:
Service time, that represents the time taken by the system to work on the request, whose value varies according
to the workload
Wait time, that represents the time the incoming request had to wait in a queue before being taken into
account by the system for working purpose
Transmission time, that represents the travelling time used to transfer the incoming request between the
different concerned elements
Scalability
Scalability represents the ability of an element (system, network, process, and so on) to handle an increasing
workload or the ability of this element to be enlarged in order to handle that increasing workload. 2 differents
categories of scalability exist, that can also be combined together:
Horizontal scalability, that consists in adding new systems to distribute the workload
Vertical scalability, that consists in modifying the resources (CPU, memory, storage capacities, networking
capacities, and so on) of the available systems
Sizing
Sizing a system consists in determining the hardware requirements for this system, such as:
Network bandwidth
Physical memory
CPU processing power
I/O capacities
The size of both hardware and database is influenced by business and technological aspects, which means that the
number of users and the related workload they generate must be taken into account.
SAP SE considers 2 different sizing levels:
Initial sizing, which refers to the sizing approach that provides guidelines about platform-independent
requirements of the hardware resources that are necessary for representative and standard delivery SAP
applications. These initial sizing guidelines assume optimal system parameter settings, standard business
scenarios, and so on
Expert sizing, which refers to a sizing operation that consists in analyzing customer-specific data in order to
provide more details on the sizing result. The main objective is to determine the resource consumption of
customized content and applications (not SAP standard delivery) using comprehensive measurements.
Tuning
Tuning an application consists in optimizing the configuration of this application to ensure its scalability and
performance when responding to an increasing workload.
SAP application
An SAP application is an SAP software solution that serves a specific business area like ERP, CRM, PLM, SRM, SCM,
and CC.

SAPS
The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of
a system configuration in an SAP environment. It is derived from the Sales and Distribution (SD) Benchmark, where
100 SAPS is defined as the computing power to handle 2,000 fully business processed order line items per hour.
For more information, refer to the following location: http://www.sap.com/benchmark → Measuring in SAPS.

2 Sizing SAP Convergent Charging

SAP Convergent Charging provides a rating and charging solution for high-volume processing in service industries,
that delivers pricing design capabilities, high performance rating and convergent balance management. Capable of
operating in real-time and in batch mode, it includes hybrid prepaid/postpaid charging capabilities, unrivaled
marketing agility for service pricing, carrier-grade scalable performance and high availability.
To ensure these performance and high availability capabilities, it is necessary to respect the following
recommendations when deploying a SAP Convergent Charging landscape:
Landscape organization
Network specifications
Operating system settings
Disk requirements
JVM settings
Landscape recommendations
Concerning your SAP Convergent Charging landscape, SAP SE recommends that you implement the following
instructions in terms of hosts sizing:
Dispatcher and guider instances should be co-located on the same physical host. All deployed dispatchers are
running, but one of them is considered as the master dispatcher. The other dispatchers are considered as slaves
Rater instances should be deployed on dedicated physical hosts. The more raters are installed, the less number
of partitions are assigned to each rater, which reduces impacts in case of rater failure. As a consequence, a
higher number of small-size raters is preferable to a smaller number of large-size raters
Updater instances can be deployed on dedicated physical hosts, or co-located on the same physical host that
another instance. All deployed updaters are started, but only one of them is nominated by the master dispatcher
as active (ACTIVE state). The other updaters are considered as backups (WAITING state)
Bulkloader instances can be deployed on dedicated physical hosts, or co-located on the same physical host that
the rater they are working with (due to constraints related to shared file system)
Considering these recommendations, SAP SE recommends that you deploy the following instances in order to meet
HA requirements:
3 dispatcher+guider couples should be deployed, each couple being deployed on a dedicated physical host
3 raters should be deployed, each rater being deployed on a dedicated physical host
2 updaters should be deployed
NOTE
SAP Convergent Charging is designed for horizontal scalability, which means that it is possible to deploy additional
hosts in order to increase the global performance of your landscape. For these additional hosts, the above
recommendations must be followed.
In addition to this deployment strategy, SAP SE recommends that you implement the following requirements for
each host in terms of hardware:
Hyper-threading technology: To improve parallelization of computing operations, hyper-threading technology
should be activated. Each host should have up to 64 hyper-threaded cores (or 32 non-hyper-threaded cores)

installed and split among the available sockets, for 2 or 3 deployed raters. In case more raters are necessary, the
horizontal scalability of SAP CC gives the possibility to add other hosts. In case bigger machines (with more
sockets) are used, these additional installed raters shall be bound to dedicated resources using the NUMA
technology to optimize memory accesses
CPU/Core frequency: To improve the processing time of the events handled by SAP CC, the fastest available
CPUs shall be used, such as CPUs with a minimum frequency of 3.2 Ghz
Network recommendations
The different components of your SAP Convergent Charging landscape communicate over the network, which is very
solicited and implies to implement the following instructions to ensure the lowest possible latency:
Technologies: To ensure a maximum bandwith, the fastest network technologies shall be used
Shared folders: In case of host failure, folders shared by bulkloaders and raters must be accessible from other
running hosts to ensure the continuation of the data files processing operations
OS recommendations
Every host of your landscape takes part of the overall performance of SAP Convergent Charging. It is thus necessary
to implement the following instructions to handle a maximum of incoming events :
Virtualization technology: Using virtualization to split resources of bigger machines and install multiple instances
of SAP CC on similar physical hardware is not recommended
Power-saving mode: Modern CPUs can run in power-saving mode, which usually corresponds to the default
option. As SAP CC requires the maximum CPU available speed, double-check and possibly adjust the parameters
to ensure that the CPU is running in “performance” mode, which means using highest frequency
(Linux only) nproc setting: The “nproc” linux setting gives the possibility to limit the number of processes that a
user can execute simultaneously. Considering that SAP CC starts a high number of java threads, it is thus
necessary to increase the “nproc” setting in order to avoid OutOfMemory exceptions (that could occur in case
the JVM could not start a givent thread). To increase this limit, open the limits.conf file located in the
/etc/security/ folder and add or update the following lines accordingly:
<sapcc_user> soft nproc <tuned_value>
<sappcc_user> hard nproc <tuned_value>
Where:
<sapcc_user> corresponds to the operating system user related to SAP CC
<tuned_value> should be greater than the sum of all java threads started by the SAP CC instances, including
CA Introscope agent threads, JVM Garbage Collection Threads, and so on… In case of any doubt, you can set
this value to the maximum value allowed by the concrete operating system
(Linux only) nofile setting: The “nofile” linux setting gives the possibility to limit the number of file descriptors
that can be simultaneously opened. Considering that SAP CC handles a high number of files, it is thus necessary
to increase the “nofile” setting in order to avoid failures during files opening operations. To increase this limit,
open the limits.conf file located in the /etc/security/ folder and add or update the following lines
accordingly:
<sapcc_user> soft nofile <tuned_value>
<sappcc_user> hard nofile <tuned_value>
Where:
<sapcc_user> corresponds to the operating system user related to SAP CC

<tuned_value> should be large enough to ensure that SAP CC can open as many files as necessary. In case of
any doubt, you can set this value to the maximum value allowed by the concrete operating system
(Linux only) huge pages memory: Memory is managed in blocks that are called “pages” and whose default size is
set on Linux operating systems to 4096 bytes. CPUs have a built-in management unit that contains a list of these
pages, each page being referenced through a page table entry whose browsing is CPU consuming. Considering
that SAP CC manages large amounts of memory, it is thus necessary to enable the concept of “huge pages”, that
consists in blocks of memory coming in 2MB, which divides the number of page references by 512 (that is more
suitable for managing multiple gigabytes of memory. To enable huge pages, open the /etc/sysctl.conf file
that contains the configuration of the Linux kernel and add or update the following lines accordingly:
vm.hugetlb_shm_group = <group_id>
vm.nr_hugepages = <nb_pages>
shmmax = <tuned_value>
Where:
<group_id> corresponds to the group identifier of the SAP CC “<SYSTEM_ID>adm” user that will reserve
huge pages
<nb_pages> corresponds to the multiplier of the huge page size to compute reserved memory, which should
include JVM memory and SAP CC cached structures
<tuned_value> should be greather than the reservable memory
And execute the following command to apply the modifications:
sysctl -p
Then, allow the user to use and lock memory by opening the /etc/security/limits.conf file and adding or
updating the following lines accordingly:
@<sapcc_user> soft memlock unlimited
@<sapcc_user> hard memlock unlimited
Where <user> corresponds to the operating system user that will reserve memory
Finally, update the JVM settings by adding the -XX:UseLargePages option within the jstart.config files of
each instance, and restart these instances.
Disk recommendations
The processing time of the events handled by SAP CC also depends on the low latency of disk I/O operations. As a
consequence, SAP SE recommends that you implement the following instructions to ensure performance and
reliability of your landscape:
Network storage: For sharing and access optimizations, the use of network storage technologies such as NAS or
SAN shall be preferred to typical solutions based on hosts’ folders sharing
SSD technology: To minimize latency during writing operations, SSDs are recommended to store data files
generated by SAP CC. In addition, due to folders sharing requirements, the use of CFS shall be preferred.
JVM recommendations
SAP Convergent Charging is made-up with a set of java-based applications whose execution is performed by JVM
instances that can be configured to fit specific requirements. For further information about the available options,
refer to the “Java Virtual Machine” dedicated section afterwards.
Every Java object created by the SAP CC instances is handled in 2 different Java memories:

The Heap memory, which is divided into the following portions known as “generations”, whose content is
reorganized as time goes by for optimization and performance purposes:
Young generation, that represents the most active portion of the heap and that is used by SAP CC to store
the most-used objects whose lifecycle rapidly evolves
Old / Tenured generation, that represents the less active portion of the heap, used by SAP CC to store
longer-lived objects such as the objects belonging to catalogs
Permanent / Metaspace generation, that contains metadata required by the JVM
Each generation is continuously reorganized to ensure performance regarding the access to the contained
objects. This reorganization of the heap is made during “garbage collection” (GC) operations that may impact the
global performance of your landscape.
The Direct memory, that provides access to native I/O operations, and that is used by the SAP CC instances to
store the cached structures
To ensure performance and stability of your landscape, SAP SE recommends that you implement the following
instructions to set up the JVM options described in the “Java Virtual Machine” dedicated section:
JVM Option Recommendation

-Xmn<SIZE> The size of the young generation of the heap memory depends on your
business. SAP SE recommends you to consult the “Generate Java GC Log for
SAP Convergent Charging” SAP Note 1950168 documentation, that you can
consider as an starting point to set a relevant size for the young generation
used by your SAP CC instances
-Xms<SIZE> Considering a default 4 Go size used to store the catalog data within the
tenured generation of the heap memory, SAP SE recommends you to set
the following value:
-Xmn + 4 Go
-Xmx<SIZE> Same value as -Xms
-Xss<SIZE> 256k
-XX:CompileThreshold=<NUMBER> 1000
-XX:SurvivorRatio=<RATIO> 16
-XX:TargetSurvivorRatio=<NUMBER> 90
-XX:ConcGCThreads=<NUMBER> Set a value that corresponds to:
<Total nb of cores on the host> / <nb of instances on the host>
NOTE
This number should not exceed the number of cores allocated to the
instance (for example in case of NUMA binding)
-XX:ParallelGCThreads=<NUMBER> Same value as -XX:ConcGCThreads
-XX:PromotedPadding=<NUMBER> 5 for raters only
-XX:{+-}UseParallelOldGC Enable the option
-XX:{+-}UseSplitVerifier Enable the option
-XX:{+-}ScavengeBeforeFullGC Enable the option
-XX:{+-}UseAdaptiveSizePolicy Enable the option for all instances but raters
-XX:{+-}TieredCompilation Enable the option

3 Configuring SAP Convergent Charging

Configuring the SAP CC User Interfaces
Configuring the desktop applications
Keywords
GUI, graphical user interface, Core Tool, BART Tool, CAT Tool
Preliminary Notes
For further information, refer to the following SAP CC documentations:
“Launching Core Tool” section of the SAP CC Installation Guide documentation
“Launching BART Tool” section of the SAP CC Installation Guide documentation
“Launching CAT Tool” section of the SAP CC Installation Guide documentationDescription
Description
All desktop applications of SAP Convergent Charging have a default configuration that relies on a configuration file
that is automatically created (at first launch time) if this file does not exist. You can use the following procedures to
modify the configuration file of the different graphical user interfaces of your SAP CC landscape and thus fit your
specific needs:
Configuring Core Tool
Configuring BART Tool
Configuring CAT Tool
NOTES
Configuration files are available in the config folder of each user interface
The settings defined in the configuration files do not relate to an SAP user, but are applied to all SAP users
Configuring Core Tool

The starting behavior of the Core Tool user interface can be modified to fit specific needs. The following table
contains the list of available parameters that you can change:
Parameter Type Description Default value Possible values

language string Language used within the GUI EN An ISO-639 code
country string The country specific language used US An ISO-3166
within the GUI code
catalog.cache. integer Maximum period (in seconds) of 0 Any positive or
retention_period retention in a cache of some objects null integer
referenced in decision trees. value
The value 0 deactivates the cache.
The recommended value for better
user experience is 60.
frame.width integer The width of the window of the GUI 900 1 to 65536

frame.height integer The height of the window of the GUI 700 1 to 65536
help.contents.url string Address of the online helps The URL of the A valid HTTP or
help.components.url accessible from the “Help” menu of SAP CC Core Tool file URL pointing
help.portal.url the Core Tool, that can point to local user interface to online helps
files or to web address (such as SAP documentation
Help Portal) on SAP Help
Portal
xml.verbose boolean Verbose mode, used to trace false true / false
communications between Core Tool
and the dispatcher or updater
instance of the Core Server system
To modify the starting behavior of the Core Tool user interface, execute the following procedure:
1. Ensure the concerned Core Tool is completely stopped
2. Edit the “core_tool.config” configuration file. If this file does not exist, create a copy from the
“core_tool.config.sk” template file
3. Modify the value of the relevant parameters
4. Restart the Core Tool
Configuring BART Tool

The starting behavior of the Core Tool user interface can be modified to fit specific needs. The following table

country string The country specific language used US An ISO-3166 code
in the GUI
frame / width integer The width of the window of the GUI 900 1 to 65536
frame / height integer The height of the window of the GUI 700 1 to 65536
log / level integer The level of the generated log 2 0 (debug)
messages 1 (info)
2 (warning)
3 (error)
BartHelpContentsURL string Address of the online helps The URL of the A valid HTTP or
BartHelpPortalURL accessible from the “Help” menu of SAP CC BART file URL pointing
the BART Tool, that can point to local Tool user to online helps
files or to web address (such as SAP interface
Help Portal) documentation
on SAP Help
Portal
To modify the starting behavior of the BART Tool user interface, execute the following procedure:
1. Ensure the concerned BART Tool is completely stopped
2. Edit the “bart_tool.config” XML configuration file. If this file does not exist, create a copy from the
“bart_tool.config.sk” template file


4. Restart the BART Tool
Configuring CAT Tool

The starting behavior of the CAT Tool user interface can be modified to fit specific needs. The following table

country string The country specific language US An ISO-3166 code
used in the GUI
log.level string The level of the generated log inform debug
messages inform
warning
error
cat.help.contents.url string Address of the online helps The URL of the SAP A valid HTTP or
help.portal.url accessible from the “Help” menu CC CAT Tool user file URL pointing
of the CAT Tool, that can point to interface to online helps
local files or to web address (such documentation on
as SAP Help Portal) SAP Help Portal
To modify the starting behavior of the CAT Tool user interface, execute the following procedure:
1. Ensure the concerned CAT Tool is completely stopped
2. Edit the “cat_tool.config” configuration file. If this file does not exist, create a copy from the “cat_tool.config.sk”
template file
4. Restart the CAT Tool
Configuring the web applications
Keywords
GUI, graphical user interface, web application, Tomcat, Cockpit
Preliminary Notes
“Launching Cockpit” section of the SAP CC Installation Guide documentation
“Enhanced Logging and Tracing Framework” section of the SAP CC Application Help documentation
Description
SAP Convergent Charging provides an optional web application named Cockpit, that is dedicated to administrators
and consultants who needs to manage the system parameters of a Core Server system. You can use the following
procedure to modify the configuration file of the Cockpit web application and thus fit your specific needs.
Configuring Cockpit

The configuration of the Cockpit application relies on a text file named sap_cc_cockpit_<NAME>.properties,
where <NAME> corresponds to the name of the deployed Cockpit web application.
NOTES
A template file named sap_cc_cockpit_[WEB_APP_NAME].properties.sk is available in the delivered
ZIP file of the SAP CC Cockpit software unit. You can use this template to create various configuration files (but
SAP SE recommends that you do not modify the template itself).
The Cockpit configuration file uses the ISO 8859-1 character encoding format. As a consequence, characters
that cannot be directly represented in this encoding scheme must be written using unicode escapes. For
further information, refer to the Java™ Language Specification.
The following table contains the list of parameters that you can change, grouped upon the following categories:
Core Server communication settings
Core database communication settings
Cockpit database communication settings
Cache management
Data files management
User management and security settings
Tracing settings
Parameter Values Type

cc.sid By default, no SID is set. The Web application can thus 
SID of the Core Server system you want to not start.
administer. If you modify this SID while
sessions are running, the SAP CC power users
can continue their sessions and save their
modifications using the previously defined
Core Server system.
hci.http.url By default, no URL is set. The Web application can thus 
CSV list of URLs relating to deployed not start.
dispatchers. In a secure environment, use You must set URLs which correspond to instances that
URLs based on HTTPS. belong to the targeted Core Server system declared in
the “cc.sid” parameter.
sqlhelper.jdbc.uri You must set one or two valid URIs which correspond to 
JDBC URI of the reference database instance database instances.
used by SAP CC Cockpit to start For SAP HANA, the URI format is:
jdbc:sap://<primary_server>:<port>[;<secondary_server>:<por
t>][/?databaseName=<tenant_name>]
For Sybase ASE, the URI format is:
jdbc:sybase:Tds:<server>:<port>/<database_name>?<prop1>=
<value1>&<prop2>=<value2>

For Oracle with “thin” driver, the URI format is:

- jdbc:oracle:thin:@//<server>:<port>/<ServiceName>
- jdbc:oracle:thin:@<server>:<port>:<SID>
For MS SQL Server (IPv4), the URI format is:
jdbc:sqlserver://<server>:<port>;DatabaseName=<database_n
ame>;sendStringParametersAsUnicode=true[;IntegratedSecurit
y=true]
For MS SQL Server (IPv4 or IPv6), the URI format is:
jdbc:sqlserver://;serverName=<server>;port=<port>;Database
Name=<database_name>;sendStringParametersAsUnicode=tru
e[;IntegratedSecurity=true]
For IBM DB2, the URI format is:
jdbc:db2://<server>:<port>/<database_name>:currentSchema
=<schema_name>;
sqlhelper.login You must set a value that corresponds to an already 

Login used for authenticating on the Core defined user.
database
NOTE
For security reasons, SAP SE recommends that you
create a service user dedicated to connections between
SAP CC Cockpit and the Core database. This user shall
be granted a read access to database views pointing on
the FILE_METADATA and FILE_METADATA_PATH tables.
sqlhelper.password You must set a password that respects the SAP password 
Password of the previously specified login, policy.
used for authenticating on the Core database
sqlhelper.connection.count The default value is set to: 20 
Number of connections to be opened with the You can set any positive value.
Core database
sqlhelper.statement.cache.size The default value is set to: 0 
Size of the statement cache You can set any positive value.
CAUTION
SAP SE recommends that you do not modify this
parameter except under supervision of the SAP Support
team.
sqlhelper.id.interval The default value is set to: 10000 
Size of the unique ID batch reservation You can set any positive value greater than 1000.
CAUTION
SAP SE recommends that you do not modify this
parameter except under supervision of the SAP Support
team.

sqlhelper.max.redo The default value is set to: 4 

Number of times an instance will re-execute a You can set any positive value.
request in the Core database
sqlhelper.reconnect.interval The default value is set to: 10 
Duration (in seconds) between two You can set any positive value.
reconnection attempts
sqlhelper.reconnect.attempts The default value is set to: 4 
Number of attempts when connecting to the You can set any positive value.
Core database
sqlhelper.db.instance.count The default value is set to: 0 
Number of SAP CC Core database instances You can set any positive value.
that the application can connect to
sqlhelper.db.timeout The default value is set to: 0 
Frequency (in seconds) of "ping" operations You can set any positive value greater than 30. Setting
that are sent to the SAP CC Core database this parameter to 0 disables the ping operations
sqlhelper.connection.heartbeat The default value is set to: 0 
Frequency (in seconds) of "heartbeat" You can set any positive value greater than 30. Setting
operations that are sent to the Core database this parameter to 0 disables the ping operations
sqlhelper.jdbc.properties You can set a CSV formatted value as specified in RFC 
Additional properties for the SQL connections 4180, which means that:
Fields are separated by a comma delimiter and
optionally enclosed by a text double-quote
Each field is the concatenation of a property name
and a property value, using the following format:
<property_name>=<property_value>
NOTE
The user login and password cannot be set in this
parameter because there are defined by the
“sqlhelper.login” and “sqlhelper.password” parameters.
query.limit.fetchSize The default value is set to: 10000 
Maximum number of results per query You can set any positive value greater than 10000
Cockpit database communication settings
datasource.jdbc.uri You must set a valid URI respecting the following format: 
The JDBC URI of the H2 embedded database For a file-based data storage, the URI format is:
instance used by SAP CC Cockpit to start jdbc:h2:file:<absolute_path_of_database_file>
For an in-memory data storage, the URI format is:
jdbc:h2:mem:<database_name>
CAUTION
If this parameter is not set, the “jdbc:h2:mem:cockpit”
in-memory data storage is used by default. Please note
that all data stored within an in-memory data storage is

lost in case of a SAP CC Cockpit restart.
datasource.login You must set a value that corresponds to an already 
The login used for authenticating on the defined user.
Cockpit database
datasource.password You must set a password that respects the SAP password 
The password used for authenticating on the policy.
Cockpit database
datasource.pool.size The default value is set to: 10 
The size of the pool dedicated to the You can set any positive value.
connections to the Cockpit database
datasource.timeout The default value is set to: 30000 
Maximum period (expressed in milliseconds) You can set any positive value. Setting this parameter to
allocated to the execution of a query 0 disables the timeout mechanism.
performed on the Cockpit database
NOTE
SAP SE recommends that you always set a value for this
timeout to avoid any contention problem.
datasource.cache.size The default value is set to: 131072 
The size of the cached structure (expressed in You can set any positive value.
Kilobytes) used by the H2 embedded RDBMS
to store the frequently used data
NOTE
For further information about this cached structure,
refer to the H2 database documentation.
Cache management
cache.type The default value is set to: simple 
Type of the cached structure containing You can set one of the following values: none, simple
queries
cache.simple.evict.scheduler The default value is set to: 60 
Duration (in seconds) between two reset You can set any value in the following range: ]0,300[
operations performed on the cache of queries
Data files management
http.multipart.max-file-size The default value is set to: 10240 
Maximum size (expressed in Kilobytes) of the You can set any positive value.
file to upload.
CAUTION
Modifying this value requires a modification of the
memory resources allocated to the Java web server
running Cockpit. SAP SE thus recommends that you only
change this value in case you encounter errors when
importing files.

Session settings
http.session.expiration.scheduler The default value is set to: 60 
Duration (in seconds) between two You can set any positive value.
verifications performed on HTTP sessions in
order to detect expired ones. When an HTTP
session is expired, this session is deleted.
browser.sessionTimeout The default value is set to: 120 
Maximum period (expressed in minutes) of You can set any positive value that corresponds to a
inactivity until which the session of a SAP CC period that must be longer than the lock timeout defined
power user expires. When this timeout is defined by the “browser.sessionLockTimeout”
reached, the unsaved modifications are lost. parameter.
browser.sessionLockTimeout The default value is set to: 10 
Maximum period (expressed in minutes) You can set any period that must be shorter than the
during which a session can be left inactive timeout defined by the “browser.sessionTimeout”
(meaning that there is no interaction between parameter. Setting this parameter to 0 disables the
the user and the web application). When this locking mechanism.
timeout is reached, the application locks the
user session automatically and the user must
log on again.
Logging and tracing settings
ls.app.severity The default value is set to: INFO 
Severity threshold for the generation of log You can set one of the following values: DEBUG, PATH,
messages related to the business processing INFO, WARNING, ERROR or FATAL
(application level)
ls.app.destination The default value is set to: LDC,LDF1 
CSV list of output destinations for the log Possible values are: LDC, LDF1, LDF2, LDF3, LDF4 and
messages related to the application level LDF5
ls.sys.severity The default value is set to: INFO 
Severity threshold for the generation of log You can set one of the following values: DEBUG, PATH,
messages related to the system processing INFO, WARNING, ERROR or FATAL
(system level)
ls.sys.destination The default value is set to: LDC,LDF1 
CSV list of output destinations for the log Possible values are: LDC, LDF1, LDF2, LDF3, LDF4 and
messages related to the system processing LDF5
(system level)
ls.trc.severity The default value is set to: ERROR 
Severity threshold for the generation of trace You can set one of the following values: DEBUG, PATH,
messages INFO, WARNING, ERROR or FATAL
ls.trc.domain The default value is set to: 
CSV list of trace domains that the generated SQL,NET,MSG,HB,AK,BLK,CACHE,LOCK,NOTIF,ADMIN,HC
messages relate to I,WS,WSBUS,CIF,RIF,SLDDS,JCO,PPI,PERF,DATA
ls.trc.destination The default value is set to: LDC,LDF2 
CSV list of output destinations for the Possible values are: LDC, LDF1, LDF2, LDF3, LDF4 and
generated messages LDF5

ld.console.enabled The default value is set to: false 

Enables/disables the use of the console Possible values are: true or false
ld.console.formatter The default value is set to: TRACE 
Output format of traces generated within the Possible values are: TRACE, LIST or XML
console
ld.fileX.enabled The default value is set to: true 
Enables/disables the use of fileset destination Possible values are: true or false
#X (X from 1 to 5)
ld.fileX.name The default value is set to: 
Path, name and extension of trace files for @CATALINA_HOME@/logs/@WEBAPP_NAME@_LDF2.t
fileset destination #X (X from 1 to 5) rc
You can set any string, using the following variables:
@CATALINA_HOME@, that is replaced at runtime by
the home folder of Catalina (Tomcat)
@WEP_APP_NAME@, that is replaced at runtime by
the context path of the deployed application (in
which possible URL separators are replaced by '_')
ld.fileX.size The default value is set to: 2M 
Maximum size before rotation of the trace You can set any value respecting the <value><unit>
files for fileset destination #X (X from 1 to 5) format, where:
<value> is a mandatory positive integer
<unit> is an optional string representing the unit, that
can be: K (kilo), M (mega) or G (giga)
ld.fileX.setsize The default value is set to: 4 
Number of trace files before rotation for You can set any positive value
fileset destination #X (X from 1 to 5)
ld.fileX.formatter The default value is set to: LIST 
Output format of traces when using fileset Possible values are: TRACE, LIST or XML
destination #X (X from 1 to 5)
 Mandatory
 Optional
To modify the configuration of the Cockpit web application, execute the following procedure:
1. Edit the configuration file
3. Save your modifications
Configuring the command-line applications
Keywords
UI, user interface, Setup Tool, Config Tool
Preliminary Notes


“Launching Setup Tool” section of the SAP CC Installation Guide documentation
“Launching Config Tool” section of the SAP CC Installation Guide documentation
“Launching CAT Tool” section of the SAP CC Installation Guide documentation
Description
Some command-line applications of SAP Convergent Charging rely on a configuration file that needs to be modified
to fit the configuration of your landscape. You can use the following procedures to modify these configuration files
and thus fit your specific needs:
Configuring Setup Tool
Configuring Config Tool
Configuring Setup Tool

The Setup Tool user interface directly connects to the back-end database, using connection parameters that are
defined in the boot.config file available in the config folder of dispatcher instances. For further information
about the available parameters, refer to the “Boot configuration file” dedicated section afterwards.
Configuring Config Tool

The Config Tool user interface directly connects to the back-end database, using connection parameters that are
defined in the boot.config file available in the “config” folder of dispatcher instances. For further information
about the available parameters, refer to the “Boot configuration file” dedicated section afterwards.
Configuring the Core Server system
Allowance management
Keywords
Allowance, SAP CRM, integration
Preliminary notes
For further information, refer to the “Allowance Management” feature description of the SAP CC Application Help
documentation.
Description
As described in the Application Help documentation, SAP CC gives the possibility to manage service add-ons for your
charge plans and refill plans by modeling:
The master data that define the allowances
The interaction between allowances and charging or refilling logic, which define the usage of allowances
In addition to the allowances management capabilities provided by the Core Tool user interface, you can use the
following procedure to configure allowances when SAP CC is integrated with SAP CRM.
Allowances management with SAP CRM

If your landscape is integrated with SAP CRM, allowances can be created on demand or automatically by SAP CRM
each time a provider contract id activated or modified. To activate such functionality, you must configure SAP CC as
described in the Integration Guide for the Offer-to-Cash End-to-End Process based on SAP Billing. For further
information, refer to the “Allowances Within the Offer-to-Cash Business Process” section of this dedicated
documentation available within the SAP CCBilling solution.
Boot configuration file
Keywords
boot.config, SAP Profile Folder, database connection
Preliminary notes
“SAP Central Repository” section of the SAP CC Installation Guide documentation
“Choosing System IDs” section of the SAP CC Installation Guide documentation
Description
For each instance of the Core Server system, a boot configuration file is defined in the SAP Profile Folder of the SAP
Central Repository. Copied within the config folder of each deployed instance of the Core Server system during the
instance startup phase, this boot.config file contains some parameters that are used to connect to the back-end
database.
Configuration options
Parameter Values Type

SQLHELPER_JDBC_URI JDBC URI of the Core database instance. 
For SAP HANA, the URI format is:
jdbc:sap://<primary_server>:<port>[;<secondary_server>:<port>][/?databa
seName=<tenant_name>]
For Sybase ASE, the URI format is:
jdbc:sybase:Tds:<server>:<port>/<database_name>?<prop1>=<value1>&<
prop2>=<value2>
For Oracle with “thin” driver, the URI format is:
- jdbc:oracle:thin:@//<server>:<port>/<ServiceName>
- jdbc:oracle:thin:@<server>:<port>:<SID>
For MS SQL Server (IPv4), the URI format is:
jdbc:sqlserver://<server>:<port>;DatabaseName=<database_name>;sendSt
ringParametersAsUnicode=true[;IntegratedSecurity=true]
For MS SQL Server (IPv4 or IPv6), the URI format is:
jdbc:sqlserver://;serverName=<server>;port=<port>;DatabaseName=<data

base_name>;sendStringParametersAsUnicode=true[;IntegratedSecurity=tr
ue]
For IBM DB2, the URI format is:
jdbc:db2://<server>:<port>/<database_name>:<prop1>=<value1>;<prop2>
=<value2>
SQLHELPER_LOGIN Login used for authenticating on the Core database, that must 
correspond to an already defined user.
SQLHELPER_PASSWORD Password of the previously specified login, used for authenticating 
on the Core database.
SYSTEM_ID SID of the Core Server system. 
You must set a value that corresponds to the system identifier used
to at installation time. For further information, refer to the
dedicated “Choosing System IDs” section available in the SAP CC
Installation Guide documentation.
DISCOVERY_MULTICAST_ADDRESS Multicast IP address (IPv4 or IPv6) used for UDP discovery in case of 
database connection failure.
DISCOVERY_PORT Port used for UDP discovery in case of database connection failure. 
BOOT_DISPATCHER_LIST CSV list of IP addresses (or hostnames) that correspond to 
dispatcher instances that can be contacted in case of discovery
failure.
 Mandatory
 Optional
Modifying the boot configuration file of an instance

To modify the boot configuration file, execute the following procedure:
1. Edit the “boot.config” file, that is located in the SAP Profile Folder of the Central Repository
2. Modify the relevant settings according to your needs
4. To apply your modifications, restart the concerned instance of the Core Server system. During the startup phase,
the modified boot.config file will be copied from the SAP Profile Folder to the local config folder of the
instance (overwriting the existing boot.config file).
NOTE
SAP SE recommends that you check the content of the boot.config file located in the local config folder of
the instance, to ensure that your modifications have correctly been reflected.
Business data management
Keywords
Public holidays, currency, currencies, tax, taxation, EZTax, VAT, rate, rule

Preliminary notes
“Public holidays” section of the Core Tool online help available in the SAP CC User Interfaces documentation
“Tax Calculation” feature description available in the SAP CC Application Help documentation
“Tax Calculation Process” section of the SAP CC Application Help documentation
“Launching Core Tool”, “Launching Setup Tool” and “Launching Admin+” sections of the SAP CC Installation
Guide documentation
Description
In addition to master data, your business also relies on business data that need to be configured. You can use the
following procedures to manage the relevant business data and thus fit your specific needs:
Managing public holidays
As described in the Application Help documentation, charging and refilling operations create transactions that need
to be enriched with taxation information computed by SAP CC in accordance with the defined taxation settings. You
can use the following procedures to configure the settings related to currencies and taxation and thus fit your
specific business needs:
Managing the currencies framework, including:
Modifying ISO currencies
Synchronizing SAP currencies
Reforming currencies
Managing the taxation framework, including:
Enabling the VAT framework
Enabling the EZTax framework
Modifying VAT rates
Modifying VAT rules
Customizing VAT Rules
Managing public holidays

Public holidays represent business data that :
Can be used within the “Public Holidays Splitter” and “Public Holidays Comparison” logic components
Are part of the catalog cache (also called “offer-level” cache) handled by raters and updaters
Are used at runtime by raters and updaters during charging and refilling operations, when processing the pricing
logic configured in price plans, charging plans or refill logic
Are defined within a dedicated file using an XML format defined in the following table:
Element Sub element Attribute Description

holiday code Attribute used to identify the public holiday, that must be
unique among the defined holidays
description lang Language used for the description
label Description of the holiday in the specified language
group code Name of the group of public holidays the currently defined
holiday belongs to
fixedDay month Name of the month

Possible values are: “January”, “February”, “March”, “April”,

“May”, “June”, “July”, ”August”, “September”, “October”,
“November” or “December”
day Number of the day in the specified month
Possible values are integer values from 1 to 28, 29, 30 or 31
according to the concerned month
relativeDay month Name of the month
Possible values are: “January”, “February”, “March”, “April”,
“May”, “June”, “July”, ”August”, “September”, “October”,
“November” or “December”
weekday Day of the week
Possible values are: “Monday”, “Tuesday”, “Wednesday”,
“Thursday”, “Friday”, “Saturday” or “Sunday”
position Position of the weekday in the specified month
Possible values are: “First”, “Second”, “Third”, “Fourth” or
“Fifth”
easterRelative offset Integer value use to define when the holiday occurs, relatively
to Easter Sunday (which is used as the reference date)
enumeratedDay List of specified dates. Refer below in this table for further
information about each enumerated date
enumeratedDay date value Concerned date, using the YYYY-MM-DD format, where:
YYYY corresponds to the year of the date
MM corresponds to the month of the date (from 1 to 12)
DD corresponds to the day of the date (from 1 to 31)
EXAMPLES
Example 1 (Fixed day): The following XML file defines the New Year’s Day holiday. This public holiday:
Is named “New Year’s Day” in english, and “Nouvel An” in french
Is available in 2 groups named “US” (United States) and “FR” (France)
Occurs on the first day of January
<?xml version="1.0" encoding="UTF-8"?>

<holiday code="NewYearsDay">
<description lang="en" label="New Year's Day" />
<description lang="fr" label="Nouvel An" />
<group code="US" />
<group code="FR" />
<fixedDay month="January" day="1" />
</holiday>
Example 2 (Relative day): The following XML file defines the Thanksgiving holiday. This public holiday:
Is named “Thanksgiving” in both english and french
Is only available in the “US” (United States) group
Occurs on the fourth Thursday of November in the United States


<holiday code="Thanksgiving">
<description lang="en" label="Thanksgiving" />
<description lang="fr" label="Thanksgiving" />
<group code="US" />
<relativeDay month="November" weekday="Thursday" position=”fourth” />
</holiday>
Example 3 (Easter-relative day): The following XML file defines the Easter Monday holiday. This public holiday:
Is named “Easter Monday” in English, and “Lundi de Pâques” in french
Is available in 2 groups named “US” (United States) and “FR” (France)
Occurs one day after Easter Sunday

<holiday code="EasterMonday">
<description lang="en" label="Easter Monday" />
<description lang="fr" label="Lundi de Pâques" />
<group code="US" />
<group code="FR" />
<easterRelativeDay offset=”1” />
</holiday>
Example 4 (Easter-relative day): The following XML file defines the Good Friday holiday. This public holiday:
Is named “Good Friday” in English, “Vendredi Saint” in French, and “Karfreitag” in german
Is available in 3 groups named “BE” (Belgium), “FR” (France) and “DE” (Germany)
Occurs 2 days before Easter Sunday

<holiday code="GoodFriday">
<description lang="en" label="GoodFriday" />
<description lang="fr" label="Vendredi Saint" />
<description lang="de" label="Karfreitag" />
<group code="BE" />
<group code="FR" />
<group code="DE" />
<easterRelativeDay offset=”-2” />
</holiday>
Example 5 (Enumerated day): The following XML file defines the chinese New Year's Day holiday. This public
holiday:
Is named “Chinese New Year” in English and “Nouvel An Chinois” in French
Occurs at a different date each year

<holiday code="GoodFriday">
<description lang="en" label="Chinese New Year" />
<description lang="fr" label="Nouvel An Chinois" />
<enumeratedDay>
<date value="2015-02-19" />
<date value="2016-02-08" />

<date value="2017-01-28" />

<date value="2018-02-16" />
<date value="2019-02-05" />
<date value="2020-01-25" />
</enumeratedDay>
</holiday>
By default, a list of predefined public holidays is embedded by SAP Convergent Charging. The XML file containing this
default list of holidays is named “public_holidays.xml”, and is located in the config folder of the Core Tool user
interface. In case you need to modify this default list, execute the following procedure:
1. Launch the Core Tool user interface and and log in with an individual user granted the “Administrator” role
2. Export the list of defined holidays using the “Export” command of the “Tools>Public holidays” menu
3. Modify the content of the created file using the previously provided description
4. Import the list of modified holidays using the “Import” command of the “Tools>Public holidays” menu
Managing the currencies framework

SAP CC manages the following types of currencies:
ISO currencies, whose up-to-date list is provided at installation time
SAP currencies, that are used in an integrated scenario with the SAP ERP/FI-CA component
These currencies are set up in master data that relate to both service provider and customers, within elements such
as charges, charge plans, refill plans, refill logic, offers and subscriber accounts. You can use the following procedures
to manage currencies within your landscape.
NOTES
You can set up reusable charges and refill logic using the multicurrency option. In this case, the final currency is
then set up in the charge plans or offers. A unique charge can then be modeled and used in different charge
plans with different currencies.
In charge plans, you can set up the currency information for each charge customized in the plan. A specific
currency parameter is automatically added by the Core Tool user interface, that gives you the possibility to:
Redefine this parameter with a new default value
Link this parameter with an internal parameter defined in the charge plan
Link this parameter with a parameter defined in the charge plan, that will be set up for each provider
contract (in a CRM application or external provisioning system)
As far as refill plans are concerned, you cannot set up any currency in a refill plan. The final currency that will
be used corresponds to the currency of the prepaid account to be refilled
Modifying ISO currencies

A default list of ISO currencies is provided at installation time. In case you need to modify this default list, execute
the following procedure:
2. Export the list of defined currencies using the “Export” command of the “Tools>Currencies” menu
3. Modify the content of the created file
4. Import the list of modified currencies using the “Import” command of the “Tools>Currencies” menu

NOTE
For further information about currencies import and export commands, refer to the “Currencies” subsection of the
SAP CC Core Tool User Interfaces documentation, available in the “Tools” section.
Synchronizing SAP currencies

SAP currencies correspond to currencies defined within the SAP ERP/FI-CA component of the SAP Business Suite,
whose list must be manually synchronized in SAP CC.
To synchronize the list of SAP currencies, execute the following procedure:
2. Synchronize the list of currencies using the “Synchronizing currencies” command of the “Tools>Currencies”
menu. Concerned instances will be automatically updated in a short time.
NOTE
For further information about the currencies synchronization command, refer to the “Currencies” subsection of the
SAP CC Core Tool User Interfaces documentation, available in the “Tools” section.
Reforming currencies
Reforming currencies consists in changing some characteristics of an existing, or replacing an existing currency by
another one. The computed prices must then be converted by applying a given exchange rate.
SAP Convergent Charging gives the possibility to manage multiple currencies simultaneously, when the concerned
currencies are used in different price plans and charged on different accounts. To switch from one currency to
another without modifying the pricing implementation, no native mechanism is available. As a consequence,
currencies reforming operations must be executed:
During the initial implementation phase of SAP CC, when master data are configured. SAP SE recommends that
you design your pricing logic independently from currencies, by:
Designing multicurrencies charges, offers and charge plans
Using reusable elements such as translation tables or pricing macros, that give the possibility to design 2
charges that use the same pricing logic, but that compute amounts with 2 different currencies
During the maintenance phase of SAP CC, in accordance with other possible systems in case of an integrated
scenario, in particular with third-party invoicing systems regarding:
Dates or slots for the currency switching time (for example to align invoices creation)
External accounts, whose information can be modified because of the currency switch
The impact of the currency switch operation, that may modify the switching policy (batch migration Vs on-
the-fly migration)
Managing the taxation framework

SAP CC manages the following tax systems:
Value Added Tax (VAT), with or without VAT rules
Flat Tax, that consists of a constant marginal rate
BillSoft EZTax, that is used to calculate taxes related to the U.S. Telco taxes

Tax information is used in master data that relate to both service provider and customers, within elements such as
charges and subscriber accounts. You can use the following procedures to manage taxes within your landscape.
CAUTION
It is only possible to add a new tax system to the tax system configured at installation time
Never remove a tax system if a master data of the service provider or of the customers is configured to use this
tax system
Enabling the VAT framework

In case you did not select the VAT tax system at installation time, you can use the following procedure to enable it:
1. Modify if necessary the VAT rates or VAT rules using the following dedicated procedures:
Modifying VAT rates
Modifying VAT rules
2. Launch the Setup Tool user interface and identify as the administrator of the concerned Core Server system
3. Execute the “vatax importCountryTaxPolicies” command, specifying the absolute path of the file containing the
country tax policies to import
4. Launch the Admin+ user interface and identify as the administrator of the Core Server system
5. For each concerned instance, modify the value of the TAX_FRAMEWORK system parameters to “VAT” or
“VAT;EZTAX”
6. Restart the concerned instances of the Core Server system
Enabling the EZTax framework

In case you did not select the EZtax tax system at installation time, you can use the following procedure to enable it:
1. Ensure that the Billsoft EZtax third-party software is installed within your landscape
3. Execute the “eztax importTSTypes” command, specifying the absolute path of the file containing the EZtax
transaction/service types
4. Edit the “default.fpl” file, that is located in the SAP Profile Folder of the Central Repository, and:
Set the “tax.ezTax” parameter to “true”
Add the following parameter: “tax.eztaxRootFolder = <EZTAX_ROOT_FOLDER>”, where
<EZTAX_ROOT_FOLDER> corresponds to the root folder where EZtax is installed
6. For each concerned instance, modify the value of the TAX_FRAMEWORK system parameters to “EZTAX” or
“VAT;EZTAX”
8. Install taxer instances in your landscape using the “Adding Core Server instances in a multi-hosts landscape”
procedure available in the SAP CC Installation Guide documentation
Modifying VAT rates

A list of VAT rates is deployed by SAPinst at installation time when the VAT tax system is selected. You can use the
following procedure to modify this default list:
2. Execute the “vatax exportVATRate” command to export the VAT rates from the Core database, specifying the
absolute path of the file that will contain the exported VT rates
5. Execute the “vatax importVATRate” command to import the modified VAT rates into the Core database,
specifying the absolute path of the file containing the modified rates
NOTE
A default list of VAT rates is deployed at installation time in the “vat_rate.txt” file that is available in the
“exe/uc/<OS>/CC_CORE_SERVER/tax/” subfolder of the SAP Central Repository, where <OS> corresponds to the
operating system of the host. For further information about the SAP Central Repository, refer to the “Document
Definitions” section available in the SAP CC Installation Guide documentation.
To import this default list, execute the steps 5 and 6 of this procedure using this “vat_rate.txt” file.
Modifying VAT rules

A list of VAT rules is deployed by SAPinst at installation time when the VAT tax system is selected. You can use the
following procedure to modify this default list:
2. Execute the “vatax exportVATRules” command to export the VAT rules from the Core database, specifying the
absolute path of the file that will contain the exported rules
CAUTION
You can modify EU VAT rules, but it is only possible to add customized VAT rules. For further information
about VAT rule customization, refer to the “Customizing VAT Rules” procedure afterwards

5. Execute the “vatax importVATRules” command to import the modified VAT rules into the Core database,
specifying the absolute path of the file containing the modified rules
6. Refresh instances’ cached structures in a HA environment, restart the concerned instances of the Core Server
system otherwise
NOTE
A default list of VAT rules is deployed at installation time in the “vat_rules.txt” file that is available in the
“exe/uc/<OS>/CC_CORE_SERVER/tax/” subfolder of the SAP Central Repository, where <OS> corresponds to the
operating system of the host. For further information about the SAP Central Repository, refer to the “Document
Definitions” section available in the SAP CC Installation Guide documentation.

To import this default list, execute the steps 5 and 6 of this procedure using this “vat_rules.txt” file.

When the VAT tax system is enabled within your landscape, a list of VAT rules for EU VAT 2010 and EU VAT 2015 is
deployed at installation time. In case you need to add specific VAT rules, you can use the following procedures to:
Model your own VAT rules
Create the modeled VAT rule
To model a specific VAT rule, consider the following guidelines:

Determine the supplier zone, that corresponds to the reference for the service provider whose consumptions
taxes must be calculated by SAP CC
Determine the business categories (B2B or B2C) that are relevant for your VAT rule
For each business category, determine the origin of the place of taxation that can be:
The supplier's place of establishment
The customer's place of establishment (B2B)
The customer's place of residence (B2C)
For certain business requirements, the place of taxation depends on particular conditions that are not basically
the places of establishment or residence. In this case, the adequate place must be dynamically determined at
runtime by SAP CC according to the configuration of the pricing logic (see charges customized in charge plans or
offers). You must then:
Configure the pricing logic in order to configure this place determination
Set up a price plan that defines a parameter or that computes a property containing at runtime the
appropriate values, or you must ensure that the chargeable items received from the mediation system will
contain this taxation place information
Determine the default sources for the B2B and B2C places of taxation. The VAT 2010 directive defines the
following places according to the business categories:
B2B services: Customer's place of establishment (the holder of the charged account in the subscriber
account)
B2C services: Service provider's place of establishment
EXAMPLES
Example 1: You want to create a customized VAT rule to model the article 59b of the EU VAT 2010 directive that
says: “Radio and television broadcasting services and telecommunications services, supplied by suppliers
established in a third country to non-taxable customers in the EU, are taxable at the place where the private
customer effectively consumes the service. Other general rules apply otherwise”. To model this rule, consider the
following configuration:
Reference Supplier Zone: Third Country
Source for the B2B place of taxation: None
Source for the B2C place of taxation: Place dynamically set by SAP Convergent Charging at runtime. It must
correspond to the effective place (country) of consumption of the customer service. The price plan must
compute an appropriate property or the mediation system must provide this information in the chargeable
items related to the service consumption
Default source for the B2B place of taxation: Customer's place of establishment (the holder of the charged
account in the subscriber account)
Default source for the for the B2C place of taxation: Service provider's place of establishment

Example 2: You want to create a customized VAT rule that gives you the possibility to finely configure the
determination of the places of taxation within the pricing logic (in the price plans). To model this rule, consider the
Reference Supplier Zone: Any Country
Source for the B2B place of taxation: Place dynamically set by SAP Convergent Charging at runtime (according
to the configuration of the charges customized in charge plans or offers)
Source for the B2C place of taxation: Place dynamically set by SAP Convergent Charging at runtime (according
to the configuration of the charges customized in charge plans or offers)
Default source for the B2B place of taxation: Customer's place of establishment (the holder of the charged
account in the subscriber account)
Default source for the for the B2C place of taxation: Service provider's place of establishment
Once your VAT rule has been modeled, use the following table to create the rule, that consists of a dedicated row:
That must be inserted in the file containing VAT rules
That respects the following syntax:
<RL_NAME>;<RL_DESCR>;<REF_SUPPLIER_ZONE>;<B2B_PLACE_OF_TAXATION_ORIG>; <B2C_PLACE_OF_TAXATION_ORIG>;
<DEFAULT_B2B_PLACE_OF_TAXATION>;<DEFAULT_B2C_PLACE_OF_TAXATION>
Property Type Description

RL_NAME  This property corresponds to the name of the VAT rule, used
as a unique identifier of the VAT rule.
This name is visible in the Core Tool when the power user
configures the tax settings for each charge customized in a
charge plan (or in an offer).
RL_DESCR  This property corresponds to the description of the VAT rule.
This description is visible in the Core Tool when the power user
configures the tax settings for each charge customized in a
charge plan (or in an offer).
REF_SUPPLIER_ZONE  This property corresponds to the zone of the service provider.
Possible values are:
0: EU (European Union)
1: TC (Third Country)
2: AC (Any Country)
B2B_PLACE_OF_TAXATION_ORIG  This property corresponds to the source for the place of
B2C_PLACE_OF_TAXATION_ORIG taxation. Possible values are:
0: Supplier's place of establishment (the service provider
supplying the customer service to charge)
1: Customer's place of establishment (the holder of the
prepaid or external account that is charged by SAP CC)
2: Place dynamically determined by SAP CC according to
the configuration of the pricing catalog (see charges
customized in charge plans or offers)
DEFAULT_B2B_PLACE_OF_TAXATION  This property corresponds to the default source for the place
DEFAULT_ B2C_PLACE_OF_TAXATION of taxation. Possible values correspond to the above listed
values.
 Mandatory

 Optional
EXAMPLES
Considering the previously modeled VAT rules, the following rows must be created:
Example 1: ART59b;Rule description;1;;2;1;0
Example 2: CustomRule; Rule description;2;2;2;1;0
Catalog transport
Keywords
Catalog transport, transport destination, change list, scheduler
Preliminary notes
“Catalog Transport” section of the SAP CC Application Help documentation
“Launching Setup Tool”, “Launching Admin+” and “Securing communications with the Core Server” sections of
the SAP CC Installation Guide documentation
“transportdestination importList”, “transportdestination exportList” and “certentry import” commands of the
SAP CC Setup Tool User Interface documentation
Description
As described in the Application Help documentation, SAP Convergent Charging gives the possibility to transport data
of a given catalog from an SAP CC system to one or several other SAP CC system(s), using the Catalog Transport
feature. This feature is based on change lists that can be transported to transport destinations that are defined
within the Core Server system. You can use the following procedures to configure the Catalog Transport feature and
thus fit your specific needs:
Managing transport destinations
Scheduling transport requests operations
CAUTION
If the Catalog Transport feature is used to transport change lists to secured SAP CC systems, please note that these
remote SAP CC systems must respect the following constraints:
The external communications (relying on the XML over HTTP or SOAP over HTTP communication channels) of
the dispatcher and updater instances must be configured with the “off” or “oneway” secure mode. The “dual”
authentication mode is not supported
The certificates associated to the remote SAP CC systems must be valid for all the external communications
Managing transport destinations

By default, no transport destination is defined at installation time. In case you want to transport change lists
between SAP CC systems, it is thus necessary to configure transport destinations, each transport destination
representing a SAP CC system to which objects can be transported. To configure a list of transport destinations on a
given SAP CC system, execute the following procedure:
NOTE

To execute the dedicated commands described below, run the Setup Tool user interface.
1. Export the list of transport destinations using the “transportdestination exportList” dedicated command
2. (Optional) In case the targeted transport destinations correspond to a secured landscape, you need to import
the certificates of the secured SAP CC system, using the “certentry import” dedicated command. For further
information, refer to the “Securing communications with the Core Server” section of the SAP CC Installation
Guide documentation
3. Edit the newly created file and modify its content to add, modify or remove transport destinations. For further
information about the structure of transport destination files, refer to the dedicated XML schema accessible
from the documentation of the “transportdestination importList” command.
(Optional) In case of secured transport destination, specify the alias of the adequate certificate within the
“trustedCertificateEntryAlias” parameter. When this alias is not specified, the certificates defined for the “ws”
communication channel of the updaters will be used by default
4. Import the modified list of transport destinations using the “transportdestination importList” dedicated
command.
NOTE
No restart of the updaters is required to take the new destinations into account.
Scheduling transport requests operations

Change lists can be transported to the defined transport destinations:
Manually via the Core Tool user interface
Automatically by a dedicated scheduler
To modify the behavior of the scheduler in charge of executing transport requests, execute the following procedure:
2. Modify the value of the following system parameters for each concerned updater instance:
TRANSPORT_SCHEDULER_ENABLED, which gives the possibility to enable or disable the scheduler
TRANSPORT_SCHEDULER_RECURRENCE, which defines the recurrence period of the scheduler
For further information about these system parameters, refer to their dedicated documentation available in the
SAP CC System Parameters Reference documentation.
Chargeable items charging process
Keywords
Charging, session database, session-based
Preliminary notes
“Chargeable Items Charging” feature description of the SAP CC Application Help documentation
“Launching Admin+” section of the SAP CC Installation Guide documentation
“Process: Charging and Rating” and “Process: Session-Based Charging” groups in the SAP CC System Parameters
Reference documentation

Description
As described in the Application Help documentation, SAP CC gives the possibility to charge incoming events using
different execution modes that suit multiple businesses. These charging operations can concern both external or
internal events, and lead to the generation of output data handled by external systems such as SAP Convergent
Invoicing.
You can use the following procedures to manage the charging capabilities of SAP CC:
Enabling the Session Database, that is only relevant for landscapes implementing the Dual Database feature
Limiting the number of charging sessions, that can be used to limit the creation of an unexpected high number of
charging sessions
Enabling the Session Database

In case your business implements the Dual Database feature, it is necessary to enable the Session database once it
has been installed within your landscape. To enable the use of the Session database, execute the following
procedure:
2. Modify the value of the following system parameters for each concerned rater instance:
RATING_SESSION_SQLHELPER_CONNECTION_COUNT, which gives the possibility to specify a number of
connections to open on an instance of the Session database
RATING_SESSION_SQLHELPER_DB_INSTANCE_COUNT, specifying a positive number of Session database
instances that will be used by the raters
RATING_SESSION_SQLHELPER_JDBC_URI_DBIx (where x corresponds to the number of RAC nodes that are
available for the Session database), which defines the JDBC URIs for connecting to the Session database
RATING_SESSION_SQLHELPER_LOGIN and RATING_SESSION_SQLHELPER_PASSWORD, which corresponds
to the credentials used to authenticate on the Session database
RATING_SESSION_UPDATE_POOL_SIZE, which defines the size of the pool containing the modifications
queries performed on the Session database
RATING_SESSION_UPDATE_MAX_BATCH_SIZE, which defines the maximum number of queries that can be
handled by a given thread of the pool dedicated to modification queries performed on the Session Database
RATING_SESSION_SELECT_POOL_SIZE, which defines the size of the pool containing all the search queries
performed on the Session Database
3. For each RATING_TABLE_X table that exists in the Core database, execute the following command to remove the
old data that are related to the session-based charging operations, considering that:
<COREDB_USER> corresponds to the name of the Core database administrator
<COREDB_PASSWORD> corresponds to the password of the Core database administrator
sqlplus <COREDB_USER>/<COREDB_PASSWORD>
truncate table RATING_SESSION_X
4. Restart the rater instances of the Core Server system
Limiting the number of charging sessions

In case your business relies on charging operations performed using the session-based execution mode, you may
want to prevent the creation of an unexpected high number of charging sessions. To limit the number of charging
sessions that can be started per subscriber account, execute the following procedure:
2. Modify the value of the following system parameter for each concerned rater instance:
RATING_SESSION_PER_SUBSCRIBER_ACCOUNT_LIMIT, which gives the possibility to specify the maximum
number of charging sessions that can be started in parallel for each subscriber account
For further information about this system parameter, refer to its dedicated documentation available in the SAP
CC System Parameters Reference documentation.
Chargeable items recharging process
Keywords
Recharging, rerating, counter snapshot, rerate file processor, retention period
Preliminary notes
“Chargeable Items Recharging” feature description of the SAP CC Application Help documentation
“Launching Setup Tool” and “Launching Admin+” sections of the SAP CC Installation Guide documentation
“Process: Rerating” group in the SAP CC System Parameters Reference documentation
“deactivateRecharging” command of the SAP CC Setup Tool User Interface documentation
Description
As described in the Application Help documentation, SAP CC gives the possibility to correct errors by executing
recharging operations that cancel previous charging operations and perform new ones on identified sets of
chargeable items. These recharging operations:
Are executed by default in conjunction with the BART Server system
Can be handled by SAP Convergent Invoicing in case your landscape is integrated with this SAP system
You can use the following procedures to manage the recharging capabilities of SAP CC:
Configuring the retention period of counter snapshots
Deactivating the recharging feature based on counter snapshots
Using SAP CI instead of BART Server for recharging operations
Configuring the retention period for counter snapshots

By default, SAP CC gives the possibility to store counter snapshots during 40 days. For business, legal or technical
reason, you can change this retention period from 1 to 70 days.
To modify the retention period for counter snapshots within your SAP CC landscape, execute the following
procedure:
2. For each concerned updater, modify the value of the COUNTER_SNAPSHOT_COUNT system parameter
CAUTIONS
SAP SE recommends that you do not change this retention period on a production landscape

The retention period for counter snapshots must be lower than or equal to the retention period used for
expired allowances. For further information, refer to the “Configuring the allowances purge mechanism”
section
Deactivating the recharging feature based on counter snapshots

When the counter snapshot mechanism is enabled, counters are backed up regularly within counter snapshots that
are used during recharging operations. In case you do not plan to perform recharging operations, you can deactivate
the recharging feature (based on counter snapshots) and thus increase the reactivity of the Core Server system by
optimizing your data storage.
CAUTION
This procedure definitively deactivates the recharging capabilities (based on counter snapshots) of SAP Convergent
Charging, and cannot be activated again. When performed, it will not be possible to execute any chargeable items
recharging operation.
RECOMMENDATION
As this procedure requires a restart of the rater and updater instances, you can take advantage from a patch
implementation to execute this procedure. If so, execute the following preliminary steps:
Implement the concerned patch in order to update your system
Restart 1 dispatcher only (as a dispatcher is required to execute the Setup Tool user interface)
Then, execute this procedure.
To deactivate the chargeable items recharging feature within your SAP CC landscape, execute the following
procedure:
1. Launch the Setup Tool user interface and identify as the administrator of the Core Server system
2. Execute the “migration deactivateRecharging” command
4. Restart the updater instances of the Core Server system
5. Once this command has ended, you can verify the following elements to ensure that the feature has been
successfully deactivated:
The “com.sap.SCC.core_server.000632” log message (“The recharging feature is deactivated”) must be
displayed in the starting log of both raters and updaters
The value of the “RECHARGING_STATUS” system indicator must be set to “off”
NOTE
The COUNTER_SNAPSHOT table of the Core database contains the counter snapshots used for recharging purpose.
As these counter snapshots will not be used anymore, you can empty this table to optimize your data storage. To
ensure the integrity of the database structure for future updates, SAP SE recommends that you do not delete this
table.

Communications channels
Keywords
Communication channels, securing, UDP
Preliminary notes
“Communication Channel Security” section of the SAP CC Security Guide documentation
“Securing a landscape” and “Launching Admin+” sections of the SAP CC Installation Guide documentation
Description
SAP Convergent Charging communications rely on different communication channels whose use depend on the
concerned elements. You can use the following procedures to configure the settings related to communication
channels and thus fit your specific needs or performance requirements:
Modifying the database communication settings
Enabling the UDP discovery mechanism
Securing the communication channels

To communicate with the databases available within your SAP CC landscape, it is necessary to define dedicated
connections whose number depends on the enabled services.
To modify the number of connections used by each instance, modify the value of the following system parameters
for each concerned instance:
SQLHELPER_CONNECTION_COUNT, which defines the connections to open on the Core database
RATING_SESSION_SQLHELPER_CONNECTION_COUNT, which defines the connections to open on the Session
database, when this database is used
For further information about these system parameters, refer to their dedicated documentation available in the SAP
Enabling the UDP discovery mechanism

SAP Convergent Charging gives to client applications and other deployed instances the possibility to detect the list of
available dispatchers. Based on UDP, this proprietary discovery mechanism relies on multicast requests that are sent
on the Messages over UDP communication channel.
If your network configuration support UDP communications, you can execute the following procedure to enable the
UDP discovery mechanism within your SAP CC landscape:
1. Launch the Admin+ user interface and identify as the administrator of the concerned Core Server system
EXTERNAL_DISCOVERY_ENABLED, which gives the possibility to enable or disable the discovery mechanism
EXTERNAL_DISCOVERY_MULTICAST_ADDRESS, which represents the multicast IP address used by
dispatchers to inform about their availability and their connection parameters
EXTERNAL_DISCOVERY_PORT, which represents the port of the defined multicast IP address
3. Restart the master dispatcher
4. Restart the other deployed instances


For security purposes, all communication channels (except the Messages over UDP one) used to communicate within
your SAP CC landscape can be secured. For further information about the available securing procedures, refer to the
dedicated “Securing a landscape” section of the SAP CC Installation Guide documentation.
Data cache management
Keywords
Cache size, cache warmup, smart mode, normal mode, shared allowances, refresh, scheduler
Preliminary notes
“Caching Policies” section of the SAP CC Application Help documentation
“refresh_shared_allowance_cache” command of the SAP CC Admin+ User Interface documentation
“Tuning: Data Caches” and “Process: Allowance Management” groups in the SAP CC System Parameters
Description
As described in the Application Help documentation, most of the instances of the Core Server system manage data
within cached structures that are stored in memory. You can use the following procedures to manage some of these
cached structures of your SAP CC landscape and thus fit your specific needs or performance requirements:
Determining the size of cached structures
Modifying the size of cached structures
Modifying the accesses cache
Modifying the subscription cache
Modifying the session cache
Modifying the shared allowances cache
Modifying the SQL statements cache
Enabling the cache warmup mechanism
Refreshing the shared allowances cache
Determining the size of cached structures

To determine the size of a given cached structure, the best way consists in putting a set of objects in this cache and
determining the average size of these objects. The recommended method consists in simulating the presence of
1,000 end customers of a service provider, and creating all the business objects that are relevant and necessary for
your implementation:
Customer master data: 1,000 subscriber accounts, 1,000 provider contracts or subscriptions (and relevant
accesses), relevant data tables (subscriber mapping tables and subscriber range tables)
Master data related to the service provider: Relevant pricing objects (charge plans, offers and suboffers),
charges with price plans and charging plans including pricing macros or data tables like tier or translation tables,
mapping or range tables
To determine the size of a given cached structure, execute the following procedure:
1. Start an instance of each type (dispatcher, updater, guider, rater, and taxer when relevant) with the default
values for sizing the cached structure
3. Retrieve the S1 value of the following system parameters for each concerned instance:
SUBSCRIPTION_CACHE_SIZE, which defines the memory allocated to store objects in the subscription cache
GUIDING_CACHE_SIZE, which defines the memory allocated to store objects in the access cache
SESSION_MEMORY_SIZE, which defines the memory allocated to store objects in the rating sessions cache
4. Retrieve the FM1 value of the following system parameters for each concerned instance:
SUBSCRIPTION_CACHE_FREE_MEMORY, which defines the remaining free memory in the subscription cache
GUIDING_CACHE_FREE_MEMORY, which defines the remaining free memory in the access cache
SESSION_FREE_MEMORY, which defines the remaining free memory in the rating sessions cache
5. Create N0 typical objects (1000 for example) that will be stored in each cached structure
6. Restart the instances started in Step 1
7. Re-execute Step 3 and Step 4, considering the retrieved values as S2 and FM2
8. For each cached structure of each concerned instance, compute the consumed memory related to the created
objects, taking into consideration that:
If the size of the cached structure has changed, apply the following formula: (S2-FM2) - (S1-FM1)
If the size of the cached structure has not changed, calculate the difference between the free memory
available at the first launch and the free memory available at the second launch: FM1 - FM2
9. Divide the previous result by the number of objects you have created in the cached structure, and then multiply
the result by the NF number of objects you plan to have in the future.
To sum up, the size of the cached structure can be estimated using the following formula, depending whether
the size of the cached structure has changed between the 2 launches, or not:
((FM1-FM2) / N0) x NF
(((S2-FM2)-(S1-FM1)) / N0) x NF
10. Add the result to the first computed size: You now have the size of your cached structure, that you can divide by
the number of available instances supposed to managed this volume of objects
11. Increase S2 and the total size of the JVM with this number in order to prevent the memory allocated to the
cached structure from being taken by another cached structure or by the JVM itself
Modifying the size of cached structures

To handle your business requirements, it is necessary to configure the different cached structures handled by the
instances of the Core Server system. In case of a production landscape, SAP SE recommends you to use values that
have previously been determined on a non-production landscape during test campaigns.
CAUTION
The size of the cached structures handled by a given instance must not exceed the value of the
MaxDirectMemorySize JVM option. If this constraint is not respected, OutOfMemory errors will occur.
To configure the different cached structures, execute the following procedure:


2. For each concerned instance, modify the value of the relevant parameters, as described in the dedicated
sections afterwards
3. Restart the concerned instances
Modifying the accesses cache

To modify the cached structure containing the guiding information used for request routing purpose, modify the
value of the following system parameters for each concerned guider instance:
GUIDING_CACHE_SIZE, which defines the memory allocated to store the cached objects
GUIDING_CACHE_INSTANCES, which defines the maximum number of caches used by each instance
Modifying the subscription cache

To modify the cached structure containing the provisioning data (provider contracts, subscriptions, counters and
subscriber accounts), modify the value of the following system parameters for each concerned rater instance:
SUBSCRIPTION_CACHE_SIZE, which defines the memory allocated to store the cached objects
SUBSCRIPTION_OBJECT_AVERAGE_SIZE, which defines the average size of 1 cached object
SUBSCRIPTION_CACHE_INSTANCES, which defines the maximum number of subcaches used by each instance
Modifying the session cache

To modify the cached structure containing the data related to charging sessions, modify the value of the following
system parameters for each concerned rater instance:
SESSION_MEMORY_SIZE, which defines the memory allocated to store the cached objects
SESSION_MEMORY_INSTANCES, which defines the maximum number of subcaches used by each instance
Modifying the shared allowances cache

To modify the cached structure containing the data related to shared allowances, modify the value of the following
system parameters for each concerned rater instance:
SHARED_ALLOWANCE_CACHE_SIZE, which defines the memory allocated to store the cached objects
SHARED_ALLOWANCE_OBJECT_AVERAGE_SIZE, which defines the average size of 1 cached object
SHARED_ALLOWANCE_CACHE_INSTANCES, which defines the maximum number of subcaches used by each
instance
NOTE
For performance reasons, this cached structure can be refreshed:

Regularly by a dedicated scheduler

On-demand by using a dedicated command of the Admin+ user interface
For further information about the shared allowances cache refreshing, refer to the “Refreshing the shared
allowances cache” dedicated section afterwards.
Modifying the SQL statements cache

To modify the cached structure containing the SQL request statements, modify the value of the following system
parameters for each concerned instance:
SQLHELPER_STATEMENT_CACHE_SIZE, which defines the memory allocated to store the cached objects and is
used by all instances when communicating with the Core database
RATING_SESSION_SQLHELPER_STATEMENT_CACHE_SIZE, which defines the memory allocated to store the
cached objects and is used by the rater instances when communicating with the Session database
CAUTION
SAP SE recommends you to avoid changing these parameters on a production landscape, except under the direct
supervision of a support specialist from your SAP Support Team
Enabling the cache warmup mechanism

To increase the reactivity of the Core Server system during online and offline charging operations, the content of the
cached structures can be pre-loaded from the Core and Session databases in order to avoid latency. These pre-
loading operations rely on a cache warmup mechanism that can be enabled or disabled to fit specific needs.
NOTE
The cache warmup mechanism is disabled by default.
CAUTION
This procedure requires to partially restart the Core Server system. As a consequence, SAP SE recommends you to
avoid enabling this function in a production system landscape without a preliminary validation on a quality control
landscape.
To modify the configuration of the cache warmup mechanism, execute the following procedure:
2. Modify the value of the following system parameters for the concerned instances, taking into account the
existing constraints between these parameters:
CACHE_WARMUP_THREAD_COUNT, by defining a number of thread allocated to warmup operations, that
usually equals to the number of available CPUs minus one
SQLHELPER_CONNECTION_COUNT, by adding new connections to the Core database

RATING_SESSION_SQLHELPER_CONNECTION_COUNT, by adding new connections to the Session database

(when the Session database is used within your landscape)
EXAMPLES
To permanently disable the cache warmup mechanism for all rater instances of the Core Server system,
execute the following command:
set CACHE_WARMUP_THREAD_COUNT 0 all rater
set SQLHELPER_CONNECTION_COUNT X all rater, where X corresponds to the previous value of this
parameter, decreased by the number of threads previously allocated to warmup operations
To temporary allocate 4 threads to warmup operations performed by a given instance of the Core Server
system, execute the following commands:
set SQLHELPER_CONNECTION_COUNT X memory <INSTANCE_ID>, where X corresponds to the previous
value of this parameter, increased by 4
set CACHE_WARMUP_THREAD_COUNT 4 memory <INSTANCE_ID>
When the cache warmup mechanism is activated, it is possible to configure the Core Server system in order to
activate a smart execution mode for the partitions distribution operations performed by the master dispatcher. This
execution mode gives the possibility to control the warmup operations performed by the targeted instances during
these partitions distribution operations, and thus to control the overall impact of warmup operations on the online
stateful charging operations.
To activate and configure this smart distribution mode, refer to the “Distributing partitions to guiders and raters
using a smart mode” section of this documentation.

To increase the reactivity of the Core Server system, the content of the cached structures can be transferred directly
from one instance to another using the network. These network transfer operations decrease the overall solicitation
of the Core and Session databases, and decrease the duration of the warm-up operations performed by raters and
guiders during partition redistribution.
NOTE
The network data transfer mechanism is enabled by default.
To modify the configuration of the network data transfer mechanism, execute the following procedure:
2. Modify the value of the following system parameters for each concerned dispatcher instance:
RATER_PARTITION_SWITCH_CACHE_TRANSFER_ENABLED, which gives the possibility to enable or disable
the use of network data transfer operations when switching partitions handled by raters
GUIDER_PARTITION_SWITCH_CACHE_TRANSFER_ENABLED, which gives the possibility to enable or disable
the use of network data transfer operations when switching partitions handled by guiders
DATA_TRANSFER_REQUEST_HANDLER_QUEUE_SIZE, which gives the possibility to specify the maximum
number of Class1 and Class2 requests that can be queued in the dispatcher
DATA_TRANSFER_REQUEST_HANDLER_THREAD_COUNT, which gives the possibility to specify the number
of threads dedicated to the processing of Class1 and Class2 requests in the dispatcher

3. Modify the value of the following system parameters for each concerned rater and/or guider:
DATA_TRANSFER_CLASS1_QUEUE_SIZE and DATA_TRANSFER_CLASS2_QUEUE_SIZE, which give the
possibility to specify the maximum number of respectively Class1 and Class2 requests that can be queued in
the instance
DATA_TRANSFER_CLASS1_THREAD_COUNT and DATA_TRANSFER_CLASS2_THREAD_COUNT, which give
the possibility to specify the number of threads allocated to the instance for processing respectively Class1
and Class2 requests
DATA_TRANSFER_CLASS1_RESPONSE_HANDLER_THREAD_COUNT and
DATA_TRANSFER_CLASS2_RESPONSE_HANDLER_THREAD_COUNT, which give the possibility to specify the
number of threads allocated to the instance for processing responses to respectively Class1 and Class2
requests
DATA_TRANSFER_CLASS2_MAX_SEND_THROUGHPUT, which gives the possibility to specify the maximum
network bandwidth that the instance can use to respond to Class2 requests
DATA_TRANSFER_CLASS2_MAX_RECEIVE_THROUGHPUT, which gives the possibility to specify the
maximum network bandwidth that the instance can use to receive responses to Class2 requests
DATA_TRANSFER_CLASS2_MAX_MESSAGE_SIZE, which gives the possibility to specify the maximum size of
messages that can be sent by the instance when responding to Class2 requests
DATA_TRANSFER_CLASS1_TIMEOUT and DATA_TRANSFER_CLASS2_TIMEOUT, which give the possibility to
specify the maximum time (in seconds) that the instance can take to respond to respectively Class1 and
Class2 requests
Refreshing the shared allowances cache

Contrary to the other cached structures that contain partitioned data, the shared allowances cache contains data
that is shared among the running raters. To ensure consistency and synchronization between the running raters, the
cached structure containing the shared allowances must be regularly refreshed. These refreshing operations can be:
Manually performed using the “refresh_shared_allowance_cache” dedicated command that is available in the
Admin+ user interface
Automatically executed by dedicated scheduler (managed by the master dispatcher):
That you can enable or disable
Whose recurrence can be configured to fit specific needs
NOTES
The shared allowances cache can be refreshed according to using the following execution modes:
incremental, which gives the possibility to add the new shared allowances, remove the deleted shared
allowances and update the distributed counters statuses
full, which gives the possibility to add or update all valid shared allowances and all distributed counters
statuses
The scheduler in charge of refreshing the shared allowances cache is enabled by default, and uses the
incremental execution mode
To modify the configuration of the scheduler in charge of refreshing the cached structure containing the shared
allowances, execute the following procedure:

2. For each concerned dispatcher, modify the value of the following parameters:
SHARED_ALLOWANCE_CACHE_REFRESH_SCHEDULER_ENABLED, which gives the possibility to enable or
disable the execution of the scheduler
SHARED_ALLOWANCE_CACHE_REFRESH_SCHEDULER_RECURRENCE, which defines the recurrence period of
the scheduler
Keywords
Data files, error files, bulkloader
Preliminary notes
“Data Files Generation” and “Data Files Bulk Loading Process” process descriptions available in the SAP CC
Application Help documentation
“XXX_PRE_CREATE_FILE (BulkWriter)” system parameter description available in the SAP CC System Parameters
Description
During the execution of the different processes handled by SAP Convergent Charging, data files are generated for
multiple purposes such as integration with third-party systems, error management, notifications, logging, tracing,
and so on. You can use the following procedures to configure the generation of the data files and thus fit your
specific needs:
Modifying the data files processor
Modifying the version of data files generated by raters
Enabling the file name sequencing for data files generated by raters
Enabling the line numbering for data files generated by raters
Enabling the archive files cleaning for data files generated by raters
Enabling the pre-creation policy for data files generated by raters and bulkloaders
Modifying the version of error files generated by bulkloaders
Enabling the file name sequencing for error files generated by bulkloaders
Modifying the data files processor

During charging and refilling operations, raters generate data files whose persistency is managed by a dedicated
framework which gives the possibility to implement the following file processors:
Transaction File processor, which creates a single file whose content can be customized
Data File processor, which creates multiple data files which contain different data related to transactions
Charged Item File, Refill Record File or Chargeable Item File processor, which give the possibility to create data
files whose content corresponds to taxed & charged transactions transcribed into:
Chargeable items, during chargeable items acquisition and charging operations
Charged items, during chargeable items charging and prepaid accounts refilling operations
Refill records, during prepaid accounts refilling operations
Rerate File processor, which gives the possibility to create data files whose content can be used by a third-party
system for rerating purposes

Enabling the Transaction Integration Framework (TIF) to generate Transaction Files

To enable the Transaction File processor, execute the following procedure:
2. For each concerned rater, modify the value of the TRANSAC_PROC_CLASS system parameter to the following
value: com.highdeal.tif.tfp.TransactionFileProcessor
NOTES
For further information about this file processor, refer to the description of the “Process (Old): Output Data
Generation (Transaction File Processing)” group available in the SAP CC System Parameters Reference
documentation
This file processor is not compatible with charge plans. Even if this processor is not deprecated, SAP SE
recommends that you avoid using it
Enabling the Transaction Integration Framework (TIF) to generate Data Files

To enable the Data File processor, execute the following procedure:
value: com.highdeal.tif.dbFile.TransactionFileProcessor
NOTES
For further information about this file processor, refer to the description of the “Process (Old): Output Data
Generation (DB File Processing)” group available in the SAP CC System Parameters Reference documentation
This file processor is not compatible with charge plans. Even if this processor is not deprecated, SAP SE
recommends that you avoid using it
Enabling the Charging output Integration Framework (CIF) processor

To enable the Charging output Integration Framework (CIF) processor and generate data files containing either
charged items, chargeable items or refill records, execute the following procedure:
value: com.highdeal.tif.chargeditem.TransactionProcessorShell
To fit specific needs such as data files path, multithreaded generation, rollover policy, file compression, and so on,
you can configure the data file generation of all available channels (prepaid, postpaid, charged and acquired) using
the following parameters:
Settings Description
rootPath Writing location for generated files. For further information, refer to the
description of the XXX_ROOT_PATH-BulkWriter system parameter

channelCount Number of writing channels. For further information, refer to the description
of the XXX_CHANNEL_COUNT-BulkWriter system parameter
timeBasedFileRolloverPolicy Rolling policy for generated files. For further information, refer to the
maxSizeBasedFileRolloverPolicy description of the XXX_TIME_BASED_FILE_ROLLOVER_POLICY-BulkWriter
and XXX_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY-BulkWriter system
parameters
deflate Compression policy, that respects the RFC 1951 specifications. For further
deflateOutputFormat information, refer to the description of the XXX_DEFLATE-BulkWriter and
XXX_DEFLATE_OUTPUT_FORMAT-BulkWriter system parameters
storeFileInformation Flag used to store information about the generated files into the
“CHARGED_ITEM_FILES” table of the Core database
fileVersion Version of the generated data files. To modify this parameter, refer to the
“Modifying the version of data files generated by raters” dedicated procedure
available afterwards
lineNumbering Flag used to write line numbers in the generated data files. To modify this
parameter, refer to the “Enabling the line numbering for data files generated
by raters” dedicated procedure available afterwards
cleanArchivedFile Flag used to enable or disable the removal of uncommitted items from the
generated data files. To modify this parameter, refer to the “Enabling the
archive files cleaning for data files generated by raters” dedicated procedure
available afterwards
fileSequenceId Identifier used for sequencing the names of the generated data files. To
modify this parameter, refer to the “Enabling the file name sequencing for
data files generated by raters” dedicated procedure available afterwards
preCreateFile Flag used to enable or disable the pre-creation of data files. To modify this
parameter, refer to the “Enabling the pre-creation policy for data files
generated by raters and bulkloaders” dedicated procedure available
afterwards
eventDateShifting To modify this mechanism, refer to the “Enabling the event date shifting
mechanism for data files generated by raters” dedicated procedure available
afterwards
billableItemValidator To modify this mechanism, refer to the “Enabling the billable item validation
for data files generated by raters” dedicated procedure available afterwards
To configure the CIF parameters, execute the following procedure:

2. Export the CIF configuration of the rater instances using the following command:
cif export rater rater.cif.xml
3. Edit the retrieved “rater.cif.xml” configuration file
4. Modify the relevant parameters
6. Import the modified CIF configuration for the rater instances using the following command:
cif import rater rater.cif.xml
NOTE
Template files named cif.rater.config.xml.sk is available in the config subfolder of the SAP Central
Repository, within subfolders whose name depends on the installation scenario:
“sapci” in case of integrated scenario with SAP Convergent Invoicing
“standalone” otherwise
Enabling the Rerating Integration Framework (RIF)

To generate data files for rerating purpose, execute the following procedure:
2. For each concerned rater, modify the value of the RERATE_PROC_CLASS system parameter to the following
values:
com.highdeal.rif.chargeditem.RerateProcessorShell, in case you use the CIF
com.highdeal.rif.dbFile.RerateFileProcessor, in case you use the Data File processor
To fit specific needs such as data files path, multithreaded generation, rollover policy, file compression, and so on,
you can configure the data file generation of rerating requests using the following parameters:
rootPath Writing location for generated files. For further information, refer to the
description of the XXX_ROOT_PATH-BulkWriter system parameter
channelCount Number of writing channels. For further information, refer to the description
of the XXX_CHANNEL_COUNT-BulkWriter system parameter
timeBasedFileRolloverPolicy Rolling policy for generated files. For further information, refer to the
maxSizeBasedFileRolloverPolicy description of the XXX_TIME_BASED_FILE_ROLLOVER_POLICY-BulkWriter
and XXX_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY-BulkWriter system
parameters
deflate Compression policy, that respects the RFC 1951 specifications. For further
deflateOutputFormat information, refer to the description of the XXX_DEFLATE-BulkWriter and
XXX_DEFLATE_OUTPUT_FORMAT-BulkWriter system parameters
preCreateFile Flag used to enable or disable the pre-creation of data files. To modify this
parameter, refer to the “Enabling the pre-creation policy for data files
generated by raters and bulkloaders” dedicated procedure available
afterwards
To configure the RIF parameters, execute the following procedure:

2. Export the RIF configuration of the rater instances using the following command:
rif export rater rater.rif.xml
3. Edit the retrieved “rater.rif.xml” configuration file
4. Modify the relevant parameters

6. Import the modified RIF configuration for the rater instances using the following command:
rif import rater rater.rif.xml
NOTE
Template files named rif.rater.config.xml.sk is available in the config subfolder of the SAP Central
Repository, within subfolders whose name depends on the installation scenario:
“sapci” in case of integrated scenario with SAP Convergent Invoicing
“standalone” otherwise
Modifying the version of data files generated by raters

During charging and refilling operations, raters generate data files containing information about incoming events. To
modify the version of these data files generated by raters, execute the following procedure:
4. For each “bulkwriter” XML element located under a “chargedItemTransactionProcessor” XML element, set the
“fileVersion” attribute to “1” or “2”
5. For each “bulkwriter” XML element located under a “chargeableItemTransactionProcessor” XML element, set
the “fileVersion” attribute to “1” or “2”
Enabling the file name sequencing for data files generated by raters
The 2nd version of data files generated by the rater instances gives the possibility to add a sequence number to the
names of these generated files. To enable this file name sequencing for data files generated by raters, execute the
following procedure:
2. Get the number of database connections currently set for rater instances using the following command:
get SQLHELPER_CONNECTION_COUNT persistent rater
3. Increase this number of connections by 1 using the following command:
set SQLHELPER_CONNECTION_COUNT <increased_value> persistent rater
Where <increased_value> corresponds to the number of database connections, increased by 1
4. Enable the sequencing for error files by executing the following command:
set ITEM_FILE_SEQUENCE_ENABLED true persistent rater

8. For each “bulkwriter” XML element located under a “chargedItemTransactionProcessor” XML element, set the
following attributes to the relevant values:
“fileVersion” to “2”
“fileSequenceId” to “CHARGED_ITEM”
9. For each “bulkwriter” XML element located under a “chargeableItemTransactionProcessor” XML element, set
the following attributes to the relevant values:
“fileSequenceId” to “CHARGEABLE_ITEM”
Enabling the line numbering for data files generated by raters

The 2nd version of data files generated by the rater instances gives the possibility to add the line number as the first
field of each element of these data files. To enable this line numbering for data files generated by raters, execute the
following procedure:
4. For each “bulkwriter” XML element, set the “lineNumbering” attribute to “true”
Enabling the archive files cleaning for data files generated by raters
SAP CC gives the possibility to activate an automatic cleaning mechanism in order to remove the uncommited items
from data files, and the associated control files. To enable this automatic cleaning mechanism for data files
generated by raters, execute the following procedure:
4. For each “bulkwriter” XML element, set the “cleanArchivedFile” attribute to “true”


Enabling the pre-creation policy for data files generated by raters and bulkloaders
For optimization purpose, data files generated by raters and bulkloaders can be asynchronously pre-created, instead
of waiting for the associated channel to create these files on demand. To enable the pre-creation of data files
generated by raters and bulkloaders, execute the following procedure:
rif export rater rater.rif.xml
3. Edit the retrieved “rater.cif.xml” and “rater.rif.xml” configuration files
4. For each “bulkwriter” XML element, set the “preCreate” attribute to “true”
6. Import the modified configurations for the rater instances using the following command:
rif import rater rater.rif.xml
Modifying the version of error files generated by bulkloaders

During charging and refilling operations, raters generate data files containing information about incoming events.
These data files are taken into account by bulkloaders, in charge of converting the content of these files and sending
them to third-party systems. When an error occurs during bulk loading operations, the bulkloaders generate error
files whose content depends on the configured version.
To modify the version of error files used by bulkloaders, execute the following procedure:
2. Export the CIF configuration of the bulkloader instances using the following command:
cif export bulkloader bulkloader.cif.xml
3. Edit the retrieved “bulkloader.cif.xml” configuration file
4. For each “bulkwriter” XML element, set the “fileVersion” attribute to “1” or “2”
6. Import the modified CIF configuration for the bulkloader instances using the following command:
cif import bulkloader bulkloader.cif.xml
7. Restart the bulkloader instances of the Core Server system
Enabling the file name sequencing for error files generated by bulkloaders
The version 2 of error files generated by bulkloaders gives the possibility to add a sequence number to the names of
the files. To enable this sequencing for error files, execute the following procedure:
2. Get the number of database connections currently set for bulkloader instances using the following command:

get SQLHELPER_CONNECTION_COUNT persistent bulkloader

3. Increase this number of connections by 1 using the following command:
set SQLHELPER_CONNECTION_COUNT <increased_value> persistent bulkloader
Where <increased_value> corresponds to the number of database connections, increased by 1
4. Enable the sequencing for error files by executing the following command:
set ITEM_FILE_SEQUENCE_ENABLED true persistent bulkloader
6. Export the CIF configuration of the bulkloader instances using the following command:
cif export bulkloader bulkloader.cif.xml
7. Edit the retrieved “bulkloader.cif.xml” configuration file
8. For each “bulkwriter” XML element located under a “bulkReader” XML element, set the following attributes to
the relevant values:
“fileSequenceId” to a unique value (e.g. “COM_EXCEPTION”)
10. Import the modified CIF configuration for the bulkloader instances using the following command:
cif import bulkloader bulkloader.cif.xml
11. Restart the bulkloader instances of the Core Server system
Enabling the recording of file metadata

To monitor the generation of data files at rater and bulkloader level, execute the following procedure:
2. For each concerned rater and bulkloader, enable the service in charge of recording metadata related to data
files generated by SAP CC by executing the following commands:
set FILE_METADATA_RECORDING_ENABLED true persistent rater
set FILE_METADATA_RECORDING_ENABLED true persistent bulkloader
3. Modify if necessary the update interval related to the recording service by modifying the
FILE_METADATA_UPDATE_INTERVAL system parameter. For further information about this system parameter,
refer to its dedicated documentation available in the SAP CC System Parameters Reference documentation
4. Restart the concerned instances of the Core Server system. Metadata related to data files generated during the
execution of the different processes are now recorded in the Core database. You can use the “Analyze Item
Files” dedicated application available in the SAP CC Cockpit user interface to visualize and analize these
metadata.
Enabling the event date shifting mechanism for data files generated by raters
To enhance the integration with SAP Convergent Invoicing, an event date shifting mechanism is available in SAP CC
to match the behavior of both system regarding the interval of event dates (inclusion, exclusion). To enable this
mechanism and shift the event dates, execute the following procedure:
4. Add the necessary “eventDateShifter” XML element in the processing channel, such as:
Around each “sequence” XML element which surrounds a “billableItemValidator” XML element
Around each “billableItemValidator” XML element which is not surrounded by a “sequence” XML element
Enabling the billable item validation for data files generated by raters
To detect some possible errors during the generation of the billable items, SAP CC gives the possibility to perform a
verification of the format of the charged items’ fields.
NOTES
In case of charged item aggregation, SAP SE recommends to disable the billable item validation to avoid
loosing charged items related to events which are already confirmed
The billable item validation mechanism may impact the global performance of your landscape. As a
consequence, SAP SE recommends that you use this mechanism in validation landscapes to ensure the correct
generation of billable items, and then disable it in production landscape
To enable this validation mechanism, execute the following procedure:

4. Add the necessary “billableItemValidator” XML element in the processing channel. SAP SE recommends that you
put this element before the output operation within the data files, to avoid writing data that will later lead to
errors
Data purging
Keywords
Purge, allowance, change list, file metadata, retention period, expired, scheduler, product usage metrics
Preliminary notes
“Data Purging” section of the SAP CC Application Help documentation
“Data Purging and Archiving” section of the SAP CC Operations Guide documentation

Description
As described in the Application Help documentation, SAP Convergent Charging manages high volumes of data that is
stored within the different databases (Core, Session and BART databases). To ensure performance, it is necessary to
remove obsolete and/or useless data. You can use this procedure to configure the purge of:
Expired allowances whose expiration date exceeds a given retention period
Metadata related to data files generated by SAP CC during the execution of the different processes
Metrics related to the product usage
Configuring the allowances purge mechanism

Purge operations related to allowances data can be executed:
Automatically using a dedicated scheduler
Manually using the “start_purge_allowances” command of the Admin+ user interface
The following table contains the list of system parameters and indicators you can configure:
System parameter Description
ALLOWANCES_PURGE_RETENTION_PERIOD Number of days until which expired allowances are
kept into the database and cannot be deleted
ALLOWANCES_PURGE_THREAD_COUNT Number of threads to use when performing the
allowances purge operations
ALLOWANCES_PURGE_LAST_TRIGGER Date of the last manual execution of an allowances
purge operation
ALLOWANCES_PURGE_SCHEDULER_LAST_TRIGGER Date of the last automatic execution of a purge
operation performed by the scheduler
ALLOWANCES_PURGE_SCHEDULER_ENABLED Enables/disables the scheduling of purge operations
related to expired allowances
ALLOWANCES_PURGE_SCHEDULER_RECURRENCE Execution recurrence of the dedicated scheduler
ALLOWANCES_PURGE_SCHEDULER_MAX_THROUGHPUT Maximum number of charging contracts per second
that the scheduler can consider when purging
allowances
By default, the scheduler in charge of executing allowances purge operations is pre-configured:

To be triggered every day at midnight
To be executed using 1 thread per rate
To purge the allowances of 10 charging contracts per second at the most
To take into account a default retention period for allowances which must be the same than the retention
period used for recharging purposes (set as 40 days by default)
To modify the configuration of the purge operations of data that relate to expired allowances, execute the following
procedure:
2. For each rater instance, modify the values of the following system parameters:
ALLOWANCES_PURGE_RETENTION_PERIOD
ALLOWANCES_PURGE_THREAD_COUNT
3. For each updater instance, modify the values of the following system parameters:
ALLOWANCES_PURGE_SCHEDULER_ENABLED
ALLOWANCES_PURGE_SCHEDULER_RECURRENCE
ALLOWANCES_PURGE_SCHEDULER_MAX_THROUGHPUT
NOTES
Only one execution of the scheduler is possible at the same time. The date of this execution is recorded in the
ALLOWANCES_PURGE_SCHEDULER_LAST_TRIGGER indicator, for information purpose
For performances purposes, the execution of the scheduler in charge of purging the expired allowances is
linked to the scheduler used to perform the activation of provider contracts. When the execution of these two
schedulers occurs at the same time, a merged operation is performed to immediately remove expired
allowances of each activated provider contract. As this merged operation also shares the technical configured
resources (threads and throughputs), SAP SE recommends that you decouple the execution of the 2 schedulers
if you detect any overload or latency
Configuring the file metadata purge mechanism

Purge operations related to file metadata can be executed:
Automatically using a dedicated scheduler
Manually using the “purge_file_metadata” command of the Admin+ user interface
The following table contains the list of system parameters and indicators you can configure:
FILE_METADATA_PURGE_SCHEDULER_ENABLED Enables/disables the scheduler in charge in charge of
purging metadata related to data files generated by SAP
CC
FILE_METADATA_PURGE_SCHEDULER_RECURRENCE Execution recurrence of the dedicated scheduler, that
corresponds by default to an execution every day at
midnight
FILE_METADATA_PURGE_RETENTION_PERIOD Number of days until which file metadata whose reference
date is exceeded must be taken into account by the
dedicated scheduler in charge of purging file metadata
To modify the configuration of the purge operations of data that relate to file metadata, execute the following
procedure:
2. For each updater instance, modify the values of the following system parameters:
FILE_METADATA_PURGE_SCHEDULER_ENABLED
FILE_METADATA_PURGE_SCHEDULER_RECURRENCE
FILE_METADATA_PURGE_RETENTION_PERIOD
Configuring the product usage purge mechanism

As described in the “Recording product usage metrics” dedicated section, metrics related to product usage are
recorded in the Core database by a dedicated scheduler. In addition to the recording of these metrics, this scheduler
is also in charge of executing the purge of metrics that exceed the retention period.
As a consequence, no manual purge operation is available. You can only tune the purge of product usage metrics by:
Modifying the retention period for the recorded metrics
Enabling the scheduler in case it has been disabled
Keywords
JVM options, virtual machine, memory heap, garbage collection, buffers
Preliminary notes
“JVM option recommendations for SAP Convergent Charging” SAP Note 2006073 documentation
“Generate Java GC Log for SAP Convergent Charging” SAP Note 1950168 documentation
Description
The architecture of SAP Convergent Charging relies on a set of java-based applications whose execution require a
Java Runtime Environment that can be configured to fit specific requirements. You can use this procedure to
determine the different JVM options that must be configured within the startup configuration files of each
concerned element.
The following table contains the list of JVM options you can configure:
JVM Option Description
JVM Settings for Garbage Collection
-XX:{+-}PrintGC Enables/disables the basic GC logging mode, which consists in
recording 1 line for every Young Generation GC and for every Full GC
-XX:{+-}PrintGCDetails Enables/disables the detailed GC logging mode, whose content
depends on the algorithm used for garbage collection
-Xloggc:<FULL_PATH> Defines the path and name of the logging file. Setting this option
implicitly sets the -XX:+PrintGC and -XX:+PrintGCTimeStamps options.
-XX:LogGcMaxFileSize=<SIZE> Defines the maximum size of a GC log file, expressed in bytes. If the log
file exceeds this size, a new log file is created. A number of “old” log
files are kept, according to the value of the -XX:LogGcMaxFileCount
option
-XX:LogGcMaxFileCount=<NUMBER> The maximum number of files to use for the GC log. A new GC log file
is created when the JVM is restarted or when the log file size exceeds
the size given by the -XX:LogGcMaxFileSize option
-XX:{+-}PrintGCCause Prints/hides information related to the reason of the garbage
collection
-XX:{+-}PrintGCTimeStamps Prints/hides the timestamp of the garbage collection
-XX:{+-}PrintTenuringDistribution Prints/hides tenuring age information
-XX:{+-}PrintPromotionFailure Prints/hides additional diagnostic information about promotion failure
-XX:{+-}PrintFLSStatistics Prints/hides additional information about the fragmentation of the
heap memory
JVM Settings for Garbage Collection and History

-XX:{+-}GCHistory Enables/disables the garbage collection history. When enabled, you

can configure the way this history is stored by defining the other
-XX:GCHistory* options
-XX:GCHistoryFilename=<FULL_PATH> Defines the path and name of the file used to store the information
related to garbage collection history
-XX:GCHistoryMaxFileSize=<SIZE > Defines the maximum size of a file containing information related to
garbage collection history, expressed in bytes
-XX:GCHistoryMaxFileCount=<NB_FILES> Defines the maximum number of files that are used for the garbage
collection history, from 1 to 99. A new garbage collection history file is
created when the JVM is restarted.
NOTE
The “.b<00..99>” extension is added for backup files.
(e.g. sapjvm_gc.prf.b00, which is the newest backup file)
-XX:GCHistoryCompressionLevel=<LEVEL> Defines the compression level for garbage collection history files.
0 means no compression
9 is the maximum possible compression
5 is the default value, which corresponds to medium compression
and medium CPU cost, but which is not recommended for SAP CC
JVM Settings for Performance and Stability
-Xmn<SIZE> Defines the size of the heap memory for the young generation,
expressed in bytes. Append the letter k or K to indicate kilobytes, or m
or M to indicate megabytes
-Xms<SIZE> Defines the initial size of the heap memory, expressed in bytes. This
value must be a multiple of 1024 greater than 1MB. Append the letter
k or K to indicate kilobytes, or m or M to indicate megabytes. The
default value is 2MB
-Xmx<SIZE> Defines the maximum size of the heap memory, expressed in bytes.
This value must be a multiple of 1024 greater than 2MB. Append the
letter k or K to indicate kilobytes, or m or M to indicate megabytes.
The default value is 64MB.
-Xss<SIZE> Defines the size of the Java thread stack, expressed in bytes. Append
the letter k or K to indicate KB, m or M to indicate MB, g or G to
indicate GB. The default value depends on the virtual memory
-XX:{+-}UseParallelOldGC Enables the use of the parallel compacting collector algorithm for GCs
operations. Enabling this option implicitely enables the -
XX:+UseParallelGC option
-XX:{+-}UseSplitVerifier Enables the splitting of the verification process into two phases: type
referencing (performed by the compiler) and type checking
(performed by the JVM runtime). This option was deprecated in JDK 8,
and verification is now split by default without a way to disable it
-XX:MaxDirectMemorySize=<SIZE> Defines the maximum total size (in bytes) of the New I/O (the java.nio
package) direct-buffer allocations. Append the letter k or K to indicate
kilobytes, m or M to indicate megabytes, g or G to indicate gigabytes.
By default, the size is set to 0, which means that the JVM chooses
automatically the size for NIO direct-buffer allocations

-XX:CompileThreshold=<NUMBER> Defines the number of interpreted method invocations before

compilation. By default:
On server side, the JIT compiler performs 10000 method
invocations to gather information for efficient compilation
On client side, the default setting is 1500 invocations
-XX:SurvivorRatio=<RATIO> Defines the initial survivor space ratio that is used by the throughput
garbage collector (which is enabled by the -XX:+UseParallelGC and/or -
XX:+UseParallelOldGC options). By default, the initial survivor space
ratio is set to 16
-XX:ConcGCThreads=<NUMBER> Defines the number of threads used for concurrent GC. The default
value depends on the number of CPUs that are available for the JVM
-XX:ParallelGCThreads=<NUMBER> Defines the number of threads used for parallel garbage collection in
the young and old generations. The default value depends on the
number of CPUs that are available for the JVM
-XX:TargetSurvivorRatio=<NUMBER> Defines the desired percentage of survivor space (from 0 to 100) used
after young garbage collection. By default, this option is set to 90%
-XX:{+-}ScavengeBeforeFullGC Enables garbage collection of the young generation before each full
GC. This option is enabled by default and it is not recommended to
disable it, as scavenging young generation before a full GC can reduce
the number of objects reachable from the old generation space into
the young generation space
-XX:{+-}UseAdaptiveSizePolicy Enables the automatic sizing of the young generation and selection of
an optimum survivor ratio to maximize performance during parallel GC
-XX:PromotedPadding=<NUMBER> Defines the size of the buffer used for promotion failures
-XX:{+-}DisableExplicitGC Disables the processing of calls to System.gc(). SAP SE recommends
that you disable this option for updaters and dispatchers
-XX:{+-}TieredCompilation Enables the tiered compilation
Other JVM Settings
-Dsapcc.home File path and name of the SAP CC Working Directory
-Dboot.config=<FULL_PATH> File path and name of the boot.config file
-Dfile.encoding Encoding settings. Must be set to UTF-8
-Dsun.nio.ch.useIPv6Stack Only required for MS Windows landscapes using IPv6
-Dcom.sap.jvm.xerces Must be set to true
.disallowDoctypeDecl.failEarly
JCo destinations
Keywords
JCo destination, RFC over TCP/IP, SAP ERP reference, SAP CRM, FI-CA
Preliminary notes
SAP JCo documentation available on SAP Help Portal
“Launching Setup Tool” and “Securing the RFC over TCP/IP communications” sections of the SAP CC Installation
Guide documentation

Description
SAP Convergent Charging uses the JCo technology to communication with the SAP CRM and SAP ERP/FI-CA systems,
through the Remote Function Calls (RFCs) protocol provided by SAP. You can use this procedure to manage the
different JCo destinations for your landscape.
JCo server settings
JCo client settings
Tuning settings
Security settings
Parameter Values
JCo server settings
jco.client.ashost By default, no value is set. You must set the value that
Host name or IP address of the SAP corresponds to the targeted host
Application Server (or SAP Netweaver
Gateway)
jco.client.sysnr By default, no value is set. The system number corresponds to the
SAP System Number used to determine the last two numbers of the port the targeted SAP System runns on
gateway service
JCo client settings
jco.client.client By default, no value is set. You can set any 3-digits value that
Name of the SAP logon client corresponds to the targeted SAP System (preserving the leading
zeros in case they appear in the number)
jco.client.user By default, no value is set. You must specify a service user that
Login used for authenticating on the remote relates to a communication channel between SAP CC and an SAP
SAP System system (ERP, CRM) that is available in your landscape
jco.client.passwd By default, no value is set. You must set a password that respects
Password of the previously specified login, the SAP password policy
used for authenticating on the remote SAP
System
jco.client.lang The default value is set to: en
Language of the remote SAP System You can set any ISO two-character language code or SAP-specific
single-character language code
Tuning settings
jco.destination.peak_limit The default value is set to: 10
Maximum number of active connections that You can set any positive value
can be simultaneously created for a JCo
destination
jco.destination.pool_capacity The default value is set to: 3
Maximum number of idle connections kept You can set any positive value. Setting this parameter to 0 disables
open by the JCo destination the pooling of connections

Secuity settings
jco.client.snc_mode The default value is set to: 0
Enables/disables the use of Secured Network Possible values are:
Communications (SNC) 0: Not activated
1: Activated
jco.client.snc_lib By default, no value is set. You must set a value that corresponds
Absolute path of the SAP Cryptographic to the absolute path of the targeted library, such as:
Library that provides secured network For MS Windows operating systems:
connections C:\usr\sap\<SID>\SYS\exe\uc\<OS>\sapcrypto.dll
For Linux, HP-UX and Solaris operating systems:
/usr/sap/<SID>/SYS/exe/uc/<OS>/libsapcrypto.so
For AIX operating systems:
/usr/sap/<SID>/SYS/exe/uc/<OS>/libsapcrypto.o
Where:
<SID> corresponds to the system identifier of the concerned
Core Server system
<OS> corresponds to the relevant operating system
jco.client.snc_qop The default value is set to: 3
Security level of the secured network Possible values are:
connections 1: Authentication only
2: Integrity protection
3: Privacy protection
8: Use the value from snc/data_protection/use on the
SAP Application Server
jco.client.snc_myname By default, no value is set. You must set a value that corresponds
Name of the secured network connection, to the SNC name for SAP Convergent Charging, such as:
p:CN=SAPCC, O=<MyCompany>, C=US
that overrides the default secure network
connection partner
NOTES
Although this parameter is optional, SAP SE recommends
that you set this value in order to ensure that a correct SNC
name is used for the connection
The SNC name does not correspond to the Distinguished
Name you used when creating the Personal Security
Environment. The SNC name has the following syntax:
p:<Distinguished_Name>.
jco.client.snc_partnername By default, no value is set. You can find the Application Server’s
SNC name of the Application Server, that SNC name in the profile parameter named snc/identity/as
acts os the SNC partner
Creating JCo destinations

To create a JCo destination, execute the following procedure:
1. Connect to the host of your landscape where a dispatcher is installed

2. Copy the jco.destination.sk file available in the config/sapci folder of the dispatcher instance in a new
jco.destination file
3. Edit this newly created file and modifiy the relevant parameters to fit the targeted SAP system. For further
information about the available parameters, refer to the Configuration options section above
5. Execute the “jcodestination import” command to import these parameters in the Core database
Setting up the ERP reference system

SAP Convergent Charging communicates with a particular SAP ERP system in your landscape to synchronize some
business or technical data (such as currencies, billable item (BIT) classes or consumption item classes). This reference
ERP system correspond to a JCo destination that is set at installation time by SAPinst (in case of integrated
installation scenario). In case you need to modify this initial configuration or refer to a new SAP ERP system, execute
the following procedure:
2. Execute the “jcodestination list” command to retrieve the list of all the JCo destinations that are available in the
Core database
3. If the targeted SAP ERP system corresponds to one of the previously retrieved JCo destinations, execute the
“jcodestination export” command to ensure that the configuration of this JCo destination is correct. If the
targeted SAP ERP system does not correspond to one of the previously retrieved JCo destinations, or if the
exported configuration does not fit, you must create the relevant JCo destination using the Creating JCo
destinations section above
4. Once the relevant JCo has been located or created, execute the “erpreferencesystem setJCoDestination”
command, specifying the name of the JCo destination that must be used to communicate with the SAP ERP
system
Logging and tracing
Keywords
Log, trace, category, severity, domain, threshold, troubleshoot
Preliminary notes
“Launching Config Tool” section of the SAP CC Installation Guide documentation
“Starting and stopping the servers” section of the SAP CC Installation Guide documentation
“Troubleshooting: Logs and Traces” group in the SAP CC System Parameters Reference documentation
“Startup configuration file” configuration section of this documentation
This procedure uses the following variables:
<SAPCC_SYSADM_USERNAME> and <SAPCC_SYSADM_PASSWORD>, which corresponds to the name and
password of the administrator of your Core Server system ("admin" by default)
<INSTANCE_ID>, which corresponds to the identifier of a concerned instance

<LEVEL>, which corresponds to a possible level (DEBUG, PATH, INFO, WARNING, ERROR or FATAL)
<XML_FILE_PATH>, which corresponds to an XML file containing the exported configuration of the Core Server
system
Description
As described in the Application Help documentation, SAP Convergent Charging provides logging and tracing features
that give the possibility to generate both trace and log messages:
According to defined levels such as severity, thresholds, domains, categories
Using different output formats
In multiple output destinations
That can be viewed and analyzed in the SAP Management Console (SAP MC or SAP MMC)
Mainly addressed to administrators and support specialists, the generation of these log and trace messages can be
configured in order to fit specific needs such as landscape monitoring, performance tracing, issue troubleshooting,
and so on. You can use this procedure to configure the logging and tracing capabilities of your Core Server system
and thus fit your specific needs.
Logging and tracing features can be configured:
Through SAP CC system parameters
Trough dedicated options of the JVM
The following table contains the list of available settings, including the correspondence between Core Server system
parameters and JVM options (when exists):
Settings Description System parameter JVM option
Logs Severity threshold for logs LS_APP_SEVERITY ls.app.severity
(business processing) Identifier(s) of the destination(s) LS_APP_DESTINATION ls.app.destination
Logs Severity threshold for logs LS_SYS_SEVERITY ls.sys.severity
(system processing) Identifier(s) of the destination(s) LS_SYS_DESTINATION ls.sys.destination
Traces Severity threshold for traces LS_TRC_SEVERITY ls.trc.severity
Identifier(s) of the destination(s) LS_TRC_DESTINATION ls.trc.destination
Domain(s) for traces LS_TRC_DOMAIN ls.trc.domain
Console Enable/Disable LDC_ENABLED ld.console.enabled
Destination Output format LDC_FORMATTER ld.console.formatter
Fileset Destination Enable/Disable LDF1_ENABLED ld.file1.enabled
#1 Output format LDF1_FORMATTER ld.file1.formatter
Number of files available for the rotation LDF1_FILESET_SIZE ld.file1.setsize
Maximum file size before rotation LDF1_FILE_SIZE ld.file1.size
File path, name, and extension LDF1_FILE_NAME ld.file1.name
Enable/Disable LDF3_ENABLED ld.file3.enabled

Fileset Destination Output format LDF3_FORMATTER ld.file3.formatter

#3 Number of files available for the rotation LDF3_FILESET_SIZE ld.file3.setsize
JCo traces Level of JCo traces, from 0 to 10 JCO_TRACE_LEVEL N/A
(integrated Level of JCo CPIC traces, from 0 to 3 JCO_CPIC_TRACE_LEVEL N/A
landscape)
Enable/Disable JCo RFC traces JCO_JRFC_TRACE_LEVEL N/A
Path of the folder used to write trace files JCO_TRACE_PATH N/A
By default, logging and tracing features are configured to fit a productive landscape, which corresponds to the
The logging feature is enabled, with severity thresholds set to INFO
The tracing feature is enabled, with severity thresholds set to ERROR
Log and trace messages are generated in different files, that are available in SAP MC or SAP MMC applications
Generated files are stored in the working directory of each concerned instance
File rotation is enabled
Modifying the logging and tracing policy

To fit specific needs, you can modify the default configuration of the logging and tracing features. According to the
modifications, you can perform:
Immediate modifications, that are temporary. This kind of modifications can only be performed using the
Admin+ user interface, and only concern severity thresholds and domains associated to:
A given instance
All instances of a given type
A whole SAP system
Deferred modifications, that concerns all available settings and require to restart the targeted instances. This
kind of modifications can be performed:
Using the Admin+ user interface in case of few modifications
Using the Config Tool user interface in case of mass modifications
By updating startup configuration files
Immediate modifications using Admin+

To perform immediate modification of the severity thresholds and domains, execute the following procedure:

2. Modify the values of the following system parameters:

LS_APP_SEVERITY
LS_SYS_SEVERITY
LS_TRC_SEVERITY
LS_TRC_DOMAIN
EXAMPLES
To permanently set the severity of logs related to business processing operations to INFO for all instances of
the Core Server system, execute the following command:
set LS_APP_SEVERITY INFO all all
To temporary increase the severity of logs related to system processing operations to DEBUG for a given
instance of the Core Server system, execute the following command:
set LS_SYS_SEVERITY DEBUG memory <INSTANCE_ID>
NOTE
To reset the severity thresholds to the default value, execute the following commands:
set LS_APP_SEVERITY INFO all all
set LS_SYS_SEVERITY INFO all all
set LS_TRC_SEVERITY ERROR all all
Deferred modifications using Admin+

To perform deferred modification of a given setting related to logging and tracing features, execute the following
procedure:
2. Modify the configuration of logs and/or traces, using a persistent scope
EXAMPLES
To permanently increase the severity of traces to DEBUG for a given instance of the Core Server system,
execute the following command:
set LS_TRC_SEVERITY DEBUG persistent <INSTANCE_ID>
To change the number of files generated in destination#1 and apply this modification to all the instances of the
Core Server system, execute the following command:
set LDF_FILESET_SIZE <NB_FILE> persistent all
Deferred modifications using Config Tool

procedure:
1. Launch the Config Tool user interface using the configuration export command in order to export the
whole configuration of your SAP CC Core Server system into an XML file:
config configuration export <XML_FILE_PATH> all

2. Open the newly created XML file, and for each instance type (rater, updater, guider, bulkloader, taxer,
dispatcher), mark down the values of each parameter that relate to the configuration of the logging and tracing
features. For a complete list of parameters to analyze, refer to the “Configuration Options” section above.
3. For each analyzed system parameter:
Set the corresponding JVM option to the same retrieved value
Remove the “value” XML attribute of the system parameter from the configuration file
4. Update the following JVM options:
-Dls.trc.severity=PATH
-Dls.trc.domain=SQL,NET,HB
5. Remove the following JVM option:
-Dld.console.enabled=true
6. Edit the Startup Configuration File of each concerned instance and set the previously determined values for the
different JVM options. For further information, refer to the Startup configuration file section
7. Execute the configuration import command in order to import the content of the XML file containing the
modified configuration of your Core Server system:
config configuration import <XML_FILE_PATH>
EXAMPLE
Considering the following list of system parameters for a given instance type:
LDF1_ENABLED = true
LDF1_FILE_NAME = work/log/@[email protected]
LDF1_FILE_SIZE = 4
LDF1_FILESET_SIZE = 200M
LDF1_FORMATTER = LIST
LS_APP_DESTINATION = LDF1
LS_SYS_DESTINATION=LDF1
LS_TRC_DESTINATION=LDF2
The corresponding JVM options to set are:
-Dld.file1.enabled=true
-Dld.file1.name=work/log/@[email protected]
-Dld.file1.size=4
-Dld.file1.setsize=200M
-Dld.file1.formatter=LIST
-Dls.app.destination=LDF1
-Dls.sys.destination=LDF1
-Dls.trc.destination=LDF2
-Dls.trc.severity=PATH
-Dls.trc.domain=SQL,NET,HB
Deferred modifications using startup configuration files

procedure:
1. Edit the Startup Configuration File of each concerned instance. For further information, refer to the Startup
configuration file section
2. Update the value of each JVM option determined using the list of parameters available in the “Configuration
Options” section above.
Integrating SAP CC logs and traces with your Java application

In case you need to interface your Java-based application to the SAP CC logging and tracing framework, you need to
fulfill the following requirements:
You must use the SAP JVM
Your source code interacts with the sap.com~tc~logging~java.jar SAP CC library, that needs to be
included in the classpath of your application
Your source code interacts with the core_client.jar SAP CC library, that contains public APIs you can use
within your application, in particular the following packages:
com.highdeal.cnd.message, used for communications with SAP CC performed over the Messages over
TCP/IP communication channel
com.highdeal.hci.http, used for communications with SAP CC performed over the XML over HTTP
communication channel
Your client application contains a configuration file that defines the relevant system parameters of SAP CC as
defined in the “Configuration options” section above.
Master data management
Keywords
Product modeling, chargeable item class, refill item class, charged item class, refill record class, refill logic, reusable
charge, counter name dictionary, spending status description, charge plan, refill plan, monitoring plan, shared
counters, provider contract, charging contract, subscription, access, batch rating group assignment, subscriber
account, subscriber mapping table, subscriber range table, offer
Preliminary notes
“Master Data” section of the SAP CC Application Help documentation
“Launching Core Tool” section of the SAP CC Installation Guide documentation
“Roles and Authorizations” section of the SAP CC Security Guide documentation
Description
As described in the Application Help, SAP Convergent Charging manages different sets of master data whose
availability depends on the implemented model that can be:
Provider contracts and subscriptions, that corresponds to the initial model which was based on subscriptions,
but that is no more supported except in upgraded landscapes containing related master data

Provider contracts only, that corresponds to a new model designed to facilitate the integration with the SAP
ERP/FI-CA component of the SAP Business Suite, within which commercial products are configured through
charging units available from SAP CC charge plans.
For a complete list of master data associated to each available model, refer to the “Master Data” section of the SAP
CC Application Help documentation. You can use the following procedure to configure the different master data
related to the service provider and thus fit your specific business needs.
Configuring master data for the service provider

To configure the master data related to the service provider, execute the following procedure:
1. Launch the Core Tool user interface and identify as a user granted the “Marketing” role
2. Set up the relevant master data according to your needs, using the following information:
Master Data Description
(reusable) Core Tool menu: File / New / Charge
Charge Charges are used to manage fees related to the use of a customer service. Each charge applies
to a chargeable item class, and includes:
A price plan
A charge plan
Charge plan Core Tool menu: File / New / Charge Plan
Charge plans represent the charging conditions for accessing or consuming goods or services of
a service provider. Each charge plan consists of :
One or multiple charges
A set of parameters used to configure the charge(s)
A release status
Chargeable Core Tool menu: File / New / Chargeable Item Class
item class Chargeable items are sent to SAP CC by network elements for charging purpose. Each
chargeable item represents a set of properties used:
During the execution of the price plan that is associated to the different charges related to
the class of the chargeable item.
By a third-party billing system during billing and invoicing operations
Charged item Core Tool menu: File / New / Charged Item Class
class Charged items represents items generated by SAP CC during charging operations. Each charged
item is associated to a class that defines the properties to output, whose values can be
generated by price plans or on-the-fly computed. The following table contains the list of
properties that can be generated by SAP CC, that you can also use when configuring:
A charge customized in a charge plan or in an offer
An allowance logic customized in an allowance plan
Property Description
Account Type Code Type of account charged by SAP CC.
0: Prepaid account
1: External (postpaid) account
Account Type Is Boolean used to indicate that the account charged by SAP CC is a prepaid
Prepaid account
Account Type Name Textual representation of the type of account charged by SAP CC.
“prepaid”
“postpaid”
Allowance Event Class name of the allowance event that was sent to the allowance.
Class Name
NOTE
This property is empty for one-shot and recurring triggers.
Allowance Share Unique identifier used to group and access to shared allowances.
Identifier
Allowance Unique Unique identifier of the allowance.
Identifier
Allowance Validity Start date of the validity period of the allowance
Start Date
Allowance Validity End date of the validity period of the allowance
End Date
Amount (Excluding Amount of the charged item computed by SAP CC during the charging operation,
Tax) without any tax amount.
NOTE
This amount equals to the base amount when the charge customized in a
charge plan (or in an offer) is configured to deal with a net amount
Base Amount Reference amount of the charged transaction used by SAP CC to compute the
tax amount and generate the final amounts (amount excluding tax, total amount
including tax). This amount can be net or gross, according to the configuration of
the charge customized in a charge plan (or in an offer) that has been triggered
during the charging operation.
NOTES
To manage tax in an external system, consider the “VAT Transaction Gross
Price Flag” and the “Tax Is Included” fields
In case the EZtax tax system is selected, SAP CC considers the net amount
Base Rated Amount Reference amount, computed during the execution of a price plan of a master
charge, and used by SAP CC during the execution of the price plan of a
dependent charge (when exists).
Chargeable Items Boolean used to inform whether the operation which generated the charged
Are Exported item was also configured to generate chargeable items, or not
Charge Activation Cancelation date of the subscription, only available for cancelling a one-shot
Cancelation Date rate within a charge
Charge Activation Identifier of the activated charge in a provider contract or subscription.
Code
NOTE
This identifier can also correspond to the identifier of the refill logic in a
provider contract
Charge Activation Creation date of the subscription, only available for one-shot rates containing an
Effective Date activation event
Charge Component Type of the rate component that is activated in the price plan, that can be:
Name Usage Rates
Recurring Rates
One-Shot Rates
Charge Date Date of the charged event (usage, recurring or one-shot) or refill event

Charge Reference In case the charging operation was based on an external reference, this property
corresponds to the identifier of this external reference
Charge Reference In case the charging operation was based on an external reference, this property
Name corresponds to the name of this external reference, set in the charging plan of
the activated charge
Charge Type Code Numeral code used to identify the charge.
0: Closing
1: Refill charge
2: Internal charge
3: External charge
4: Not charged
Charge Type Name Textual representation of the type of charge charged by SAP CC.
“closing”
“refillCharge”
“internalCharge”
“externalCharge”
“notCharged”
Chargeable Item Class name of the chargeable item that was charged by SAP CC, only available
Class Name for usage charging operations
Charged Amount is Boolean used to indicate whether the amount of the charged transaction is a
a Credit credit amount, or not
Charged Amount is Boolean used to indicate whether the amount of the charged transaction is a
a Debit debit amount, or not
Charged Item Set Identifier of a set of charged items or refill records generated by SAP CC.
Identifier
or NOTE
Refill Record Set
A charged item set represents a charged item coming from a master charge
Identifier plus charged items possibly coming from the dependent charges.
Charged Tax Tax amount of the charged transaction, that is an alias of the “Tax Amount”
Amount property
Charged Tax Code Tax code of the charged transaction, that is an alias of the “Tax Code” property
Charged Tax Detail
Charged Tax Status Deprecated (use “Tax Status Code” instead)
Code Textual representation of the tax status of the charged transaction, that is an
alias of the “Tax Status Code” property.
“tsNoTax”: No tax was applied
“tsForInfo”: The computed tax information is given for information purpose
“tsApplied”: The tax was applied
“tsTaxExempted”: Tax exemption
“tsBuyerSubjectToPay”: The buyer is responsible for reversing the tax to the
tax authority
Deprecated values:
“tsTaxMissedForInfo”: Information is missing for the data related to the tax
“tsTaxMissedForApply”: The tax information was missing to apply the tax
“tsUnknown”: The tax status is unknown
Charged Tax Status Deprecated (use “Tax Status Identifier” instead)
Identifier Numerical code of the tax status of the charged transaction, that is an alias of
the “Tax Status Identifier” property.


0: No tax was applied
1: The computed tax information is given for information purpose
2: The tax was applied
3: Tax exemption
4: The buyer is responsible for reversing the tax to the tax authority
Deprecated values:
-1: Information is missing for the data related to the tax
-2: The tax information was missing to apply the tax
-3: The tax status is unknown
Charged Total Deprecated (use “Total Amount” instead)
Amount (Incl. Tax) Total amount of the charged transaction, including tax
Charged Boolean used to indicate whether the charged transaction concerns a charging
Transaction is a operation related to a prepaid account, or not
Prepaid Debit
Charged Boolean used to indicate whether the charged transaction concerns a refilling
Transaction is a operation related to a prepaid account, or not
Prepaid Refill
Charging Name of the charging component
Component Name
Charging Detail
Field
Contract Identifier Identifier of the provider contract, whose value depends on the context:
In a charge plan, this identifier corresponds to the identifier of the provider
contract which generated the charged item
In an allowance plan, this identifier corresponds to the identifier of the
provider contract owning the allowance which generated the charged item
Contract Item External identifier set by an external system (or by the SAP CRM system in case
External Identifier of integrated scenario), retrieved from the external code set in a contract item
stored within SAP CC
Contract Item Identifier set by an external system (or by the SAP CRM system in case of
Identifier integrated scenario), retrieved from the name (or code) set in a contract item
stored within SAP CC
Contract Type Type of contract which generated the charged item.
“P”, for provider contracts
“S”, for subscriptions
Currency ISO 4217 (three-letter) code of the charged transaction currency
End of Rating End date of the period related to a recurring rate, that can be different from the
Recurring Period “End of Rating Reference Recurring Period” property that is used when the
recurring rate is prorated
End of Rating End date of the reference period related to a recurring charge
Reference
Recurring Period
Event Date Date of the rated event, that equals to the consumption date of a usage rate or
to the triggering date of the recurring rates or one-shot rates
Event Processing Date when the event which generated the charged item was processed by SAP
Date CC
Excluded Last Day
of the Rating
Recurring Period

External Account Identifier of the postpaid account to be charged, that is set in the external
Code account of the related subscriber account
External System Identifier of the external system to be charged (in case of postpaid account),
Code that is set in the external account of the related subscriber account
First Dispatch Code Dispatch code #1, which corresponds to the name of the property chosen as the
first criteria when filtering External Account transactions
Name of Rate
Component Used
Offer Code Identifier (name) of the activated offer concerned by the charging operation
Overrun From Identifier of the prepaid account which called the overrun, that is
Empty for the first overrun
Only available in the context of prepaid account overrun
Overrun To Identifier of the prepaid account from which the overrun is called, that is:
Empty for the last overrun
Only available in the context of prepaid account overrun
Prepaid Balance Current amount of the prepaid account balance selected determined during the
Amount charging operation
Prepaid or External Identifier of the account (prepaid or external postpaid) to charge
Account Code
Prerating Deprecated
Reservation Identifier of the reservation in case of a prerating operation
Identifier
Price Plan Name Identifier (name) of the executed price plan of a charge
Produced by a Type of the charge (customized in a charge plan or in an offer) that contains the
Master Charge price plan triggered during the charging operation.
Component Possible values are:
1: Master charge
2: Dependent charge
Produced by an Boolean used to indicate whether the charged item was generated by an
Allowance allowance, or not
Rated Amount Amount of the rated transaction, before tax computation. This raw amount is
computed by SAP CC when executing the price plan of a charge customized in a
charge plan (or in an offer), and equals to the “Base Amount” property when no
overrun exists.
NOTE
Do not use this field to set up the generation of charged transactions or
charged items.
Rated Amount is Boolean used to indicate whether the amount is prorated, or not
Prorated
Rated Amount is Boolean used to indicate whether the amount concerns a refund, or not
Refunded
Rated Boolean
Rated Date
Rated Number
Rated String
Rated Tax Amount Deprecated (use “Base Amount” instead)
Tax amount computed during the execution of a (net) price plan, that is
available in the rated transaction.

NOTES
Do not use this property when the price plan is gross
charged items
Rated Tax Code Code of the tax
Rated Tax Status Deprecated (use “Tax Status Code” instead)
Code
Rated Tax Status Deprecated (use “Tax Status Identifier” instead)
Identifier
Rated Total Amount Deprecated (use “Rated Amount” instead)
Total amount, including tax, computed during the execution of a (net) price
plan.
NOTES
Do not use this property when the price plan is gross
charged items
Rating Activation Date when the recurring charge has been triggered during a charging operation
Date
Rating Consumption date of the chargeable item related to a usage charging operation
Consumption Date
Rating Event Origin Type of charged event.
“U” (Usage): The event corresponds to the usage of the consumed service,
that is configured within usage rates or refills in the pricing logic
“R” (Recurring): The event corresponds to a periodic fee, that is configured
within recurring rates or refills in the pricing logic
“O” (One-shot): The event corresponds to a one-off fee, that is configured
within one-shot rates or refills in the pricing logic
Refill Amount
Refill Currency
Refill Date
Refill ISO Currency
Sender Job Identifier of the sender that sent a job of charging operations to SAP CC (for
Identifier example, job identifiers are used in case of mass charging operations when SAP
CI sends one or more jobs of charging operations to SAP CC)
Second Dispatch Dispatch code #2, which corresponds to the name of the property chosen as the
Code second criteria when filtering External Account transactions
Service Identifier Identifier of the consumed customer service provided by a service provider, that
is only available for usage charging operations
Service Provider Identifier of the service provider, that corresponds to the name of the catalog of
Name the service provider
Service Provider ISO 3166 country code of the service provider according to the tax settings of
Country Code the charge customized in a charge plan (or in an offer) executed at runtime
Session Rating Identifier of the session reservation, that is only available for session-based
Reservation charging operations
Identifier

Start of Rating Start date of the period related to a recurring rate, that can be different from
Recurring Period the “Start of Rating Reference Recurring Period” used when a recurring charge is
prorated
Start of Rating Start date of the reference period related to a recurring rate
Reference
Recurring Period
Subscriber Account Identifier of the subscriber account
Code
Subscriber Account Reference of the subscriber account
Reference
Subscriber Boolean used to inform about the relationship between the subscriber and the
Consumes Service customer service. When this property is set to “true”, the business transaction
(Client) relates to a client relationship, which means that the subscriber consumed the
service provided directly by the service provider
Subscriber Provides Boolean used to inform about the relationship between the subscriber and the
Service (Partner) customer service. When this property is set to “true”, the business transaction
relates to a partner relationship, which means that the subscriber consumed the
service provided by a partner of the the service provider
Subscription Code Identifier of the triggered subscription
Subscription Commitment date of the subscription
Commitment
Expiration Date
Subscription Resumption date of the subscription
Resumption Date
Subscription Suspension date of the subscription
Suspension Date
Tax Amount Amount of tax applied and adjusted to a charged transaction, that is associated
to the “Currency” property which contains the related currency
Tax Code String representation of the tax code of a charged transaction (or charged item)
assigned to a prepaid or external postpaid account.
“/<COUNTRY_CODE>/<VAT_RATE_LEVEL>#<timestamp>”, for the VAT tax
system, where:
- <COUNTRY_CODE> is an ISO 3166 country code (2-digit)
- <VAT_RATE_LEVEL> is a value from 0 to 5
“/RAW/<RATE_ID>”, for the Flat tax system, where <RATE_ID> is the
identifier of the flat tax rate defined in the charge
“NO_TAX”, when no tax system is defined in the charge or in the subscriber
account, or when the system configuration is erroneous
“EZTAXED”, for the EZtax tax system used for U.S telco taxes
Tax Determination Information about the tax, used by the billing system.
Type Possible values, that depends on the tax status, are:
“00”, default value available when the tax status is
“BUYER_SUBJECT_TO_PAY”, “TAX_EXEMPTED” or “NO_TAX” to inform that
the tax status is applied and must not be calculated by the billing system
“01”, available when the tax status is “FOR_INFO” to inform that the tax
system is VAT, or Flat
“04”, available when the tax status is “FOR_INFO” to inform that the tax
system is EZtax
Tax is Included in Boolean used to inform whether the tax amount is included in the total amount,
Total Amount or not. This property is set to “true” when the tax status is set to “APPLIED” or
“FOR_INFO”

Tax Status Code Textual representation of the tax status.

“tsNoTax”: No tax was applied
“tsForInfo”: The computed tax information is given for information purpose
“tsApplied”: The tax was applied
“tsTaxExempted”: Tax exemption
“tsBuyerSubjectToPay”: The buyer is responsible for reversing the tax to the
tax authority
Deprecated values:
“tsTaxMissedForInfo”: Information is missing for the data related to the tax
“tsTaxMissedForApply”: The tax information was missing to apply the tax
“tsUnknown”: The tax status is unknown
Tax Status Identifier Numerical code of the tax status.
0: No tax was applied
1: The computed tax information is given for information purpose
2: The tax was applied
3: Tax exemption
4: The buyer is responsible for reversing the tax to the tax authority
Deprecated values:
-1: Information is missing for the data related to the tax
-2: The tax information was missing to apply the tax
-3: The tax status is unknown
Third Dispatch Code Dispatch code #3, which corresponds to the name of the property chosen as the
third criteria when filtering External Account transactions
Total Amount Total amount of the charged transaction, tax included. This amount is used by
(Including Tax) SAP CC to debit the balance of the concerned prepaid account, or charge the
concerned external postpaid account.
NOTE
The total amout equals to the base amount when the charge customized in a
charge plan (or in an offer) is configured to gross.
Triggering Contract Identifier of the provider contract which triggered the generation of the charged
Identifier item via an allowance. The value of this property depends on the type of trigger:
For a one-shot trigger or a recurring trigger, the value corresponds to the
identifier of the provider contract which owns the allowance
For an event-based trigger, the value corresponds to the identifier of the
provider contract which sent an event to the allowance
Triggering Contract External identifier of the provider contract item which sent an event to the
Item External allowance generating the billable items through an Event-Based Trigger
Identifier component. Otherwise, this property contains the external identifier of the
parent provider contract item of the allowance
Unrounded Rated Amount computed by the charges, having up to 6 decimal places before being
Amount rounded according to the TRANSACTION_PRECISION system parameter.
NOTE
This property is required for the tax framework but may not be used in the
charged item mapping.
User Service Identifier of the end customer related to the usage of the consumed service
Identifier

VAT Business Entity Boolean used to inform about the business category (B2B or B2C) of the
subscriber account relating to the charged account (prepaid or external
postpaid).
“true”, to inform the business category is B2B
“false”, to inform the business category is B2C
VAT Place of
Taxation
VAT Transaction Boolean used to inform whether prices computed during the execution of a
Gross Price Flag price plan are net, or gross.
“true”, for gross prices
“false”, for net prices
VAT Transaction Code of the tax rate level, that is configured in the charge customized in a
Rate Code charge plan (or in an offer) when the invoicing tax system is EU VAT.
“0”: Normal
“1”: Intermediary
“2”: Reduced
“3”: Super reduced
“4”: Zero
“5”: Special
“-1”: No tax
VAT Transaction Flat tax rate configured in the charge customized in a charge plan (or in an
Raw Rate offer), that is only available when the customized charge is configured to use the
“Flat” tax system
VAT Transaction Identifier of the flat tax rate as configured in the charge customized in a charge
Raw Rate ID plan or in an offer, that is only available when the customized charge is
configured to use the “Flat” tax system.
NOTE
Some properties can be used both in charge plans and allowance plans, while other properties
can only be used in charge plans or in allowance plans.
The following properties can only be used in allowance plans:

Allowance Event Class Name
Allowance Unique Identifier
Allowance Validity Start Date
Allowance Validity End Date
Triggering Contract Identifier
The following properties can be used in both charge plans and allowance plans:
Account Type Code
Account Type Name
Account Type is Prepaid
Chargeable Item Unique Identifier
Chargeable Item Unique Identifier Type
Charged Item or Refill Record Set Identifier
Charged Item or Refill Record Set Identifier Type
Charged Item or Refill Record Set identifier
Contract Identifier
Contract Type

Currency
End of Rating Recurring Period
Event Date
Event Processing Date
External Account Code
External Account Name
ISO Currency
Prepaid Account Name
Prepaid or External Account Code
Produced by an Allowance
Sender Job Identifier
Session Rating reservation Identifier
Start of Rating Recurring Period
Subscriber Account Code
The other properties can only be used in charge plans

(shared) Counters represent numeric variables that you can define and declare within a reusable
Counters charge, and reuse within other master data. SAP CC provides you with 2 types of counters:
Persistent counters, that are saved in the Core database
Transient counters, that are only stored in memory
If you want to share a counter between several items in a provider contract, you may need to
set up some specific configurations in the catalog of the service provider. By default, such a
shared counter is initialized with the zero value. If you want to design other initial values, you
must create a logic that will initialize the counter with the value of a parameter redefined in
each provider contract. To initialize such shared counters, you can:
Create and set up a dedicated charge plan containing a customized charge that includes a
recurring rate component charged at the start of the period
Create and set up a dedicated charge plan containing a customized charge that includes a
one-shot rate component triggered by an Activation event (at the creation of the related
contract item)
Configure the refill logic of an existing refill plan with a customized charge that includes a
recurring refill component
Configure the refill logic of an existing refill plan with a customized charge that includes a
one-shot refill component triggered by an Activation event (at the creation of the contract
item assocaited to this refill plan)c
Counter name Core Tool menu: Tools > Counter Dictionary > Edit
dictionary The counter name dictionary defines a set of counter names that can be used in other master
data such as charge plans or refill plans, when declaring counters
Monitoring Core Tool menu: File / New / Monitoring Plan
plan Monitoring plans represents the generation policy of spending statuses, that include:
A list of spending status identifiers
The counters to monitor
A list of rules used to determine the relevant labels
Refill item Core Tool menu: File / New / Refill Item Package
class Refill items are sent to SAP CC by network elements for refilling purpose. Each refill item
represents a set of properties used during the execution of a refill logic
Refill logic Core Tool menu: File / New / Refill Logic
Refill logic is used by SAP CC to manage refill operations related to the use of a customer
service. This master data can be customized at refill plan level

Refill plan Core Tool menu: File / New / Refill Plan

Refill plans are used to credit the prepaid accounts of customers. Each refill plan consists of:
A refill logic
A set of parameters used to configure the refill logic
A release status
Refill record Core Tool menu: File / New / Refill Record Class
class A refill record class represents a list of properties that must be included in each refill record
output by SAP CC during refilling operations
Spending Core Tool menu: File / New / Spending Status Description
status A spending status description represents a list of named labels that are used when modeling
description monitoring plans, each spending status being exposed to an external policy control or
monitoring system
Offer Core Tool menu: File / New / Offer
Offers are master data that belong to the old data model, and that represent set of charges
customers can subscribe to. SAP CC provides you with 2 types of offers:
Simple offers, that contain one or multiple charges
Complex offers, that contains one or multiple suboffers with the addition of zero, one or
multiple charges
NOTE
Master data related to the service provider are grouped within a pricing catalog that can be transported to another
landscape. For further information, refer to the “Catalog transport” dedicated section available in this
documentation.
Configuring master data for the customers of the service provider

To configure the master data related to the customers of the service provider, execute the following procedure:
1. Launch the Core Tool user interface and identify as a user granted the “CSR” role
2. Set up the relevant master data according to your needs, using the following information:
Master Data Description
Access Core Tool menu: File / New / Access
Accesses are used to grant end customers the access and use of services provided by the
service provider. Each access includes:
The technical identifier of the consumed service (Service ID)
The technical identifier under which an end customer consumes the service (User
Service ID)
Provider contract Core Tool menu: File / New / Provider Contract
Web Service: contractProvisioning
Provider contracts represent the business agreement between the service provider and
a given customer, taking into account some specific conditions. Each provider contract
refers to a unique subscriber account, and contains all the information that is necessary
to execute charging (or refilling) operations on this account.
NOTES
Necessary accesses are automatically created by SAP CC in background.

For development, test, or training purposes, you can manually create a provider
contract via the Core Tool user interface. In case of an integrated landscape with
the SAP CRM system, SAP SE recommends that you use the dedicated Web Service
to synchronize this master data with all the relevant systems.
If you installed the BART Server system within your landscape to manage batch
charging operations, you can modify the default policy related to batch rating
group assignment in order to fit your specific needs. For further information, refer
to the “Implementing the batch rating group assignment mechanism” dedicated
procedure afterwards.
Subscriber account Core Tool menu: File / New / Subscriber Account
Web Service: suacProvisioning
Subscriber accounts are used to store the information related to the account and
balance of each customer of the service provider.
NOTE
For development, test, or training purposes, you can manually create a subscriber
account via the Core Tool user interface. In case of an integrated landscape with the
SAP CRM system, SAP SE recommends that you use the dedicated Web Service to
synchronize this master data with all the relevant systems.
Subscriber mapping Core Tool menu: File / New / Subscriber Mapping Table
table Web Service: subscriberMappingTableManagement
Subscriber mapping tables are part of the subscriber accounts, and contain specific data
related to customers and represented as mapping tables.
NOTES
Subscriber mapping tables are not available in subscriptions.
A contract item can link several subscriber mapping tables.
A given subscriber mapping table can be reused within different contract items in
different provider contracts.
mapping table via the Core Tool user interface. In case of an integrated landscape
with the SAP CRM system, SAP SE recommends that you use the dedicated Web
Service to synchronize this master data with all the relevant systems.
Subscriber range Core Tool menu: File / New / Subscriber Range Table
table Web Service: subscriberRangeTableManagement
Subscriber range tables are part of the subscriber accounts, and contain specific data
related to customers and represented as range tables. This master data is particularly
recommended to design a pricing logic whose pricing is based on the customer data.
NOTES
Subscriber range tables are not available in subscriptions.
A contract item can link several subscriber range tables.
A given subscriber range table can be reused within different contract items in
different provider contracts.
range table via the Core Tool user interface. In case of an integrated landscape
with the SAP CRM system, SAP SE recommends that you use the dedicated Web
Service to synchronize this master data with all the relevant systems.
Subscription Core Tool menu: File / New / Subscription
Subscriptions represent the charging agreement conditions between the service
provider and a given customer, taking into account some specific conditions. Each
subscription can be:
Online, which means that they can be charged in real-time mode
Offline, which means that they can only be charged in batch mode
Hybrid, which means that they can be charged in both batch or real-time mode
according to the consumed service
Implementing the batch rating group assignment mechanism

When the BART Server is deployed in a landscape, the created provider contracts dedicated to offline charging
operations are by default balanced on the defined batch rating groups. In case this assignment policy does not fit
your business requirements, you can use the following procedure to modify this default behavior by developing a
Java class that implements your own assignment policy:
1. Develop your specific Java class by using the com.highdeal.batchgroup.contract package available in the
Core SDK and:
Implementing the IContractBatchRatingGroupAssignmentPolicy interface
Overriding the getBatchratingGroupAssignment(…) method
2. Create a JAR file containing this newly created single class, and copy this JAR file to the
exe/uc/<OS>/CC_CORE_SERVER/jars/ subfolder of the SP Central Repository, where <OS> correspond to
the operating system of the Core Server
2. Modify the value of the BATCH_RATING_GROUP_ASSIGNMENT_POLICY_CLASS system parameter for each
concerned updater instance, specifying the name of your own Java class that must be used when assigning batch
rating groups, using the following syntax: <package_name>.<class_name>
For further information about this system parameter, refer to its dedicated documentation available in the SAP
3. Update the startup configuration file of each concerned updater instance by adding the created JAR file to the
classpath. For further information, refer to the “Startup configuration file” dedicated procedure afterwards.
4. Restart the concerned instances of the Core Server system.
NOTE
To test that your modifications have been correctly taken into account, you can trigger the creation of a provider
contract from the SAP CRM system or from the Core Tool user interface and check the assigned batch rating group.
Notifications
Keywords

Notification group, notification policy, monitoring, alert
Preliminary notes
SAP CC Notification Reference documentation
“com.highdeal.notification” Java package and “NotifBook” API descriptions, available in the SAP CC Java/XML API
Description
For monitoring and alerting purposes, SAP Convergent Charging gives the possibility to generate notifications at
business and administrative levels. These notifications are organized into notification groups, and rely on a dedicated
framework you can integrate with your client application. You can use the following procedures to configure the
management of notifications within your SAP CC landscape and thus fit your specific needs:
Configuring the notification policy
Enabling the notification policy
Handling SAP CC notifications in your Java application
Available notifications
Notifications are organized into the following groups
ABM group, which contains the notifications triggered during the charging operations when:
The balance of a prepaid account or of a credit limit goes below a specified threshold
An alert has been configured in the price plan or charging plan of a charge that has been activated within a
provider contract or a subscription
A prepaid account has expired
Administrative group, which contains the notifications related to the connections between the different running
elements (instances, databases, and so on)
The following table contains the list of available notifications, including their belonging group:
Notification Group
ID Level Name, pretty name and description ABM Admin.
0 inform AMOUNT_ALERT (amountAlert)  
Sent when a prepaid account or a credit limit balance goes below the amount
threshold of the alert, this notification provides the following information:
The service provider of the subscriber account
The identifier of the subscriber account
The related balance type (prepaid or credit limit
The identifier of the balance for which an amount alert has been triggered
The current amount of the balance with its currency
The message of the alert as configured in the subscriber account
The amount threshold of the alert
These alerts are configured for each subscriber account by the external CRM or
the provisioning system during the customer data provisioning process (in an
integrated installation scenario).
1 inform EXPIRATION_ALERT (expirationAlert)  

Sent when the expiration alert of a prepaid account is triggered, this

notification provides the following information:
The identifier of the subscriber account
The identifier of the balance for which an amount alert has been triggered
The message of the alert as configured in the subscriber account
The state related to the alert
The date when the state change occurs
The period when the alert is triggered around the change date
These alerts are configured for each subscriber account by the external CRM or
the provisioning system during the customer data provisioning process (in an
integrated installation scenario).
2 inform INSTANCE_UP (instanceUp)  
The instance of the Core Server is running.
3 inform INSTANCE_DOWN (instanceDown)  
The instance of the Core Server has been manually stopped.
NOTE
This notification may not be sent in case of instance failure.
4 failure DB_LINK_DOWN (dbLinkDown)  
The instance of the Core Server has lost its connection with the database, due
to the following possible reasons:
The database is stopped (accidentally or voluntarily)
The network interface is down
The instance cannot contact the database host because of a network
problem (such as a firewall configuration)
NOTE
This notification is not sent when the instance cannot contact the database
because of a wrong configuration.
5 inform DB_LINK_UP (dbLinkUp)  
The instance of the Core Server has opened new database connections.
6 failure DB_FAILURE (dbFailure)  
The database returned a failure exception. See the “message” argument of the
notification for further details about the reason of the problem.
7 fatal OUT_OF_MEMORY (outOfMemory)  
The instance of the Core Server has been stopped because its JVM has thrown
an OutOfMemory exception.
NOTE
This notification may not be sent in case of insufficient JVM memory.

8 inform PNR_SCHEDULER_WAKESUP (pnrSchedulerWakesUp)  

The scheduler of the updater instance wakes up and starts a new activation
cycle.
9 inform PNR_SCHEDULER_SLEEPS (pnrSchedulerSleeps)  
The scheduler of the updater instance is sleeping and may be waiting for its
next activation cycle.
10 warn PNR_SCHEDULER_INTERRUPTED (pnrSchedulerInterrupted)  
The execution of the scheduler of the updater instance has been interrupted.
The environment of the instance prevents the scheduler to complete its cycle
(the activation failed, a problem occurred at memory level, and so on),
according to a reason available in the notification details.
11 security AUTHENTICATION_FAILURE (authenticationFailure)  
Sent when an XML message has been received without a valid authentication
(unknown login or wrong password), this notification provides the following
information:
The specified login (or “no login” when no login is specified)
The reason of the authentication failure (unknown login or wrong
password)
12 inform USER_ALERT (userAlert)  
Sent when a user defined alert is triggered, this notification provides the
following information:
The code that identifies the user alert
The message describing the user alert
The code of the subscriber account
A list of properties that gives additional information about the user alert
Use the Core Tool user interface to configure your own alerts by using the Alert
Triggering Operator in a reusable charge defined for the service provider.
13 inform RENEW_RESERVATION (renewReservation)  
For internal use only.
14 inform SPENDING_STATUS_REPORT (spendingStatusReport)  
For internal use only.
15 inform NO_ACCESS (noAccess)  
Sent when the No Access Function component is triggered, this notification
provides the following information:
The values of each property selected in the No Access Function component
The message defined in the No Access Function component
Configuring the notification policy

To fit specific needs, it is possible to define a notification policy that relies on an XML-formatted configuration file
which includes a sequence of notification publishers. Each notification publisher gives the possibility to filter a subset
of notifications that must be sent to a given output destination.
To filter notifications, you can use one of the following elements:
Element Sub element Attribute Description
filters all accept Optional attribute used to enable or disable all notifications
Possible values are: “true” or “false”
range lower Lower identifier of a range of notifications
upper Upper identifier of a range of notifications
set id Identifier of a notification
name pattern Regular expression that define the list of notifications
prettyName pattern Regular expression that defines the list of notifications
level lowerLevel Lower level of notifications to send
Possible values are: “quiet”, “inform”, “warn”, “security”, “alert”,
“failure” or “fatal”
nameFilter pattern Regular expression that defines the list of notifications to filter
according to their name
argumentFilter name Name of the argument available in the notification, that must be
used as a filter
pattern Regular expression that defines the value of the argument
EXAMPLES
Example 1: The following XML file defines a notification policy that filters the USER_ALERT and NO_ACCESS
notifications :
<notificationPolicy>
<filters>
<set id=”12”/>
<set id=”15”/>
</filters>
</notificationPolicy>
Example 2: The following XML file defines a notification policy that filters the notifications whose ID is in the range
[2,6], which means :
INSTANCE_UP
INSTANCE_DOWN
DB_LINK_UP
DB_LINK_DOWN
DB_FAILURE

<filters>
<range lower=”2” upper=”6”/>
</filters>

Example 3: The following XML file defines a notification policy that filters all notifications:
Containing a “sample” argument whose value is “value”
Containing a “sample2” argument whose value is “value2”

<sequence>
<argumentFilter name=”sample” pattern=”value” />
<argumentFilter name=”sample2” pattern=”value2” />
</sequence>
Once filters have been defined, it is then necessary to define output locations, that can be:
The network layer, used to publish notifications using the Packets over TCP/IP communication channel
JCo destinations, used to publish AMOUNT_ALERT and EXPIRATION_ALERT notifications to a JCo destination
Customer Management Areas, used to send notifications to the relevant SAP CRM or SAP ERP system according
to information available in the concerned subscriber account
The following table contains the possible elements that you can use to specify output locations:
Element Attribute Description
network groups This optional attribute gives the possibility to specify
a group containing a subset of notifications to send on
the network. When not specified, all previously
filtered notifications are sent.
Possible values are: “abm”, “admin” or “abm,admin”
JCo destination Name of the JCo destination defined in the system
function Name of the JCo function to use
multiJCoDestination selectedApplication SAP system to use for sending notifications
customerManagementAreaRouting selectedApplication SAP system to use for sending notifications
EXAMPLES
Example 1: The following XML files both define a notification policy that:
Filters the INSTANCE_UP and INSTANCE_DOWN notifications
Sends these notifications on the network

<filters>
<set id=”2” />
<set id=”3” />
</filters>
<network />

<sequence>
<nameFilter pattern=”INSTANCE_UP”>
<network />
</nameFilter>
<nameFilter pattern=”INSTANCE_DOWN”>
<network />
</nameFilter>
</sequence>
Example 2: The following XML files define a notification policy that:

Filters the AMOUNT_ALERT (whose property “sample” is set to “value”) and EXPIRATION_ALERT notifications
Sends AMOUNT_ALERT notifications on the network
Sends EXPIRATION_ALERT notifications:
On the network
To the “FCT” function of the “dest” JCo destination, writing possible errors into dedicated files according to
a given policy defined within a bulkWriter element

<sequence>
<nameFilter pattern=”AMOUNT_ALERT”>
<argumentFilter name=”sample” pattern=”value”>
<network />
</argumentFilter>
</nameFilter>
<nameFilter pattern=”EXPIRATION_ALERT”>
<sequence>
<JCo destination=”dest” function=”FCT”>
<bulkWriter
adminParameterPrefixName="NOTIF_WRITER"
rootPath="SAPCC_NOTIF/ERROR/Instance#@INSTANCE_ID@/@JCO_DESTINATION_NAME@"
channelCount="4"
timeBasedFileRolloverPolicy="HOURLY"
maxSizeBasedFileRolloverPolicy="1M"
deflate="false"
fileVersion="2"
fileSequenceId="NOTIF_WRITER_EXCEPTION"
/>
</JCo>
<network />
</sequence>
</nameFilter>
</sequence>

<nameFilter pattern=”AMOUNT_ALERT”>
<argumentFilter name=”sample” pattern=”value”>
<network />
</argumentFilter>
<nameFilter pattern=”EXPIRATION_ALERT”>
<sequence>
<JCo destination=”dest” function=”FCT”>
<bulkWriter
adminParameterPrefixName="NOTIF_WRITER"
rootPath="SAPCC_NOTIF/ERROR/Instance#@INSTANCE_ID@/@JCO_DESTINATION_NAME@"
channelCount="4"
timeBasedFileRolloverPolicy="HOURLY"
maxSizeBasedFileRolloverPolicy="1M"
deflate="false"

fileVersion="2"
fileSequenceId="NOTIF_WRITER_EXCEPTION"
/>
</JCo>
<network />
</sequence>
</nameFilter>
</nameFilter>
Enabling the notification policy

To enable your specific notification policy defined within an XML configuration file, execute the following procedure:
2. Execute the “notificationpolicy import” command, specifying the absolute path of the XML configuration file
containing your notification policy
Handling SAP CC notifications in your Java application

If you developed a Java client application within which you want to handle the notifications generated by your Core
Server system, you need to use the com.highdeal.notification package available in the Core SDK in order to:
Implement the NotificationHandler Java interface
Instantiate the NotificationServiceClient object
Implementing the NotificationHandler Java interface

As described in the SAP CC Java/XML API Reference documentation, the NotificationHandler interface always invokes
the handleNotification method that provides the following information:
systemName, that corresponds to the SID that contains the instance which sent the notification
instanceID, that corresponds to the identifier of the instance which sent the notification
timestamp, that corresponds to the date when the notification has been sent
uid, that corresponds to the unique identifier of the notification class
args, that corresponds to the arguments of the notification
To retrieve information related to an handled notification, consider the following sample code that you can adapt to
fit your business requirements:
public void handleNotification
(String sid, InstanceId iid, long timestamp, int uid, String... args) {
NotificationDescription desc = NotifBook.searchNotificationDescription(uid);
if (desc == null) {
// Should never occur
System.out.println("Unknown notification");
return;
}
String notifName = desc.getName();
String notifPrettyName = desc.getPrettyName();
NotificationLevel notifLevel = desc.getSeverityLevel();
String[] notifArgName = desc.getAdditionalInfoKeys();
...
CAUTION

The thread invoking the handler is the thread that listens to the socket. As a consequence, this thread must be
quickly freed to avoid loosing further notifications.
Implementing the NotificationServiceClient object

Once you implemented the NotificationHandler interface, it is necessary to perform the following operations within
you Java application:
Instantiate an InstanceMap object using the searchInstanceMap method of the
NotificationServiceClient class
Instantiate a NotificationServiceClient object and:
Initialize this object using the setNotificationHandler method
Prepare the connection to the relevant SAP CC system using the addAllConnections method
Connect this object to start receiving notifications from the relevant SAP CC system
To receive and handle notifications within your Java application, consider the following sample code that you can
adapt to fit your business requirements:
NotificationHandler handler = <YOUR_NOTIFICATIONHANDLER_IMPLEMENTATION>
InstanceMap map = NotificationServiceClient.searchInstanceMap(serverUrl, login, password);
client = new NotificationServiceClient();
client.setNotificationHandler(handler);
client.addAllConnections(map);
client.connect(null, 10000);
Startup configuration file
Keywords
startup, jstart, instance, JVM option, classpath, libpath
Preliminary notes
“Document Definitions section of the SAP CC Installation Guide documentation
This procedure uses the following variables:
<SYSTEM_ID>, which corresponds to the identifier of your system
<INSTANCE_NAME>, which corresponds to the name of the concerned instance
<HOSTNAME>, which corresponds to the name of the host containing the concerned instance
Description
The different instances of the Core Server system use startup configuration files to initiate their startup process.
These configuration files are stored in the SAP Profile Folder in the Central Repository of an SAP system. You can use
this procedure to configure the startup configuration file of each instance available within your SAP CC landscape
The following table contains the list of settings that can be configured within startup configuration files:
Settings Parameter Description

JVM Options .javaParameters This parameter includes all the JVM options used by the JRE to
execute an SAP CC Instance. For further information, refer to the
“Java Virtual Machine” section of this documentation.
Each option has the same prefix: "-D" or "-X"
Java class path of .classPath This parameter is used to specify all the specific Java classes that must
customized functions be loaded by the instance on startup.
Library path of .libPath This parameter is only relevant when the ".classPath" parameter is
customized functions modified and when the related Java classes require native libraries.
CAUTION
Do not modify other parameters.
Modifying a startup configuration file

To modify the startup configuration file of a given instance, execute the following procedure:
1. Edit the jstart.config file of the concerned instance, that is located in the following subdirectory of the SAP
Central Repository: profile/jstart/<SYSTEM_ID>_<INSTANCE_NAME>_<HOSTNAME>
3. Restart the concerned instance of the Core Server system
System and data auditing
Keywords
Auditing, recording, usage measurement, usage metric, change log, snapshot, user operation
Preliminary notes
“System and Data Auditing” section of the SAP CC Application Help documentation
“System and Data Auditing: Product Usage Measurement Settings” and “System and Data Auditing: Data and
Operation Auditing Settings” groups in the SAP CC System Parameters Reference documentation
“metriclist”, “purge_object_change_logs” and “purge_user_operations” commands of the SAP CC Admin+ User
Interface documentation
“Launching Admin+” and “Launching Core Tool” sections of the SAP CC Installation Guide documentation
“Installation of Diagnostics Agents” SAP Note 1365123 documentation
Description
For system control purpose, SAP Convergent Charging provides detailed information about the usage of the SAP CC
product and the tracking of modifications performed on master data and related user operations. You can use the
following procedures to configure the product usage measurement and master data auditing mechanisms available
within your SAP CC landscape and thus fit your specific needs.
Measuring product usage

In terms of product usage measurement, the SAP CC Core Server system gives the possibility to:

Record metrics dedicated to the business usage of the SAP CC product

Provide some customer usage information to SAP Solution Manager
Recording product usage metrics

SAP Convergent Charging is delivered with a set of metrics dedicated to the measurement of its business usage,
providing information such as:
The volume of master data configured within the system
The volume of transational data generated b ythe system during business operations
These metrics are recorder in the Core database by a dedicated scheduler whose execution depends on a policy you
can modify to fit specific needs. To modify the behavior of the scheduler in charge of recording metrics related to
business usage, execute the following procedure:
METRIC_RECORDING_SCHEDULER_ENABLED, which gives the possibility to enable or disable the scheduler
METRIC_RECORDING_DAY_TIME, which defines the time when the metrics are recorded
METRIC_RECORDING_TIME_WINDOW, which defines the retention period for recorded metrics. Once this
period is reached, the scheduler in charge of recording metrics deletes the recorded metrics that are older
than this period. As this scheduler is executed once a day, 1 day of recorded metrics are deleted at each
purge operation.
NOTE
The recorded business usage metrics can be browsed using the Core Tool user interface. For further information,
refer to its dedicated online help available in the SAP CC User Interfaces documentation.
Measuring customer usage in SAP Solution Manager

In an integrated scenario with SAP Solution Manager, SAP CC can communicate with the SAP SMD Agent to provide
information related to customer usage. The following procedures give the possibility to configure both SAP
Convergent Charging and SAP Solution Manager for customer usage measuring purpose.
Step 1: Configuring SAP CC for customer usage measurement

To communicate with SAP Solution Manager, SAP CC must fulfill the following requirements:
SAP Solution Manager must be installed within your landscape
SAP CC must be registered in SAP Solution Manager as a technical system. For further information, refer to the
“Managed Systems” section of the SAP Solution Manager documentation
An SMD Agent must be installed on each machine hosting a Core Server system. For further information, refer to
the dedicated SAP Note 1365123 documentation
Once these requirements are fulfilled, execute the following procedure:
1. Enable the scheduler in charge of recording metrics related to business usage. For further information, refer to
the “Recording product usage metrics” dedicated procedure described above
2. Launch the Core Tool user interface and and log in with an individual user granted the “User Administrator” role

3. Create a technical user named “SM_COLL_<SID>”, where <SID> corresponds to the SID of the concerned Core
Server system. This user must not be granted any role. The password of this used will be used afterwards when
configuring the SAP Solution Manager side
Step 2: Configuring SAP Solution Manager for customer usage measurement

To communicate with SAP CC, execute the following procedure:
1. Launch the SMD Agent Administration user interface and identify as an administrator
2. Click the “Application Configuration” tab
3. Select “Agent Applications” > “com.sap.smd.agent.application.global.configuration”
4. For each updater of the concerned Core Server system:
Fill the “Select scope” field with the name of the machine hosting the updater
Click the “Edit” button
Add the “<SID>/sapj2ee/com/user” property
Fill this property with the name of the “SM_COLL_<SID>” user created in Step 1
Add the “<SID>/sapj2ee/com/pwd” property
Fill this property with the password of the “SM_COLL_<SID>” user created in Step 1
Add the “<SID>/sapj2ee/msgserver/httpport” property
Fill this property with the HTTP port number of the updater
Auditing master data and user operations

In terms of master data and user operations audit, the SAP CC Core Server system gives the possibility to record the
operations that are executed by the SAP CC users, and the resulting modifications on the associated master data.
Recording user operations

SAP Convergent Charging gives the possibility to track and view some user operations executed by the SAP CC users
and performed on the SOAP over HTTP and XML over HTTP communication channels. Enabled by default with all
available domains activated, SAP SE recommends that you do not disable this User Operation Auditing feature
which enriches the auditing capabilities of your SAP Convergent Charging landscape.
CAUTION
This feature increases the volume of data that is stored in the USER_OPERATION table of the Core Database, which
may significantly impact the performance of the whole Core Server system. SAP SE recommends that you regularly
perform purge operations to optimally maintain your Core Server system. For further information about such purge
operations, refer to the “purge_user_operations” command of the Admin+ user interface.
To modify the behavior of the User Operation Auditing feature, execute the following procedure:
2. Modify the value of the following system parameters for each concerned instance:
AUDIT_DOMAIN, which gives the possibility to specify a subset of user operations domains to audit
AUDIT_ACTIVATION, which gives the possibility to enable or disable the recording of user operations

NOTE
Enabling the User Operation Auditing feature requires a restart of the concerned instances. Disabling the feature
does not necessary require a restart of the concerned instances, depending whether permanent and/or runtime
values are modified. If the runtime values are set to false, the feature is immediately disabled, but the pending
mass operations continue to be audited until they end.
Recording master data modifications

SAP Convergent Charging gives the possibility to track and view the changes that are performed on master data
evertytime is user operation is executed. Enabled by default, this Data Object Auditing feature cannot be
deactivated within your SAP Convergent Charging landscape.
To get additional details about the modifications made on master data, SAP Convergent Charging provides a Data
Object Snapshot feature that is enabled by default with all available domains activated and that gives the
possibility to record snapshots of the modified master data.
CAUTION
This feature increases the volume of data that is stored in the OBJECT_CHANGE_LOG, OBJECT_SNAPSHOT and
OBJECT_CHANGE_DATA tables of the Core Database, which may significantly impact the performance of the whole
Core Server system. SAP SE recommends that you regularly perform purge operations to optimally maintain your
Core Server system. For further information about such purge operations, refer to the “purge_object_change_logs”
command of the Admin+ user interface.
To modify the behavior of the Data Object Snapshot feature, execute the following procedure:
2. Modify the value of the following system parameters for each concerned instance:
AUDIT_OBJECT_DOMAIN, which gives the possibility to specify a subset of data domains to audit
AUDIT_OBJECT_ACTIVATION, which gives the possibility to enable or disable the recording of snapshots
NOTE
Enabling the Data Object Snapshot feature requires a restart of the concerned updaters. Disabling the feature does
not necessary require a restart of the concerned updaters, depending whether permanent and/or runtime values
are modified. If the runtime values are set to false, the feature is immediately disabled.
Thread dump files generation
Keywords
Thread dump, troubleshoot
May 2019 Public 100/150
Preliminary notes
“dump” command of the SAP CC Admin+ User Interface documentation
“Troubleshooting (Advanced): Thread Dump File Generation” group in the SAP CC System Parameters Reference
documentation
Description
In addition to logging and tracing capabilities, SAP Convergent Charging gives the possibility to generate thread
dump files, which contain information about the execution context of the different threads that are executed by the
instances of the Core Server system. In case a problem occurs during the execution of a business or technical
operation, or if the execution exceeds some defined thresholds, the related instance generates these dump files
automatically.
Mainly addressed to support specialists, the generation of these thread dump files can be configured in order to fit
specific needs mainly related to issue troubleshooting. You can use this procedure to configure the generation of
thread dump files within your SAP CC landscape and thus fit your specific needs.
The following table table contains the list of SAP CC system parameters you can use to configure the generation of
thread dump files:
THREAD_DUMP_ENABLED Enables/disables the generation of thread dump files
THREAD_DUMP_MINIMUM_INTERVAL Minimum time interval (in seconds) between the
generation of two thread dump files
THREAD_DUMP_OUTPUT_PATH Storage location of the thread dump files
THREAD_DUMP_RETENTION_PERIOD Retention period (in days) for thread dump files
THREAD_DUMP_THRESHOLD_CPU_TIME Threshold (in ms) relating to CPU time above which a
thread dump file must be generated
THREAD_DUMP_THRESHOLD_OUTPUT_ITEMS Threshold relating to the number of output items
generated by a thread above which a thread dump file
must be generated
THREAD_DUMP_THRESHOLD_RATING_CONTEXTS Threshold relating to the number of rating contexts used
by a thread above which a thread dump file must be
generated
THREAD_DUMP_THRESHOLD_SQL_TIME Threshold (in ms) relating to the duration of an SQL query
executed within a thread above which a thread dump file
must be generated
THREAD_DUMP_TRIGGER_PERIOD Period (in seconds) used by the scheduled trigger after
which a thread dump file must be generated
Modifying the generation of thread dump files

To modify the configuration of the thread dump files mechanism, execute the following procedure:
2. For each concerned rater, modify the value of the THREAD_DUMP_ENABLED system parameter in order to
enable or disable the generation of thread dump files
May 2019 Public 101/150
3. For each concerned instance, modify the value of the other available system parameters according to your needs
Keywords
SLD, payload
Preliminary notes
“Update of SAP System Component Repository in SLD” SAP Note 669669 documentation
Description
The Core Server system can be integrated with third-party applications. You can use the following procedure to
configure the settings related to the integration with the SAP System Landscape Directory system.
Modifying the SAP SLD connection settings

To send payload information to the SAP SLD system, it is necessary to configure some settings related to the
integration with third-party systems. To modify this configuration, execute the following procedure:
2. For each dispatcher instance, modify the values of the following system parameters:
SLD_URL, which corresponds to the URL of the SLD Data Supplier Service in the SAP SLD system, that must
respect the following format: http://<SLD_HOST>:<SLD_PORT>/sld/ds
SLD_USER, which gives the possibility to specify the name (or identifier) of the SAP SLD user that must be
used by the Core Server system to log on the SAP SLD system
SLD_PASSWORD, which corresponds to the password of the specified SAP SLD user
SLD_SCHEDULER_ENABLED, which gives the possibility to enable or disable the scheduler in charge of
sending information to the SAP SLD system
SLD_SCHEDULER_RECURRENCE, which gives the possibility to modify the recurrence of the scheduler,
configured by default to send information to the SAP SLD system every day at 1:00 AM
Users management
Keywords
User, password, security policy, user isolation, user session, concurrent edition, role, right
Preliminary notes
“User Administration and Authentication” section of the SAP CC Security Guide documentation
“User Session Management” section of the SAP CC Application Help documentation
“Launching Admin+” and “Launching Core Tool” sections of the SAP CC Installation Guide documentation
May 2019 Public 102/150

“Security Management Settings” and “User Management Settings” groups in the SAP CC System Parameters
“About users” section of the SAP CC Core Tool User Interfaces documentation
“list_clients”, “disconnect_client”, “purge_object_change_logs” and “purge_user_operations” commands of the
SAP CC Admin+ User Interface documentation
Description
SAP Convergent Charging provides proprietary mechanisms to manage users and associated concepts such as
password policy, user roles, working sessions, and so on. You can use the following procedures to configure the
management of users within your SAP CC landscape and thus fit your specific needs:
Separating service and individual users
Security policy for user passwords
Managing working sessions within user interfaces
Creating users
Resetting the emergency user
Separating service and individual users

SAP Convergent Charging defines 2 types of users:
Individual users, whose passwords are encrypted and must be regularly changed
Service users, whose passwords are less secured (for performance reasons) and never expire
Each type of user is associated to security profiles containing access rights to each communication channel. To
enable or disable the isolation between individual users and service users, execute the following procedure:
2. For each concerned updater, modify the value of the USER_ISOLATION_ENABLED system parameter in order to
enable or disable the isolation of users
Security policy for user passwords

Every user defined in your SAP CC landscape is protected by a password whose securing policy can be configured to
fit specific needs. To enable or disable the Password Management Policy, execute the following procedure:
2. For each concerned updater, modify the value of the PASSWORD_MANAGEMENT_ENABLED system parameter
in order to enable or disable the password management policy
When the Password Management Policy is enabled, SAP CC also gives the possibility to modify the following options
that make up this securing policy:
Policy option Description
Mandatory Determines whether passwords are mandatory or not.
This option is always enabled, and cannot be modified
Different from login Determines whether passwords must be different from login.
This option is always enabled, and cannot be modified. As a consequence, a given
password cannot be similar to the associated login
May 2019 Public 103/150

Minimum length The PASSWORD_MANAGEMENT_MINIMUM_LENGTH system parameter specifies

the minimum length for passwords. Setting this system parameter to 0 means that
no minimum length is required for passwords
Complexity The PASSWORD_MANAGEMENT_COMPLEXITY system parameter specifies the
complexity rules that passwords must respect
Maximum duration The PASSWORD_MANAGEMENT_EXPIRATION_DELAY system parameter specifies
the number of days after which the password of an individual user expires and must
be changed. Setting this system parameter to 0 means that passwords never expire
Maximum idle duration The PASSWORD_MANAGEMENT_MAX_IDLE_DELAY system parameter specifies the
maximum number of days until which a user must logon before being automatically
locked. Setting this system parameter to 0 means that users are not locked even if
they never logon
Reuse cycle The PASSWORD_MANAGEMENT_REUSE_CYCLE system parameter specifies the
number of different values that must be used for password before reusing a given
value. Setting this system parameter to 0 means that there is no limit regarding the
reuse of passwords
Reuse delay The PASSWORD_MANAGEMENT_REUSE_DELAY system parameter specifies the
number of days until which a previously used password can be reused. Setting this
system parameter to 0 means that previously used passwords can be reused
Modification interval The PASSWORD_MANAGEMENT_CHANGE_DELAY system parameter specifies the
minium number of days between 2 password modifications. Setting this system
parameter to 0 means that passwords can be changed whenever you want
Failed login attempts The PASSWORD_MANAGEMENT_FAIL_LIMIT system parameter specifies the
number of successive failed logon attempts until which the user is automatically
locked. Setting this system parameter to 0 means that logon attempts are not
limited
SHA-256 hash rounds Gives the possibility to configure the complexity of encryption applied to passwords
by specifying the number of steps of the algorithm that is applied to hash passwords
before storing them in the Core database.
The PASSWORD_HASH_ROUNDS_FOR_INDIVIDUAL_USERS and
PASSWORD_HASH_ROUNDS_FOR_SERVICE_USERS system parameters specify the
number of hash rounds applied to password hashing for respectively individual users
and service users.
CAUTION
This number of steps has a performance impact on communications with SAP CC,
during which passwords are hashed using the same number of steps as the number
used for storing passwords in the database. By default, this number of steps is set
to 10000 for both individual and service users. This value ensures a good
protection for passwords of individual users, but increase the latency on web
services and HCI by 10 milliseconds approximately. To reduce this performance
impact, SAP SE recommends using a lower value for service users such as 1000
rounds or 100 rounds:
For 1000 rounds, the latency is expected to increase of 1 ms approximately
For 100 rounds, the increase of latency is non-measurable
NOTE
May 2019 Public 104/150

Changing the value of these parameters is not taken into account immediately. It
only affects the users when their password is modified.
To modify the Password Management Policy, execute the following procedure:

2. For each concerned updater, modify the value of the system parameters that correspond to the policy options
you need to modify. For further information about the concerned system parameters, refer to their dedicated
documentation available in the SAP CC System Parameters Reference documentation
Managing working sessions within user interfaces

Working sessions within the Core Tool and BART Tool user interfaces can be controlled in terms of:
Concurrent edition within the Core Tool, used to prevent multiple users working on the same master data
Multiple accesses to a given user interface by a given individual user
Security regarding inactivity between the user interface and the Core Server
To enable or disable the management of working session within user interfaces, execute the following procedure:
2. For each concerned updater, modify the value of the USER_SESSION_ENABLED system parameter in order to
enable or disable the management of user sessions. For further information about this system parameter, refer
to its dedicated documentation available in the SAP CC System Parameters Reference documentation
When the management of working sessions is enabled, SAP CC also gives the possibility to modify the following
options that make up this management policy:
Policy option Description
Simultaneous The USER_SESSION_SESSION_LIMIT_PER_USER_AND_TOOL system parameter specifies the
connections maximum number of simultaneous connections that a given user can make on a given GUI.
When this limit is reached, further connections are refused. Setting this system parameter
to 0 means that a given user can connect as many times as he wants to a given GUI
Inactivity period The USER_SESSION_VALIDITY_PERIOD system parameter specifies the maximum period
during which a working session can be left inactive, which means that there is no interaction
between the GUI and Core Server. Setting this system parameter to 0 means that user
sessions never expire
NOTE
In case of user session failure, you can use the “delete_user_session” command of the Admin+ user interface.
When a session is deleted, the objects opened in “edition” mode during this working session are released and can
be modified within another session.
To modify the management policy for working sessions, execute the following procedure:
May 2019 Public 105/150

2. For each concerned updater, modify the value of the system parameters that correspond to the policy options
you need to modify. For further information about the concerned system parameters, refer to their dedicated
documentation available in the SAP CC System Parameters Reference documentation
Creating users
Both individual users and service users defined in SAP Convergent Charging are:
Protected by a password that respects a security policy you can configure to fit specific needs. For further
information, refer to the “Security policy for user passwords” dedicated section above
Assigned to roles that represent access rights to sets of master data domains
To create users within your SAP Convergent Charging landscape, execute the following procedure:
1. Launch the Core Tool user interface and identify as the administrator of the Core Server system or as a user
granted the “User Administrator” role
2. Create the relevant users, assigning them the adequate roles
Resetting the emergency user

In case you created users in a incorrect way that avoids you to log on to any SAP CC user interface, you can reset the
emergency user. This user corresponds to the first super administrator user created at installation time, with whom
you will be able to log on again and perform adequate modifications. For further information, refer to the “Resetting
the Emergency User” dedicated SAP Note 1890952.
Configuring the BART Server system
Acquisition sessions and consolidation
Keywords
CDR, acquisition session, consolidation cache
Preliminary notes
“Chargeable Items Acquisition” section of the SAP CC Application Help documentation
“Chargeable Items Consolidation Process” section of the SAP CC Application Help documentation
Description
As described in the Application Help documentation, the BART Server system provides acquisition and consolidation
features for incoming CDRs, that you can configure using the following procedure.
Modifying the acquisition and consolidation settings

To configure the acquisition and consolidation operations performed by the BART Server system, refer to the
“Modifying the BART Server configuration file” section above and modify the following settings of the BART Server:
May 2019 Public 106/150

acquisition.session.max.number, that gives the possibility to specify the maximum number of simultaneous
acquisition sessions that can run at a given time
acquisition.session.monitoring.period, that corresponds to the period between 2 generations of “acquisition
session status” events. For further information, refer to the “Monitoring and event broadcasting” dedicated
section above
consolidation.cache.enable, that gives the possibility to enable or disable the consolidation cache used to
temporary store additional information related to CDRs
consolidation.cache.size, that corresponds to the size of the consolidation cache
Acquiring CDRs with the Java API

Network elements or applications can send CDRs to the BART Server system and manage the related acquisition
sessions. The BART Server then acquires these incoming CDRs, and sends them as chargeable items to the Core
Server system. You can develop your own application using the Java APIs available in the BART Software
Development Kit (SDK) and:
Implementing the CDRServiceClient Java class of the com.highdeal.bart.message Java package, in case
of communications performed via the Packets over TCP/IP communication channel
Implementing the Java classes of the com.highdeal.bart.hci Java package, in case of communications
performed via the XML over HTTP communication channel (HTTP Communication Interface)
For further information, refer to the “com.highdeal.bart.message” and “com.highdeal.bart.hci” Java packages
descriptions available in the SAP CC Java/XML API Reference (BART Library) documentation, that also include the
documentation of the concerned XSD fragments.
EXAMPLE 1
The following Java snippet defines a client application that communicates using the Packets over TCP/IP
communication channel for handling incoming CDRs :
CDRServiceClient collector;
try { collector = new CDRServiceClient("BART_HOST",2009); }
catch (Exception e) {
System.out.println("Cannot initialize BART Collector client -> "+e);
e.printStackTrace();
}
// Building up the acquisition session

AcquisitionSessionModel session = new AcquisitionSessionModel(...)
try {session = collector.startAcquisitionSession(session);}
catch (InvalidAcquisitionException e) {System.out.println("InvalidAcquisitionException -> "+e);}
catch (ServerUnavailableException e) {System.out.println("OperationFailureException -> "+e);}
catch (CommunicationFailureException e) {System.out.println("OperationFailureException -> "+e);}
catch (Throwable t) {System.out.println("Throwable -> "+t); }
System.out.println("StartAcquisition() completed");
// Building up some CDRs

Vector cdrs = new Vector();
cdrs.add(new CDRModel(...)
try {result = collector.acquireCDR(cdrs, session);}
catch (InvalidCDRException e) {System.out.println("InvalidCDRException -> "+e);}
catch (Throwable t) {System.out.println("Throwable -> "+t);}
try {session = collector.stopAcquisitionSession(session);}

May 2019 Public 107/150

catch (Throwable t) {System.out.println("Throwable -> "+t);}

System.out.println("StopAcquisition() completed");
EXAMPLE 2
The following Java snippet defines a client application that communicates using the XML over HTTP communication
channel for handling incoming CDRs :
HttpMessageSender sender = ....

StartAcquisitionSessionOp op = new StartAcquisitionSessionOp();
String description = "Test snippet";
String source = "BART Reference";
AcquisitionSessionModel session =
new AcquisitionSessionModel(source, description,
AcquisitionSessionModel.ACQUIRE_AND_DEDUPLICATE_MODE);
op.setAcquisitionSession(session);
MessageOriginator originator = new MessageOriginator();

// Setting the name and password of a user granted the right to create a session in the BART Server
originator.setName("USER");
originator.setAuthentication(new SimpleMessageAuthentication("PASSWORD"));
MessageHeader header = new MessageHeader();

header.setOriginator(originator);
MessageBody body = new MessageBody();

body.addOperation(op);
MessageEnvelope envelope = new MessageEnvelope();

envelope.setBody(body);
envelope.setHeader(header);
try {
MessageEnvelope result = sender.send(envelope);
StartAcquisitionSessionResult opRes =
(StartAcquisitionSessionResult)result.getBody().getResult(0);
session = opRes.getAcquisitionSession();
}
catch (CommunicationFailureException e) {System.out.println("CommunicationFailureException: "+e);}
catch (OperationFailureException e) {System.out.println("OperationFailureException -> "+e);}
System.out.println("StartAcquisition() completed");
Acquiring CDRs with an IEC

An IEC (Import/Export Connector) application can send CDRs to the BART Server system and manage the related
acquisition sessions. The BART Server then acquires these CDRs, and sends them as chargeable items to the Core
Server system. You can customize this IEC application using some Java tasks that will apply to the concerned data.
For further information, refer to the “About Scenario” section of the CAT Tool online help available in the SAP CC
User Interfaces documentation.
BART Server configuration file
Keywords
bart.config
Preliminary notes
May 2019 Public 108/150


Description
As described in the Installation Guide documentation, the configuration of the BART Server system is located in the
bart.config file:
That is available in the config folder of the BART Server instance
Whose content is grouped upon the following sections:
Database connectivity
Logs and traces
Connection to the Core Server system
Connection to the BART Server system
Business operations settings
You can use this procedure to configure the different settings of the BART Server configuration and thus fit your
specific needs.
The following table contains the list of settings that can be configured within the configuration file of the BART
Server system. For further information about the possible values of each parameter, refer to the documentation
available within the bart.config file itself:
Settings Description BART Server option

Database connectivity
Connection JDBC URI of the BART database db.sqlhelper_jdbc_uri
Name of the BART database user db.sqlhelper_login
Password of the BART database user db.sqlhelper_password
CSV list of additional properties for SQL db.sqlhelper_jdbc_properties
connections
Number of database connections to open db.sqlhelper_connection_count
Retry policy Maximum number of request retries db.sqlhelper_max_redo
Duration (in seconds) between 2 db.sqlhelper_reconnect_interval
reconnection attempts
Maximum number of reconnection db.sqlhelper_reconnect_attempts
attempts
Technical settings Size of the statement cache db.sqlhelper_statement_cache_size
Unique ID for batch reservation db.sqlhelper_id_interval
Logs and traces
Logs Severity threshold for logs ls.app.severity
(business processing) Identifier(s) of the destination(s) ls.app.destination
Logs Severity threshold for logs ls.sys.severity
(system processing) Identifier(s) of the destination(s) ls.sys.destination
Traces Severity threshold for traces ls.trc.severity
Identifier(s) of the destination(s) ls.trc.destination
Domain(s) for traces ls.trc.domain
May 2019 Public 109/150

Console Destination Enable/Disable ld.console.enabled

Output format ld.console.formatter
Fileset Destination #1 Enable/Disable ld.file1.enabled
Output format ld.file1.formatter
Number of files available for the rotation ld.file1.setsize
Maximum file size before rotation ld.file1.size
File path, name, and extension ld.file1.name
Connection to the Core Server system
Connection CSV list of dispatchers to contact cc.dispatcher.boot.http.url.list
Name of the technical user used to cc.login
connect to the Core Server system
Password of the specified technical user cc.password
Connection to the SAP URL of the targeted SAP SLD system bart.sld.url
SLD system (SAP SLD) Name of the SAP SLD user bart.sld.user
Password of the SAP SLD user bart.sld.password
Business settings
Acquisition Maximum number of parallel acquisition acquisition.session.max.number
sessions
Polling period (in milliseconds) for acquisition.session.monitoring.period
generating events
May 2019 Public 110/150

Rerating Number of threads used for rerating rerating.pool.size

operations, each subscription being
rerated by a dedicated thread
Maximum number of rerating requests rerating.queue.size
that can be queued when rerating
subscriptions
Specifies whether CDRs to select for rerating.limited_to_rated_status
rerating purpose must have the
STATUS_RATED status, or not
Maximum number of subscriptions (by rerating.max_number_subscriptions
batch rating group) that can be rerated as
the same time within a rerating session
Rating and charging Maximum number of parallel rating rating.session.max.number
sessions
Polling period (in milliseconds) for rating.session.monitoring.period
generating events
Maximum number of concurrent threads rating.session.threads
for each rating session
Size of the CDR commit block rating.cdr.commit.block
Specifies whether the batch charge API rating.cdr.batch_charge
must be used, or not
Maximum number of CDRs in a given rating.cdr.charge.block
batch charge operation
Name of a specific property to add in the rating.cdr.rating_date.property_name
chargeable item during rating operations
and containing the rating date
Name of a specific property to add in the rating.cdr.unique_id.property_name
chargeable item during rating operations
and containing a unique identifier
Source of the unique identifier to add in rating.cdr.unique_id.source
the chargeable item during rating
operations
Specifies whether CDRs must be rerating.consolidate.before.rating
consolidated before being rated
Specifies whether CDRs selected from the rating.bench_mode
BART database must be rated, or simply
used for benchmarking purpose
Absolute path of the file used to store sql.failures.log.file.name
CDRs that have been rated but not
committed due to a database failure
Enables/disables the cached structure cache.consolidation.enable
used for consolidation operations
Size of the cached structure used for cache.consolidation.size
consolidation operations
Job management Maximum number of running jobs scheduler.job.pool.size
Polling period (in milliseconds) for scheduler.job.monitoring.period
generating events
May 2019 Public 111/150

Bulk operations Number of threads that can bart.bulk.threads

simultaneously handle requests
concerning bulk operations
Number of objects to select within the bart.bulk.searchFetchSize
BART database for each transaction
Number of objects modified by each bart.bulk.modificationFetchSize
commit for each database transaction
Technical settings
XML validation Enables/disables the validation of the bart.xml_schema_validation
XML schema
Report handling Number of report handlers report.handler.number
Java class name of the handler report.handler.<n>.classname
Absolute path of the configuration file to report.handler.<n>.properties
use when instantiating the report handler
List of topics (separated by “;”) the report report.handler.<n>.topics
handler must subscribe to
Magic number Enables/disables the deduplication magic_number.database_deduplicate
computation operations of CDRs within the BART
database
Number of magic numbers to use magic_number.number
Name of the CDR to which the magic magic_number.<n>.item_name
number <n> should be associated
List of fields that must be concatenated magic_number.<n>.fields
to build the magic number
Monitoring Enables/disables the monitoring bart.monitoring
capabilities of the BART Server
Maximum number of monitoring listeners bart.monitoring.clients.max.number
Modifying the BART Server configuration file

To modify the configuration file of the BART Server system, execute the following procedure:
1. Edit the “bart.config” file, that is located in the config folder of the BART Server instance
4. Restart the BART Server system
Communication channels
Keywords
Communication channels, SQL failure, securing, SLD
Preliminary notes
“Securing a landscape” and “Launching Admin+” sections of the SAP CC Installation Guide documentation
May 2019 Public 112/150

Description
Communications with the BART Server system rely on different communication channels whose use depend on the
concerned elements. You can use the following procedures to configure the settings related to communication
channels and thus fit your specific needs or performance requirements:
Modifying the Core Server connection settings
Modifying the communication settings for acquisition and rerating operations

To communicate with the BART database, refer to the “Modifying the BART Server configuration file” section above
and modify the following settings of the BART Server:
logon, that corresponds to the name of the BART database user
password, that corresponds to the password of the specified user
database URI, that corresponds to the URI of the BART database
sql.failures.log.file.name, that corresponds to the absolute path of the file used to store information related to
non-committed CDR modifications in case of BART database failure. This SQL failure file is used on startup by the
BART Server to commit these non-committed CDRs
Modifying the Core Server connection settings

To communicate with the Core Server system, refer to the “Modifying the BART Server configuration file” section
above and modify the following settings of the BART Server:
cc.login, that corresponds to the name of the technical user used to connect to the Core Server system
cc.password, that corresponds to the password of the specified technical user
cc.dispatcher.boot.http.url.list, that corresponds to a CSV list of URLs (including port number) relating to
dispatcher instances.
NOTES
Use HTTPs URLs in case of secured communications
When the security is activated, the BART Server system cyphers the passwords specified in the bart.config
configuration file
Modifying the communication settings for acquisition and rerating operations

To perform acquisition and recharging operations using the BART Server system, it is necessary to configure some
settings related to communications performed over the Packets over TCP/IP communication channel. To modify this
configuration, refer to the “Modifying the BART Server configuration file” section above and modify the following
settings of the BART Server:
bart.collector.server.hostname, that corresponds to the IP address or name of the machine hosting the BART
Server system
bart.collector.server.port, that corresponds to the port number of the BART Server collector service
bart.collector.server.threads, that corresponds to the number of threads that can simultaneously handle
requests concerning the collector service of the BART Server
rerating.pool.size, that corresponds to the size of the pool dedicated to rerating requests
rerating.queue.size, that corresponds to the number of rerating requests handled by the rerating service
May 2019 Public 113/150

For security purposes, communication channels used to communicate with the BART Server system can be secured.
For further information about the available securing procedures, refer to the dedicated “Securing a landscape”
section of the SAP CC Installation Guide documentation.
Keywords
Preliminary notes
Description
Java Runtime Environment. The BART Server system is a Java process whose execution can be configured to fit
specific requirements. To determine and modify the different JVM options for the BART Server system, refer to the
“Java Virtual Machine” procedure available for the instances of the Core Server system, and apply the relevant
modifications on the startup file of the BART Server system.
Logging and tracing
Keywords
Log, trace, category, severity, domain, threshold, troubleshoot
Preliminary notes
“Launching Bart+” section of the SAP CC Installation Guide documentation
“Troubleshooting: Logs and Traces” group in the SAP CC System Parameters Reference documentation
Description
and so on. You can use this procedure to configure the logging and tracing capabilities of your BART Server system
May 2019 Public 114/150

Logging and tracing features of the BART Server system can be configured to fit specific needs. By default, logging
and tracing features are configured to fit a productive landscape, which corresponds to the following configuration:
The logging feature is enabled, with severity thresholds set to INFO
The tracing feature is enabled, with severity thresholds set to ERROR
Log and trace messages are generated in different files, that are available in SAP MC or SAP MMC applications
Generated files are stored both in the console and in the “log” directory of the BART Server system
File rotation is enabled
Modifying the logging and tracing policy

To fit specific needs, you can modify the default configuration of the logging and tracing features. According to the
modifications, you can perform:
Immediate modifications, that are temporary and that can only be performed using the “set” command of the
Bart+ user interface. For further information, refer to its dedicated online help available in the SAP CC User
Interfaces documentation
Deferred modifications, that consist in modifying the BART Server configuration file as described in the
“Modifying the BART Server configuration file” dedicated section
Magic Number Pattern
Keywords
Magic number, deduplicate
Description
To identify and tag duplicated CDRs, the BART Server system manages sequences of magic numbers that are used to
uniquely identify a CDR within the BART database. Each magic number can be made up with the following
information:
The CDR name
The consumption date, that represents the usage date of the customer service
The user identifier (USID), that represents the technical identifier of the end customer
The service identifier (SID), that represents the technical identifier of the customer service
And all the other data, such as call duration, callee, caller, usage type, service type, and so on… whose
availability depends on your business requirements
You can use this procedure to define the pattern for magic numbers used by the BART Server system for each type of
CDR, and thus fit your specific needs.
Setting up a pattern for magic numbers

To set up a pattern for magic numbers used during deduplicating operations, refer to the “Modifying the BART
Server configuration file” section above and modify the following settings of the BART Server:
magic_number.database_deduplicate, that gives the possibility to enable or disable the CDR deduplication
feature provided by the BART Server system
magic_number.number, that corresponds to the number of magic number patterns to use, which shall be
similar to the number of CDR types
May 2019 Public 115/150

magic_number.<n>.item_name, that corresponds to the name of the CDR to which the magic number pattern is
associated
magic_number.<n>.fields, that corresponds to the list of fields that must be concatenated to build the magic
number, each field corresponding to:
A standard property of the associated CDR
An additional information available in the associated CDR, that is prefixed by the “item.” string
EXAMPLE
Considering a CDR named “SAMPLE_CDR” containing:
The “consumption_date”, “user_id” and “service_id” standard properties
The “ZZ_USAGE_TYPE” and “ZZ_SERVICE_TYPE” additional information, that are used during batch
charging operations to price the usage of the customer service
You can then define the following magic number pattern using the following configuration:
magic_number.database_deduplicate=true
magic_number.number=1
magic_number.1.item_name=SAMPLE_CDR
magic_number.1.fields=consumption_date;user_id;service_id;item.ZZ_USAGE_TYPE;item.
ZZ_SERVICE_TYPE
Monitoring and event broadcasting
Keywords
Monitoring, event, broadcasting, report file handler, UDP
Preliminary notes
“Chargeable Items Acquisition” and “Chargeable Items Rerating” features descriptions, available in the SAP CC
Description
The BART Server system can broadcast events through XML messages that are generated according to a defined
frequency on the network. The following table contains the list of supported events:
Topic Event Description
Acquisition Acquisition This event is triggered each time a new acquisition session is started
session start through the mediation chain. This event mainly contains the definition of
the session being created
Acquisition This event is triggered at a regular frequency (depending on the BART
session status Server settings) and describes the elapsed time of the session, the
number of newly acquired CDRs and the number of duplicated CDRs
Acquisition This event is triggered each time an acquisition session is complete, and
session stop contains the total duration of the session, the number of acquired CDRs
and the number of duplicated CDRs. When this event is triggered, a
report file is generated, containing details about the acquisition session
May 2019 Public 116/150

Rating Rating session This event is triggered each time a new rating session is started. This
start event mainly contains the definition of the session being created
Rating session This event is triggered at a regular frequency (depending on the BART
status Server settings) and describes the elapsed time of the session, the
number of rated CDRs and the number of erroneous CDRs
Rating session This event is triggered each time a rating session is complete, and
stop contains the total duration of the session, the number of rated CDRs and
the number of erroneous CDRs. When this event is triggered, a report file
is generated, containing details about the rating session
Job execution Job start This event is triggered each time a job execution is started. This event
mainly contains the definition of the job being started
Job status This event is triggered at a regular frequency (depending on the BART
Server settings) and describes the elapsed time of the job execution
Job stop This event is triggered each time a job execution is complete. It contains
the total duration of the job execution
Mainly addressed to administrators and support specialists, the generation of these events can be configured in
order to fit specific needs such as landscape monitoring. You can use this procedure to configure the monitoring and
event broadcasting capabilities of your BART Server system and thus fit your specific needs.
Modifying the monitoring settings

To adapt the BART Server system to specific monitoring needs, refer to the “Modifying the BART Server
configuration file” section above and modify the following settings of the BART Server:
bart.monitoring, that gives the possibility to enable or disable the monitoring capabilities of BART Server
bart.monitoring.clients.max.number, that corresponds to the maximum number of monitoring listeners
acquisition.session.monitoring.period, that corresponds to the period between 2 generations of “acquisition
session status” events described above
rating.session.monitoring.period, that corresponds to the period between 2 generations of “rating session
status” events described above
scheduler.job.monitoring.period, that corresponds to the period between 2 generations of “job status” events
described above
scheduler.job.pool.size, that gives the possibility to specify the maximum number of jobs that can be active at a
given time
Modifying the report file settings

Everytime a stop event relating to acquisition or rating session is triggered, the BART Server system generates a
report file containing detailed information of the completed session.
EXAMPLES
The following file represents a report related to an acquisition session:
CREATION DATE = Tue Nov 15 21:34:10 CET 2005
ACQUISITION DATE = 2005-11-15 21:34:10.717
ACQUISITION DURATION = 24 sec
ACQUISITION SOURCE = location_with_CDRs\source.txt
ACQUISITION DESCRIPTION = Sample acquisition
ACQUISITION MODE= Acquisition and de-duplicate mode
NB CDR ACQUIRED = 961
May 2019 Public 117/150

NB CDR DUPLICATE= 39
NB CDR CONSOLIDATE = 950
STATUS= ended
The following file represents a report related to an rating session:
CREATION DATE = Tue Nov 29 17:53:32 CET 2005
RATING START DATE = 2005-11-29 17:53:32.303
RATING DURATION = 2 sec
RATING MAX CONSUMPTION DATE = 2005-11-29 17:53:32.287
RATING DESCRIPTION = null
RATING MODE= most mode
NB CDR RATED = 100
NB CDR IN ERROR= 0
STATUS= cleaned
The generation of report files relies on dedicated handlers in charge of listening to the adequate stop events. To
configure this report file handling mechanism, refer to the “Modifying the BART Server configuration file” section
above and modify the following settings of the BART Server:
report.handler.number, that gives the possibility to specify a number of file report handlers. Setting this
parameter to 0 disables the reporting capabilities of BART Server
report.handler.<n>.classname, that corresponds to the name of the Java class implementing the Event Handler
Framework which describes how the events are handled
report.handler.<n>.properties, that corresponds to the absolute path of the configuration file to use when
instantiating the report handler
report.handler.<n>.topics, that corresponds to the list of topics (separated by “;”) the handler must subscribe
to, considering the following possible topics: acquisition, rating and job
Once report handlers have been configured, you need to modify the configuration files specified in the
“report.handler.<n>.properties” settings accordingly, using the execute the following procedure:
1. Edit the relevant configuration file, or create a copy from the default “report.config” file that is located in the
config folder of the BART Server instance
2. Modify the following settings according to your needs:
folder, that corresponds to the absolute path of the folder containing the generated files
filename, which gives the possibility to specify a prefix for the names of the generated files
fileSuffix, which gives the possibility to specify a suffix for the names of the generated files
NOTE
The configuration of the default file handler leads to the generation of report files within the logs folder of the
BART Server instance, that are named “report_<DATE>.txt”, where <DATE> corresponds to the date of the file
generation.
Rating sessions
Keywords
CDR, rating session, thread
May 2019 Public 118/150

Preliminary notes
“Offline Charging” section of the SAP CC Application Help documentation
Description of the offline execution mode of the “Chargeable Items Charging Process” available in the SAP CC
Description
As described in the Application Help documentation, the BART Server system provides a batch rating feature used to
rate acquired and consolidated CDRs. This feature relies on rating sessions that you can configure using the following
procedure.
Modifying settings related to rating sessions management

To configure the management of rating sessions handled by the BART Server system, refer to the “Modifying the
BART Server configuration file” section above and modify the following settings of the BART Server:
rating.session.max.number, that gives the possibility to specify the maximum number of simultaneous rating
sessions that can run at a given time
rating.session.monitoring.period, that corresponds to the period between 2 generations of “rating session
status” events. For further information, refer to the “Monitoring and event broadcasting” dedicated section
above
rating.session.threads, that corresponds to the maximum number of threads that can be allocated to a given
rating session
Rerating sessions
Keywords
CDR, rerating session, thread
Preliminary notes
“Rerating Operations driven by the BART Server” description of the “Chargeable Items Rerating” feature
available in the SAP CC Application Help documentation
“Rerating driven by the BART Server” description available in the “Chargeable Items Rerating Process” section of
the SAP CC Application Help documentation
Description
As described in the Application Help documentation, the BART Server system can be configured to work in
conjunction with the Core Server system during rerating operations. This feature relies on rerating sessions that you
can configure using the following procedure.
Modifying settings related to rerating sessions management

To configure the management of rerating sessions handled by the BART Server system, refer to the “Modifying the
BART Server configuration file” section above and modify the following settings of the BART Server:
rerating.pool.size, that gives the possibility to specify the number of threads used to rerate subscriptions
May 2019 Public 119/150

rerating.queue.size, that corresponds to the maximum number of rerating requests that can be queued when
rerating subscriptions
CAUTION
The “rerating.pool.size” parameter must not exceed the maximum number of concurrent rating sessions defined
though the “rating.session.max.number” parameter. Furthermore, the number of rating and rerating sessions
running at the same time must also not exceed the maximum number of concurrent rating sessions.
Keywords
SLD, payload
Preliminary notes
Description
The BART Server system can be integrated with third-party applications. You can use the following procedure to

To send payload information to the SAP SLD system during the startup sequence of the BART Server system, it is
necessary to configure some settings related to the integration with third-party systems. To modify this
configuration, refer to the “Modifying the BART Server configuration file” section above and modify the following
settings of the BART Server:
bart.sld.url, that corresponds to the IP address or name of the SLD Data Supplier Service in the targeted SAP SLD
system, using the following format: http://<SLD_HOST>:<SLD_PORT>/sld/ds
bart.sld.user, that corresponds to the name of the SAP SLD user
bart.sld.password, that corresponds to the password of the specified user
BART database
Keywords
Database, retention period, partitioning
Preliminary notes
“Database partitioning” section of the SAP CC Application Help documentation
“BART Database” dedicated online help available in the SAP CC Database References documentation
Description
May 2019 Public 120/150

The BART database represents the back-end database of a SAP Convergent Charging landscape that is used by the
BART Server system to store technical data. To improve performances of the BART Server system regarding the
storage of large number of CDRs, the BART database is partitioned using using a “Storage partitioning” method. You
can use the following procedures to modify the behavior of the BART database regarding data partitioning, and thus
fit your specific needs.
Modifying the partitioning settings

The storage partitioning of the BART database can be adapted to improve performances during some operations
such as data purging or archiving. According to your RDBMS, you can use the following procedures to configure:
The number of days that CDRs are kept in the BART database
The number of days or partitions that are created in advance
How partitions are created (automatically or manually)
The directories used to store tablespaces, filegroups or segments
Partitioning settings for Sybase ASE

The partitioning mechanism of a BART database running under a Sybase ASE RDBMS relies on the following SQL
procedures:
Procedure Description
CONFIGURE This procedure gives DBA the possibility to configure the global partitioning
policy by filling in the PARTITION_PURGE table with the parameters specified as
arguments
ADD_SEGMENT This procedure gives DBA the possibility to create a new segment
REMOVE_SEGMENT This procedure gives DBA the possibility to remove a segment which is no more
used for storing new partitions
MANAGE_NEW_PARTITION This procedure gives DBA the possibility to manually trigger the creation of new
partitions, that are only created if needed.
NOTE
To create partitions automatically, you can create a job within Sybase ASE that
calls the MANAGE_NEW_PARTITION procedure
To modify the default configuration of the partitioning mechanism, you must execute these procedures specifying
arguments that correspond to your needs. The following table contains the list of availeble arguments you can use:
Procedure Argument Description

CONFIGURE partitionDays (integer) The number of days CDRs are kept in the BART
database. Set by default to 40 days, this retention
period cannot exceed 70 days.
partitionAdvanceDays (integer) The number of partitions to create in advance
ADD_SEGMENT segment (varchar) Name of the segment to add, with a maximum of
256 characters
REMOVE_SEGMENT segment (varchar) Name of the segment to remove
MANAGE_NEW_PARTITION None None
May 2019 Public 121/150

Partitioning settings for Oracle

The partitioning mechanism of a BART database running under an Oracle RDBMS relies on the following SQL
procedures:
BART_ARCHIVE_PURGE This procedure gives DBA the possibility to configure the global partitioning
.CONFIGURE policy, by filling in the PARTITION_PURGE table with the parameters specified
as arguments
BART_ARCHIVE_PURGE This procedure gives DBA the possibility to create a new directory, resize an
.ADD_DIRECTORY existing directory or reactivate a removed directory
NOTES
Each directory name is unique and is respect the “BART_yyyymmdd”
pattern, where yyyymmdd is a date
You must create one directory at least at installation
Resize the directory in case the initial size is exceeded
BART_ARCHIVE_PURGE This procedure gives DBA the possibility to configure tablespace names
. CONFIGURE_TABLESPACE
BART_ARCHIVE_PURGE This procedure gives DBA the possibility to remove a directory which is no more
.REMOVE_DIRECTORY used in order to store new tablespaces
BART_ARCHIVE_PURGE This procedure gives DBA the possibility to manually trigger the creation of new
.MANAGE_NEW_PARTITION partitions, that are only created if needed
BART_ARCHIVE_PURGE This procedure activates the Oracle database scheduler for calling each day (at
.START_SCHEDULER 2:00 AM), the MANAGE_NEW_PARTITION procedure
BART_ARCHIVE_PURGE This procedure stops the Oracle database scheduler used to execute the
.STOP_SCHEDULER MANAGE_NEW_PARTITION regularly
BART_ARCHIVE_PURGE This procedure is equivalent to the START_SCHEDULER procedure except that
.RUN_SCHEDULER the first execution of the MANAGE_NEW_PARTITION procedure is immediate

BART_ARCHIVE_PURGE partitionDays (integer) The number of days CDRs are kept in the BART
.CONFIGURE database. Set by default to 40 days, this
retention period cannot exceed 70 days
partitionAdvanceDays The number of partitions to create in advance
(integer)
BART_ARCHIVE_PURGE directory (varchar) Path of the directory to create, with a
.ADD_DIRECTORY maximum of 2.000 characters
fileSize (varchar) Initial size of the directory to create. Set by
default to 1GB, this size cannot exceed 128GB
extendSize (varchar) The extension size of the directory,
automatically handled by Oracle when
necessary, and set by default to 250MB
BART_ARCHIVE_PURGE tablespaceprefix (varchar) The prefix of the tablespace name, set by
. CONFIGURE_TABLESPACE default to “BART_”
May 2019 Public 122/150

tablespacesuffix (varchar) The suffix of the tablespace name

datafilesuffix (varchar) The suffix of the file containing the
tablespace, set by default to “.dat”
BART_ARCHIVE_PURGE directory (varchar) The name of the directory to remove
.REMOVE_DIRECTORY
BART_ARCHIVE_PURGE None None
.MANAGE_NEW_PARTITION
.START_SCHEDULER
.STOP_SCHEDULER
.RUN_SCHEDULER
Partitioning settings for MS SQL Server

The partitioning mechanism of a BART database running under a Microsoft SQL Server RDBMS relies on the following
SQL procedures:
CONFIGURE This procedure gives DBA the possibility to configure the global partitioning
policy by filling in the PARTITION_PURGE table with the parameters specified as
arguments
ADD_DIRECTORY This procedure gives DBA the possibility to create a new directory, resize an
existing directory or reactivate a removed directory for storing filegroups
NOTES
Each directory name is unique and is respect the “BART_yyyymmdd”
pattern, where yyyymmdd is a date
You must create one directory at least at installation
REMOVE_DIRECTORY This procedure gives DBA the possibility to remove a directory which is no more
used in order to store new filegroups
MANAGE_NEW_PARTITION This procedure gives DBA the possibility to manually trigger the creation of new
partitions, that are only created if needed
NOTE
To create partitions automatically, you can create a job within SQL Server that
calls the MANAGE_NEW_PARTITION procedure

CONFIGURE partitionDays (integer) The number of days CDRs are kept in the BART
database. Set by default to 40 days, this retention
period cannot exceed 70 days.
partitionAdvanceDays (integer) The number of partitions to create in advance
May 2019 Public 123/150
ADD_DIRECTORY directory (varchar) Path of the directory to create, with a maximum of

2.000 characters
fileSize (varchar) Initial size of the directory to create, set by default
to 1GB
extendSize (varchar) The extension size of the directory, automatically
handled by SQL Server when necessary, and set by
default to 250MB
REMOVE_DIRECTORY directory (varchar) The name of the directory to remove
MANAGE_NEW_PARTITION None None
Configuring the Diameter Server system
AVP dictionary
Keywords
AVP dictionary, XML, XSD
Preliminary notes
“AVP Dictionary” section of the SAP CC Application Help documentation
Description
The Diameter Server system used an AVP dictionary that is used to store all the AVP descriptions related to specific
vendor network elements, that are not natively recognized by the Diameter Stack provided by the Traffix Systems
company, and must thus be defined and described to be used during CCRs and CCAs mapping operations. You can
use the following procedure to modify this configuration file and thus fit your specific business needs.
CAUTION
The AVP dictionary is designed and customized by the project team during the implementation project phase. SAP
SE recommends that system administrators do not change these settings.
Modifying the AVP dictionary

To modify the AVP dictionary of the Diameter Server system, execute the following procedure:
1. Stop the Diameter Server system
2. Backup the “avpDictionary.xml” file, that is located in the config folder of the Diameter Server instance
3. Edit the “avpDictionary.xml” file
6. Restart the Diameter Server system
May 2019 Public 124/150

Communication Channels
Keywords
Communication channels, securing
Preliminary notes
“Securing a landscape” section of the SAP CC Installation Guide documentation
Description
Communications with the BART Server system rely on different communication channels whose use depend on the
concerned elements. You can use the following procedure to secure these communication channels and thus fit your
specific needs or performance requirements.

For security purposes, all communication channels (except the Messages over UDP one) used to communicate within
your SAP CC landscape can be secured. For further information about the available securing procedures, refer to the
dedicated “Securing a landscape” section of the SAP CC Installation Guide documentation.
Diameter Server configuration file
Keywords
serverConfig.xml
Preliminary notes
Description
As described in the Installation Guide documentation, the configuration of the Diameter Server system is located in
the serverConfig.xml file:
That is available in the config folder of the Diameter Server instance
License management
Diameter stack
Exchange capability information
Supported applications
Supported vendors
Peer discovery policy
Incoming messages handling
Routing table to handle proxiable requests
Logging and tracing
Security settings
Charging stack
May 2019 Public 125/150
You can use this procedure to configure some settings of the Diameter Server configuration and thus fit your specific
needs.
The following table contains the list of settings that can be configured within the configuration file of the Diameter
Server system, including recommendations reagarding their modification:
Settings Description SAP CC Configurable

setting
License management
LicenseKey License key of the OpenBlox Java Diameter  
Stack used by the Diameter Server system
Diameter stack
URI IP address or name of the machine hosting the  
Diameter Server system
StackType Peer mode of the Diameter Server system  
MajorVersion Major version of the Diameter Base Protocol  
MinorVersion Minor version of the Diameter Base Protocol  
Exchange capability information
Realm Domain name, used to determine whether  
messages can be satisfied locally or routed to
another domain
VendorId Identifier of the Diameter vendor  
ProductName Product name of the Diameter Server system  
FirmwareRevision Firmware revision, used to inform Diameter  
peers
Supported applications
ApplicationId Identifier used to determine which Diameter  
application supports the messages
ApplicationIdType Type of application  
Supported vendors
SupportedVendorID Identifier used in CER and CEA messages to  
inform peers that the sender supports the
vendor-specific AVPs defined by this identified
vendor
Peer discovery policy
TWTimer Watchdog Timer (in seconds) used to control  
the frequency of DWR messages. A small value
fasters the detection of a peer failure, but
increases the number of generated messages
AcceptUnknownPeers Accept or refuse CERs from unknown peers  
CheckProtocolErrors Enable or disable the check of protocol errors  
May 2019 Public 126/150

Incoming messages handling

OpenedSessionsMaximum Maximum number of opened sessions  
StateEventPoolCoreSize  
StateEventPoolMaximumSize  
StateEventHandlerQueueCapacity  
StateEventPoolKeepAliveTime  
Routing table to handle proxiable requests
RealmName Primary key of the realm-based routing table  
RealmApplicationId Identifier of application, used as secondary key  
in routing table lookups
RealmLocalAction Handling method for messages.  
The default value is set to: LOCAL
Possible values are: LOCAL, RELAY, PROXY or
REDIRECT
Logging and tracing
RootLoggerLeverl Severity threshold for logs, that is hot  
modifiable and thus does not require a restart
of the Diameter Server system.
The default value is set to: INFO
Possible values are: OFF, SEVERE, WARNING,
INFO, CONFIG, FINE, FINER, FINEST or ALL
Security settings
SecurityId Identifier used during TLS negociation between  
diameter peers
TLSKeyStoreFile Name of the file as keystore and containing  
private keys and certificates related to the
Diameter Server system
TLSTrustStoreFile Name of the file used as truststore and  
containing private keys and certificates trusted
by the Diameter Server system
TLSKeyStorePassword Passphrase of the keystore  
TLSTrustStorePassword Passphrase of the truststore  
TLSEnabledProtocol List of TLS protocols  
TLSEnabledCipherSuite List of cypher suites  
Charging stack
OCSHostName IP address or name of the machine hosting the  
Core Server system
OCSPort External port of the dispatcher instance of the  
Core Server system, used by the Diameter
Server system to communicate over the Packets
over TCP/IP communication channel
OCSUser Name of the technical user used to connect to  
the Core Server system
OCSPassword Password of the specified technical user  
May 2019 Public 127/150

OCSSecured Enable or disable the securing of  

communications with the Core Server system
OperationTimeout Timeout (in milliseconds) for charging requests  
NOTE
Set by default to 1000ms, SAP SE recommends
that you modify this value according to your
business requirement.
SLDURL URL of the targeted SAP SLD system  
SLDUser Name of the SAP SLD user  
SLDPassword Password of the SAP SLD user  
 Yes
 No
 Yes, also during installation
 Not recommended
Modifying the Diameter Server configuration file

To modify the configuration file of the Diameter Server system, execute the following procedure:
2. Backup the “serverConfig.xml” file
3. Edit the “serverConfig.xml” file, that is located in the config folder of the Diameter Server instance
Keywords
Preliminary notes
Description
Java Runtime Environment. The Diameter Server system is a Java process whose execution can be configured to fit
specific requirements. To determine and modify the different JVM options for the Diameter Server system, refer to
the “Java Virtual Machine” procedure available for the instances of the Core Server system, and apply the relevant
modifications on the startup file of the Diameter Server system.
May 2019 Public 128/150
Logging and tracing
Keywords
Logging.properties, log, trace, category, severity, domain, threshold, troubleshoot
Preliminary notes
Description
and so on. You can use this procedure to configure the logging and tracing capabilities of the Diameter Server
system, that rely on the Java native logging framework whose configuration is located in the logging.properties
file:
That is available in the config folder of the Diameter Server instance
Handlers definition
Handlers configuration
Default log level
The following table contains the list of settings related to logging capabilities of the Diameter Server system that you
can configure to fit your specific needs:
Handlers definition
handlers CSV (space delimited) list of handlers’ classnames for the root logger, set by
default to: java.util.logging.ConsoleHandler java.util.logging.FileHandler
Default log level
.level Default log level for avery logger whose level is not explicitely defined, set by
default to: CONFIG
Possible values are: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER,
FINEST or ALL
Console handler configuration
java.util.logging Log level for the console output, set by default to: ALL
.ConsoleHandler.level
May 2019 Public 129/150

FINEST or ALL
java.util.logging Classname of the string formatter used for texts printed into the console
.ConsoleHandler.formatter
File handler configuration
java.util.logging Log level for the console output, set by default to: ALL
.FileHandler.level
FINEST or ALL
java.util.logging Classname of the string formatter used for texts printed into the console
.ConsoleHandler.formatter
java.util.logging Pattern used to generate the ouput file name, that consists of a string
.ConsoleHandler.pattern including the following components which are replaced at runtime:
“/“, that represents the local pathname separator
“%t“, that represents the system temporary directory
“%h“, that represents the value of the “user.home“ system property
“%g“, that represents the generation number used to distinguish rotated
logs. If no “%g“ field has been specified and if the file count is greater than
one, the generation number will be added to the end of the generated
filename, after a dot
“%u“, that represents a unique number used to resolve conflicts
“%%“, that can be used to translate a single percent sign “%“
java.util.logging Approximate maximum amount to write (in bytes) to a given file. Setting this
.ConsoleHandler.limit system parameter to 0 means that the written amount is not limited
java.util.logging Number of output files available for the rotation cycle
.ConsoleHandler.count
java.util.logging Specifies whether the FileHandler should append content onto an existing
.ConsoleHandler.append output file, or not
Modifying the logging settings of the Diameter Server

To modify the logging settings of the Diameter Server system, execute the following procedure:
2. Backup the “logging.properties” file
3. Edit the “logging.properties” file, that is located in the config folder of the Diameter Server instance
Multiple services credit-control
Keywords
MSCC, service dictionary, XML, XSD
May 2019 Public 130/150

Preliminary notes
“Service Dictionary” section of the SAP CC Application Help documentation
“Service dictionary” section of this documentation
Description
As described in the Application Help documentation, the service dictionary gives the possibility to register multiple
services with different mappings, and thus implement the multiple-services credit control feature within the
Diameter Server system. You can use the following procedure to modify the relevant settings of the service
dictionary and thus fit your specific business needs regarding MSCC.
Implementing MSCC
The following table contains the list of AVPs that rely to the MSCC support:
XML element Description

msccServiceKeyDesc Determines which mapping must be applied to the CCR
msccServiceDesc Defines the mapping that must be used to transform CCRs into charging requests.
Mandatory to activate the support of MSCC, this element contains one
“msccMappingDesc” sub-element
msccMappingDesc Indicates where the following sub-elements can be found in the CCR:
Mandatory sub-elements:
eventNameDesc, that corresponds to the name of the chargeable item class
reservationIdDesc, that corresponds to the identifier of the reservation
unitPropertyDesc, that corresponds to the unit property which is used to
identify the property to inverse in case of inverse rating
Optional sub-elements:
infoPropertyDesc, that corresponds to a user property to map, when required.
You can define a default value for this property in case this property is not
available in the MSCC AVP
To activate the support of MSCC, you must thus execute the “Modifying the service dictionary” procedure and add at
least one “msccServiceDesc” element to the service dictionary.
NOTES
If a CCR contains several MSCC AVPs but no “msccServiceDesc” element is defined in the service dictionary, a
DIAMETER_UNABLE_TO_COMPLY error will be sent
The “serviceDictionaryMSCC.xml” is provided in the examples folder of the Diameter Server instance as an
example including MSCC elements. In this example, the “Rating-Group” AVP is used as key for the mapping and
as reservation ID.
Service dictionary
Keywords
Service dictionary, AVP, XML, XSD
May 2019 Public 131/150

Preliminary notes
“Service Dictionary” section of the SAP CC Application Help documentation
Description
The Diameter Server system used a service dictionary that is used to store all the descriptions of each managed
service, including the AVP mapping between the Diameter messages and the charging operation messages
exchanged between the Diameter and Core Server systems. You can use the following procedure to modify this
configuration file and thus fit your specific business needs.
CAUTION
The service dictionary is designed and customized by the project team during the implementation project phase.
SAP SE recommends that system administrators do not change these settings.
Modifying the service dictionary

To modify the service dictionary of the Diameter Server system, execute the following procedure:
2. Backup the “serviceDictionary.xml” file, that is located in the config folder of the Diameter Server instance
3. Edit the “serviceDictionary.xml” file
6. Use the “serviceDictionary.xsd” XSD schema to ensure that your modifications are valid
Keywords
SLD
Preliminary notes
Description
The Diameter Server system can be integrated with third-party applications. You can use the following procedure to

To send payload information to the SAP SLD system during the startup sequence of the Diameter Server system, it is
necessary to configure some settings related to the integration with third-party systems. To modify this
May 2019 Public 132/150

configuration, refer to the “Modifying the Diameter Server configuration file” section above and modify the
following settings of the Diameter Server:
SLDURL, that corresponds to the IP address or name of the SLD Data Supplier Service in the targeted SAP SLD
system, using the following format: http://<SLD_HOST>:<SLD_PORT>/sld/ds
SLDUser, that corresponds to the name of the SAP SLD user
SLDPassword, that corresponds to the password of the specified user
Configuring the IEC system
Scenario management
Keywords
CAT, scenario
Preliminary notes
“Launching CAT Tool” section of the SAP CC Installation Guide documentation
“About scenario” section of the SAP CC CAT Tool User Interfaces documentation
Description
The CAT Tool user interface gives the possibility to model scenarios that represent sequences of basic actions
executed by the IEC Server system. For further information, refer to the “About scenario” section of the SAP CC CAT
Tool User Interfaces documentation, that contains details about:
Scenario modeling
Scenario building
Scenario execution
Specific actions
Keywords
Java function, customization, SDK
Preliminary notes
“com.highdeal.iec” Java package description, available in the SAP CC Java/XML API Reference (IEC Library)
documentation
Description
The IEC Server system can be customized by developing your own Java classes using the IEC SDK that gives the
possibility to:
Add new actions
Customize the reporting capabilities of the IEC Server system
Customize the connection to the BART Server system
May 2019 Public 133/150

For further information, refer to the SAP CC Java/XML API Reference (IEC Library) documentation.
May 2019 Public 134/150

4 Tuning SAP Convergent Charging
May 2019 Public 135/150

Distributing partitions to guiders and raters using a smart mode

v.0.1 (12/07/2016 - Public) – SAP CC 5.0 and later
Keywords
cache, warmup, distribution, partition, smart mode, online stateful, master dispatcher, rater, guider, burst
protection
See Also in SAP CC documentation

“Partitions mapping reorganization” section of the SAP CC Application Help documentation
“Cache warm-up” section of the SAP CC Application Help documentation
“Tuning: Partitions Distribution and Warmup” group in the SAP CC System Parameters Reference documentation
Description
To increase the reactivity of the Core Server, raters and guiders handle data within dedicated cached structures.
To avoid latency, a cache warmup mechanism can be activated in order to retrieve this data from the Core and
Session databases, and pre-load them into these cached structures. When this warmup mechanism is activated, it is
possible to configure the Core Server system in order to activate a smart execution mode for the partitions
distribution operations performed by the master dispatcher. This execution mode gives the possibility to control the
warmup operations performed by the targeted instances during these partitions distribution operations (executed
when guiders or raters start, shut-down or fail), and thus to control the overall impact of warmup operations on the
online stateful charging operations.
Activating the smart distribution mode

If the CACHE_WARMUP_THREAD_COUNT system parameter has been set to a positive value, the cache warmup
mechanism is activated. In this case, the master dispatcher distributes partitions using the smart execution mode as
soon as the number of running instances is greater than or equals the value of the
xxx_PARTITION_SWITCH_MIN_INSTANCE_COUNT system parameter. It is then necessary to configure the following
system parameters:
xxx_PARTITION_SWITCH_WARMUP_TIMEOUT, which defines the maximum duration allocated to a partition
warmup operation performed by a guider or rater in a smart distribution context. SAP SE recommends you to set
a value that corresponds to twice the average duration of the partition warmup operations, that can be
retrieved from the dedicated Introscope probes
xxx_PARTITION_SWITCH_CONCURRENT_PARTITIONS, which defines the maximum number of not-yet warmed
partitions that can be simultaneously assigned to a guider or rater for warming purpose.
EXAMPLE
Considering a Core Server system containing 4 raters, setting the
RATER_PARTITION_SWITCH_CONCURRENT_PARTITIONS system parameter to 3 implies that a maximum of 12
partitions can be simultaneously assigned by the master dispatcher to the running raters for warming purpose.
May 2019 Public 136/150

xxx_PARTITION_SWITCH_DB_INSTANCE_CONCURRENT_PARTITIONS, which defines the maximum number of

partitions per database instance that can be simultaneously assigned to the running guiders or raters for
warming purpose
EXAMPLE
Considering a landscape containing a Core database made up with 3 database instances, setting the
GUIDER_PARTITION_SWITCH_DB_INSTANCE_CONCURRENT_PARTITIONS system parameter to 3 implies that a
maximum of 9 partitions can be simultaneously assigned by the master dispatcher to the running guiders for
warming purpose, whatever the number of running guiders is.
NOTE
In case both xxx_PARTITION_SWITCH_DB_INSTANCE_CONCURRENT_PARTITIONS and
xxx_PARTITION_SWITCH_CONCURRENT_PARTITIONS are defined, the minimum of the 2 corresponding number of
partitions is used by the master dispatcher when assigning partitions for warming purpose.
EXAMPLE 1
Considering:
A Core Server system containing 5 raters, 1 of these raters shutting down
A Core database made up with 3 database instances
The RATER_PARTITION_SWITCH_CONCURRENT_PARTITIONS system parameter set to 3
The RATER_PARTITION_SWITCH_DB_INSTANCE_CONCURRENT_PARTITIONS system parameter set to 3
Then the number of partitions that can be simultaneously assigned by the master dispatcher to the 4 running
raters for warming purpose is: min((5-1)x3,3x3)=9 partitions.
EXAMPLE 2
Considering:
A Core Server system containing 4 running guiders
A Core database made up with 3 database instances
The GUIDER_PARTITION_SWITCH_CONCURRENT_PARTITIONS system parameter set to 2
The GUIDER_PARTITION_SWITCH_DB_INSTANCE_CONCURRENT_PARTITIONS system parameter set to 3
Then the number of partitions that can be simultaneously assigned by the master dispatcher to the running
guiders for warming purpose is: min(4x2,3x3)=8 partitions.
CAUTION
If the cache warmup mechanism is not activated, no warmup operation is performed by raters or guiders, which
leads to additional latency that impacts the online stateful charging operations.
May 2019 Public 137/150

Tuning the smart distribution mode

SAP SE recommends you to consider the following configuration as the minimum possible configuration:
xxx_PARTITION_SWITCH_CONCURRENT_PARTITIONS = 1
xxx_PARTITION_SWITCH_DB_INSTANCE_CONCURRENT_PARTITIONS = 1
xxx_PARTITION_SWITCH_MIN_INSTANCE_COUNT = (total number of running instances) - (acceptable number of
down instances at a given time) + 1
EXAMPLE 1
Considering:
A Core Server system containing 6 raters deployed on 3 hosts
An acceptable number of 1 host failure, similar to 2 raters failure
Then the xxx_PARTITION_SWITCH_MIN_INSTANCE_COUNT system parameter can be set to (6-2)+1=5, which
means that the smart execution mode will be used by the master dispatcher:
Until more than 4 raters remain running
When a fifth rater will start
Then, you need to tune the values of both xxx_PARTITION_SWITCH_CONCURRENT_PARTITIONS and

xxx_PARTITION_SWITCH_DB_INSTANCE_CONCURRENT_PARTITIONS system parameters according to the previously
explained behavior.
The objective is to determine the values that give the best ratio between:
The duration of an instance startup or shutdown operation
The impact of warmup operations on the online stateful charging operations
These values can be determined by analyzing the following performance and health metrics:
SAP CC | Warm-Up | SAP CC, which shows the number of partitions assigned to a given instance
SAP CC | Warm-Up | SAP CC, which shows the number of warmed partitions of a given instance
Protecting raters and guiders against warmup overloading

In case a rater or guider is added or removed from the list of running instances, the master dispatcher redistributes
the partitions among the list of running raters and guiders for warming purposes. When the smart execution mode
has been activated, it is also possible to configure the following system parameters in order to protect the raters and
guider against possible overloading due to warmup operations:
GUIDER_PARTITION_SWITCH_BURST_PROTECTION_INITIAL_DELAY, which defines the minimum delay (in
seconds) between the first and second assignments of partition to each guider during a smart warmup operation
GUIDER_PARTITION_SWITCH_BURST_PROTECTION_DELAY, which defines the minimum delay (in seconds)
between the assignment of partitions to each guider during a smart warmup operation
RATER_PARTITION_SWITCH_BURST_PROTECTION_INITIAL_DELAY, which defines the minimum delay (in
seconds) between the first and second assignments of partition to each rater during a smart warmup operation
RATER_PARTITION_SWITCH_BURST_PROTECTION_DELAY, which defines the minimum delay (in seconds)
between the assignment of partitions to each rater during a smart warmup operation
As the JVM is more solicited on startup due to additional internal operations, SAP SE recommends that you set an
initial delay that is bigger than the delay used for the subsequent assignments.
May 2019 Public 138/150

EXAMPLE
Considering a configuration where:
1 rater is starting
6 partitions (Pa to Pf) must be assigned by the master dispatcher to this starting rater
RATER_PARTITION_SWITCH_CONCURRENT_PARTITIONS =5, which means that a maximum of 5 partitions
can be simultaneously assigned to this rater for warming purpose
The following schema shows how this list of partitions are assigned to the rater using delays for protection
purpose:
At t1, the master dispatcher assigns the partition Pa to the rater, which represents the first partition
assignment.The rater puts Pa in its dedicated queue and starts warming up this partition.
At t2, the master dispatcher assigns the partition Pb to the rater, which represents the second partition
assignment, delayed using the value of the RATER_PARTITION_SWITCH_BURST_PROTECTION_INITIAL_DELAY
system parameter. The rater puts Pb in its dedicated queue and starts warming up this partition.
At t3, the master dispatcher assigns the partition Pc to the rater, which represents the third partition
assignment, delayed at least with the value of the RATER_PARTITION_SWITCH_BURST_PROTECTION_DELAY
system parameter. The rater puts Pc in its dedicated queue and starts warming up this partition.
At t4, the master dispatcher assigns the partition Pd to the rater, which represents the fourth partition
system parameter. The rater puts Pd in its dedicated queue and starts warming up this partition.
At t5, the master dispatcher assigns the partition Pe to the rater, which represents the fifth partition
system parameter. The rater puts Pe in its dedicated queue and starts warming up this partition.
At t6, which corresponds to an undefined time but that is greater than the value specified in the
RATER_PARTITION_SWITCH_BURST_PROTECTION_DELAY system parameter, the rater successfully warmed
up one of the previously assigned partitions (Pa to Pe). The master dispatcher then assigns the partition Pf to
the rater. The rater puts Pf in its dedicated queue and starts warming up this partition.
NOTE
In case the smart execution mode has not been activated, all the 6 partitions (Pa to Pf) would be simultaneously
assigned to the rater by the master dispatcher, which could decrease the performance of the rater regarding
the warmup operations.
May 2019 Public 139/150

May 2019 Public 140/150

Modifying the table rollover policy for charging sessions

Keywords
session database, session-based charging, rating session, charging session, rollover, fragmentation

“Table rollover for rating sessions” and “Dual Database” sections of the SAP CC Application Help documentation
“Backends: Database Management Settings” group in the SAP CC System Parameters Reference documentation
Description
As described in the description of the “Dual Database” feature available in the SAP CC Application Help
documentation, the Session database is an optional database that contains the different data related to the business
objects handled by SAP CC during the session-based charging operations.
When this database is used, each event that occurs on a given rating session leads to one or multiple operations that
directly impact the content of the Session database. These frequent modifications may lead to the fragmentation of
the database tables, which decreases its performances and can consequently decrease the overall performance of
your landscape.
You can use this procedure to configure a rollover mechanism that reduces the fragmentation of the storage related
to the rating sessions within the Session database.
Enabling the table rollover mechanism

If the RATING_SESSION_TABLE_ROLLOVER_COUNT system parameter has been set to a value higher than 1, the
table rollover mechanism is activated. In this case, the rater instances record the session data in the relevant table
considered as destination for the current period.
NOTE
You can use the RATING_SESSION_TABLE_ROLLOVER_STATUS indicator to see the status of the mechanism,
particularly the validity period of the currently used destination.
Tuning the table rollover policy

As described in the Application Help documentation, the configuration of the rollover mechanism is based on the
following system parameters:
RATING_SESSION_TABLE_ROLLOVER_COUNT, used to specify the number of tables that can be used as
destinations by the raters to store the rating sessions
RATING_SESSION_TABLE_ROLLOVER_PERIOD, that defines the validity period (in days) of the table that is
currently used as destination for storing the rating sessions data
May 2019 Public 141/150

To fit your specific needs, SAP SE recommends that you take into consideration the maximum duration of your rating
sessions. Indeed, the validity period must be large enough to avoid that a pending rating session that has been
created within a given destination table locks the defragmentation of this table after the table switch.
EXAMPLE
Considering 2 destination tables used to store rating sessions whose maximum observed duration is 1 day, you can
set a validity period of 7 days. This validity period implies that:
During the 7 first days, the rating sessions will be created in the current destination table
The 8th day, the new rating sessions will be created in the newly switched destination table. The cleanup of the
previous destination table begins and will lead to the deletion of the ended rating sessions, but will not impact
the pending ones
The 9th day, all rating sessions created in the previous destination table are theoretically ended and can be
deleted
The 10th day, the previous destination table is empty, and is thus no more fragmented
Once you determined a validity period, SAP SE recommends that you start using 2 destination tables. You can
increase this number up to 4 destination tables, but you need to keep in mind that each destination table represents
the same physical storage, that needs to be available in your landscape. Increasing the number of destination tables
thus requires multiplying the physical storage space. Theoretically, when the validity is well-tuned, 2 destination
tables should be enough.
NOTE
If you hot change the number of destination tables or the validity period, the “From” date available in the
RATING_SESSION_TABLE_ROLLOVER_STATUS indicator will not reflect the real start date of the period.
May 2019 Public 142/150

5 Monitoring SAP Convergent Charging
May 2019 Public 143/150

Monitoring the file metadata

Keywords
file metadata, item file, cockpit, monitoring

“Enabling the recording of file metadata” section in this documentation
“Analyze Item Files” application description in the SAP CC Cockpit Online Help documentation
Description
Analyze Item Files is an application available in the SAP CCockpit application that enables the SAP CC administrators
(system, application, business) to filter and visualize the metadata related to the data files generated during the
different processes. For monitoring purpose, you can use the following procedures to create relevant dashboards
that you can save as variants and reuse later.
Monitoring the unprocessed items

Unprocessed items correspond to items which have not been processed yet, for possible reasons such as:
These items are new items, recently stored within data files
These items correspond to invalid items that could not be sent to SAP CI
Communication errors occurred during the communication with SAP CI
And so on
The following procedure gives you the possibility to create a dashboard for monitoring the unprocessed items
created because of a communication error, distributed by class name over the recording period. SAP SE recommends
that you consider this dashboard as a sample, that you can adapt to fit your specific needs or preferences.
Filtering the items

To create the relevant filter, execute the following operations:
1. Click the “Unprocessed Items” element of the “Items By Status” visual filter, that corresponds to item files
containing unprocessed items (whatever their creation reason is)
2. Click the “Communication error” element of the “Unprocessed Items By Creation Event” visual filter to
determine a subset of all the unprocessed items
3. Click the “Measure By” button and select the “Unprocessed Items” element to modify the behavior of the third
visual filter and thus display the daily repartition of the unprocessed items created because of a communication
error
4. Click the “Adapt Filters” button and browse the list of additional filters using the “More Filter” button
5. Select the “Written Itens (Rater) by Class Name” element, that appears in the “Additional Filters” section
6. Click the “Measure By” button and select the “Unprocessed Items” element to modify the behavior of this
additional visual filter used to display the repartition of the unprocessed items according to the name of the
associated item class
May 2019 Public 144/150

7. Select the “Show on Filter Bar” option

8. Click the “Go” button to update the filter bar that now contains four visual filters dedicated to the unprocessed
items
Modifying the smart chart

To display a more suitable smart chart, execute the following operations:
1. Click the “Selected Chart Type” button and select the “Pie Chart” element
2. Click the “Settings” button and only select the “Unprocessed Items” and “Class Name” elements to modify the
content of the smart chart and thus build a pie chart displaying the repartition of the unprocessed items
according to the name of the associated item class
3. Click the “OK” button
Modifying the table

To display a more suitable smart chart, execute the following operations:
1. Click the header of the “Unprocessed Items” column, and click the “Sort Descending” element
2. Click the header of the “Class Name” column, and click the “Group” element
3. Click the “Settings” button and only select the “Name”, “Status”, “Class Name”, “Unprocessed Items”, “Progress”
and “Creation Date” elements to modify the content of the table and display the relevant information
4. Click the “OK” button
Creating a variant
To create a variant that will be available for future connections to the Analyze Item Files application, execute the
following operations:
1. Click the “Select Variant” button to open the window dedicated to the management of variants
2. Click the “Save As” button
3. Fill the “Name” field with a relevant name for your dashboard, such as “Unprocessed items per item class”
4. In case you want this dashboard to be loaded on startup, select the “Set as Default” option
5. Click the “OK” button to create this dashboard
May 2019 Public 145/150

6 Troubleshooting SAP Convergent Charging

Logs and traces
Troubleshooting JCo RFC communications

To temporarily troubleshoot the JCo RFC communications between SAP CC and the SAP CRM system or the SAP ERP
system you can enable the JCo trace management.
CAUTION
SAP SE recommends that you take particular care when enabling JCo traces, as the performance of the whole SAP
CC system may reduce significantly. In case you must be enable JCo traces on a production landscape, contact your
SAP Support Team.
Once you determined the appropriate JCo trace levels that are relevant for your investigations, execute the following
procedure:
2. Check or set up the path for the generated traces by modifying the value of the JCO_TRACE_PATH parameter
3. Modify the value of the following system parameters for each concerned dispatcher and bulkloader instance:
JCO_TRACE_LEVEL, which gives the possibility specify the level of JCo traces to generate
JCO_JRFC_TRACE_LEVEL, which gives the possibility enable or disable the generation of JCo RFC traces
JCO_CPIC_TRACE_LEVEL, which gives the possibility specify the level of JCo CPIC traces to generate
For further information about these system parameters, “Logging and tracing ” section of this documentation.
IMPORTANT NOTE
At the end of your investigations, do not forget to disable the generation of JCo traces by setting the value of the
JCO_TRACE_LEVEL system parameter back to 0 for the concerned instances.
May 2019 Public 146/150

Typographic Conventions
Type Style Description
Arrows separating the parts of a navigation path, for example, menu options.
Example Text Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation
Example text Emphasized words or phrases in body text, graphic titles, and table titles
EXAMPLE TEXT Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.
Example text Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example text Exact user entry. These are words or characters that you enter in the system exactly as
they appear in the documentation.
<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system, for example, “Enter your <User
name>”.
EXAMPLE Keys on the keyboard, for example, F2 or ENTER .
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
May 2019 Public 147/150

Copyrights
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE or an SAP affiliate company and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks
of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP SE or an SAP affiliate company in
Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius,
and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP SE or an SAP affiliate company and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional warranty.
May 2019 Public 148/150

Disclaimer
Some components of this product are based on Java™. Any code change in these components may cause
unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these
components.
Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be
modified altered in any way.
May 2019 Public 149/150

SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE. The information contained herein may be changed without prior notice.

Tuning Guide

Uploaded by

Copyright:

Available Formats

Tuning Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tuning Guide

Uploaded by

Copyright:

Available Formats

Tuning Guide

SAP Convergent Charging (SAP CC 5.0)

May 2019 Public 2/150

2 SIZING SAP CONVERGENT CHARGING ....................................................................................... 17

May 2019 Public 3/150

May 2019 Public 4/150

Modifying the shared allowances cache ............................................................................................................................................ 50

May 2019 Public 5/150

Preliminary notes ............................................................................................................................................................................... 96

May 2019 Public 6/150

Modifying the logging and tracing policy ......................................................................................................................................... 115

May 2019 Public 7/150

Description ....................................................................................................................................................................................... 131

4 TUNING SAP CONVERGENT CHARGING ....................................................................................135

5 MONITORING SAP CONVERGENT CHARGING .............................................................................143

6 TROUBLESHOOTING SAP CONVERGENT CHARGING ......................................................................146

TYPOGRAPHIC CONVENTIONS .........................................................................................................147

May 2019 Public 8/150

Disclaimer ............................................................................................................................................ 149

May 2019 Public 9/150

1 Before You Start

This Tuning Guide is an SAP document that contains:

May 2019 Public 10/150

What's New in this Document

May 2019 Public 11/150

Modifications and enhancement of the following sections:

May 2019 Public 12/150

CER Capabilities-Exchanging-Request (Diameter)

CFS Clustered File System

DWR Device-Watchdog-Request (Diameter)

MSCC Multiple-Services Credit Control (Diameter)

NUMA Non-Uniform Memory Access

May 2019 Public 13/150

May 2019 Public 14/150

May 2019 Public 15/150

May 2019 Public 16/150

2 Sizing SAP Convergent Charging

May 2019 Public 17/150

May 2019 Public 18/150

May 2019 Public 19/150

JVM Option Recommendation

May 2019 Public 20/150

3 Configuring SAP Convergent Charging

Configuring the desktop applications

Configuring Core Tool

Parameter Type Description Default value Possible values

May 2019 Public 21/150

Configuring BART Tool

Parameter Type Description Default value Possible values

May 2019 Public 22/150

3. Modify the value of the relevant parameters

Configuring CAT Tool

Parameter Type Description Default value Possible values

Configuring the web applications

May 2019 Public 23/150

Parameter Values Type

May 2019 Public 24/150

For Oracle with “thin” driver, the URI format is:

sqlhelper.login You must set a value that corresponds to an already 

May 2019 Public 25/150