SAP Convergent Charging 4.1 Operations Guide

SAP Convergent Charging 4.1

OPERATIONS GUIDE | PUBLIC

Document Version: : 2.0 – 2019-08-30

SAP Convergent Charging 4.1 Operations Guide

© 2

016

SA

P S

E o

r a

n S

AP

aff

ilia

te c

om

pa

ny.

All

rig

hts

re

serv

ed

.

2 PUBLIC

SAP Convergent Charging 4.1 Operations Guide (v2.0)

Documentation in SAP Help Portal

Documentation in SAP Help Portal

SAP Help Portal is the central place to access public information.

You can find the SAP CC product documentation on SAP Help Portal at the following location: help.sap.com/cc41

Quick link: cc41

http://help.sap.com/cc41



Content PUBLIC 3

Content

1 Document History .................................................................................................................................................. 8

2 Introduction ............................................................................................................................................................ 9

2.1 Target Audience ....................................................................................................................................................... 9

2.2 About This Document .............................................................................................................................................. 9

2.3 Supportability .........................................................................................................................................................10

2.4 What’s New in This Document ................................................................................................................................10

2.4.1 What’s New in SP 1 ........................................................................................................................................... 11

2.4.2 What’s New in SP 0 .......................................................................................................................................... 11

2.5 Document Abbreviations ........................................................................................................................................ 11

3 Before You Start ...................................................................................................................................................13

3.1 Global Definitions .................................................................................................................................................... 13

3.2 Fundamental User Assistance ................................................................................................................................ 13

3.2.1 Product Documentation Set ............................................................................................................................ 14

3.3 Important SAP Notes .............................................................................................................................................. 15

3.3.1 CA APM Introscope 9.x .................................................................................................................................... 16

3.3.2 SAP Solution Manager 7.1 ................................................................................................................................ 17

3.3.3 SAP JVM ........................................................................................................................................................... 17

3.3.4 DBA Cockpit ..................................................................................................................................................... 17

3.4 Additional Information ............................................................................................................................................ 18

4 Technical System Landscape ............................................................................................................................. 19

4.1 Software Component Matrix .................................................................................................................................. 19

4.1.1 Java Components ............................................................................................................................................ 19

4.2 Related Documentation .......................................................................................................................................... 21

4.3 System Landscape Directory (SLD) ....................................................................................................................... 21

4.4 SAP Solution Manager for SAP CC ......................................................................................................................... 21

4.4.1 Infrastructures of SAP Solution Manager ....................................................................................................... 22

4.4.2 Application Operations.................................................................................................................................... 23

4.4.3 Work Centers Used for SAP CC ...................................................................................................................... 25

4.4.4 Monitoring and Alerting................................................................................................................................... 26

4.4.5 Root Cause Analysis ........................................................................................................................................ 28

4.4.6 Related Information ........................................................................................................................................ 28

4.5 CA Introscope for SAP CC ..................................................................................................................................... 28

4.5.1 Features........................................................................................................................................................... 30

4.5.2 CA Introscope in SAP Solution Manager ........................................................................................................ 30

4.5.3 CA Introscope Components............................................................................................................................ 30

4.5.4 Management Module for SAP CC ................................................................................................................... 32

4.5.5 Technical Operations for SAP CC ................................................................................................................... 35


4.6 SAP Management Console .................................................................................................................................... 37

4 PUBLIC


Content

5 Monitoring of SAP CC ......................................................................................................................................... 38

5.1 Monitoring Installation and Setup ......................................................................................................................... 38

5.2 Component Specific Monitoring ............................................................................................................................ 38

5.3 Monitoring .............................................................................................................................................................. 39

5.3.1 Technical Monitoring....................................................................................................................................... 39

5.3.2 Performance Monitoring ................................................................................................................................. 40

5.3.3 Alert Monitoring .............................................................................................................................................. 40

5.4 Technical Monitoring and Alerting Using SAP Solution Manager 7.1 SP13 and Later .......................................... 40

5.4.2 Implementation in Your SAP CC Landscape .................................................................................................. 42

5.4.3 Working with the Technical Monitoring Work Center in SAP Solution Manager............................................ 43

5.5 Technical Monitoring Using CA Introscope for SAP .............................................................................................. 44

5.5.2 Implementation in Your SAP CC Landscape .................................................................................................. 45

5.5.3 Manual Monitoring with CA Introscope .......................................................................................................... 45

5.5.4 CA IS Workstation User Interface ................................................................................................................... 47

5.5.5 CA IS WebView User Interface ........................................................................................................................ 48

5.6 Manual Monitoring ................................................................................................................................................. 48

5.7 Database Monitoring.............................................................................................................................................. 50


5.8 Error and Process Monitoring ................................................................................................................................. 51

5.8.1 SAP Solution Manager 7.1 ................................................................................................................................ 51

5.9 Business Monitoring with BART Tool of SAP CC................................................................................................... 52

5.9.1 Offline Charging Scenario Variant................................................................................................................... 52

5.10 Monitoring of SAP Java Components .................................................................................................................... 52

5.10.1 Java Monitoring and Management ................................................................................................................. 52

5.11 Detailed Monitoring and Tools for Problem and Performance Analysis ............................................................... 53

5.11.1 Log and Trace Files in your System Landscape ............................................................................................. 53

5.11.2 Log and Trace Files in SAP CC 4.1................................................................................................................... 53

5.11.3 Files of the SAP CC Core Server System ........................................................................................................ 54

5.11.4 Log Files of the Java Garbage Collection ........................................................................................................ 57

5.11.5 Technical Operations ...................................................................................................................................... 60

5.11.6 Files of the Other SAP CC Systems ................................................................................................................. 61

5.11.7 Files of the Graphical User Interfaces ............................................................................................................. 62

5.11.8 Further Information ......................................................................................................................................... 62

5.11.9 Error Files of SAP CC 4.1 ................................................................................................................................. 62

5.11.10 Useful Errors and Error Code List ................................................................................................................... 65

5.12 Further Information ............................................................................................................................................... 66

5.12.1 Monitoring SAP Notes ..................................................................................................................................... 66

6 Management of SAP CC...................................................................................................................................... 67

6.1 Starting and Stopping ............................................................................................................................................ 67

6.1.1 Launch Tools for SAP CC ................................................................................................................................ 67

6.1.2 Start and Stop Sequence ................................................................................................................................ 69

6.1.3 Related Documentation ................................................................................................................................... 71

6.2 Software Configuration ........................................................................................................................................... 71

6.2.1 Configuration Files .......................................................................................................................................... 72

6.3 Administration Tools.............................................................................................................................................. 73

6.4 Backup and Restore ............................................................................................................................................... 75


Content PUBLIC 5

6.4.1 Backup and Restore Strategy ......................................................................................................................... 75

6.4.2 General Recommendations .............................................................................................................................77

6.4.3 Detailed Backup and Restore .......................................................................................................................... 78

6.4.4 Operating System, Software and Configuration Data .................................................................................... 83

6.4.5 Database for SAP CC 4.1 ................................................................................................................................. 83

6.4.6 SAP CC 4.1 Third-Party Components ............................................................................................................. 84

6.4.7 Further Information ......................................................................................................................................... 85

6.5 Periodic Tasks ........................................................................................................................................................ 85

6.5.1 Automated Periodic Tasks .............................................................................................................................. 85

6.5.2 Required Manual Periodic Tasks..................................................................................................................... 88

6.5.3 Detailed Periodic Tasks ................................................................................................................................... 95

6.6 Load Balancing....................................................................................................................................................... 98

6.6.1 Detailed Load Balancing.................................................................................................................................. 99

6.6.2 Setup Change ................................................................................................................................................ 100

6.6.3 Troubleshooting ............................................................................................................................................ 100

6.7 User Management................................................................................................................................................ 100

6.8 Management of Outdated Technical Data............................................................................................................ 101

6.8.1 Potential Outdated Technical Data ................................................................................................................ 101

6.8.2 Log Files......................................................................................................................................................... 103

6.9 Administration: System Audit and Control ......................................................................................................... 103

6.9.1 Viewing System Information ......................................................................................................................... 103

6.9.2 Viewing the System Configuration Settings ................................................................................................. 104

6.9.3 Viewing Log Messages .................................................................................................................................. 105

6.9.4 Viewing Product Software Usage and Customer Usage ...............................................................................107

6.9.5 Viewing Audited Users Operations ................................................................................................................107

6.9.6 Viewing Data Object Changes ........................................................................................................................107

6.9.7 Viewing Traces .............................................................................................................................................. 108

6.9.8 Viewing Processing Thread Dumps .............................................................................................................. 108

6.9.9 Viewing Java Thread Dumps ......................................................................................................................... 108

7 High Availability .................................................................................................................................................. 110

7.1 Downtimes ............................................................................................................................................................ 110

7.1.1 Planned Downtimes ........................................................................................................................................ 111

7.1.2 Unplanned Downtimes ................................................................................................................................... 113

7.2 Single Point of Failure ........................................................................................................................................... 113

7.3 High Availability in SAP CC 4.1 .............................................................................................................................. 115

7.3.1 HA Concepts .................................................................................................................................................. 115

7.3.2 HA Setup ........................................................................................................................................................ 116

7.3.3 High Availability for Third-Party Components ............................................................................................... 117

7.3.4 HA Setup Change ........................................................................................................................................... 117

8 Purging and Archiving ........................................................................................................................................ 118

8.1 Data Purging and Archiving .................................................................................................................................. 118

8.2 Detailed Purge and Archive in Core Database...................................................................................................... 118

8.2.1 Core Server and Core Database .................................................................................................................... 118

8.2.2 Archiving and Purging Audit Data .................................................................................................................. 119

8.3 Detailed Purge and Archive in BART Database ................................................................................................... 120

6 PUBLIC


Content

8.3.1 BART Server and BART Database ................................................................................................................ 120

8.4 Archiving Logs....................................................................................................................................................... 125

9 Software Change Management ....................................................................................................................... 126

9.1 Software Maintenance ..........................................................................................................................................126

9.1.1 One-Off Maintenance .....................................................................................................................................126

9.1.2 SAP CC Software Units .................................................................................................................................. 127

9.2 Regular Maintenance ............................................................................................................................................ 127

9.2.1 BillSoft EZTaz Technology Monthly Update Maintenance ............................................................................128

9.3 Support Package and Patch Implementation ..................................................................................................... 130

9.3.2 SAP Notes ...................................................................................................................................................... 133

9.3.3 Support Package Downloads ......................................................................................................................... 133

9.3.4 Implementation Plan ......................................................................................................................................134

9.3.5 Planning the Software Maintenance .............................................................................................................. 135

9.3.6 Testing and Validating the Technical Implementation .................................................................................. 135

9.3.7 Determining the Minimal Production Landscape .......................................................................................... 135

9.3.8 Updating the Server Systems ........................................................................................................................ 135

9.3.9 Updating the Client Applications Based on the Java Libraries ..................................................................... 140

9.3.10 Updating the Graphical User Interfaces and the IEC Application................................................................. 140

9.3.11 Post Processing............................................................................................................................................. 140

10 Troubleshooting of SAP CC.............................................................................................................................. 142

10.1 Getting Assistance ................................................................................................................................................142

10.1.2 Development and Integration Troubleshooting.............................................................................................143

10.1.3 Technical Configuration Troubleshooting .....................................................................................................144

10.1.4 Business Configuration Troubleshooting ......................................................................................................144

10.1.5 Component Troubleshooting .........................................................................................................................144

10.1.6 Log Troubleshooting ...................................................................................................................................... 145

10.1.7 Performance Troubleshooting .......................................................................................................................146

10.2 Root Cause Analysis and Exception Management in SAP Solution Manager ......................................................146

10.2.2 Working with the Root Cause Analysis Work Center in SAP Solution Manager ............................................148

10.3 Troubleshooting and Root Cause Analysis Using CA Introscope for SAP ...........................................................148

10.3.2 Troubleshooting Using CA IS Workstation Console and Investigator ...........................................................149

10.3.3 Working with Investigator ..............................................................................................................................149

10.4 Problem Determination ........................................................................................................................................ 152

10.5 System Troubleshooting ...................................................................................................................................... 154

10.6 Troubleshooting and Performance Analysis ........................................................................................................ 155

10.7 User Interfaces ...................................................................................................................................................... 157

10.7.1 Troubleshooting Problems with the User Interfaces ..................................................................................... 157

10.7.2 Troubleshooting of Core Tool ........................................................................................................................159

10.7.3 Troubleshooting of Admin+ and BART+ ....................................................................................................... 160

10.8 Advanced Troubleshooting: Tracing Tools .......................................................................................................... 160

10.8.1 Working with Traces in the Core Server System ........................................................................................... 161

10.8.2 Working with Business Process Tracing ........................................................................................................163

10.8.3 Working with End-To-End Tracing .................................................................................................................164

10.8.4 Working with Performance Traces ................................................................................................................165

10.8.5 Traces in BART Server System ......................................................................................................................165


Content PUBLIC 7

10.8.6 Diameter Server System ................................................................................................................................166

10.8.7 Communications Taxing (CT) Server System ...............................................................................................166

10.8.8 Traces in Graphical User Interfaces ...............................................................................................................166

10.8.9 Traces in IEC Applications .............................................................................................................................168

10.9 Advanced Troubleshooting: Thread Dump Files ..................................................................................................170

10.9.1 Working with Thread Dump Files ...................................................................................................................170

10.10 Errors and Exceptions ........................................................................................................................................... 171

10.11 Error Reason Codes .............................................................................................................................................. 171

10.11.1 Core Server Error Reason Codes (for Non-Business Errors) ........................................................................ 171

10.11.2 Exception Management ................................................................................................................................. 175

10.12 Detailed SAP CC 4.1 Troubleshooting .................................................................................................................. 176

11 Support Desk Management ...............................................................................................................................178

11.1 Remote Support Setup ......................................................................................................................................... 178

11.2 Problem Message Handover................................................................................................................................. 178

8 PUBLIC


Document History

1 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/cc41 .

The following table provides an overview of the most important document changes:

Version Date Description

1.0 January 2016 Initial version (SAP CC 4.1 SP 0)

1.1 May 2016 First maintenance revision (as of SAP CC 4.1 SP 1)

1.2 October 2016 Second maintenance revision (as of SAP CC 4.1 SP 2)

1.3 August 2018 Third maintenance version

2.0 2019-08-30 Fourth maintenance version



Introduction PUBLIC 9

2 Introduction

2.1 Target Audience

This SAP product document contains both high-level information on an application and business process level as well

as very detailed technical information. It is therefore intended for the following audiences:

• Operation team experts

• Technology consultants

• Application administrators

• System administrators

• Support specialists

2.2 About This Document

The Operations Guide provides a starting point to optimally maintain and run your SAP Convergent Charging software,

referred to as SAP CC in this document. Designing, implementing, and running your SAP CC 4.1 systems at peak

performance, around the clock, has never been more vital for your business success than now.

This guide provides a starting point for managing your SAP CC 4.1 software applications and maintaining and running

them optimally. It contains specific information for various tasks and lists the tools that you can use to perform them.

You use this guide during the Production Operation Phase but also during the Project Implementation Phase for

administering and monitoring the SAP CC system landscapes.

This guide also provides references to the documentation required for these tasks, so you will sometimes also need

other documents such as the Master Guide and SAP CC Application Help. See the user assistance, page [13].

This SAP product document contains the following main sections:

• Technical System Landscape, page [19]

This section lists the software components of SAP CC 4.1 and introduces the other software applications

recommended for monitoring and maintaining the landscape.

• Monitoring of SAP CC, page [38]

This section details the monitoring and tools used for SAP CC 4.1. Some installation recommendations are

provided. The trace and log files produced by the systems are also detailed in this section.

• Management of SAP CC, page [67]

This section describes the start and stop sequences, the configuration and administration of the SAP CC 4.1

system landscape. It explains how to operate backup & restore activities, archiving activities, how to manage load

balancing and high availability for the landscape.

• Software Change Management, page [126]

This section describes the maintenance of SAP CC 4.1 server systems and how to install a patch or a Support

Package (SP). It explains how to update the Taxer instances and the CT Server system with US

Telecommunication data.

• Troubleshooting of SAP CC, page [142]

10 PUBLIC


Introduction

This section describes a problem determination method for root cause analysis and provides some

troubleshooting cases.

2.3 Supportability

SAP Convergent Charging 4.1 provides functions for extended supportability. These functions are intended for use by

IT administrators, power users, operation team experts, and support specialists.

This section describes the different support tools that are available:

Feature In this Document

Monitoring Describes how to monitor different aspects of the SAP CC software product, using CA Introscope for SAP and SAP Solution Manager:

• Information:

○ SAP Solution Manager for SAP CC, page [21]

○ CA Introscope for SAP CC, page [28]

• Operations:

○ Technical Monitoring Using CA Introscope for SAP, page [44]

○ Technical Monitoring and Alerting Using SAP Solution Manager 7.1 SP13 and Later, page [40]

○ Root Cause Analysis and Exception Management in SAP Solution Manager, page [146]

○ Troubleshooting and Root Cause Analysis Using CA Introscope for SAP, page [148]

Advanced

Troubleshooting

Describes how to locate the available support tools and how to set up a connection that

enables users with remote support.

• Logging and Tracing:

○ Logging and Tracing, page [53]

• Tracing:

○ Advanced Troubleshooting: Tracing Tools, page [160]

○ Working with Business Process Tracing, page [163]

○ Working with End-To-End Tracing, page [164]

○ Working with Performance Traces, page [165]

• Supportability tools based on thread dump files

2.4 What’s New in This Document

This section highlights the main changes in this SAP product document as part of your user assistance. They relate

both to new or changed features in the SAP Convergent Charging 4.1 software deliveries and to documentation

enhancements to enrich your SAP user experience continuously.


Introduction PUBLIC 11

2.4.1 What’s New in SP 1

As of SP 1, SAP Convergent Charging provides you with the following features:

Feature in SP 1 In This Document

Software Maintenance Update procedures adapted to take into account the new tracing domains (DATA, PERF, PPI).

Troubleshooting of SAP CC New advanced tracing tools for your SAP Support Team to manage end-to-end

tracing, business process tracing, targeted tracing, and performance traces.

See:

• Advanced Troubleshooting: Tracing Tools, page [160]

• Working with Business Process Tracing, page [163]

• Working with End-To-End Tracing, page [164]

• Working with Performance Traces, page [165]

New supportability tools based on thread dump files.

2.4.2 What’s New in SP 0

As of SP 0, SAP Convergent Charging provides you with the following features:

Feature in SP 0 In This Document

• Monitoring

• Troubleshooting

New performance and health metrics about processing queue management and HMI connection mechanisms. See Technical Monitoring Using CA Introscope for

SAP, page [44].

Consult the Metric Reference and Performance Troubleshooting about the

complete metric hierarchy. This user assistance details the performance and

health metrics and provides troubleshooting information.

The Simulation Tool subcomponent is discontinued, and information is removed from this document. It is replaced by SAP Pricing and Simulation.

2.5 Document Abbreviations

The table below shows the list of abbreviations used throughout this document.

Abbreviation Meaning

APM Application Performance and Monitoring

http://service.sap.com/sap/support/notes/2269858


http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_metrics/index.html

12 PUBLIC


Introduction

Abbreviation Meaning

CA (Wily) Computer Associates

CC SAP Convergent Charging (SAP CC)

CCMS Central Computing Management System

Available in SAP Solution Manager

CDR Consumption Detail Record

CEN Central Monitoring System

CI SAP Convergent Invoicing (in SAP ERP/FI-CA)

CT SAP CC Communications Taxing Server

EM CA APM Introscope Enterprise Manager

IS CA APM Introscope

JVM Java Virtual Machine

MC SAP Management Console

MMC Microsoft Management Console

SAP furnishes a snap-in for the Microsoft Management Console (SAP MMC Snap-In)

RDBMS Relational Data Base Management System

SID SAP system Identifier

SLD System Landscape Directory

SMD SAP Solution Manager Diagnostics

Available in SAP Solution Manager

SP Support Package

SPOF Single Point of Failure

VAT Value Added Tax


Before You Start PUBLIC 13

3 Before You Start

Caution

This guide does not replace the daily operations handbooks that SAP recommends clients create for their specific

production operations.

3.1 Global Definitions

3.1.1.1 SAP Application

An SAP application is an SAP software solution that serves a specific business area like ERP, CRM, PLM, SRM, SCM,

CC.

3.1.1.2 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 with

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 possibly other third-party systems.

A business scenario is a unit that can be implemented separately and reflects the customer’s prospective course of

business.

3.1.1.3 Component

A component is the smallest individual unit considered within the Solution Development Lifecycle; components are

separately produced, delivered, installed, and maintained.

3.2 Fundamental User Assistance

SAP is the thought leader in providing people with the knowledge they need to deploy and use software successfully.

Our user assistance is a seamless part of the attractive, simple, and enjoyable experience of using SAP software. We

assist you, before you even know you need help.

For a complete list of the available guides, application help, primary help, or other product documentation related to

SAP Convergent Charging 4.1, see SAP Help Portal at the following location: http://help.sap.com/cc SAP CC 4.1

http://help.sap.com/cc


14 PUBLIC


Before You Start

Note

SAP Convergent Charging is part of the SAP Solution for commerce: SAP Hybris Billing. The end-to-end solution is

based on SAP Business Suite 7i2016 and SAP CC 4.1. Consult the central solution at:

https://service.sap.com/BRIM Resources

Refer to the O2C Integration Guide documentation for more information about the integrated features, processes,

and functions provided by the SAP solution. SAP Hybris Billing is formerly known as SAP Billing and Revenue

Innovation Management (BRIM).

Primary Help Application Help

SAP CC Admin+

SAP CC BART+

SAP CC BART Setup Tool

SAP CC BART Tool

SAP CC CAT Tool

SAP CC Config Tool

SAP CC Core Tool

SAP CC HTTP Client

SAP CC Import/Export Connector (IEC)

SAP CC Message Client

SAP CC Setup Tool

SAP CC Application Help (aka SAP CC Library)

• Scope and Feature Description

• Architecture

• Master Data

○ Pricing catalog of the digital service

○ Customer Master Data

• Processes and Functions

Guides References

SAP CC Configuration Guide

SAP CC Installation Guide

SAP CC Master Guide

SAP CC Operations Guide

SAP CC Release and Information Note (RIN)

SAP CC Security Guide

SAP CC Sizing Guide and SAP CC Sizing Guidelines

SAP CC Transition Guide (Offline Charging in SAP CI)

SAP CC Upgrade Guide

SAP CC Database References

SAP CC Error Code Reference

SAP CC Java/XML API References

SAP CC Log Message Reference and Error

Troubleshooting

SAP CC Metric Reference and Performance

Troubleshooting

SAP CC Notification Reference

SAP CC System Parameter Reference

SAP CC Web Services Documentation

3.2.1 Product Documentation Set

The product documentation set of SAP Convergent Charging 4.1 includes the following SAP documents:

SAP CC Admin+

https://service.sap.com/BRIM

https://service.sap.com/BRIM

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/terminal/adminplus.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/terminal/bartplus.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/tool/bartsetuptool.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/bart_tool/frameset.htm

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/cat_tool/frameset.htm

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/tool/configtool.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_tool/frameset.htm

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/httpClient/httpclient.html


http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/messageClient/messageclient.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/tool/setuptool.html

http://service.sap.com/~sapidb/012002523100020126472015E







https://service.sap.com/~sapidb/012002523100000449452015E




http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_dbref/index.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_errors/index.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_javadoc/index.html?overview-summary.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_messageids/index.html




http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_notifications/index.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_paramref/index.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_wsdoc/index.html


http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/terminal/adminplus.html



SAP CC Application Help (aka SAP CC Library)

SAP CC BART+

SAP CC BART Setup Tool

SAP CC BART Tool

SAP CC CAT Tool

SAP CC Config Tool


SAP CC Core Tool

SAP CC Database References

SAP CC Error Code Reference

SAP CC HTTP Client

SAP CC Import/Export Connector (IEC)

SAP CC Installation Guide

SAP CC Java/XML API References

SAP CC Log Message Reference and Error Troubleshooting

SAP CC Master Guide

SAP CC Message Client

SAP CC Metric Reference and Performance Troubleshooting

SAP CC Notification Reference

SAP CC Operations Guide

SAP CC Release and Information Note (RIN)

SAP CC Security Guide

SAP CC Setup Tool

SAP CC Sizing Guide and SAP CC Sizing Guidelines


SAP CC Transition Guide (Offline Charging in SAP CI)

SAP CC Upgrade Guide

SAP CC Web Services Documentation

3.3 Important SAP Notes

This section summarizes the most important SAP Notes referred to in this guide.


http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/terminal/bartplus.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/tool/bartsetuptool.html



http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/tool/configtool.html


http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_tool/frameset.htm

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_dbref/index.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_errors/index.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/httpClient/httpclient.html



http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_javadoc/index.html?overview-summary.html



http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/messageClient/messageclient.html


http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_notifications/index.html




http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/tool/setuptool.html






http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_wsdoc/index.html

16 PUBLIC


Before You Start

3.3.1 CA APM Introscope 9.x

SAP Note Number Title

797147 Introscope Installation for SAP Customers

This SAP Note is the central note of CA Introscope (IS) for SAP, a specialized

component of SAP Solution Manager:

• Implementation

• Installation

1579474 Management Modules for Introscope delivered by SAP

SAP delivers some specialized Management Modules for the CA Introscope

for SAP component and its Enterprise Manager (EM):

• Modules for CA Introscope Enterprise Manager 9.7

• Modules for CA Introscope Enterprise Manager 9.5

• Modules for CA Introscope Enterprise Manager 9.1.5

Note

This SAP Note includes the details of the predefined enhancements to

CA Introscope Enterprise Manager (EM). SAP delivers these additional

modules in a particular package. The package includes all the necessary

Introscope Management Modules.

You need the following modules for SAP CC:

• SAP Navigation

• SAP SRM CRM that includes the necessary binary files for SAP

Convergent Charging

1453216 CA Introscope for SAP Convergent Charging

• Implementation of CA Introscope for SAP

• Installation

• Configurations

Note

This SAP Note includes the necessary installation guides for SAP

Convergent Charging release 4.1. Refer to the document dedicated to

SAP CC 4.1 with CA Introscope 9.7 and SAP Solution Manager 7.1 as of

SP13.

2138309 Introscope 9.7 Release Notes



https://service.sap.com/sap/support/notes/1579474







2071100 Introscope 9.5 Release Notes

1565954 Introscope 9 Release Notes

1280961 1280961 - SAP Extended Diagnostics by CA Wily

SAP Extended Diagnostics by CA Wily contains a full reseller version of CA

Introscope.

3.3.2 SAP Solution Manager 7.1


1875021 System Monitoring Setup for SAP Convergent Charging

• Implementation of System Monitoring for SAP CC in SAP Solution

Manager 7.1 as central monitoring system (CEN)

○ How to setup System Monitoring for SAP CC 4.1 system in SAP

Solution Manager 7.1 SP12 and later

○ How to setup System Monitoring for SAP CC 3.0 system in SAP

Solution Manager 7.1 SP6

3.3.3 SAP JVM


1367871 Time zone updates for SAP JVM

3.3.4 DBA Cockpit


1265134 DBA Cockpit: Connecting a remote database (Oracle)

1388700 DBA Cockpit: Setup in Solution Manager for MS SQL Server

1664432 DBA Cockpit: SAP HANA database as remote database

1532253 SYB: Remote DB Monitoring for Sybase ASE






http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1367871&_NLANG=en&_NVERS=0




18 PUBLIC


Before You Start


1267189 DBA Cockpit: IBM DB2 as Remote Database

3.4 Additional Information

For more information about specific topics, see the quick links as shown in the table below:

Content Quick Link on SAP Sites

Monitoring http://www.sdn.sap.com/irj/sdn/netweaver

SAP Solution

Manager

General information:

https://support.sap.com/solutionmanager

http://help.sap.com/solutionmanager71

Installation and operations:

https://service.sap.com/instguides SAP Components SAP Solution Manager Guides

Functional documentation:

http://help.sap.com Application Lifecycle Management SAP Solution Manager SAP

Solution Manager 7.1 Application Help SAP Library (English) for Solution Manager 7.1 SP13

Solution

Manager

Diagnostics

General information about end-to-end Root Cause Analysis (RCA):

https://service.sap.com/diagnostics

Functional documentation:

http://help.sap.com Application Lifecycle Management SAP Solution Manager SAP

Solution Manager 7.1 Application Help SAP Library (English) for Solution Manager 7.1 SP13

Application Operations Root Cause Analysis & Exception Management

Security http://service.sap.com/security

Security Guides

http://service.sap.com/securityguide

Related SAP

Notes

http://support.sap.com/notes

Released Platforms

http://service.sap.com/platforms

SAP Help

Portal


User assistance and product documentation of SAP CC available for each major release


http://www.sdn.sap.com/irj/sdn/netweaver

https://support.sap.com/solutionmanager


https://service.sap.com/instguides


http://help.sap.com/






http://help.sap.com/saphelp_sm71_sp13/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm







http://help.sap.com/saphelp_sm71_sp13/helpdata/en/92/c65043f2004b098fda16b8e56ef702/content.htm

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/92/c65043f2004b098fda16b8e56ef702/content.htm

http://service.sap.com/security

http://service.sap.com/securityguide

http://support.sap.com/notes

http://service.sap.com/platforms



Technical System Landscape PUBLIC 19

4 Technical System Landscape

A system landscape consists of a number of hardware and software components that depend on each other regarding

installation, software update, and demands on interfaces.

The system landscape contains all the SAP Systems that you have installed. It can consist of several system groups,

whose SAP CC systems are linked by transport routes. These groups include the development systems (DEV), quality

assurance systems (QAS), and the production systems (PRD).

A separate and dedicated system landscape can be the production landscape.

4.1 Software Component Matrix

SAP Convergent Charging 4.1 is a Java-based software. It includes several mandatory and optional components.

4.1.1 Java Components

The Java components of your SAP CC 4.1 software include several server systems and graphical user interfaces.

4.1.1.1 Server Systems

SAP CC 4.1 Component Description GUI Real Time

(Online

Charging)

Batch

Mode

(Offline

Charging)

Core Server (multi-instance)

• Server system

• Admin. utilities

Rating and Charging Engine X X X

Diameter Server

• Server system

Online Mediation and Credit

Control

(X)

BART Server

• Server system


Offline Mediation (X) (X)

Communications Taxing Server (CT)

• Server system

US Telecommunication Tax Management Services (via RFC)

(X)

20 PUBLIC


Technical System Landscape

4.1.1.2 Graphical User Interfaces

SAP CC 4.1 Component - Programs Related Server System Comment

Core Tool

• Core Tool

• Admin+

Core Server

BART Tool

• BART Tool

• BART+

BART Server

CAT Tool

Connector Administration Tool (CAT)

IEC Application (not a server

system)

Optional: Remote IEC (for

monitoring purpose)

Standalone program

These graphical user interfaces are fat client programs based on Java swing technology.

Note

Some console or command-line user interfaces are available for administering the server systems. They are

included in the relevant components.

4.1.1.3 Other Applications

SAP CC 4.1 Component Description Related Server Systems

IEC (Import/Export Connector) Offline Mediation Acquisition

and Preparation

• Core Server

• BART Server

• Other (depending on

implementation)

4.1.1.4 JSEE and JVM

For technical reasons, both SAP JVM 32-bit and SAP JVM 64-bit are installed on MS Windows Intel 64-bit hosts by the

SAPinst user interface of SAP CC 4.1.

For US installations with the US Telecommunication Taxes, note that SAP CC Core Server (Taxer instance type) and

CT Server have also a particular installation.



Caution

Do not change these installations. Consult the SAP CC Installation Guide for details about the installation of JSEE

on your platform.

4.2 Related Documentation

You can find more information about the technical system landscape in SAP Help Portal at help.sap.com/cc41.

4.3 System Landscape Directory (SLD)

System Landscape Directory (SLD) of SAP NetWeaver is the central information repository for your system landscape.

It contains information about technical systems, landscapes, business systems, products, and software components

in your system landscape. You must configure manually SAP CC systems to connect to SLD and send data

periodically.

All the server systems of SAP CC 4.1 can send information about installed hardware and software components in your

system landscapes to facilitate the central configuration of the landscape (applications, machines):

• Core Server

• BART Server

• Diameter Server

• Communications Taxing (CT) Server

The SAP CC systems update regularly the System Landscape Directory repository. Installation information is available

in SAP Solution Manager.

Note

During the implementation project, refer to the:

• SAP CC Installation Guide for more information about the initial preparations and installation

• SAP CC Configuration Guide for more information about the Customizing activities and manual procedures

You can find the latest version in SAP Help Portal at: http://help.sap.com/nw70 SAP NetWeaver 7.0 SAP

NetWeaver 7.0 Library (English) SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle

Management by Key Capability Software Life Cycle Management System Landscape Directory

4.4 SAP Solution Manager for SAP CC

SAP Solution Manager is a platform that provides integrated content, tools, and methodologies that you need to

implement, support, operate, and monitor your enterprise´s solutions from SAP.

SAP Solution Manager enables you to accelerate and optimize the implementation process and access full support and

continuous improvement offerings from SAP.

With SAP Solution Manager, you can:


http://help.sap.com/nw70

http://help.sap.com/nw70

22 PUBLIC



• Minimize risk and increase the reliability of your IT solutions

• Reduce total cost of ownership (TCO) throughout the solution life cycle

• Manage your core business processes and link business processes to the underlying IT infrastructure

• Get more on your return-on-investments (ROI), because it supports both SAP and non-SAP software

Note

To benefit from some important features of SAP Solution Manager, you need to install the infrastructure for CA

Introscope third party. Refer to the CA Introscope for SAP CC section in this document, page [28].

4.4.1 Infrastructures of SAP Solution Manager

You use the following infrastructures of SAP Solution Manager to manage the server systems of SAP Convergent

Charging 4.1:

Monitoring

Infrastructure

Description Key Functions

Technical

Monitoring and

Alerting

This infrastructure helps you to improve the performance and

health of SAP CC systems in complex, heterogeneous landscapes.

It enhances the traditional CCMS-based monitoring infrastructure

with advanced features:

• Simplified maintenance of the diagnostic agents that are

automatically updated and configured

• System landscape awareness (landscape setup and changes

are automatically detected and updated)

• Self-monitoring is available for SAP Solution Manager

landscape and infrastructure components

• Grouping metrics and alerts prevents alert flooding

• Graphical overview of landscape status

Note

SAP Convergent Charging 4.1 does not support the following

features:

• Simplified configuration of the managed systems

• Mass maintenance (configuration can be done on

multiple managed systems at the same time using

template concept)

• Central administration with operation tasks performed

from the Administration Work Center

Analysis Tools

Technical Monitoring

Alerting Framework

Alert Inbox

Technical Monitoring

Alert Inbox

Agent Framework The agent framework manages diagnostic agents installed in all managed SAP CC systems and back-end database systems,

centrally.



Monitoring

Infrastructure

Description Key Functions

Special: CA Introscope for SAP

The Enterprise Manager (EM) acts as the central repository for all Introscope performance data and metrics collected in an

application environment. The EM system processes performance

data and makes it available to users for production monitoring and

diagnosis.

4.4.1.1 Recommendation by SAP

Install and use CA Introscope and SAP Solution Manager for your SAP CC 4.1 system landscapes. Configure SAP

Solution Manager with the agent framework and CA Introscope infrastructures.

CA Introscope is delivered as a component of SAP Solution Manager, you shall consider installing the correct version

regarding to your SAP CC release and support package number.

4.4.1.2 Related Documentation (SAP Solution Manager 7.1)

For more information about SAP Solution Manager 7.1, consult in SAP Help Portal at:

http://help.sap.com/solutionmanager71 Application Help SAP Library (English), SP13 SAP Solution Manager

Infrastructures

Refer to the following topics in SAP Help Portal:

• Agent framework

• Introscope

4.4.2 Application Operations

Application Operations in SAP Solution Manager provides all capabilities for central monitoring, message alerting,

analysis, and administration of SAP CC and SAP solutions. It helps you to reduce TCO by predefined content and

centralized management tools for all aspects of operations in SAP Solution Manager.



http://help.sap.com/saphelp_sm71_sp13/helpdata/en/dc/646a53e744e047e10000000a441470/content.htm?frameset=/en/9e/596617c91c4e6f84a2f0181a6402c3/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=123&show_children=false




http://help.sap.com/saphelp_sm71_sp13/helpdata/en/f5/0b1ce518c549199f272d0dd0b93613/content.htm?frameset=/en/34/68ec17302d4d94a3a6053ae690db1d/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=442&show_children=false

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/21/3ff439b43b45fb8381d3d9c5cf6267/content.htm?frameset=/en/34/68ec17302d4d94a3a6053ae690db1d/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=450&show_children=false

24 PUBLIC



Application

Operations

Description Available Work Center

System and Application

Monitoring

You can monitor the status of complex SAP system landscapes and manage alerts using the End-to-End

Monitoring and Alerting infrastructure (MAI):

• System, database, and host monitoring

• Alert inbox

Note

SAP Convergent Charging 4.1 does not support the

following features:

• End-user experience monitoring

• Integration monitoring

• Job monitoring and business intelligence

monitoring

Technical Monitoring Work Center

Technical

Analytics and

Dashboards

You can use interactive and technical reporting functions

to run reports on various aspects across solutions. Use

application operations dashboards to display the

availability and performance of your managed systems:

• Interactive reporting

• Application dashboard

○ System availability

○ System performance

○ End-user experience reporting

• Technical reporting

○ SAP EarlyWatch Alert

○ Service level reporting

○ Service Data Control Center

○ Solution reporting

○ Reporting in the System Monitoring Work Center

Technical Monitoring Work

Center

Data Volume Management

(DVM)

You can monitor the data volume in your system landscape and reduce total operating costs by

decreasing the size of the databases and the monthly

increase in data.

Data Volume Management Work Center



Application

Operations

Description Available Work Center

Technical Administration and

Guided

Procedures

You can perform efficient planning, implementation, execution, and reporting of the day-to-day operational

activities.

You can create guided procedures to support processes

that are performed periodically. You can use guided

procedures, for example, to speed up and simplify

processes.

Technical Administration Work Center

Root Cause

Analysis and

Exception

Management

You can analyze the root cause of an incident and provide

solutions for distributed and multi-technology solutions

using a top-down approach.

You can manage the following reports:

• End-to-End Analysis

• System Analysis

• Host Analysis

• Database Analysis

Root Cause Analysis Work Center

This work center is the central

access to functions and methods

for monitoring your solutions and

accelerating problem solving.

This improves the availability of

your solutions.


http://help.sap.com/solutionmanager71 Application Help SAP Library (English), SP13 Application Operations

4.4.3 Work Centers Used for SAP CC

SAP Solution Manager provides the necessary central work environments in the form of specialized work centers.

These work centers are the central access to functions and methods for monitoring your SAP solutions and

accelerating problem solving. This improves the availability of your solutions.

Work Center Description

Technical

Monitoring

The Technical Monitoring work center provides tools and capabilities for monitoring the SAP

CC system landscape:

• Technical monitoring inbox alert: alerts from the system monitoring area

• System monitoring: current status of systems, databases, and hosts

See also: Technical Monitoring and Alerting Using SAP Solution Manager 7.1 SP13 and Later,

page [40]



http://help.sap.com/saphelp_sm71_sp13/helpdata/en/f7/edd478213449dba4e49ad601966aab/content.htm?frameset=/en/d6/b729db0a2a41589e9fa8f25eba7fcb/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=1470&show_children=false


26 PUBLIC




Root Cause Analysis The Root Cause Analysis work center is the central access to functions and methods for

monitoring your solutions and accelerating problem solving:

• End-to-end analysis: tools to perform cross-component root cause analysis

• System analysis: tools to perform system-specific root cause analysis (log viewer,

monitoring consoles of CA Introscope)

This improves the availability of your solutions.

See also: Root Cause Analysis and Exception Management in SAP Solution Manager, page

[146]

SAP Solution Manager

Configuration

(transaction

SOLMAN_SETUP)

You use this work center to configure SAP Solution Manager immediately after installation, following an upgrade, or after implementing a Support Package (SP) or a patch level. SAP

Solution Manager leads you through the process using guided procedures and provides a

constant overview of the progress of your configuration.

• In Managed System Configuration, you configure a Technical System for each SAP CC

system cluster registered in SAP SLD

• In Technical Monitoring, you assign monitoring templates to the managed technical

systems; In SAP Solution Manager, each managed technical system consists of type

technical instance, database, and host.

SAP Solution

Manager

Administration

This work center is the central access point for all the information and functions you need to

run the SAP Solution Manager. You set up and manage solutions, projects and systems, and

can perform user functions and common administration tasks.

You use this work center to setup the system monitoring of SAP Convergent Charging based

on CA Introscope (IS), a specialized software for application and performance monitoring.

Important Note

In the Infrastructure view of SAP Solution Manager Administration work center, you have

central access to all systems in your system landscape. You choose a tool, to ensure that

the infrastructure is provided. You can create or edit technical systems and install

additional CA Introscope Enterprise Manager systems or instances. CA Introscope (IS) is

the monitoring application used to monitor the server system of SAP Convergent

Charging.



Work Centers

4.4.4 Monitoring and Alerting

4.4.4.1 Templates for SAP CC

As of SP12 of SAP Solution Manager 7.1, End-to-End Monitoring and Alerting Infrastructure (MAI) in System Monitoring

contains various predefined templates for SAP Convergent Charging 4.1. These predefined templates contain the







metrics, events, and alerts (MEA), and their attributes. They also contain settings for notifications when an alert

occurs.

Note

The metric definitions rely on CA Introscope technology. SAP CC provides you with the Metric Reference and Performance Troubleshooting documentation that is your central information access for monitoring or

troubleshooting problems.

You can base your own templates on the templates delivered by SAP and adjust them to your requirements. The following templates are available:

Template in SAP Solution Manager Description Managed Object

Type

SAP Convergent Charging 4.5 (*) SAP CC Core Server systems in the system landscape

Technical System (**)

SAP Convergent Charging 4.5 BulkLoader Bulkloader instances of the Core Server

systems

Technical

Instance

SAP Convergent Charging 4.5 Dispatcher Dispatcher instances of the Core Server systems

Technical Instance

SAP Convergent Charging 4.5 Rater Dispatcher instances of the Core Server

systems

Technical

Instance

SAP Convergent Charging 4.5 Taxer Taxer instances of the Core Server systems Technical

Instance

SAP Convergent Charging 4.5 Updater Updater instances of the Core Server systems Technical Instance

(*) The naming convention includes a number that relates to the technical version number of your SAP Convergent Charging

software: “4.5” refers to the commercial release 4.0 of SAP CC.

(**) In SAP Solution Manager, the technical system consists of the SAP CC system and its back-end database system.

For more information about templates in SAP Solution Manager 7.1, consult in SAP Help Portal at the following

location: http://help.sap.com/solutionmanager71 Application Help SAP Library (English), SP13 SAP Solution

Manager Infrastructures Technical Monitoring and Alerting Using Templates . You can create and edit custom templates, assign and activate templates.

4.4.4.2 Technical Operations for SAP CC

View the technical operations for SAP Convergent Charging:

• Technical Monitoring and Alerting Using SAP Solution Manager 7.1 SP13 and Later, page [40]

• Root Cause Analysis and Exception Management in SAP Solution Manager, page [146]









http://help.sap.com/saphelp_sm71_sp13/helpdata/en/88/823853c4986957e10000000a44538d/content.htm

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/88/823853c4986957e10000000a44538d/content.htm

28 PUBLIC



4.4.4.3 Related Information

For more information about the template, consult information about in SAP Solution Manager 7.1, consult in SAP Help

Portal at: http://help.sap.com/solutionmanager71 Application Help SAP Library (English), SP13 Application

Operations Work Centers SAP Solution Manager Configuration Using Templates .

For more information about the templates, consult information about in SAP Solution Manager 7.1, consult in SAP Help

Portal at: http://help.sap.com/solutionmanager71 Application Help SAP Library (English), SP13 Template

Management .

4.4.5 Root Cause Analysis

To allow for identification, analysis, and resolution of problems, SAP provides component-specific RCA content for

SAP CC 4.1 in combination with SAP Solution Manager 7.1. You can set up Root Cause Analysis after you set up your

SAP CC system landscape.

4.4.5.1 Technical Operations for SAP CC



• Troubleshooting and Root Cause Analysis Using CA Introscope for SAP, page [148]

4.4.6 Related Information

Topic Guide/Tool Location

SAP Solution

Manager

SAP Solution

Manager

Diagnostics

Introscope Setup

Guide

In SAP Service Marketplace:

https://service.sap.com/instguides Installation & Upgrade

Guides SAP Components SAP Solution Manager Release 7.1 6

Additional Guides - Introscope Introscope Setup Guide 9.7

4.5 CA Introscope for SAP CC

SAP delivers a packaged solution that provides you with application performance management tools for SAP

Convergent Charging 4.1. This solution is based on the CA Introscope 9.x software products and supports Java-based

applications.

CA Introscope (IS) allows the technical monitoring of SAP CC in live production environments.







http://help.sap.com/saphelp_sm71_sp13/helpdata/en/88/823853c4986957e10000000a44538d/content.htm?frameset=/en/af/b0ddec01e34180886934bd7dcd6d58/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=2302&show_children=false

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/88/823853c4986957e10000000a44538d/content.htm?frameset=/en/af/b0ddec01e34180886934bd7dcd6d58/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=2302&show_children=false



http://help.sap.com/saphelp_sm71_sp13/helpdata/en/e9/fe6e05e160423891d48cb9f15a2b55/content.htm?frameset=/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=994&show_children=falsehttp://help.sap.com/saphelp_sm71_sp12/helpdata/en/f7/edd478213449dba4e49ad601966aab/content.htm?frameset=/en/d6/b729db0a2a41589e9fa8f25eba7fcb/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=1470&show_children=false






http://service.sap.com/solmaninstguides




• It provides a central server system that collects performance data pushed from agents located in the monitored

SAP CC systems and makes metric data available to the monitoring consoles and to SAP Solution Manager.

• User interfaces provide specialized dashboards that enable to monitor manually the system health, performance,

and stability. This is the starting point for detecting issues and investigating a root cause analysis.

Note

CA IS is a component of SAP Solution Manager as an additional infrastructure.

CA Introscope for SAP CC

Note

SAP provides you with the necessary CA IS instrumentation and console dashboards dedicated to the support of

SAP Convergent Charging 4.1.

• The specialized instrumentation is available in the SAP IS Agent, which is a component of SAP Solution

Manager. By default, the installation of SAP CC also includes this agent.

• SAP CC cannot include the latest version of this agent so you should consider checking the correct version

available for your SAP CC release and SP number.

• The dashboards and console alerts are available in an additional installation package that includes all the

Introscope Management Modules developed by SAP. Make sure that you install the Management Module that

includes the monitoring dashboards specialized for SAP Convergent Charging: SAP_SRM_CRM (Products

for "SRM and CRM"). Refer to the SAP Note 1579474 - Management Modules for Introscope delivered by

SAP or to the installation considerations in this document.

• The primary help is available in the online documentation of the SAP SRM CRM management module. Once

installed, it is available as a Web application. The topics dedicated to SAP Convergent Charging are named:

Introscope for SAP CC



30 PUBLIC



4.5.1 Features

CA Introscope for SAP provides you with the:

• Necessary components customized for SAP CC and for SAP Solution Manager

• Instrumentation agents and probes specialized for SAP CC and Java applications

• Monitored metric definitions (throughput, latency, other performance data)

• Console dashboards including graphs and alert indicators

With CA IS, you can:

• Operate the technical monitoring

• Determine the source of problems quickly

• Conduct incident triage by identifying the source of the issues (front-end systems, internal components,

database, host resources, file system)

• Perform root cause analysis by isolating the problems and determining where to investigate

Note

If you would like to increase the benefits of CA Introscope through custom dashboards and instrumentation, or

extend CA Introscope's capabilities with Introscope Powerpacks™, you can purchase SAP Extended Diagnostics by

CA APM/Wily through SAP. Refer to SAP Note 1280961 - SAP Extended Diagnostics by CA Wily.

4.5.2 CA Introscope in SAP Solution Manager

CA Introscope (IS) is integrated with SAP Solution Manager 7.1 to enable application analysis and operations directly in

the work centers of SAP Solution Manager:

• Stability analysis

• Technical and performance monitoring

• Message alerting

• Root cause analysis

Note




4.5.3 CA Introscope Components

In an SAP system landscape, the available components of CA IS are Enterprise Manager, Agent, Workstation, and

WebView:




CA IS Component Description

Enterprise Manager The CA IS Enterprise Manager (EM) system acts as the central repository for all Introscope

performance data and metrics collected in the Java application environment of the SAP CC

Core Server systems and other systems.

The EM system processes performance data and makes it available to IT administrators,

SAP CC administrators, and to support specialists for production monitoring and diagnosis.

Agent CA Introscope agents collect and report performance metrics from the various components

inside the running instances of the SAP CC Core Server systems in the system landscape.

One agent is deployed per Java Virtual Machine (JVM) process that is dedicated to execute

an instance in an SAP CC system.

Workstation CA IS Workstation provides a user interface to control the monitored SAP CC Core Server systems. CA IS Workstation accesses performance metrics managed by CA IS Enterprise

Manager.

They can view performance metrics and alert indicators in monitoring dashboards. If you

want to customize alerts and views to represent your unique environment, you need a

license extension.

CA IS Workstation includes the following features:

• Monitoring Console

• Investigator

• Management Module Editor

• Transaction Trace Session

Note

You can directly access to this user interface in the work centers of SAP Solution

Manager.

WebView CA IS WebView is a Web-based user interface to display console dashboards and performance metrics collected by the CA IS Enterprise Manager system. Introscope's

customizable dashboards and Explorer tree views for authorized SAP users run in a browser

interface, so that critical information can be viewed by those who need it anytime, anywhere.

It includes the following features:

• Console to view performance data presented in dashboards

• Investigator to view performance metrics by selecting items from the Investigator tree

• Transaction Viewer to view transaction trace event data

Notes

• You can access to this user interface in the work centers of SAP Solution Manager.

• You cannot create customized dashboards or run reports.

32 PUBLIC



4.5.4 Management Module for SAP CC

The delivered SAP_SRM_CRM (Products for "SRM and CRM") management module provides all the monitoring

dashboards specialized for SAP Convergent Charging. This module includes the necessary elements that contain and

organize metric data with monitoring logic, for presentation in the CA IS Workstation user interface:

• Metric definitions

• Metric grouping definitions (and few calculators)

• Console dashboards with graphs and alert indicators

4.5.4.1 Metrics for SAP CC

A metric is a measurement of application performance. It is a performance indicator. CA IS Enterprise Manager (EM)

compiles or computes the performance metrics by reusing performance raw data reported by the local agents. The

metrics can be monitored and recorded both in CA IS Enterprise Manager (EM) and SAP Solution Manager.

The basic metrics are:

Basic Metric Description Example

Average Response

Time

Average treatment execution time in milliseconds,

latency (the lower, the better)

Typically, this is the latency.

Errors Per Interval Number of exceptions thrown during the treatment executions per time interval (none, the better)

Responses Per

Interval

Number of treatment executions per time interval,

throughput (the higher, the better)

Typically, this is the throughput.

Stall Count Number of treatments or executions started but that have not completed within a defined time threshold

Notes

• If a treatment or an execution is counted as

stalled, this does not mean that it is interrupted

and will never be completed, but that its

processing exceeded a configured time

threshold. This is not a timeout that relates to an

error.

• By default, the stall threshold is set to 30

seconds for each instance of the SAP CC Core

Server systems in the system landscape. This is

a global configuration in the CA IS Agent

profiles.

Refer to the CA IS documentation for more information about the available metrics.



Note

During the implementation project, refer to the:

• SAP CC Installation Guide for more information about the initial preparations and installation

• SAP CC Configuration Guide for more information about the Customizing activities and manual procedures

4.5.4.2 Metric Groupings, Alerts, and Calculators

The delivered SAP_SRM_CRM (Products for "SRM and CRM") management module provides the customized

elements:

• Custom metric groupings that specify which metrics to act upon; used as building blocks for elements such as

alerts.

• Custom console alerts of possible problems in the SAP CC application, generated by comparing metric values

against predefined threshold values and producing a status.

• Custom calculators that sum or averages metric data to produce custom metrics for the technical monitoring of

SAP CC.

Note

The alert concept of CA Introscope differs from the alert concept in SAP Solution Manager:

• In CA IS, an alert is a visual information during manual monitoring; about the initial preparations and

installation

• In SAP Solution Manager, an alert refers the automated message alerting function that allows you to start

necessary investigations

4.5.4.3 Console Dashboards, Alert Indicators, and Graphs

The management module provides the customized console dashboards that allow you to monitor the SAP CC Core

Server systems in your system landscape:

Console Dashboard Description Console Alert

Central Dashboards The CC Overview and the CC Triage dashboards are the starting points to monitor

the Core Server systems.

CC Overview Provides an instantaneous view of the monitored system health. It allows navigating

through other specialized dashboards that

monitor different performance data and

metrics of the Core Server systems in your

SAP system landscape.

This central dashboard contains an alert indicator for each specialized

dashboard to view the system

health state quickly.

34 PUBLIC



Console Dashboard Description Console Alert

CC Triage Provides an overview of the monitored system

health and performance. It includes a visual

summary of the complete system: instances

of the monitored Core Server system,

communications with frontend (mediation,

BART Server) and backend systems (Core

Database, data files).

Note

In an integrated SAP Solution scenario

with SAP ERP/FI-CA and SAP CRM of SAP

Business Suite, consider also the SAP JCo

communications and the corresponding

dashboard (see CC JCo) that is not

available in the CC Triage dashboard.

This central dashboard contains

the global alert indicators that are

necessary for each specialized

dashboard to view the system

health state quickly.

Specialized Dashboards

CC Incoming Request Provides the performance (throughput, latency) and health (errors) of the

communication interfaces with the front-end systems or applications

CC Outgoing Request Provides the performance (throughput, latency) and health of the internal components that prepare the communications with the back-end systems including

file systems

CC Internal Activities Provides the activity of the internal schedulers

CC CPU and Memory Provides the performance and health of the CPUs, host memory, and Java Garbage Collection (GC) processing

CC Cache Provides the performance and health of the data caches used in some specific

instances types to optimize the business operations (rating and charging, data

provisioning)

CC JDBC Provides the performance and health (throughput, latency) of the communication

interfaces with the back-end database systems

CC JCo In an integrated SAP Scenario with SAP ERP/FI-CA or SAP CRM, provides the performance and health (throughput, latency) of the JCo/RFC communication

interface with the SAP ERP and SAP CRM systems



Console Dashboards in CA IS for SAP CC

4.5.5 Technical Operations for SAP CC


• Technical Monitoring Using CA Introscope for SAP, page [44]



4.5.6.1 Documentation and Community

For general information about the installation, configuration, and use of CA Introscope, visit SAP sites at the following

locations:


Installation of CA Introscope delivered

by SAP

Introscope for SAP Setup Guide

SAP Service Marketplace:


Guides SAP Components SAP Solution Manager Release 7.1

Additional Guides - Introscope Introscope Setup Guide 9.1.5

SAP Community Network (SAP SCN):





36 PUBLIC




SAP Community Network (SCN) is the social network for SAP professionals.

SAP SCN has its own terms of use governing the usage of which you have to

accept prior to access of any SCN information.

http://scn.sap.com Spaces Technical Operations Root Cause

Analysis & Exception Management RCA Wiki Tools in Root Cause

Analysis Introscope - Wiki Introscope Setup Guide 9.1.5

SAP Solution

Manager

Diagnostics

Installation Guide SAP Service Marketplace:


Guides SAP Components SAP Solution Manager Release 7.1 6

Additional Guides - Introscope Introscope 9.7 for SAP - Setup Guide

Troubleshooting of CA Introscope

Introscope Troubleshooting

SAP Community Network (SAP SCN):





Analysis & Exception Management RCA Wiki Tools Introscope -

Wiki Troubleshooting

Direct link: Introscope Troubleshooting (wiki in SAP SCN)

Introscope for SAP Primary Help SAP documentation for the management modules as a web

application

It is available in the directory <EM_FOLDER>/webapps/ where

<EM_FOLDER> is the installation directory of the IS Enterprise

Manager system.

Wiki in SAP SCN SAP Community Network:





Analysis & Exception Management RCA Wiki Tools Introscope -

Wiki

Direct link: Introscope for SAP

Introscope for SAP CC

Primary Help The online documentation of the SAP SRM CRM management module includes the information about the dashboards, console alerts, and

metric groupings that relate to the technical monitoring of SAP

Convergent Charging.

CA Documentation

http://scn.sap.com/

http://scn.sap.com/

http://wiki.scn.sap.com/wiki/display/TechOps

http://wiki.scn.sap.com/wiki/display/TechOps

http://wiki.scn.sap.com/wiki/display/TechOps/RCA_Home


http://wiki.scn.sap.com/wiki/display/TechOps/RCA_Introscope_Home






http://scn.sap.com/

http://scn.sap.com/








http://scn.sap.com/

http://scn.sap.com/











CA Introscope

Workstation

User Guide Refer to CA Support:

CA APM Introscope Workstation User Guide 9.1

CA Introscope

WebView

User Guide Refer to CA Support:

CA APM Introscope Webview User Guide 9.1

4.6 SAP Management Console

The SAP Management Console (SAP MC) provides a common framework for centralized system management. It

allows you to monitor and perform basic administration tasks on the SAP system centrally, thus simplifying system

administration.

Using the SAP MC you can:

• Monitor and control (start, stop, or restart) the SAP systems, ABAP, and Java instances with a single tool.

• Display SAP system log and trace files, start profiles, instance parameters, the system environment, SAP

environment, and so on.

• Display and control Java and ABAP processes.

• Monitor system alerts.

• Save the current console configuration in a file to reuse it later or to forward it to other users.

• Start third-party tools (such as Telnet), if available, to manage an application server.

The SAP Management Console in the SAP NetWeaver AS is available in two modes:

• SAP Management Console

○ The SAP MC is a Java applet that can be run from any web browser supporting Java. Thus, you can administer remote systems without needing a local installation.

• Standalone SAP Microsoft Management Console

○ SAP has developed the SAP Systems Manager snap-in which allows you to monitor, start or stop the SAP

system centrally from the SAP Microsoft Management Console (SAP MMC.) The SAP MMC is available for

Windows only.

More information: Microsoft Management Console: Windows

http://help.sap.com/erp2005_ehp_04/helpdata/EN/63/0f5bc7bc3611d2890d0000e8200722/frameset.htm

38 PUBLIC


Monitoring of SAP CC

5 Monitoring of SAP CC

Within the management of SAP Technology, real-time monitoring is an essential task during production operations or

when finalizing the project implementation. Deploying a monitoring architecture enables the system administrators

and operation teams to get an overview of the SAP system landscape at a glance and provides an infrastructure to

gather and manage system information.

Monitoring works as an early warning system that monitors and displays the status of multiple systems and

independent business components.

The main features of the monitoring architecture are:

• User-definable alert monitors for critical system events

• Method assignments to analyze alerts and react to them automatically

• Performance system to display recent performance data graphically

5.1 Monitoring Installation and Setup

Refer the following activities and installation considerations:



5.2 Component Specific Monitoring

The following table lists the components of SAP Convergent Charging 4.1 and the third-party components to monitor in

your SAP system landscape:

Component and System Product Monitor

Core Server

• SAP CC system

• Hosts

SAP CC 4.1 • Technical monitoring:

○ Technical Monitoring and Alerting Using SAP Solution

Manager 7.1 SP13 and Later, page [40]

○ Technical Monitoring Using CA Introscope for SAP, page

[44]

○ Manual Monitoring, page [48]

• Error monitoring

BART Server

• SAP CC system

• Host

Monitoring of business operations, page [52]

• Offline acquisition

• Offline charging


Monitoring of SAP CC PUBLIC 39

Component and System Product Monitor

Diameter Server

• SAP CC system

• Hosts

CT Server

• SAP CC system

• Host

Core Database

• Database system

• Hosts

Database

Technology

Database monitoring, page [50]

BART Database

• Database system

• Hosts

IEC Database

• Database system

• Host

5.3 Monitoring

5.3.1 Technical Monitoring

Technical monitoring consists in monitoring the performance and health of systems in complex, heterogeneous

landscapes. It targets the infrastructure levels of the SAP CC systems:

• Communications with front-end and back-end and systems

• Internal important activities (data cache management, intra-communications)

This monitoring is based on metrics available in CA Introscope for SAP CC, page [28]. SAP CC provides you with the

Metric Reference and Performance Troubleshooting documentation.

Consider the following activities:



• Manual Monitoring, page [48]


40 PUBLIC




SAP recommends that you define and implement automated monitoring for technical monitoring and alerting. Refer to

the Technical Monitoring and Alerting Using SAP Solution Manager 7.1 SP13 and Later section, page [40].

5.3.2 Performance Monitoring

You use performance monitoring to display statistical data on the performance of the SAP CC 4.1 systems in your SAP

system landscape.

If you are analyzing the performance of an SAP CC system, you should normally start with the Triage dashboard in the

monitoring consoles of CA Introscope for SAP. You can use also IS Investigator and the Metric Reference and

Performance Troubleshooting documentation; see Troubleshooting and Root Cause Analysis Using CA Introscope for

SAP, page [148].

Performance monitoring facilitates the tuning of SAP Convergent Charging in real time, high volume, and high

availability environments.


SAP recommends that you define and implement automated monitoring for technical monitoring and alerting. Refer to

the Technical Monitoring and Alerting Using SAP Solution Manager 7.1 SP13 and Later section, page [40].

5.3.3 Alert Monitoring

Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system landscape. SAP

provides you with the infrastructure and recommendations needed to setup your alert monitoring to recognize critical

situations for SAP Convergent Charging 4.1 as quickly as possible.

Consider the following activities:



Define and implement automated monitoring for technical monitoring and alerting. Refer to the Technical Monitoring

and Alerting Using SAP Solution Manager 7.1 SP13 and Later section, page [40].

5.4 Technical Monitoring and Alerting Using SAP Solution Manager 7.1 SP13 and Later

During the implementation phase or the production operation phase, you can use SAP Solution Manager in

combination with CA APM Introscope for SAP to monitor the performance and health of the SAP CC systems in real

time.





Use the Technical Monitoring functions in SAP Solution Manager to manage the monitoring of the performance and

health of SAP CC 4.1 systems in complex, heterogeneous landscapes. It targets the infrastructure levels of the SAP CC

systems.

A dedicated work center is the central access to functions and tools for monitoring your SAP solutions and

accelerating problem solving.



The Technical Monitoring work center provides tools and capabilities for monitoring the SAP CC system landscape.

Technical monitoring inbox

alert

Provides central access to automated alerts from the system monitoring area

Allows you to start analyzing and solving detected problems in the SAP CC

landscape

System monitoring Provides the current status of systems, databases, and hosts

Allows you to access the latest snapshot of monitoring data for systems,

databases and hosts

Note

Consult the other work centers used for SAP CC in SAP Solution Manager for SAP CC, page [21].



Work Centers

In your SAP CC 4.1 implementation project, use SAP Solution Manager 7.1 SP13 and later to:

• Define your application landscape

• Define the monitors and thresholds for SAP CC 4.1


Implement and use Technical Monitoring in SAP Solution Manager 7.1 for monitoring your SAP CC 4.1 system

landscape in real time. Follow the Customizing activities outlined in SAP Solution Manager.

Note

Prior to SP12, SAP Solution Manager 7.1 does not deliver predefined content for SAP CC 4.1. System Monitoring for

SAP CC 4.1 can be implemented with a custom template.

Go to: SAP Solution Manager SAP Solution Manager Configuration (transaction SOLMAN_SETUP) Managed

Systems Configuration Technical System .

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/94/a39804783346d0bb466c38e2beda35/content.htm?frameset=/en/e1/af84531083ff4fe10000000a44176d/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=1897&show_children=false






42 PUBLIC



5.4.1.2 Related Documentation (Technical Monitoring Work Center)

For more information about SAP Solution Manager 7.1, consult in SAP Help Portal at: http://help.sap.com

Application Lifecycle Management SAP Solution Manager SAP Solution Manager 7.1 Application Help SAP

Library (English) of Solution Manager 7.1 SP13 Application Operations Work Centers In Application Operations


Product Documentation Main Topic Related Topics

SAP Solution Manager 7.1

Application Help

Technical Monitoring Work Center Technical Monitoring Alert Inbox

System Monitoring

5.4.2 Implementation in Your SAP CC Landscape

5.4.2.1 Prerequisites

• The CA Introscope packaged solution is installed

• SAP Solution Manager is configured with CA Introscope using the SAP Solution Manager Administration work

center

• The SAP CC system is:

○ Installed and configured to work with CA Introscope; otherwise manually configure the Introscope Java Agent as described in the SAP Note 1453216.

○ Configured to provide information to SAP Solution Landscape Directory (SAP SLD)

○ Registered in SAP SLD

Note


http://help.sap.com/solutionmanager71 Application Help SAP Library (English), SP13 Application

Operations Work Centers in Application Operations SAP Solution Manager Administration Work Center

Introscope

5.4.2.2 Installation Considerations

• Install both Diagnostics Agent and SAP Host Agent on each machine hosting an instance of the running SAP CC

system (Core Server) and its back-end database system; refer to the detailed SAP Note 1365123.

• Implement Technical Monitoring in SAP Solution Manager 7.1 SP13 or later for the monitoring of SAP Convergent

Charging; apply the setup procedures outlined in SAP Note 1875021. In case of any problems not covered by the






http://help.sap.com/saphelp_sm71_sp12/helpdata/en/9a/3a73b801bd422c89672eb8a952504f/content.htm

http://help.sap.com/saphelp_sm71_sp12/helpdata/en/e4/5d55b4bb024f048c0a732a38371e28/content.htmhttp:/help.sap.com/saphelp_sm71_sp12/helpdata/en/e4/5d55b4bb024f048c0a732a38371e28/content.htm








http://help.sap.com/saphelp_sm71_sp13/helpdata/en/21/3ff439b43b45fb8381d3d9c5cf6267/content.htm?frameset=/en/4e/31a64d4d4f4b52b82d0c88452f0072/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=2376&show_children=false

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/21/3ff439b43b45fb8381d3d9c5cf6267/content.htm?frameset=/en/4e/31a64d4d4f4b52b82d0c88452f0072/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=2376&show_children=false





FAQ, report an incident on component SV-SMG-MON-ALR or SV-SMG-MON-DIA component in SAP Support

Portal.

Note

You use the SAP Solution Manager Configuration work center (transaction SOLMAN_SETUP) to:

• Complete the information about the SAP CC system declared in SAP Solution Manager

• Set up the managed system cluster

• Set up the technical monitoring

5.4.3 Working with the Technical Monitoring Work Center in SAP Solution Manager

To use tools and capabilities for monitoring SAP CC landscape, you start the Technical Monitoring work center in SAP

Solution Manager by using SAP Logon and SAP Easy Access.

Note

In SAP Solution Manager, a technical system consists of the SAP system but also the instances, hosts, and IT

infrastructure devices that contribute to it.

5.4.3.1 Activities

You can monitor:

• Availability

• Performance

• Exceptions and errors

• Alerts

5.4.3.2 Monitor an SAP CC System and its Hosts

• In the Technical Monitoring work center, choose System Monitoring.

• In the Selection screen area, choose All Systems.

• To view the status of technical systems that relate to SAP Convergent Charging, select them.

• Click System Monitoring. To display monitored data, select a location (Start Embedded or Start New Window).

A window displays the monitored data that relates to the SAP CC cluster. The cluster is identified by the SID of the SAP

CC system.

• Click the System Name to view the hierarchy of the cluster and analyze the system hierarchy:

○ Instances of the SAP CC system; several instances are hosted by the same machine. The type of the instance

○ Instances of the database system

44 PUBLIC



• The naming convention of the instance node level is: <SID>~UNSPECIFIC~<INSTANCE_ID> on <HOST_NAME>

where:

○ <SID> is the SAP system unique identifier

○ <INSTANCE_ID> is the identifier of the instance in the SAP CC Core Server system (example: dispatcher#1, rater#2, updater#1, bulkLoader#2)

○ <HOST_NAME> is the name of the machine hosting an instance of the SAP CC system

• Click Availability to

• Click Performance to

• Click Exception to

• Click Alerts to view the alert inbox and the alerts raised for the system cluster

Note

Click Configuration Status to view the configuration settings in SAP Solution Manager that relates to the SAP CC

monitoring. A window opens the SAP Solution Manager Configuration work center at the stage of the configuration

of the Technical Monitoring feature.

5.4.3.3 Monitor the Back-End Database System and its Hosts

Refer to the procedure above.

5.4.3.4 Related Documentation



Library (English) for SAP Solution Manager 7.1 SP13 Application Operations System and Application Monitoring

System, Database, and Host Monitoring Using Monitoring and Alert Monitoring a System

5.5 Technical Monitoring Using CA Introscope for SAP

During the implementation phase or the production operation phase, you can use CA APM Introscope to monitor

manually the performance and health of the SAP CC Core Server systems in the SAP system landscape. You can use

the information delivered by the monitoring consoles to analyze the SAP CC systems and take appropriate actions

when necessary.

You work with the predefined dashboards and alerts to operate the technical monitoring of SAP Convergent Charging.


Install and use CA Introscope for monitoring and root cause analysis of SAP CC 4.1. Follow the setup procedure

outlined in SAP Note 1453216.



http://help.sap.com/saphelp_sm71_sp13/helpdata/en/5b/0c9ccfd262427685c245d7ea85cd7a/content.htm?frameset=/en/c5/5d7a53ece90a2ce10000000a44538d/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=1479&show_children=false

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/5b/0c9ccfd262427685c245d7ea85cd7a/content.htm?frameset=/en/c5/5d7a53ece90a2ce10000000a44538d/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=1479&show_children=false




In case of any problems with CA Introscope not covered by the FAQ, open a customer message on component XX-

PART-WILY in SAP Support Portal.


landscape in real time; see Technical Monitoring and Alerting Using SAP Solution Manager 7.1 SP13 and Later, page

[40].

5.5.2 Implementation in Your SAP CC Landscape


• Implement the CA Introscope for SAP solution packaged by SAP in your production system landscape. Refer to

the SAP Note 797147 - Introscope Installation for SAP Customers to implement CA APM Introscope and install its

components (Enterprise Manager, Workstation, WebView) in your SAP system landscape. This package is a

component of SAP Solution Manager.

• Implement the additional package delivered by SAP on top of the CA IS Enterprise Manager system. It includes

the necessary Introscope Management Modules developed by SAP. Refer to the SAP Note 1579474 - Management

Modules for Introscope delivered by SAP to install the required specialized package provided by SAP to enhance

the services and functions of CA Introscope.

• Make sure that you have installed the Management Module that includes the monitoring dashboards specialized

for SAP Convergent Charging: SAP_SRM_CRM (Products for "SRM and CRM").

Note

For later manual installation, refer to the SAP CC 4.1 Configuration Guide and to SAP Note 1453216 for more about

information about setting up and configuring CA Introscope for SAP CC 4.1.

5.5.3 Manual Monitoring with CA Introscope

You monitor nominal performance of the SAP CC Core Server systems. You can view live data or historical data.

Refer to the product documentation of CA Introscope for more information about:

• User interfaces and windows

• Getting started of the user interfaces (start, stop, ...)

• Using of the monitoring consoles in the user interfaces (navigation, tasks, operations)

• Using the Workstation Investigator tool


The Management Module SAP_SRM_CRM (Products for "SRM and CRM"). It is installed to the top of the CA IS

Enterprise Manager system. This management module includes the monitoring instrumentation and dashboards

specialized for SAP Convergent Charging.





46 PUBLIC



5.5.3.2 Monitoring performance with dashboards and alert indicators in the monitoring consoles

• Identify the health or performance problems in the CC Overview dashboard. Verify the overall alert indicators.

• Use the CC Triage dashboard to determine the current activities of the monitored system and to refine your

understanding of normal situation or potential problems.

Dashboards for SAP Convergent Charging Available in CA IS Monitoring Consoles

• Use the specialized dashboards to determine the current throughputs, latencies, and errors in the monitored SAP

CC Core Server systems:

Console Dashboard

CC Incoming Request

CC Outgoing Request

CC Internal Activities

CC CPU and Memory

CC Cache

CC JDBC

CC JCo

Refer to the primary help available in the monitoring console to understand the performance metrics and signaled

problems.



5.5.4 CA IS Workstation User Interface

5.5.4.1 Get Started (MS Windows)

• Go to the C:\usr\sap\ccms\apmintroscope directory.

• Start the user interface by launching the Introscope_Workstation.exe program for MS Windows.

• Enter the URL and dedicated communication port of the CA IS Enterprise Manager system.

• Log on with your credentials.

• In the Workstation menu, select the New Console submenu.

• A new Console window opens.

• Select one of the dashboards dedicated to SAP Convergent Charging. The naming convention is “CC …”. For

example, you select the CC Overview (SAP SRM CRM) item in the drop box.

Consult the documentation of CA Introscope for more information about this user interface.

The user interface displays the selected dashboard:

• Navigate to the relevant dashboards to perform your daily tasks for technical monitoring.

• Check out the alert indicators. Perform investigation, root analysis, troubleshooting in the monitoring console or

in Workstation Investigator.

Note

When your system landscape includes several SAP CC systems, use the Lens feature to display the instances of the

SAP CC system to monitor. You select the corresponding CA Introscope agents.

5.5.4.2 Using CA IS Workstation Investigator

In the monitoring consoles, when a metric viewer displays abnormal information, you can open an Investigator window

directly focused on the corresponding metric. Refer to the Troubleshooting and Root Cause Analysis Using CA

Introscope for SAP section, page [148].

5.5.4.3 More Information

Consult the secondary help available when you click:

• The title of a dashboard

• The [i] icons near to the graphs

Consult also the CA APM Workstation User Guide in the product documentation of CA Introscope. Refer to the relevant

bookshelf from CA Support.

48 PUBLIC



5.5.5 CA IS WebView User Interface

5.5.5.1 Get Started (MS Windows)

• Log on to the CA Introscope WebView user interface with your credentials.

• In the Console tab, select one of the dashboards dedicated to SAP Convergent Charging. The naming convention

is “CC …”. For example, you select the CC Overview (SAP SRM CRM) item in the drop box.

• Click the View button.

The user interface displays the selected dashboard. Navigate to the relevant dashboards to perform your daily tasks

for technical monitoring.

Check out the alert indicators. Perform investigation, root analysis, troubleshooting.





Consult also the CA APM WebView User Guide in the product documentation of CA Introscope. Refer to the relevant


5.6 Manual Monitoring

Manual monitoring is a highly effort-intensive approach that usually requires expert involvement.

You can use the following tools and user interfaces to perform manual monitoring of the SAP CC 4.1 systems in your

system landscape:

User Interface Day to Day Tasks Quick Procedure

Admin+ View the indicators of the SAP CC system about:

• Host memory and Java heaps

• Data cache usage

• Scheduled activities

Note

Refer to the SAP CC System

Parameter Reference documentation

for the complete list of indicators.

Use the get command and the relevant

indicators.

Example

You can view the FREE_MEMORY.



http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_paramref/FREE_MEMORY.html



User Interface Day to Day Tasks Quick Procedure

View some statistics of the:

• Business services

• Technical services

Use the get command and the

SERVICES_STATISTICS indicator to retrieve

statistics about the different services

running in an instance of the SAP CC Core

Server system.

View some service time statistics for the client systems or applications that are

connected to SAP Convergent Charging

via the Message TCP technical interface:

• General information about the

connection (access point,

identifications, time,

communications)

• Information about the requested

service operations

Use the fetch_client_statistics

command to display service time statistics

for the connected SAP CC charging

client(s).

BART+ View the running sessions in the SAP CC

BART Server system related to the offline

charging operations:

• Batch acquisition

• Batch rating and charging

Use the monitor command to display the

current sessions.

BART Tool Manually monitor the offline charging

operations

• Batch acquisition

• Batch rating and charging

Use the Supervision window to display the

current sessions.

CA Introscope

Workstation

Manually monitor the health and

performance of the system

See the CA APM/Wily Introscope for

Monitoring SAP CC section in $3 Technical

System Landscape this document.

Use the Console of CA IS Workstation to

display the predefined dashboards available

for monitoring the health and performance

of the SAP CC systems in the SAP system

landscape.

See the Technical Monitoring Using CA

Introscope section in §4 Monitoring of SAP

CC of this document for more information

about the manual procedures.

SAP Solution Manager Manually monitor the health and

performance of the system


Define and implement automated monitoring for technical monitoring and alerting. Refer to the Technical Monitoring

and Alerting Using SAP Solution Manager 7.1 SP13 and Later section, page [40].

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_paramref/SERVICES_STATISTICS.html

50 PUBLIC



5.7 Database Monitoring

Database monitoring is essential for the functioning of SAP Convergent Charging 4.1. A list of database monitoring

documentation references is provided in this section.

SAP CC 4.1 Component Back-End Database

Core Server Core Database

BART Server BART Database

IEC IEC Database

Customer Database

For more information about database monitoring in SAP Solution Manager, consult in SAP Help Portal at:

http://help.sap.com Application Lifecycle Management SAP Solution Manager SAP Solution Manager 7.1

Application Help SAP Library (English) Application Operations Database Analysis


Install and use DBA Cockpit for monitoring the databases of SAP CC 4.1.

Follow the setup procedures outlined in SAP Notes 1664432 (SAP HANA), 1532253 (Sybase ASE), 1265134 (Oracle),

1388700 (MS SQLServer) and 1267189 (IBM DB2).

The prerequisites for database administration and monitoring are described in SAP Notes 1027146.


For more information:

• See: http://help.sap.com Technology SAP NetWeaver Platform Technical Operations for SAP NetWeaver

Administration of Databases

• Read the section related to your database system:

○ For SAP HANA, read “Database Administration for SAP HANA”

○ For Sybase ASE, read “Database Administration for SAP ASE”

○ For IBM DB2, read “Database Administration for IBM DB2 for Linux, UNIX, and Windows”

○ For Oracle, read “Database Administration for Oracle”

○ For Microsoft SQL Server, read “Database Administration for Microsoft SQL Server”













5.8 Error and Process Monitoring

5.8.1 SAP Solution Manager 7.1

The system monitoring functions monitor the systems within your solution landscape in real time. On the managed

hosts, log file and process monitoring can be set up.


Install and use Technical Monitoring for SAP CC 4.1.


Follow the setup procedure outlined in SAP Note 1875021.

5.8.1.3 Error Monitoring

The log files of SAP CC 4.1 are monitored for "Error" patterns. The monitor will present its status and alerts according

to the presence and severity of log entries in the SAP Convergent Charging log files.

5.8.1.4 Operating System Monitoring

The server machines hosting the SAP Convergent Charging application are monitored for resource consumption.

Operating system metrics like overall CPU and memory consumption are reported. In addition, the Operating System

processes java.exe are monitored for resource consumption. You can customize the thresholds for alert triggering to

suit our individual needs.



landscape in real time; see Technical Monitoring and Alerting Using SAP Solution Manager 7.1 SP13 and Later, page

[40].


52 PUBLIC



5.9 Business Monitoring with BART Tool of SAP CC

5.9.1 Offline Charging Scenario Variant

Use the SAP CC BART Tool user interface to monitor the business operations performed by the SAP CC BART Server

system:

• Offline acquisition of service consumption information from mediation systems

○ You monitor the acquisition sessions collecting the Consumption Detail Records (CDRs) that relate to customer service usage

• Offline charging of these service consumptions

○ You monitor the batch rating and charging sessions running or scheduled in the BART Server system.

5.9.1.1 Related Information

See about the supervision in the BART Tool documentation in SAP Help Portal at the following location:

http://help.sap.com/cc SAP CC 4.1 System Administration and Maintenance Information BART Tool BART

Overview What you can do in BART Tool


Consult the SAP CC Application Help for more information about the offline charging services.

5.10 Monitoring of SAP Java Components

5.10.1 Java Monitoring and Management

Java monitoring and management provides developers, supporters, and customers with information about:

• Configuration, such as release, version, host, and port

• Monitoring critical conditions for IT operations

• Detailed performance and status data to detect and diagnose problems

• Detailed statistics on activity and resource consumption for accounting and auditing, service level agreement

(SLA) reporting, and problem analysis

See Also: Log Files







5.11 Detailed Monitoring and Tools for Problem and Performance Analysis

5.11.1 Log and Trace Files in your System Landscape

Log and trace files are essential for analyzing problems and determining possible causes.

Consider the logging and tracing features of:

• SAP Convergent Charging (SAP CC systems, user interfaces, applications)

• Java Virtual Machine (JVM) that executes the process of an instance of a running SAP CC system

• Back-end database

Note

As of SP 1, the running SAP CC Core Server system can generate thread dump files that provides your SAP Support

Team with some supportability and tracing-like tools.

5.11.2 Log and Trace Files in SAP CC 4.1

SAP CC has a common framework used by all its software components:

Functions Core Sever BART Server Diameter

Server

CT Server Graphical User

Interfaces

Severity thresholds management

Different levels of

information can be

recorded in the files

according to thresholds

based on the severity of

the records

By default:

- INFO for logs

- ERROR for traces

Yes Yes Yes Yes Not enabled by default

Rotating files

Different log files are

successively used each

time the current log file

reaches its maximum size.

Yes

Maximum

size: 200MB

Yes

Maximum size:

2MB

Yes

Maximum size:

20MB

Yes

Maximum

size: 2MB

Not enabled by

default

Backup of files

A backup log file is created

each time the current log

Yes

Yes

Yes

Yes

Not enabled by default

54 PUBLIC



Functions Core Sever BART Server Diameter

Server

CT Server Graphical User

Interfaces

file reaches its maximum

size.

Old backup log files are

recycled.

Notes

• For each SAP CC server system, there is a specific log file for containing console error messages.

• In the following, the <HOME> directory refers to the path: /usr/sap/<SID>/<INSTANCE_NAME>/

where <SID> is specified at installation (and is the unique ID of the SAP system) and <INSTANCE_NAME> is

automatically assigned to an instance by SAPinst

and is composed of three characters and two digit that represent the instance number

Note that <INSTANCE_NB> is different from <INSTANCE_ID>. Consult the SAP CC Installation Guide for

more details.

• The <WORKING_DIRECTORY> is a shared repository defined at the installation time. See the SAP CC

Installation Guide for more details.

• By default, the logging and tracing function is disabled in the graphical user interfaces. Refer to the

Troubleshooting of SAP CC section for more information about the temporary recording of logs and traces in

the SAP CC GUIs (Core Tool, BART Tool, CAT Tool).

• Consider the log files that relate to the performance and health of the Java garbage collection (GC) processed

by each Java Virtual Machine that executes an instance of a running SAP CC system.

5.11.3 Files of the SAP CC Core Server System

The following default settings are available for a productive system landscape and can be customized during the

implementation project phase or later during the operation phase:



SAP CC

4.1

Componen

t

Content Filenames (By Default) Path (By Default)

Core Server

All

instances

Logs Files (current):

<INSTANCE_ID>_LDF1.0.log

Backup files:

• <INSTANCE_ID>_LDF1.1.log

• …

• <INSTANCE_ID>-LDF1.<n>.log

Format: <INSTANCE_ID> =

<INSTANCE_TYPE>#<NB>

Example

dispatcher#1_LDF1.0.log,

dispatcher#1_LDF1.1.log,

rater#2_LDF1.0.log,

rater#2_LDF1.1.log

Each instance of the SAP CC Core Server system has

its own set of log files. Several instances can be

installed on the same host machine.

By default, the first destination fileset is used to

record the log messages.

<HOME>/work/log/

Core

Server

All

instances

Traces Files:

• <INSTANCE_ID>_LDF2.0.trc

• <INSTANCE_ID>_LDF2.1.trc

• …

• <INSTANCE_ID>_LDF2.<n>.trc



Example

rater#2_LDF2.0.trc,

rater#2_LDF2.1.trc,

rater#2_LDF2.2.trc,

rater#2_LDF2.3.trc

Each instance of the SAP CC Core Server system has

its own set of trace files. Several instances can be

installed on the same host machine.

By default, the second destination fileset is used to

record the trace messages.

<HOME>/work/log/

Core

Server

Thread Files Files:

<HOME>/work/dump/

56 PUBLIC



SAP CC

4.1

Componen

t


All

instances

<INSTANCE_ID>_<DATE>_<TRIGGER_TYPE>.z

ip

There are different filename classes: one for

each type of trigger

Example

rater#2_yyyy-MM-

dd'T'HH'h'mm'm'ss's_ondemand.zip (when

the dump command is used in Admin+)

(see the

THREAD_DUMP_OUTPUT_PA

TH system parameter)

Core

Server

All

instances

Dump Full dump of threads of the complete SAP CC

system or of the specified instances.

The dump describes each Java processing

thread with its stack traces.

Console of Admin+

Core Server

Dispatcher

instances

Bulkloader

instances

Traces

JCo RFC

communication

s with SAP

CRM and SAP

ERP/FI-CA

systems

Files:

JCO*.trc

<HOME>/work/

Core Server

Taxer

instances

EZTax Logs (Tax Journal)

No tax log file

Core

Server

Taxer

instances

Status

message

including error

codes

<INSTANCE_ID>_<THREAD_ID>.sta

These files are generated by the external tax system

(BillSoft EZTax) when the taxer instances start. Each

taxer can produce several files.

<HOME>/work/

5.11.3.1 See Also

Consider also the log files of the Java Virtual Machine; see the Log Files of the Java Garbage Collection section, page

[57].

5.11.3.2 Related Tasks

Configure the logs and traces:



• Use Admin+ to get the current system configuration settings for log and trace management in the running SAP

CC Core Server system.

View logs and traces:

• Use Admin+ and the logs command to display some logs of the Core Server systems.

• Use BART+ and the logs command to display some logs of the BART Server system.

• Use Root Cause Analysis in SAP Solution Manager to display the logs and traces of the SAP CC systems and the

other components (Java virtual machine, back-end database). See Root Cause Analysis and Exception

Management in SAP Solution Manager, page [146].


Topic Location in SAP Help Portal

System configuration for the logging and the

tracing function

Activate the functions

How to configure the functions


System parameters of the functions

System configuration


Detailed descriptions of the functions

Information recorded

Possible output destinations

SAP CC Application Help

Detailed descriptions of the important log

messages

SAP CC Log Message Reference and Error Troubleshooting

Troubleshooting problems with logs and traces • SAP CC Log Message Reference and Error

Troubleshooting

• SAP CC Operations Guide

5.11.4 Log Files of the Java Garbage Collection

To track any performance issue with the Java garbage collection (GC) processing, it is important to log all garbage

collector events.

SAP Convergent Charging is based on the Java technology. A Java Virtual Machine (JVM) executes the process of an

instance in an SAP CC system. Each virtual machine performs a garbage collection (GC) function to manage and

optimize the allocated host memory and the physical storage of data in this memory. SAP CC runs with an SAP JVM

that provides two types of log entries:

• Basic logs

58 PUBLIC



• Advanced logs

Note

By default, the logging and tracing of the garbage collection processed by the running Java Virtual Machines is not

enable. Refer to the SAP CC Configuration Guide.

SAP CC 4.1

Component


Core Server

All instances

GC History (Logs) • Files (current):

○ garbage-

<INSTANCE_ID>gc.prf

• Backup files:

○ garbage-<INSTANCE_ID>gc.prf.b00

○ ..

○ garbage-

<INSTANCE_ID>gc.prf.b19

Format: garbage-<INSTANCE_ID>gc.prf

With: <INSTANCE_ID> =

<INSTANCE_TYPE>#<INSTANCE_NB>

Example

garbage-rater#1gc.prf,

garbage-rater#1gc.prf.b00,

garbage-rater#2gc.prf,

rater#2gc.prf.b00

Each instance of the SAP CC Core Server system

has its own set of log files. Several instances can

be installed on the same host machine.

By default, the first destination fileset is used to

record the log messages.

<PATH_TO_WORK_FOLDER>

Core Server

All instances

Traces • Files:

○ garbage-<INSTANCE_ID>.txt

○ <INSTANCE_ID>_LDF2.1.trc

○ …

○ <INSTANCE_ID>_LDF2.<n>.trc



Example

rater#2_LDF2.0.trc,

rater#2_LDF2.1.trc,

<PATH_TO_WORK_FOLDER>



SAP CC 4.1

Component


rater#2_LDF2.2.trc,

rater#2_LDF2.3.trc

Each instance of the SAP CC Core Server system

has its own set of trace files. Several instances

can be installed on the same host machine.

By default, the second destination fileset is used

to record the trace messages.

Notes

• Consider the central SAP Note 1950168 – Generate the Java GC logs for SAP CC for more information about

the recommended configuration settings and some configuration determination rules.

• For advanced troubleshooting, consider the trace entries. The SAP JVM does a lot of tracing, which can aid

runtime analysis of Java programs like the systems and applications (IEC) of SAP Convergent Charging.

Examples are garbage collection statistics, method tracing or exception tracing. See the related product

documentation.

Example

For example, an administrator of an SAP CC Core Server system can define the following configuration settings for

the logging of the garbage collection activity in the Java virtual machines that run this SAP CC system in a

production environment. Note that a total of 3 TB storage space is reserved:

• GC History (enabled) of SAP JVM:

○ GC History Filename and Path: <PATH_TO_WORK_FOLDER>/garbage-<INSTANCE_ID>gc.prf

○ GC History Compression Level: 0

○ GC History Max File Size: 100 MB

○ GC History Max File Count: 20

• Log GC

○ Filename and Path: <PATH_TO_WORK_FOLDER>/garbage-<INSTANCE_ID>.txt

○ Log GC Max File Size: 50 MB

○ Log GC Max File Count: 20

○ Print GC Details: yes

○ Print GC Cause: yes

○ Print GC Date Stamps: yes

○ Print Tenuring Distribution: yes

○ Print Promotion Failure: yes

○ Print FLS Statistics: 1

Do not configure your SAP CC systems with these JVM options and values. Use the SAP recommendations in the

notes below.


60 PUBLIC



5.11.4.1 See Also

User Assistance Topic Documentation and Location

Administration Configuration SAP CC 4.1 Configuration Guide and central SAP Note 1950168 –

Generate the Java GC logs for SAP CC for more information about the

recommended configuration settings and some configuration

determination rules

Monitoring This document

Troubleshooting This document

Tracing

Handling pb


For more information about the SAP JVM, consult the product documentation available in SAP Help Portal:

User Assistance Topic Location

Getting Started Features help.sap.com Technology Platform SAP NetWeaver 7.3 SAP

JVM

Administration Configuration help.sap.com Technology Platform SAP NetWeaver 7.3 SAP

JVM Configuration and Setup of SAP JVM

5.11.5 Technical Operations

5.11.5.1 Monitoring the Log Files

As an administrator:

• Check there is no error recorded in the log files.

• If a log file includes an error or a caution, check the SAP CC Log Message Reference and Error Troubleshooting

documentation and contact your SAP Support Team.





https://help.sap.com/saphelp_nw73/helpdata/en/47/dc90b4ef17452289f9128b8c2bbd77/content.htm?current_toc=/en/71/72ab7c8ca14e5b94e0320c1656df18/plain.htm&show_children=true






https://help.sap.com/saphelp_nw73/helpdata/en/f0/cec51dabd1461b87e4db9e3958710e/content.htm

https://help.sap.com/saphelp_nw73/helpdata/en/f0/cec51dabd1461b87e4db9e3958710e/content.htm



5.11.6 Files of the Other SAP CC Systems

SAP CC 4.1

Component


BART Server Logs • bart_server_LDF1.0.log

• bart_server_LDF1.1.log

• …

• bart_server.<n>.log

<HOME>/work/log/

File report about offline acquisition

sessions or batch

rating and

charging sessions

(offline charging)

• Mass acquisition of Consumption

Detail Records (CDRs)

○ bart_REPORT_ACQUISITION_Y

Y-MM-DD_X.txt

• Batch charging results:

○ bart_REPORT_RATING_YY-MM-

DD_X.txt

<HOME>/work/

Traces bart_server_LDF2.0.trc <HOME>/work/log/

Dump Full dump of threads of the complete SAP

CC system or of the specified instances.

The dump describes each Java processing

thread with its stack traces.

Console of BART+

Diameter Server Logs • diameter_server.log

• diameter_server.log.0

• diameter_server.log.1

• …

• diameter_server.log.<n>

<HOME>/work/logs/

CT Server

The

Communications

Taxing Server

catches the

traces from JCo

and from BillSoft

EZTax.

Logs • ct_server.log

• ct_server.0.log

• ct_server.1.log

• …

• ct_server.<n> .log

<HOME>/work/log/

EZTax Logs (Tax Journal)

• EZTax-YYYYMMDDHHmmss-0.log

• EZTax-YYYYMMDDHHmmss-1.log

• …

• EZTax-YYYYMMDDHHmmss-<n>.log

These files are generated by the external tax

system (BillSoft EZTax).

<HOME>/work/eztaxLogs

/

See the

EZTAX_LOG_DIRECTORY

parameter

62 PUBLIC



SAP CC 4.1

Component


Status message including error

codes

EZTax.sta

This file is generated by the external tax

system (BillSoft EZTax) when the CT Server

starts.

If other *.sta files exist, it means that some

programs from BillSoft EZTax have been

launched by a user.

<HOME>/work/eztaxLogs

/

See the

EZTAX_LOG_DIRECTORY

parameter

Traces ct_server.trc <HOME>/work/log/

5.11.7 Files of the Graphical User Interfaces

SAP CC 4.1

Components


Core Tool

BART Tool

CAT Tool

Logs No file by default N/A

Traces No file by default N/A

Operation request

messages (*)

Operation requests

and XML messages

sent to the SAP

system

No file by default N/A

(*) The XML message content is only visible in the Core Tool user interfaces.

Refer to the Troubleshooting of SAP CC chapter, page [142] for more information about the traces and other

supportability tools and procedures.

5.11.8 Further Information

Topic Guide/Tool

Formats of the logs Security Guide - SAP CC 4.1

Configuration of the log file management Configuration Guide - SAP CC 4.1

5.11.9 Error Files of SAP CC 4.1

Regularly verify that the error directories do not include any erroneous files.



5.11.9.1 Error Files of the Main Component

SAP CC

4.1

Compone

nt

Content Filenames (By Default) Path (Default Settings)

Core Server

All

instances

Error message

<INSTANCE_ID>.err

Each instance of the Core

Server system has its own set

of error log files. Several

instances can be installed on

the same host machine.

<HOME>/work

Core

Server

Bulkload

er

instances

Invalid

billable

items in file

that have

been

rejected by

SAP ERP/FI-

CA (*)

Instance#<INSTANCE_ID

>.err

Each bulkloader instance of

the Core Server system has

its own set of error log files.

Several instances can be

installed on the same host

machine.

A control file includes the

error message. Try to fix the

problem and consult the

Troubleshooting section.

<WORKING_DIRECTORY>/SAPCC_CIT/POSTPAID/INVA

LID/

And:

<WD>/SAPCC_CIT/PREPAID/INVALID/

Billable

items in file

not sent due

to

communicat

ion failure

with

SAP ERP/FI-

CA (*)


>.err






machine.


error message. Try to

reestablish the connection

with SAP CI and consult the


<WORKING_DIRECTORY>/SAPCC_CIT/POSTPAID/COM_

EXCEPTION/

And:

<WD>/SAPCC_CIT/PREPAID/COM_EXCEPTION/

Consumptio

n items in

file that have

been

rejected by

SAP ERP/FI-

CA (*)


>.err






machine.





<WORKING_DIRECTORY>/SAPCC_CI/ACQUIRED/INVAL

ID/

And:

<WD>/SAPCC_CI/CHARGED/INVALID/

64 PUBLIC



SAP CC

4.1

Compone

nt

Content Filenames (By Default) Path (Default Settings)

Consumption items in

file not sent

due to

communicat

ion failure

with

SAP ERP/FI-

CA (*)


>.err






machine.


error message. Try to

reestablish the connection

with SAP CI and consult the


<WORKING_DIRECTORY>/SAPCC_CI/

ACQUIRED/COM_EXCEPTION/

And:

<WD>/SAPCC_CI/CHARGED /COM_EXCEPTION/

Notification

alerts not

sent to SAP

CRM or SAP

ERP/FI-CA


>.err

Each Bulkloader instance of





machine.





<WORKING_DIRECTORY>/SAPCC_NOTIF/ERROR/

(*) Note

The bulkloader instances are only installed in a system landscape in an integrated SAP Solution scenario with the

SAP CRM and SAP ERP/FI-CA components of SAP Business Suite.

• By default, the error files related to the mass loading function of billable items and consumption items into the

SAP ERP/FI-CA systems are located in subfolders of the Working Directory defined at the installation time in

each machine hosting an instance of the SAP CC system.

You can determine those subfolders by getting the values of the following system parameters with Admin+:

○ BIT_LOADER_ERR_INVALID_BIT_WRITER_ROOT_PATH and

○ BIT_LOADER_ERR_COM_EXCEPTION_WRITER_ROOT_PATH

○ NOTIF_WRITER_ROOT_PATH

• In case of advanced system configurations, these names of parameters can change:

○ Use Setup Tool from a dispatcher instance and export the CIF configuration of the bulkloader instances: setup cif export bulkLoader <myfilename>

○ In the exported file, locate the error handling nodes that include root path information



5.11.9.2 File Formats

For more information about the formats of the error files, refer to the SAP CC Application Help documentation. In the

Processes and Functions chapter, consult the Data File Bulk Loading Process section.

5.11.9.3 Error Files of Other Components

SAP CC 4.1

Component

Content Filenames (By Default) Path (Default)

BART Server Error message error.log <HOME>/work/

SQL failure files

When a SQL failure occurs during a

batch rating and charging session, the

BART Server system securely stops all

on-going processes, saves the list of

CDRs being charged to files and shuts

down to prevent any other failure.

The lists of pending CDRs in process

are saved to sql failures files.

The sql failure files are reloaded when

the BART Server system restarts and

the content is then committed to the

running database.

The function prevents the system from

triggering faulty batch charging

sessions, which may lead to

inconsistencies in price computation.

<HOME>/work/logs/sql_failures

See the sql.failures.log.file.name

parameter

Diameter

Server

CT Server Error message sapct.err <HOME>/work/

5.11.10 Useful Errors and Error Code List

5.11.10.1 BART Server

During a batch rating and charging session, the BART Server system can retrieve rating and charging errors from the

connected Core Server system. The BART Server system always stores an error code directly in each processed

Consumption Detail Record (CDR).

You can analyze the error through the BART Tool user interface or by consulting the error code list available in the

<BART_HOME>/docs/errors/ folder.

66 PUBLIC



5.12 Further Information

5.12.1 Monitoring SAP Notes

5.12.1.1 Java Connector


636912 Frequent installation problems with SAP Java

628962 How to switch on the SAP JCo trace

598891 Tools for analyzing SAP JCo and RFC errors in Web AS





Management of SAP CC PUBLIC 67

6 Management of SAP CC

SAP provides you with an infrastructure that allows your system administration team to administer SAP Technology

effectively by completing all tasks related to technical administration and operation.

This section describes the related topics on the SAP application level:

• Starting and Stopping, page [67]

• Software Configuration, page [71]

• Administration Tools, page [73]

• Backup and Restore, page [75]

• Periodic Tasks, page [85]

• Load Balancing, page [98]

• Management of Outdated Technical Data, page [101]

Note

In a productive system landscape, consider also the following information:

• High Availability, page [110]

• Purging and Archiving, page [118]

• Software Change Management, page [126]

6.1 Starting and Stopping

The procedure for starting and stopping the SAP CC systems depends on the underlying operating system.

6.1.1 Launch Tools for SAP CC

6.1.1.1 MS Windows: SAP Microsoft Management Console (MMC)

The SAP Microsoft Management Console (sapmmc) was installed during the SAP CC Core Server installation. It

enables you to see all your SAP systems and to manage them.

To start or restart the servers of SAP CC and the instances of these servers:

• Double-click the icon on your Desktop to start the SAP MMC

• Click the SAP system containing the server you want to start

68 PUBLIC


Management of SAP CC

• Right-click the instance or the server you want to start and choose Start or Restart

Use the same procedure to stop the servers. For the last step, right-click the instance or the server you want to stop

and choose Stop.

6.1.1.2 UNIX Operating Systems: SAP Management Console (MC)

The SAP Management Console (sapmc) was installed during the installation of the SAP CC Core Server system. It

enables you to see all your SAP systems and to manage them. It is installed in the following folders:

• /usr/sap/<SID>/SYS/exe/uc/<OS_PLATFORM>/servicehttp/sapmc/sapmc.html

• /usr/sap/<SID>/<INSTANCE_NAME>/exe/servicehttp/sapmc/sapmc.html (in each instance folder)

To launch this tool:

• Launch a web browser capable of running Java applications

• Open the sapmc.html file from the host

6.1.1.3 SAP Control

The SAP Control command-line application has the following partial synopsis:

sapcontrol [-trace <filename>]

[-debug]

[-user <user> <password>]

[-host <hostname>]

-nr <instance number>

-function <webmethod> [parameter list]

Where:

• The -trace option can be used to write SOAP request and/or response information into the specified file

• The -debug option can be used to write local trace to the “stderr” writing channel

• The -user option gives the possibility to execute the operation using a specific user, such as a SAP CC individual

or service user granted the Administrator role

• The -host option gives the possibility to specify the host concerned by the operation

• The -nr parameter is used to specify the number of the instance concerned by the operation

• The -function parameter is used to specify the operation to perform on the target instance, such as:

○ Start, which directly starts the process

○ Stop, which corresponds to: - a hard shutdown when no timeout is specified

- a soft shutdown with timeout when a timeout is specified

○ RestartInstance, which indeed corresponds to a Stop action followed by a Start action

○ Shutdown, which corresponds to a soft shutdown without timeout (that SAP SE or an SAP affiliate company recommends you to avoid)

○ And so on



Note

To get the whole synopsis of the SAP Control application (particularly the list of supported functions), consult its

documentation.

Example

Considering a landscape containing a host:

• Whose hostname is “SAPCCHOST1” and IP address is 192.168.1.1

• That contains a rater instance whose name is “CCR04” and belonging to the “CCD” Core Server system

whose administrator username is “CCDadm” and password is “CCDpwd”

You can use the following synopsis to execute a soft shutdown with a 3s timeout on this rater:

sapcontrol -host 192.168.1.1 -user CCDadm CCDpwd -nr 4 -function Stop 3000

6.1.2 Start and Stop Sequence

6.1.2.1 Real Time Scenario (Online Charging Variant)

SAP CC 4.1

Component

Sequence Tool and Description

Core Server

All instances

1 (n) • SAP Control

• SAP Management Console (UNIX Operating Systems)

• SAP Microsoft Management Console (MS Windows)

Note

Start all the instances of the Core Server system. Prefer starting first the

dispatcher instances but this is not mandatory:

○ Dispatcher instances

○ Updater instances

○ Guider instances

○ Rater instances

○ Bulkloader instances

○ Taxer instances

All the different instances will establish the right connections. The Bulkloader

and the Taxer instances are maybe not installed on your landscape depending

on your Business Scenario.

You can get the list of the instances by using Admin+ and the list command.

Diameter Server

2 Optionally launch:

• SAPCONTROL

70 PUBLIC



• SAP Management Console (UNIX OS)


6.1.2.2 Batch Mode Scenario (Offline Charging Variant)

SAP CC 4.1

Component

Sequence Tool and Description

Core Server

All instances

1 (n) • SAP Control



Recommendations

• Start or restart one instance at a time: one after the other. Wait for an

instance to be fully (re)started before (re)starting another one.

• Always first (re)start the Dispatcher instances.

• SAP SE recommends this specific order for (re)starting:

1. Dispatcher

2. Updater

3. Guider

4. Rater

5. Bulkloader

BART Server 2 Optionally launch:

• SAP Control



IEC 3 Optionally launch:

• From console: iec_remote.sh (UNIX Shell Script)

• From command prompt: iec_remote.bat (MS Windows)

6.1.2.3 Communications Taxing Server Scenario

Component Sequence Tool and Description

CT Server 1 • SAP Control





6.1.3 Related Documentation

Topic Location

SAP Management

Console (SAP MC)

SAP Management Console on SAP Help Portal

SAP Snap-In for Microsoft

Management

Console (SAP MMC

Snap-In)

SAP Microsoft Management Console: Windows on SAP Help Portal

SAP Control Starting and Stopping SAP NetWeaver Management Agents

Consult the SAP NetWeaver 7.0 EHP1 Technical Operations Manual from the SAP Help Portal at the following location:

http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 including Enhancement Package 1 System

Administration Technical Operations Manual

6.2 Software Configuration

This chapter explains which components of SAP Convergent Charging 4.1 are configurable and which tools are

available for adjusting.

All the configuration procedures are grouped in a unique configuration document. The relevant tools (graphical user

interfaces and command line programs) are provided with each software component.

SAP CC 4.1

Component

Configuration Tools Description

Core Server Core Tool Business configuration (Master Data, Business Data)

Admin+ Business configuration (Business Data)

Technical configuration

Setup Tool Technical configuration

Config Tool Business configuration (SAP System Parameters)

Technical configuration (SAP System Parameters)

BART Server

(Offline charging)

BART Tool Business configuration (Transactional Data)

Job management

Monitoring

http://help.sap.com/34212da60ac54baebaf71b03fd0ac16d

http://help.sap.com/db29f6d5eb9a49598b378c923bd9c894

http://help.sap.com/saphelp_nw73/helpdata/en/49/9a15525b20423ee10000000a421938/frameset.htm



72 PUBLIC



SAP CC 4.1

Component

Configuration Tools Description

BART+ Business configuration (Master Data)


BART Setup Tool

Import/Export Connector (IEC)

Connector Administration Tool (CAT Tool)


Diameter Server

(Online charging)

N/A

The Diameter Server

system has no specific

configuration tool

A text editor should be used

CT Server N/A

The Communications

Taxing Server system has

no specific configuration

tool

A text editor should be used

For more information about these configuration tools, see the SAP CC product documentation in SAP Help Portal at

the following location: http://help.sap.com/cc41 Application Help Power User Documentation – User Interfaces

For more configuration and implementation information, see the SAP CC 4.1 Configuration Guide in SAP Help Portal at

the following location: http://help.sap.com/cc41 Installation and Configuration

6.2.1 Configuration Files

All the components of SAP CC 4.1 use some configuration files located in the <HOME>/config/ installation folder.

Templates are also provided (*.sk file extension) for facilitating the management of these configuration files.

6.2.1.1 Core Server

The SAP CC Core Server system uses mostly configurations stored in SAP CC Core Database in the following database

tables:

• INSTANCE_CONFIGURATION

• CONFIGURATION

• CERT_STORE

• INSTANCE_CERT_STORE

You can use the Admin+ user interface and the Setup Tool user interface to view or change the system settings

relating to system processes or business processes.



http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/index.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_uis/index.html





6.2.1.2 BART Server

The SAP CC BART Server system uses a single configuration file (bart.config) in read/write access. Its file format uses

the ISO 8859-1 character encoding.

Some settings are stored in SAP CC BART Database in the CERT_STORE and INSTANCE_CERT_STORE database

tables. You can use the BART Setup Tool user interface to view or change the security certificates.

Note

Characters that cannot be directly represented in this encoding scheme must be written using Unicode escapes.

Consult details at: http://java.sun.com/docs/books/jls/third_edition/html/lexical.html#3.3.

6.3 Administration Tools

This chapter explains which components have administration tools and where to find related documentation.

SAP CC 4.1

Component

Administration Tool(s) Description Server System Restart is

Needed?

Core Server Admin+ Configuration:

• System parameter

management

○ Business settings

○ Technical settings

• Business data

Always (*)

(*) Online changes are only

possible for log settings. See the

parameter reference

documentation.

Setup Tool Configuration management

• System

• Data

Certificate management

License management

Always

Config Tool System parameter management Always

Core Tool User management

Master data (for Service

Provider) configuration and

maintenance

Customization of business data

(public holidays, currencies) and

maintenance

No restart

BART Server BART+ • Business configuration

(Master Data) Always (*)

http://java.sun.com/docs/books/jls/third_edition/html/lexical.html#3.3

74 PUBLIC



SAP CC 4.1

Component

Administration Tool(s) Description Server System Restart is

Needed?

• Technical configuration

• Other:

○ Troubleshooting of connected SAP CC

system

(*) Online changes are only

possible for log settings.

BART Setup Tool

BART Tool System configuration

Operations

No restart

Diameter Server N/A

The Diameter Server has

no specific configuration

tool

A text editor should be used Always

CT Server N/A

The Communications

Taxing Server has no

specific configuration

tool

A text editor should be used Always


Consult the primary help documentation in SAP Help Portal. User guides for power users and IT administrators are

available for with each user interface.

Topic Location

Detailed information about the user interfaces

provided with the Core Server system:

• Admin+

• Setup Tool

• Config Tool

• Core Tool

http://help.sap.com/cc SAP CC 4.1 Application Help

Power User Documentation - User Interfaces

System parameters and indicators of the Core

Server system http://help.sap.com/cc SAP CC 4.1 System

Administration and Maintenance Information SAP CC System

Parameter Reference

Detailed information about the user interfaces

provided with the BART Server system:

• BART+

http://help.sap.com/cc SAP CC 4.1 Application Help

Power User Documentation - User Interfaces









Topic Location

• BART Setup Tool

• BART Tool

Note

You can consult the System Parameter Reference for the Core Server system in SAP Help Portal at:

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_paramref.


For taking into account the parameter changes, the server systems must be restarted. In a production environment,

schedule always these operations during a specific low traffic period: A downtime is necessary, and this process can

temporarily decrease the performances of SAP CC. Consult the High Availability section in this document, page [110].

6.4 Backup and Restore

You need to back up your system landscape regularly to ensure that you can restore and recover it in case of failure.

6.4.1 Backup and Restore Strategy

The backup and restore strategy for SAP CC 4.1 consists of two parts:

• Backup and restore coverage for each component (see table below)

• Cross-system data dependencies and handling

The backup and restore strategy for your system landscape should not only consider SAP systems but should also be

embedded in overall business requirements and incorporate your company’s entire process flow.

In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of a data center

through fire. It is most important in this context that you ensure that backup devices are not lost together with normal

data storage (separation of storage locations).

Based on the type of application data a component holds, we have used a categorization scheme that can be used to

analyze the backup requirements of any system component and to easily determine an appropriate backup method for

this component.

The following table contains the component list of SAP CC 4.1 and the appropriate categories:

SAP CC 4.1

Component

Category Data for Backup and Restore Backup Method for

Application Data

Core Server X

Original application data,

data exchange with other

systems, data managed by

• Application data: Back up the data and

ensure data consistency with other

systems

• Software: Backup is necessary

File backup

Database backup

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_paramref

76 PUBLIC



SAP CC 4.1

Component


Application Data

a DBMS, not based on SAP

WebAS • Software configuration: Backup is

necessary

• Logs: Backup is necessary

BART Server X





WebAS

• Application data: Back up the data and


systems


• Software configuration: Backup is

necessary


Database backup

Diameter

Server

II

Only software and

configuration information,

no application data

Note

Data exchange with other

systems

• Application data: No data backup is

required

• Software: Initial software backup after

installation and backup after changes

have been applied


necessary

• Logs: Backup is required

Note

After a system crash, you can use any of

the procedures to restore your

component:

• Perform a new installation and

restore the configuration

• Restore the backup of the software

and the software configuration

N/A

CT Server IX



systems, data not managed

by a DBMS

• Application data: Back up the application

specific file system (tax journal files)



necessary

• Log files: Backup is required

File backup

IEC IX / X



systems, data managed or

not managed by a DBMS


specific file system and ensure data

consistency with other systems



necessary

• Logs: No backup is required

File backup

Database backup



SAP CC 4.1

Component


Application Data

Core Tool II

Only software and


no application data


required

• Software: No backup is required

• Software configuration: No backup is

required

• Logs: No data backup is required

N/A

BART Tool II

Only software and


no application data


required



required

• Logs: No data backup is required

N/A

CAT Tool VI



systems, data not managed

by a DBMS


specific file system (scenario files)



required

• Logs: No backup is required

File backup

6.4.2 General Recommendations

You must regularly test your backup and restore strategy. A single test is insufficient, since the SAP CC 4.1 system

landscape is likely to change and render a given strategy redundant. System administrators need an up-to-date

backup and recovery strategy to restore failed systems.

SAP recommends that you perform a backup:

• After the initial installation and configuration of the SAP CC 4.1 system landscape

• After specific changes, such as changes to the configuration, software update of individual components, or

replacement of components made to the system landscape. This of course depends on the frequency of such

changes.

When you decide which components or which parts of the components to back up, consider the following factors:

• Time required for a complete reinstallation

• Time required for additional configuration

• Effects of the expected downtime of one or more infrastructure components with regard to the overall availability

of the landscape

A backup process must ensure:

• Logical consistency

Restore the SAP CC 4.1 system landscape (cross-system data consistency) to a consistent status: The

78 PUBLIC



restoration applies at document level at the time of the backup. This includes the successful rollback of all open

business transactions with respect to the exchange of data.

• Physical consistency

Restore individual SAP CC 4.1 components to a consistent state, followed by a successful startup of the restored

components, and a successful reconnection to other components. Physical consistency provides a working

runtime environment in which newly created business data can be exchanged. This is required to develop a

transactional conduct on user level to react to broken workflows and outdated documents appearing after the

restoration.

6.4.3 Detailed Backup and Restore

When you plan a backup and restore strategy for application data, software and configuration files, you must consider

the following elements:

• Operating system

• Database data files

• Database software

• SAP software and file systems

• Log files (SAP and others)

• Software of other system components (file systems and configuration files)

A component that has application data (a database, for example) usually comprises application software and

configuration files (runtime infrastructure) that need a backup as well. A component, which contains no application

data, may comprise configuration files and software that require a backup.

The following table lists various elements of components and details the necessary data that needs backup or needs to

be restored in each category.

SAP CC 4.1 Component Online Charging Offline Charging

Core Server Yes Yes

Core Database Yes Yes

Core Tool Yes Yes

Diameter Server Yes -

BART Server - Yes

BART Database - Yes

BART Tool - Yes

IEC - Yes

CAT Tool - Yes



SAP CC 4.1 Component Online Charging Offline Charging

CT Server Yes Yes

6.4.3.1 Online and offline charging: Core Server, Core Database, Core Tool

SAP CC 4.1

Component

Data to be

Backed Up

Data Location Backup Recommended

Backup Frequency

Core Server Software Files created by SAPinst in the appropriate folder

(/usr/sap/<SID>/SYS/profile/)

Note

Each instance of the Core Server has its own

installation folder.

• Once a month to once

a week

• After installation or

maintenance changes

Software Configuration

• Files in /usr/sap/<SID>/<INSTANCE_ID>/config/

folder (for each instance)

• Configuration data records in database (see

Core Database detailed in this table)

• Once a month to once

a week


maintenance changes

Application

Data

• Data is mostly stored in the Core Database

detailed in this table

• Some important data files

See Core Database

Logs Files in /usr/sap/<SID>/<INSTANCE_ID>/work/

folder (for each instance)

Once a month to once a week

Core Database

Software Depends on your RDBMS After installation and after maintenance changes

Software

Configuration

Depends on your RDBMS After installation and after

maintenance changes or

once a month to once a

week

Application

Data

In the database Once a month to once a

week

Logs Depends on your RDBMS

Core Tool Software Files in default installation folder (<HOME>/)

80 PUBLIC



SAP CC 4.1

Component

Data to be

Backed Up


Backup Frequency


Files in <HOME>/config/ folder (default

installation)

6.4.3.2 Online Charging with Diameter Server

SAP CC 4.1

Component

Data to be

Backed Up


Backup Frequency

Diameter Server

Software Files created by SAPinst in the appropriate folder (/usr/sap/<SID>/SYS/profile)

After installation and after maintenance changes

Software

Configuration

Files in /usr/sap/<SID>/<INSTANCE_ID>/config/

folder

After installation and after


once a month to once a week


folder


6.4.3.3 Offline Charging with BART Server, BART Database, BART Tool, IEC, and CAT Tool

SAP CC 4.1

Component

Data to be

Backed Up


Backup Frequency

BART Server Software Files created by SAPinst in the appropriate folder (/usr/sap/<SID>/SYS/profile)

• Once a month to once a

week


maintenance changes



folder

• Once a month to once a

week


maintenance changes

Application Data

Data is stored in the BART Database detailed in this table

See BART Database


folder




SAP CC 4.1

Component

Data to be

Backed Up


Backup Frequency

BART Database

Software Depends on your RDBMS After installation and after maintenance changes

Software

Configuration

Depends on your RDBMS After installation and after



Application

Data

In the database Once a month to once a week


IEC Software Files in default installation folder (<home>/)

Software

Configuration

Files in <HOME>/config/ folder (default

installation)

After installation and after



Application

Data

Data is stored in the IEC Database detailed in this

table

See IEC Database

Logs Files in <HOME>/logs/ folder (default

installation)

IEC Database Software Depends on your RDBMS


Depends on your RDBMS After installation and after maintenance changes or


Application Data

In the database


BART Tool Software Files in default installation folder (<HOME>/)


Files (*)

CAT Tool Software Files in default installation folder (<HOME>/)


File and database

Application

Data

Files

82 PUBLIC



6.4.3.4 Special: CT Server

SAP CC 4.1

Component

Data to be

Backed Up


Backup Frequency

CT Server Software Files created by SAPinst in the appropriate folder (/usr/sap/<SID>/SYS/profile)

After installation and after maintenance changes



folder

After installation and after maintenance changes or


Application

Data

Tax Journal (EZTax Log Files)


folder


The locations of the folders containing files are chosen at installation time and may differ from the table above.

6.4.3.5 CC_EZTAX Central Repository

When your system landscape includes functions to manage the US taxes for telecommunications, you must backup

and restore a central repository CC_EZTAX that includes few software files and data related to the BillSoft EZTax

software:

SAP CC 4.1

Component

Data to be

Backed Up


Backup Frequency

CC_EZTAX

Central

Repository

Software Files created by SAPinst in the appropriate folders of

CC_EZTAX repository:

• /jar/ contains the file eztax.jar

• /lib/ contains EZTax library files (*.dll, *.so)

• Once a month to

once a week


maintenance

changes


Not applicable

Application

Data

• transervdesc.txt file

• EZTax database files (CC_EZTAX/db/)

See Core Database

Logs Not applicable

The following sections describe specific information about the various elements you must consider, such as, the

operating system used, the database software, and so on, when you plan a backup and restore strategy for application,

software, and configuration files.



6.4.4 Operating System, Software and Configuration Data

Apart from business-critical application data (generally held in databases), you can also back up the system and

application software (including configuration files). If you do this, you do not have to reinstall the system and

application software if the software becomes damaged.

It is always possible to reinstall the operating system, software, and configuration data. However, reinstallation and

configuration can take a long time. Therefore, if a backup of the software and configuration is available, you can reduce

the time needed to restore your system after a system failure.

6.4.4.1 Online Backup

The data contained in the database can be backed up online; however, it is not possible to do the same for the runtime

infrastructure. An online backup refers to the system landscape and not the databases that contain the business-

critical application, or the infrastructure components.

If you perform a backup while the server is running, open files may not be backed up.

6.4.4.2 File System Backup versus Full System Backup

A file system backup only applies to specific files or files systems, whereas a full system backup applies to all files and

file systems, including the operating system.

After installation of new software components, certain entries in the configuration files of the operating system cannot

be found in the file systems in which the software installation occurred.

SAP therefore recommends that you perform a full system backup after installation, and that you back up the file

systems of the installed software and the operating system on a regular basis.

For more information concerning possible backup scenarios, see on SAP Service Marketplace at:

service.sap.com/atg Advanced Technology Group Backup & Restore Documentation .

6.4.5 Database for SAP CC 4.1

SAP recommends that you run the database in archive mode.

This means that all actions on the database that modify data is recorded by the database and written to a transaction

log. With regular full backups of your database (either offline or online), as well as a complete set of transaction logs

since the last backup, it is possible to restore a crashed database to any point in time before the database crashed.

SAP CC 4.1

Component

Database Application Data for Backup and Restore Backup Method for

Application Data

Core Server Core

Database

Business critical original data (master data)

Configuration data of the software component (Core

Server)

RDBMS supplier relevant

method(s) and tools

BART Server BART

Database

Business critical data (master data)

Business critical data (transactional data): CDR

RDBMS supplier relevant

method(s) and tools

84 PUBLIC



Configuration data of the software component (BART

Server)

6.4.5.1 Backing up a Database

To ensure recoverability of your SAP CC systems, SAP recommends that you regularly back up the Core and BART

databases. The procedure depends on the technology of the backend database:

• When using SAP HANA, refer to the SAP Note 1642148 and to the SAP HANA Administration Guide

• When using Sybase ASE, refer to the SAP Notes 1585981 and 1588316, which describes how to set up automatic

backups of data and log files

• When using Oracle, Microsoft SQL Server or IBM DB2, refer to the normal database procedures

For SAP Convergent Charging, SAP recommends that you dump transaction logs at least every hour to ensure that the

logs do not fill up the devices.

6.4.5.2 Restoring a Database

Restore the Core Database or the BART Database using the normal database procedures. See the database

documentation for details.

6.4.6 SAP CC 4.1 Third-Party Components

The following table lists various elements of components and details the necessary data that needs backup or needs to

be restored in each category.

6.4.6.1 BillSoft EZTax

Component Category Data for Backup and Restore Backup Method for

Application Data

BillSoft EZTax

X





WebAS

• Application data: Backup the data and


systems



necessary


File backup






6.4.7 Further Information

6.4.7.1 Backup and Restore SAP Notes

Check SAP Support Portal at https://support.sap.com/notes regularly, to see which SAP Notes are available for a

Solution Operations Guide.

6.5 Periodic Tasks

6.5.1 Automated Periodic Tasks

This chapter describes all automatable tasks required to run periodically to keep the application running smoothly over

time. Such tasks may be required on component level and are therefore relevant in each scenario that uses the

component.

It is important that you monitor the successful execution of these tasks on a regular basis.

6.5.1.1 Core Server Tasks

Automated Periodic

Task

Scheduling

Tool

Recommended

Frequency

Description

Business task:

Periodic fee

management

Admin+ or

another

application

Every day at

midnight

To have valid data for the invoicing and billing

processes, SAP CC must compute all the relevant

periodic fees. This computation must be compliant

with the billing process and potential billing cycles.

An external scheduler can be plugged by the

implementation project team to regularly trigger the

activation of periodic fees for provider contracts or

subscriptions. Refer to the relevant documentation.

SAP CC provides an internal scheduler to trigger the

automated activation of periodic and one-off fees

(see recurring rates and one-shot rates) of

subscriptions for end customers. This scheduler

does not take into account the provider contracts.

Refer to the System Parameter Reference about the

configuration of the

ACTIVATION_SCHEDULER_ENABLED parameter

and other related parameters.

See the SAP CC Application Help for more

information about the activation process.

https://support.sap.com/notes

86 PUBLIC



Automated Periodic

Task

Scheduling

Tool

Recommended

Frequency

Description

Note

Consult also the manual triggering of the

activation of periodic fees.

Business task:

Subscriber account

expiration alert

management

Admin+ Every day at

midnight

Disabled by default


information about the subscriber account

expiration function.

See the System Parameter Reference about the


EXPIRATION_ALERT_SCHEDULER_ENABLED

parameter and other related parameters.

Technical task:

Heartbeat mechanism

Admin+ Every 2 seconds or

less

See the Parameter Reference for more information

about the heartbeat function of the instances of the

Core Server.

See the Parameter Reference about the


HEARTBEAT_POLLING_PERIOD parameter and

other related parameters.

Technical task:

Refreshing the data

caches (offer level)

Admin+ Every 5 minutes See the Parameter Reference for more information

about the refresh function of offer business objects.



REFRESH_SCHEDULER_ENABLED parameter and


Technical task:

Cleanup of rating

records

Admin+ Every day at

midnight

Disabled by default


information about the obsolete prerating function.



CLEANUP_SCHEDULER_ENABLED parameter and


Technical task:

Purging expired

allowances in

contracts

Admin+ Every day at

midnight See the SAP CC Application Help for more

information about the purge mechanism dedicated

to expired allowances.

Technical task:

Transport of change

lists

Every day at

midnight

Disabled by default

See the Detailed Periodic Tasks section below for

more information about the transport of change

lists.



6.5.1.2 Core Database Tasks

Automated Periodic

Task

Task

Scheduling

Tool

Recommended

Frequency

Description

Oracle database

periodic optimization

RDBMS Tool Weekly or monthly

according to your

traffic

See the “Detailed Periodic Tasks” section

6.5.1.3 BART Server Tasks

Automated Periodic

Task (BART Server)

Task

Scheduling

Tool

Recommended

Frequency

Description

Managing batch rating and charging sessions

BART Tool (using jobs)

Weekly or monthly according to your

business traffic

Jobs can be configured in the BART Server system for scheduling batch rating and charging sessions.

See the BART Tool documentation in SAP Help

Portal at the following location:

http://help.sap.com/cc SAP CC 4.1

Administration and Maintenance BART Tool

Jobs About Jobs

Specific tool

depending on

the customer

implementati

on project

Weekly or monthly

according to your

business traffic

The periodic triggering of batch charging operations

is managed in an external system connected to the

BART Server via the HCI technical interface.

6.5.1.4 BART Database Tasks

Automated Periodic

Task

Task

Scheduling

Tool

Recommended

Frequency

Description

Oracle database


RDBMS Tool Weekly or monthly

according to your

traffic




http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/bart_tool/Jobs/About_jobs.htm

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/bart_tool/Jobs/About_jobs.htm

88 PUBLIC



Automated Periodic

Task

Task

Scheduling

Tool

Recommended

Frequency

Description

Database cleaning BART Tool

(using jobs)

Weekly or monthly

according to your

traffic

Jobs can be used for scheduling database cleaning.

See the BART Tool documentation from the SAP

Help Portal at the following location:

http://help.sap.com/cc SAP CC 4.1

Administration and Maintenance BART Tool

Jobs About Jobs

Purge and archive of

outdated data (CDRs)

RDBMS Tool Monthly See the Configuration Guide about the procedures

to archive transaction data (CDRs).

These procedures are automated or can be manual.

6.5.1.5 Diameter Server Tasks

Automated Periodic

Task

Task

Scheduling

Tool

Recommended

Frequency

Description

N/A There is no automated periodic task.

6.5.1.6 CT Server Tasks

Automated Periodic

Task

Task

Scheduling

Tool

Recommended

Frequency

Description

N/A There is no automated periodic task.

6.5.2 Required Manual Periodic Tasks

This chapter describes all manual tasks required to run periodically to keep the application running smoothly over

time. A manual task needs a person to for each execute in opposite to the scheduled tasks listed above which can be

automated using a task scheduler program. Such tasks may be required on component level and are therefore relevant

in each scenario that uses the component.

It is important that you monitor the successful execution of these tasks on a regular basis.

Caution

The periodic tasks are defined by a frequency or must be triggered by an event. For example, a manual task can be

necessary after certain executions of a job.





6.5.2.1 Core Server Tasks

Manual Periodic

Task (Core Server)

Tool Supporting this

Task

Recommended

Frequency or

Survey

Description

Monitor and change

the sizes of data

caches

Admin+ Weekly or

Monthly

In a production system, check the cache sizes

every week if a lot of provisioning is done in

your system landscape, every month otherwise.

With the Admin+ user interface, check the

values of the

SUBSCRIPTION_CACHE_STATUS,

GUIDING_CACHE_STATUS and

SESSION_STATUS indicators.

Here are a few signs indicating that you should

increase the size of a cache:

• The remaining free memory is less than

20% of the total memory of the cache

• The fmem field is less than 50MB

• The miss field is a lot greater than the e

field

• A NOT_ENOUGH_SPACE error is logged in

traces files

Note

For defining the new sizes of these data

caches, you can use the determination

method detailed in the SAP CC

Configuration Guide without creating new

objects. Use the

SUBSCRIPTION_CACHE_STATUS,

GUIDING_CACHE_STATUS and

SESSION_STATUS indicators to know how

many objects are stored in the caches and

you can compute the average size of one

object.

Check for error files

in the output data

folders (in the SAP

Working Directory)

In each Working Directory of the SAP CC

system, verify that there is no remaining error

file.

90 PUBLIC



Manual Periodic

Task (Core Server)


Task

Recommended

Frequency or

Survey

Description

System operation:

Purge technical

data necessary to

the safe operation

management

Admin+ (with the purge_idempotency

command)

Daily, weekly or

monthly

The period must

be determined

during the

implementation

project phase

If your SAP CC system landscape provides refill

services

Note

For defining the purge period, refer to the

SAP CC Configuration Guide.

Business task:

Periodic fee

management

Admin+ or another

application

Monthly or

business

dependent

To have valid data for the invoicing and billing

processes, SAP CC must compute all the

relevant periodic fees. This computation must

be compliant with the billing process and

potential billing cycles.

• An external triggering can be plugged by

the implementation project team to

manually trigger the activation of periodic

fees for provider contracts or

subscriptions. Refer to the relevant

documentation.

• Use the start_activation command

or the

start_contract_activation

command of Admin+ to manually trigger

the activation of periodic and one-off fees

(see recurring rates and one-shot rates) of

subscriptions for end customers.


information about the activation process.

Note

Consult also the automated triggering of

the activation of periodic fees.

Maintain the Public Holidays

Core Tool Yearly Before the end of the year, maintain the public holidays

Check the available

space

Archive the log files Yearly

To be fine

determined

You can have to archive the logs. The periodicity depends on the system

configuration and on the available space of your

platform

Update the VAT

rates

Setup Tool Rare and not

periodic

You must update the VAT rates known by the

SAP CC system for legal reasons



Manual Periodic

Task (Core Server)


Task

Recommended

Frequency or

Survey

Description

Update the VAT

rules

Setup Tool Rare and not

periodic

You must update the VAT rates known by the

SAP CC system for legal reasons

Update the BillSoft EZTax installation

for all the Taxer

instances

BillSoft EZTax Monthly Update

Monthly

Before the end of

the current month

Every month, before the end of the month, BillSoft sends an updated version of EZTax that

contains the tax rates for the next month.

This update should ideally be launched before

the end of the current month (see the

maintenance procedure [page 128].

Old tax rates are always logged in the new

releases of EZTax.

Caution Do not stop all the Taxer instances at the

same time.

Update the DST rules

SAP JVM Rare and not periodic

The daylight saving time rules can change and may impact your business for specific regions

Update the list of

ISO currencies

Core Tool Rare and not

periodic

The SAP User should import an up-to-date list

of ISO currencies

Update the list of

SAP currencies

Core Tool Not periodic In an integrated SAP Solution scenario with SAP

ERP/FI-CA of SAP Business Suite, the SAP user

should manually synchronize the SAP CC 4.1

system each time the SAP currencies are

changed in the SAP ERP reference system (or

master system)

Maintain the

master data of the

service provider

Core Tool Not periodic During the production phase, you may need to

change the master data related to the pricing

configuration for a service provider.

Model the changes of the objects in the pricing

catalog, test the changes with a quality

landscape, and transport the changes to the

production system.

Example Create a new charge plan for a new option

added to the customer services.

Process rerating in case of mistakes in

the invoices

Core Tool Not periodic

92 PUBLIC



Manual Periodic

Task (Core Server)


Task

Recommended

Frequency or

Survey

Description

Relaunch the cache

warm-up

mechanism

Admin+ Rare and not

periodic

After a mass creation or maintenance operation

of master data related to a very large volume of

customers, SAP recommends that you

manually trigger the data cache warm-up

function of the SAP CC 4.1 system. Use the

start_cache_warmup command.

Note See the SAP CC Application Help for more

information about the cache warm-up

mechanism and the customer data

provisioning processes.

Add an instance in

an SAP CC system

SAPinst Rare and not

periodic

Add an SAP

ERP/FI-CA system

to the customer

management area

Several user

interfaces are

necessary (Setup

Tool, Core Tool)

Rare and not

periodic

You may need to deploy more SAP systems in

the system landscape to:

• To manage high volume of customer

master data and enable load balancing

functions

• To enable multisite deployments

Note

Refer to the SAP CC Configuration Guide for

more information about the relevant

procedure to:

• Declare a new JCo destination

• Define a new customer management

area

• Apply the changes in the SAP CC

system



Manual Periodic

Task (Core Server)


Task

Recommended

Frequency or

Survey

Description

Add an SAP CRM

system to the

customer

management area

Several user

interfaces are

necessary (Setup

Tool, Core Tool)

Rare and not

periodic

You may need to deploy more SAP systems in

the system landscape to:

• To manage high volume of customer

master data and enable load balancing

functions

• To enable multisite deployments

Note Refer to the SAP CC Configuration Guide

for more information about the relevant

procedure to:

• Declare a new JCo destination

• Define a new customer management

area

Apply the changes in the SAP CC system

Purging change lists

Admin+ or Core Tool Weekly, monthly or yearly

See the Detailed Periodic Tasks section below for more information about the purge of change

lists.

6.5.2.2 Core Database Tasks

Manual Periodic

Task (Core

Database)

Tool Supporting

this Task

Recommended

Frequency or

Survey

Description

Oracle database

periodic

optimization

RDBMS Tool


Database indexes

reconstruction

RDBMS Tool

Data purging and archiving

See the chapter Purging and Archiving, page [118]

Purge technical

data relating to job

operations

performed via Web

Services

Admin+ According to

volumetry

The frequency

depends on the

quantity of performed

job operations

Job operations performed via Web Services

create technical data recorded in the WS_JOB

table of the Core database. You need to

periodically remove this data to ensure

performances of your SAP CC system.

Use the purge_job_record command.

94 PUBLIC



6.5.2.3 BART Server Tasks

Manual Periodic Task

(BART Server)

Tool

Supporting

this Task

Recommended

Frequency or

Survey

Description

Update the DST rules SAP JVM Rare and not

periodic

The daylight saving time rules can change and may

impact your business for specific regions.

Check the available space

Trigger CDR offline

acquisition

BART Tool Daily, weekly or

monthly

According to the type of business manage by SAP

CC, you need to acquire the CDRs related to a day

of business traffic.

Trigger batch charging BART Tool Daily, weekly or

monthly

According to the type of business managed by SAP

CC, you request the batch charging operations

Specific tool depending on

the customer

implementati

on project

Daily, weekly or monthly

The manual triggering of batch charging operations is managed in an external system connected to the

BART Server via the HCI technical interface.

6.5.2.4 BART Database Tasks


(BART Database)

Tool

Supporting

this Task

Recommended

Frequency or

Survey

Description

Oracle database


RDBMS Tool After a campaign

of acquisition

sessions and

rating sessions, it

is recommended

to perform this

task


Purge and archive of

outdated data (CDRs)

RDBMS Tool Periodic

40 days by default

See the chapter Purging and Archiving, page [118]

Available for SAP HANA, Sybase ASE, Oracle and

MS SQL Server only



6.5.2.5 Diameter Server Task


(Diameter Server)

Tool

Supporting

this Task

Recommended

Frequency or

Survey

Description

Update the DST rules SAP JVM Rare and not

periodic

The daylight saving time rules can change and may

impact your business for specific regions.

6.5.2.6 CT Server Task


(CT Server)

Tool

Supporting

this Task

Recommended

Frequency or

Survey

Description

Create tax journal

(purge and archive of

EZTax log files)

BillSoft

EZTax

programs

To be determined

according to the

frequency of

invoices or the

frequency of the

tax declaration

reporting

The Communications Taxing Server stopped,

archive by moving the EZTax log files and use the

BillSoft EZTax programs for aggregating these logs.

Update the BillSoft EZTax installation

BillSoft EZTax

Monthly

Update

Monthly

Before the end of

the current month

Every month, before the end of the month, BillSoft sends an updated version of EZTax that contains

the tax rates for the next month.

This update should ideally be launched before the

end of the current month (see the maintenance

procedure [page 128].

Old tax rates are always logged in the new releases

of EZTax.

6.5.3 Detailed Periodic Tasks

6.5.3.1 Oracle Database Periodic Optimization

After some time of using SAP CC 4.1, it becomes possible and necessary to analyze and optimize the Oracle database

tables/indexes of the specific users reserved for SAP CC. To ensure high level of performance with SAP CC, SAP

recommends that you optimize the Oracle database usage by regularly launching the commands below.

They can be applied with the Core Database system and the BART Database system. Use the following requests to

analyze and optimize the tables by estimating the statistics for a database schema:

CONNECT system/manager

EXEC dbms_stats.gather_schema_stats(ownname => '<schema name in uppercase>', cascade =>

true, estimate_percent => 10, degree => 8);

96 PUBLIC



ALTER SYTEM flush shared_pool;

The estimate_percent and degree parameters can be changed according to the accuracy of the estimation

required and the degree of parallelism required, ideally set to twice the number of CPUs of the host.

Note that this estimation is only useful when the database has a considerable volume of data stored.

Note

The above procedure can be automated so that it is performed periodically (for example: monthly or weekly) during

a specific low traffic period: This process will temporarily decrease the performances of the database and SAP CC

4.1.

6.5.3.2 Time Zones

SAP CC 4.1 does not manage time zones but it uses the local time of the host machines. All the hosts of the SAP CC

landscape must have the same operating system time zone.

Caution

Once installed, do never change the OS time zone of the machines that host the components of SAP Convergent

Charging.

6.5.3.3 Daylight Saving Time (DST) Updates

SAP CC 4.1 manages the DST (also called summertime) by using data provided by the SAP JVM. When DST rules are

modified or created, you must update your landscape by updating all the JVM installations.

The SAP JVM includes both rules for daylight saving times and descriptions of global time zones in a unique container.

For updating the DST rules, you have to update your landscape by applying the procedure outlined in SAP Note

1367871.

Note that SAP Convergent Charging does not use the data related to descriptions of time zones as it does not manage

time zones and uses only the local time of the hosts.

Caution

Changing the time zone of the host is not a possible workaround for a lake of DST rules. Contact first your SAP

Support Team.

6.5.3.4 Purges of Allowances in Master Data

When using the Allowance Management feature, it is necessary to regularly purge allowance data in provider contracts

from the back-end database system to ensure the global performance of the SAP CC systems and avoid latency

issues.

This customer data purge mechanism can be executed:

• Manually, using the start_purge_allowances command of the Admin+ user interface and specifying the

following parameters:




○ A reference date, which is used to determine the list of expired allowances to remove

○ A maximum throughput, which corresponds to the maximum number of provider contracts per second that each rater instance can consider during allowance purge operations, and thus control the impact of these

operations on the global performance of the system

For further information about this command, refer to the SAP CC User Interfaces documentation.

• Automatically, using a dedicated scheduler in the SAP CC system; refer to the SAP CC System Parameter

Reference documentation for more information about the ALLOWANCES_PURGE_SCHEDULER_ENABLED

system parameter.

Both manual and scheduled executions of the purge operations log the following information when starting and

stopping:

• The number of provider contracts whose allowances have been successfully purged

• The number of provider contracts containing allowances which could not be purged

• The number of allowances successfully purged in contracts

Refer to the SAP CC Log Message Reference documentation for more information about the log messages that

relates to the allowance purge operations and its mechanism. See the definitions of the

com.sap.SCC.core_server.000508 log message ID.

Note

In addition to the log information, the following indicators are available to know the reference dates of the last

manual or scheduled purge operation:

• ALLOWANCES_PURGE_LAST_TRIGGER

• ALLOWANCES_PURGE_SCHEDULER_LAST_TRIGGER

For further information about these indicators, consult the SAP CC System Parameter Reference documentation.

6.5.3.5 Transports of Change Lists

All the transport requests whose status is set to “CREATED” are automatically executed by a dedicated scheduler in

charge of transporting all the corresponding change lists to the defined destinations.

For more information about the configuration of this scheduler, refer the SAP CC 4.1 Configuration Guide

documentation.

6.5.3.6 Purges of Change Lists

To avoid latency and ensure the global performance of the system, it is necessary to regularly delete from the Core

database the data related to change lists, which have been transported to remote SAP CC system(s).

Purge operations can be executed:

• Unitary, using the Delete menu of the Core Tool user interface and selecting a change list to delete

• In bulk mode, using the purge_change_lists command of the Admin+ user interface and specifying a

reference date which is used to delete the change lists created before this date and associated to already

executed transport requests

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_paramref/ALLOWANCES_PURGE_SCHEDULER_ENABLED.html

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_messageids/com.sap.SCC.core_server.000508.html

98 PUBLIC



For more information about these purge operations, refer to the SAP CC 4.1 User Interfaces documentation.

6.6 Load Balancing

SAP CC 4.1 features some load balancing functions. To achieve load balancing, multiple instances of a server system

are started at a time on the same or different host machines.

SAP CC 4.1

Component

Program Load Balancing Description

Core Server Dispatcher instance Function included Several dispatcher instances can be

installed

The connected client applications

perform the load balancing by using

the Java API Reference of SAP CC 4.1

Guider instance Function included

Several guider instances can be installed

Rater instance Function included

Several rater instances can be installed

Bulkloader instance

(Optional)

Function included

Several bulkloader instances can be

installed

Taxer instance

(Optional)

Function included Several taxer instances can be

installed

Updater instance No load balancing is possible

Caution

Only one instance is active

Diameter Server Main server program Implementation tasks

required on client

application side

Several programs can be installed on

several hosts in the system landscape

The connected client applications are

responsible for managing load

dispatching

BART Server Main server program N/A

Batch mode scenario

Load balancing function is only used for real time scenarios

CT Server Main server program N/A

Batch mode scenario

Load balancing function is only used

for real time scenarios



SAP CC 4.1

Component

Program Load Balancing Description

Several programs can be installed on

several hosts in the system landscape

SAP Gateway is used for load

balancing

6.6.1 Detailed Load Balancing

The following functions are provided with SAP CC 4.1 to ensure the load balancing of the solution.

6.6.1.1 Core Server

Load Balancing Method

(Core Server)

Description Tools to be Used

Intelligent load balancing management

The master dispatcher instance of the Core Server is responsible for the load balancing functions of some other

instances (Guider, Rater, and Taxer).

Once installed and started, these types of instances are

immediately taken into account by the Master Dispatcher

Instance and by the other Dispatcher Instances.

The master dispatcher instance is in charge of the

replications and synchronizations of data (data cache

management with relevant invalidations).

No specific tool

The Master Dispatcher

Instance of the Core

Server has this function

Round robin for accessing

the dispatcher instances

The Java based client applications that use services of the

Core Server connect seamlessly to one or other Dispatcher

instances.

The load balancing function is embedded in the Java API of

SAP CC 4.1.

The client application

uses the Java API of

SAP CC 4.1

For more information about the master dispatcher instance of the SAP CC Core Server system, see the SAP CC

Application Help in SAP Help Portal at the following location: http://help.sap.com/cc41 Application Help

6.6.1.2 Diameter Server


(Diameter Server)




100 PUBLIC



Load dispatching made by

the client application

Several Diameter Server programs can be installed in the

landscape. The Diameter Server is a stateless server that

has no application data:

• There is no need to replicate data

• Each installed Diameter Server program is

autonomous and there is no need of updating

simultaneously with data

The client application

6.6.1.3 CT Server


(CT Server)


Load balancing of SAP

Gateway

The SAP Gateway can oversee the load balancing to each

CT Server.

There is no need to replicate data.

The different CT Server programs must have the same

version of BillSoft EZTax with the last monthly update.

The user must archive the tax journals (EZTax log files) and

merge them with the BillSoft EZTax programs.

SAP Gateway

For more information, see the SAP Gateway documentation about the load balancing functions from the SAP Help

Portal at: http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 including EHP1 System Administration

Technical Operations Manual General Administration Tasks Administration of SAP NetWeaver Systems AS ABAP

(Application Server for ABAP) Administration Connectivity Gateway Administration Load Balancing for

Registered Programs

6.6.2 Setup Change

6.6.2.1 Core Server

If the initial business traffic increased a lot, you may need to add some rater instances of the Core Server to your

production landscape. You must follow the sizing guidelines to determine the instances you need to add. When

installing a new instance on an existing or new host, the traffic for rating and charging services will be automatically

reorganized with all the running rater instances.

You can also add other types of instances of the Core Server: Taxer, Guider, and Dispatcher.

6.6.3 Troubleshooting

In case of difficulties with the business traffic, you can explore two solutions:

• Fine tune the existing platform



http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/ace6623b1e35bae10000000a42189d/frameset.htm






• Add instances and hosts to your landscape

6.7 User Management

SAP CC 4.1 features some user management functions. You use the SAP CC Core Tool user interface to configure your

SAP users.

Refer to the primary help documentation of Core Tool for more information about the available procedures; see page

[13].

User assistance:

• Configuring the system; see the Technical Feature Settings chapter in the SAP CC Configuration Guide

documentation, page [13]

• Concept: Application Help

• Security: Security Guide

6.8 Management of Outdated Technical Data

Generated temporary technical data can be regularly removed if not needed anymore. The tasks to be performed for

this purpose are listed in the above chapter Periodic Tasks, see page [85].

6.8.1 Potential Outdated Technical Data

SAP CC System Description

Core Server The SAP CC Core Server System generates technical data files as output results of the business processes (rating, charging, rerating and refilling).

The management of these files depends on the scenario for your landscape:

• Standard scenario

• Integrated scenario

See the next sections for details.

BART Server The SAP CC BART Server System acquires and stores technical data named Consumption

Detail Record (CDR) in the BART Database. This data is used as input for the offline charging

process and may become outdated.

See the Purging and Archiving section, page [118] for details.

Diameter Server None

CT Server None

102 PUBLIC



6.8.1.1 Core Server: Standard Landscape

SAP CC System Description Location

Core Server

• Rater instances

The rater instances of the Core Server

System generate voluminous charged

item files and refill record files that must

be transmitted to a third-party billing

system.

Depending on the integration between

the SAP CC Core Server system and this

external system, these files can become

outdated.

In a scenario with such an external

system, you can consult the system

configuration of the Core Server to

determine if these files are automatically

removed by SAP CC or if they should be

regularly archived.

In the repository <WORKING_DIRECTORY>,

the files are temporarily stored in the

subfolders:

• /CC_POSTPAID/

• /CC_PREPAID/

The <WORKING_DIRECTORY> is a particular

shared central repository defined at the

installation time. See the Installation Guide

for more details.

Notes

• The current system configuration may be different from the default configuration. Check the configurations of

the rater instances of the SAP CC Core Server system.

• Some voluminous error files may exist in these folders. Do not remove them. See the Troubleshooting of SAP

CC section, page [142] for details about problems with charged item files or refill record files.

6.8.1.2 Core Server: Integrated Landscape

SAP CC System Description Location

Core Server

• Rater instances

• Bulkloader

instances

The rater instances of the Core Server system generate voluminous charged

item files and refill record files that must

be transmitted to a third-party billing

system.

In the repository <WORKING_DIRECTORY>,

the files are temporarily stored in the

subfolders:

• /CC_POSTPAID/

• /CC_PREPAID/

The <WORKING_DIRECTORY> is a shared

central repository defined at the installation

time. See the Installation Guide for more

details.

In an integrated scenario with SAP ERP and SAP CRM components from SAP Business Suite, these files are used by

the SAP CC 4.1 Core Server and they are automatically removed by default:

○ Charged item files

○ Refill record files

○ Notification files



Notes

• The current system configuration may be different from the default configuration. Check the configurations of

the Rater instances and of the bulkloader instances of the SAP CC Core Server system.

• Some voluminous error files may exist in these folders. Do not remove them. See the Troubleshooting of SAP

CC section, page [142] for details about problems with charged item files or refill record files.

6.8.2 Log Files

The log files produced by the SAP CC 4.1 Server Systems are not considered as outdated technical data. Their volume

must be checked or monitored.

6.9 Administration: System Audit and Control

6.9.1 Viewing System Information

Use SAP Solution Manager or SAP CC Admin+ to retrieve information about the SAP CC systems in your SAP system

landscape.

The Admin+ user interface allows you to view some system indicators managed by the Core Server system. Use the

get command to retrieve information about:

6.9.1.1 Technical Information

SAP CC Core Server

System

Description Example

System Information

• Current date of the instance hosts

• Name of the server system

• Identifier of the instances

• Names of the machine hosting the

instances of the SAP CC system

get VERSION

Installation Information

Installation path of the instance of the SAP CC system

Installation number

get INSTALLATION_PATH

Memory

Data Cache

104 PUBLIC



SAP CC Core Server

System

Description Example

Services Statistics about the different services running in an instance of the SAP CC Core Server

system

get SERVICES_STATISTICS

Refer to the SAP CC System Parameter Reference documentation for the complete list of indicators and parameters; see page [13].

6.9.1.2 Business Information

You can view the following business indicators defined in the SAP CC Core Server system:

SAP CC Core

Server

System

Description Example

Charging The number of sessions currently stored in the session cache

get SESSION_COUNT

Activation Last date when the activation process

was requested by an SAP CC user and

triggered in the SAP CC system

get ACTIVATION_LAST_TRIGGER

Last date when a scheduled activation

on subscriptions was triggered in the

SAP CC system

get ACTIVATION_SCHEDULER_LAST_TRIGGER

Account and

Balance

Management

The last date when the expiration alert

mechanism was started

get EXPIRATION_ALERT_PROCESS_LAST_TRIGGER

The last date when the expiration alert

mechanism was triggered by a

scheduler of the SAP CC system

get EXPIRATION_ALERT_SCHEDULER_LAST_TRIGGER

Notification Last date when the expiration alert

mechanism was started

(EXPIRATION_ALERT_PROCESS_LAST_TRIGGER)

6.9.2 Viewing the System Configuration Settings

You can inspect the configuration settings of the SAP CC systems in your SAP system landscape. Use the appropriate

user interfaces.


file://///frcfr03/FRCFR03/SCC40VAL/jws/scc.product/scc_04VAL_COR/gen/dbg/java/packaged/full/_base/core_paramref/EXPIRATION_ALERT_PROCESS_LAST_TRIGGER.html

file://///frcfr03/FRCFR03/SCC40VAL/jws/scc.product/scc_04VAL_COR/gen/dbg/java/packaged/full/_base/core_paramref/EXPIRATION_ALERT_PROCESS_LAST_TRIGGER.html



6.9.2.1 System Parameters

You can inspect configuration parameters of the SAP CC systems.

• Use both the Admin+ and Config Tool user interfaces to view the defined values for a Core Server system.

• Use the BART+ user interface and the SAP CC Configuration Guide to view the defined values for a BART Server

system.

• Use the SAP CC Configuration Guide to view the defined values for a Diameter Server system.

• Use the SAP CC Configuration Guide to view the defined values for a Communications Taxing Server system.

Note that a system parameter can configure a business feature or a technical feature of SAP Convergent Charging.

Refer to the following product documents in our user assistance:

• Primary Help of Admin+

• Primary Help of Config Tool

• System Parameter Reference

• Configuration Guide

6.9.2.2 Other System Configurations

You can inspect some configuration settings that complete the system parameters. Use the Setup Tool user interface

to view the defined configuration.


• Primary Help of Setup Tool

• Configuration Guide

6.9.3 Viewing Log Messages

You can inspect detailed information available in logs and traces recorded by the SAP CC systems.


• Log Message Reference and Error Troubleshooting

• Primary Help of Admin+ and BART+

• SAP Log Viewer

6.9.3.1 Getting and Viewing Logs of the SAP CC Systems

You can get the log messages generated by the systems of SAP Convergent Charging by using the following

procedures:

• To view all the logs and traces in SAP Solution Manager

106 PUBLIC



• To view all the logs and traces in SAP Management Console

• To view the SAP CC system logs and traces in Admin+

• To view the SAP CC system logs and traces in BART+

By default, the file extensions are *.log and *.trc. The logs and traces are not mixed. These settings may be

customized in your running SAP CC system. Refer to the Log and Trace Files section in this guide, page [53].

6.9.3.2 Procedure: Viewing the Logs (and Traces) in SAP Solution Manager

In the Root Cause Analysis Work Center of SAP Solution Manager, use the System Analysis report to display the logs

and traces of SAP Convergent Charging:

• Start a system analysis: choose the System Analysis report in the navigation area.

• Select the system cluster that corresponds to your SAP CC platform.

• Click Log Viewer. A window displays all the host machines available in this cluster, the status of the Diagnostic

agents, and the declared log stores.

• Select the host and the log (or trace) files to analyze.

See:

• SAP Solution Manager for SAP CC, page [21]

• SAP product documentation of SAP Solution Manager

6.9.3.3 Procedure: Viewing the Logs (and Traces) in SAP Management Console (SAP MC, SAP MMC)

To view the logs (and traces) in your SAP Management Console:

• Select the SAP CC system by its SID (SAP System Identifier) that is unique in the SAP system landscape

• Select the host you want to work with; Right-click and choose the All Tasks menu.

• Then select the View Developer Traces... submenu.

• Select the log (or trace) files to analyze.

See: SAP product documentation of SAP MC

6.9.3.4 Procedure: To view the SAP CC Core Server system logs and traces in Admin+

• Launch the Admin+ user interface and log on

• Use the logs command to display some log and trace messages

See: primary help of Admin+, page [13]



6.9.3.5 Procedure: To view the SAP CC BART Server system logs and traces in BART+

• Launch the BART+ user interface and log on

• Use the logs command to display some log and trace messages

See: primary help of BART+, page [13]

6.9.4 Viewing Product Software Usage and Customer Usage

To audit the SAP Product usage of the SAP CC software product, you can use the SAP CC Core Tool user interface to

generate a license auditing file for the SAP Global License Auditing System (GLAS). See the Tools menu. It replaces the

reporting function of business/usage metrics.

You can also generate a usage metric report in the same user interface; see the Window menu.

Refer to the primary help of Core Tool for more information; see page [13].

6.9.5 Viewing Audited Users Operations

When enabled, you can inspect most of the business or technical operations requested by the SAP CC users (both

service users and individual users) to plan preventive or corrective actions in the SAP CC systems. You use the audit

concept and the SAP CC Core Tool user interface to view audited operations depending on the system configuration.


[13].

User assistance:



• Technical operations:

○ Managing audits in with Core Tool

○ Viewing and inspecting audited user operations (with Core Tool)

• Associated technical operations: Purging the audit data recordings (with Admin+); see the Purging and Archiving

section, page [118]

6.9.6 Viewing Data Object Changes

When enabled, you can inspect the changes in the persistent configuration data. You use the audit concept and the

SAP CC Core Tool user interface to view audited information: data object change logs and object snapshots depending

on the system configuration.


[13].

User assistance:

108 PUBLIC





• Technical operations:

○ Managing audits in Core Tool

○ Viewing and inspecting object change logs and object snapshots of audited data objects (with Core Tool)

• Associated technical operations: Purging the audit data recordings (with Admin+); see the Purging and Archiving

section, page [118]

6.9.7 Viewing Traces

Your support specialists can inspect detailed information available in recorded trace messages. You can perform the

procedures to view log messages as detailed in this chapter.

Consult also the following sections in this guide:

• Log and Trace Files, page [53]

• Advanced Troubleshooting: Tracing Tools, page [160]

• Working with Traces in the Core Server System, page [161]




See also:

• Thread dumps

6.9.8 Viewing Processing Thread Dumps

Your support specialists can inspect detailed information available in recorded thread dumps. The generated files

contain about the execution context of the processing threads that are executed within each instance of the running

SAP CC Core Server system. In case a problem occurs during the execution of an operation or if the execution exceeds

some defined thresholds, the system generates dump files automatically in addition to logs and traces.

6.9.9 Viewing Java Thread Dumps

Your support specialists can inspect detailed information available in recorded thread dumps.

Each instance of an SAP CC system runs in a Java process that executes the SAP CC software. The dumps and dump

files contain information about each Java processing thread, including the stack traces.



6.9.9.1 Procedure: To view the dumps of the SAP CC Core Server system in Admin+


• Use the dump command to display the dump and stack trace for one or several instances in the SAP CC Core

Server system

See: primary help documentation of Admin+, page [13]

6.9.9.2 Procedure: To view the dump of the SAP CC BART Server system in BART+

• Launch the BART+ user interface and log on

• Use the dump command to display the dump and stack trace

See: primary help documentation of BART+, page [13]

110 PUBLIC


High Availability

7 High Availability

High availability applications allow you to maximize downtime security and minimize downtimes. You can achieve this

objective controlling the growth of redundant data and by implementing suitable logic to control redundant systems.

At SAP, the focus on high availability (HA) is always directed at business applications and their related components.

SAP relies on the high availability applications of partner products with regard to the components such as, the

operating system, database, and hardware, which are mandatory for implementing the infrastructure.

Note

For more information, see on SAP Service Marketplace at: https://service.sap.com/ha.

To gain competitive advantage, you must think of a collaborative business. This means integrating existing

heterogeneous system landscapes to include business partners, customers, and suppliers. The responsibilities

concerning the use of a high availability application should be divided between customers, partners, and SAP as

described below:

• Customer

○ Decision for and against high availability applications

○ Operation of a high availability environment

• Partner

○ Provisions for hardware, infrastructure, and high availability applications

○ Implementation of a high availability application at customer using their own technology or SAP technology

• SAP

○ Supports and provides technologies to enable the implementation of partner high availability applications

○ No certification of high availability applications of individual partners

Note

For more information, see on SAP Service Marketplace at: https://service.sap.com/partners.

The trend is towards open system architectures in which end-to-end business processes combined with Web services run on multiple distributed application components. Such environments demand high availability not only for single

components, but also for entire scenarios.

Note

SAP, along with partners, has developed a range of high availability applications, which many customers have

already in use. The applications you choose will vary according to your system landscape. Ensure that you discuss

your plans with your SAP consultant and hardware partner before implementation.

7.1 Downtimes

Downtime defines the time during which you cannot use a system or a resource productively. Irrespective of how the

SAP system landscape is defined (with or without a high availability application); a breakdown of one or several

https://service.sap.com/ha

https://service.sap.com/partners


High Availability PUBLIC 111

components always requires action. To cope with these exceptional situations, it is imperative to ensure that the

necessary resources are available in the event of malfunctions, problems, queries, such as an SAP specialist or a

network administrator.

There are two types of downtimes described in the following chapters:

• Planned Downtimes

• Unplanned Downtimes

7.1.1 Planned Downtimes

Planned downtime is the time for scheduled maintenance and upgrade during which a system cannot be used for

normal productive operations. This time is used for a variety of purposes so that a system can function optimally and

reliably.

Some of the possible causes of planned downtime are as follows:

• Parameter change

• Update to Support Packages (SPs) or patches

• Hardware maintenance

• Landscape reorganization by adding/removing an instance (to the Core Server system)

• Upgrades to new releases of SAP application components, database or operating system

• Database reorganization

• Database backup

• Archiving of business data objects

7.1.1.1 Preparation

You must:

• Agree upon a planned downtime in close cooperation between the IT department and the respective

departments. This is the only way of defining the timeframe for the necessary downtimes, without restrictions

being placed on the way the application works. A low traffic period is preferable.

• Inform all those involved in advance about the upcoming system downtime

• Keep the downtime as brief as possible

7.1.1.2 Possible Maintenance Actions

The following table lists the possible changes in SAP systems and the downtimes, which can be planned in each case to

rectify the problem:

112 PUBLIC


High Availability

Maintenance

Action

Downtime Downtime (HA

Setup)

Description

Parameter

changes

Mandatory Recommended Most of the configuration parameter changes require a partial or complete restart of the relevant system.

Hot modifications:

Few parameters can be changed online with the configuration

tools Admin+ and BART+. Consult the SAP CC System

Parameter Reference for details.

Check the wanted changes and how they should be applied

and schedule your downtime accordingly. In case of a HA

setup, the downtime is not necessary but recommended.

Always schedule the changes during a low traffic period.

Patch for SAP CC

Mandatory Recommended Patches can be installed with SAPinst. Consult their notes to schedule a downtime for your landscape.

In case of a HA setup, the downtime is not necessary but

recommended.

Always schedule the patch implementation during a low

traffic period.

Support

Package for SAP

CC

Mandatory Recommended Support Packages (SPs) can be installed with SAPinst.

Consult their notes to schedule a downtime for your

landscape.


recommended.

Always schedule the SP implementation during a low traffic

period.

Maintenance of

the host

machine: OS,

memory,

storage,

network

Mandatory Recommended You must plan a downtime period.


recommended.

Always schedule the changes during a low traffic period.

Add or remove

instances of the

Core Server

Not relevant Not relevant No downtime period is necessary.

You can simply install and run new instances in the

landscape.

Ensure that the landscape keeps certain symmetry in term of

different types of installed instances, their number and their

distribution on the hosts.



Maintenance

Action

Downtime Downtime (HA

Setup)

Description

Maintenance of the SAP CC

database

Conditional Conditional Consult the documentation of your database about the maintenance downtime.

Recommendation

In case of HA setup, disconnect first the SAP CC system

from the RAC instance you want to shut down. Use the

admin_sql_connections command of the Admin+

user interface.

Upgrade of replaced SAP CC

release 4.0 to

release 4.1

Mandatory Mandatory You must plan a downtime period.

7.1.2 Unplanned Downtimes

Unplanned downtime is the time during which a system cannot be used for normal productive operations due to

unforeseen failure in hardware or software components, or operator mistakes.

Unplanned downtime can be extremely costly to an organization. The source of unplanned downtime can be in any of

the layers that make up the complete software and hardware environment:

• Front-end and middleware services for connection to the web, including the Internet Transaction Server (ITS), the

SAP Web Application Server (SAP Web AS), and the SAP Enterprise Portal.

• SAP system services of the individual application components of the SAP Business Suite – such as the Business

Warehouse (BW), Business-to-Business Procurement (BBP) – and the SAP kernel.

• Underlying hardware and software services, such as the database services, network and operating system

services, and various hardware services, including servers, disks, memory, and uninterruptible power supply

(UPS).

The risk of unplanned downtimes occurring can be minimized by avoiding single point of failures (SPOFs) in a complex

system landscape. For the different components in a complex system landscape, there are several ways of avoiding

these SPOFs.

7.2 Single Point of Failure

No measures for avoiding unplanned downtimes specified in the following list are a safeguard against logical errors.

You can only protect against logical errors by implementing the appropriate backup and recovery measures.

The following table provides a list of SAP CC components, their SPOFs, and their corresponding high availability setup.

114 PUBLIC


High Availability

SAP CC 4.1

Component

Single Point of

Failure

Failure Description or

Business Impact

HA Setup Description

Core Server Dispatcher instance Business critical: no external communication functions, no

intelligent management of all

other instance types of the

server

Already included

Several instances must be installed

on different hosts

All instances are running and are

active. Only one instance (named

master) is responsible for the

management of the instance map.

Rater instance Business critical: no rating and no charging services, no

balance management

function

Already included


on different hosts

Guider instance Business critical: no rating

and no charging services can

be provided

Already included


on different hosts

Taxer instance Business critical: no rating

and charging services with US

telecommunication taxes.

The VAT services are still

available depending on the

configuration of the server.

Already included


on different hosts

Updater instance Business critical: no master

data can be managed, and no

refill request can be

processed

Already included


on different hosts

All the updater instances are running

but only one is active. The other

instances are reserved for backup

purpose.

The interfaced applications must be

able to contact all the updater

instances. A particular

implementation may be required.

Core Database Database Business critical: SAP CC

system is down

Use the RAC edition of Oracle EE or

SE

In case of failure of an instance of the

Oracle RAC Database, some events may

not be charged.

Use failover mechanism of MS

SQLServer

Diameter Server Server program Business critical: no rating

and charging services can be

provided via this channel

Already included



SAP CC 4.1

Component

Single Point of

Failure


Business Impact


Several servers must be installed on

different hosts

All servers are running and are

active. The network elements are

configured with all the Diameter

Servers.

Other

Component

Single Point of

Failure


Business Impact


Operating

System

OS

Memory (storage)

Memory Business critical: system is down (no data or files can be

created and stored)

SAN or RAID technology

Network Network elements Business critical: system is down (no communication)

Redundant cabling

Active components (hubs, switches,

routers)

Network Interface Card (NIC)

SAProuter

Network File System (NFS)

Note

The components or subcomponents of SAP CC 4.1 that are part of a batch mode scenario (offline charging) are not

listed in this table: BART Server, BART Database, Communications Taxing Server (CT Server), and Bulkloader

instance of the Core Server.

7.3 High Availability in SAP CC 4.1

High availability for SAP CC 4.1 is achieved through deploying its components with a specific landscape architecture.

Only the components with real time services for online charging have a HA concept.

7.3.1 HA Concepts

Component Description

Core Server See HA Setup

116 PUBLIC


High Availability

Component Description


information about the mechanisms provided to

ensure HA.

Core Database High availability is only achieved with Oracle RAC SE

or Oracle RAC EE

Diameter Server See HA Setup

BART Server HA not relevant

This component is only used for the offline charging that

is a batch processing mode that does not require high

availability.

BART Database HA not relevant

This component is only used as backend for the offline

charging that is a batch processing mode that does not

require high availability.

Communications Taxing Server HA not relevant

The calculation of US taxes by SAP CI is performed in a

batch mode that does not require high availability.

How to define and install your landscape for high availability is described in the Sizing Guidelines and in the Sizing

Guides available in SAP Help Portal at the following location: https://help.sap.com/cc41 Planning

7.3.2 HA Setup

Component HA Setup Description

Core Server Several instances must be installed on different hosts on the landscape.

Deployment rules and recommendations are provided in the Sizing Guidelines document for

determining your technical landscape architecture.

Consult the SAP CC 4.1 Installation Guide for applying the determined landscape architecture.

Consult the SAP CC 4.1 Library (Application Help) for details about the mechanisms performed

by the instances of the Core Server system for achieving the high availability.

Core Database High availability is only achieved with Oracle RAC.

Consult the documentation provided with this RDBMS.

In case of failure of an instance of the Oracle RAC database, you may need to reset the

communications with the SAP CC system using the Admin+ user interface.

https://help.sap.com/cc41

https://help.sap.com/cc41




Diameter Server Several servers must be installed on different hosts on the landscape.

The network elements (ex.: Service Control Points (SCP)) in the intelligent network (IN) must be

configured with all the installed Diameter Servers.

7.3.3 High Availability for Third-Party Components

For more information about high availability for database, operating system, hardware element, network element of

disk technology, consult the SAP NetWeaver 7.0 EHP1 Technical Operations Manual at: http://help.sap.com SAP

NetWeaver SAP NetWeaver 7.0 including Enhancement Package 1 System Administration Technical Operations

Manual General Administration Tasks High Availability SAP High Availability documentation

7.3.4 HA Setup Change


Core Server It is possible to add some instances of the Core Server system to improve the high availability.

You must determine the new instances to be added to the production landscape according to

the sizing guidelines and just install and start these new instances:

• Guider instances

• Rater instances

• Taxer instances



118 PUBLIC


Purging and Archiving

8 Purging and Archiving

See:

• Getting Started

• Detailed Purge and Archive in Database

• Archiving Logs

8.1 Data Purging and Archiving

Data purging and archiving allows you to:

• Transfer out-of-date data from the back-end database system to a file system, to later move this data in another

consistent and secure storage system

• Possibly definitively delete this source data, to decrease the global database size and increase the performance of

the system

Notes

• Consider also the outdated technical data that is not stored to a back-end database but to the file system. See

Management of Outdated Technical Data, page [101].

• The logs generated by SAP CC are not stored to the back-end database. Therefor consider the log archiving in

this chapter.

8.2 Detailed Purge and Archive in Core Database

Caution

The purge and archive functionalities are only available for Sybase ASE, Oracle, and MS SQL Server. They are not

available for IBM DB2.

8.2.1 Core Server and Core Database

To keep a constant volume size for the database or to control its maximum size, it is necessary to purge some out-of-

date data. This purge can be periodical or not, automated or manual. A database that is too large can dramatically

decrease the global performances of SAP CC.

You may want to define purge and/or archiving for:

• Audit data


Purging and Archiving PUBLIC 119

○ SAP CC stores audit information when the auditing features are enabled in the system. No archiving

mechanism is provided, but two commands of the Admin+ user interface give the possibility to purge the

different audit data recordings related to the Data and Operation Auditing features. For further information

about this purging mechanism, please refer below.

• Allowances data

○ When the Allowances Management feature is used, SAP CC stores different information related to allowances.

No archiving mechanism is provided, but it is possible to purge this data manually (using the Admin+ user

interface) or automatically (using a dedicated scheduler). For further information about this purging

mechanism, please refer below.

• Idempotency management data

○ SAP CC stores information to ensure safe operation of either refilling services invocation or Web Services

consumption. This data must be regularly purged to warranty high performances of the SAP CC system. Refer

to the Periodic Tasks section in this guide. The old data is stored in the WS_IDEMPOTENCY table of the Core

Database.

• Technical data relating to job operations

○ SAP CC stores information about the execution of job operations performed via Web Services, such as the job

status. This data is stored in the WS_JOB table of the Core Database and must be regularly purged to ensure

the global performance of the SAP CC system. For further information, refer to the Periodic Tasks section in

this guide.

8.2.2 Archiving and Purging Audit Data

To manage the security and audit level of your systems, the Data and Operation Auditing features give the possibility to

track the operations that are requested by your SAP CC users, to log changes to persistent configuration data, and to

record the before and after versions of the different data objects impacted by these user operations.

Audit data is created according to the system configuration of your running SAP Core Server system. For example,

view the AUDIT_ACTIVATION and AUDIT_OBJECT_ACTIVATION parameter values to know the current system

settings.

All this data is stored in the following tables of the back-end database system (Core Database):

Audit Data Recording Generation Database Table Reserved Storage Space

(Tablespace, Filegroup,

Segment)

Object change logs Always created OBJECT_CHANGE_LOG OBJECT_CHANGE_DATA

Object snapshots Depends on the system configuration

OBJECT_SNAPSHOT OBJECT_CHANGE_DATA

Operation execution

recordings

Depends on the

system configuration

USER_OPERATION CATALOG_DATA

As the auditing functions can lead to a large number of recorded audit data, they may significantly impact the

performance of the whole SAP CC system. SAP highly recommends that you perform manual purging operations

regularly.

Depending on your security policy, you may need to plan the archiving of this audit data.

120 PUBLIC



8.2.2.1 Archiving Out-of-Date Audit Data Recordings

To archive the audit data recordings, refer to the database documentation.

8.2.2.2 Purging Out-of-Date Audit Data Recordings

To purge out-of-date audit data recordings, you use the following commands of the Admin+ program user interface:

• purge_user_operations, which gives the possibility to purge the out-of-date data related to the execution of user

operations, stored in the USER_OPERATION table

• purge_object_change_logs, which gives the possibility to purge the out-of-date data related to both the object

change logs and their associated object snapshots, stored in the OBJECT_CHANGE_LOG and

OBJECT_SNAPSHOT tables

For more information about these commands, refer to the command-line help of the Admin+ user interface, or refer to

its primary help in the SAP CC User Interfaces online documentation.

Notes

• To decrease the volume of audit data recordings, you can fine configure the audit domains that define the auditable objects and auditable user operations. Depending on your business and technical requirements, you

may exclude some elements from the auditing functions. Consult the SAP CC Configuration Guide about the

AUDIT_OBJECT_DOMAIN and AUDIT_DOMAIN system parameters, see page [13].

• For more information about the Data Object Auditing feature and the User Operation Auditing feature, refer to

the Application Help documentation. You may consider some option

8.3 Detailed Purge and Archive in BART Database

8.3.1 BART Server and BART Database

The following procedures enable the DBA to purge and archive outdated data (Consumption Detail Records). It is also

explained how to reuse archived data. The purge can be periodical or not, automated or manual. The old data to be

purged is stored in the CDR table of the database.

The archive period cannot be less than the retention period configured at installation time (see PARTITION_DAYS on

the PARTITION_PURGE table). Consult the SAP CC Configuration Guide for more information.

Legal and local policy may also apply.

Notes

• Refer to the purge and archive tables in the database schema to know the current configuration of the purge

and archive process

• You must be connected as DBA to your RDBMS to use the following procedures

• BART Server must be shut down while purging or archiving the BART database



8.3.1.1 SAP HANA

The following table describes the procedures to use for configuring data purge and archive:

Procedure overview Description

MANAGE_PURGE This procedure performs a purge without archiving the purged data.

Caution

This procedure definitively removes the data

MANAGE_ARCHIVE This procedure archives the data in a CSV file.

Caution

Do not use this procedure if the archived database is not stored on a safe storage

system (SAN or local RAID1-5 drive)

IMPORT FROM CSV

FILE ‘<file>’ INTO CDR

WITH FAIL ON INVALID

DATA

This statement imports the data from a CSV file into the database.

Note

For more information, consult the documentation of the IMPORT FROM CSV

statement in the SAP HANA SQL and System Views Reference, available at:

http://help.sap.com/hana_appliance

The following arguments are required for the MANAGE_PURGE procedure:

• toDate (DATE): the maximum consumption date (excluded) of the CDRs to purge

• retentionPeriod (INTEGER): the period during which CDRs must be kept for rerating, expressed in days

• checkCDR (INTEGER)

○ 0 means: Do not check the status of the CDRs to be purged

○ 1 means: Check the status of the CDRs to be purged

The following arguments are required for the MANAGE_ARCHIVE procedure:

• toDate (DATE): the maximum consumption date (excluded) of the CDRs to archive

• retentionPeriod (INTEGER): the period during which CDRs must be kept for rerating, expressed in days

• checkCDR (INTEGER)



• archiveDirectory: the directory where the data will be archived.

○ The directory must exist and be writable

○ The exported data will be located in the file

“<archiveDirectory>/export/<schema>/CD/CDR_ARCHIVE/data”

○ If the file already exists, its content is replaced

http://help.sap.com/hana_appliance

122 PUBLIC



The “IMPORT FROM CSV” statement must be executed with the path of the CSV file, which contains the data to

import.

8.3.1.2 Sybase ASE

The following table describes the procedures to use for configuring data purge and archive:


MANAGE_ARCHIVE Use this procedure to copy the data to be purged into data files in a given directory.

Notes

• The archived partitions are removed from the database

• This procedure can also be used to remove data without archiving them into

data files (using the “purgeWithNoArchive” argument described below)

Caution Do not use this procedure if the archived database is not stored on a safe storage

system (SAN or local RAID1-5 drive)

IMPORT_ARCHIVE This procedure allows the DBA to re-import into the same database an existing archive.


• destinationDirectory (nvarchar 1024, mandatory)

○ Destination directory in which archives are stored

• checkCDR (integer, default 1)

○ 0 means: Do not check the status of the CDRs to archive

○ 1 means: Check the status of the CDRs to archive

• force (integer, default 0)

○ 0 means: Stop the procedure if CDRs are in status (0, 1, 7) for those dates (result of the request to check

CDRs).

○ 1 means: Do not stop the procedure if CDRs are in status (0, 1, 7) for those dates.

• purgeWithNoArchive (integer, default 0)

○ 0 means: archive and remove the partitions

○ 1 means: only remove the partition

The following arguments are required for the IMPORT_ARCHIVE procedure:

• fromDate (varchar)

• toDate (varchar)

• archiveDBName (varchar)



8.3.1.3 Oracle SE, Oracle EE

This table describes the package procedures to use for configuring data purge and archive.

Package procedure overview Description

BART_ARCHIVE_PURGE.MANAGE_PURGE This procedure enables administrators to

perform a purge. It detaches automatically

the tablespace as a transportable tablespace

to archive the data.

Store the purged data (transportable

tablespace) and the data dump file (.dmp) on

a removable backup medium.

BART_ARCHIVE_PURGE.MANAGE_PURGE_WITHOUT_ARCHIVE This procedure enables administrators to perform a purge without archiving the

purged data.

Caution This procedure definitively destroys the

data.

BART_ARCHIVE_PURGE.IMPORT_ARCHIVE This procedure allows the DBA to re-import

into the same schema an existing archive

container that has been previously detached

from this schema.

Note Copy the archive to the SAN (in the

appropriate directory) before applying

this procedure and keep a backup copy

for you.

BART_ARCHIVE_PURGE.CLEAN_IMPORTED_ARCHIVE This procedure deletes all the partitions that

have been re-created from existing archives.

Caution This procedure destroys the data. You

must have a backup of the archive before

applying the procedure.

The following arguments are required for the BART_ARCHIVE_PURGE.MANAGE_PURGE procedure:





○ 0 means: Stop the procedure if CDRs are in status (0, 1, 7) for those dates (result of the request to check CDRs).


124 PUBLIC



The following arguments are required for the BART_ARCHIVE_PURGE.MANAGE_PURGE_WITHOUT_ARCHIVE

procedure:





○ 0 means: Stop the procedure if CDRs are in status (0, 1, 7) for those dates (result of the request to check CDRs).


The following arguments are required for the BART_ARCHIVE_PURGE.IMPORT_ARCHIVE procedure:



8.3.1.4 MS SQL Server

This table describes the procedures to use for configuring data purge and archive.


MANAGE_ARCHIVE Use this procedure to copy the data to be purged in a new empty database.

Manually detach this database to create an archive of the data including the old

partitions. Store the archive on a removable backup medium.

MANAGE_PURGE This procedure removes the already archived partitions from the current database.

Caution Do not use this procedure if the archive database is not stored on a safe storage

system (SAN or local RAID1-5 drive).

IMPORT_ARCHIVE This procedure allows the DBA to re-import into the same database an existing archive.






○ 0 means: Stop the procedure if CDRs are in status (0, 1, 7) for those dates (result of the request to check

CDRs).



The following arguments are required for the IMPORT_ARCHIVE procedure:






8.4 Archiving Logs

Depending on the configuration of your SAP CC systems, the volume of the logs can increase. You must monitor their

sizes and determine a policy for archiving all the logs produced.

Consult the Log and Trace Files section for details about the locations of these files; see page [53].

126 PUBLIC


Software Change Management

9 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and testing

procedures for complex software landscapes and multiple software development platforms. These functions support

your project teams, development teams, and application support teams.

The goal of Software Change Management is to establish consistent, solution-wide change management that allows

for specific maintenance procedures, global rollouts (including localizations), and open integration with third-party

products.

9.1 Software Maintenance

You must maintain all your SAP Convergent Charging 4.1 systems up-to-date in the SAP system landscapes. You must

schedule regular maintenance and one-off maintenance activities.

9.1.1 One-Off Maintenance

SAP has adapted our major release strategy to better fit your adoption cycle. To ensure that you benefit from new

developments and innovations while minimizing the impact on your core operational systems, SAP uses support

packages (SPs) to speed up the delivery of new functions.

With SAP support packages, you can install and activate new functions depending on your business needs and

requirements without having to perform a system upgrade.

You can selectively implement the new functions and activate the software upon business demand. As a result, you can

isolate the impact of software updates and make new functions available faster due to shortened test cycles.

Notes

As an administrator of SAP Convergent Charging, you manage the implementation of the latest support packages

and patch levels. See:

• Support Package and Patch Implementation, page [130]

○ Support Packages (SPs), page [130]

○ Patches, page [131]

9.1.1.1 Software Downloads

You can download the SAP Convergent Charging 4.1 software in the SAP Software Download Center (SWDC) that is

available in SAP Support Portal.

https://support.sap.com/software.html

http://support.sap.com/


Software Change Management PUBLIC 127

9.1.2 SAP CC Software Units

Maintenance Regular Maintenance (Period) One-Off Maintenance

Core Server Monthly

For the US Telco tax management

function

Yes

Consult the Support Packages and Patch

Implementation section in this document

[page 130]

Diameter Server N/A

No software change

Yes

BART Server N/A

No software change

Yes

CT Server Monthly


function

Yes

Frontend Graphical User

Interfaces

All the standalone tools

N/A

No software change

Yes

Java Libraries

Core SDK, BART SDK

N/A

No software change

Yes

9.1.2.1 Third-Party Components

Maintenance Regular Maintenance (Period) One-Off Maintenance

Database System

(RDBMS)

Check with your provider Check with your provider

BillSoft EZTax Monthly


function

N/A

9.2 Regular Maintenance

Regular maintenance is key to your systems.

128 PUBLIC



9.2.1 BillSoft EZTaz Technology Monthly Update Maintenance

The monthly update of the BillSoft EZTax installation(s) is mandatory for the tax function for US telecommunications.

You must update three categories of units:

• The BillSoft EZTax installations

• A central repository CC_EZTAX used by SAP Convergent Charging

• The relevant server systems of SAP CC (CT Server, Taxer instances of the Core Server)

At the original installation time, SAPinst has created a specific central repository dedicated to the management of

application data. It is named CC_EZTAX in the following procedures and may differ on your landscape.

9.2.1.1 Maintenance of BillSoft EZTax Software

You need to monthly update your BillSoft EZTax software and data.

• It is installed on each machine that hosts one or several Taxer instances of the SAP CC Core Server.

• It is installed on the machine that hosts the SAP CC Communications Taxing (CT) Server.

Procedure:

Consult the maintenance procedures from the BillSoft EZTax documentation.

9.2.1.2 Maintenance of CC_EZTAX Central Repository

You need to monthly update the CC_EZTAX central repository that includes EZTax software files and data required by

SAP Convergent Charging software. It has been created at the installation time by SAPinst.

This folder must contain the changed files:

• the transervdesc.txt file

• the subdirectories db, jar and lib:

○ db/ contains EZTax database files

○ jar/ contains the file eztax.jar

○ lib/ contains EZTax library files depending on the operating system: *.dll (MS Windows) or *.so (UNIX)

9.2.1.2.1 Procedure:

Once you have updated the BillSoft EZTax installations, you update the CC_EZTAX central repository by copying

necessary files and directories listed above.

Notes

• Verify if the CC_EZTAX central repository is shared by several SAP CC Server Systems: CT Server, Taxer

instances of the Core Server. These systems will be automatically updated when you restart them.



• Verify if the CC_EZTAX central repository is shared by another major version of SAP Convergent Charging.

These systems will be automatically updated when you restart them.

• Consult the SAP CC Installation Guide for details and recommendations.

Maintenance of Taxer Instances of the Core Server

You need to monthly update your BillSoft EZTax software files and application data. It has been installed on each

machine that hosts one or several Taxer instances of the SAP CC Core Server system.

The CC_EZTAX central repository must be up-to-date.


• Stop and restart sequentially all the Taxer instances of the Core Server system. When restarting, each Taxer

instance will update its local installation folder by copying all these files to the folder: /config/eztax/..

• Use the Setup Tool user interface of SAP CC for updating the Core Database system with the latest

transaction/service types declared in the transervdesc.txt file present in the CC_EZTAX repository:

○ Use the eztax importTSTypes command and this file for inserting the new types in the database

• Use the Admin+ user interface of SAP CC for updating the relevant instances of the Core Server system:

○ Start admin+ and log on as administrator

○ Use the refresh_transerv_list command for updating the Updater instance(s)

Caution

Do never stop all the taxer instances at the same time. Prefer updating one instance after the other.

9.2.1.3 Maintenance of CT Server

You need to monthly update your BillSoft EZTax software files and data on the machine that hosts the SAP CC

Communications Taxing (CT) Server system.

The CC_EZTAX central repository must be up-to-date.


Stop and restart sequentially the CT Server systems. When restarting, the CT Server system updates its local

installation folder by copying all these files to the folder: /config/eztax/.

130 PUBLIC



9.3 Support Package and Patch Implementation

Recommendation

SAP recommends that you implement the delivered support packages (SPs) and patches in your SAP system

landscapes to maintain the SAP Convergent Charging 4.1 software. Plan your maintenance operations during

periods with low business traffic.

You can find the maintenance versions of SAP Convergent Charging 4.1 in the SAP Software Download Center (SWDC)

in SAP Support Portal at the location: https://support.sap.com/swdc . The latest support package is always

available. It includes a complete version of the SAP CC software product.

You use this latest version as basis for an initial installation (new implementation project phase), for an update of a

running system (production, quality control, test, development), or for a migration project (from former main release

of SAP CC).

An SAP Note details the content of the version and the update procedures and lists the patch levels that are available.

9.3.1.1 Support Packages (SPs)

A support package is a complete maintenance version of the SAP CC 4.1 software. You can install it as initial version or

you can update a system landscape with the latest version. It relates to all the server systems, user interfaces, and

other applications of SAP Convergent Charging.

Note

SAP Convergent Charging 4.1 does not include any Support Package Stacks (SP-Stacks), which are sets of support

packages.

Before implementing and installing a support package, check in its delivery SAP Note if a patch is available.

Note

SAP Convergent Charging 4.1 does not provide you with the support packages (SPs) in the Support Packages and

Patches subarea in the SAP Software Download Center (SWDC) in SAP Support Portal. The support packages of

SAP CC 4.1 are only available in the Installations and Upgrades subarea.

You update the following components of SAP Convergent Charging in your SAP system landscape:

SAP CC Component Software Unit: Server

System

Software Unit:

User Interface

Software Unit:

Library

Description

Main components

Core Server and

Tool

Core Server

• Server system


Core Tool Core SDK (for

mediation systems)

• Java libraries

• API

specifications

Online and offline

charging system

Server system

User interfaces

Java libraries

https://support.sap.com/swdc

https://support.sap.com/swdc



SAP CC Component Software Unit: Server

System

Software Unit:

User Interface

Software Unit:

Library

Description

BART Server and Tool

BART Server

• Server system


BART Tool BART SDK (for mediation systems)

• Java libraries

• API

specifications

Optional Components

(server systems)

Diameter Server Diameter Server

• Server system

Online charging

based on diameter

communications

Communications

Taxing (CT) Server

Communications Taxing

Server

• Server system

In an integrated SAP

Solution scenario

with SAP ERP/FI-CA

Other Components

Import/Export

Connector

IEC Application CAT Tool

Components of the SAP CC Software

9.3.1.2 Support Package Location

You can find the latest version of SAP CC 4.1 in SAP Support Portal at: https://support.sap.com/installations A-Z

Index C SAP Convergent Charging SAP Convergent Charging 4.1 Installation

9.3.1.3 Patches

A patch is a partial maintenance version of SAP CC 4.1. It relates to one or several software units. Patches may exist for

the following software units:

SAP CC Software Unit

(Technical Name)

Software Unit Component Product Instance in

PAM

BART SDK 4.6 BART SDK BART Server and Tool BART Tool / Frontend

BART SERVER 4.6 BART Server BART Server and Tool BART Server

BART TOOL 4.6 BART Tool BART Server and Tool BART Tool / Frontend

https://support.sap.com/installations

https://support.sap.com/installations

132 PUBLIC



SAP CC Software Unit

(Technical Name)

Software Unit Component Product Instance in

PAM

CAT TOOL 4.6 CAT Tool Import/Export Connector IEC Tool / Frontend

CC CORE SDK 4.6 Core SDK Core Server and Tool Core Tool / Frontend

COMMUNICATIONS

TAXING 4.6

CT Server Communications Taxing (CT)

Server

Communications Taxing

Server

CONVERGENT CHARGING 4.6

Core Server Core Server and Tool Core Server

CORE TOOL 4.6 Core Tool Core Server and Tool Core Tool / Frontend

DIAMETER 4.6 Diameter Server Diameter Server Diameter Server

IEC 4.6 IEC Application Import/Export Connector IEC / Frontend

Software Units of SAP Convergent Charging 4.1

Note

You use the technical names of the SAP CC software units when downloading the patch levels. The naming

convention includes a number that relates to the technical version number of your SAP Convergent Charging

software: 4.6 refers to the commercial release 4.1 of SAP CC.

9.3.1.4 Patch Location

You can find detailed information about the availability of support patches for SAP CC 4.1 in SAP Support Portal at:

https://support.sap.com/patches A-Z Index C SAP Convergent Charging SAP Convergent Charging 4.1

SAP CC

Subcomponent

Server System User Interface Library Description

Main

subcomponent

Core Server CONVERGENT CHARGING 4.6

CORE TOOL 4.6 CC CORE SDK 4.6 Online and offline charging system

Server system

User interfaces

Java libraries

Optional

subcomponents

(server systems)

https://service.sap.com/~form/handler?_APP=00200682500000001943&_EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=INTRO_SWDC_SP_C&V=MAINT

https://support.sap.com/patches

https://support.sap.com/patches



SAP CC

Subcomponent

Server System User Interface Library Description

Diameter Server DIAMETER 4.6

Online charging based on diameter

communications

BART Server BART SERVER 4.6 BART TOOL 4.6 BART SDK 4.6

Communications

Taxing Server

COMMUNICATIONS

TAXING 4.6

Other subcomponents

IEC

• IEC 4.6

• CAT TOOL

4.6

9.3.2 SAP Notes

SAP Notes provide detailed information on new maintenance versions (support package or patch). They include the

update operations and procedures to implement a maintenance version of the SAP CC software component.

Caution

Refer to the relevant SAP Notes before implementing a support package (or a patch) to update your SAP CC 4.1

your system landscapes. Consult the update procedures and prerequisites in these documents.

The SAP Note of a support package lists all the patch levels that relate to this support package. You plan the

implementation of these support patches.

Example

The following SAP Notes enable the implementation of the support package 1 of SAP Convergent Charging 4.1:

• 2269858 - SAP CC 4.1 Support Package 1

• 2273944 - Technical Implementation of SP 1

You can easily update your SAP system landscapes with these notes and this guide.

9.3.3 Support Package Downloads

A support package is included in a multispanning archive that is distributed to several files available for downloads.

Download all the files in the same local repository and unpack the archive.



134 PUBLIC



Note

Refer to the SAP Note 886535 for more information about multispanning archives.

Once unpacked, the local repository includes a copy of an installation DVD. The name of the root directory is the SAP

material number of the installation DVD. It includes several files and the DATA_UNITS directory.

Note

Refer to the SAP CC 4.1 Installation Guide documentation for more information about the detailed content of an

installation DVD.

9.3.4 Implementation Plan

Before you begin the actual update, you must first plan it carefully. This includes requesting all the SAP Notes you

need. Careful planning is a prerequisite for a successful SAP system update.

The update sequence includes the following main steps:

• A: Update of the server systems of SAP Convergent Charging

• B: Manual restart of the Core Server instances of SAP Convergent Charging

• C: Update and restart of the other server systems of SAP Convergent Charging

○ Diameter

○ Communications Taxing

○ BART

• D: Update of the client applications and systems that use the Java Library of SAP Convergent Charging such as

SAP Convergent Mediation by Digital Route

• E: Update of the graphical user interfaces and the IEC application of SAP Convergent Charging

○ Core Tool

○ BART Tool

○ CAT Tool

○ IEC

Recommendation

SAP recommends that you first update all the server systems of SAP Convergent Charging. Then you update all the

client applications and systems connected to these SAP CC server systems:

• External applications or other systems that use the Java Libraries of the SAP Convergent Charging

• Graphical user interfaces (GUIs) of SAP Convergent Charging

• SAP CC IEC

When updating an application, the configuration of data may change: it may not be compliant any longer with non-

updated applications.

Do not maintain a system landscape with different versions of the SAP CC server systems, different versions of the

SAP CC GUIs and different versions of the SAP CC Java Libraries installed in the client applications or systems

connected to a server system of SAP Convergent Charging.




Caution

Refer to the relevant SAP Notes before implementing a support package (or a patch) to update the SAP CC 4.1

server systems in your system landscapes. Consult the update procedures and prerequisites in these documents.

9.3.5 Planning the Software Maintenance

You decide when to start the update. If you have special requirements regarding the availability of your SAP system,

adjust the process and the length of the upgrade to fit the expected amount of downtime or restricted services in high

availability (HA) environment.

To schedule the software maintenance, prefer periods with low business traffic when possible in your environment.

Otherwise, consider off-peak times to avoid peak traffic periods. Estimate the level of the business traffic flow.

In a high availability (HA) environment, consider periods with limited business traffic. In a non HA environment, you

stop the SAP systems.

During the maintenance update, various actions are performed in the system. The runtime of these actions depends on

various factors and is therefore specific to each SAP system.

Test and validate the update, by applying the maintenance operations to a preproduction system.

9.3.6 Testing and Validating the Technical Implementation

Test and validate the maintenance update (support package, patch level) before to be able to update the production

system. First, update your preproduction, validation, or quality assurance systems.

9.3.7 Determining the Minimal Production Landscape

In high-availability (HA) environment, you determine for each type of instances in the SAP CC Core Server system, the

count of instances that must run together to handle the business traffic that is expected according to your estimation.

You determine the minimal production landscape.

Use the preproduction systems (or validation systems). Simulate the business traffic and stop some instances.

Caution

If you cannot define this minimal production landscape, do restart the instances one-by-one after the update with

SAPinst. See Manually Restart the Core Server Instances and Other SAP CC Systems, page [139].

9.3.8 Updating the Server Systems

At the scheduled times, you operate the update of the SAP CC systems in your development, test, quality assurance,

preproduction system landscapes to validate the implementation of the new support package or patch level.

Finally, you update the productive SAP CC systems in your production system landscape.

136 PUBLIC



9.3.8.1 Overview

You perform the update of the server systems with the SAPinst user interface on the SAP Global Host of each SAP CC

system.

The update consists in the following stages:

Stage Core Server BART Server Diameter Server CT Server

Data update in the

database

X X N/A N/A

Consult the section about the

regular maintenance for this server.

SAP CC 4.1

software binaries

update

X X X X

Server system

restart

X X X X

Important Note

You do not need to stop the server systems before the update with SAPinst. After the maintenance update, you

must manually restart all the Core Server instances and other SAP CC server systems.

9.3.8.2 Preparation: Identify the Hosts

To update a server system and a system landscape, you will have to launch the SAPinst program:

• On the machines hosting the BART Server system, the Diameter Server system and the Communications Taxing

(CT) Server system

• On the SAP Global Host of the Core Server system

You must identify these hosts before starting the update.

Note

The SAP Global Host of a Core Server system is the first installed host of the SAP system. The SAP Central Instance

is installed on this host and must be a dispatcher instance of the SAP CC system.

To find the global host for the Core Server system:

• Go to the following directory on any machine hosting instances of the Core Server system:

○ <DRIVE>:\usr\sap\<SID>\SYS\profile\ (MS Windows operating system)

○ /usr/sap/<SID>/SYS/profile/ (UNIX and other operating systems)

• Open the profile file DEFAULT.PFL

• See the value of the variable SAPGLOBALHOST



9.3.8.3 Preparation: Copy the DVD

To update a server system, you will have to launch the SAPinst program from the delivered DVD:

• Go to the installation DVD. See the Installation Guide for more information about installation DVD.

• Fully or partially copy the maintenance DVD to the host(s) of an SAP CC system. See the Installation Guide for

more information about preparing the installation folders.

9.3.8.4 Launch SAPinst

To update an SAP CC server system in your SAP system landscape, you must launch the SAPinst program:

• On the machines hosting the SAP CC BART Server system, the Diameter Server systems, and the CT Server

system

• On the global host for the Core Server system

• Execute the following procedure:

○ Go to the CC41_IM_* subdirectory in the installation folder where * is your OS. See the Installation Guide for

more information about the installation DVD.

○ Start SAPinst by launching the sapinst.exe program for MS Windows or the sapinst script for other OSs.

○ Click SAP Convergent Charging Software Life-Cycle Options Update Update – SAP Systems

Note

In a multihost environment, you do not need to launch the SAPinst program from the other hosts of the SAP CC

Core Server system to implement a support package. The instances located on other hosts are automatically

updated when they restart.

SAPinst prompts you for the following parameters:

Installation

Mode

You can update your SAP system either in Typical or Custom mode.

• If you choose Typical, the update is performed with default settings.

This means that you only have to respond to a small selection of

prompts.

• If you choose Custom, you are prompted for all the parameters.

Note

If you do not choose the Custom parameter mode, you can change any

parameter on the Parameter Summary screen.

SAP System

Identification

You must specify the SAP Profile Folder.

138 PUBLIC



SAP System

Administrator

Password

Give the password of the System Administrator.

Note

This screen is only available with MS Windows with remote hosts.

Database User Give the user and the password used to connect to the database.

Note

This screen is only available if the database password has changed since

the last execution of SAPinst.

(Custom Mode only)

Database

Update

Select the SQL scripts to execute.

Update Archives Specify the archives to be updated.

Restart

Instances

In development or test landscapes, you can make the instances or the server

restart at the end of the update. With this option, only the running instances

restart. If you have stopped some instances before the update, they do not

restart.

Important Notes Do not use this option with a HA setup in a production landscape. Prefer

restarting the server systems and Core Server instances manually or with

a custom program.

Because the Diameter Server system is used for online charging, restart

it at off-peak times to avoid service disruption.



9.3.8.5 Manually Restart the Core Server Instances and Other SAP CC Systems

After the update of the SAP CC Core Server system, you must manually restart all its system instances in case of HA

setup.

Recommendations

SAP recommends that you perform the following tasks when updating an SAP CC Core Server system:

• Restart a dispatcher instance first.

• With the HA setup, avoid restarting too many instances at the same time. Restart an instance or a bundle of

instances and wait until it has restarted before restarting another one. The complete restart takes into account

the ends of the cache warm-up functions in the starting instances.

• Do not stop and start all the instances of the same type (all the raters for example) at the same time.

• Before to restart another rater instance:

○ Wait for the successful end of the cache warm-up of the starting rater instances; you can view the

recorded logs and verify the presence of multiple the com.sap.SCC.core_server.000404 log messages.

○ Ensure that the warm-up is fully and successfully completed: this expected log entry must be present for

all types of cached data objects (subscriber accounts, provider contracts, and so on) and for all the

database partitions handled by the starting rater instance.

○ Verify that all the log entries are recorded in the log files.

• Before to restart another guider instance, wait for the successful end of the cache warm-up of the starting

guider instances. Verify that the expected log message (com.sap.SCC.core_server.000404) is present in the

log files. It is about the cached data objects named accesses.

Caution

You must keep enough instances running to handle the current business traffic in the system landscape. In case of

high-level traffic, you must have determined the minimal production landscape during the validation of the support

package implementation.

Do not restart too many instances at the same time. If you do not know, restart only one instance after the other.

9.3.8.5.1 Procedure: To restart an instance with the SAP Management Console (SAP MMC):

Apply one of the following procedures to restart an instance of the Core Server system:

(MS Windows) To restart a Core Server instance:

2. Double-click the icon on your Desktop to start the SAP MMC console

3. Click the SAP system containing the instance you want to restart

4. Right-click the instance and choose Restart

5. Verify the logs

(UNIX and Linux) You can use the SAP Management Console applet to restart a Core Server instance.

Launch the SAP Management Console by opening the following HTML file:

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/sapcc_messageids/com.sap.SCC.core_server.000404.html

140 PUBLIC



• /usr/sap/<SID>/SYS/exe/uc/<OS_PLATFORM>/servicehttp/sapmc/sapmc.html

• /usr/sap/<SID>/<INSTANCE_NAME>/exe/servicehttp/sapmc/sapmc.html (in each instance folder)

where <INSTANCE_NAME> corresponds to the name of the instance of the SAP CC system. By default, it is

composed of three characters and two digits.

Note

Use a web browser capable of running Java applets.

9.3.8.5.2 Procedure: To restart an instance with the SAP Control:

You can use SAP Control command-line application to restart a Core Server instance. See SAP Control, page [68].

9.3.9 Updating the Client Applications Based on the Java Libraries

You must update all the external applications or systems that use the Java Libraries of the SAP Convergent Charging.

9.3.10 Updating the Graphical User Interfaces and the IEC Application

You must update all the Graphical User Interfaces and the IEC application of SAP CC 4.1.

To update the user interfaces and the IEC application, you have to:

• Get the zip files. They are available on the DVD in the directory CC41_TOOLS_CONTENT_UC_OSIND. See the

Installation Guide for more information about the DVDs and the zip files to use.

• Unzip the appropriate file in the installation directory.

• Save the old configuration files (*.config).

• Rename (from *.config.sk to *.config) and customize the new configuration files accordingly.

• Download and install the SAP JVM 8.1. See the Installation Guide for more information about this procedure

9.3.11 Post Processing

Verify the last minute information in the relevant Technical Implementation Note provided with each support package

of SAP CC.



9.3.11.1 Post-Processing Tasks After a Core Server Update

9.3.11.1.1 Task 1:

As of SP 1, SAP recommends that you verify the values of the LS_TRC_DOMAIN system parameter in your running SAP

CC Core Server systems. New tracing domains are available: DATA, PERF, and PPI. In a production SAP CC system, set

up the system parameter with all the existing domains.

You can use the reset command of Admin+.

9.3.11.1.2 Task 2:

In an integrated SAP Solution with SAP Convergent Invoicing (SAP CI) in SAP ERP, please verify that the Event Date

Shifting function is enabled in the rater instances of your running SAP CC system. There is no basic system parameter

to view but there is an advanced configuration record to check.

In Setup Tool, export the CIF configuration settings and check that the eventDateShifter XML nodes are present in

the file. See the SAP CC Configuration Guide for more information and user assistance, page [13].

142 PUBLIC


Troubleshooting of SAP CC

10 Troubleshooting of SAP CC

This section provides a central starting point for problem solving with SAP Convergent Charging. It provides guidance

on how to deal with issues that may come up when implementing or operating SAP Convergent Charging applications

and systems (server systems, user interfaces, and other programs).

It discusses the following troubleshooting information:



10.1 Getting Assistance

You can use the Troubleshooting sections in the SAP CC documents to get help in unexpected situations when working

with the following domains:

Installation Troubleshooting Software Maintenance

Troubleshooting

Upgrade Troubleshooting

• Preparations

• Initial installation

• Post-installation activities

• Implementation of a support

package (SP)

• Implementation of a patch

level

• Preparations

• Implementation validation

• Upgrade processing

• Post-upgrade activities

Development and Integration

Troubleshooting

Configuration Troubleshooting Performance an Health

Troubleshooting

• Java development and

integration

• Web Services integration

• Technical configuration

• Business configuration

• Systems

• Communications

• Charging policy processing

• Internal functions


Troubleshooting of SAP CC PUBLIC 143

User Troubleshooting Log Troubleshooting Components

• SAP users • Technical configuration

• Business configuration

○ System

○ Master Data

• Server systems

• Java Virtual Machines (JVM, J2EE)

• User interfaces

• System landscapes


Advanced Troubleshooting

• Tracing by Support Team

10.1.1.1 Installation Troubleshooting

Refer to the SAP CC Installation Guide for more information about troubleshooting during the preparations, initial

installation, or the post activities.

10.1.1.2 Software Maintenance Troubleshooting

Refer to the SAP CC Operations Guide (this document) for more information about troubleshooting during the software

maintenance operations (support package or patch implementation). See the Software Change Management section,

page [126].

Refer also to the available SAP Notes that are associated to a delivery about last-minute information and

troubleshooting information.

10.1.1.3 Upgrade Troubleshooting

Refer to the SAP CC Upgrade Guide for more information about troubleshooting during the preparations, upgrade

processing, and follow-up activities.

10.1.2 Development and Integration Troubleshooting

10.1.2.1 Java Development Troubleshooting

Refer to the Java API References of SAP CC for more information.

144 PUBLIC



10.1.2.2 Web Services Integration Troubleshooting

Refer to the Web Services Documentation of SAP CC for more information.

10.1.3 Technical Configuration Troubleshooting

Consult the SAP CC Configuration Guide and the primary help of each user interface of SAP CC.

10.1.4 Business Configuration Troubleshooting

10.1.4.1 System Configuration

Consult the SAP CC Configuration Guide and the primary help of each user interface that is available to administrate

the SAP CC systems.

10.1.4.2 Data Configuration

Consult the SAP CC Configuration Guide and the primary help of the Core Tool user interface.

10.1.5 Component Troubleshooting

This section cannot provide an easy step-by-step guide to troubleshooting of every single possible problem that might

occur when running SAP CC.

10.1.5.1 Server Systems

To troubleshoot problems with an SAP CC system, we recommend setting up SAP Solution Manager.

10.1.5.2 Java Virtual Machines

Troubleshooting problems with SAP JVM:

• Memory issues

• Garbage collection processing issue

• Performance issues

• Crashes

The worst case problem from an SAP JVM point of view is an actual VM crash. Although the VM crash should be

detected and the server node will be restarted, it still indicates a serious problem.



Putting it simply, there are two possible reasons for a VM crash: an out-of-memory situation that cannot be handled

easily, or a VM bug (although some other causes are possible, for example hardware issues etc.).

To render further analysis possible, the SAP JVM will write an extensive protocol about its current state and the last

actions performed before the crash. This protocol can be found in a file called hs_err_pid<process id>.log in the

working directory. Although the content of the protocol can be very technical and hard to understand without expert

knowledge, it can help to recognize out-of-memory situations or give hints about the crash cause to non-expert users

as well. In any case, if you want to report the problem to SAP, it will certainly help to provide the crash protocol along

with your incident report.

10.1.5.3 User Interfaces

See the primary help of each user interface of SAP CC.

10.1.6 Log Troubleshooting

Logs are a starting point for identifying a potential anomaly.

Setup some log monitoring features with SAP Solution Manager.

10.1.6.1 Working with Logs from SAP CC

Refer to the SAP CC Log Message Reference for more information about the log messages generated by the SAP CC

systems and about the resolution plans to troubleshoot potential problems.

10.1.6.2 Logs from another Interfaced System

A system or an application communicates with SAP CC systems in the SAP system landscape. It records log entries

about issues and potential anomaly.

Depending on your system landscape, refer to the troubleshooting documentation of the following systems:


• Mediation system

• CRM or provisioning system

• ERP system

• Voucher system

Important Note

These proprietary logs can include information that relates to and comes from a connected SAP CC system. This

information provides you with details about the errors and exceptions in the SAP CC system.

For example, a log in a CRM application can relate to an error code and an exception replied by the SAP CC Core

Server system.

Refer to the following user assistance:

146 PUBLIC



• SAP CC Java API References

• SAP CC Web Services Documentation

• SAP CC Error Code Reference

10.1.6.3 Traces from SAP CC

Your SAP Support Team can use traces generated by SAP CC to determine the root causes of a problem.

10.1.7 Performance Troubleshooting

Performance and scalability are fundamental characteristics of the SAP CC software. The most important indicators

for system performance are response time and data throughput. A system behaves in a predictable manner when

throughput rises.

Performance troubleshooting facilitates and optimizes the resolution of performance problems in the SAP system

landscape or in a particular component:

• SAP CC Core Server systems

• Other SAP CC systems

• Systems and applications connected to an SAP CC system

• SAP CC user interfaces (for example SAP CC Core Tool)

Performance troubleshooting facilitates and optimizes the resolution of performance problems with the convergent

charging services and other business services.

• Online charging (event based, session based, stateless rating)

• Offline charging (batch events)

• Isolated symptoms

Refer to the Troubleshooting and Performance Analysis section in this document; see page [155].

10.2 Root Cause Analysis and Exception Management in SAP Solution Manager

Analyzing the root cause of an incident in multi-technology system landscapes with distributed systems requires a

systematic top-down approach.

A root cause analysis is triggered by an incident in IT Service Management or by solution monitoring (system

monitoring or business monitoring).

The objective is to identify and provide:

• Immediate corrective action (workaround) to restore service operations as quickly as possible with minimal

disruption to end users by isolating the area of concern

• Complete solution to the issue at hand



Use the Root Cause Analysis (RCA) functions in SAP Solution Manager to manage the end-to-end analysis, system

analysis, host analysis, and database analysis.

A dedicated work center is the central access to functions and methods for monitoring your SAP solutions and

accelerating problem solving. This improves the availability of your SAP CC 4.1 systems.

Work Center and Reports Description

Root Cause Analysis Work

Center

This work center is the central access to functions and methods for monitoring

your solutions and accelerating problem solving.

This improves the availability of your solutions.

End-to-End Analysis Provides tools to perform cross-component root cause analysis.

System Analysis Provides tools to perform system-specific root cause analysis:

• You can use Log Viewer to display and verify to the logs and traces of the

monitored SAP CC 4.1 systems:

○ Core Server

○ BART Server

• You can use the monitoring consoles of CA Introscope to display and verify

performance view

○ Core Server

Note

Consult the other work centers used for SAP CC in SAP Solution Manager for SAP CC, page [21].


Implement and use Root Cause Analysis in SAP Solution Manager for root cause analysis of SAP CC 4.1. Follow the

Customizing activities outlined in SAP Solution Manager.

10.2.1.2 Related Documentation (Root Cause Analysis Work Center)



Library (English) of Solution Manager 7.1 SP13 Application Operations Root Cause Analysis & Exception

Management

Product Documentation Main Topic Related Topics

SAP Solution Manager 7.1

Application Help

Root Cause Analysis Work Center End-to-End Analysis

System Analysis

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/8a/74df672b024cfa873d4a6bf71bf0a1/content.htm?frameset=/en/86/ee3e0a5bc644af852182e03d1a8042/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=2153&show_children=false

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/8a/74df672b024cfa873d4a6bf71bf0a1/content.htm?frameset=/en/86/ee3e0a5bc644af852182e03d1a8042/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=2153&show_children=false



http://help.sap.com/saphelp_sm71_sp13/helpdata/en/92/c65043f2004b098fda16b8e56ef702/content.htm?frameset=/en/5b/0c9ccfd262427685c245d7ea85cd7a/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=1872&show_children=false




http://help.sap.com/saphelp_sm71_sp13/helpdata/en/8a/74df672b024cfa873d4a6bf71bf0a1/content.htm?frameset=/en/92/c65043f2004b098fda16b8e56ef702/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=2153&show_children=false

http://help.sap.com/saphelp_sm71_sp12/helpdata/en/97/e0881d54174358b8964c1aa11b1d7d/content.htm

http://help.sap.com/saphelp_sm71_sp12/helpdata/en/20/1db257c1324147a1f07b35b9b9c5dd/content.htm

148 PUBLIC



10.2.2 Working with the Root Cause Analysis Work Center in SAP Solution Manager

To troubleshoot problems with SAP CC landscape, you start the Root Cause Analysis work center in SAP Solution

Manager by using SAP Logon and SAP Easy Access.


The Technical Monitoring functions are implemented. See Technical Monitoring and Alerting Using SAP Solution

Manager 7.1 SP13 and Later, page [40].



Works Centers RCA Work Center RCA and Exception Management

10.2.2.2 Display the logs and traces of SAP CC 4.1



• Click Log Viewer. A window displays all the host machines available in this cluster, the status of the Diagnostic

agents, and the declared log stores.

• Select the host and the log or trace files to analyze.

10.2.2.3 Display the performance monitors of SAP CC 4.1



• Click CA Introscope and select the monitoring console you want to use: CA IS Workstation or CA IS WebView. A

window displays the user interface.

Refer to next section for more information about troubleshooting and root cause analysis with CA Introscope for SAP.

10.3 Troubleshooting and Root Cause Analysis Using CA Introscope for SAP

During the production operation phase, you can use CA APM Introscope to monitor manually the performance and

health of the SAP CC Core Server systems in the SAP system landscape. You can use the information delivered by the

monitoring consoles to analyze the SAP CC systems and take appropriate actions when necessary.

You work with the predefined dashboards and alerts as the starting point for troubleshooting. In CA IS Workstation

Console, you view the performance and health metrics in graphical viewers.





http://help.sap.com/saphelp_sm71_sp13/helpdata/en/92/c65043f2004b098fda16b8e56ef702/content.htm?frameset=/en/8a/74df672b024cfa873d4a6bf71bf0a1/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=2154&show_children=false

http://help.sap.com/saphelp_sm71_sp13/helpdata/en/92/c65043f2004b098fda16b8e56ef702/content.htm?frameset=/en/8a/74df672b024cfa873d4a6bf71bf0a1/frameset.htm&current_toc=/en/b3/64c33af662c514e10000000a114084/plain.htm&node_id=2154&show_children=false




Install and use CA Introscope for SAP for technical monitoring and root cause analysis of SAP CC 4.1. Follow the setup

procedure outlined in SAP Note 1453216. Refer to the installation considerations in the Technical Monitoring Using CA

Introscope for SAP, see page [44].

Also, implement and use Root Cause Analysis in SAP Solution Manager for root cause analysis of SAP CC 4.1 to benefit

from extended supportability tools.

10.3.2 Troubleshooting Using CA IS Workstation Console and Investigator

To troubleshoot problems with SAP CC, you use Console and Investigator in the CA Introscope user interfaces (IS

Workstation, IS WebView).

10.3.2.1 Get Started

• Start the CA IS Workstation user interface; see the procedure, page [44].

• Open a monitoring console to display the monitoring dashboards.

• Select a graph in a console dashboard that displays abnormal metric values.

• Move the cursor over a point on the graph to open a tooltip. This tooltip displays information about the metric

name, exact value of the metric, minimum and maximum values for the metric across the period represented by

the data point.

• Press F2 to pin the tooltip.

• Click the hyperlink to open this metric directly in CA IS Workstation Investigator.

Consult the documentation of CA Introscope for more information about the user interfaces:

• Working with Console

• Working with Investigator

10.3.3 Working with Investigator

Investigator displays all the metrics defined for SAP CC. The IS Enterprise Manager system collects or computes these

performance metrics.

Consult the Metric Reference and Performance Troubleshooting documentation about the complete metric hierarchy.

This user assistance details the performance and health metrics and provides troubleshooting information.

The Investigator window displays the Metric Browser. A root node corresponds to the system landscape; subnodes

correspond to the hosts installed in the landscape.

Information about SAP CC systems and system instances is available in the SAP Convergent Charging nodes. This

node is available in each host machine that belongs to the same SAP CC Core Server system. The node name is:

<SID>_<INSTANCE_ID>_SCCCoreServer.



150 PUBLIC



Example

DEV_rater#1_SCCCoreServer

TST_rater#1_SCCCoreServer2

Consider the following elements dedicated to SAP CC. The list may change depending on the:

• Type of SAP CC system instance

• Version of the installed module management

Monitoring

Function

Description

Frontends Provides the lists of metrics that relate to the front-end activities:

• BulkReader: the file system activities that read in bulk mode:

○ Business data resulting from the convergent charging and refilling operations

• HTTP: the public communications via the HTTP Communication Interface (HCI) technical

interface) of SAP Convergent Charging

○ Service operation requests; each type of request is identified by a unique technical key

that is the name of a Java class in the SAP CC Core Server system. Refer to the API

References documentation for the list of the operations that are available in HCI.

Example

CreateChargePlanOplImpl: relates to the creation operation request of a charge plan in

the pricing catalog stored in master data of a service provider

• InternalMessage: the inter-instance communications via the Message TCP

technical interface of SAP Convergent Charging

○ Administration requests, metric requests, rater instance activation request, rater refreshing requests

• Message: the public communications via the Message TCP technical interface of SAP

Convergent Charging; this includes:

○ Handler: details per technical request handler

○ Operation: details per service operation

• WebService: the public communications via the Web Services technical interface of SAP

Convergent Charging; this node includes a subnode for each Web service and the list of

service operations requested by connected applications or systems.

Example

Webservicename



Monitoring

Function

Description

Backends Provides the lists of metrics that relate to the back-end activities:

• InternalMessage: the inter-instance communications via the Message TCP technical interface

of SAP Convergent Charging

• POSTPAID_CIT_WRITER (BulkWriter): the file system activities that write data in bulk mode:

○ Business data resulting from the convergent charging and refilling operations: postpaid charged items

• XXX (BulkWriter): the file system activities that write data in bulk mode:

○ Data temporarily stored in file and resulting from business or technical operations

• XXX (YYY DB): the database where XXX and YYY the db techno (Oracle DB, MS SQL Server

DB, ...)

○ SQL: per statement details

• Message: the public communications via the Message TCP technical interface of SAP

Convergent Charging

JMX Provides the lists of JMX metrics of SAP Convergent Charging: the com.highdeal node includes the following entries.

• Cache: performance metrics about the data caches available in each instance of the SAP CC

Core Server system

Example

Provisioning cache

Note

All the metrics that are visible in the Sensor node, are deprecated. They correspond to the

service statistics information available in the Admin+ user interface and the

SERVICE_STATISTICS system indicator. Refer to the SAP CC System Parameter Reference

documentation for more information about this indicator. Consult the primary help of Admin+

to view manually the information with the get command.

152 PUBLIC



Monitoring

Function

Description

SAP CC For an SAP CC system instance, provides the alphabetical lists of metrics that relates to:

• Connection: performance data related to the availability of the High-speed Messaging

Infrastructure (HMI) that is the low level technical layer of the Message TCP technical

interface.

• Logic Tree: performance data related to the processing of logic trees. The logic trees are

executed during charging and activation operations; They include the pricing elements: price

plan of the charges, the refill logic, and the allowance logic.

• Message: performance and health data about the public communications via the Message

TCP technical interface of SAP Convergent Charging. Metrics are organized per service and

then per operation, and include information such as response times, number of responses

and number of errors in different categories.

• Queue: performance and health data of main processing queues and their associated

execution threads. The queues are used for inter-thread, non-blocking, asynchronous

communication. The queues shall be considered regarding throughput, latency and

reliability.

• Scheduler: performance and health data about the internal schedulers enabled in the SAP CC

Core Server system

• Transaction: performance and health data about the technical transactions (commits and

rollbacks) managed by an instance in a running SAP CC Core Server system

• Warm-Up: performance and health data about the data cache warm-up processing. The data

is only for caches using partitioning and direct memory.

Consult the CA Instroscope documentation for more information about the basic elements.





Consult also the CA APM Workstation User Guide in the product documentation of CA Introscope. Refer to the relevant


Consult the SAP and CA communities.

10.4 Problem Determination

10.4.1.1 A Problem Occurs

When a problem occurs, the user gets an error message:



• All the graphical user interfaces (Core Tool, BART Tool), can display a message and an action for the power user

• All the SAP CC systems record logs and traces with fatal error, error, or warning severity levels when they detect

an anomaly

• Error codes and Java exceptions are provided by the systems when an operation request is sent by a connected

external system that uses the technical interfaces of SAP CC ; When interfacing an external system (Java

development or Web Services integration), the development consultants and the implementation project teams

These messages provide answers to many problems and assist you with most of the problem isolation and resolution.

Corrective or preventive actions to be planed are suggested to resolve the problem or to prevent a future issue.

10.4.1.2 Collection of Information

To collect information related to your problem:

Tool or Function Description

Logging Log messages to permanently record the events and status of a

software system

Tracing Trace messages to analyze a software system in detail from a

programmer’s standpoint as exceptional procedure

Audit

Error Files

Error Codes and Exceptions

10.4.1.3 Try To Reproduce

Sometimes you can try to reproduce the unexpected behavior on a quality landscape.

You can increase temporarily the volume of log and trace information recorded by the SAP CC systems.

10.4.1.4 Advanced Collection

You can increase temporarily the volume of information by using the following functions:

Traces (SAP CC system)

• Debug mode (Admin+ Tool)

• Verbose mode (Core Tool)

154 PUBLIC



10.4.1.5 Problem Isolation

Try to identify the component or the function

10.4.1.6 Typical Problems

The table below lists the typical problems that you can encounter with SAP CC:

• Connection issues

• Requested operation cannot be processed by the system

• Master data becomes un-synchronized

• Other business data becomes unsynchronized (currency, …

• Input data is not received

• Output data is not sent

○ Charged items

○ Billable items

○ Acquired chargeable items

• Notifications are not sent

• User rights and authorization

• Unusual service times

10.5 System Troubleshooting

As a system administrator or an application administrator, you must monitor the SAP CC systems. They must manage

the issues and potential issues signaled by a log message with an error or warning severity.

• They can use the Log Message Reference documentation to plan their investigations

• They can increase temporarily the volume of log messages recorded by the SAP system by changing online the

log severity thresholds to INFO for all the instances of the system

10.5.1.1 Procedure

• Launch the SAP CC Admin+ user interface and log on

• Set up the severity thresholds for logs to the INFO level

○ Use the set command and apply immediately and permanently these changes for all the instances of the

system:

set LS_APP_SEVERITY INFO all all

set LS_SYS_SEVERITY INFO all all



Note

You can change temporarily the settings for one single instance of the system: set LS_SYS_SEVERITY INFO memory <instanceID>


Topic Location

Monitoring Operations Guide

This document

Troubleshooting Operations Guide

This document

Log Message Reference http://help.sap.com/cc SAP CC 4.1 System Administration and

Maintenance Information Log Messages

10.6 Troubleshooting and Performance Analysis

Slow communications or unexpected internal activities may be the root causes or participate to an existing issue. In

some cases, most notably performance issues, a problem can have its roots in a number of seemingly unrelated

components. You narrow down the probable root cause by proceeding with your analysis.

This section introduces what steps you can take to identify and resolve specific performance issues and what you can

do to enhance the performance of your monitored SAP CC systems in the following areas:

• Host resources (CPU, memory, disk)

• Size and growth of data structures

• Transactional problems

• SQL statement performance

• Security, authorization, and licensing

• Configuration






156 PUBLIC



10.6.1.2 General Symptoms

By observing the general symptoms shown by the monitored SAP CC system such as poor performance, high memory

usage, garbage collections, you can start to narrow down the possible causes as a first step in analyzing the

performance issue.

Symptom Description

High Memory Consumption You observe that the amount of memory allocated by the SAP CC system instance is higher than expected. The following alerts indicate issues with high memory

usage:

Out of Memory Situations You observe trace files or error messages indicating an Out of Memory (OOM) situation.

Permanently Slow System

Issues with overall system performance can be caused by a number of very

different root causes. Typical reasons for a slow system are:

• resource shortages of CPU

• memory

• disk I/O

• network performance as an SAP CC system is a cluster of instances

distributed on several hosts and connected to other interfaced front-end and

back-end systems and applications

• other running processes

Note that:

• Operating system tools can also provide valuable information on disk I/O load.

Check your OS.

• Standard network analysis tools can also be helpful to determine whether the

network is the main bottleneck.

Another reason for poor performance, which in many cases cannot be detected by

the SAP CC system instance itself, are other processes running on the same host

that are not related to SAP Convergent Charging. You can use the operating

system tools to check for such processes. Note that SAP only supports production

systems running on dedicated hardware.

Sporadic Issues If performance issues only appear infrequently, the problem may be related to other tasks running on the SAP CC system at the same time.

These tasks include not only maintenance related tasks, or remote replication

(network I/O), but also Java tasks.

See also the Isolated Symptoms section.

Refer to the Metric Reference and Performance Troubleshooting documentation about the complete metric hierarchy.

This user assistance details the performance and health metrics and provides troubleshooting information about the

observed mass symptoms.




10.6.1.3 Isolated Symptoms

When the performance issue seems to relate to a single element, you may use the performance traces and targeted

tracing function.

Example

For example, the excessive response times of few charging operations lead to business errors. The usage and

consumption of a digital service by a particular end customer of the service provider cannot be charged. In this

case, the processing of the charging operations may involve a specific contract (or subscription) configured in

customer master data.

The customer data or the defined charging and tariff policy may be the root cause of this abnormal situation:

• A large mapping table

• A charge plan or an allowance plan assigned to the provider contract

In this situation, the fine analysis of performance traces may help you to narrow down the possible causes and to

detect the root cause.

Refer to the Advanced Troubleshooting: Tracing Tools section in this document; see page [160] about:

• Working with Business Process Tracing

• Working with Traces in the Core Server System

• Working with End-To-End Tracing

10.7 User Interfaces

During the production operation phase or the project implementation phase, you troubleshoot problems that may

arise with the user interfaces of SAP Convergent Charging.

10.7.1 Troubleshooting Problems with the User Interfaces

To troubleshoot problems that relate to the SAP CC user interfaces, you can:

• Display the Operating System (OS) console (MS Windows) that may provide logs or traces

• View the operation requests and responses between the SAP CC user interface and the connected SAP CC

system:

○ Use the XML verbose mode in Core Tool

○ Use the debug mode in Admin+ and BART+

• Use the logging and tracing functions

The following table lists the supportability functions:

158 PUBLIC



User Interface OS Console Logging and Tracing Operation Requests

Core Tool • Not visible by default (MS

Windows operating

systems)

• Visible by default (UNIX,

Linux, and other operating

systems)

• Available

• Disabled by default

XML verbose option

BART Tool • Available


N/A

CAT Tool • Available


N/A

Admin+ Visible by default N/A Debug mode

BART+ N/A Debug mode

10.7.1.1 Procedure: Displaying the Operating System Console (MS Windows) with the SAP CC GUIs

You can enable the MS Windows console by changing the launch scripts (*. bat).

• Make a copy of the command file and edit the script.

• Change the Java executable from javaw.exe to java.exe.

Example

To display the operating system (MS Windows) console when starting the Core Tool user interface, replace the line

in the core_tool.bat launch script file:

SET JAVA=%SAPCC_JAVA_HOME%/bin/javaw

With the following line:

SET JAVA=%SAPCC_JAVA_HOME%/bin/java

10.7.1.2 Procedure: Enabling the traces for troubleshooting

To troubleshoot a graphical user interface of SAP CC, you can easily record the logs and traces to destination files and

to the operating system (OS) console.

Note

Consult the SAP CC Application Help for more information about the logging and tracing functions, which provide

you with extended supportability tools.

Recommendation

In a productive system landscape, contact your SAP Support Team. A support specialist adapts the temporary

configuration settings to your requirements.



• Edit the relevant launch script depending on the operating system and the SAP CC graphical user interface.

• Depending on your operating system, change the instruction that sets up the variable LOGS_ENABLED:

Environment Script File and Technology New Script Instruction

MS Windows • core_tool.bat

• bart_tool.bat

• cat_tool.bat

SET LOGS_ENABLED=true

UNIX and other Operating Systems

• core_tool.sh

• bart_tool.sh

• cat_tool.sh

LOGS_ENABLED=true

• Check the variable LOG_FILE_PATH. You must have the write permission on the working directory.

• Save the file.

• Start your SAP CC user interface again.

• Try to reproduce the problem.

• Once the problem is resolved, disable the traces by changing the variable back to false.

Note

You can set up some other options of the logging and tracing functions. For example, you can change the size of the

generated files.

Refer to the SAP CC System Parameter Reference documentation for detailed information about each option. See

the System: Log and Trace Settings section about:

• Log messages: LS_APP_SEVERITY and LS_SYS_SEVERITY

• Trace messages: LS_TRC_SEVERITY

10.7.1.3 Procedure: Disabling the traces for troubleshooting

• Edit the relevant launch script depending on the operating system and the graphical user interface of SAP CC.

• Change the instruction that sets up the variable LOGS_ENABLED to false.

• Save the script file.

• Start your SAP CC user interface again.

Recommendation

In MS Windows, you can disable the OS console that is displayed when launching the SAP CC graphical user

interface.

10.7.2 Troubleshooting of Core Tool

To troubleshoot problems with the Core Tool user interface, you can:

http://help.sap.com/saphelpiis_cc41/helpdata/en/e4/core_paramref/summaryof-LOGTRACE.html

160 PUBLIC



• Display and view the operating system (OS) console

• Enable the logging and tracing functions

• Enable the recording of XML messages and included operation requests exchanged between a user interface and

its connected SAP CC system

10.7.2.1 Communications with the SAP CC System

To troubleshoot the Core Tool user interface, you can easily record the messages exchanged by the user interface and

the connected Core Server system. These records allow you to see and understand the requested business

operations, their responses, and the respective contents.

Refer to the primary help and the Preferences menu for more information about the XML verbose mode.

Note

Refer to the API Reference documentation for more specification information about the HTTP Communication

Interface (HCI) technical interface of SAP CC, the formats of the XML/HTTP messages, and the detailed contents

of the operation requests.

10.7.3 Troubleshooting of Admin+ and BART+

To troubleshoot the Admin+ and BART+ user interfaces, you can easily enable the debug mode in the console user

interfaces.

Refer to the primary help and the debug command for more information.

10.8 Advanced Troubleshooting: Tracing Tools

Using tracing assumes that a problem is already noticed by a log message, by a complaining user or by non-functioning

services or functions of the monitored SAP CC systems or by connected applications and systems. Tracing is an

exceptional procedure performed or supervised by a support specialist from your SAP Support Team.

A support specialist can use the information provided by the trace messages. These voluminous messages include

information about the location of the failure inside the SAP CC systems:

• At runtime, you change manually the trace severity threshold to PATH and the log severity thresholds to INFO.

See the instructions in Working with Traces in the Core Server System, page [161].

• You setup a tracing session to arm the targeted tracing function. It triggers automated trace generation for the

next charging operation. See the instructions in Working with Business Process Tracing, page [163].

• Additionally, SAP CC supports the SAP Passport technology to receive and manage passports via the Web

Services technical interface. See the instructions in Working with End-To-End Tracing, page [164].

Caution

Do not perform these procedures in a production system landscape without the direct supervision of a support

specialist from your SAP Support Team.

This section gives you an overview of the available tracing tools.



Consult the SAP CC Application Help documentation for more information about the logging and tracing features,

targeted tracing, or performance traces; see page [13].

See in this section:

• Working with Traces in the Core Server System, page [161]




10.8.1 Working with Traces in the Core Server System

10.8.1.1 Preparations: Determining the Appropriates Settings

You identify and define the system parameter values:

• Determine the severity threshold for trace messages that is relevant for your issue: INFO or PATH. Consult the

SAP CC System Parameter Reference for more information about the thresholds, page [13]. See the user

assistance available about the LS_TRC_SEVERITY system parameter.

• Determine if additional tracing domains are expected to facilitate the investigations and the troubleshooting. By

default, you must deactivate these domains. Your support specialists or experts from the operation team

recommend the appropriate values. Consult the SAP CC System Parameter Reference for more information,

page [13]. See the user assistance available about the LS_TRC_DOMAIN system parameter.

Example

The tracing domains are specialized.

• To check communication via the Web Services technical interface, you use the WS additional tracing domain.

• To check data cache function or data lock function, you use the CACHE or LOCK additional tracing domain.

• To check performance traces, you use the PERF additional tracing domain.

• Determine if you need traces from all the instances of the SAP CC system or just from certain instance types

(rater, dispatcher, …)

• Determine when to perform the procedure: determine the period or the cause event that is relevant.

Recommendation

Enrich your SAP user experience and benefit from the user assistance available page [13]:

• Refer to the SAP CC System Parameter Reference for more information about each option.

• Consult the SAP CC Application Help for more information about the logging and tracing functions, which

provide you with extended supportability tools.

162 PUBLIC



10.8.1.2 Procedure of the Technical Operation

Caution

In a productive system landscape, first contact your SAP Support Team.

Do not perform this procedure, except under the direct supervision of a support specialist from your SAP Support

Team.

• Launch the SAP CC Admin+ user interface and log on

• Retrieve and write down the current configuration information:

○ Use the get command: get LS_APP_SEVERITY get LS_SYS_SEVERITY get LS_TRC_SEVERITY get LS_TRC_DOMAIN

• Set up the severity thresholds for logs to the information level (INFO)


system:

set LS_APP_SEVERITY INFO MEMORY all

set LS_SYS_SEVERITY INFO MEMORY all

• Select the additional tracing domains according to the preparation task; Use the set command and apply

immediately and permanently these changes for all the instances of the system.

○ By default, you must deactivate the additional tracing domains:

set LS_TRC_DOMAIN UNSET MEMORY all

○ Apply the recommendation provided by SAP Support Team: set LS_TRC_DOMAIN SQL MEMORY all

• Set up the severity threshold for traces to PATH level (or INFO level):


system:

set LS_TRC_DOMAIN PATH MEMORY all

• Restore the previous settings or reset to the recommended settings. Use the get command the set commands

and apply immediately and permanently these changes for all the instances of the system:

○ Use the get command to retrieve the initial values of the configuration parameters of the SAP CC system at

the startup time: get LS_APP_SEVERITY PERSISTENT all get LS_SYS_SEVERITY PERSISTENT all get LS_TRC_SEVERITY PERSISTENT all get LS_TRC_DOMAIN PERSISTENT all

○ Use the set command to restore the previous settings.

Note

You can change temporarily the settings for one single instance of the system: set LS_TRC_SEVERITY PATH memory <instanceID>



10.8.2 Working with Business Process Tracing

As of SP 1, the support specialists from your SAP Support Team can use the targeted tracing function when isolated

irregularities or performance issues occur during a particular charging operation.

With Admin+, they recommend that you setup a tracing session for an identified subscriber account and for a defined

period. The SAP CC system triggers the predefined targeted tracing automatically when it detects a new charging

operation request that relates to the selected subscriber account. The relevant rater instance increases the trace

severity threshold locally and generates the trace messages belonging to the PERF and DATA tracing domains.

See the SAP CC Application Help documentation for more information about the targeted tracing function and

business process tracing.

Note

Refer to the SAP CC Application Help about the:

• supported operations

• supported technical interfaces

• targeted tracing function

10.8.2.1 Preparation

You determine the subscriber account to work with. It may relate to failed charging operations. You can use the thread

dump to facilitate this determination.

10.8.2.2 Procedure of the Technical Operation

Caution



Team.

• Launch the Admin+ user interface and log on.

• Use the start_trace_session command to arm the targeted tracing; see the primary help for more

information.

• Wait for the next charging operation request that relates to the specified subscriber account in the master data of

the service provider.

• Transmit the trace files to your support specialists or operation team experts.

10.8.2.3 Next

To troubleshoot the problem, the analysis of the traces facilitates the identification of the:

• Execution errors

164 PUBLIC



• Execution path

• Execution subpaths concerning the different steps of the process execution

10.8.3 Working with End-To-End Tracing

As of SP 1, the SAP CC system supports the SAP Passport received from interfaced systems (or applications) via the

Web Services technical interface. The SAP CC system interprets the received passports and triggers the customized

targeted tracing automatically. All the relevant instances increase the trace severity threshold locally and generate the

trace messages depending on the custom passport.

Note

You can combine end-to-end tracing with business process tracing (or system process tracing) to generate

supplementary traces temporarily. These traces can relate to back-end systems (or frontends). Simply configure

the passport.

See the SAP CC Application Help documentation for more information about the targeted tracing function and end-to-

end process tracing.

10.8.3.1 Technical Operation: Customizing the Targeted Tracing (trace severity threshold, generated traces)

In your interfaced system or test system, you set up the trace flags in the SAP Passport sent to SAP Convergent

Charging:

• Determine the tracing domains you need in the generated traces:

SAP CC Tracing Domain Corresponding Trace Flag in SAP Passport

All the domains different from tracing domains already associated to a trace flag: SQL, JCO, DATA, PERF, HCI,

and WS

C function Trace

DATA ABAP Trace (bit 7)

JCO RFC Trace (bit 3)

PERF (performance traces) SAT (bit 10)

SQL SQL Trace (bit 0)

WS and HCI WebService (bit 11)

• Set up the appropriate bits in the trace flag property included in the SAP Passport sent to the SAP CC Core Server

system.

• Determine the temporary severity thresholds you need for your targeted tracing:

Increased Severity Threshold in SAP CC Corresponding Trace Flag in SAP Passport

WARNING No trace flag is used; it is the default behavior of the

targeted tracing function in SAP CC.

PATH ABAP Condens. 1 (bit 8)

INFO ABAP Condens. 2 (bit 9)

DEBUG (highest severity threshold level) Both ABAP Condens. 1 and ABAP Condens. 2



• Set up the appropriate bits in the trace flag property in the SAP Passport transmitted to the SAP CC system.

10.8.3.2 Result

If you successfully set the trace flags in the SAP Passport, the SAP CC system records all subsequent activities for an

operation request and the trace messages corresponding to the following domains are available.

• No domain (always)

• SQL domain

• JCO domain

• HCI and WS domains

• PERF domain

• DATA domain

When the service operation request is replied, you can work with the recorded trace messages.

To continue the troubleshooting operation, locate the traces and transmit them to the support specialists from your

SAP Support Team for further investigation and analysis.

10.8.4 Working with Performance Traces

Performance traces are additional trace messages recorded in the standard trace files of the SAP CC systems. They

belong to the PERF specialized tracing domain. All the typical configuration options apply to these traces: format, file

rotation, file size. To facilitate the research, each trace message contains the Transaction ID set in the custom or

predefined SAP Passport.

The support specialists from your SAP Support Team help you generating these traces and continue the investigations

(issue location, root cause analysis).

See the SAP CC Application Help documentation for more information about performance traces.

Note

Depending on your implementation, the performance traces may also relate to few charging operations that are out

of scope of your business case. For technical reasons, they relate to other charging operations. Do not consider

these trace entries during your investigations.

Related user assistance:


10.8.5 Traces in BART Server System

Use the BART+ user interface and perform the procedure.

166 PUBLIC



Caution



Team.

10.8.6 Diameter Server System

Use the procedure and change the configuration of the Diameter Server system.

Caution



Team.

10.8.7 Communications Taxing (CT) Server System

Use the procedure and change the configuration of the Communications Taxing (CT) Server system.

Caution



Team.

10.8.8 Traces in Graphical User Interfaces

For troubleshooting purposes, you can temporarily enable the logging and tracing functions in the graphical user

interfaces of SAP CC:

• Core Tool

• BART Tool

• CAT Tool

The procedure plans that you modify the launch script corresponding to your OS environment and to your SAP CC

GUI.


You determined:

• the relevant launch script file



• the temporary configuration settings

10.8.8.2 Procedure: Preparing

To troubleshoot problems with the SAP CC user interfaces, SAP recommends that you:

• Define the DEBUG severity threshold for the generation of traces.

• Concentrate the recording of all the logs and traces to the same fileset destination, which is a rotating fileset.

• Set up the file generation with the TRACE file format.

Notes

• SAP Support Team can adapt the recommendations.

• Refer to the SAP CC System Parameter Reference documentation for detailed information about each option.

See the Logs and Traces Settings section.

The table defines the necessary Java options to set up in the launch scripts:

Options Recommended Value Comment

ls.app.severity

The severity threshold for the

generation of log messages

related to the business

processing (application level)

INFO

ls.sys.severity


generation of log messages

related to the system

processing (system level)

INFO

ls.trc.severity


generation of trace messages

DEBUG

Note

Ask your SAP Support Team if another severity

threshold is necessary.

ls.app.destination LDF1

ls.sys.destination LDF1

ls.trc.destination LDF1

168 PUBLIC



Options Recommended Value Comment

ls.trc.domain Set up this option without specifying any particular trace

domain to include in the traces. The user interface

records the standard traces.

Note

Ask your SAP Support Team.

ld.file1.enabled true

ld.file1.name

The file path, name, and

extension of the files in

destination fileset

myfilename.trc Depends on your installation

Example

/tmp/mycoretool.trc

Or

\temp\mycoretool.trc

Notes

• This file mostly includes traces. The file

extension is *.trc.

• Ask your SAP Support Team.

ld.file1.formatter

The format of logs and traces

generated in the destination

TRACE

Note

Ask your SAP Support Team about the expected file

format for further analyses and investigations.

ld.file1.setsize

The number of files for the

rotations in the destination

fileset

2

Note

Ask your SAP Support Team about the number of

reused files.

ld.file1.size 3000000

Note

Ask your SAP Support Team about the file size

recommended in your SAP system landscape.

10.8.9 Traces in IEC Applications

For troubleshooting purposes, you can temporarily enable the logging and tracing functions in the Import/Export

Connector (IEC) applications of SAP CC.



10.8.9.1 Procedure: Enabling the traces for troubleshooting

• Copy the relevant launch script of your IEC application: iec.bat, iec.sh, iec_remote.bat, or iec_remote.sh.

• Change the value of the trace severity threshold:

○ Locate the line in the script file that defines the LS_TRC_SEVERITY script variable; the final command reuses this variable as argument and Java option when launching the IEC program.

○ Set up the value to DEBUG.

Topic Script File

extension

Default Line in Script File Recommended Value for

Troubleshooting

MS Windows *.bat SET LS_TRC_SEVERITY=INFO SET LS_TRC_SEVERITY=DEBUG

UNIX *.sh LS_TRC_SEVERITY=INFO LS_TRC_SEVERITY=DEBUG

• Save the file.

• Restart your IEC application with this new launch script.

• Try to reproduce the problem.

Notes

• The default value is INFO.

• Consult the primary help for more information about the launch scripts to run an IEC depending on your

operating system and system landscape.

• Consult the SAP CC Application Help for more information about the severity levels.

• You may need to add some entries to define the destination of the logs and traces (ls.app.destination,

ls.sys.destination, and ls.trc.destination=LDC,LDF2).

10.8.9.2 Other Options

Other options are available to manage the traces and logs generated by an IEC application. Refer to the SAP CC

Configuration Guide for more information about all the possible values; see in the section that relates to the technical

settings of the BART Server system: Configuration of BART Server → System Settings for Logging and Tracing →

Setting up the Logging and Tracing Function.

Example

The launch scripts include a line that triggers the execution of the program. This line includes Java options (-Dxxx)

where xxx is the technical name of the Java option.

For example, the option -Dld.console.enabled=true activates recording of logs and traces in the OS console

depending on the selected destinations for logs or traces.

exec $JAVA -Dsun.nio.ch.useIPv6Stack -Duser.language=en -Dld.console.enabled=true -

Dls.trc.severity=$LS_TRC_SEVERITY -Dls.trc.domain= -Dfile.encoding=UTF-8 -classpath

$CLASSPATH com.highdeal.iec.launcher.HttpLauncher -repositoryDir=../iec-repository $1

$2 $3 $4 $5 $6 $7 $8 $9

You can manage the destinations of the logs and traces by specifying the following Java options:

170 PUBLIC



• ls.app.destination=LDC,LDF1

• ls.sys.destination=LDC,LDF1

• ls.trc.destination=LDC,LDF2

10.9 Advanced Troubleshooting: Thread Dump Files

10.9.1 Working with Thread Dump Files

As of SP 1, the support specialists from you SAP Support Team can setup supportability tools based on thread dump

files when a problem occurs during the execution of an operation or when the execution exceeds some defined

thresholds:

Trigger in SAP CC Exceeded Thresholds Other Triggers

Time Reached scheduling period

CPU CPU time

Rating Contexts Number of rating contexts that are used

by a processing thread

Back-End File System Number of written output items

Back-End Database Execution time of SQL queries

Errors

• Timeout of a given charging

operation request

• Unsupported exception which

occurred

This function improves the troubleshooting capabilities of your running SAP CC Core Server systems. It gives you

valuable insight about the execution context of the threads when a problem occurs, and doing so helps you to quickly

determine the root cause and fix the problem.

For more information about this function and available options, refer to the description of the Troubleshooting

(Advanced): Thread Dump Generation group available in the SAP CC System Parameter Reference documentation; see

page [13].

User assistance:

• Monitoring: you can monitor this feature by using the reported performance and health metrics in SAP Solution

Manager and CA Introscope for SAP.

• Monitoring: you can monitor some processing queues and assigned execution threads



10.10 Errors and Exceptions

10.10.1.1 Core Server

There are three types of errors or exceptions that can be generated when the client application or when the connected

SAP CC Core Server system encounters a problem. They can be signaled in three possible ways.

Problem Returned as an Exception to

the Client Application

Saved in Server System Logs

Client application side failure Never Never

The client application has to manage the

generation of logs.

Business errors Always returned

Nested exceptions and error

messages give more information

about the precise nature of the

error/problem

Depends on API error type and on log

settings.

The INFO log level shows all errors.

Core Server side failure Always returned Depends on API error type and on log settings.

The INFO log level shows all errors.

Exceptions are generated when an error occurs. An exception contains a description of the overall possible reason for

the error. The exception can contain nested exceptions giving further details about the possible causes of the error.

Exceptions are described in the SAP CC Java API Reference documentation (the ‘JavaDoc’).

Note

The Core Tool user interface and the BART Server system are client applications regarding to the Core Server

system. They catch the errors and exceptions signaled by the Core Server system.

10.10.1.2 Core Tool

The Core Tool user interface catches the exceptions signaled by the connected Core Server system and warns the

power user.

10.11 Error Reason Codes

10.11.1 Core Server Error Reason Codes (for Non-Business Errors)

The SAP CC Core Server system signals the non-business errors with one single Java class of error message:

com.hgideal.hci.serverFailureException.

172 PUBLIC



General Failures Back-End Database Technical Functions

All reasons relative to general server

system failure and data cache

management

Example

• SERVER_SHUTTING_DOWN

• INCOMPATIBLE_CONFIGURATION

All reasons relative to back-end

databases

Example

• DATABASE_FAILURE

• DATABASE_FAILOVER

All reasons relative to the Audit

functions

Internal Communications Communications with Interfaced

Systems

Business Functions

All reasons relative to inter-

instance communications

between instances in an SAP

CC system

Example

• INTER_INSTANCE_CO

MMUNICATION_FAILU

RE

• SERVER_TO_CLIENT_

COMMUNICATION_FAI

LURE

All reasons relative to the:

• Message TCP technical

interface

• HTTP Communication

Infrastructure (HCI) technical

interface

All reasons relative to the:

• Access control functions and

customer master data identification

• Guiding functions

• Bulk loading functions

10.11.1.1 Error Codes

The table below lists the available reason codes and their possible cause. Refer to the SAP CC Java API Reference

documentation for more detailed information and specification:

Reason Code Description

ACCESS_COMPATIBILITY_FAILURE Reason code for old use of accesses (in subscriptions).

AUDIT_FAILURE Reason code when the operation cannot be audited.

CACHE_INVALIDATION_FAILURE Reason code when the updater instance did not succeed to update in a synchronous way, the data

caches belonging to rater instances of the SAP CC

system.




CANNOT_LOCK_RESOURCE Reason code when the Core Server cannot lock

resources into the database after having tried

SQLHELPER_MAX_REDO attempts.

CURRENCY_IS_NOT_DEFINED Reason code when a currency is unknown because the

currency is not defined.

DATABASE_FAILOVER Reason code when the Core Server system is failing

over due to a database failure.

DATABASE_FAILURE Reason code when a failure occurred with the database.

HCI_CONCURRENCY_OPERATION Reason code relative to a service invocation on HCI APIs, which is in concurrency with another.

HCI_SERVICE_VIOLATION_PROTOCOL Reason code when XML stream received by the HCI

servers (updater and dispatcher) is not conformed to

the HCI protocol.

HCI_UNSUPPORTED_SERVICE Reason code relative to a service invocation on HCI

APIs, which is not supported.

INCOMPATIBLE_CONFIGURATION Reason code when the Core Server cannot load its configuration due to out of rank parameter values or

missing parameter values.

INTER_INSTANCE_COMMUNICATION_FAILURE Reason code for networking/communication issues between rater or updater instances of the Core Server.

IO_FAILURE Reason code when the Core Server encountered some

IO failure.

MESSAGE_QUEUE_FULL Reason code relative to fulfilling of queues implemented by message protocol.

MESSAGE_UNSUPPORTED_SERVICE Reason code relative to a service invocation on

message, APIs which is not supported.

OFFER_CACHE_BUSY_WHILE_REFRESHING Reason code when the subscription cannot be charged

because its related offer is temporary inaccessible due

to cache refreshing process.

SERVER_SHUTTING_DOWN Reason code when the Core Server is shutting down.

SERVER_TIMEOUT_OCCURED Reason code when the Core Server cannot execute the

API with the required timeout.

SERVER_TO_CLIENT_COMMUNICATION_FAILURE The server encountered communication or network issues while trying to reply to the client.

174 PUBLIC




SLEEPING_BULK_LOADER Reason code when the backup rejects a rating request

due to the restarting of the original rater regarding the

partition ID.

STATEFUL_SERVICE_VIOLATION_PROTOCOL The message sent to the stateful API is not conformed

to the stateful protocol.

STATELESS_SERVICE_VIOLATION_PROTOCOL The message sent to the stateless API is not conformed

to the stateless protocol.

SWITCH_BACK_TO_RATER Reason code when the backup rejects a rating request due to the restarting of the original rater instance

regarding the partition ID.

TAX_CACHE_BUSY_WHILE_REFRESHING Reason code when the subscription cannot be charged

because taxes are temporary inaccessible due to cache

refreshing process.

UNSUPPORTED_FAILURE Reason code when the server system failure is

unknown or not supported by SAP CC.

Note

Contact your SAP Support Team

UNSUPPORTED_JAVA_FAILURE Reason code when the server system failure is a Java

error and is not supported.

Note

Contact your SAP Support Team

When a non-business error occurs in the server system, consult the serverFailureException in the SAP CC Java

API Reference for an up-to-date list and an indication of the possible causes.


You can find this reference documentation in the SDK of SAP CC or in SAP Help Portal at the following location:

http://help.sap.com/cc SAP CC 4.1 Development Information Java API References Core Library

com.highdeal.hci Exceptions serverFailureException

Note

Download is also possible in SAP Help Portal for offline consultation.





10.11.2 Exception Management

10.11.2.1 Message TCP

When the communication between your client application and the SAP CC system fails, your application handles the

following exception:

com.highdeal.cnd.message.CommunicationFailureException

The available reasons are:

• The communication between your client application and the Core Server system is closed or is closing.

• The connection queue is full.

• The communication has been interrupted due to timeout specified by the client application.

• The timeout set by the client has expired.

• The sent or received message cannot be managed by the communication protocol because it is too long.

Refer to the SAP CC Java API Reference documentation for more information about the possible causes and

suggested actions.

Example

SAP Convergent Mediation and SAP CC BART Server handle this exception.

10.11.2.2 Web Services

Refer to the SAP CC SOAP API Specifications documentation for more information about the Web Services technical

interface and the error and exception handling for each service operation.

Refer to the SAP CC Error Core Reference documentation for more information about the possible errors and actions

to solve your issues.

10.11.2.3 HCI

When a business error occurs in the connected SAP CC Core Server system, your client application handles the

following exceptions:

• OperationFailureException

• OperationFailureErrorException

An exception is available for each operation request. Refer to the SAP CC Java API Reference documentation for an

up-to-date list and an indication of the possible causes.

When a non-business error occurs in the connected Core Server system, consult the ServerFailureException and

ServerErrorException exceptions in the SAP CC Java API Reference documentation for an up-to-date list and an

indication of the possible causes.

It means that the operation request did not succeed, and no change is performed into the back-end database system.

176 PUBLIC



The SAP CC system records these exceptions and associated details to the logs and traces.

10.12 Detailed SAP CC 4.1 Troubleshooting

10.12.1.1 Failover Recovery (Oracle RAC)

As system administrator, you may have to switch the connections established by SAP CC with the database backup

instance (due to failover) to the primary instance of the database.

To recover the connections with the primary instances of Oracle RAC:

• Repair the primary instance(s) of the Oracle RAC database


• Use the admin_sql_connections command to reconnect all the rater instances and the guider instances of the

SAP CC Core Server system to the repaired instance of Oracle RAC

• Determine the impacted instances of the SAP CC Core Server system: View the values of the

SQLHELPER_JDBC_URI parameters

• When relevant, use the refresh_sql_connections command to reconnect the other types of instances of the

SAP CC Core Server system

10.12.1.2 Resetting Working Session for a User

As system administrator, you may have to reset the user working session locks in the SAP CC Core Server system

when this function is enabled and when a user has crashed his working session.

To reset the working session for a user:


• Use the delete_user_session command

10.12.1.3 Client Application of the Core Server System

Your Java-based client applications use the Java APIs of SAP CC. Those APIs include functions that can generate

errors and exceptions.

Possible errors:

• Cannot communicate with Core Server system

• Cannot communicate with the back-end database system

• Element (or object) already used

• Timeout error

• No response from server system

• Core Server system identifies not enough time to get a response from database before timeout



• Bad configuration

• Ignorable tag exception

• Core Server system not reachable is displayed

Possible reasons:

• Bug

• Connection closed

• Message too long

• Client timeout

• Server not reachable

• Integration errors

• Client side errors (incorrect use of APIs)

• Incorrect use of Core Tool

10.12.1.4 Charged Item Files Partially or Not Loaded in SAP ERP/FI-CA

Description

Symptom There are some data files with the file extensions *.err.zip or *.err.csv remaining in the

folders of the bulkloader instances of the SAP CC Core Server system.

Possible reason They include charged items that have not been converted in billable items and then loaded in the

SAP ERP/FI-CA System for the billing and invoicing functions.

Possible resolution

The error messages are loaded into corresponding control files. Open these control files and try to solve the problems (connection lost with the SAP ERP system, invalid billable items).

When the problems are solved, it is necessary to change manually the file extension to

‘*.arc.zip’ or ‘*.arc.csv’. The Core Server will automatically try to load again the files into

SAP ERP.

10.12.1.5 Unusual service times for charging services

Your Java-based client application interacts with the batch or stateful service clients of SAP CC to perform charging

operations. Those charging clients perform operations whose latencies can increase unusually.

When such a situation occurs, you can displays service time statistics for one or all connected SAP CC charging

client(s), using the following commands of the Admin+ user interface:

• list_clients, which displays the list of connected SAP CC charging client(s)

• fetch_client_statistics, which display the service time statistics for one or several connected SAP CC

charging client(s)

For further information about this command, refer to the SAP CC User Interfaces documentation.

178 PUBLIC


Support Desk Management

11 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support organization that

seamlessly integrates your end users, internal support employees, partners, and SAP Active Global Support specialists

with an efficient problem resolution procedure.

For support desk management, you need the methodology, management procedures, and tools infrastructure to run

your internal support organization efficiently.

11.1 Remote Support Setup

All issues are reported through SAP Solution Manager.

Issues are analyzed by your SAP Support Team. Level 1 and Level 2 support are handled by SAP.

Connect to SAP at the following location: https://support.sap.com/access-support Available Connection Types

11.2 Problem Message Handover

In case of any problems with the SAP Convergent Charging not covered by the FAQ, open a customer message on

component IS-CC in SAP Support Portal at the following location: https://support.sap.com/incident Report a

Product Error - Incidents

When you report an incident, report also following information that is necessary to reproduce the error.

• The Support Package and Patch Level of the SAP CC 4.1 application where the problem happens

Consult the documentation about using service desk at the following location: http://help.sap.com SAP Solution

Manager SAP Solution Manager 7.0 (English) Incident Management Service Desk

https://support.sap.com/access-support

https://support.sap.com/access-support

https://support.sap.com/incident

https://support.sap.com/incident



http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/ff/6ea7a870ac469ea54cedd12666cc5d/frameset.htm

http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/ff/6ea7a870ac469ea54cedd12666cc5d/frameset.htm


Important Disclaimers and Legal Information PUBLIC 179

Important Disclaimers and Legal Information

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.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means

that experimental features may be changed by SAP at any time for any reason without notice. Experimental features

are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental

features in a live operating environment or with data that has not been sufficiently backed up.

The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the

future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual

property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code

Any software coding and/or code snippets are examples. They are not for productive use. The example code is only

intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and

completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code

unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language

We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may

use masculine word forms to refer to all genders.

www.sap.com/contactsap

© 2016 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 and its distributors

contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company

for informational purposes only, without representation or warranty of

any kind, and SAP or its affiliated companies shall not be liable for

errors or omissions with respect to the materials. The only warranties

for SAP or SAP affiliate company 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.

SAP 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. All

other product and service names mentioned are the trademarks of

their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

http://www.sap.com/contactsap

https://www.sap.com/about/legal/trademark.html

SAP Convergent Charging 4.1 Operations Guide

Documents