Installation Guide

SAP Convergent Charging (SAP CC 4.0)

Target Audience

System Administrators

Technical Consultants

CUSTOMER Document version: 1.3 – April 2014

CAUTION

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

You can find the latest version on SAP Service Marketplace (SMP) at the following locations:

https://service.sap.com/instguidescc40 Install

https://service.sap.com/instguides SAP Business Suite Applications SAP Convergent Charging SAP CC 4.0 Install

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

1.1 November 2013 First maintenance version (SAP CC 4.0 SP02 – Feature Pack)

1.2 February 2014 Second maintenance version (SAP CC 4.0 SP03)

1.3 April 2014 Third maintenance version available (SAP CC 4.0 SP04 – Feature Pack):

Support of Sybase ASE database

Database preparations

DOCUMENT HISTORY .............................................................................................................. 2

TABLE OF CONTENTS............................................................................................................... 3

1 INTRODUCTION ............................................................................................................ 6

New features ................................................................................................................................. 6 Operating Systems and Databases Releases ........................................................................................... 6

SAP Notes for the Installation ....................................................................................................... 6

Document Abbreviations .............................................................................................................. 6

2 INSTALLATION OPTIONS COVERED BY THIS GUIDE .................................................................. 8

Overview ....................................................................................................................................... 8 Installable Elements ................................................................................................................................ 8 Special Legal Requirements ................................................................................................................... 10

Dependencies .............................................................................................................................. 10 Server Systems ....................................................................................................................................... 10 GUIs ....................................................................................................................................................... 11 Databases .............................................................................................................................................. 12

3 PREPARATION ............................................................................................................ 13

Preparation Checklist .................................................................................................................. 13

Landscape .................................................................................................................................... 13

Choose your SAP System IDs ....................................................................................................... 13

Prepare the Hosts........................................................................................................................ 14 Download the Installation DVD ............................................................................................................. 14 Download the Java Cryptography Extension Jurisdiction Policy Files Archive ....................................... 15 Download the SAP Cryptographic Library ............................................................................................. 15 Download SAPCAR ................................................................................................................................. 15 Download SAP JVM 6.1 ......................................................................................................................... 16 Check Free Space on the Hosts .............................................................................................................. 16 System Landscape Directory (Optional) ................................................................................................ 16 Global Host and the Central Repository ................................................................................................ 17 Create the sapmnt Directories (UNIX and LINUX) ................................................................................. 18 Create and Share the Working Directory............................................................................................... 19 Configure the host’s OS for UTF-8 Encoding .......................................................................................... 19 Configure OS Time Zones on each Host ................................................................................................. 19 Set the Environment Variables SAP_IPv6_ACTIVE and NI_USEIPv6 ...................................................... 19 Prepare the Installation Folders ............................................................................................................ 20 Customize the Installation DVD ............................................................................................................. 22 Install Processor Drivers (WINDOWS).................................................................................................... 22

Prerequisites for US Telco Taxes Computation (TAXERS AND CT SERVER) ................................. 23 Install Additional Microsoft Libraries .................................................................................................... 23 Install Billsoft EZTax............................................................................................................................... 23 Create a Central Repository for EZTax Information ............................................................................... 23

Install your SAP ERP System ........................................................................................................ 24 Create a User for SAP CC ....................................................................................................................... 24 Create an RFC Destination (CT SERVER) ................................................................................................ 24 Storage of Consumption Data in SAP CI ................................................................................................ 25

Install the CA Wily Introscope Enterprise Manager .................................................................... 25

Users............................................................................................................................................ 25 On UNIX and Linux ................................................................................................................................. 26 On Windows .......................................................................................................................................... 26

Securing the Communication Channels ...................................................................................... 26 Get an OpenBlox License Key (Diameter Server) ................................................................................... 26 Determine the Securing Mode ............................................................................................................... 26

4 DATABASE INSTALLATION .............................................................................................. 29

Setting up the database .............................................................................................................. 29

Preparing the ASE Database ....................................................................................................... 29 Install Sybase ASE Database .................................................................................................................. 29 Configuring Sybase ASE Server .............................................................................................................. 31 Create the Devices ................................................................................................................................. 33 Create the Database .............................................................................................................................. 33 Create a Login ....................................................................................................................................... 34

Preparing the SQL Server Database ............................................................................................ 34 Install SQL Server Management Studio ................................................................................................. 34 Set the Authentication Mode ................................................................................................................ 34 Create a Login ....................................................................................................................................... 34 Give the Appropriate Roles .................................................................................................................... 35 Test the New Login ................................................................................................................................ 35 Create the Database .............................................................................................................................. 35

Preparing the Oracle Database ................................................................................................... 35 Oracle Installation ................................................................................................................................. 36 Initialization ........................................................................................................................................... 36 Create a User Account ........................................................................................................................... 36 Grant the User ....................................................................................................................................... 36

Preparing the DB2 Database ....................................................................................................... 37 Start the DB2 Command Prompt ........................................................................................................... 37 Create the Database .............................................................................................................................. 37 Create a User ......................................................................................................................................... 37 Grant the User ....................................................................................................................................... 38

Creating Tablespaces, Filegroups or Segments ........................................................................... 38 Create Tablespaces (Oracle and DB2) ................................................................................................... 38 Create Filegroups and Associated Database Files (SQL Server) ............................................................. 40 Create Segments (Sybase ASE) .............................................................................................................. 42

5 INSTALLATION ............................................................................................................ 44

Installing the Servers ................................................................................................................... 44 Run SAPInst ........................................................................................................................................... 44 Run SAPInst for the Core Server - First Step ........................................................................................... 45 Run SAPInst for the Core Server - Add Instance(s) ................................................................................. 51 Run SAPInst for the BART Server ........................................................................................................... 53 Run SAPInst for the Diameter Server ..................................................................................................... 58 Run SAPInst for the CT Server ................................................................................................................ 62

Installing the Tools, the IEC and the SDK .................................................................................... 62 Prepare the Installation ......................................................................................................................... 62 Organize Directories .............................................................................................................................. 64 Get the Installation Files from DVD ....................................................................................................... 64 Core Tool ............................................................................................................................................... 64 BART Tool .............................................................................................................................................. 65

IEC .......................................................................................................................................................... 65 CAT Tool................................................................................................................................................. 67 Simulation Tool ...................................................................................................................................... 68 Installing the SDKs ................................................................................................................................. 68

6 POST-INSTALLATION .................................................................................................... 69

Cleanup ....................................................................................................................................... 69

Installing the SAP License ............................................................................................................ 69 Apply for the Permanent License ........................................................................................................... 69 Install the Permanent License ............................................................................................................... 69 Restart the Instances ............................................................................................................................. 70

Starting and Stopping the Servers............................................................................................... 70 Windows ................................................................................................................................................ 70 Other Operating Systems ...................................................................................................................... 70 Related Documentation......................................................................................................................... 71

Accessing to the Online Help of the Tools .................................................................................. 71

System Configuration .................................................................................................................. 71

Administrating the Servers ......................................................................................................... 71

Support Packages and Patch Implementation ............................................................................ 71

User Management ...................................................................................................................... 71 BART User Management ....................................................................................................................... 72

Configuring SAP CC for the System Landscape Directory ........................................................... 72

Configuring the Technical Monitoring in SAP Solution Manager 7.1 .......................................... 72

7 ADDITIONAL INFORMATION ........................................................................................... 73

Uninstalling SAP CC ..................................................................................................................... 73 Uninstalling an Instance or a Server ...................................................................................................... 73 Uninstalling the Database ..................................................................................................................... 74 Uninstalling the IEC, a Tool or a SDK ..................................................................................................... 74

Disclaimer .................................................................................................................................... 76

Documentation in SAP Support Portal ........................................................................................ 76

Documentation in SAP Help Portal ............................................................................................. 76

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

Here you can find the new features of the installation for this release.

Operating Systems and Databases Releases

To know which operating systems and database releases are supported for each component of SAP CC 4.0, see the Product Availability Matrix at the following address: http://service.sap.com/pam.

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

SAP Note Title

197623 Temporary license keys

94998 Requesting license keys and deleting systems

611361 Hostnames of SAP servers

1453216 CA Wily Introscope for SAP Convergent Charging

1238121 SAP JVM for Software Logistics Tools

1240081 "Java Cryptography Extension (JCE) Jurisdiction Policy" files

397175 SAP Cryptographic Software - Export control

1036194 OS timers are not synchronized

1367498 SAP JVM installation prerequisites

1375494 SAP system does not start after applying SAP kernel patch

1363170 DB6: Installing fix packs for DB2 v9.7 (Windows)

1875021 System Monitoring Setup for SAP Convergent Charging

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

CDR Consumption Detail Record

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

NFS Network File system

PKCS Public-Key Cryptography Standards

PSE Personal Security Environment

RAC Real Application Cluster (Oracle)

RDBMS Relational Database Management System

SAPSID SAP System Identifier (see also SID)

SAR SAP Archive

SID SAP system Identifier

SLD System Landscape Directory

SNC Secure Network Communications

TIF Transaction Integration Framework

TLS Transport Layer Security

URL Uniform Resource Locator

VAT Value Added Tax

XML eXtended Markup Language

Installable Elements

Software Components

This guide covers the installation of the following software components of SAP Convergent Charging:

Core Server and Core Tool

Diameter Server

BART Server and BART Tool

Communications Taxing (CT) Server

Import/Export Connector (IEC) and CAT Tool

Simulation Tool

Software Units

Each component includes several software units: server system, graphical user interface, and integration libraries for fronted systems or applications connected to SAP CC and based on Java technology.

You can install all the elements detailed in the following table:

SAP CC Software Components

Software Units Third-party Software

Back-End System

Server System Frontend System

Frontend GUI RDBMS

Server Systems

Core Server and Core Tool

Core Server System

Core SDK Core Tool (Billsoft EZTax) Only for US Telco tax management

Core Database

Diameter Server Diameter Server System

- - - -

BART Server and BART Tool

BART Server System

BART SDK BART Tool - BART Database

Communications Taxing (CT) Server

CT Server System

- - Billsoft EZTax Only used by SAP CI in batch mode for US Telco tax management

-

Other Components

Import/Export Connector (IEC) and CAT Tool

IEC IEC SDK CAT Tool - (Customer Database)

(IEC Database)

SAP CC Software Components

Software Units Third-party Software

Back-End System

Server System Frontend System

Frontend GUI RDBMS

Simulation Tool - - Simulation Tool

- -

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

See the SAP CC 4.0 Master Guide, the SAP CC 4.0 Sizing Guidelines, and the SAP CC 4.0 Library to determine which software components and units you need to install. Also ask your SAP Solution Consultant.

NOTE

The Core Server system is composed of several system instances deployed to different hosts: dispatchers, updaters, guiders, raters, taxers and bulkloaders.

CAUTION

This guide does not cover the installation of SAP ERP. However, SAP Convergent Charging and SAP ERP can work together and some installation steps depend on whether you use the Convergent Invoicing scenario or not.

See the figure below for an overview of a standard platform.

Special Legal Requirements

The features that depend on special legal requirements are listed in the following table:

System Feature

Core Server Tax Management

BART Server None

IEC None

Diameter Server None

Communications Taxing Server U.S Telco Tax Management

Server Systems

Take the following remarks into account when planning your system landscape:

You need to install the Core Server system for using the BART Server or the Diameter Server system, or the IEC application

The BART Server system and the IEC application are used for batch charging operations (refer to the “Chargeable Items Charging” process in the SAP CC 4.0 Library (Application Help))

The Diameter Server system is used in real time systems (online charging systems)

The Communications Taxing Server system is used by the SAP ERP /FI-CA system to compute US Telco taxes. See the figure below for an overview of a platform with the Communications Taxing component

NOTE

US Telco taxes are computed with the Billsoft EZTax software. You must install EZTax if you manage US Telco taxes, see page [23].

CAUTION

The taxers and the CT Server are only available for Windows and Linux Red Hat operating systems.

GUIs

If you install an SAP CC server system, you must install the corresponding graphical user interfaces (GUI). Respect the following constraints:

The Core Server and the Core Tool components can be installed on distinct hosts. You can install several Core Tool user interfaces on distinct hosts

The IEC and the CAT Tool components can be installed on distinct hosts but you need to be able to transfer scenario files to the host of the IEC

The BART Server and the BART Tool components can be installed on distinct hosts

The Simulation Tool component is a standalone program. You can install it anywhere.

CAUTION

In a high availability (HA) environment, do not install the graphical user interfaces (Core Tool or BART

Tool) on a machine that hosts an instance of an SAP CC server system (Core Server, BART Server).

Databases

Respect the following constraints for installing the databases:

If you install the Core Server component, you must install the Core Database in a back-end database system

If you install the BART Server component, you must install the BART Database in a back-end database system

In most cases, the IEC database is not installed. You need to install the IEC database only if you want the IEC to be connected to a database (use of the Export to Database Action and Import XCI from Database Action components of the CAT Tool). Note that other solutions are now preferred such as using SAP CC BART Server or SAP Convergent Invoicing in SAP ERP / FI-CA

You have to complete the following preparations before installing SAP Convergent Charging:

Determine your Landscape [page 13]

Choose your SAP System IDs [page 13]

Prepare the hosts [page 14]

Prepare the installation folders [page 20]

Prepare the installation of the different tools, of the IEC and the SDKs [page 62]

The following preparation activities depend on your landscape:

Prerequisites for US Telco taxes computation (taxers and CT Server) [page 23]

Create an RFC destination (CT Server) [page 24]

Install your SAP ERP system [page 24]

The following preparation activities are optional:

Install the CA Wily Introscope Enterprise Manager [page 25]

Install certificates to secure the different communication channels [page 26]

Determine which servers, databases and tools you want to install. Determine the SAP System IDs (SID) – see below – for the mandatory and optional components (Core Server, BART Server, Diameter Server and CT Server) of SAP CC. Also check which instances you need in the Core Server. Determine on which hosts you will install these elements. See the SAP CC Library and your SAP Solution Consultant to help you planning your landscape.

The SAP system ID or SID is the identifier for the SAP system. Choose an SAP system ID for each SAP CC server system (Core, BART, Diameter or CT) you want to install on your landscape.

Choose your SID carefully. Renaming is complicated and requires that you re-install the SAP system.

The following rules must be respected:

The SID must be unique throughout your organization and consistent throughout your SAP system installation landscape. If you want to install an additional application server instance, make sure that no gateway instance with the same SID exists in your SAP system landscape

The ID must consist of exactly three alphanumeric characters

Only uppercase letters are allowed

The first character must be a letter (not a digit)

The following IDs are reserved and cannot be used: ADD ALL AMD AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP TOP UID USE USR VAR

Download the Installation DVD

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

However, you can also download the latest version of SAP Convergent Charging in SAP Software Download Center (SWDC). It is available in SAP Support Portal at the following address: https://service.sap.com/swdc

Download the latest support package (SP) of SAP CC 4.0 on SAP Service Marketplace at: https://service.sap.com/installations A-Z Index(on the left frame) C SAP Convergent

Charging SAP Convergent Charging 4.0 .

A support package of SAP CC is a complete version this SAP software component. It includes all the SAP CC software components and units provided in the installation media. You can use is for an initial installation or for an update of an SAP CC system.

An SAP Note details the content of the version and the update procedures and lists the patch levels that are available. Before installing a support package, check in its SAP Note if a patch is available.

Download

A support package is included in a multispanning archive that is distributed to several files available for downloads. Download all the files in the same local directory and unpack the archive.

NOTE

Refer to 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.

DVD Content

The DVD contains the following elements:

DVD Directory Content Description

<INSTALL_DVD>/ The root directory contains the following files: CDLABEL.ASC

CDLABEL.EBC

COPY_TM.HTM

COPY_TM.TXT

DATA_UNITS

LABEL.ASC

LABEL.EBC

LABELIDX.ASC

MD5FILE.DAT

MID.XML

SHAFILE.DAT

VERSION.ASC

VERSION.EBC

DVD Directory Content Description

<INSTALL_DVD> /DATA_UNITS/

The DATA_UNITS directory contains a subdirectory for each data unit available in the installation DVD. A data unit may include several software units:

The SAPInst program and the installation framework is available in the following folders:

CC40_IM_***

INST_CC40_UC_***

The software units of SAP CC are available in the following folders: Core Server System: CC40_UC_***

Diameter Server System: CC40_DIAMETER_UC_***

BART Server System: CC40_BART_UC_***

CT Server System: CC40_CT_UC_***

All the other software units (user interfaces, development libraries) are available in the CC40_TOOLS_CONTENT_UC_OSIND folder

Note that *** corresponds to the following operating systems:

WINDOWS_X86_64 (or WINDOWS_X8664)

AIX_PPC64

HPUX_IA64

SOLARIS_X86_64

LINUX_X86_64

Download the Java Cryptography Extension Jurisdiction Policy Files Archive

The SAP JVM is not delivered with Java Cryptography Extension (JCE) Jurisdiction Policy files. The delivery of these is subject to import restrictions in some countries. The JCE Jurisdiction Policy files must be made available so that SAPInst can install them.

Download the “Unlimited” JCE Jurisdiction Policy files as described in SAP Note 1240081.

NOTE

Go to the link for jvm6.1.

Download the SAP Cryptographic Library

If you want to secure connections between SAP CC and other SAP systems (such as SAP ERP or SAP CRM), you must download the SAP Cryptographic Library installation package which is available for authorized customers on the SAP Service Marketplace at https://service.sap.com/swdc.

Download and export control for the SAP Cryptographic Library are described in SAP Note 397175.

Download SAPCAR

Go to https://service.sap.com/support Software Downloads Support Packages and Patches

Search for Support Packages and Patches . Then search for the term SAPCAR (which is required to unpack the SAR archive).

Download SAP JVM 6.1

Get the SAP JVM 6.1 on SAP Service Marketplace at the following location: https://service.sap.com/support Software Downloads Support Packages and Patches

Search for Support Packages and Patches . Then search for the term SAP JVM 6.1

We recommend that you choose the highest available patch level. Download the .SAR file and copy it to a directory of your choice in your system.

Check Free Space on the Hosts

Use the table below to determine how much free space you need on each host to install SAP Convergent Charging:

CC Component Installation DVD Depot ( logs and temporary files) Instance(s)

Core Server 4.1GB 1GB 1GB per instance

BART Server Diameter Server CT Server

4.1GB 1GB 1GB

NOTE

The depot is used by the installation program (SAPInst) to create temporary files. Each time you launch SAPInst, you need to check that you at least have 1GB or free space for storing these temporary files. SAPInst creates the following directories:

/tmp/SAPInst_dir for UNIX and Linux

<DRIVE>:\Program Files\SAPInst_instdir for Microsoft Windows

/tmp/SAPInst_exe* for UNIX and Linux

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

NOTE

Give the read, write and execute permissions to all users on the working directory.

System Landscape Directory (Optional)

Determine if the System Landscape Directory of SAP NetWeaver (SLD) is installed on your platform. If SLD is installed, you can provide SAPInst with connection information so that SAP CC updates regularly the SLD, see page [47].

NOTES

It is also possible to configure the access to the SLD after the installation of SAP CC; See page [72].

For more information about System Landscape Directory of SAP NetWeaver, consult the documentation in SAP Help Portal at the following address:

http://help.sap.com/nw70 SAP NetWeaver 7.0 SAP NetWeaver 7.0 Library (English)

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management

by Key Capability Software Life Cycle Management System Landscape Directory

Global Host and the Central Repository

The SAP Global Host is the first host machine installed with an instance of an SAP system. There is a global host for each SAP system. The first installed instance of an SAP system is the Central Instance. In an SAP CC Core Server system, the central install is a dispatcher instance.

The global host includes the SAP Central Repository of each installed SAP system. This repository includes executable programs and profiles of all instances. In an SAP system with distributed instances and hosts, this repository is a file directory and must be shared for all hosts of the SAP system:

On Windows, the central repository is shared and is visible by the other hosts in the SAP system. The share name is saploc or sapmnt

On UNIX and Linux and other operating systems, the central repository needs to be shared using Network File System (NFS) and then mounted for all hosts belonging to the same SAP system

The location of the central repository is:

OS of the Global Host Central Repository External Visibility

MS Windows operating system

<DRIVE>:\usr\sap\<SID>\SY

S\

The installation program (SAPInst) creates this directory.

Other hosts can access to the central repository of their SAP system via:

\\<SAP_GLOBAL_HOST>\sapmnt\<

SID>\SYS\

The installation program (SAPInst) creates a MS Windows share from sapmnt to the <DRIVE>:\usr\sap\ directory.

UNIX and Linux or other operating systems

/sapmnt/<SID>/

The installation program (SAPInst) creates the /usr/sap/<SID>/ directory and creates some symbolic links to the subdirectories in the central repository.

Other hosts can to the central repository of their SAP system via a mount directory /sapmnt/:

/sapmnt/<SID>/

Where <SID> is the SAP System Identifier of the SAP CC system to install.

The central repository includes the following subdirectories for an SAP system:

Subdirectory Description

exe This directory contains executable kernel programs in a subdirectory uc/<OS_PLATFORM>/.

In an SAP CC system with distributed instances and hosts, this directory must be shared for all hosts of the system.

Subdirectory Description

global

This directory contains log files.

In an SAP CC system with distributed instance and hosts, this directory must be shared for all hosts of the system.

profile This directory is the central SAP Profile Folder. It contains the start and operation profiles of all instances:

Startup configuration files

Boot configuration files

In an SAP CC system with distributed instance and hosts, this directory must be shared for all hosts of the system.

It includes the subfolders:

boot jstart

Create the sapmnt Directories (UNIX and LINUX)

If you perform a multi-host installation of the Core Server, you have to create and share the /sapmnt directory.

On the global host (first host to be installed), perform the following operations:

Create the /sapmnt/ folder

Create a NFS share of /sapmnt with the options rw and no_root_squash

Using the following commands :

mkdir /sapmnt

/etc/init.d/nfs start

/sbin/chkconfig nfs on

chmod –R 766 /sapmnt

echo “/sapmnt *(rw,sync,no_root_squash)” >> /etc/exports

/usr/sbin/exportfs –ra

/etc/init.d/nfs restart

NOTE

Open the ports to allow remote client to connect.

CAUTION

Disable the no_root_squash option after the installation.

On the other hosts, mount the /sapmnt folder exported by the global host to a local /sapmnt folder.

This procedure enables SAPInst to read and copy files from the global host.

Refer to your system administrator for setting up and mounting NFS share.

Create and Share the Working Directory

To install the Core Server component, you need a working directory to store a large volume of charged items, chargeable items, and other output records. This working directory must be created for each Rater and shared with each Bulkloader.

Execute the following commands:

mkdir /workingDirectory

echo “/workingDirectory *(rw,sync,no_root_squash)” >> /etc/exports

/usr/sbin/exportfs –ra

/etc/init.d/nfs restart

NOTE

Open the ports to allow remote client to connect.

Configure the host’s OS for UTF-8 Encoding

All the machines hosting a component of SAP Convergent Charging must use UTF-8 encoding during the installation so that SAPInst can work properly.

On UNIX and Linux, use the following command:

export 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.

Configure OS Time Zones on each Host

All the machines hosting an SAP CC component must have the same time zone. Before installing SAP Convergent Charging 4.0, you must set the time zone on each host.

On UNIX and Linux, use the following commands:

cat /etc/sysconfig/clock (to check the time zone)

cd /usr/share/zoneinfo (to choose your time zone) ln –s /usr/share/zoneinfo/GOOD-TIME_ZONE /etc/localtime

e.g.: ln –s /usr/share/zoneinfo/US/Pacific localtime

On Windows, use the following commands:

tzutil /g to (to check the time zone)

tzutil /s <TimeZoneID> (to change the time zone)

e.g.: tzutil /s “Pacific Standard Time”

CAUTION

Once SAP Convergent Charging is installed, do not change the time zone on any host.

Set the Environment Variables SAP_IPv6_ACTIVE and NI_USEIPv6

PRELIMINARY CAUTION

Setting the SAP_IPv6_ACTIVE and NI_USEIPv6 environment variables is only relevant when preparing a host whose system has an installed IPv6 stack. Setting these environment variables on a system which only has an IPv4 stack leads to a failure of SAPInst.

To use the SAP Installer SAPInst properly, you must set the following environment variables on your operating system:

SAP_IPv6_ACTIVE, used for JCo communications

NI_USEIPv6, used for communication with the SAP Microsoft Management Console (sapmmc)

On UNIX and Linux, execute the following procedure:

Log on to the operating system using the root user

Edit the “/etc/environment” file

Add the following lines: NI_USEIPv6=1

SAP_IPv6_ACTIVE=1

Save the file

On Windows, execute the following procedure:

Open the “Control Panel” from the start menu

Click on “System”, then “Advanced system settings” to open the “System Properties” dialog

Select the “Advanced” tab, and click the “Environment Variables” button to open the dialog dedicated to the management of user and system variables

In the “System variables” section, click the “New…” button to open the “New System Variable” dialog

Enter “NI_USEIPv6” as the variable name, and “1” as the value

Click “OK” to create the new variable

Click again the “New…” button to open the “New System Variable” dialog

Enter “SAP_IPv6_ACTIVE” as the variable name, and “1” as the value

Click “OK” to create the new variable

Prepare the Installation Folders

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

Create an installation folder on each host (e.g.: mkdir dvd)

From the installation DVD or the local directory that includes a copy or a partial copy(see below how to create a partial copy: Customize the installation DVD) 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.

NOTES

Rather than copying it on every host you can share the installation folder across your network

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

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.

The tables below list the data units which are necessary for a software component of SAP Convergent Charging. You must determine the relevant of data units depending on the operating system (OS) of the hosts in the SAP CC system landscape:

Data Unit Core Server Diameter Server BART Server CT Server

CC40_IM_*** Yes Yes Yes Yes

INST_CC40_UC_*** Yes Yes Yes Yes

CC40_UC_*** Yes - - -

CC40_TOOLS_CONTENT_UC_OSIND Yes - Yes -

CC40_DIAMETER_UC_*** - Yes - -

CC40_BART_ UC_*** - - Yes -

CC40_CT_ UC_WINDOWS_ *** - - - Yes

Note that *** corresponds to the OS:

X86_64 (or X8664)

AIX_PPC64

HPUX_IA64

SOLARIS_X86_64

LINUX_X86_64

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 DATA_UNITS subdirectory of the installation DVD

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

EXAMPLE

You copy the following subdirectories and the file LABELIDX.ASC (the one you find under DATA_UNITS folder) to a local directory:

LABELIDX.ASC

CC40_IM_WINDOWS_ X86_64

INST_CC40_UC_WINDOWS_ X86_64

CC40_UC_WINDOWS_ X86_64

CC40_BART_ UC_WINDOWS_X86_64

CC40_TOOLS_CONTENT_UC_OSIND

Install Processor Drivers (WINDOWS)

Before installing any SAP CC server on Windows with SAPinst, you have to install processor drivers as described in the SAP Note 1036194.

PRELIMINARY NOTE

The Taxers instances and the Communications Taxing Server component are only supported on Microsoft Windows and Linux operating systems.

Install Additional Microsoft Libraries

The SAP JVM 32-bit is installed by SAPInst when your landscape includes a taxer instance or the CT Server component. Because these hosts are on Intel 64-bit, you have to install additional MS libraries. Please see the SAP Note 1367498 and execute the vcredist_x86.exe binary as described in the SAP Note 1375494.

Install Billsoft EZTax

Install Billsoft EZTax software if you need to manage US Telco taxes. You must install Billsoft EZTax as many times as the number of taxer instances in the Core Server plus one for the CT Server. Contact your Billsoft vendor.

Create a Central Repository for EZTax Information

For every taxer instance of the Core Server and for the CT Server systems, SAPInst needs to access to EZTax information (software files and application data). You must create a CC_EZTAX central repository containing the required files (see below). You must set the permissions of the CC_EZTAX folder so that the SAP Convergent Charging Administrator User created during the installation of the Core Server system is authorized to read it. If the permissions are not correctly set, the taxer instances may not start.

The CC_EZTAX folder must contain the following elements:

The transervdesc.txt file

The subdirectories db, jar and lib, which respectively contain:

The EZTax database files

The file eztax.jar

The EZTax library files: *.dll (MS Windows) or *.so (UNIX)

On Windows:

Location in the Billsoft EZTax Installation

Content to be Copied from Billsoft EZTax to the CC_EZTAX Repository

Location in the CC_EZTAX Repository

txt transervdesc.txt .

allfiles.zip All the files of the archive db

Java Interface eztax.jar jar

Java Interface and dll *.dll(EZTaxJava.dll,EZTax2.dll) lib

On Linux:

Location in the Billsoft EZTax Content to be Copied from Billsoft Location in the CC_EZTAX

Installation EZTax to the CC_EZTAX Repository Repository

Allfiles.zip transervdesc.txt .

allfiles.tar.gz All the files of the archive db

Linux64_eztax.java.tar eztax.jar jar

Linux64_eztax.java.tar and lib *.so(libEZTaxJava.so,libEZTax.so) lib

NOTE

You can consult the Operations Guide about the backup and restore procedures and about software maintenance procedures that apply to the CC_EZTAX central repository.

If you want to install an integrated landscape with the SAP ERP system, you have to install the SAP ERP system with SAP Convergent Invoicing (SAP CI) before installing SAP Convergent Charging.

Create a User for SAP CC

The SAP CC Core Server system calls RFC procedures by using the SAP JCo. As a prerequisite, you have to create a user for the SAP Convergent Charging system in the SAP ERP/FI-CA system. This user must have the following attributes:

User Type "C Communications Data"

Profile with authorization objects: F_KKBIXBIT, F_KKBIXCON, S_TABU_DIS, and S_RFC

NOTE

You can consult the Security Guide for more information about the required SAP users in your system landscape. Refer to the User Management section in User Administration and Authentication.

Create an RFC Destination (CT SERVER)

The CT Server is a JCo server and implements functions that are called up by an ABAP Backend. It is registered via the SAP Gateway and waits for inbound RFC calls.

The CT Server registers itself under a program ID to an SAP gateway (not for a specific SAP system). If an RFC call is passed on from any SAP system to this SAP gateway with the option Connection with a registered program (with the same program ID), the connection takes place with the CT Server.

Once an RFC function has been executed, the CT Server waits for further RFC calls from the same or other SAP systems.

If an RFC connection is interrupted or terminated, the CT Server automatically registers itself again on the same SAP gateway under the same program ID.

Procedure

In your SAP ERP system, you must:

Use the transaction SM59 to define an RFC destination with connection type T (TCP/IP connection) in the SAP system

Choose the registration mode (Registered server program option under the Technical settings tab page) for this destination

The destination contains the information about the SAP gateway and the registered CT Server (RFC server program) required during CT Server installation; See page [23]

Storage of Consumption Data in SAP CI

The installer proposes options related to the integration of SAP CC with SAP CI. You have to determine if the storage of consumption data is done in SAP CI on your platform.

For more information on the storage of consumption data in SAP Convergent Invoicing, consult the SAP Convergent Charging Library or Application Help.

For more information on the options in SAPInst, refer to the installation of servers (SAP Convergent Charging Integration Scenario).

NOTE

These options are available only for an installation from scratch. The functional scope of a SAP CC platform already installed is not changed.

If you install SAP Convergent Charging with the storage of consumption data in SAP CI, SAP CI manages the rerating function (enabled by default).

NOTE

If you want to move to a landscape where SAP CI manages the rerating function instead of BART Server, you must upgrade your platform. For more information on the migration procedure, refer to SAP CC Upgrade Guide.

CA Wily Introscope Enterprise Manager is a third-party monitoring application which is licensed for SAP and its customers. If you want to monitor your platform with Wily Introscope, you must install it before installing an SAP CC server system by running SAPInst.

To get information about the installation of CA Wily Introscope for SAP Convergent Charging, refer to the SAP Note 1453216.

SAPInst creates a user named sapadm when you install the Core Server component for the first time on the Global Host. It also creates another user named <SID>adm where <SID> corresponds to the SID of your SAP system for each SAP system you install (e.g.: cc0adm).

On UNIX and Linux

SAPInst creates a new group named sapsys. The users created by SAPInst are members of sapsys.

On Windows

SAPInst creates a new group named SAP_LocalAdmin, SAP_SAP_GlobalAdmin, SAP_SAP_LocalAdmin. The users created by SAPInst are members of the newly created groups.

NOTE

If you install a multi-host landscape, it is highly recommended to create domain users. To create domain users, the account you use for launching SAPInst must have the permissions to create domain users. If not, you must create the users before to launch the installation.

SAP Convergent Charging uses the following communication channels for internal and external communications:

HTTP, used by the Web Services and HCI technical interfaces for external communications

TCP/IP, used for internal communications between the different instances of the Core Server component

You can secure these communication channels during the installation with SAPInst (see the SAP Convergent Charging Security steps of the installation).

Get an OpenBlox License Key (Diameter Server)

Before installing the Diameter Server component, you have to ask to your SAP Consultant for a valid license key for OpenBlox.

Determine the Securing Mode

Read the Application Help documentation in order to determine which securing mode (oneway Vs. dual) has to be used for your platform.

The securing procedure relies on the use of X.509 V3 digital certificates (DER encoded) and their associated private keys (1024, 2048 or 4096 bits encrypted). The certificates and the associated private keys can be stored:

In a common keystore file using a PKCS#12 format

In separate files, using the PKCS#8 format for files containing the private keys

As a prerequisite, you have to create:

One certificate (with the associated private key and keystore) for securing the BART Server

One certificate (with the associated private key and keystore) for securing the Diameter Server

Two certificates (with the associated private keys and keystores) for securing both the internal and external communication channels of the Core Server

NOTE

You can use the same certificate for securing the internal and the external channels of the Core Server.

The securing procedure relies on certificates and private keys, which are used to secure the different communication channels used by SAP CC components. The following steps give you the possibility to create:

A private key

A X.509 v3 digital certificate, named “certificate.der ” and DER encoded

A keystore stored in a PKCS#12 archive file named “keystore.p12” and containing the created private certificate and private key

You have to repeat this procedure for every certificate (with the associated private key and keystore) required to secure your landscape.

Generating a private key

To create a private key named “key.pem”, type the following command:

openssl genrsa -out key.pem <key_size>

NOTE

The “key_size” parameter represents the size (in bits) of the private key you want to generate. Possible values are: 1024, 2048 or 4096.

Creating a X.509 v3 digital certificate

The creation of a X.509 v3 digital certificate is based upon a configuration file taken into account by the openssl command. This configuration file contains a property named “subjectAltName”, which gives the possibility to provide an exhaustive list of hostnames and/or IP addresses (IPv4 or IPv6) used to identify the host to trust and connect to. This property uses the following format:

IP:{$localHostAddress},DNS:{$localHostName},DNS:{$localCanonicalHostName}

You can use a generic domain name (e.g. DNS:*.mydomain.com) in order to easily add possible new hosts, but we highly recommend you to specify a list of IP addresses and/or hostnames (e.g. IP:192.168.0.1, IP: fe80::192.168.0.2, DNS:host1).

Create a configuration file named “openssl.config”,and use the following text content (adapting the “SubjectAltName” property to your own configuration):

[ req ]

distinguished_name = req_distinguished_name

x509_extensions = v3_req

[ req_distinguished_name ]

[ v3_req ]

subjectAltName = DNS:*.mydomain.com

CAUTION

When a condensed IPv6 address is used in the subjectAltName property, the openSSL tool

automatically records the complete address. This complete address corresponds to the address which must be provided when connecting to a given service secured with this certificate

In addition, we also recommend you to use a pretty name when filling the common name, in order to distinguish each generated certificate. This common name contains information related to the trusting authority, i.e. the host to trust and connect to.

To generate the “certificate.pem” certificate, type the following command:

openssl req -new -x509 -key key.pem -out certificate.pem -days 365 -config

openssl.config -subj "/CN=<pretty_name>"

Creating the keystore used to store the certificate and its private key

To create a keystore named “keystore.p12”, secured with a passphrase and containing the previously created private key and certificate, type the following command:

openssl pkcs12 -export -in certificate.pem -inkey key.pem -out keystore.p12

-passout pass:<keystore_passphrase>

Deleting the private key

For security reasons, delete the previously created private key using the following command:

del key.pem

Modifying the certificate’s format from PEM to DER

To convert the certificate from a PEM format to a DER one, type the following command:

openssl x509 -in certificate.pem -out certificate.der -outform der

Deleting the PEM certificate

For security reasons, delete the useless PEM certificate using the following command:

del certificate.pem

NOTE

You can apply the security after SAP CC installation but always before starting the production environment. See the section “Common procedure for securing the SAP CC components" of the SAP Convergent Charging Application Help documentation.

Depending on your landscape, you must install one database system (the Core database) up to three databases (the Core database, the BART database and the IEC database). Install one of the following Database Management System on each database host:

Sybase ASE

Oracle

Microsoft SQL Server

IBM DB2

NOTE

For more information about the installation of Sybase ASE, see the following page on SAP Community Network http://scn.sap.com/community/ase and the Sybase Web Site http://www.sybase.com/products/databasemanagement/adaptiveserverenterprise.

For more information about the installation of Oracle, see the following pages on SAP Community Network http://scn.sap.com/community/oracle and http://scn.sap.com/docs/DOC-7888.

For more information on the installation of Microsoft SQL Server, see the following page on SAP Community Network http://scn.sap.com/docs/DOC-8286

For more information on the installation of IBM DB2, see the SAP Note 1363170 (Windows) and the following page on SAP Community Network http://scn.sap.com/docs/DOC-7812.

RECOMMENDATION

You can either install all the databases on the same database instance using different logins or have one database instance per database.

Nevertheless, it is highly recommended to install a database instance dedicated to the BART Server component to facilitate database administration and improve performances. Using the Core database instance for the BART Server component can prevent from tuning the database according to CDR volumes.

Install Sybase ASE Database

To install Sybase ASE, we recommend you to read the installation documentation of Sybase ASE available at http://infocenter.sybase.com. This section documents the specific installation requirements and configuration of ASE for SAP Convergent Charging.

To use some SAP Convergent Charging in conjunction with Sybase Adaptive Server, you must have a license for the following options of Sybase ASE:

To use partitioning with the Core Server or BART Server components, you must have a Partitioning License for Sybase ASE

To use secure connections between SAP Convergent Charging and Sybase ASE, you must have a Security License for Sybase ASE

To use high availability with SAP Convergent Charging, you must have a High-Availability License for Sybase ASE

CAUTION

You must install a Licensed Copy of Sybase Adaptive Enterprise Suite. SAP Convergent Charging does not work with a Free Developer Edition or Small Business Edition of Sybase ASE Suite.

The first step of the installation procedure consists in installing the Sybase Adaptive Server binaries, using the “Typical” Install Set mode. After the installation of these binaries, you will have to configure the new servers, including a possible Sybase Control Center (which is used to monitor the Adaptive Server).

NOTE

If a Sybase Control Center is already installed in your landscape, you can skip this configuration step and connect your Sybase Adaptive Server to this Control Center at a later time.

To configure the new Adaptive Server, it is necessary to provide the following information:

System Administrator’s Password: Specify a password which is compliant with your password management policy

Confirm System Administrator’s Password: Confirm the above specified password

Application Type: Mixed (OLTP/DSS), which corresponds to the default value of this option

Page Size: 8k, Note that the page size required by SAP Convergent Charging is different from the default page size of 4k. As this value cannot be modified after the installation of Sybase ASE, it is thus important to set explicitly the page size to 8k. This modification of the default value leads to a warning message informing that the newly specified page size must be similar between databases used for import purposes.

Default Character Set: utf-8 : Unicode 3.1 for UTF-8 Character Set

Default Sort Order: altdict : Alternate (lower-case first) dictionary ordering, which corresponds to the default value of this option

If a Sybase Control Center must be installed, the following information must be provided:

SCC agent administrator password: Specify a password which is compliant with your password management policy

Confirm SCC agent administrator password: Confirm the above specified password

ADDITIONAL NOTE

To configure Sybase ASE, you can also use the isql tool:

Interactively to execute dedicated commands

To execute scripts containing a list of commands

When using the interactive mode, you have to:

Execute the isql tool to authenticate using a username and a password (which must be the same than the information provided during the installation of Sybase ASE):

isql –U<username> –P<password>

Type every command which must be executed, followed by a go statement: <command_to_execute>

go

When using the script mode, you have to:

Create a text file containing the list of commands which must be executed : <command_to_execute>

go

<command_to_execute>

go

and so on…

Execute the isql tool to authenticate and specify the above created file considered as an input file to execute:

isql –U<username> –P<password> -i<input_file>

Whatever the execution mode, you exit the isql tool by using the following command:

quit

For further information about the isql tool, refer to its dedicated documentation.

Configuring Sybase ASE Server

The correct behavior of SAP Convergent Charging on Sybase ASE depends on the correct configuration of the Sybase ASE Server. After the installation of the Sybase ASE Server, it is thus very important to configure the following parameters:

Parameter Required value

number of open objects 10000

number of open indexes 2000

max network packet size 16384

default network packet size 16384

optimization goal allrows_rmix

disable varbinary truncation 1

number of user connections 200

number of locks 1000000

deadlock checking period 800

lock hashtable size 16384

row lock promotion HWM 214748364

row lock promotion LWM 214748364

SQL batch capture 1

NOTE

To automatically set the required parameters to their adequate values, it is possible to execute the following script using the isql tool:

Script sp_configure "number of open objects", 10000

go

sp_configure "number of open indexes", 2000

go

sp_configure "max network packet size", 16384

go

sp_configure "default network packet size", 16384

go

sp_configure "optimization goal", 0, 'allrows_mix'

go

sp_configure "disable varbinary truncation", 1

go

sp_configure "number of user connections", 200

go

sp_configure "number of locks", 1000000

go

sp_configure "deadlock checking period", 800

go

sp_configure "lock hashtable size", 16384

go

sp_configure "row lock promotion HWM", 214748364

go

sp_configure "row lock promotion LWM", 214748364

go

sp_configure "SQL batch capture", 1

go

If you want to use partitioning with the Core Server or BART Server components, you must activate semantic partitioning on Sybase ASE by setting the following parameters:

Parameter Required value

enable semantic partitioning 1

number of open partitions 55000

NOTE

To automatically set the required parameters to their adequate values, it is possible to execute the following script using the isql tool:

Script sp_configure "enable semantic partitioning", 1

go

sp_configure "number of open partitions", 55000

go

If you want to use a secured connection between SAP Convergent Charging and Sybase ASE, you must activate SSL on Sybase ASE by setting the following configuration parameter:

Parameter Required value

enable SSL 1

NOTE

To automatically set the required parameters to their adequate values, it is possible to execute the following command using the isql tool:

sp_configure "enable SSL", 1

go

Create the Devices

Before creating database for Sybase ASE, it is required to create at least two devices per database, one for the data and another one for the logs. To create a device, you can execute the following command using the isql tool:

disk init name=”<data device name>”, physname=”<path to data physical

device>”, size=”<data size>”

go

disk init name=”<log device name>”, physname=”<path to log physical

device>”, size=”<log size>”

go

Create the Database

To create a database for SAP Convergent Charging in Sybase ASE, use the following command in the isql tool:

create database <dbname> on <data device>=”<data size>” log on <log

device>=”<log size>”

go

NOTES

<data size> and <log size> correspond to the amount of space to allocate for the database. These sizes are made up with a quantity and a unit. The following units specifiers are supported:

k or K (kilobytes)

m or M (megabytes)

g or G (gigabytes)

t or T (terabytes)

Example: size=”1024M”

It is recommended to use the following minimum values for the <data size> and <log size> parameters:

“8192M” for the <data size> parameter

“256M” for the <log size> parameter

Create a Login

You must create a login for each SAP CC database that you have to install. To create a login, use the following command in the isql tool:

create login <dblogin> with password <dbpwd>

go

To grant the given login with all the rights for the created databases, you need to create an alias for this login as database owner for each database. This can be done using the isql tool, for each database and login, using the following commands:

use <db name>

go

sp_addalias <dblogin>,dbo

go

IMPORTANT NOTE

For a production system, it is recommended to backup the databases regularly. Refer to SAP Notes 1585981 and 1588316.

Install SQL Server Management Studio

The database preparation is performed with the SQL Server Management Studio application. See http://www.microsoft.com/ to download and install this application.

Set the Authentication Mode

In SQL Server Management Studio, right-click the appropriate server and select Server Properties. In the Security tab, select the option SQL Server and Windows Authentication.

Create a Login

You must create a SQL Server login for each SAP CC database that you have to install.

NOTE

You need to know the database administrator login and password for this part of the installation.

Use the procedure below to create a login for each database:

Connect to SQL Server as Database Administrator

In SQL Server Management Studio, open Object Explorer and expand the folder corresponding to the appropriate server

Right-click the Security folder, point to New and click Login

On the General tab, enter the new login

Select the SQL Server Authentication option

Enter and confirm the password for this login

Select the policy options to be applied to the new login. Note that Enforce password policy is the most secure option

Ensure that the Default Database is the master one

Click OK

NOTES

This login is used by SAP CC to connect to the corresponding database

If you want to use the Windows authentication for SQL Server, apply the procedure described in the SAP Note 1559324 after you have finished SAP CC installation

Give the Appropriate Roles

On the Server Roles tab, check the following options:

dbcreator

diskadmin

serveradmin

and then click OK.

Test the New Login

Right-click the server you want to connect to, choose the SQL Server Authentication and click Connect.

Create the Database

To create the Core database:

Connect to the server with the appropriate login (see previous section).

Right-click on the Databases item of the server and select New Database...

In the Options tab, choose the appropriate language and make the database case-sensitive and compatible with ASCI Unicode by selecting the value of the collation parameter. Collation defines the way strings are stored, sorted and compared in SQL Server. For SAP Convergent Charging installation, case-sensitive databases are required (e.g.: choose the Japanese_Unicode_CS_AS value for Japanese) In the Options tab, ensure that the compatibility level is SQL Server 2008 (100)

In the General tab, enter the name of the database

Click Ok. The database is created

NOTE

In production environment we recommend you to choose the “Full” option for the recovery model in the option tab.

Apply the same procedure to create the BART database.

Oracle Installation

SAP Convergent Charging is a pure Java application. Both the application and the client APIs use the default UTF-8 encoding provided by Java. When installing Oracle, you must choose the UTF-8 encoding.

Initialization

The initialization parameters are located in the spfile/init.ora file of your installation. We recommend the following specific values for several initialization parameters of your Oracle instance:

The bind peaking feature of Oracle is incompatible with SAP Convergent Charging. Set the _optim_peek_user_binds parameter to FALSE for each database to disable the bind peeking feature

Increase the maximum number of processes and sessions by setting the processes and sessions parameters to 300 multiplied by the number of databases on the same Oracle instance. For example, if you install the Core database and the BART database on the same instance, set these parameters to 600

Follow the procedure below to correctly set these parameters and restart the server.

Procedure sqlplus / as sysdba

SQL> alter system set “_optim_peek_user_binds”=false

scope=spfile;

SQL> alter system set processes=300 scope=spfile;

SQL> alter system set sessions=300 scope=spfile;

SQL> shutdown immediate

SQL> startup

CAUTION

The value of the parameters parallel_automatic_tuning and parallel_max_servers must not be modified.

Create a User Account

Create up to three user accounts, as needed: one for the Core database, one for the BART database and one for the IEC database. For creating the accounts, execute the following procedure by replacing <dbuser> by the login and <dbpwd> by the password:

Procedure sqlplus / as sysdba

SQL> create user <dbuser> identified by <dbpwd>;

SQL> grant CONNECT, RESOURCE TO <dbuser>;

Grant the User

Grant the new user with the following roles and privileges, using the following procedure:

Procedure SQL> grant EXECUTE_CATALOG_ROLE to <dbuser>;

SQL> grant EXP_FULL_DATABASE, IMP_FULL_DATABASE to <dbuser>;

SQL> grant CREATE PROCEDURE to <dbuser>;

SQL> grant CREATE SESSION to <dbuser>;

SQL> grant CREATE TABLESPACE, DROP TABLESPACE to <dbuser>;

SQL> grant ALTER TABLESPACE to <dbuser>;

SQL> grant CREATE ANY DIRECTORY to <dbuser>;

SQL> grant DROP ANY DIRECTORY to <dbuser>;

SQL> grant EXECUTE ON dbms_lock TO <dbuser>;

Start the DB2 Command Prompt

The database preparation is performed with the SQLDB2 Command Prompt. To start this application on windows:

Click on the Start Windows button and then select Run

Enter the db2cmd command

To start this application on UNIX or Linux systems, run the db2profile script of the instance owner.

Create the Database

To create the Core database or the BART database, use the following procedure:

In the command prompt enter db2

Enter the command line: create database <database_name> pagesize 8192, where <database_name> is the name of the database

Then increase the number of primary log files to 50 using the following command: update db cfg for <database_name> using LOGPRIMARY 50

Create a User

The following procedures describe how to create a user for your database. Create two users if needed: one for the Core database and one for the BART database. Then use the created users in order to connect to these databases.

Windows procedure

The users are Windows users: they are created on Windows and then added to the DB2Users group. To create a user, execute the following procedure:

Click on Start Windows button, and then select Control Panel

Go into the folder User Accounts and then again User Accounts

Open the Manage User Accounts window

In the Advanced tab, click on the Advanced button

Right click Users (in left part of the window) and select New User….

Enter the user name and the password for the database user

Click Create and close the New User dialog

Click Users (in left part of the window) and double-click on the previously created user to open it. The Properties window opens

Go into the Member Of tab and click Add

In the Enter the object names to select text area, type db2users

Click the Check Names button: the group name must automatically be replaced by the right group

Procedure for other Operating Systems

Execute the following procedure to create a user:

Create a new user using the useradd command

Update the .profile file in the new user’s home. See your database documentation for more information

Grant the User

Type the following command lines to grant the user with the administration rights on the corresponding database:

Connect to the database, using the connect to <database_name> command

To grant the user, type: grant dbadm on database to <database_user>, where <database_name> corresponds to the name of the database and <database_user> to the user for this database

Tablespaces, filegroups, and segments share the same concept: they represent reserved spaces on one or multiple disks where the database system stores objects like tables and indexes:

The tablespace concept is present in Oracle and IBM DB2 databases

The filegroup concept is present in Microsoft SQL Server technology

The segment concept is present in Sybase ASE technology

For each tablespace, filegroup, or segment, you can define a maximum size, an initial size and other options like the minimum size of each sub element into a tablespace, a filegroup or a segment.

SAP Convergent Charging uses specific tablespaces, filegroups, and segments to store objects. Before installing SAP CC, you have to create the tablespaces, filegroups, or segments which are required for the Core and BART databases.

Create Tablespaces (Oracle and DB2)

According to the edition (Standard or Enterprise) of the Core database, create the tablespaces listed in the table below, using the recommended minimal sizes:

Tablespace Description Minimal Size (Mo)

Standard Enterprise

CATALOG_DATA This tablespace contains the tables used to store the objects belonging to the catalog. The operations audit is also stored in this tablespace.

180 180

CATALOG_INDX This tablespace contains the indexes used for the objects belonging to the catalog. The operations audit is also concerned.

220 220

Tablespace Description Minimal Size (Mo)

Standard Enterprise

SUBSCRIBER_DATA This tablespace is used to store the tables containing objects belonging to provider contracts and subscriptions.

100 20000

SUBSCRIBER_INDX This tablespace contains the indexes used for the objects belonging to provider contracts and subscriptions.

200 20000

ACCESS_DATA This tablespace contains the tables used to store the chronologies of the mappings between technical identifiers and the corresponding contract or subscription.

10 1000

ACCESS_INDX This tablespace contains the indexes used for the chronologies of the mappings between technical identifiers and the corresponding contract or subscription.

20 250

PRERATING_DATA This tablespace contains the tables used to store prerating data.

10 2000

PRERATING_INDX This tablespace contains the indexes used for prerating data.

10 3000

COUNTER_DATA This tablespace contains the table used to store the counters declared in subscriptions and provider contracts.

20 1000

COUNTER_INDX This tablespace contains the indexes used for counters.

10 10

C_SNAPSHOT_DATA This tablespace contains the table used to store counter values for subscriptions and provider contracts.

20 1000

C_SNAPSHOT_INDX This tablespace contains the indexes used for counter values.

10 10

Oracle: SESSION_RATING_DATA

DB2: SESSION_DATA

This tablespace contains the tables used to store session-based events and charging session histories for failover purposes.

1500 7000

Oracle: SESSION_RATING_INDX

DB2: SESSION_INDX

This tablespace contains the indexes used for session-based events and charging session histories for failover purposes.

500 500

OBJECT_CHANGE_DATA This tablespace contains the tables used to store data related to the object change log of detailed audit.

100 2000

OBJECT_CHANGE_INDX This tablespace contains the indexes used for object change log of detailed audit.

100 1000

ALLOWANCE_DATA This tablespace contains the table used to store allowances.

20 1500

Tablespace Description Minimal Size (Mo)

Standard Enterprise

ALLOWANCE_INDX This tablespace contains the indexes used for allowances.

15 500

According to the edition (Standard or Enterprise) of the BART database, create the tablespaces listed in the table below, using the recommended minimal sizes:

Tablespace Description Minimal Size (Mo)

Standard Enterprise

BART_DATA This tablespace is used to store the tables containing BART data other than CDRs.

50 50

BART_INDX This tablespace contains the indexes used for BART data other than CDRs.

10 10

CDR_DATA This tablespace contains the tables used to store data related to the CDRs of BART.

100 2000

CDR_INDX This tablespace contains the indexes used for data related to the CDRs of BART.

600 10000

EXAMPLE

Use one of the following command lines to create the CATALOG_DATA tablespace:

Oracle Procedure

SQL> CREATE BIGFILE TABLESPACE CATALOG_DATA DATAFILE

<file_location> SIZE <tablespace_size>;

Where:

<file_location> is the name and the location of the file where data related to the tablespace CATALOG_DATA will be stored. If the location is not specified, a default file will be used

<tablespace_size> is the size of the tablespace. With your DBA, determine the appropriate size for your tablespaces and consider using the AUTO_EXTEND option

DB2 Procedure

DB2 CREATE TABLESPACE CATALOG_DATA MANAGED BY DATABASE USING

(FILE '<file_location>' <tablespace_size>)

Where:

<file_location> is the name and the location of the file where data related to the tablespace CATALOG_DATA will be stored

<tablespace_size> is the size of the tablespace. With your DBA, determine the appropriate size for your tablespaces

Create Filegroups and Associated Database Files (SQL Server)

List of filegroups to be created

You have to create the following filegroups for the Core database:

Filegroup Description

CATALOG_DATA This filegroup contains the tables used to store the objects belonging to the catalog. The operations audit is also stored in this filegroup.

CATALOG_INDX This filegroup contains the indexes used for the objects belonging to the catalog. The operations audit is also concerned.

SUBSCRIBER_DATA This filegroup is used to store the tables containing objects belonging to provider contracts and subscriptions.

SUBSCRIBER_INDX This filegroup contains the indexes used for the objects belonging to provider contracts and subscriptions.

ACCESS_DATA This filegroup contains the tables used to store the chronologies of the mappings between technical identifiers and the corresponding contract or subscription.

ACCESS_INDX This filegroup contains the indexes used for the chronologies of the mappings between technical identifiers and the corresponding contract or subscription.

PRERATING_DATA This filegroup contains the tables used to store prerating data.

PRERATING_INDX This filegroup contains the indexes used for prerating data.

COUNTER_DATA This filegroup contains the table used to store the counters declared in subscriptions and provider contracts.

COUNTER_INDX This filegroup contains the indexes used for counters.

C_SNAPSHOT_DATA This filegroup contains the table used to store counter values for subscriptions and provider contracts.

C_SNAPSHOT_INDX This filegroup contains the indexes used for counter values.

SESSION_RATING_DATA

This filegroup contains the tables used to store session-based events and charging session histories for failover purposes.

SESSION_RATING_INDX This filegroup contains the indexes used for session-based events and charging session histories for failover purposes.

OBJECT_CHANGE_DATA This filegroup contains the tables used to store data related to the object change log of detailed audit.

OBJECT_CHANGE_INDX This filegroup contains the indexes used for object change log of detailed audit.

ALLOWANCE_DATA This filegroup contains the table used to store allowances.

ALLOWANCE_INDX This filegroup contains the indexes used for allowances.

Create the following filegroups for the BART database:

Tablespace Description

BART_DATA This filegroup contains the tables used to store data related to the CDRs of BART.

BART_INDX This filegroup contains the indexes used for data related to the CDRs of BART.

CDR_DATA This filegroup is used to store the tables containing BART data other than CDRs.

Tablespace Description

CDR_INDX This filegroup contains the indexes used for BART data other than CDRs.

Procedure for creating filegroups and database files

For each filegroup, you have to create a database file to make the filegroup ready to use.

To create the filegroups and their associated database file for the Core database, use the following procedure for each filegroup:

Right-click the Core Database item and select Properties

In the Filegroups tab, click the Add button to add a filegroup

Enter the name of the filegroup (see the previous paragraph) and click Ok

In the File tab, click the Add button to add a file

Enter the name of the file (choose a name related to the name of the filegroup, possibly the same name). Select the corresponding filegroup in the filegroup column and click Ok

Apply the same procedure to create the filegroups and the database files for the BART database.

Create Segments (Sybase ASE)

List of segments to be created

The following segments must be created for the Core database:

Segment Description

CATALOG_DATA This segment contains the tables used to store the objects belonging to the catalog. The operations audit is also stored in this segment

CATALOG_INDX This segment contains the indexes used for the objects belonging to the catalog. The operations audit is also concerned

SUBSCRIBER_DATA This segment is used to store the tables containing objects belonging to provider contracts and subscriptions

SUBSCRIBER_INDX This segment contains the indexes used for the objects belonging to provider contracts and subscriptions

ACCESS_DATA This segment contains the tables used to store the chronologies of the mappings between technical identifiers and the corresponding contract or subscription

ACCESS_INDX This segment contains the indexes used for the chronologies of the mappings between technical identifiers and the corresponding contract or subscription

PRERATING_DATA This segment contains the tables used to store prerating data

PRERATING_INDX This segment contains the indexes used for prerating data

COUNTER_DATA This segment contains the table used to store the counters declared in subscriptions and provider contracts

COUNTER_INDX This segment contains the indexes used for counters

Segment Description

C_SNAPSHOT_DATA This segment contains the table used to store counter values for subscriptions and provider contracts

C_SNAPSHOT_INDX This segment contains the indexes used for counter values

SESSION_RATING_DATA This segment contains the tables used to store session-based events and charging session histories for failover purposes

SESSION_RATING_INDX This segment contains the indexes used for session-based events and charging session histories for failover purposes

OBJECT_CHANGE_DATA This segment contains the tables used to store data related to the object change log of detailed audit

OBJECT_CHANGE_INDX This segment contains the indexes used for object change log of detailed audit

ALLOWANCE_DATA This segment contains the table used to store allowances

ALLOWANCE_INDX This segment contains the indexes used for allowances

The following segments must be created for the BART database:

Segment Description

BART_DATA This segment contains the tables used to store BART data other than CDRs

BART_INDX This segment contains the indexes used for BART data other than CDRs

CDR_DATA This segment contains the tables used to store data related to the CDRs of BART

CDR_INDX This segment contains the indexes used for data related to the CDRs of BART

Procedure for creating segments

To create a segment, you can execute the following command using the isql tool:

exec sp_addsegment “<segment name>”, “<db name>”, “<device name>”

go

Where:

<segment name> corresponds to the name of the segment to create

<db name> corresponds to the name of the database where the segment must be created

<device name> corresponds to the name of the device where the segment must be located

Run SAPInst

Run SAPInst on the Host

To run SAPInst, execute the following procedure:

Go to the CC40_IM_* data unit where * corresponds to your OS. See page [22] for more information about data units

For UNIX or Linux, use the following command to set the execution rights on the sapinst program: >chmod +x sapinst

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

NOTE

To install instances of the Core Server system on several hosts, you must run SAPInst on each host machine. The first host you install is called Global Host.

Run SAPInst Remotely

If you want to perform a remote installation, you have to start SAPInst on the remote host and SAPInst GUI on the local host.

To run SAPInst on the remote host, use the following command:

sapinst -nogui JCE_POLICY_ZIP=<path_of_JCE_policy_archive>

To run the SAPInst GUI on the local host, use the following command:

sapinstgui -host <name_of_remote_host>

NOTES

See the SAP Note 1238121 for more information

Do not forget to open the default port 21212 to the remote host to allow communications.

The installation is made up with five steps:

1. Choose Option

2. Define Parameters

3. Summary

4. Execute

5. Completed

Choose Option

Click SAP Convergent Charging Install Standard System Installation and choose the component of SAP CC that you want to install: the Core Server, the BART Server, the CT Server or the Diameter Server.

For the Core Server, click SAP Convergent Charging Install Standard System Installation

Core Server - First Step if you install the global host. Click SAP Convergent Charging Install

Standard System Installation Core Server - Add Instances if you want to add instances on this host or on another one.

NOTES

The Core Server and the Core Tool must be installed before the BART Server and the Diameter Server. Moreover, the dispatcher instances of the Core Server must be running (see Starting and Stopping the Servers). If you install the BART Server first, the installation will fail because a connection to the Core Server is needed. If you install the Diameter Server first, the installation will fail for the same reason

The CT Server can be installed at any time. No connection to the Core Server is required

SAPInst prompts for input parameters during the Define Parameters step of the installation. This section describes the parameters which are common to all installations. To know which parameters are specific to a server, see the following sections.

Run SAPInst for the Core Server - First Step

Media browser (optional)

It may happen that you have to define the location of the installation folder (if the content of the LABELIDX file is not sufficient).

Installation Mode You can install your SAP CC system according to the following modes:

If you select the Typical mode, the installation is performed with default settings. You only have to respond to a small selection of prompts

If you choose Custom mode, you are prompted for all the parameters

Choose the Custom mode in case you are installing SAP CC on the global host.

NOTE

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

SAP System ID You have to specify the SAP System ID or the SAP Profile Directory (if you add a host). Refer to the section Choose your SAP System IDs

or read SAPInst to have more information about how to choose your SAP System Identifier (SID).

If you install a new SAP system, enter the SID for this system. If you install the instances of this system on more than one host, make sure that you assign the same SID to all these instances. The identifier for the database instance can be

different from the SID.

If you add instances to an existing SAP system - for example, if you install additional application server instance(s) for an existing SAP system - enter the location of the profile directory of the existing SAP system.

If you uninstall an SAP system, enter the location of the profile directory of the SAP system you want to uninstall.

(WINDOWS ONLY) When installing a new SAP system or adding instances to an existing SAP system, select the destination drive. The system will be installed in the directory <DESTINATION_DRIVE>:\usr\sap\<SID>\. This option is not available if there is at least one SAP system already installed on the host.

NOTE

The location of the SAP Profile Folder of your SAP CC system is one of the following folders:

Windows: \\<SAP_GLOBAL_HOST>\sapmnt\<SID>\SYS\profile\

UNIX, Linux, and i5/OS: /sapmnt/<SID>/profile/

Existing parameters will be retrieved from the SAP system profile directory.

CAUTION

Choose different SAP System IDs for the Core Server, BART Server, Diameter Server and CT Server components. An SAP System ID must be unique on the network to avoid mixing up different SAP systems. When installing twice the same component, you must set different SAP System IDs for the two systems for making them work properly.

Master Password Choose the Master Password. This password will be used for all the OS users created during the installation. Read SAPInst Help (type F1 in SAPInst) to have more information about the master password, restrictions and dependencies.

Operating System Users

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

Windows Domain

(WINDOWS ONLY) Choose the Windows domain in which you want to create the SAP system accounts. Read SAPInst Help (type F1 in SAPInst) for more information.

RECOMMENDATIONS

If you want your SAP system to run on one host, you can choose Local Domain (local installation)

If you want your SAP system to be distributed on several hosts, we strongly recommend that you perform a domain installation to avoid authorization

problems

For more information about Windows domains, see the Windows documentation

JCE Unlimited Strength Jurisdiction Policy Files

Give the path to the JCE files. See page [15] for more information about JCE jurisdiction policy files.

License Tick the Generate a Temporary License box. See page [69] for installing a permanent license after you finish installing the system.

Database Type Indicate your RDBMS: MS SQL Server, Oracle, Oracle RAC, DB2, DB2 pureScale, or Sybase ASE.

Database Connection

Enter the connection parameters for the Core database. These parameters are defined during the database preparation (see page [29]).

The exact title and content of this dialog depend on the database type chosen in the previous step.

Tick the box Use Partitioning if you want to partition your database.

Tablespaces / Filegroups / Segments

Specify in which tablespaces, filegroups, or segments the database tables and indexes will be created.

Possible values are restricted to the list of tablespaces, filegroups or segments which are available in the Core Database. Refer to the Creating Tablespaces, Filegroups or Segments section for creating tablespaces, filegroups, or segments.

Working Directory

Choose the Working Directory for the SAP CC Core Server system. . Please refer to the Create and Share the Working Directory section and the SAPInst dialog for additional information.

Wily Introscope Java Agent

Give the host and the port of the CA Wily Introscope Enterprise Manager if needed. See page [25] for more information about installing the CA Wily Introscope.

Untick the box Use monitoring with Wily Introscope if you do not want to use Wily Introscope to monitor the server.

System Landscape Directory

Enter the URL, login and password used to submit the payload to the System Landscape Directory.

Untick the box Configure System Landscape Directory if you do not want to

configure the connection to SLD.

SAP Convergent Charging Security

Choose if you want to enable encryption of all the communication channels of the Core Server component.

If the encryption is enabled, choose the import format for the X.509 v3 certificates and their associated private keys used to encrypt the communication channels:

A common keystore file using the PKCS#12 format

2 separate files, using the PKCS#8 format for the file containing the private key

Check that the prerequisite Securing the Communication Channelsis fulfilled.

Import Key Pair From PKCS#12 File

This dialog is displayed only if you chose to encrypt communication channels and to import the key pair from a common PKCS#12 keystore file.

Enter the location of the PKCS#12 keystore file and its passphrase.

This dialog is displayed twice:

A first time when configuring the key pair used for the encryption of the external channels of the Packets over TCP/IP, SOAP over HTTP and XML over HTTP communication channels

A second time when configuring the key pair used for the encryption of the internal channel of the Packets over TCP/IP communication channel

Import Key Pair From Separate Files

This dialog is displayed only if you chose to encrypt communication channels and to import the key pair from 2 separate files.

Enter the location of the PKCS#8 file containing the private key and the location of the file containing the X.509 v3 certificate.

This dialog is displayed twice:

A first time when configuring the key pair used for the encryption of the external channels of the Packets over TCP/IP, SOAP over HTTP and XML over HTTP communication channels

A second time when configuring the key pair used for the encryption of the internal channel of the Packets over TCP/IP communication channel

SAP Convergent Charging Administrator User

Provide and confirm the password of the super administrator and emergency user of the SAP CC system. The temporary user is named admin. The password must contain at least one uppercase letter, one lowercase letter and one digit. It cannot contain the text admin and its length must be greater than 5 characters.

SAP Convergent Charging Tax

Choose your tax framework(s): VAT, EZTax, both or none.

The EZTax framework is dedicated to US Telco taxes computation. It is available on Windows platforms only. If you choose EZTax, enter the location of the EZTax

installation folder or the path to the EZTax directory. See page [23] for more details about the EZTax directory.

SAP Convergent Charging Integration Scenario

Choose the integration scenario of SAP Convergent Charging:

Stand-alone

Billing and Invoicing in SAP Convergent Invoicing

Billing, Invoicing, and Storage of Consumption Data in SAP Convergent Invoicing

The first option means that you do not work with billable items and consumption items.

The second option means that you work with billable items only.

The third option means that you work with both billable items and consumption items.

JCo Connections Configuration

This dialog is only displayed if you chose an integration scenario with SAP Convergent Invoicing in the previous step.

Enter the JCo connection parameters for SAP Convergent Invoicing and SAP CRM if this is relevant for your installation.

If you want to secure connections between SAP Convergent Charging and SAP Convergent Invoicing or SAP CRM, tick the box Install SAP Cryptographic Library. A manual configuration step is required after the installation to enable the secure connections.

SAP Cryptographic Software

This dialog is only displayed if you chose to install the SAP Cryptographic Library in the previous step.

Enter the location of the SAP Cryptographic Library archive. Refer to the related section for downloading this library.

SAP Convergent Charging Instances

Enter the instances you want to install on this host.

The table at the top of the dialog lists the installed instances in the Core Server component when adding new instances to an existing system. It is empty when installing a new system.

CAUTION

You must install a dispatcher instance on the global host of the SAP system. This is the Central Instance

You must install at least one dispatcher instance and one updater instance if you want to install and connect the Core Tool to the Core Server

The pair (Instance Type, Number) forms the Instance ID of the system instance. It must be unique through the SAP CC system. You can use the same number for different instance types (rater#1, guider#1)

The rater and bulkloader instances must be installed in pairs on the same host: using the same instance number

Taxer instances are only available on Windows and Linux platforms and require the EZTax library

SAP Convergent Charging Dispatcher Instance

This dialog is displayed once for each dispatcher instance you chose to install on the host.

Enter a port and optionally a host name or IP address (IPv4 or IPv6) for each service of the dispatcher instance. The ports must not be in use by other processes, and the host names or IP addresses must correspond to the host.

Please note the ports used for connecting to the dispatcher, because you may need them later on. You will be asked for the HTTP port during the installation of the BART Server and the message port during the installation of the Diameter Server.

SAP Convergent Charging Updater Instance

This dialog is displayed once for each updater instance you chose to install on the host.

Enter a port and optionally a host name or IP address (IPv4 or IPv6) for each service of the updater instance. The ports must not be in use by other processes, and the host names or IP addresses must correspond to the host.

Start Instances after Installation

Untick the box Start Convergent Charging Instances after Installation if you do not want the server instances to start automatically after installation.

Prerequisites Checker

Enter the location of the file that contains the prerequisite checks.

An up-to-date Prerequisites Checker file from the Installation Master DVD is selected by default.

Unpack Archives Specify the archives to be unpacked. All archives should be unpacked.

SAP System Administrator

(UNIX and Linux) Change the password for the SAP system administrator if you want it to be different from the master password.

Specify the User ID and the Group ID if your system is distributed over several hosts. Use the same User ID and Group ID on each host.

RECOMMENDATION

SAP AG recommends that you install the Core Tool component and that you create the following users from the Core Tool user interface just after installing the Core Server:

A user dedicated to user management, granted with the User Administrator role

A technical user for the connection between the Core Server and the BART Server systems,

granted with the Process Manager role

The detailed procedure to create a user and grant roles to it is described in the Core Tool Online Help.

Results

You can install the other instances of the Core Server system in the system landscape.

Run SAPInst for the Core Server - Add Instance(s)

If you already have installed the Global Host (see the First Step phase), you can add new instances to the Core Server. Those instances can be located on the Global Host or on any other host. In case you add an instance on a host different from the Global Host, perform the following command lines:

On UNIX and Linux (on the host that is different from the Global Host):

mkdir /sapmnt

mount –t nfs <GLOBAL_HOST>:/sapmnt /sapmnt

mkdir /workingDirectoryCC

mount –t nfs <GLOBAL_HOST>:/workingDirectoryCC /workingDirectoryCC

On Windows (on the Global Host):

net share workingDirectoryCC=<DRIVE_LETTER>:\workingDirectoryCC

NOTES

Check that you have the no_root_squash option on your NFS shares

On NFS v4 you must have the same domain property between the different hosts in the file/etc/idmapd.conf

Installation Mode

You can install your SAP CC system according to the following modes:

If you select the Typical mode, the installation is performed with default settings. You only have to respond to a small selection of prompts

If you choose Custom mode, you are prompted for all the parameters

If you choose Custom, you are prompted for all the parameters

Choose the Custom mode in case you are installing SAP CC on the global host.

NOTE

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

Profile directory

Give the path of the profile folder on the global host. On linux in the folder /sapmnt you just mounted or in windows use the share created by SAPInst \\<GLOBAL_HOST>\sapmnt\

Master Password

Choose the Master Password. This password will be used for all the OS users created during the installation. Read SAPInst Help (type F1 in SAPInst) to have more

information about the master password, restrictions and dependencies.

SAP System Administrator

(UNIX and Linux <SID>adm account) Change the password for the SAP system administrator if you want it to be different from the master password.

Specify the User ID and the Group ID if your system is distributed over several hosts (should be the same than on global host). Use the same User ID and Group ID on each host.

JCE Unlimited Strength

Jurisdiction Policy Files

Give the path to the JCE files. See page [15] for more information about JCE jurisdiction policy files.

SAP Convergent Charging Instances

Enter the instances you want to install on this host.

The table at the top of the dialog lists the installed instances in the Core Server system when adding new instances to an existing system. It is empty when installing a new system.

CAUTION

You must install a dispatcher instance on the global host of the SAP system. This is the Central Instance

You must install at least one dispatcher instance and one updater instance if you want to install and connect the Core Tool to the Core Server

The pair (Instance Type, Number) forms the Instance ID of the system instance. It must be unique through the SAP CC system. You can use the same number for different instance types (rater#1, guider#1)

The rater and bulkloader instances must be installed in pairs on the same host: using the same instance number

Taxer instances are available on Windows and Linux platforms only and require the EZTax library

SAP Convergent Charging Dispatcher Instance

This dialog is displayed once for each dispatcher instance you chose to install on the host.

Enter a port and optionally a host name or IP address (IPv4 or IPv6) for each service of the dispatcher instance. The ports must not be in use by other processes, and the host names or IP addresses must correspond to the host.

Please note the ports used to connect to the dispatcher, because you may need them later on. You will be asked for the HTTP port during the installation of the BART Server and the message port during the installation of the Diameter Server.

SAP Convergent

This dialog is displayed once for each updater instance you chose to install on the

Charging Updater Instance

host.

Enter a port and optionally a host name or IP address (IPv4 or IPv6) for each service of the updater instance. The ports must not be in use by other processes, and the host names or IP addresses must correspond to the host.

Start Instances after Installation

Untick the box Start SAP CC Instances after Installation if you do not want the server instances to start automatically after installation.

Prerequisites Checker

Enter the location of the file that contains the prerequisite checks.

An up-to-date Prerequisites Checker file from the Installation Master DVD is selected by default.

SAP System Administrator

(UNIX and Linux sapadm account) Change the password for the SAP system administrator if you want it to be different from the master password.

Specify the User ID and the Group ID if your system is distributed over several hosts (should be the same than on global host). Use the same User ID and Group ID on each host.

Results

A new instance of the Core Server system is ready. You can install the other instances of the Core Server system in the system landscape.

When you have installed all the instances, you can start and check the system and install the user interfaces. See:

Starting and Stopping the Servers, page [70]

Installing the Tools, the IEC and the SDK, page [62]

You can install the other SAP CC server systems:

BART Server (offline charging)

Diameter Server (online charging with credit control and credit reservation)

Run SAPInst for the BART Server

PRELIMINARY NOTE

You have to start the dispatcher instances of the Core Server system before installing the BART Server component. See the section Starting and Stopping the Servers.

Prerequisites

The Core Server system is up and running

The technical user required for the communications between the BART Server and Core Server systems is available

Procedure

If you install the BART Server system on another host machine than Global Host, do the following action on the host:

On UNIX and Linux (on the hosts):

mkdir /sapmnt

mount –t nfs <GLOBAL_HOST>:/sapmnt /sapmnt

NOTES

Check that you have the no_root_squash option on your NFS shares

On NFS v4 you must have the same domain property between the different hosts in the file/etc/idmapd.conf

SAP System ID You have to specify the SAP System ID or the SAP Profile Directory (if you add a host). Refer to the section Choose your SAP System IDs

or read SAPInst to have more information about how to choose your SAP System Identifier (SID).

If you install a new SAP system, enter the SID for this system. If you install the instances of this system on more than one host, make sure that you assign the same SID to all these instances. The identifier for the database instance can be different from the SID.

If you add instances to an existing SAP system - for example, if you install additional application server instance(s) for an existing SAP system - enter the location of the profile directory of the existing SAP system.

If you uninstall an SAP system, enter the location of the profile directory of the SAP system you want to uninstall.

(WINDOWS ONLY) When installing a new SAP system or adding instances to an existing SAP system, select the destination drive. The system will be installed in the directory <DESTINATION_DRIVE>:\usr\sap\<SID>\. This option is not available if there is at least one SAP system already installed on the host.

NOTE

The location of the SAP Profile Folder of your SAP CC system is one of the following folders:

Windows: \\<SAP_GLOBAL_HOST>\sapmnt\<SID>\SYS\profile\

UNIX, Linux, and i5/OS: /sapmnt/<SID>/profile/

Existing parameters will be retrieved from the SAP system profile directory.

CAUTION

Choose different SAP System IDs for the Core Server, BART Server, Diameter Server and CT Server systems. An SAP System ID must be unique on the network to avoid mixing up different SAP systems. When installing twice the same component, you must set different SAP System IDs for the two systems for making them work properly.

Master Password

Choose the Master Password. This password will be used for all the OS users created during the installation. Read SAPInst Help (type F1 in SAPInst) to have more information about the master password, restrictions and dependencies.

SAP System Administrator

(UNIX and Linux <SID>adm account) Change the password for the SAP system administrator if you want it to be different from the master password.

Specify the User ID and the Group ID if your system is distributed over several hosts (should be the same than on global host). Use the same User ID and Group ID on each host.

JCE Unlimited Strength Jurisdiction Policy Files

Give the path to the JCE files. See page [15] for more information about JCE jurisdiction policy files.

Database Type Indicate your RDBMS for the BART database: MS SQL Server, Oracle, Oracle RAC, DB2, or Sybase ASE.

NOTE

IBM DB2 pureScale is not supported by the BART database.

Database Connection

Enter the connection parameters for the BART database. These parameters are defined during the database preparations. See page [29] for more information.

The exact title and content of this dialog depend on the database type chosen in the previous step.

Tick the box Use Partitioning if you want to partition your database.

NOTE

The partitioning option is not supported with IBM DB2.

Tablespaces / Filegroups / Segments

Specify in which tablespaces, filegroups, or segments the database tables and indexes will be created.

Possible values are restricted to the list of tablespaces, filegroups or segments which are available in the BART Database. Refer to the Creating Tablespaces, Filegroups or Segments section for creating tablespaces, filegroups or segments.

Wily Introscope Java Agent

Give the host and the port of the CA Wily Introscope Enterprise Manager if needed. See page [25] for more information about installing the CA Wily Introscope.

Untick the box Use monitoring with Wily Introscope if you do not want to use Wily Introscope to monitor the server sytem.

System Landscape Directory

Enter the URL, login and password used to submit the payload to the System Landscape Directory (SLD) in your system landscape.

Untick the box Configure System Landscape Directory if you do not want to configure the connection to SLD.

SAP Convergent Charging Security

Choose if you want to enable encryption of all the communication channels of the BART Server system.

If the encryption is enabled, choose the import format for the X.509 v3 certificates and their associated private keys used to encrypt the communication channels:

A common keystore file using the PKCS#12 format

2 separate files, using the PKCS#8 format for the file containing the private key

Check that the prerequisite Securing the Communication Channelsis fulfilled.

Import Key Pair From PKCS#12 File

This dialog is displayed only if you chose to encrypt communication channels and to import the key pair from a common PKCS#12 keystore file.

Enter the location of the PKCS#12 keystore file and its passphrase.

This dialog is displayed twice:

A first time when configuring the key pair used for the encryption of the external channels of the Packets over TCP/IP, SOAP over HTTP and XML over HTTP communication channels

A second time when configuring the key pair used for the encryption of the internal channel of the Packets over TCP/IP communication channel

Import Key Pair From Separate Files

This dialog is displayed only if you chose to encrypt communication channels and to import the key pair from 2 separate files.

Enter the location of the PKCS#8 file containing the private key and the location of the file containing the X.509 v3 certificate.

This dialog is displayed twice:

A first time when configuring the key pair used for the encryption of the external channels of the Packets over TCP/IP, SOAP over HTTP and XML over HTTP communication channels

A second time when configuring the key pair used for the encryption of the internal channel of the Packets over TCP/IP communication channel

BART Server Settings

Enter a port and optionally a host name or IP address (IPv4 or IPv6) for each service of the BART Server system. The ports must not be in use by other processes, and the host names or IP addresses must correspond to the host.

SAP Convergent Charging Core Server Connection Security

Enter the security level for the connection from BART Server to Core Server. This level depends on the security configuration of the Core Server system.

The possible security levels are:

None The communications between the BART Server and the Core Server systems are not encrypted.

Oneway The communications between the BART Server and the Core Server systems are encrypted. The identity of the Core Server system is verified by the BART Server system.

Dual (import key pair from PKCS#12 file)

The communications between the BART Server and the Core Server systems are encrypted. The BART Server system and the Core Server system identify each other.

Dual (import key pair from separate files)

The two different Dual options determine the import format for the X.509 v3 certificates and their associated private key, which will be used for the encryption:

In a common keystore file using the PKCS#12 format

In 2 separate files, using the PKCS#8 format for the file containing the private key

Import Key Pair From PKCS#12 File

This dialog is only displayed if you chose the Dual security level for the communications between the BART Server and the Core Server, and to import the key pairs from a common PKCS#12 keystore file.

Enter the location of the PKCS#12 keystore file and its passphrase.

Import Key Pair From Separate

This dialog is only displayed if you chose the Dual security level for the

Files communications between the BART Server and the Core Server, and to import the key pairs from 2 separate files.

Enter the location of the PKCS#8 file containing the private key and the location of the file containing the X.509 v3 certificate.

Import Certificates

This dialog is only displayed if you chose the Oneway or Dual security level for the communications between the BART Server and the Core Server.

Enter the location of the X.509 certificate(s) used by the Core Server.

This step is required if the certificate used by the Core Server are self-signed or signed by a Certification Authority which is not recognized.

SAP Convergent Charging Core Server Connection

Enter the connection parameters (HTTP host and port) of the dispatcher instance(s) of the Core Server system. See the step SAP CC Dispatcher Instance of the Core Server installation. The list must contain the connection parameters of at least one dispatcher instance.

Enter the login and password of a valid technical user defined in the Core Server system. The user must be granted with the Process Manager role.

CAUTION

Each dispatcher instance specified in the list must be running during the BART Server installation so that the connection parameters can be verified.

To start the dispatcher(s) of the Core Server system, see the section Starting and Stopping the Servers.

Start server after Installation

Untick the box Start server after Installation if you do not want the server to start automatically after installation.

Prerequisites Checker

Enter the location of the file that contains the prerequisite checks.

An up-to-date Prerequisites Checker file from the Installation Master DVD is selected by default.

Unpack Archives

Specify the archives to be unpacked. All archives should be unpacked.

Run SAPInst for the Diameter Server

If you install the Diameter Server on another host than Global Host, do the following action on the host:

On UNIX and Linux (on the hosts):

mkdir /sapmnt

mount –t nfs <GLOBAL_HOST>:/sapmnt /sapmnt

NOTES

Check that you have the no_root_squash option on your NFS shares

On NFS v4 you must have the same domain property between the different hosts in the file/etc/idmapd.conf

SAP System ID You have to specify the SAP System ID or the SAP Profile Directory (if you add a host). Refer to the section Choose your SAP System IDs

or read SAPInst to have more information about how to choose your SAP System Identifier (SID).

If you install a new SAP system, enter the SID for this system. If you install the instances of this system on more than one host, make sure that you assign the same SID to all these instances. The identifier for the database instance can be different from the SID.

If you add instances to an existing SAP system - for example, if you install additional application server instance(s) for an existing SAP system - enter the location of the profile directory of the existing SAP system.

If you uninstall an SAP system, enter the location of the profile directory of the SAP system you want to uninstall.

(WINDOWS ONLY) When installing a new SAP system or adding instances to an existing SAP system, select the destination drive. The system will be installed in the <DESTINATION_DRIVE>:\usr\sap\<SID>\ folder. This option is not available if there is at least one SAP system already installed on the host.

NOTE

The location of the SAP Profile Folder of your SAP CC system is one of the following:

Windows: \\<SAP_GLOBAL_HOST>\sapmnt\<SID>\SYS\profile\

UNIX, Linux, and i5/OS: /sapmnt/<SID>/profile/

Existing parameters will be retrieved from the SAP system profile directory.

CAUTION

Choose different SAP System IDs for the Core Server, BART Server, Diameter Server and CT Server components. An SAP System ID must be unique on the network to avoid mixing up different SAP systems. When installing twice the same component, you must set different SAP System IDs for the two systems for making them work properly.

Master Password Choose the Master Password. This password will be used for all the OS users created during the installation. Read SAPInst Help (type F1 in SAPInst) to have more information about the master password, restrictions and dependencies.

SAP System Administrator

(UNIX and Linux <SID>adm account) Change the password for the SAP system administrator if you want it to be different from the master password.

Specify the User ID and the Group ID if your system is distributed over several hosts (should be the same than on global host). Use the same User ID and Group ID on each host.

JCE Unlimited Strength Jurisdiction Policy Files

Give the path to the JCE files. See page [15] for more information about JCE jurisdiction policy files.

OpenBlox License Enter the license key for the OpenBlox software included in the Diameter Server.

SAP Convergent Charging Security

Choose if you want to enable encryption of the external interface of the Diameter Server.

If the encryption is enabled, choose the import format for the X.509 v3 certificates and their associated private key used for the encryption of the communication channels:

A common keystore file using the PKCS#12 format

2 separate files, using the PKCS#8 format for the file containing the private key

Check that the prerequisite Securing the Communication Channels is fulfilled.

Import Key Pair From PKCS#12 File

This dialog is displayed only if you chose to encrypt communication channels and to import the key pairs from a common PKCS#12 keystore file.

Enter the location of the PKCS#12 keystore file and its passphrase.

Import Key Pair From Separate Files

This dialog is displayed only if you chose to encrypt communication channels and to import the key pairs from 2 separate files.

Enter the location of the PKCS#8 file containing the private key and the location of the file containing the X.509 v3 certificate.

SAP Convergent Charging Core Server Connection

Enter the security level for the connection between the Diameter Server and the Core Server. This level depends on the security configuration of the Core Server.

The possible security levels are:

Security None The communications between the Diameter Server and the Core Server are not encrypted.

Oneway The communications between the Diameter Server and the Core Server are encrypted. The identity of the Core Server system is verified by the Diameter Server.

Dual (import key pair from PKCS#12 file)

The communications between the Diameter Server and the Core Server are encrypted. The Diameter Server and the Core Server identify each other.

Dual (import key pair from separate files)

The 2 different Dual options determine the import format for the X.509 v3 certificates and their associated private key, which will be used for the encryption:

In a common keystore file using the PKCS#12 format

In 2 separate files, using the PKCS#8 format for the file containing the private key

Import Key Pair From PKCS#12 File

This dialog is only displayed if you chose the Dual security level for the communications between the Diameter Server and the Core Server components, and to import the key pairs from a common PKCS#12 keystore file.

Enter the location of the PKCS#12 keystore file and its passphrase.

Import Key Pair From Separate Files

This dialog is only displayed if you chose the Dual security level for the communications between the Diameter Server and the Core Server components, and to import the key pairs from2 separate files.

Enter the location of the PKCS#8 file containing the private key and the location of the file containing the X.509 v3 certificate.

Import Certificates

This dialog is only displayed if you chose the Oneway or Dual security level for the communications between the Diameter Server and the Core Server components.

Enter the location of the X.509 certificate(s) used by the Core Server.

This step is required if the certificates used by the Core Server are self-signed or signed by a Certification Authority which is not recognized.

Diameter Service Enter the port and optionally the host name or IP address (IPv4 or IPv6) of the Diameter Server interface. The port must not be in use by other processes, and

the host name or IP address must correspond to the host.

SAP Convergent Charging Core Server Connection

Enter the connection parameters (external host and port) of the Dispatcher instance(s) of the Core Server component. The list must contain the connection parameters of at least one dispatcher instance.

CAUTION

Each dispatcher instance specified in the list must be running during the Diameter Server installation so that the connection parameters can be verified.

To start the dispatcher(s), see the section Starting and Stopping the Servers.

Run SAPInst for the CT Server

EZTax Settings

Enter the location of the EZTax installation folder or the path to the eztax directory. See page [23] for more details.

JCo Settings Enter the JCo connection parameters. See page [24] for more details.

If you want to secure connections for the CT Server, tick the box Install SAP Cryptographic Library. A manual configuration step is required after the installation to enable the secure connections.

Prepare the Installation

Install the SAP JVM 6.1

You must download and install the SAP JVM on any machine hosting:

The Core Tool

The BART Tool

The CAT Tool

The Simulation Tool

The IEC

The Core SDK

The BART SDK

The IEC SDK

SAP JVM installation procedure:

Unpack the SAP JVM you previously downloaded with the SAP archiving program SAPCAR

Execute the command SAPCAR –xvf SAPJVM*.SAR to unpack the SAP JVM files under the subdirectory sapjvm_6

NOTE

You have to check that the local_policy.jar and US_export_policy.jar are present in the “<path to the SAP JVM 6.1>/jre/lib/security” folder. If not, you must copy them from the JCE previously downloaded.

Set the SAPCC_JAVA_HOME Environment Variable

You have to set the SAPCC_JAVA_HOME environment variable to the path to the SAP JVM 6 as described below:

Type the command for Windows: set SAPCC_JAVA_HOME=<path to the SAP JVM 6.1>

Type the command for Linux: export SAPCC_JAVA_HOME=<path to the SAP JVM 6.1>

NOTE

The installation on Mac OS is supported for:

The Core Tool

The BART Tool

The CAT Tool

The Simulation Tool

Apple supplies its own version of Java. Check that Java for Mac OS is updated to the minimum Java version 1.6.0_22 on any machine hosting one of the above-mentioned tools.

Security Settings

To give the possibility for a client application to trust the Core Server system, it is necessary to import the certificate (and its private key) of the Core Server system into the truststore used by this client application.

To import the “certificate.ext.der” certificate (the one you created to secure external communication in the Core Server) into a java keystore named “keystore.cli.jks”, type the following command:

keytool -importcert -file certificate.ext.der -keystore keystore.cli.jks -

noprompt

NOTE

You will be prompted to type a passphrase for the java keystore file which will contain the certificate to import. It is necessary to remember this passphrase in order to execute the following command.

NOTE

When the security is activated, use the HTTPS protocol to connect the Core Tool to the Core Server.

Organize Directories

In order to ease the maintenance, we strongly recommend that you create a directory for each program you want to install.

Get the Installation Files from DVD

The installation ZIP files used to install the graphical user interfaces and tools, the IEC and the SDKs are available on the installation DVD in the subdirectory CC40_TOOLS_CONTENT_UC_OSIND (see the previous section about the data units). See the table below to determine which files you need for your installation.

SAP CC Software Unit Required Setup Files

Core Tool core_tool.zip

BART Tool bart_tool.zip

IEC iec.zip

CAT Tool cat_tool.zip

Simulation Tool sim_tool.zip

Core SDK core_sdk.zip

BART SDK bart_sdk.zip

CAUTION

The Core Tool must be installed before the BART Tool because you need to use the Core Tool for creating or granting a user for the BART Tool

The Core Tool must be installed after the Core Server

The BART Tool must be installed after the BART Server

Core Tool

Use the procedure below to install the Core Tool component and its user interfaces (Core Tool, Admin+).

Install Unzip the core_tool.zip file in the installation directory

(Mac OS) Type the following command in a terminal to set execution permission to the launcher script: chmod +x /<installation_directory>/bin/CoreTool.app/Contents/MacOS/core_tool

(UNIX and Linux) Type the following command in a terminal to set execution permission to the launcher script: chmod +x core_tool/bin/core_tool.sh

Start and Login

(Windows) Launch the core_tool.bat script from the bin directory to start the Core Tool user interface

(Mac OS) Launch the CoreTool.app application from the bin directory to start the Core Tool user interface

(UNIX and Linux) Launch the core_tool.sh script from the bin directory to start the Core Tool user interface

Type:

admin as login

The Convergent Charging Administrator User password defined during the Core Server installation with SAPInst as password

Click the Options tab to:

Set the URL of the Core Server system by specifying the dispatcher host name or IP address (IPv4 or IPv6) and the corresponding port. The syntax of the URL is: http://<dispatcher_host>:<dispatcher_port> or, if the Core Server is configured to use the HTTPS protocol: https://<dispatcher_host>:<dispatcher_port>

Select the currency

Click OK

BART Tool

Use the procedure below to install the BART Tool component and its user interfaces (BART Tool, BART+).

Install Unzip the bart_tool.zip file in the installation directory

(Mac OS) Type the following command in a terminal to set execution permission to the launcher script: chmod +x /<installation_directory>/bin/BARTTool.app/Contents/MacOS/bart_tool

(UNIX and Linux) Type the following command in a terminal to set execution permission to the launcher script: chmod +x bart_tool/bin/bart_tool.sh

In the config directory, make a copy of the file bart_tool.config.sk and name it bart_tool.config

Indicate the URL of the BART Server in the BARTServerURL parameter of the bart_tool.config file. The syntax is one of the following: http://<bart_server_host>:<bart_port>/ or, if the BART Server is configured to use the HTTPS protocol: https://<bart_server_host>:<bart_port>/

Start and Login

(Windows) Launch the bart_tool.bat script from the bin directory to start the BART Tool

(Mac OS) Launch the BARTTool.app application from the bin directory to start the BART Tool

(UNIX and Linux) Launch the bart_tool.sh script from the bin directory to start the BART Tool

Login with the Convergent Charging Administrator User or any other user created with the Core Tool and having the Batch Rating Administrator role

IEC

Use the procedure below to install the IEC component and its import/export connector (IEC) application.

Unzip the Installation Files

Unzip the iec.zip file in the installation directory.

Create Database Tables

NOTE

This step is only relevant if you plan to use one of the following components in a configuration scenario customized with the CAT Tool user interface:

Export to Database

Import XCI from Database

For ASE databases

Make sure that your IEC database was created (see the procedure page [29])

Get the script ase_iecdb_create.sql located into the iec_sql directory of your installation

Execute the script with the following command: isql –U< dbuser> –P<dbpwd> -Iase_iecdb_create.sql where <dbuser> corresponds to the login, <dbpwd> to the password of the user created for the IEC Database

For Oracle databases

Make sure that your IEC database was created (see the procedure page [35])

Get the script oracle_iecdb_create.sql located into the iec_sql directory of your installation

Execute the script with the following command: sqlplus <dbuser>/<dbpwd> < oracle_iecdb_create.sql where <dbuser> corresponds to the login and <dbpwd> to the password of the user created for the IEC Database

For DB2 databases

Make sure that your IEC database was created (see the procedure page [37])

Get the script db2_iecdb_create.sql located into the iec_sql directory of your installation

Execute the script with the following commands: db2 connect to <database_name> db2 –tvf db2_iecdb_create.sql where <database_name> corresponds to the name of the IEC Database

For SQL Server databases

Make sure that your IEC database was created (see the procedure page [34])

Get the script sqlserver_iecdb_create.sql located into the iec_sql directory of your installation

Open the script with the Microsoft SQL Server Management Studio

Execute the script with the Microsoft SQL Server Management Studio: you have to connect to the server and then select the IEC Database

Start the IEC In the bin directory, launch the IEC application by:

(Windows) Double-clicking the iec.bat script

(UNIX and Linux) Executing the following commands: chmod a+x iec.sh dos2unix iec.sh and launching the iec.sh script

The IEC launch script accepts the following arguments:

-login <USR_LOGIN> -password <USR_PASSWORD> <SCENARIO_DIR> -

uri <CCD_URI> [-rootDir [<LOG_DIR>]] [-scheduled]

Where:

<USR_LOGIN> is the login of a power user or administrator having the right to execute the connector program

<USR_PASSWORD> is the password which is associated to the <USR_LOGIN> provided technical user

<SCENARIO_DIR> is the path to the scenario file to be executed by the import/export connector (IEC) application; this configuration scenario is customized during the implementation project phase.

<CCD_URIS> is a comma-separated list of URIs relating to dispatcher instances of the Core Server. Every provided URI has the following syntax: <PROT>://<HOST_ADDRESS>:<MSG_TCP_PORT> where: <PROT> is the communication protocol (possible values are: tcp and tcps) <HOST_ADDRESS> is the hostname or the IP address (IPv4 or IPv6) of the machine hosting the dispatcher instance related to the URI <MSG_TCP_PORT> is the port number of the host that is dedicated to the dispatcher instance for the communications via the Packets over TCP/IP communication channel -rootDir [<LOG_DIR>] is an optional argument; <LOG_DIR> is the directory where the log files are created; if <LOG_DIR> is not mentioned, the default directory is the user working directory that depends on the procedure used to launch the connector program -scheduled is an optional argument; this argument enables the scheduler as configured in the scenario to be executed; if this argument is not mentioned, the scenario is executed only once even if the scenario defines regular activities

NOTES

You can use IEC Remote to test scenarios in a development or test system landscape only. Apply the procedure described above with the iec_remote.sh script

If your connector needs to call Java classes (available in jar files) from external applications, ensure that the jars directory of your installation contains these jar files

CAT Tool

Use the procedure below to install the CAT Tool:

Unzip the cat_tool.zip file in the installation directory

(Mac OS) Type the following command in a terminal to set execution permission to the launcher script: chmod +x /<installation_directory>/bin/CATTool.app/Contents/MacOS/cat_tool

(UNIX and Linux) Type the following command in a terminal to set execution permission to the launcher script: chmod +x cat_tool/bin/cat_tool.sh

If you use the BART Server component, copy the bart_iec.jar files from your BART Server installation to the jars directory

In the config directory, make a copy of the file cat_tool.config.sk and name it cat_tool.config

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

(Mac OS) Launch the CATTool.app application from the bin directory to start the CAT Tool

(UNIX and Linux) Launch the cat_tool.sh script from the bin directory to start the CAT Tool

Simulation Tool

Use the procedure below to install the Simulation Tool:

Unzip the sim_tool.zip file in the installation directory

In the config directory, make a copy of the file sim_tool.config.sk and name it sim_tool.config

(Mac OS) Type the following command in a terminal to set execution permission to the launcher script: chmod +x /<installation_directory>/bin/SimulationTool.app/Contents/MacOS/sim_tool

(UNIX and Linux) Type the following command in a terminal to set execution permission to the launcher script: chmod +x sim_tool/bin/sim_tool.sh

(Windows) Launch the sim_tool.bat script from the bin directory to start the Simulation Tool

(Mac OS) Launch the SimulationTool.app application from the bin directory to start the Simulation Tool

(UNIX and Linux) Launch the sim_tool.sh script from the bin directory to start the Simulation Tool

Installing the SDKs

Use the procedure below to install the SDKs:

Unzip the core_sdk.zip file in the installation directory

Unzip the bart_sdk.zip file in the installation directory

On the Global Host of the Core Server system, disable the no_root_squash option on your NFS shares after the installation.

You must install a permanent SAP license for the Core Server system. When you install the Core Server system, a temporary license is automatically installed. This temporary license allows you to use the system for only four weeks from the date of installation.

CAUTION

Before the temporary license expires, you must apply for a permanent license key from SAP. We recommend that you apply for a permanent license key as soon as possible after installing your system.

Apply for the Permanent License

To obtain a permanent license key, see http://service.sap.com/licensekey on the SAP Service Marketplace.

You need to indicate the hardware key for each machine hosting an instance of the Core Server when applying for a permanent license. The hardware keys are written in a file called hardware_keys.txt stored in one of the following directories on any instance host:

<DRIVE>:\usr\sap\<SID>\sys\profile\ (MS Windows)

/usr/sap/<SID>/sys/profile/ (Other operating systems)

Install the Permanent License

You must use the Setup Tool on any machine hosting a dispatcher to install the permanent license.

Go to one of the following directories:

<DRIVE>:\usr\sap\<SID>\<INSTANCE_NAME>\script\ (MS Windows)

/usr/sap/<SID>/<INSTANCE_NAME>/script/ (Other operating systems)

Where <INSTANCE_NAME> corresponds to the name of the instance of the SAP CC system. By default it is composed of three characters and two digits. For a dispatcher, the instance name starts by CCD.

Type the following command: setup license import <license_file> , where <license_file> corresponds to the path to the file containing the license

Restart the Instances

You must restart all the instances of the Core Server for the new license to be taken into account. See the section Starting and Stopping the Servers to know how to restart the instances.

Windows

SAP Microsoft Management Console (MMC)

The SAP Microsoft Management Console (sapmmc) was installed during the Core Server system installation. It enables you to see all your SAP systems and to manage them.

To start or restart the servers:

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

Click the SAP system containing the server you want to start

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

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

Other Operating Systems

SAP Management Console (MC)

The SAP Management Console (sapmc) was installed during the Core Server system installation. It enables you to see all your SAP systems and to manage them. It is installed in the following directories:

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

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

Where <INSTANCE_NAME> corresponds to the name of the instance of the SAP CC system. By default it is composed of three characters and two digits.

To launch this tool:

Launch a web browser capable of running Java applications

Open the sapmc.html file from the host

SAP Control

Use the sapcontrol program to start and stop the server systems or some server instances. This program is installed in the /usr/sap/hostctrl/exe/ directory.

Use the following options (respect the option order):

-host: To specify on which host is the server you want to manage

-user: To give the user you want to use for managing the server (use the sapadm user created during the installation for example) if you’re not login in sapadm you must specify the password

-nr: To give the number of the SAP instance

-function: To specify the command which must be applied to the server (Start, RestartInstance, Stop, and so on)

E.g.: sapcontrol -user cc1adm <password> -nr <instance number> -function RestartInstance

Related Documentation

Topic Location

SAP Management Console (SAP MC) SAP Management Console

SAP Snap-In for Microsoft Management Console (SAP MMC Snap-In)

SAP Microsoft Management Console: Windows

After installing the Core Tool user interface, you must configure the localization of the online Help systems. Execute the following procedure:

Go to the config directory in the directory where you installed the Core Tool

Make a copy of the file core_tool.config.sk and name it core_tool.config

Uncomment the three last lines dedicated to online help

You can also consult the online Help of the Core Tool user interface in SAP Help Portal at: http://help.sap.com/cc SAP CC 4.0 Configuration Information Power User Documentation - Core Tool .

Execute the same procedure for the other tools. See the SAP CC Configuration Guide for more details.

After installing SAP Convergent Charging, refer to the SAP CC Configuration Guide for configuring the system.

After installing your system landscape, refer to the SAP CC Operations Guide for administrating the server and back-end database systems.

See the SAP CC Operations Guide if you want to install support packages and patches.

CAUTION

After the installation, check that the default super administrator and emergency user (“admin”) is not available in a production system landscape.

During the post-installation, you create several individual or service users in SAP CC depending on your requirements. See the section Standard Users of the SAP CC Security Guide to know which SAP CC users have to be created and their roles.

BART User Management

Apply the following procedure if you want to change the technical user dedicated to the communications between the Core Server and the BART Server systems:

Follow the instructions of the Security Guide to create a user dedicated to BART Server

After the creation of the BART Server user, the configuration of the BART Server must be updated. Edit the file bart.config located in the following directory: <DRIVE>:\usr\sap\<SID>\CAB<INSTANCE_NB>\config\bart.config (MS Windows) /usr/sap/<SID>/CAB<INSTANCE_NB>/config/bart.config (Other OSs) where <INSTANCE_NB> is the number automatically assigned to the BART Server system by SAPInst

Modify the values of the properties cc.login and cc.password respectively with the login and the password of the BART Server user

Restart the BART Server system

To configure the access to an SAP SLD system, refer to the section System settings for the System

Landscape Directory in the SAP CC Configuration Guide.

In the SAP Solution Manager Configuration work center (transaction SOLMAN_SETUP), choose Technical Monitoring > Define Scope.

Select the SAP CC 4.0 system and continue with the next step Setup Monitoring to assign templates.

NOTE

Refer to SAP Note 1875021 for more information about the available template files and the technical monitoring setup for SAP Convergent Charging systems.

To setup the monitoring, assign appropriate templates to the SAP CC instances, the system database, and the hosts they are installed on, and apply the monitoring.

This section describes how to uninstall a whole component or a single instance of the Core Server system.

Uninstalling an Instance or a Server

Uninstalling an instance or a server is done with SAPInst.

NOTE

To uninstall instances of the Core Server distributed over several hosts, you must:

Run SAPInst on each host

Start with the hosts different from the global host

Finish by launching SAPInst on the global host

Use the following procedure to uninstall SAP CC:

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

Click SAP Convergent Charging Software Life-Cycle Options Uninstall Uninstall SAP

Systems or Single Instances

NOTE

You do not need to stop the servers before uninstalling SAP CC.

General SAP System Parameters

You have to specify the location of your SAP system profile directory:

Windows: \\<SAPGLOBALHOST>\sapmnt\<SID>\SYS\profile\

UNIX, Linux and i5/OS: /<SAP Mount Directory>/<SID>/profile/ or /usr/sap/<SID>/SYS/profile/

Existing parameters will be retrieved from the SAP system profile directory.

Uninstall Instances

Tick the Uninstall all instances of the SAP system from this host box if you want to uninstall all the instances hosted on this machine. Select the Delete OS User option if you want to delete the users created during the installation.

In you do not tick the Uninstall all instances of the SAP system from this host box, select the instances you want to uninstall in the table. Note that you cannot select the Delete OS User option.

Parameter Summary

Check that the choices you have made during the previous steps are correct. You can change them and go back to previous steps. Then click Ok to make the component

uninstalled.

Uninstalling the Database

SAPInst does not delete your Core or BART database. Please refer to the documentation of your RDBMS for deleting the databases.

Uninstalling the IEC, a Tool or a SDK

Use the following procedure to uninstall one of the components listed below:

The Core Tool

The BART Tool

The CAT Tool

The Simulation Tool

The IEC

The Core SDK

The BART SDK

Procedure:

Delete the installation directory

Delete the SAPCC_JAVA_HOME environment variable

Copyrights

© 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.

This documentation may describe use cases that are not authorized for all customers in all regions. Please refer to your license agreement and comply with any territorial or use restrictions that apply.

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 on SAP Service Marketplace and in SAP Support Portal at the following location: https://service.sap.com/instguides SAP Business Suite Applications SAP Convergent Charging SAP CC 4.0 .

Quick link: instguidescc40

You can find the SAP CC product documentation in SAP Help Portal at the following location: http://help.sap.com/cc SAP CC 4.0 .

Quick link: cc40

© 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