cc40_UpgradeG_CSTMR_v1-0

Upgrade Guide

SAP Convergent Charging (SAP CC 4.0) Target Audience

System Administrators Application Administrators Technology Consultants

CUSTOMER Document version: 1.0 – August 2013

August 2013

August 2013

CAUTION

Before you start the upgrade, make sure you have the latest version of this document.

You can find the latest version on SAP Service Marketplace in SAP Support Portal at the following location: Upgrade or

SAP Business Suite Applications SAP Convergent

Charging SAP CC 4.0 Upgrade .

You can subscribe to this folder.

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

Version Date Description

1.0 August 2013 Initial version

https://service.sap.com/instguidescc40

https://service.sap.com/instguides

August 2013

DOCUMENT HISTORY ...................................................................................................................3

TABLE OF CONTENTS ....................................................................................................................4

1 INTRODUCTION..................................................................................................................7

About this Document ................................................................................................................7 Purpose ............................................................................................................................................. 7 Integration......................................................................................................................................... 7 Constraints ........................................................................................................................................ 7

New Features ............................................................................................................................7 For the Upgrade Process .................................................................................................................... 7 Candidate Feature for the Upgrade .................................................................................................... 8

SAP Notes for the Upgrade........................................................................................................8 Definition ........................................................................................................................................... 8 SAP Notes for Preparing the Upgrade ................................................................................................. 8

Document Abbreviations ..........................................................................................................9

2 QUICK GUIDE ..................................................................................................................10

Checklist ................................................................................................................................. 10 SAP Notes for the Upgrade ............................................................................................................... 10 Additional Documentation ............................................................................................................... 11

Upgrade Planning.................................................................................................................... 11

Upgrade Preparations ............................................................................................................. 11

Follow-up Activities ................................................................................................................. 11

3 PLANNING ......................................................................................................................12

Upgrade Plan .......................................................................................................................... 12

Upgrade in an SAP System Group ............................................................................................ 12 Global Process Sequence .................................................................................................................. 12

Software Units ........................................................................................................................ 13

Planning the Upgrade Schedule ............................................................................................... 15 Procedure ........................................................................................................................................ 15

Steps of the Upgrade Phase .................................................................................................... 15

Detailed Upgrade Sequence .................................................................................................... 16 Online Scenario ................................................................................................................................ 17 Offline Scenario ............................................................................................................................... 17

Upgrade in an Integrated Scenario with SAP ERP ..................................................................... 18 Communications Taxing Server......................................................................................................... 19 Migrating Chargeable Item Packages ............................................................................................... 19 Migration from BART to SAP CI with the Storage of Consumption Data in SAP CI ............................... 19 Migration from SAP CC 3.0 to SAP CC 4.0 with the Storage of Consumption Data in SAP CI ................ 19

Upgrade Path .......................................................................................................................... 19

Upgrade Stages ....................................................................................................................... 20 Server System .................................................................................................................................. 20

Tool Information ..................................................................................................................... 21 Upgrade GUI .................................................................................................................................... 21

August 2013

Communication with Systems........................................................................................................... 22 SAP Global Host ............................................................................................................................... 22 SAP Central Repository ..................................................................................................................... 23 SAP Profile ....................................................................................................................................... 23 Other Tools ...................................................................................................................................... 24

Technical Details of the Upgrade Process ................................................................................ 24 New Management of the Launch Scripts (Core Server) ...................................................................... 24 Locations of the SQL Upgrade Scripts ............................................................................................... 25 Content of the SQL Upgrade Scripts .................................................................................................. 25

Database Specific Aspects ....................................................................................................... 27

Upgrade of Distributed and High-Availability Systems ............................................................. 28 Core Server ...................................................................................................................................... 28 Diameter Server ............................................................................................................................... 28

4 PREPARATION .................................................................................................................29

Identifying the Host(s) for the Preparations ............................................................................ 29

Checking the Version of the System to Upgrade ...................................................................... 29 Check the Version of the SAP CC Software ........................................................................................ 29 Check the version of the SAP CC database ........................................................................................ 30

Identifying the Updater Instances for the Core Server ............................................................. 30

Checking the System Configuration ......................................................................................... 31

Checking Free Space for Updated Files .................................................................................... 31

Checking Free Space for Temporary Files (UNIX LIKE OSS ONLY) .............................................. 32

Configure the OS of the Host for UTF-8 Encoding .................................................................... 32

Making a Backup Copy of the Launch Scripts for the Servers ................................................... 32

Preparing the Back-End Database Systems .............................................................................. 32 Backup the Database Schema .......................................................................................................... 32 Create new Tablespaces or Filegroups .............................................................................................. 33

Preparing the Upgrade of Client Applications .......................................................................... 33

Preparing the Installation Folders ............................................................................................ 33 Get the Installation DVD................................................................................................................... 33 Make the Installation DVD Available ................................................................................................ 34 Customize the Installation DVD ........................................................................................................ 34 Prepare the Installation Folders ........................................................................................................ 34

Checking the State of the SAP Start Services............................................................................ 35

Preparing the Upgrade of the Database Connections (Core Server) ......................................... 35 Changed Database Connection Management ................................................................................... 35 Check the Expected Connections in your Database System ................................................................ 37 Check the Connections in your Database System............................................................................... 38 Determine the New Database Communication Settings .................................................................... 38

Preparing the Transition to the New Logging and Tracing Functions ........................................ 39 Checking the Transition to the New Logging and Tracing Functions .................................................. 39 Preparing the System Configuration Settings for Logging and Tracing ............................................... 40 Identify the Necessary Customizing .................................................................................................. 44

5 UPGRADE PROCESS ..........................................................................................................46

Upgrade the SAP CC Server Systems ........................................................................................ 46 Stages.............................................................................................................................................. 47 Initialization: Database Connections Update .................................................................................... 47 Initialization: Shutdown the Server System ....................................................................................... 48

August 2013

Initialization: Backup the Software ................................................................................................... 48 Initialization: Backup the Database .................................................................................................. 49 Configuration and Checks: Starting the Upgrade GUI ........................................................................ 49 Make Entries for SAPInst .................................................................................................................. 49 Checks by SAPInst ............................................................................................................................ 51 Preprocessing by SAPInst.................................................................................................................. 51 Preprocessing: Checks Before Restarting the Upgraded Server System .............................................. 51 Processing: Restart the Upgraded Server System .............................................................................. 52 Post-Processing: Check the Restart of the Server System ................................................................... 52 Finalization: Clean the Platform ....................................................................................................... 52

Using the Accessibility Mode ................................................................................................... 52

Restarting the Upgrade Program ............................................................................................. 53

Resetting the Upgrade of a Server System ............................................................................... 53

Upgrade the Client Applications .............................................................................................. 54

Upgrade the SAP CC GUIs ........................................................................................................ 55 Upgrading the Core Tool and the BART Tool ..................................................................................... 55 Upgrading the IEC Tool .................................................................................................................... 56

6 FOLLOW-UP ACTIVITIES .....................................................................................................57

Monitor the System Landscape ............................................................................................... 57

Configure the New Features of SAP CC 4.0 .............................................................................. 58 Candidate Changes .......................................................................................................................... 58

Technical Configurations ......................................................................................................... 59 Enabling the encryption of the communication channels .................................................................. 59 Enabling the fine-grained auditing of master data modifications ...................................................... 59 Enabling the new Web Services (Charging and Recharging) .............................................................. 59

Customizing ............................................................................................................................ 60 Updating the VAT Rates ................................................................................................................... 60

Integrated Scenario with SAP Convergent Invoicing ................................................................ 60 Enabling the Rerating with SAP ERP/FI-CA (SAP Convergent Invoicing) .............................................. 60

Upgrading the SAP Online Documentation .............................................................................. 61

Implementing Support Packages After the Upgrade ................................................................ 61

Backup .................................................................................................................................... 61

After Resuming Production Operations ................................................................................... 61

7 TROUBLESHOOTING ..........................................................................................................62

Logs of SAPInst ........................................................................................................................ 62

Logs of SAP CC ........................................................................................................................ 62

Restoring the Software ........................................................................................................... 63 SAP CC Server System ....................................................................................................................... 63

8 COPYRIGHTS ...................................................................................................................66

Disclaimer ............................................................................................................................... 67

Documentation in SAP Support Portal ..................................................................................... 67

August 2013

This document explains how to upgrade an SAP Convergent Charging system landscape as productive edition.

Purpose

This document deals with the upgrade of SAP Convergent Charging 3.0 to SAP Convergent Charging 4.0.

For more information, consult the following documentation: SAP CC Library, Release Notes on SAP Service Marketplace at: SAP CC 4.0 .

The information in this document is intended for:

SAP system administrators with operating system, database knowledge SAP application administrators with knowledge of business processing of the systems and the

components of SAP Convergent Charging SAP technology consultants

Integration

If you want to upgrade SAP CC, it is essential that you familiarize yourself with the contents of the Upgrade overview included in the Master Guide before starting to upgrade.

In addition to this document, you also require other information, such as the Release Notes for the applications that you implement, the SAP Notes that are specific to this upgrade, and any other documentation referred to in this document.

Constraints

This migration cannot be done online.

The wall process requires a new installation of the software units.

For the Upgrade Process

SAP Convergent Charging 4.0 is the second version that provides an upgrade process with necessary tools and procedures.

New Feature in the Upgrade Process on 4.0

SAPInst has been modified in order to support the upgrade from SAP CC 3.0 to SAP CC 4.0

https://service.sap.com/instguidescc

August 2013

The new log and trace functions are activated for the upgraded systems

Candidate Feature for the Upgrade

Consult the Release Notes for all the changes in this version of SAP Convergent Charging.

Definition

To prepare and perform the upgrade of your SAP system, you require some additional information that is not included in this document. This information is in a range of SAP Notes in SAP Support Portal ( ), some of which you must read before you prepare the upgrade. Besides the central Upgrade Note and the applications-specific Upgrade Note, you can additionally find separate SAP Notes for the database-specific sections. When you actually upgrade the SAP system, you need information from some additional SAP Notes. These SAP Notes are named at the appropriate places in this document.

SAP Notes for Preparing the Upgrade

You must request the following SAP Notes in SAP Support Portal before you start your upgrade:

Central Upgrade Note

Contains the general upgrade problems and information about the fix archive for the upgrade

Upgrade Note for your application

Contains application-specific information

SAP Note for your database

Since these SAP Notes are updated regularly, make sure that you always use the newest version.

You must read the following SAP Notes before you start the upgrade.

SAP Note Title

Temporary license keys

Requesting license keys and deleting systems

Hostnames of SAP servers

CA Wily Introscope for SAP Convergent Charging

"Java Cryptography Extension (JCE) Jurisdiction Policy" files

SAP Cryptographic Software - Export control

Processor Driver for Windows Server 2003 must be installed

SAP JVM installation prerequisites

SAP system does not start after applying SAP kernel patch

http://service.sap.com/support

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










August 2013

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

Abbreviation Meaning

AAA Authentication, Authorization and Accounting

BART Batch Acquisition and Rating Toolset

CAT Connector Administration Tool

CI Chargeable Item

CT Communications Taxing

GUI Graphical User Interface

HA High Availability

HCI HTTP Communication Interface

HTTP HyperText Transfer Protocol

HTTPS HyperText Transfer Protocol Secure

IEC Import Export Connector

JDBC Java Database Connectivity

JRE Java Runtime Environment

JVM Java Virtual Machine

PSE Personal Security Environment

RAC Real Application Cluster (Oracle)

RDBMS Relational Database Management System

SAPSID See SID

SAR SAP Archive

SID SAP System Identifier

SNC Secure Network Communications

TIF Transaction Integration Framework

URL Uniform Resource Locator

VAT Value Added Tax

XML eXtended Markup Language

August 2013

This section contains a checklist with all the actions you need to perform:

Find SAP Notes Plan the upgrade Prepare the upgrade Upgrade the SAP Convergent Charging system landscape Perform the follow-up activities

The actions are in chronological order so that you can work through them like a checklist. For more information, follow the links to the descriptions of the actions.

You can also use the checklist to get a quick overview of the upgrade phases and the upgrade process.

Planning Upgrade Follow-upPreparation

Upgrade Phases

RECOMMENDATION

If you are experienced in performing upgrades, the checklist may contain all you need to know to perform the upgrade successfully.

SAP Notes for the Upgrade

This upgrade document is enhanced and updated by SAP Notes from SAP Support Portal ( ). These SAP Notes are an important source of information when you plan and prepare your upgrade, and also help you perform the actual upgrade.

You request the current SAP Notes for the Upgrade on page [ ]. You require at least the following SAP Notes:

Central Upgrade Note 1299009 Upgrade Note for your application 1341978

https://service.sap.com/support

August 2013

The relevant database-specific SAP Note 819655

Additional Documentation

Before, during and after the upgrade, you require additional documentation such as SAP Library documentation and troubleshooting documentation.

You make sure that you can access the SAP Library documentation for your source release and target release.

The troubleshooting and administration documentation is included in the upgrade program.

Before you start the upgrade, you must plan it carefully so that downtime is reduced to a minimum, and the upgrade runs as efficiently as possible.

CAUTION

Start planning your upgrade at least two weeks before you want to begin with the upgrade.

You can prepare for the upgrade while the system is in production operation. Run the first four roadmap steps of the upgrade as soon as possible before the actual upgrade so that you can initiate or perform the necessary preparations in time.

You can perform the follow-up activities when the upgrade program has been completed.

August 2013

This part of the document contains information about planning your upgrade.

The following information helps you plan your upgrade so that downtime is reduced to a minimum, and the upgrade runs as efficiently as possible.

Before you begin the actual upgrade, 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 upgrade.

Planning Upgrade Follow-upPreparation

Phases of the Upgrade Plan

If you have more than one SAP system, for example, a production system, a quality assurance system and a development system, you must consider the entire system group.

Upgrade the SAP systems of your group with the global sequence:

Development and test system Quality assurance and validation system Production system

Validate always an upgrade stage before performing the next upgrade.

Global Process Sequence

If your system group consists of three SAP systems and includes a quality assurance system that has been set up between the development and production system, work in the following order:

Step

1 Development system

This landscape should include all the software units of SAP Convergent Charging that are running on the

August 2013

Step

production system.

The external systems that are connected with a server system of SAP CC are not always present in this development landscape.

If an interfaced system or application uses the Java libraries (see Software Development Kit) provided by SAP Convergent Charging, it must be part of the development landscape in order to test the upgrade of these libraries.

Note that for test purposes with realistic production data, set up a quality assurance system or preproduction system between the development system and production system. This system can be a copy of the production system.

2 Quality assurance system

The landscape must include all the systems interfaced with a server system of SAP Convergent Charging: CRM, mediation, billing

3 Production system

For test purposes with realistic production data, set up a quality assurance system between the development system and production system. This system can be a copy of the production system.

A landscape for SAP Convergent Charging includes several server systems installed on different hosts:

SAP CC Core Server SAP CC Communications Taxing Server SAP CC BART Server SAP CC Diameter Server

After the upgrade of the server systems, some other applications must be upgraded:

Some applications may use Java Libraries provided in the Software Development Kits (SDKs) for SAP Convergent Charging

SAP CC Core SDK SAP CC BART SDK

The graphical User Interfaces (GUIs) of SAP Convergent Charging are part of the landscape and are installed on different machines

SAP CC Core Tool SAP CC BART Tool

EXAMPLE

August 2013

Several applications can be integrated with SAP Convergent Charging by using the SAP CC Java Libraries:

An real time mediation system that send charging operations in mass A connector application between an offline mediation system and an SAP CC system A provisioning system that massively create and maintain master data related to end

customers

Consult the SAP CC Library for more details about the Technical Interfaces provided by SAP Convergent Charging.

This guide covers the upgrades of all the elements in the following table:

Software Units Third-party Software

RDBMS

Host Server / Standalone Application

Frontend System

Frontend GUI

Core Server Core SDK Core Tool (Billsoft EZTax)

Only for US tax management

Core Database

Diameter Server - - - -

BART Server BART SDK BART Tool - BART Database

IEC IEC SDK CAT Tool - (Customer Database)

(IEC Database)

Communications Taxing Server - - Billsoft EZTax

Only used by SAP CI in batch mode for US tax management

-

Simulation Tool - Simulation Tool

- -

US taxes for telecommunications are computed with Billsoft EZTax software. You must install EZTax software if you manage US taxes. Some restrictions may apply on the operating systems of your hosts.

NOTE

The SAP CC Core Server Server system consists of several instances: dispatchers, updaters, guiders, raters, taxers, and bulkloaders.

August 2013

Create an exact schedule for the upgrade of your SAP system landscape.

Procedure

Step Description

1 You decide when to begin preparing for the upgrade

When you start the upgrade preparations depends not only on the length of the preparations but also on the length of the upgrade itself. To determine the expected total length of the upgrade of your production system, perform a test upgrade of an SAP system with a similar set of data (a system copy of your production system is ideal).

2 You decide when to start the upgrade

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.

During the upgrade, various actions are performed in the system. The runtime of these actions depends on various factors and is therefore specific to each SAP system.

3 You decide when a full backup is performed after the upgrade

The full database backup is a prerequisite for resuming production operation of your system.

It must be made after you have performed all necessary follow-up activities. This has the advantage that all database changes resulting from follow-up activities are included in the full backup.

4

You decide when production operation resumes

If possible, resume production operation only after you have performed all required follow-up activities.

The upgrade phase of the upgrade plan can be divided in a sequence that includes the following main steps:

A: Upgrade of the server systems of SAP Convergent Charging B: Upgrade of the systems that uses the Java Library of SAP Convergent Charging C: Upgrade of the graphical user interfaces (GUIs) of SAP Convergent Charging

August 2013

Upgrade Steps

The upgrade sequence is split into detailed steps by using the software units present in the landscape:

August 2013

Online Scenario

In a scenario for online charging, the Core Server

Step SAP CC Software Unit Description

A1 Core Server

B1 Mediation System

B2 Provisioning System

C1 Core Tool

Options


C2 Simulation Tool

C3 CAT Tool and IEC

Variant


A2 Diameter Server

B3 Network Monitoring System

Offline Scenario

In a scenario for offline charging, both the Core Server system and the BART Server system are the central systems of your landscape.

August 2013


A1 Core Server

A2 BART Server

B1 Mediation System

B2 Provisioning System

C1 Core Tool

C2 BART Tool

Options


C4 Simulation Tool

Variant


C3 CAT and IEC

If your SAP CC production system is connected to an SAP ERP/FI-CA system, plan the upgrade for SAP CC in the upgrade schedule for the SAP Business Suite or for SAP ERP.

Upgrade first the SAP ERP system.

Landscape SAP Convergent Charging SAP ERP

Source 3.0 SP12 EhP 6

Target 4.0 SP00 EhP 7

August 2013

Communications Taxing Server

SAP Convergent Charging provides a server system to calculate the US telecommunication taxes. SAP CC 4.0 Communications Taxing (CT) Server is used by SAP ERP/FI-CA.

The upgrade of SAP ERP/FI-CA does not require a previous upgrade of the SAP CC 4.0 CT Server already installed on the landscape. There is no constraint to upgrade the SAP CC CT Server system before the SAP ERP system or before the SAP CC Core Server system.

Migrating Chargeable Item Packages

From SAP CC 4.0 onwards, the chargeable item class replaces the Chargeable Item Package in the pricing catalog (master data related to the service provider). Both the Chargeable Item Class and the Chargeable Item Package consist of Chargeable Items. However, SAP CC 4.0 does not support the loading of Chargeable Items related to Chargeable Item Packages into SAP Convergent Invoicing (SAP CI) with Consumption Item Management enabled.

Therefore, it is mandatory to migrate the Chargeable Item Packages if your landscape needs to load Chargeable Items into SAP Convergent Invoicing (SAP CI) from SAP ERP/FI-CA with Consumption Item Management enabled. Refer to the Transition Guide for migrating the Chargeable Item Packages.

Migration from BART to SAP CI with the Storage of Consumption Data in SAP CI

Refer to the Transition Guide for migrating your system landscape from BART to SAP Convergent Invoicing with Consumption Item Management.

Migration from SAP CC 3.0 to SAP CC 4.0 with the Storage of Consumption Data in SAP CI

Refer to the Transition Guide for migrating your system landscape to SAP Convergent Invoicing with Consumption Item Management.

The migration to SAP CC 4.0 SP00 can only be performed in a system landscape using SAP CC 3.0 SP12. This upgrade path may change during the maintenance of both versions of the software.

Consult the SAP Notes of the support packages of SAP CC 3.0 to determine the appropriate upgrade path.

NOTE

Make sure that all the reusable charges of the pricing catalogs that refer to mapping tables have been migrated (since SAP CC 3.0 SP06). Consider the SAP Note 1748752 - Upgrade or update to CC3.0 SP06 from previous installation for more information about the procedures to apply on existing master data related to a service provider.



August 2013

Server System

For an upgrade of an SAP CC server system, the upgrade step is based on the following stages:

Upgrade Stages of a Server Upgrade Step

The table summarizes the stage for the upgrade process of a server system. For more information, see the section on page [ ].

Stage Level Description

Initialization Shutdown

Database Backup

Software Backup

Configuration & Checks SAPInst:

Choose Option

Define Parameters

Summary

SAPInst until Execute

Check the current version of the software and database of the SAP CC system to check that the upgrade is possible

Preprocessing SAPInst:

Execute

Completed

Update the database of the system (if applicable for the system being upgraded) by executing SQL upgrade scripts

Update the content of the archive folder in the central repository of the system

Migrate the boot configuration file of each instance of the system from the instance folders to the central repository

August 2013

Stage Level Description

System Administrator The administrator checks the new launch scripts of the SAP CC server system.

The administrator checks the system settings for the logging and tracing functions.

Processing System Administrator The administrator restarts the shutdown SAP CC server system. The system upgrades automatically its directories.

HA: SAPInst has already restarted the running instances

Post-processing System Administrator The administrator monitors and checks the restarted SAP CC server system.

Finalization System Administrator The administrator archives the logs generated by SAPInst that are no longer required and completes the upgrade.

Upgrade GUI

SAP Convergent Charging 4.0 provides a tool to facilitate the upgrade process. The same program is used for the initial installation, the patch, and the upgrade processes: SAPInst.

SAPInst is the upgrade GUI and provides you with functions for configuring the monitoring the upgrade and navigating through the roadmap steps of the upgrade of the server systems of SAP Convergent Charging.

NOTE

SAPInst does not manage the upgrades of the:

Graphical user interfaces of SAP Convergent Charging Applications using the Java Libraries of SAP Convergent Charging

August 2013

SAPInst Program

Communication with Systems

SAPInst connects to the back-end database systems that host a database for SAP CC:

Upgraded System Back-End Database Description

Core Server Core Database Perform some checks

Change the database schema

Change the system parameters of the SAP CC Core Server that are stored in the database

BART Server BART Database Perform some checks

Change the database schema

SAP Global Host

The SAP Global Host is the first host machine installed with an instance of an SAP system. This host includes the SAP central repository of this SAP system. In an SAP CC system with distributed instances on several hosts, this directory is shared for all hosts.

August 2013

SAP Central Repository

SAPInst manages the SAP Central Repository directory for each server system of SAP Convergent Charging. This directory and its subdirectories are physically shared with all the instances of the same SAP CC server system by using operating system specific sharing techniques (NFC, mounted).

The central repository directory contains subdirectories with unpacked archives of the versions of the software binary files according to the configuration of SAPInst during the upgrade process (see the upgrade stage on page [ ]):

SAP CC software corresponding to the SAP CC system being upgraded SAP Java Virtual Machine (SAP JVM) Wily Introscope SAP Startup Framework

Subdirectory Location

exe

This directory contains executable kernel programs in a subdirectory uc\<OS>\. In an SAP CC system with distributed instances, this directory must be shared for all hosts with the same operating system.

global This directory contains log files. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system.

profile This directory is the central SAP Profile Folder. It contains the start and operations profiles of all instances. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system.

The location of the central repository is:

<DRIVE>:\usr\sap\<SID>\SYS\ (MS Windows operating system) /usr/sap/<SID>/SYS/ or /sapmnt/<SID>/ (UNIX and Linux or other operating systems)

This path includes information about the SAP System Identifier (SID or SAPSID) unique number assigned to an SAP CC server system in each system landscape.

NOTE

SAPInst backups automatically this unpacked binary files to allow you to manually restore an older version of an SAP CC server system. Refer to the section on page [ ].

SAP Profile

SAPInst manages the SAP Profile directory for each server system of SAP Convergent Charging which is shared among all the instances of an SAP CC server system by using operating system specific sharing techniques. This directory belongs to the SAP Central Repository of each SAP system.

August 2013

The three profiles of the SAP system are:

Startup profile Default profile Instance profile

The location of this directory is:

<DRIVE>:\usr\sap\<SID>\SYS\profile\ (MS Windows operating system) /sapmnt/<SID>/profile/ or /usr/sap/<SID>/SYS/profile/ (UNIX and Linux or other operating

systems)

Other Tools

During the you may need to use the configuration tools provided by SAP Convergent Charging 4.0. Refer to their documentation for detailed information about the tasks you must perform:

Tool Location

Admin+

SAP CC 4.0 System Administration and

Maintenance Information User Interfaces Admin+

Setup Tool SAP CC 4.0 System Administration and

Maintenance Information User Interfaces Setup Tool

Config Tool SAP CC 4.0 System Administration and

Maintenance Information User Interfaces Config Tool

Core Tool SAP CC 4.0 Application Help User Interfaces Core Tool

BART+ SAP CC 4.0 System Administration and

Maintenance Information User Interfaces BART+

BART Setup Tool SAP CC 4.0 System Administration and

Maintenance Information User Interfaces BART Setup Tool

BART Tool SAP CC 4.0 Application Help User

Interfaces BART Tool

New Management of the Launch Scripts (Core Server)

Since SAP CC 4.0, the launch configurations of each instance of the SAP CC Core Server system are systematically retrieved from the central repository when an instance starts.

These files are located in subdirectories of the profile directory of an SAP CC system and include:

jstart.config (one for each instance) boot.config

http://help.sap.com/cc







August 2013

Do not modify these files in the local folder of the system instance. Instead, you should modify these files in the shared directory. Modifications to these files will be taken into account when the instances restart.

Locations of the SQL Upgrade Scripts

For SAP CC 4.0 Core Server and SAP CC 4.0 BART Server, the upgrade process includes modifications to the database schema of both systems.

The necessary SQL upgrade scripts are located in an archive on the delivery DVD.

For Core Server, the archive is named CC_CORE_SERVER.SAR, and includes the scripts in a directory named “core_sql”.

For BART Server, the archive is named CC_BART_SERVER.SAR and includes the scripts in a directory named “bart_sql”.

The SQL script executed by SAPInst depends on the type of database and of whether database partitioning is used:

Core Server:

Database type Partitioning enabled Name of the SQL script

Oracle Yes patch442to450_oracle_enterprise_coredb.sql

No patch442to450_oracle_standard_coredb.sql

Microsoft SQL Server Yes patch442to450_sqlserver_enterprise_coredb.sql

No patch442to450_sqlserver_standard_coredb.sql

BART Server:

Database type Partitioning enabled Name of the SQL script

Oracle Yes patch441to450_oracle_enterprise_bartdb.sql

No patch441to450_oracle_standard_bartdb.sql

Microsoft SQL Server Yes patch441to450_sqlserver_enterprise_bartdb.sql

No patch441to450_sqlserver_standard_bartdb.sql

Content of the SQL Upgrade Scripts

According to the upgrade path defined in this chapter, SAPInst will perform the following changes:

Core Database (dedicated to Core Server):

Data Category

Feature Database

August 2013

Changed

Existing Data

Enhanced

Existing Data

New Data

SAP CC System Settings

Configuration records or XML structures

System parameters

Business data (public holidays)

Web services in the dispatcher instance

INSTANCE_MAP (new values)

Integration with SAP ERP

INSTANCE_CONFIGURATION (parameters modified)

VAT rules for tax computation

VAT_RULE

Security

Authorizations

Audit

Keys and certificates for encryption of the communication channels

KEY_STORE INSTANCE_KEY_STORE

CERT_STORE INSTANCE_CERT_STORE

New authorization framework

USER_AUTH USER_ROLE USER_ROLE_AUTH

Fine-grained auditing of master data modifications

OBJECT_CHANGE_LOG OBJECT_SNAPSHOT

Master data

Related to service providers (pricing

catalogs)

Chargeable item classes

CI_DESCRIPTION

Chargeable item mapping

EXPORTABLE_ITEM_MAPPING EIM_FIELD

GENERIC_ITEM_FILES

Immediate refill RATE_COMPONENT_HOLDER ACCOUNT_EVENT_RATE

Mapping table additional information

MATA_ADDITIONAL_INFO MACA_ADDITIONAL_INFO

Range table class RACA OUT_RACA_COLUMN RACA_ADDITIONAL_INFO

Range table RATA RATA_ADDITIONAL_INFO RARO

Master data

Related to end

customers

Subscriber mapping table additional information

SUMT_ADDITIONAL_INFO

Subscriber range table SURT SURT_ADDITIONAL_INFO SURT_RARO

Counter pooling for charging contracts

CACO CACI_POOLED_COUNTER

BART Server Database

Data Category

Feature Database

Changed

Existing Data

Enhanced

Existing Data

New Data

August 2013

SAP CC System Settings

Configuration records or XML structures

System parameters

Business data (public holidays)

Security Keys and certificates for encryption of the communication channels

KEY_STORE INSTANCE_KEY_STORE CERT_STORE INSTANCE_CERT_STORE

Master data

Related to service providers (pricing

catalogs)

Master data

Related to end

customers

Rerating of charging contracts with counter pooling

COLLECTION

Before upgrading, be sure to backup the existing data to be able to rollback your upgrade when required.

You have multiple options:

Cold backup of the whole database Hot backup of the whole database Backup the SAP CC old schema Duplicate the SAP CC old schema and upgrade the duplicated schema

See your database documentation to find the best way of achieving these tasks.

RECOMMENDATION

The preferred option is the duplication. With this option, the SAP CC server system is completely untouched and the old service can restart at any time. But this assumes that the database can handle a duplicated schema in terms of data size.

Refer to the SAP CC 4.0 Operations Guide, section Backup and Restore.

August 2013

The upgrade of high-availability systems differs from the upgrade of normal systems.

CAUTION

Make sure you apply the procedures dedicated to high-availability systems if your SAP CC system landscape manages real-time charging services.

Core Server

The SAP CC Core Server system can be distributed on your landscape to ensure high service levels for real time charging services.

High-availability systems represent a key constraint for the upgrade process. When a primary system instance fails (for several reasons), the other running instances get and share the business traffic until the failed instance is up again.

In addition, the SAP CC Core Database instance is replicated across multiple hosts in a cluster. When a primary node fails, proprietary switchover software automatically switches the failed software unit to another hardware node in the cluster (see Oracle RAC technology).

Diameter Server

The SAP CC Diameter Server system can be distributed on your system landscape to ensure high service levels for real time charging services.

High-availability systems use switchover clusters to guarantee the availability of the system. The SAP CC Diameter Server is across multiple hosts in a cluster. When a primary node fails, proprietary switchover software automatically switches the failed software unit to another hardware node in the cluster.

August 2013

To update the SAP CC server systems, you will have to launch the SAPInst program:

On the global host for the Core Server On the machine hosting the

BART Server system Diameter Server system Communications Taxing (CT) Server system

Procedure:

You must identify all these hosts before starting the upgrade.

NOTE

To find the global host for the SAP CC Core Server system:

Go to the following directory on any machine hosting instances of the Core Server:

<DRIVE>:\usr\sap\<SID>\SYS\profile\ (MS Windows operating system) /sapmnt/<SID>/profile/ or /usr/sap/<SID>/profile/ (UNIX and Linux or other operating

systems)

Open the profile file DEFAULT.PFL Find the value of the variable SAPGLOBALHOST

You need to check if the installed version of the SAP CC system allows the upgrade to SAP CC 4.0. The SAP CC system must at least use SAP CC 3.0 SP06.

Refer to the section on page [ ] in this document for more information.

Check the Version of the SAP CC Software

You need to check if the version of the SAP CC software allows the upgrade to SAP CC 4.0.

Procedure:

Open the log file of any server instance of the SAP CC system to upgrade Locate the line containing the instruction LAUNCHER_STARTED. It contains the version

number of the SAP CC software installed (on 4 digits). Check that the version of the SAP CC software is at least ‘4.4.6.0’ (the third digit may be

greater).

If the version of the software of the SAP CC system does not satisfy this condition, update the SAP CC system to the latest Support Package (SP) of SAP CC 3.0 before attempting to upgrade to SAP CC 4.0.

August 2013

Check the version of the SAP CC database

For an SAP CC Core Server system or an SAP CC BART Server system, you need to check if the version of the SAP CC database allows the upgrade to SAP CC 4.0.

Procedure:

Execute the following query on the database of the system: SELECT VERSION_ID

FROM VERSION

WHERE INSTALL_DATE = (SELECT MAX(INSTALL_DATE) FROM VERSION);

Check that the result of the query is ‘4.4.2’. If the version of the database of the SAP CC system does not satisfy this condition, update the SAP CC system to the latest Support Package of SAP CC 3.0 before attempting to upgrade to SAP CC 4.0.

To upgrade the SAP CC Core Server system, all the updater instances must be stopped.

Procedure:

You must identify these instances.

Write down the instance names for each hostname of the SAP CC landscape.

NOTE

To find the updater instances of the SAP CC Core Server system:

Go to the following directory on any machine hosting instances of the Core Server:

<DRIVE>:\usr\sap\<SID>\SYS\profile\ (MS Windows operating system) /sapmnt/<SID>/profile/ or /usr/sap/<SID>/profile/ (UNIX and Linux or other operating

systems)

Locate the files containing the instance profile: They are named with the format <SID>_<INSTANCE_NAME>_<HOSTNAME>. Where:

<SID>: The SAP system identifier (3 characters) <INSTANCE_NAME>: The name of the SAP CC system instance The files with an instance name starting with the string ‘CCU’ correspond to the updater

instances of the SAP CC system.

Get the host name from the appropriate profile file

EXAMPLE

An SAP CC system landscape includes two updater instances: CCU23 and CCU34.

The first updater instance is installed on a host machine HSTA. Several instances of several SAP systems are installed on this host machine. CCU23 is the 23rd instance of a SAP system.

August 2013

The second updater instance of an SAP CC system is installed on another host machine (HSTB) belonging the same landscape. CCU34 is the 34th instance of a SAP system.

Refer to the SAP CC 4.0 Installation Guide for more information about this nomenclature.

You need to check the value of the configuration parameters of the SAP CC system according to the constraints specified in the System Parameter Reference. If at least one parameter does not satisfy a constraint, the corresponding SAP CC system instances will not be able to start after the upgrade process, until the value of the invalid parameters are corrected.

Procedure:

Go the directory /usr/sap/<SID>/CCD<INSTANCE_NB>/script/ ( or <DRIVE>:\usr\sap\<SID>\CCD<INSTANCE_NB>\script\)

Export the system configuration by executing the user interface of SAP CC with the following command: config configuration export <output_file>

Open the file where the system configuration was exported Check the values of the parameters according to the constraints specified in the SAP CC 4.0

System Parameter Reference. Correct the values of the parameters which do not satisfy these constraints.

Import the corrected system configuration by executing with the following command: config configuration import <input_file>

During the upgrade process, SAPInst copies new versions of the software units (SAP CC, SAP JVM, Wily Introscope) to the central repository. When the instances of the SAP CC system are restarted after the upgrade, these archives are copied to the local directories of each instances of an SAP CC system.

You need to check that there is enough free space available in these directories for these files:

Operating System Free space in the central repository Free space in each instance directory

Windows 64-bit 1,100MB 600MB

AIX 650MB 650MB

HP-UX 1,050MB 1,050MB

Linux 650MB 650MB

Solaris 550MB 550MB

NOTE

The free space required depends on the operating system on which the SAP CC system is installed.

August 2013

For all UNIX like OSs, the /tmp directory is used by SAPInst to create temporary files. Each time you launch SAPInst, you need to check that you have 400MB free space for storing these temporary files.

NOTE

SAPInst creates the following directories:

/tmp/SAPInst_dir /tmp/SAPInst_exe*

You can delete the /tmp/SAPInst_ exe* content once the installation with SAPInst is completed to get free space. On the contrary, it is recommended to keep /tmp/SAPInst_dir because it contains the installation log files, which could be useful in case an issue arises during later installations.

All the machines hosting an SAP CC server system must use UTF-8 encoding during the installation so that SAPInst can work properly.

On UNIX, use one of the following commands:

export LC_ALL=en_US.UTF-8

setenv LC_ALL en_US.UTF-8

Note that this configuration is needed only for the installation of SAP Convergent Charging. You are allowed to change it as soon as the installation is finished.

The upgrade process will modify automatically the launch scripts dedicated to the instances of your SAP CC server system. These files are located in the central repository of the global host. You need to backup these files and identify the files different from the default files provided with SAP Convergent Charging.

Procedure:

Do a backup copy of the following launch scripts of the server systems:

The files named jstart.config located in the directory:

<DRIVE>:\usr\sap\<SID>\SYS\profile\jstart\ (MS Windows operating system) /sapmnt/<SID>/profile/jstart/ (UNIX and Linux or other operating systems)

Backup the Database Schema

Before upgrading, be sure to backup the existing data to be able to rollback your upgrade.

Refer to the SAP CC 4.0 Operations Guide, section Backup and Restore.

August 2013

Create new Tablespaces or Filegroups

The database schema of SAP CC 4.0 uses new tablespaces (on Oracle) or filegroups (on Microsoft SQL Server) to store audit data. You need to create them before running the upgrade process.

Procedure:

On Oracle, create the following tablespaces:

OBJECT_CHANGE_DATA OBJECT_CHANGE_INDX

On Microsoft SQL Server, create the following filegroups and their associated database files:

OBJECT_CHANGE_DATA OBJECT_CHANGE_INDX

Consult your database documentation for the exact procedures on how to achieve this task.

You need to prepare the upgrade of software applications that are Java based and that use the Java Libraries provided by SAP Convergent Charging (ex: mediation application to communicate with).

Procedure:

Determine if some Java based applications use the Java Libraries of SAP Convergent Charging.

Determine the upgrade sequence and procedures for each application.

Determine if you need to modify the configurations of these applications during the upgrade process because of two new Java libraries added in this version of SAP Convergent Charging:

The SAP CC 4.0 Core SDK contains 2 new JAR files which were not present in the SAP CC 3.0 version and that must be used now for mediation applications:

logging.jar sap.com~tc~logging~java.jar

You should determine how the configuration of your applications using the Java Libraries may have to be modified in order to include these 2 new JAR files.

You copy the installation DVD to each machine hosting an SAP CC server system.

Get the Installation DVD

You normally obtain the installation DVD as part of the installation package from SAP AG.

However, you can also download an image of the latest installation DVD of SAP Convergent Charging in SAP Software Download Center (SWDC). It is available in SAP Support Portal:

Downloads Download Installations and Upgrades

Search for Installations and Upgrades . Then search for the term: SAP Convergent Charging.

https://service.sap.com/support

August 2013

Make the Installation DVD Available

You have to make the required installation media available on the central host where the upgrade will be executed.

Download

The DVD image is included in a multispanning archive that is distributed to several files available for downloads. Download all the files in the same local directory and unpack the archive.

NOTE

Refer to the SAP Note 886535 for more information about multispanning archives.

Once unpacked, the local directory includes a copy of an installation DVD. The name of the root directory is the SAP material number of the installation DVD. It includes few files and the DATA_UNITS subdirectory. You can now prepare the installation folders.

Customize the Installation DVD

You can optionally prepare a subset of the data units that are necessary for your installation. We recommend that you determine a unique subset and that you copy this subset to an installation folder on each host in the system landscape.

Refer to the SAP CC Installation Guide for more information about this customizing.

In a local directory:

Copy the selected data units from the DATA_UNITS subdirectory of the installation DVD. Copy the file LABELIDX.ASC from the root directory of the installation DVD.

You can now prepare the installation folders with this partial copy of the installation DVD.

Prepare the Installation Folders

You have to prepare a temporary installation folder on each host machine that is dedicated to the system landscape of SAP Convergent Charging.

Create an installation folder on each host. From the installation DVD or the local directory that includes a copy or a partial copy of the

installation DVD, copy the necessary elements to the installation folder of each host.

CAUTION

Make sure that the paths to the installation folders do not contain any blank.

NOTE

Do not use the /sampnt share because it is not relevant for this initial installation tasks.


August 2013

CAUTION

Mount the physical installation DVD locally. We do not recommend you to use Network File System (NFS) because reading from DVDs mounted with NFS might fail.

If you copy the installation DVD to local disk, make sure that the path to the destination location of the copied DVD does not contain any blank.

You have to check that the SAP Start Services run for each server instance on every host of the of the SAP CC server systems. It is implemented as a service on MS Windows, and as a daemon on UNIX.

Procedure:

Perform one of the following procedures on each host of the SAP CC system, depending on the operating system:

On Windows:

Open the Computer Management window Open the view Services and Applications > Services The services related to the system are named SAP<SID>_<INSTANCE_NB> (for example

SAPSCC_00). Check that all the services of the SAP CC system are running. If they are not, start them (starting the service does not start the related server instance).

On UNIX and similar operating systems:

Execute the script /usr/sap/sapservices as the root user. It starts all the services of the host which are not already started.

Changed Database Connection Management

In SAP CC 3.0, it was possible to tune the number of threads used for communication relying on the XML over HTTP (HCI) and the SOAP over HTTP communication (WS) channels, using the HTTP_SERVER_THREAD_COUNT system parameter.

In SAP CC 4.0, this parameter only concerns the XML over HTTP communication channel (HCI).

At the same time, a new system parameter named WS_SERVER_THREAD_COUNT is introduced for communications relying on the SOAP over HTTP communication channel. This parameter is created by SAPInst during the upgrade process, with default values which are the same as the current persistent values of the HTTP_SERVER_THREAD_COUNT parameter configured in the updater instances and dispatcher instances of the SAP CC 4.0 Core Server system being upgraded. New connections are required in the database system.

SAP CC 3.0 SAP CC 4.0

System Parameter

Default Settings System Parameter

Default Settings

August 2013

SAP CC 3.0 SAP CC 4.0

System Parameter

Default Settings System Parameter

Default Settings

HTTP_SERVER_THREAD_COUNT

Dedicated to front-end communications via both HCI and WS

Default Values:

Updater instance: 4

Dispatcher: 4


Dedicated to front-end communications via HCI

Default Values:

Update instance: 4 Dispatcher: 4

Constraints:

Check the SAP CC 4.0

System Parameter

Reference for more information about the known constraints.

WS_SERVER_THREAD_COUNT

Dedicated to front-end communications via the Web Services (WS)

Default Values:

Update instance: 4 Dispatcher: 4

Constrains:


System Parameter


SQLHELPER_CONNECTION_COUNT

Default Values:

Rater instance: 20

Updater: 12 Guider: 8 Bulkloader: 4 Dispatcher: 16 Taxer: 8

Constraints:

Check the SAP CC 3.0 System Parameter



Default Values:

Rater instance: 20 Updater: 16 Guider: 8 Bulkloader: 4 Dispatcher: 20 Taxer: 8

Constraints:


System Parameter


The HTTP_SERVER_THREAD_COUNT and WS_SERVER_THREAD_COUNT parameters are linked to the SQLHELPER_CONNECTION_COUNT system parameter, which is used to tune the number of connections which must be used when communicating with databases.

Parameter Constraints in SAP CC 4.0

Dispatcher Instance(s) Updater Instance(s)

August 2013

Parameter Constraints in SAP CC 4.0

Dispatcher Instance(s) Updater Instance(s)

The SQLHELPER_CONNECTION_COUNT parameter must be greater or equal to:

DISPATCHER_SERVER_THREAD_COUNT

+ HTTP_SERVER_THREAD_COUNT

+ WS_SERVER_THREAD_COUNT

+ MULTICAST_SERVER_THREAD_COUNT

The SQLHELPER_CONNECTION parameter must be greater or equal to:

MULTICAST_SERVER_THREAD_COUNT

+ HTTP_SERVER_THREAD_COUNT

+ WS_SERVER_THREAD_COUNT

+ PNR_BULK_THREAD_COUNT

NOTE

Consult the latest version of the SAP CC 4.0 System Parameter Reference for more information about these configuration constraints for each type of instance of the SAP CC 4.0 Core Server system.

To ensure that all the dispatcher and the updater instances of the SAP CC 4.0 system restart at the end of the upgrade process, you must modify the value of the SQLHELPER_CONNECTION_COUNT or HTTP_SERVER_THREAD_COUNT parameter in accordance, and during the initialization of the upgrade process.

Check the Expected Connections in your Database System

Check the communication settings of the SAP CC 4.0 Core Server system in your system landscape. Use the user interface to retrieve the following values:

Dispatcher Instance(s) Current Persistent Value

Default Value

SQLHELPER_CONNECTION_COUNT .. 16

HTTP_SERVER_THREAD_COUNT .. 4

Updater Instance(s) Current Persistent Value

Default Value

SQLHELPER_CONNECTION_COUNT .. 12

HTTP_SERVER_THREAD_COUNT .. 4

Check that the runtime values are the same than the persistent values.

Check the number of dispatcher instances in the SAP CC 4.0 Core Server system.

Check the expected connections:

By default, the SAP CC 4.0 Core Server system expects new connections for each of the dispatcher instances and new connections only for the active updater instance.

Sum up the values of the HTTP_SERVER_THREAD_COUNT parameter in these instances.

August 2013

For example, an SAP CC system deployed with two dispatcher instances and two updater instances and configured with the default settings, needs 12 = 4 + 2*4 new connections to the database system.

Check the Connections in your Database System

In your database system, check the connections dedicated to the SAP CC 4.0 Core Server system in your system landscape.

Check if you can increase the number of these connections.

Determine the New Database Communication Settings

You have to define the final values of the dispatcher instances and updater instances of the SAP CC 4.0 Core Server system in your system landscape:

HTTP_SERVER_THREAD_COUNT WS_SERVER_THREAD_COUNT SQLHELPER_CONNECTION_COUNT

Upgrade Option

Description New Settings

Option 1 The database is able to accept an increased number of connections.

The performances in the system landscape may decrease due to workload of the database system. Monitor it during the

, see page [ ].

Change the value of the SQLHELPER_CONNECTION_COUNT parameter in the dispatcher instances by adding the value of the HTTP_SERVER_THREAD_COUNT parameter.

Apply the same procedure and change the value of the SQLHELPER_CONNECTION_COUNT parameter in the updater instances.

Option 2 The database cannot accept an increased number of connections.

The performances in the system landscape may decrease due to workload of the SAP CC 4.0 Core Server system. Monitor it during the , see page [ ]. The SAP CC system manages fewer threads in parallel for the business operation requests sent via the HCI and WS technical interfaces.

Change the value of the HTTP_SERVER_THREAD_COUNT parameter in the dispatcher instances and in the updater instances.

You can divide the values of the HTTP_SERVER_THREAD_COUNT parameter by 2. In this case you can keep the values of SQLHELPER_CONNECTION_COUNT in the different instances.

Or you can adopt another strategy to adjust the values of these parameters. You can modify the value of the HTTP_SERVER_THREAD_COUNT parameter to a new value which is at most half of the previous value.

CAUTION

August 2013

The performances in the system landscape may decrease. Validate the changes in a quality assurance system with simulated business traffic (charging and refilling operations, configuration operations of master data and customer master data).

Write down these values. You use them during the initialization stage of the of the SAP CC 4.0 Core Server system, see page [ ]:

New Values Dispatcher instances Updater instances



WS_SERVER_THREAD_COUNT

Checking the Transition to the New Logging and Tracing Functions

You have to check that the new functions for logging and tracing are compliant with your IT policy. The SAP CC systems will switch to the new functions after the upgrade.

Procedures:

For each SAP CC system in your landscape, identify if you have some manual or automated procedures that handle former logs or traces to monitor or troubleshoot the system. Consult the information for the new functions and determine the changes that are necessary for these procedures.

Plan the migration of these procedures and validate them during the upgrade of your SAP CC system landscape dedicated for quality assurance and validation.

The table summarizes the old parameters and their corresponding parameters. Refer to the SAP CC System Parameter Reference documentation for more information.

SAP CC 3.0 parameters New parameter of SAP CC 4.0 New additional parameters

LOG_LEVEL

LS_APP_SEVERITY

LS_SYS_SEVERITY

LS_TRC_SEVERITY

LS_TRC_DOMAIN

LS_APP_DESTINATION

LS_SYS_ DESTINATION

LS_TRC_ DESTINATION

LDF1_ENABLED

LDF2_ENABLED

LDF3_ENABLED to LDF5_ENABLED

LOG_FILE_NAME LDF1_FILE_NAME

LDF2_FILE_NAME

LDF3_FILE_NAME to LDF5_FILE_NAME

LDC_FORMATTER

August 2013

SAP CC 3.0 parameters New parameter of SAP CC 4.0 New additional parameters

LOG_FILE_SIZE

LDF1_FILE_SIZE to LDF5_FILE_SIZE

LOG_FILE_BACKUPS LDF1_FILESET_SIZE to LDF5_FILESET_SIZE

LOG_CONSOLE LDC_ENABLED

LOG_ERRORFILE_NAME N/A

NOTE

All the log messages are recorded in the same destination files and can be filtered in a log viewer tool.

LOG_PRINT_THREADNAME_ENABLE

N/A (Always activated)

NOTE

All the output formats include the thread name information.

Preparing the System Configuration Settings for Logging and Tracing

You have to check how to adopt the new functions and how configure the systems.

Procedure:

Identify the current settings. Use the SAP CC 4.0 Configuration Guide to determine the settings relevant for your system

landscape after the upgrade.

The table details the default settings provided with SAP CC 4.0 and SAP CC 3.0:

SAP CC system Parameter of SAP CC 4.0 and default value

Parameter of former version(s) and default value

Core Server LS_APP_SEVERITY

INFO

LS_SYS_SEVERITY

INFO

LS_TRC_SEVERITY

ERROR

LS_TRC_DOMAIN

SQL,NET,MSG,HB,AK,BLK,CACHE,LOCK,NOTIF,ADMIN,HCI,WS,CIF,RIF

LOG_LEVEL

INFORM

August 2013



LS_APP_DESTINATION

LDF1

LS_SYS_ DESTINATION

LDF1

LS_TRC_ DESTINATION

LDF2

LDF1_ENABLED

true

LDF2_ENABLED

true

LDF3_ENABLED to LDF5_ENABLED

false

N/A

NOTE

All the log and trace messages were recorded in the same file destination.

LDF1_FORMATTER (for log messages)

LIST

LDF2_FORMATTER (for trace messages)

TRACE

N/A

NOTE

You cannot customize the file format in former version.

LDF1_FILE_NAME

work/@INSTANCE_ID@_LDF1.log

LDF2_FILE_NAME

work/@INSTANCE_ID@_LDF2.trc

LDF3_FILE_NAME to LDF5_FILE_NAME

Not set

LOG_FILE_NAME

work/@[email protected]

LDF1_FILE_SIZE to LDF5_FILE_SIZE

200MB

LOG_FILE_SIZE

4MB

LDF1_FILESET_SIZE to LDF5_FILESET_SIZE

4 files

LOG_FILE_BACKUPS

4 files

LDC_ENABLED

false

LOG_CONSOLE

true

LDC_FORMATTER

TRACE

N/A

NOTE


August 2013



N/A

NOTE


LOG_ERRORFILE_NAME

logs/@[email protected]


NOTE



FALSE

BART Server ls.app.severity

INFO

ls.sys.severity

INFO

ls.trc.severity

INFO

ls.trc.domain=

(Empty)

log.level

INFORM

ls.app.destination

LDC,LDF1

ls.sys.destination

LDC,LDF1

ls.trc.destination

LDC,LDF2

ld.file1.enabled

true

ld.file2.enabled

true

N/A

NOTE

All the log messages and the trace messages were recorded in the same file destination.

ld.file1.name

work/log/bart_server.log

ld.file2.name

work/log/bart_server.trc

log.file.name

../logs/bart_server.log

ld.file1.size

2MB

ld.file2.size

2MB

log.file.size

2MB

August 2013



ld.file1.setsize

4 files

ld.file2.setsize

4 files

log.file.backups

4

ld.console.enabled

false

log.console

true

N/A

NOTE


log.errorfile.name

../logs/bart_server.err

Diameter Server N/A

NOTE

Diameter Server does not benefit from the new logging and tracing functions.

It is out of scope of this upgrade task.

RootLoggerLevel

INFO

CT Server ls.app.severity

INFO

ls.sys.severity

ERROR

ls.trc.severity

ERROR

ls.trc.domain

LOG_LEVEL

INFORM

ls.app.destination

LDC, LDF1

ls.sys.destination

LDC, LDF1

ls.trc.destination

LDC, LDF2

ld.file1.enabled

true

ld.file2.enabled

true

N/A

NOTE

All the log and trace messages were recorded in the same file destination.

August 2013



ld.file1.formatter (for log messages)

LIST

ld.file2. formatter (for trace messages)

TRACE

N/A

NOTE


ld.file1.name

work/log/ct_server.log

ld.file2.name

work/log/ct_server.trc

LOG_FILE_NAME

../logs/ct_server.log

ld.file1.size

2MB

ld.file2.size

2MB

LOG_FILE_SIZE

4MB

ld.file1.setsize

4 files

ld.file2.setsize

4 files

LOG_FILE_BACKUPS

4

ld.console.enabled

false

LOG_CONSOLE

true

ld.console.formatter

TRACE

N/A

NOTE


N/A

NOTE


LOG_ERRORFILE_NAME

../logs/ct_server.err


NOTE



false

Identify the Necessary Customizing

You have to check if your online mediation system uses the Java Libraries of SAP CC for processing the usage acquisition: Check If the previous logging and tracing functions were activated.

August 2013

You have to check if your offline mediation system uses the Java Libraries of SAP CC for launching CDR acquisition sessions in SAP CC BART Server: Check If the previous logging and tracing functions were activated.

August 2013

This part of the document provides information about upgrading your systems.

When you upgrade your system, note the following:

Before you start with the upgrade, you must have completed all required planning and preparation actions.

The upgrade program does not control the entire upgrade of a SAP CC server system, from checking the requirements and importing the necessary programs through stopping production operation until production operation is resumed. The upgrade process is divided up into a number of different stages. The stages are in turn divided into levels. This section describes all the required user input and actions, as well as critical points during the upgrade.

The upgrade program must run on:

The host of the central instance of the SAP CC Core Server system. The host of the other server systems of SAP CC (BART Server, Diameter Server, CT

Server).

You can use the upgrade logs to monitor the upgrade. The upgrade program logs all actions in the upgrade logs, which you can use as your starting point for troubleshooting.

Many stages of the upgrade require no user input. In the following, you can find a description of all necessary user input.

User actions are also required when errors occur. If an error occurs, correct it and repeat the phase in which the error occurred. Once the phase has been repeated successfully, you can continue the upgrade. For more information about troubleshooting activities, refer to the

section on page [ ].

CAUTION

Upgrade of the SAP CC Core Server system:

If your SAP CC system is installed in a high-availability environment, make sure that only the mediation system that requests real time charging services is connected to the SAP CC Core Server system. The other systems (CRM, ERP, provisioning, invoicing, and billing) must not connect to the Core Server system during the upgrade process.

Upgrade of the SAP CC Diameter Server system:

If your SAP CC system is installed in a high availability switch-over environment, make sure that the failover capabilities of the cluster switch-over software are disabled during the downtime. This is to prevent unwanted failover actions during stop actions of the upgrade procedure.

The upgrade process is the same for each server system of SAP Convergent Charging with the following sequence:

Core Server

August 2013

BART Server Diameter Server Communications Taxing (CT) Server

NOTE

Some specific actions or constraints may exist. They are highlighted in the procedures.

Stages

Initialization: Database Connections Update

Database System (Core Database)

During the phase, you may have decided to change the number of connection in SAP CC Core Database, see page [ ].

Option 1: Increase of database connections Option 2: No change; The total number of connections remains the same.

In this back-end database system, increase the connections dedicated to the SAP CC Core Server system in your system landscape.

Procedure:

Apply the procedure relevant for your database system.

Consult your database documentation for the exact procedures on how to achieve this task.

Core Server System

Change the values of some system parameters. The appropriate parameters and the values have been determined during the phase (see page [ ]) depending on the following options:

Option 1: Change of the values of the SQLHELPER_CONNECTION_COUNT system parameter Option 2: Change of the values of the HTTP_SERVER_THREAD_COUNT parameter

Procedure:

August 2013

Export the configuration of the SAP CC Core Server system with the user interface of SAP CC.

Change the values of the appropriate system parameters for the dispatcher and the updater instances.

Import the changed configuration in the SAP CC system.

NOTE

Consult the SAP CC 4.0 System Parameter Reference for more information about these parameters.

Initialization: Shutdown the Server System

In order to start the upgrade procedure for a normal system, you first have to shut down the SAP CC server system you want to upgrade to version 4.0. This upgrade cannot be done online.

Core Server System

If your system is installed in a high-availability environment, you have only to shut down all the updater instances of the Core Server. They have been identified during the phase, see page [ ].

CAUTION

For high-availability services (real-time charging) do not stop all the instances of the SAP CC Core Server system but only the updater instances.

Procedure:

To shut down an SAP CC server system:

Start the SAP Management Console. In the navigation pane, open the tree structure and navigate to the node of the SAP CC

system that you want to stop. Select the system and then, from the context menu, choose Stop….

You may have to enter the login and password of the SAP system user (<sid>adm).

Wait until all the instances of the SAP CC system are fully stopped.

NOTE

Consult the SAP CC 4.0 Installation Guide or the SAP CC 4.0 Operations Guide for more details about the start and stop procedures according to your operating system.

Initialization: Backup the Software

Perform the procedures decided during the preparation phase.

August 2013

Initialization: Backup the Database

Perform the procedures decided during the preparation phase.

Backup the data in the Core Database system and in the BART Database system.

Configuration and Checks: Starting the Upgrade GUI

The upgrade of the SAP CC system landscape is performed by using the upgrade tool SAPInst. Its configurations is similar than during the implementation of a support package.

NOTE

The instances which have been shut down in preparation of the upgrade will not be restarted automatically at the end of the upgrade procedure performed by SAPInst. Only the instances running at the time of the upgrade will be restarted automatically by SAPInst.

Procedure: Run SAPInst

Go to the CC40_IM_* installation DVD where * is your OS. They have been available during the phase, see page [ ].

Start SAPInst by launching the sapinst.exe program for Windows or the sapinst program for other OSs.

Make entries for the upgrade preprocessing done by SAPInst

NOTES

You can use the accessibility mode: See Using the Accessibility Mode on page [ ] You can have to restart the upgrade program SAPInst: See

on page [ ] If you have to reset the upgrade process for a server, see

on page [ ]

Make Entries for SAPInst

Enter the following information or confirm the existing values when prompted by the upgrade program SAPInst:

Choose Option

Installation Mode

You can upgrade your SAP system either in Typical or Custom mode.

If you choose Typical, the upgrade 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

August 2013

If you do not choose the Custom mode, you can still change later any parameter on the Parameter Summary screen.

Define Parameters

SAP System Identification

You have to specify the Profile Directory of the system to upgrade.

SAP System Administrator Password

Enter the password of the SAP System Administrator.

Operating System Users

Change the passwords for the OS users if you want them to be different from the master password.

Database User

Enter the user and the password used to connect to the database of the system.

Define Parameters

(Custom Mode only )

Database Update

Select the SQL scripts to execute.

By default, the SQL scripts necessary for the upgrade are selected. It is recommended not to modify the default selection.

Update Archives

Specify the archives to be used for the upgrade.

By default, the archive corresponding to the SAP CC system being upgraded (CC_*_SERVER.SAR) and the archive for Wily Introscope (ISAGENT.SAR) are selected. It is recommended to also update the archive for the SAP JVM (SAPJVM6.SAR).

Restart Instances

You can choose to have the running instances restarted by SAPInst at the end of the upgrade.

NOTE

In a high-availability (HA) environment, choose this option. Be sure that updater instances are down.

August 2013

Summary SAPInst displays the summary of the actions scheduled.

You can modify any of the selected parameters by clicking on the appropriate checkboxes and then clicking on the Revise button.

This ends the Configuration and Checks stage of the upgrade process. SAPInst displays a final summary for the actions it will perform.

Checks by SAPInst

When you make entries for SAPInst, the upgrade program performs some checks before processing the upgrade. For more information, see the section on page [ ].

Preprocessing by SAPInst

SAPInst performs mostly this stage of the upgrade process but the system administrator has to complete the processing.

SAPInst performs the following actions during this stage:

Backup unpacked archives in the central repository to allow you to restore previous software versions

Unpack the selected archives containing the new versions of the software units to upgrade and store them in the central repository. The archive for the SAP CC software is systematically updated; The archives for Wily Introscope and the SAP JVM may also be updated during this stage.

Upgrade the database of the system (if applicable for the system being upgraded) by executing the appropriate SQL upgrade scripts.

Core Server only:

Create a shared boot configuration file (boot.config) for all instances of the system in the shared directory.

Modify the launch configuration of each instance of the system in order to retrieve this shared configuration file during startup.

BART Server only:

Modify the configuration file of BART Server (bart.config) to use the new security parameters introduced in this new version of SAP Convergent Charging.

If HTTPS is enabled in BART Server, import to the BART database the corresponding private key and certificate which were previously stored in files.

If HTTPS is enabled in Core Server, import to the BART database the client certificate of Core Server which was previously stored in a file (if applicable).

Create a script for in the directory of the BART Server instance. Remove the obsolete launch configuration properties and keystore files.

Update the launch configuration of the server instances in order to adapt the Java classpath of the server instances to take into account the new JAR files introduced in the new version.

Preprocessing: Checks Before Restarting the Upgraded Server System

You perform some checks before restarting the upgraded SAP CC server system.

August 2013

Procedure (Core Server):

Export the system parameter settings with and check the configuration for the logging and tracing functions. Change the values to be compliant with your IT policy according to your preparation works.

Processing: Restart the Upgraded Server System

You restart the instance(s) of the upgraded server system which were not running during the upgrade.

Procedure:

Start the SAP Management Console In the navigation pane, open the tree structure and navigate to the system node that you

want to start Select the system and then, from the context menu, choose Start…

You may have to enter the login and password of the SAP system user (<sid>adm)

Post-Processing: Check the Restart of the Server System

You check the status of the SAP CC server system and control its logs. The log format has changed. Refer to the SAP CC Library.

The startup process has changed: An instance tries first to connect to the background database. The UDP discovery function is disabled.

Finalization: Clean the Platform

Procedure:

You archive the logs of SAPInst and complete the upgrade:

As administrator you archive the logs generated by SAPInst. These logs are no longer required but can be needed by SAP Support or your technical support for error analysis. Refer to the section on page [ ]. The files are saved in the following directory:

MS Windows operating system: <DRIVE>:\Program Files\SAPInst_instdir\CC40\SLM\UPDATE\

UNIX and other operating systems: /tmp/SAPInst_instdir/CC40/SLM/UPDATE/

You remove the temporary files and directories that are no longer required. Result:

You can perform the next upgrade step.

You can run the upgrade program in accessibility mode. This offers the following features:

Keyboard access High-contrast color Custom font setting

The high-contrast color and custom font setting features are derived from the Windows display properties, which you have to adjust initially.

August 2013

Procedure: Activating and Adjusting Accessibility Settings on Windows

Activate and adjust the relevant settings for the font size and color schemes as follows:

Right click on your Windows desktop and choose Personalize. Select Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.

In the right-hand pane, select Window Color and Appearance. Select a color scheme from the Color scheme drop-down box. To define your own color schemes, choose Advanced.

Procedure: Switching On the Accessibility Mode

To switch on the accessibility mode, proceed as follows:

On the local host: Start the upgrade program as described in Starting the Upgrade Program [page 89] using the command: <DVD_DRIVE>:/STARTUP.bat “guimode=accessible”

On a remote host:

If you use an Internet browser to start the GUI, you only have to start the upgrade program on the local host in accessibility mode. The GUI on the remote host then automatically starts in accessibility mode.

If you start the GUI on a Windows host, proceed as described in Starting the Upgrade GUI [page 90] using the command: DSUGui.bat –accessible

When you restart the upgrade program, it continues at the point where it had stopped. You may need to restart the upgrade program in the following cases:

If an error occurred and an upgrade phase terminated If a system failure occurred

Prerequisites:

If an error occurred, you first have to correct the error. For more information about finding and correcting errors, see the Troubleshooting part of the document. If you are not sure how to proceed, contact SAP Support.

Before you restart the upgrade after a system failure, you must make sure that you meet the requirements for restarting the system successfully.

Procedure:

You can restart the upgrade program by executing the same startup script you used to launch SAPInst on the right host.

You can reset the upgrade, that is, undo all changes that have been made in the system by the upgrade program. For example, you may want to reset the upgrade in the following cases:

You want to repeat one of the Configuration and Checks stage to change an entry. You ran the Configuration and Checks stage for information purposes only and do not want

to upgrade the system now, but at a later point in time.

August 2013

You cannot complete the upgrade in time and therefore need to reset the system to enable production operation again.

The procedures for resetting the upgrade depend on the stage and the level you have reached.

Procedure: During the Initialization Stage

You can reset a stage by pressing the Back button of the upgrade GUI.

Procedure: During the Configuration and Checks Stage

As long as the upgrade is not processing, you can reset a stage by pressing the Back button of the upgrade program SAPInst.

Once the summary report is displayed do not use the Back button anymore: Use the Revise button.

Procedures: During the Processing Stage

Start the upgrade from the beginning.

Procedure: After Reaching the Post-processing Stage

NOTE

Before you overwrite or delete the upgrade directory and the /usr/sap/<SID> directory, make a backup of these directories. SAP Support or your technical support may need this backup to analyze the error.

NOTE

If you want to reset the upgrade after you have upgraded the operating system or database system, you might need to downgrade these software components. For downgrading options, see the vendor´s specification. The safest method is to reload a full backup of the whole system, including the operating system.

If you have Java client applications that use the Java Libraries (APIs) of SAP Convergent Charging, consult this section.

The JAR files from SAP CC 4.0 used by your client applications must be replaced by the JAR files from the Software Development Kit of (SDK) of SAP CC 4.0.

The SAP CC 4.0 SDK contains also 2 new JAR files which were not present in the previous SAP CC 3.0 version:

logging.jar sap.com~tc~logging~java.jar

August 2013

This procedure is different for each application installed in the system landscape.

NOTE

You may need to change the technical configurations of your client applications that use the SAP CC 4.0 Java Libraries in order to take into account the two new JAR files.

Procedure: Upgrade of JAR files

Perform the procedure identified during the phase, see page [ ].

Procedure: Upgrade of Technical Configuration of the Client Applications

Perform the procedure identified during the phase, see on page [ ].

Consult the SAP CC 4.0 Installation Guide.

Get the configuration files of your previous graphical user interfaces (GUIs) and install the new versions by re-using these configuration settings.

Upgrading the Core Tool and the BART Tool

Procedure: Core Tool

See the procedure below to install the user interface:

Upgrade

Backup the configuration file Unzip the core_tool.zip file in the installation directory

Post-processing

Launch the core_tool.bat script from the bin directory to start Core Tool Log on and check that the user interface can connect to the server

Procedure: BART Tool

See the procedure below to install the BART Tool user interface:

Upgrade

Backup the configuration file Unzip the bart_tool.zip file in the installation directory

Post-processing

Launch the bart_tool.bat script from the bin directory to start BART Tool Log on and check that the user interface can connect to the server

August 2013

Upgrading the IEC Tool

Procedure: Connector Administration Tool (CAT Tool)

See the procedure below to install the CAT Tool user interface:

Upgrade

Unzip the cat_tool.zip file in the installation directory If you use an IEC for working with the BART Server system, copy the new bart_iec.jar

files from your BART Server installation to the /jars/ directory of CAT Tool. An old version of this file should be already present.

Post-processing

Launch the cat_tool.bat script from the bin directory to start CAT Tool

August 2013

This part of the document contains information about the follow-up activities that you need to perform after you have upgraded your SAP Convergent Charging system.

When you perform follow-up activities, note the following information (in addition to the information in Quick Guide section, see page [ ]:

Perform the actions described in Quick Guide section in the specified order.

The follow-up activities are divided into three blocks:

Sequence Description

Actions needed before resuming production operation

These actions ensure that all the processes that are relevant to system operation are available again.

You can start these actions while the upgrade program is finishing the upgrade.

Actions during limited production operation

During this time, your SAP system is already consistent and all the processes that are relevant to system operation are available. However, this system state does not yet contain measures for optimizing performance, or actions for resuming standard operation (for example, resuming background processing, or adjusting authorizations).

Check the actions that are listed in this block and if necessary, perform them before you restart production operation.

Actions during production operation

You can also perform these actions when the system is back to production operation.

Monitor the performances of the business services before resuming production operation:

Real-time charging and refilling operations (Online Charging Services) Batch charging operations, rerating operations (Offline Charging Services) Configuration operations of customer master data (initial provisioning, data maintenance)

NOTE

If you have decreased the values of the HTTP_SERVER_THREAD_COUNT parameter in the dispatcher instances and in the updater instances of the upgraded SAP CC 4.0 Core Server system, simulate the following kinds of business traffic to validate the upgrade of a quality assurance system:

Refilling operation Configuration operations of customer master data

Initial provisioning Data maintenance

The SAP CC 4.0 Core Server system uses fewer threads in parallel to manage the business operation

August 2013

requests sent via the HCI and WS technical interfaces.

After the upgrade process is completed, you can configure the upgraded system to use the new features provided by SAP Convergent Charging 4.0 before resuming production operation.

Candidate Changes

This section lists the changes available in the new version of SAP Convergent Charging and that you can benefit on your system landscape after the upgrade.

NOTE

More functions are available in this software version but they are out of scope of an upgrade of the systems: A potential migration of old master data requires a migration of the existing integration developments and customizing. A new technical interface (Web Services) must be used by the connected systems. This migration must be part of a new implementation project of SAP Convergent Charging in your system landscape.

Area Feature Condition

Security Encryption of communication channels

Fine-grained auditing of master data modifications

Master Data Configuration

for the Service Provider

Chargeable item classes

Tiered pricing based on new business data tables: The range tables

Master Data Configuration

for the End Customers

Tiered pricing based on new business data tables: The subscriber range tables

Tax Management Support of EU VAT Rules in the master data

System Integration and Service Implementation

Offline charging services via the Web Services technical interface

New communication ports configured as detailed in the next section

Configuration Guide

Integrated Scenario within the SAP Business Suite components

Native rerating integration with SAP ERP/FI-CA 6.0 EhP7

SAP Convergent Invoicing stores the consumption data (the function must be enabled)

August 2013

(*) Some new functions are not applicable to master data created with a previous version of SAP Convergent Charging.

Encryption of communication channels Fine-grained auditing of master data modifications Rerating integrated with SAP ERP and SAP Convergent Invoicing

Refer to the SAP CC 4.0 Configuration Guide for information on how to configure these features.

Enabling the encryption of the communication channels

The administrator can configure the SAP CC system so that the various communication channels are encrypted. Each communication channel can be configured separately.

Procedure:

For more information, refer to the SAP CC 4.0 Configuration Guide.

Enabling the fine-grained auditing of master data modifications

The administrator can enabled the fine-grained auditing of the modifications performed on master data. This enables the recording of all modifications made to the master, with the ability to consult the master data before and after the modifications.

Procedure:

Go the directory /usr/sap/<SID>/CCD<INSTANCE_NB>/script/ of a dispatcher instance of the SAP CC system

Export the system configuration by executing the user interface with the following command: config configuration export <OUTPUT_FILE> updater

Open the file where the system configuration was exported. Locate the entry for the parameter AUDIT_OBJECT_ACTIVATION and set its value to true. Import the updated system configuration by executing with the following

command: config configuration import <INPUT_FILE>

For more information, consult the SAP CC Configuration Guide.

Enabling the new Web Services (Charging and Recharging)

Before implementing the offline charging services (batch charging, re-charging) via the Web Services technical interface, you must enable new communication ports in the dispatcher instances of the SAP CC system.

Do not apply this procedure if you migrate your system landscape from offline charging services based on SAP CC BART to services based on SAP Convergent Invoicing. Consult the section dedicated to the system landscapes that relate to a solution scenario with SAP CC and SAP ERP/FI/CA.

August 2013

Procedure

Export the instance map to a file with SAP CC with the command setup instancemap export ./instancemap.csv

Enter your login and your password at the prompt.

Modify the instance map to enable the Web Services on the dispatcher instances.

Open the file instancemap.csv in a text editor. In all the lines that include the column ‘InstanceId’ starting with ‘dispatcher’, set up

the value of the column ‘WSHost’ and ‘WSPort’ to the address and the port where you want to publish the Web services.

Set up the value of the column ‘WSSecure’ to true when the communications with the dispatcher instances must be secured.

Import the changed instance map and check on the console that the import is successful. Link the client certificate used for the secured communications with the updater instances

via the Web Services technical interface.

Use to list the certificates with the command setup certentry list Display the linked certificate entries with the command setup certentry listLinks

Link with the command setup certentry link ws

Restart the dispatcher instances of the SAP CC system.

Updating the VAT Rates

The upgrade tool does not change the VAT rates customized in the SAP CC Core Server system. You can maintain this business data by using the last version of the default VAT rates.

Procedure:

In the central repository of the SAP system:

Consult the file /sapmnt/<SID>/exe/uc/<OS>/CC_CORE_SERVER/tax/vat_rate.txt

Perform the procedure from the Configuration Guide: Setting up the VAT Rates

Refer to the SAP CC Configuration Guide.

Enabling the Rerating with SAP ERP/FI-CA (SAP Convergent Invoicing)

You can enable the triggering of the rerating in SAP Convergent Invoicing in the SAP ERP/FI-CA system to perform the rerating process for provider contracts. In this configuration, you use SAP Convergent Invoicing to store the consumption items to send back to SAP CC.

For more information on the rerating process with the storage of consumption data in SAP Convergent Invoicing in the SAP ERP system, see the SAP CC Configuration Guide.

For more information on the transition from offline charging services provided by SAP CC BART to services provided by SAP Convergent Invoicing with Consumption Item management, refer to the Transition Guide.

August 2013

You must perform the following actions before you can display the online documentation (SAP Library) in your SAP system landscape:

Install the SAP online documentation in your SAP system as described in the README.TXT file contained in the root directory of the online documentation DVD, which is delivered as part of the upgrade package.

Configure the upgraded graphical user interfaces (Core Tool)

For more information, see the Configuration Guide.

To make sure that your SAP Convergent Charging software is running smoothly, we recommend implement new Support Packages (SP) in your system as soon as they become available. This also applies after the upgrade, to avoid potential problems in your system before they occur.

If you have not included all the necessary Support Packages in the upgrade, you can still import them after the upgrade.

Back to Quick Guide, see page [ ]

Do a full backup of your systems.

During a limited period, you perform the following actions:

Daily monitor the performances

August 2013

For troubleshooting the upgrade, you can use the logs from:

SAPInst The SAP CC system being upgraded

During the execution of the upgrade process, SAPInst writes detailed logs of all the actions it performs on the file system of the host where it is executed.

These log files are written in the following directory:

MS Windows operating system:

<DRIVE>:\Program Files\SAPInst_instdir\CC40\SLM\UPDATE\

UNIX and other operating systems:

/tmp/SAPInst_instdir/CC40/SLM/UPDATE/

This directory includes subdirectories that contain the log files and control files of previous executions of SAPInst. These subdirectories have a naming convention: “log” is used as prefix and the date/time is added to the name.

EXAMPLE

The UPDATE directory includes a directory named: log_27_Sep_2012_08_53_07

Among the files contained in this directory, 2 files are particularly important. These files describe the actions performed by SAPInst during the upgrade process:

SAPInst.log (summary of actions) SAPInst_dev.log (this log file includes more detailed information than SAPInst.log)

The directory also contains an archive named SUPPORT.SAR which contains all the important log files for troubleshooting the issue.

The individual log files of the instances of the SAP CC system(s) can be used to troubleshoot issues encountered during the upgrade process.

Each instance of the system has a directory where its own log files are written:


<DRIVE>:\usr\sap\<SID>\<INSTANCE_NAME>\work\

Other operating systems:

/usr/sap/<SID>/<INSTANCE_NAME>/work/

For more details, consult the SAP CC 4.0 Operations Guide.

August 2013

SAP CC Server System

All instances of the SAP CC server system have a local copy of the software binary files. These copies are retrieved from the central repository of the system when the instances start.

In order to restore the software binary files to the previous version, you need to restore first the files on the central repository, and then restart all the instances of the SAP CC server system.

The directory in the central repository containing the software files is located in the following folder:


<DRIVE>:\usr\sap\<SID>\SYS\exe\uc\<OS>\

UNIX and Linux or other operating systems:

/sapmnt/<SID>/exe/uc/<OC>/ or /usr/sap/<SID>/SYS/exe/uc/<OS>/

Where: <OS> corresponds to the operating system where the system is installed:

Operating System Directory Name

Windows 64-bit ntamd64

AIX rs6000_64

HP-UX hpia64

Linux linuxx86_64

Solaris sunx86_64

This central repository contains the archives of the previous upgrade or update operations. It includes the following folders created by SAPInst:

Subdirectories named <SOFT_UPG_FILES> that contain the current version of the software binary files.

Backup subdirectories named <SOFT_UPG_ARCHIVED>.<ARCHIVE_DATE> that contain the backup copy of the software binary files composing a previous version.

Different software units are handled. The possible subdirectory names (for <SOFT_UPG_FILES>) are:

CC_CORE_SERVER CC_BART_SERVER CC_DIAMETER_SERVER CC_COMMUNICATIONS_TAXING_SERVER sapjvm_6 wily

NOTE

Regarding to the SAP CC Communications Taxing Server system, the subdirectories related to

August 2013

sapjvm_6 and wily are available in an intermediate folder named 32-bit.

Some subdirectories correspond to old updates (implementation of a support package) of former versions of SAP Convergent Charging.

Procedure (Core Server):

To restore the software files to the last version before the upgrade:

Remove the subdirectory CC_CORESERVER Locate the subdirectory CC_CORESERVER.<timestamp> with the highest timestamp value

and rename it to CC_CORESERVER Restart all the instances of the SAP CC system you want to restore the version so that each

instance retrieves a copy of the restored software files from the central repository. Procedure (Other server systems):

To restore the software files to the last version before the upgrade:

Remove the subdirectory CC_<system> Locate the subdirectory CC_<system>.<timestamp> with the highest timestamp value and

rename it to CC_<system> Restart all the instances of the SAP CC system you want to restore the version so that each

instance retrieves a copy of the restored software files from the central repository.

August 2013

August 2013

© Copyright 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

August 2013

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.

You can find this document at the following location: SAP Business Suite Applications SAP Convergent Charging

https://service.sap.com/instguides

© Copyright 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20

cc40_UpgradeG_CSTMR_v1-0

Documents