You are on page 1of 97

Business Scenario Configuration Guide SAP Convergent Charging (SAP CC 2.

0)
Target Audience
Technology Consultants System Administrators Solution Consultants

PUBLIC Document version: 1.0 – September, 2010

CAUTION
Before you start the implementation or your operations, make sure you have the latest version of this document. You can find the latest version from SAP Service Marketplace at the following location:  Install or
 SAP Business Suite Applications  SAP Convergent Charging  SAP CC 2.0  Install

.

The following table provides an overview of the most important document changes. Version 1.0 Date September, 2010 Description Initial version

......................................................... 25 Setting up the Cache Sizes ............................................................................................................. 29 Resetting the Login and Password for the Database ...................................................... 15 Starting and Stopping the Servers.................................................................................................................................................................................................................................................................................................. 21 Implementation Activities ............................................ 23 Additional Information.................................................................................................................... 10 2 BEFORE YOU START ........................................................... 23 3 CONFIGURATION OF THE TECHNICAL SERVICES .............................................................................................................. 25 Settings for Data Cache Management ........................................................ 24 Settings for the License Management ............................................................................................................................ 9 About this Document ............................................................................................................. 26 Enabling/Disabling the Security Policy for the Users ................................................................................................................................................................ 12 Technical System Landscape ................................................................................................................................................ 28 Setting up the User Work Session Management ................................................... 12 Global Definitions.............................................................................................................................................................................. 15 Other Operating Systems ......................................................................................................................................................................................................................................... 29 ...................................................................................................... 9 Document Abbreviations ................................................................................. 24 Settings for the Java Virtual Machine ............................................................................................................. 15 Configuration and Administration Tools ........................................ 12 Master Guides ................................................... 25 Settings for the User Management ........................................................................................................................................................................................................................................................ 26 Setting up the Security Policy for the User Passwords ................................................ 14 Business Processing .............................................................................................................................................................................................. 28 Settings for Communication ............................................................................... 23 Related Documentation ............................................................................................ 24 Install the Permanent License ............................................................................................................................ 29 Disabling up the UDP Discovery Function (Post Installation) .............................. 4 1 INTRODUCTION ........................................DOCUMENT HISTORY .................. 16 Setup Tool ....................................................................................................................................................................................................................................................................................................... 16 Admin+ Tool ..................................................................... 15 Windows ..................................................................................................................................................................................................................................................................... 24 Apply for the Permanent License . 26 Setting up the Users ......................... 9 Target Audience ......................................................................................................................................................................................................................................................................................... 12 Scenario ............................................ 12 Fundamental Guides ....................................................... 3 TABLE OF CONTENTS................................................. 27 Resetting the Emergency User ................................... 20 Bart+ Tool ................................................. 22 Important SAP Notes.......................................................................................................................................... 24 Setting up the Memory for a Rater Instance ............................................. 19 Configuration Tool .........................

.................................................................................................. 45 Setting up an Offer ........................................................................................................................ 35 Creating a Notification Policy Configuration File ................................................................ 43 Setting up Chargeable Item Classes .... 41 Setting up the Precision and Rounding for Rating and Charging (Advanced) ............................ 35 Enabling the Notification Policy Function .................................................................................................. 50 5 SYSTEM CONFIGURATION OF TRANSACTION PERSISTENCY ...................................................................................................................................................................................................................................................... 49 Setting up the Tax Framework ................................................................................................................... 48 Charged Transaction Management...................................... 30 Enabling the SLD Data Supplier Function .................................... 42 Setting up the Rerating Function ..................................................................................................... 47 Charged Item Management ......................................................................... 52 Settings for Data File Processor ....................... 49 Setting up the Taxes for the Pricing ................................................................................................................................... 52 Settings for Transaction File Processor ........................................... 47 Chargeable Item Acquisition (Implementation) .............................................................................................................................................................................................................................................................. 31 Overview of the Function.............................................................................. 43 Master Data ............. 52 Setting up the Charged Item File Processor (CIF) ................................................ 30 Setting up the Time Zone and Date Management (Implementation) .................................................................... 30 Setting up the SLD Data Supplier Function .................. 46 Transactional Data .......................................................................................................................... 36 Implementation Tasks ............ 49 Setting up the Taxes for the Accounts ... 35 Defining a Concept for the Notification Policy ..................................................... 51 Advanced: Generating Charged Transactions and Charged Items ...................................................................... 32 Setting up the Notification Policy Function ................................. 41 Rating and Charging .................................................. 41 Business Objects ................................................................................... 32 Notifications ......................................................................................................................................................... 44 Setting up Charges ....................................................................... 49 Currency Management ........................................................................................................................................................... 49 Managing a Currency Reform (Implementation) ............................................................................................................................................................................................................................................................................................................. 31 Settings for Publishing Notifications (Account Balance Alerts and Administrative Traps) ................................................... 42 Setting up the Batch Rating Groups ........... 47 Billable Item Management .................................................................................... 37 Implementing the Notification Handler in Your Java Application ............................................................................................ 53 ................................................................................................................Settings for Time Zones and Dates ....................................... 43 Setting up Charged Item Classes .......... 51 Settings for Charged Item File Processor ......................................................................................................................................................................................................... 51 Setting up the Transaction Persistency Processing Mode (TIF) ................................................... 30 Settings for the System Landscape Directory ...................... 48 Tax Management ................................................................................................ 37 Determining the Sizes of the Data Caches ................................................................................................................................................................................................................................................................................................................................................................................................................................................................ 42 Implementing the Rerating Function .................... 45 Setting up a Subscriber Account (Implementation) ................................... 41 Setting up the Public Holidays ..................... 52 Setting up the Transaction File Processor ............................................................................................................................. 46 Setting up a Subscription and Accesses (Implementation) ........................................................................................................................................................................................................................................................................................ 38 4 CONFIGURATION OF THE BUSINESS FEATURES ......................................................................

.. 55 Maintaining Billable Item Mapping ............................................................................................................................................................................................................................................................................................. 70 Setting up the HTTP Connection to the BART Server ..................... 71 Setting up the Magic Number Pattern ........................ 78 ................................................................................................ 54 Settings for Communication . 75 Technical Configuration for the Monitoring ......................... 72 Monitoring and Event Broadcasting ............................................................................................................................................................................................................................ 62 Settings for the Graphical User Interfaces ................... 57 Setting up the Default Field Mapping Between CIT and BIT (Implementation) ...................... 77 Technical Configuration for Rerating ............................. 70 Setting up the TCP/IP Connection for the Acquisition or Rerating Functions ............................................................. 57 Settings for the Communications Taxing Server .................................................................................................................................................................... 55 Setting up Billable Item Mapping (Master Data) ....................Setting up the Data File Processor .................................................................................. 65 Setting up the Connector Administration Tool ............................................................................................................................ 69 Setting up the Connection to the Database... 62 Setting up the Desktop Tool .......................................... 55 Setting up the Bulkloader Instances (CIF) ........................................................................................................... 67 Settings for the Command Line Interfaces ........................................ 54 Setting up the Rater Instances (CIF) ..................................... 59 Setting up the Log Directory for the EZTax Log Files ............................................................................................................................................................................................................................................................. 75 Technical Settings.................................................................................................................................................. 62 Setting up the BART Tool ......... 69 Setting up the Database Connection SQL Failure Management ............................. 77 CDR Acquisition ..................... 71 Setting up the Scheduled Job Management ........................................ 77 CDR Acquisition with the Java API (TCP/IP) ............................................ 69 Communication Settings ....................... 70 Setting up the Rerating Function . 76 Technical Configuration for Acquisition Sessions . 71 Setting up the Logging Function ........................................................................................................................................................................................................................ 76 Technical Configuration for CDR Consolidation Cache Management .................................................................................................................................................................. 59 Setting up a Destination .................................. 71 Basic Settings ............................................................................. 64 Setting up the Simulation Tool .......................................................................................................................... 70 Setting up the Connection to the Core Server................... 75 Advanced: Resetting the Customized File Report Handler ....................................................................................................... 55 Settings for the Conversion of Charged Items into Billable Items ............................................................................................................ 60 Setting up Other Basic Settings ................................................................................................................................... 54 Setting up the jco.......................................................... 73 Setting up the File Report Handler ............................................................................... 77 Implementation Tasks ....................................................................................................................................................................... 75 Changing the Password to Log on the Core Server..................................................................... 61 7 SYSTEM CONFIGURATION OF THE USER INTERFACES .................................................................................................................................................................................................................................................................................................. 68 8 CONFIGURATION OF THE BART SERVER ... 56 Setting up the Updater Instances (EIF) ............................................................................................................................................................................................ 74 Enabling the Monitoring Function .................................................................... 54 Settings for Charged Item File Management ........................................ 76 Technical Configuration for Rating Sessions Management .............................................................................................................................. 53 6 CONFIGURATION FOR SAP CONVERGENT INVOICING ..........................................................................................................................................destination Used to Connect to SAP CI ..........................................................................................................................................................................................

....................................................... 83 Setting up the Partitioning Configuration for Oracle ............................................................................... 83 Setting up the Partitioning Configuration for MS SQL Server .. 80 Supervision with the Event Handler Framework ....................................................................................................................................................................................................................................... 92 Implementation Tasks ........................................................................ 91 11 CONFIGURATION OF THE IEC ................................................................ 94 COPYRIGHTS ............................................................................ 92 Implementing Java Classes for Adding Functions ................................................................. 92 Setting up a Scenario ....... 90 Implementation Tasks .................................... 89 Changing the Settings of the Service Dictionary................... 92 Basic Settings .......................... 94 ICONS ............................................................................... 88 Technical Settings......................................... 82 9 CONFIGURATION OF THE BART DATABASE ............................................................................................................................................................................... 95 Disclaimer............................................................................................ 84 10 CONFIGURATION OF THE DIAMETER SERVER ....................................................................................................... 90 Setting up the AVP Dictionary ................................................................................................................................................................................................................................... 88 Setting up the Basic Configuration ............................................................................................................................................................................ 90 Changing the Settings of the AVP Dictionary ......................................... 83 Partitioning................................................................................................................................................................................................................................... 90 Setting up the Server for Development or Testing Purpose ..................................................................................................... 90 Setting up the Service Dictionary .............. 79 CDR Acquisition with the XML API . 80 Setting up the Customized Event Handlers................ 81 Job Framework .......................................................................................................................................................................................................................... 96 ................. 88 Setting up the Quick Configuration ....... 89 Business Settings .......................................................................................... 96 Documentation in the SAP Support Portal ............................................................................................................................................................................................................................................................................................................................... 93 TYPOGRAPHIC CONVENTIONS..........................................................................................................................................................................................................................................................................................................CDR Acquisition with the Java API (XML/HTTP).................................................................................................................................. 89 Setting up the Logging Configuration .......................

.

CAT. transactional data (input and output). users Configuration of the Business Features Settings of the Core Server for business objects. whereas the Configuration Guide provides information that is relevant for all the phases: Implementation Planning Integration Installation Operation & maintenance Upgrade The Configuration Guide provides some useful guidelines for configuring and tuning SAP Convergent Charging software. Security Guide. Simulation Tool) Configuration of the BART Server Settings of the BART Server for the CDR acquisition. transaction in files Configuration of the User Interfaces Settings for the all the tools (Desktop Tool. BART Tool. tax Configuration of the Transaction Persistency Settings for charged items in files. jobs Configuration of the Diameter Server Settings of the Diameter Server for the service dictionary and the AVP dictionary . transactions in files Configuration used for SAP Convergent Invoicing Settings for charged item in files. It provides the implementation tasks to plan by the project team during the implementation phase. Technical Operation Manuals or Upgrade Guide. This document contains the following main sections: Configuration of the Technical Services Settings of the Core Server for licenses. rating and charging sessions. It is therefore intended for the following audiences: Technology consultants System administrators Solution consultants Support specialist This document is not included as part of the Installation Guide.This document contains both high-level information on an application and business process level as well as very detailed technical information. referred to as SAP CC in this document. master data. It details the configurations of all the Master Data. Such guides are only relevant for a certain phase of the software life cycle. It gives some hints for main configuration parameters for business functions and technical functions.

Configuration of the Import/Export Connector (IEC) Settings for scenarios The table below shows the list of abbreviations used throughout this document. Abbreviation BIT BART CAT CC CCCIT CCA CCR CDR CI CIF CIT CT EIF GC GUI HA HCI HTTP HTTPS IEC JRE JVM MB RDBMS RIF TIF SDK Meaning Billable Item (SAP Convergent Invoicing) Batch Acquisition and Rating Toolset Connector Administration Tool SAP Convergent Charging (SAP CC) Convergent Charging Charged Item See the chapter about the configuration for SAP CI [page Credit-Control Answer Credit-Control Request Consumption Detail Record (SAP CC BART Sever) SAP Convergent Invoicing (in SAP ERP system) See the chapter about the configuration for SAP CI [page ] ] ] Charged item Integration Framework See the chapter about the configuration of the transaction persistency [page Charged Item Communications Taxing Exportable item Integration Framework Garbage Collection Graphical User Interface High Availability HTTP Communication Interface HyperText Transfer Protocol HyperText Transfer Protocol Secure Imort/Export Connector Java Runtime Environment Java Virtual Machine (JRE) Mega Bytes (different from Mb: mega bit) Relational Database Management System Rerating Integration Framework Transaction Integration Framework See the chapter about the configuration of the transaction persistency [page Software Development Kit ] .

SLD UI URL VAT XML System Landscape Directory User Interface Uniform Resource Locator Value Add taxes eXtended Markup Language .SAP CC provides several kits including API libraries.

delivered. a business scenario includes several company departments and involves with other business partners. This guide requires that the prerequisite software is installed as described in the SAP CC 2. It requires your knowledge about the software architecture and the key concepts of SAP Convergent Charging as described in the Technical Reference Guide from SAP Service Marketplace at the following location:  SAP Business Suite Applications  SAP Convergent Charging  SAP CC 2. CRM. see SAP Service Marketplace at the following location:  Install or  SAP Business Suite Applications  SAP Convergent Charging  SAP CC 2. Component A component is the smallest individual unit considered within the Solution Development Lifecycle. SRM.0  Plan . SAP SCM. which consists of several different interconnected logical processes in time. A business scenario is a unit which can be implemented separately and reflects the customer’s prospective course of business. This guide leads you through the process of performing the initial configuration of SAP CC 2.0  Install . components are separately produced. SAP Application An SAP application is an SAP software solution that serves a specific business area like ERP.0  Plan . a business scenario needs at least one SAP application (SAP ERP. SCM. or others) for each cycle and possibly other third-party systems. You can find the latest version of the relevant Master Guides from SAP Service Marketplace at the following location:  SAP Business Suite Applications  SAP Convergent Charging  SAP CC 2. It can be used for other industries. Typically. PLM. From a technical point of view. a business scenario is a cycle. installed and maintained. For a complete list of the available installation and configuration guides.0 Installation Guide. The following SAP product version and instance is mandatory for the technical implementation of SAP Convergent Charging software: .0.This Configuration Guide contains information about the settings that are required for the business scenario Convergent Charging. Business Scenario From a microeconomic perspective. CC.

Simulation Tool Simulation Tool X X This component is recommended for providing US telecommunication tax calculation services to SAP Convergent Invoicing in the SAP ERP system. . BART Server based on NW AS Technology BART SDK Java libraries BART Tool BART Tool BART+ Tool Diameter Server based on NW AS Technology Diameter Server X This component is mandatory for providing real time credit control services (via diameter protocol) to your network element or application.0 Software Component Instance .Applications Core Server based on NetWeaver Application Server Technology Core Server Instances Setup Tool Configuration Tool Optional Mandatory Core SDK Java libraries X This component is recommended for sending usage events to be charged to the Core Sever from a Java based application. It is also used for the provisioning services. Core Tool Desktop Tool Admin+ Tool Mandatory for configuring the Core Server X These components are recommended for providing batch mode rating and charging services to your network element or application. Communications Taxing Server based on NW AS Technology CT Server IEC Import/Export Connector Import/Export Connector Server X These components may be used with BART components for the offline charging services IEC Tool CAT (Communication Administration Tool) Consult the Master Guide for the software component matrix to know which software components to use for your business scenario.SAP CC 2.

interfaces. but enables you to refer to external postpaid balances stored in a third-party billing system. where the customer invoice is created. families.0 also provides credit limit management. .0 does not manage customer postpaid balances internally. With a low TCO. and so on) using any form or combination of payment methods such as prepaid.0 runs on a single system with a single customer base. and uses a single set of processes. postpaid or hybrid SAP CC 2. At the time of charging. and operational procedures. SAP CC 2. A credit limit allows your customers to limit the usage of one or more services within a given period of time. companies. and then forwards them to a billing system. the service is no longer accessible until the beginning of the next period. this system enables you to manage all your customers and services.Scenario With SAP Convergent Charging 2.0 generates charged items. SAP CC 2. the system provides credit control for these limits. such as SAP Convergent Invoicing.0 you can charge: Customers for services Different types of customers (individual. When the limit is reached. that is. Credit limits are managed in the same way as prepaid balances.0 provides real-time credit control so that you can: Control services and manage prepaid balances in real time by checking balances before delivering services to the customer Notify the customer when a balance threshold is reached Terminate the service session when the balance is depleted SAP CC 2. SAP CC 2.

It enables you to see all your SAP systems and to manage them. the reserved credit is refunded. the usage event is not sent. right-click the instance or the server you want to stop and choose Stop. for example.0. The same procedure is available for all the servers of SAP CC: Core Server based on NetWeaver Application Server Technology BART Server based on NW AS Technology Diameter Server based on NW AS Technology Communications Taxing Server based on NW AS Technology Windows The SAP Management Console (sapmmc) was installed during the installation of SAP CC 2. When a customer uses a service. Use the same procedure to stop the servers. Click the SAP system containing the server you want to start. Other Operating Systems . A network element or an application can interact with the system to: Deliver a service and send a usage event to the system. The usage events are then converted into chargeable items. After processing the chargeable items. Right-click the instance or the server you want to start and choose Start. the system generates charged items. Send a usage event before delivering a service. The system converts only postpaid charged items into billable items and then sends them to SAP Convergent Invoicing. GGSN. This business process also provides credit reservation management when credit authorization is requested. However. If the service delivery fails. For the last step. Send a usage event and ask for credit authorization. A usage event can be a ringtone download. the system can reject the usage event even if the service delivery succeeds. or a voice call. the sending of an SMS. A prerequisite for this is that the quantity of service used is known before the delivery. To start a server of SAP CC: Double-click the icon on your computer desktop to start the SAP Management Console. If the service is delivered. otherwise. which is not the case for session-based services such as voice calls or GPRS sessions. SCP. the network element or application that delivers it sends usage events to the system. and MMSC in the telecommunications industry) or from application servers.Business Processing You use this business process to charge customers for usage events that come from network elements (for example. This avoids the event being rejected but requires that the service delivery is always successful. the credit is deducted from the account balance.

Start the Tool On Microsoft Windows operating system. stop.sh script from the directory: /usr/sap/<SYSTEM_ID>/CCD<instance_number>/script/ where <instance_number> is the number automatically assigned to the Dispatcher instance by the system Connect and Log On .. select the Execute. NOTE Do not use the Admin+ Tool for stopping an instance of the server because it will be automatically restarted. Launch the admin+.bat script from the directory: C:\usr\sap\<SYSTEM_ID>\CCD<instance_number>\script\ where <instance_number> is the number automatically assigned to the Dispatcher instance by the system On UNIX operating system.. The main functions of admin+ allow you to: Connect to the server (command: host) Log on to the server Get the list and details about the known instances of the server (command: list) Get server properties (command: get) Set server properties (temporary changes or permanent changes) Manage batch rating groups Reset cache. Use the following options: -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) -function: to specify the command to apply to the server (start. Launch the admin+. SQL connections.Use the sapcontrol program to start and stop the servers. sub-menu and type: cmd in the new displayed popup window. The changes are not immediate and some instances of the Core Server must be restarted manually. the administrator opens a console to type the commands and verify the results. This program is installed in the /usr/sap/hostctrl/exe directory. This tool is included in the CC Core Tool component. the administrator opens a CMD/DOS console to type the commands and verify the results. In the Start main menu of MS Windows. and so on) -nr: to give the number of the SAP instance Admin+ Tool The Admin+ Tool is a console utility that gives you the possibility to manage local or remote instances of the Core Server by changing their parameters. user work sessions The use of all these commands is detailed in this guide.

The tool is ready to accept commands. type host Enter the host name where a Dispatcher instance of the Core Server is started Enter the port number used by this instance Type the command user Enter your login as administrator (default login: admin) Enter your password The Admin+ Tool displays the prompt ’[myhost] Instance_id>’. Getting Help You can use the help command for listing the available commands and getting help on a particular command. Type help set to display information about this command.The Admin+ Tool communicates with the Dispatcher instance(s) of the Core Server via the XML/HTTP protocol. Commands Command debug Description Advanced (for troubleshooting): Activates the DEBUG mode of the Admin+ Tool to trace the messages exchanged by admin+ with the instances of the SAP CC Core Server See also: normal command delete_user_session Deletes a user work session after a system failure of the graphical user interface See also: search_user_session command dump Advanced (for troubleshooting): Shows the thread dump of an instance of the SAP CC Core Server get Gets the value of a server parameter or gets the list of available parameters See also: set and reset commands groupadd Creates a batch rating group See also: groupadd command groupdel Deletes a batch rating group See also: groupadd command grouplist Lists all the batch rating groups See also: groupadd command groupmod Modifies a batch rating group . Once you have started the Admin+ Tool.

a charge. therefore. offer management When an end-user or an operator has modified or created an object such as an offer. as administrator. a few minutes are needed to update the rating services. a translation table or a pricing macro. NOTE Consult the Operations Guide for details about the maintenance of the Taxer instances of the Core Server. you can recover a normal situation by using the refresh_sql_connection command: SAP CC will switch all the connections back from the backup instance(s) to the primary instance(s) of Oracle RAC. if he needs to update the system quickly when working in test or training environment for example. This command updates the Updater instances of the Core Server. When the database primary instance is repaired after a down time.See also: groupadd command help host id list logs normal Displays the available commands Specifies the host name of the machine you want to connect to plus its port Shows current user and host List and summarize all the instances of the Core Server Get the last server logs Advanced (for troubleshooting): De-activates the DEBUG mode of the Admin+ Tool and comes back to the default normal mode See also: debug command output ping quit rc refresh_raters Redirect the output to a file Test the connection to an instance of Core Server Stop the Admin+ Tool Advanced: Reset the subscription data cache Scope: Troubleshooting. refresh_tax_cache refresh_transerv_list VAT Update the transaction service types from BillSoft EZTax that are displayed by the Desktop Tool of SAP CC. the operator sometimes forget to use the command Refresh Rating Instances in the Desktop Tool. you can force the refresh. In this case. . refresh_sql_connections Scope: Management of the failover between your database primary instance(s) and your database backup instance(s) of Oracle RAC.

stop_activation stop_cleanup unlocksub unlocksubs url Stop the activation process if it is running in the Core Server Stop the cleanup process if it is running in the Core Server Unlock a subscription Unlock a set of subscriptions Specify directly the URL of the instance of the Core Server to connect to See also: host command user Log on and authenticate Setup Tool . start_activation Triggers the recurring fees and the one-shot fees for all subscriptions This command freezes your Admin+ Tool until all the subscriptions have been activated by the Core Server. you have to launch another Admin+ Tool and use the stop_activation command. start_cleanup Triggers the cleanup processing by inspecting all the subscriptions that are implied into a prerate or postrate operation This command freezes the Admin+ Tool until the entire cleanup is done. See also: stop_activation command NOTE In order to stop the activation. you have to launch another Admin+ Tool and use the stop_cleanup command. NOTE Consult the help about scope for details about temporary changes (in memory) and permanent changes (persistent scope). See also: stop_cleanup command NOTE In order to stop the cleanup.reset Reset a parameter to its default value See also: get and set commands server set Manage the instances of the Core Server Set the value of a parameter temporary in the memory of a system or in a permanent and persistent mode (value stored in the database for the next restart of the system).

This tool is included in the Core Server component. It communicates with the Core Database. Configuration Tool The Configuration Tool is a command line program that helps you manage the Core Server by changing its configurations directly in the Core Database. The changes are not immediate and some relevant instances of the Core Server must be restarted.bat or *. The changes are not immediate and some relevant instances of the Core Server must be restarted according to your actions. Getting Help . Execute the Tool The Setup Tool is available from the Dispatcher instances in the installation folder.The Setup Tool is a command line program that helps you manage the Core Server by changing its configurations directly in the Core Database. The main functions allow you to: Manage the licenses – for all instances Manage the certificates and the key entries for secured HTTP service Manage the notification policy Manage the CIF configuration – for the Rater and Bulkloader instances Manage the RIF configuration – for Rater instance Manage the SAP CI (ERP) configuration – for the Updater instance Manage the VAT taxation policies Manage the EZTax transaction/service types The use of all these commands is detailed in this guide. Getting Help You can use the help command for listing the available commands and getting help on a particular command. Execute the setup script (*. The main functions allow you to export and import the complete configuration of the Core Server. This tool is included in the Core Server component.sh) with the correct arguments. Connect and Log On The tool does not manage any user work session so each command must be authenticated with a user login and password. Go to one of the following directories: C:\usr\sap\<SYSTEM_ID>\CCD<instance_number>\script\ (MS WINDOWS) /usr/sap/<SYSTEM_ID>/CCD<instance_number>/script/ (UNIX) where <instance_number> is the number automatically assigned to the Dispatcher instance by the system.

Task Start always working by exporting the configuration in a file Use the command: config configuration export Set up your changes in the file Import the configuration file Use the command: config configuration import Restart the relevant instances of the Core Server Bart+ Tool The Bart+ Tool is a console utility that helps you manage the BART Server of SAP CC by changing its parameters.sh script from the directory: .. the administrator opens a console to type the commands and verify the results. Launch the bart+. In the Start main menu of MS Windows. select the Execute.You can use the help command for listing the available commands and getting help on a particular command. The main functions allow you to: Get or set the BART Server parameters values Update the BART Server log level Monitor the acquisition sessions Intercept messages and redirect them to a specified file Ping the BART Server The use of all these commands is detailed in this guide. Execute the Tool The Configuration Tool is available from the Dispatcher instances in the installation folder. sub-menu and type: cmd in the new displayed popup window. Go to one of the following directories: C:\usr\sap\<SYSTEM_ID>\CCD<instance_number>\script\ (MS WINDOWS) /usr/sap/<SYSTEM_ID>/CCD<instance_number>/script/ (UNIX) where <instance_number> is the number automatically assigned to the Dispatcher instance by the system. Start the Tool The administrator opens a CMD/DOS console to type the commands and verify the results. Launch the bart+.bat or *. Execute the config script (*.bat script from the directory: C:\usr\sap\<SYSTEM_ID>\CAB<instance_number>\script\ where <instance_number> is the number automatically assigned to the BART Server instance by the system On UNIX. Connect and Log On The tool does not manage any user work session so each command must be authenticated with a user login and password. It communicates directly with the Core Database.. The changes are not immediate and some relevant instances of the BART Server must be restarted.sh) with the correct arguments. This tool is included in the BART Server component.

0 in your landscape: Software Component Core Server Implementation Tasks Determining the sizes of the data caches Implementation of the notification handler Chargeable Item Acquisition Master Data Provisioning (Subscriber Accounts) Master Data Provisioning (Subscription and Accesses) Setting up the default field mapping between CIT and BIT Implementation of the rerating function Java Development? Yes Yes Opt. Yes Java or other technology BART Server CDR Acquisition Implementation of the supervision function Diameter Server Setting up the Service Dictionary Setting up the AVP Dictionary Communications Taxing Server IEC n/a Implementation of Java Classes for adding functions n/a Yes Yes . Once you have started the Bart+ Tool. type host Enter the host name where a BART Server is started Enter the port number Type the command user Enter your login as administrator (default login: admin) Enter your password Getting Help You can use the help command for listing the available commands and getting help on a particular command. The following implementation activities may be scheduled for integrating SAP Convergent Charging 2./usr/sap/<SYSTEM_ID>/CAB<instance_number>/script/ where <instance_number> is the number automatically assigned to the BART Server instance by the system Connect and Log On The Bart+ Tool communicates with the BART Server via XML/HTTP. Opt.

see the quick links as shown in the table below.All these tasks are described in this document. Content Security Security Guides Related SAP Notes Released Platforms SAP Solution Manager Installation & Upgrade Documentation SAP Convergent Charging Information Center Information Centers of SAP CC are available from Service Marketplace at:  SAP Business Suite Applications  SAP Convergent Charging Quick Link on SAP Service Marketplace . SAP Note Number Title CA Wily Introscope Installation for SAP Customers The following table lists where you can find more information about SAP CC 2. Lifecycle Phase Implementation Implementation Implementation Configuration Guide Operation Operation Operations Guide Operate  Operations Guide  Install  Configuration Guide Document Technical Reference Guide Sizing Sheet Location  Plan  Technical Reference Guide  Plan  Sizing Sheet  For more information about specific topics.0 features and functions from SAP Service Marketplace or from the SAP Help Portal.

0 Core Server based on NW AS Technology. Procedure Go to one of the following directories: C:\usr\sap\<SYSTEM_ID>\CCD<instance_number>\script (MS WINDOWS) /usr/sap/<SYSTEM_ID>/CCD<instance_number>/script/ (UNIX) where <instance_number> is the number automatically assigned to the Dispatcher instance by the system. see Marketplace.txt stored in one of the following directories on any host: C:\usr\sap\<SYSTEM_ID>\SYS\profile\ (MS WINDOWS) /usr/sap/<SYSTEM_ID>/SYS/profile/ (UNIX) Install the Permanent License Use You must use the license. The default values that are used in the setups are very low. The memory allocated to the JVM must be customized for each instance to ensure high levels of performance.0 must be able to accommodate a wide range of hardware.This chapter lists the configurations of the SAP CC 2. from a basic laptop up to 64-CPU machines. Temporary licenses can be set up at installation time and must be replaced by valid license keys. so that the system can be installed on a small configuration without any modification. Type the following command: setup license import <license_file> where <license_file> is the path to the file containing the license.0 is protected by licenses. The hardware keys are written in a file called hardware_keys. . Apply for the Permanent License Use To obtain a permanent license key. A license key file is necessary for each host machine of your system landscape. SAP Convergent Charging 2. The default values are generally not suitable for a production environment. on SAP Service You need to indicate the hardware key for each machine hosting an instance of the Core Server when applying for a permanent license. on any machine hosting a dispatcher instance to install the permanent SAP Convergent Charging 2.

you must change the values of the data cache sizes to take into account the business traffic supported by SAP CC 2. The memory set for the caches must not exceed the value of MaxDirectMemorySize. you need to set the JVM command line option: -XX:MaxDirectMemorySize=<Max usable memory on the host machine dedicated to this instance> When several instances of the Core Server are installed on the same host in your system landscape.0 uses data caches for optimizing all the processes and increasing performance. CAUTION The memory set for the data caches must not exceed the value of MaxDirectMemorySize. For other instance types. split the available memory. we give recommendations for sizing the JVM used by the Rater instances. Setting up the Memory for a Rater Instance Use To be able to set large value for the data caches of SAP CC 2.0. SAP Convergent Charging 2. In this case the process will end with an OutOfMemory error.NOTE In this section. Prerequisites These sizes have been determined on a test platform during the implementation phase (see the implementation section in this chapter). Setting up the Cache Sizes Use At post-installation time of the productive landscape. Procedure Launch the Admin+ Tool Log on as administrator For each Updater instance of the Core Server Change the value of the SUBSCRIPTION_CACHE_SIZE parameter according to the cache sizing results For each Guider Instance Change the value of the GUIDING_CACHE_SIZE parameter For each Rater instance . consult your consultants. In this case the process will end with an OutOfMemory error.0.

configure the security policy for user passwords. By default.0 allows you to manage the profile of each user and their roles or rights. Setting up the Security Policy for the User Passwords Use You can configure all the security parameters by taken into account the global recommendations of SAP presented on SAP Service Marketplace at: . m or M for megabytes and g or G for gigabytes Or use a number without letters to express the size in bytes SAP Convergent Charging 2.0 allows you to configure and apply a security policy for managing the user passwords.Change the value of the SUBSCRIPTION_CACHE_SIZE parameter Change the value of the SESSION_MEMORY_SIZE parameter when applicable Restart all the instances of the server NOTE For setting the sizes of the caches. this function is enabled at installation time. Procedure Launch the Connect to the Core Server with the host command Log on as administrator with the user command Change the PASSWORD_MANAGEMENT_ENABLED parameter to true or false If you enable this function. Only positive integer values are allowed . you can: Use a number immediately followed by k or K for kilobytes.0  Install for user management information. You can also configure the rules for changing passwords.0 directly from SAP Service Marketplace at:  SAP CC 2. Enabling/Disabling the Security Policy for the Users Use SAP CC 2. Processing Mode Password Mandatory Password Different from Login Password Minimum Length Value Passwords are always mandatory The password must be different from the login (user name) You can specify the minimum length allowed for the passwords. Consult first the Security Guide of SAP CC 2.

"digit" and "special" NOTE An empty list means that there is no restriction on the complexity of the password.0 is protected by dedicated login/password management functions. after which it is expired and must be changed NOTE The value 0 means that there is no expiration delay for the passwords. digits and special characters. Procedure Launch the Admin+ Tool Log on as administrator Change the security parameters according to your security strategy Setting up the Users Use SAP CC 2. It is possible to force the use of upper case letters. you must create a user for it. "lowercase". and they do not need to be changed. lower case letters. Password Failed Login Limit You can specify the maximum number of failed logins allowed. If you have installed the BART Server. CRM). You have to set up such users and configure their roles by using the Desktop Tool. Password Complexity You can specify the type of characters that must be present at least once in the password. Password Duration Limit You can specify the time limit of the expiration period (in days) of a password. after which the user is locked and cannot be used anymore until an administrator unlocks it NOTE The value 0 means that there is no limit to the number of times a user can enter a wrong password. Parameter format: It consists of a comma separated list that can contain the values "uppercase".NOTE The value 0 means that there is no lower limit to the length of the passwords. . NOTE You must also create users for the network elements or service applications that communicate with SAP Convergent Charging (mediation system.

USER_RIGHT) VALUES (1. INSERT INTO USER_RIGHT(USER_OID. launch the Admin+ Tool. '0'. you can re-activate the emergency user for SAP CC 2.0 for the users connected to a graphical user interface. 'useradmin').Consult online help of the Desktop Tool from the SAP Help Portal at:  SAP CC 2. 'admin'. with password 'admin'. and administrator privileges directly in the database of SAP CC 2. DELETE FROM USER_PASSWORD WHERE USER_OID = 1. 'admin'). FAILED_LOGIN_COUNT. IS_HUMAN) VALUES (1. Setting up the User Work Session Management Use Multi or mono work sessions can be managed by SAP CC 2. USER_RIGHT) VALUES (1. INSERT INTO USER_RIGHT(USER_OID. Online help is directly accessible from the graphical user interface. LOCKED. LOGIN_ID.0  Desktop Tool . PASSWORD. '0'. DELETE FROM USER_RIGHT WHERE USER_OID = 1. Procedure This emergency procedure resets the default user 'admin'.0. . PASSWORD_CHANGE_DATE. '6989cd27e1ebb4d8f266d5c09469989f1caae07'. You have to configure this function by defining the number of allowed connections to the same GUI and the time limit for a work session. Procedure Launch the Desktop Tool Log on as administrator or user administrator Create the users and assign roles Resetting the Emergency User Use In emergency situations where you configured user management incorrectly and can no longer log on to any applications. Connect on the database with sufficient privileges to modify tables on the schema used by SAP CC. Procedure Launch the Admin+ Tool Log on as administrator Change the USER_SESSION_ENABLED parameter to the appropriate value Change the values of the USER_SESSION_SESSION_LIMIT_PER_USER_AND_TOOL and the USER_SESSION_VALIDITY_PERIOD parameters CAUTION For resetting a crashed working session. USER_RIGHT) VALUES (1. INSERT INTO USER_RIGHT(USER_OID. 'bartadmin'). NULL. '1').0. Use the following SQL queries: DELETE FROM HCI_USER WHERE OID = 1 INSERT INTO HCI_USER (OID.

config Change the value of the BOOT_DISPATCHER_LIST parameter by inserting the URL and port of the Dispatcher instances Remove the values of the following parameters: DISCOVERY_MULTICAST_ADDRESS DISCOVERY_PORT Restart the Master Dispatcher instance Restart the other Dispatcher instance(s) Restart the other instances of the server Resetting the Login and Password for the Database Use For test or development purpose.0.config file present in each installation of a Dispatcher instance in the folder: usr/sap/<SYSTEM_ID>/<INSTANCE_TYPE><INSTANCE_ID>/config/boot.config and stored on each instance of the Core Server. If the network configuration does not permit this function. In a productive landscape. CAUTION You must stop all the instances of the Core Server of SAP Convergent Charging for these changes.0 uses a discovery function based on UDP protocol for detecting the available Dispatcher instances of the Core Server. this should be avoided. Disabling up the UDP Discovery Function (Post Installation) Use By default. CAUTION You must stop all the instances of the Core Server of SAP Convergent Charging for these changes. SAP CC 2.The initial communication settings of SAP Convergent Charging 2. Procedure Stop all the instances of the Core Server Change the login and password in the database Identify the installation folder(s) of all the Dispatcher instance(s) Change the login/password declaration stored in the boot. you can change the login and password of the database after the installation of SAP CC 2.config .0 are stored at the end of the installation time in files named boot. Procedure Stop all the instances of the Core Server Identify all the Dispatcher instances and their URL and port Edit all the boot.config files present in each installation of an instance in the folder: usr/sap/<SYSTEM_ID>/<INSTANCE_TYPE><INSTANCE_ID>/config/boot. you can manually declare and maintain the list of available Dispatcher instances.

When needed by your business.0 can regularly send information data to the SLD.0 can send information about installable and installed components of your system landscape.0. By default. The following data are available: Incoming data: Master data: subscription. It updates regularly the System Landscape Directory (SLD).0  SAP NetWeaver 7. subscriber accounts Transactional data: chargeable items (Core Server). the connected systems and the architecture of the landscape are responsible for managing the required date format conversions from and to SAP CC 2. Procedure Launch the Connect to the Core Server with the host command Log on as administrator with the user command Change the SLD_SCHEDULER_ENABLED parameter to true . billable items. Consult online the documentation of SLD directly from SAP Help Portal at:  SAP NetWeaver 7. this function is not enabled at installation time. rated transactions.0 manage all the dates in local time. charged transactions.0 Library (English)  SAP NetWeaver Library  SAP NetWeaver by Key Capability  Solution Life Cycle Management by Key Capability  Software Life Cycle Management  . charges Transactional data: charged items. CCRs (Diameter Server) Outgoing data: Master data: offers. CCAs (Diameter Server) SAP Convergent Charging 2.Restart the Master Dispatcher instance Restart the other Dispatcher instance(s) Restart the other instances of the server Setting up the Time Zone and Date Management (Implementation) Use The applications of SAP CC 2. Prerequisite A SLD server is up and running.0. CDRs (BART Server). the implementation must take into account the management of the time zones outside SAP CC 2. Activities When relevant. Enabling the SLD Data Supplier Function Use SAP CC 2.

You can define the communication settings and the time period between two updates of SLD.0.Set up the other relevant parameters as described in the next section Restart all the Dispatcher instances of the Core Server Setting up the SLD Data Supplier Function Use You have to configure manually SAP CC 2. It is available in the Software Development Kit (SDK) or from SAP Service Marketplace at the following location:  SAP Business Suite Applications  SAP Convergent Charging  SAP CC 2.0 to connect to the SLD and send periodically data. Procedure Launch the Connect to the Core Server with the host command Log on as administrator with the user command Change the communication and scheduling parameters to the appropriate values: Communication Parameters SLD_URL SLD_USER SLD_PASSWORD The SLD server URL: http://<HOST>:<PORT>/sld/ds The username for the log on to the SLD The password for the username Scheduling Parameter SLD_SCHEDULER_RECURRENCE Recurrence pattern for the scheduler in charge of sending updates to the System Landscape Directory By default this parameter is set to every day at 1:00 AM Restart all the Dispatcher instances of the Core Server NOTE Consult the Parameter Reference for more information about the syntax for the value of the . Prerequisites A SLD server is up and running. . The SLD data supplier function is activated in SAP CC 2.0  Install .

and the notifications are configured in the Notification Policy which is configured in an XML file that must be imported into the database. The feature uses the BARBus communication layer on the LAN. ABM notifications are alerts that are triggered when an account balance level goes below a specified threshold. Notifications .highdeal.). NOTE Consult the Technical Reference Guide for more information about the BARBus communication layer. Note that this group includes also alert that can be defined in price plan and charging plan by using the .notification Java package for implementing the notification framework.SAP Convergent Charging 2.. Notification Policy An administrator can define the rules for publishing notifications by setting up a notification policy. Your application can handle these notifications by implementing the Java framework.0 provides a framework based on Java APIs for implementing this feature in your client application. Consult also the Javadoc from the Core SDK for implementing the notification framework in your application.0 features notifications and alerts at business level and at administrative level that allows you to monitor events and receive alerts or notifications when these events occur. Overview of the Function Notification Groups The event types that generate notifications are defined in the following notification groups: ABM Group: trigger some Account Balance Management level notifications that are published on the network. Use the Desktop Tool to configure the alerts as part of the subscriber account settings (refer to the for more information about the alert settings for credit limit balances and prepaid accounts). Administrative Group: trigger some Admin notifications related to the connections between the systems (database. and when an account has expired. SAP CC 2. Implementation You need to use the Java APIs of SAP CC 2. All the instances of the Core Server have the same notification policy. instances of the Core Server.0 and its com. The event types are organized into Notification Groups. . The implementation project is detailed in the next Implementation section.. This policy defines: The filters that can be applied for limiting the internal events that will generate a notification The outputs for these notifications Notification Output The network notification service is used for publishing both the ABM notifications and the administrative notifications.

e. EXPIRATION_ALER T/1 inform Prepaid account USER_ALERT / 12 inform Price plan or charging plan You can get the last list of notifications from the Core SDK in the Javadoc.ABM Notifications The Account Balance Management (ABM) notifications are described in the following table: Notification Name / ID ALERT_AMOUNT / 0 Level inform Scope Prepaid account or a credit limit balance Description Thrown when an amount alert is triggered i. when a prepaid account or a credit limit balance falls below alert amount threshold The following information is provided: The service provider of the subscriber account The code of the subscriber account Is "prepaid" or "creditLimit" if the related balance is a prepaid account or a credit limit balance The code of the balance for which an amount alert has been triggered The amount of the balance with its currency The user message of the alert The amount threshold of the alert Thrown when an expiration alert of a prepaid account is triggered The following information is provided: The service provider of the subscriber account The code of the subscriber account Is "prepaid" or "creditLimit" if the related balance is a prepaid account or a credit limit balance The code of the balance for which an amount alert has been triggered The user message of the alert The state related to the alert Thrown when a user defined alert is triggered This message includes: The code that identifies the user alert The message describing the user alert The service provider of the subscriber account The code of the subscriber accountA list of properties that give additional information about the user alert Use the to configure your own alerts by using the in a charge. topic of the Core Administrative Notifications The following notifications can be sent by: .

dbLinkDown / 4 failure common The instance of the Core Server has lost its connection with its database There are several reasons: The database is stopped (accidentally or voluntarily) The network interface is down The instance cannot contact the database host because of a network problem (firewall configuration. …) This trap is not thrown at the instance launching time if the instance cannot contact the database because of a wrong configuration. pnrShedulerWakes Up / 8 pnrShedulerSleep s/9 inform common The Updater instance scheduler wakes up. The scheduler starts a new activation cycle. The Updater instance scheduler has been interrupted. The environment of the instance prevents the scheduler to complete its cycle (activation has failed. dbLinkUp / 5 outOfMemory / 7 inform fatal common common The instance of the Core Server has opened new database connections The instance of the Core Server has been stopped because its JVM has thrown an OutOfMemoryException Sometimes the trap won’t be sent because the JVM has not enough memory to process the trap. The trap has the argument “alertMessage” set with the reason of the interruption. It means that it is waiting for its next activation cycle. wrong password) The trap has the argument “alertMsg” set with . pnrShedulerInter rupted / 10 inform Updater instance authenticationFa ilure / 11 security common An XML message has been received without a valid authentication (unknown login. inform Updater instance The Updater instance scheduler sleeps.Notification Pretty Name / ID instanceUp / 2 instanceDown /3 Level inform inform Availability common common Description The instance of the Core Server is running The instance of the Core Server was manually stopped This trap may not be sent when the instance crashes. problem of memory …).

dbFailure / 6 failure common The database has returned a failure exception The trap has the argument “alertMessage” set with the reason of the problem. with “no login” otherwise. It includes a main XML element ( notificationPolicy) that can include two nested elements: filters and network. do the following: Define your notification policy concept Create the notification policy configuration file (xml format) Enable the function Restart the Core Server (all instances) Defining a Concept for the Notification Policy By default all the notifications are sent. topics of the Core Setting up the Notification Policy Function Prerequisites The notification function has been implemented in your landscape by your project team and consultants. admin) and if you want to filter some notifications. Activities To set up the notification policy. You have to decide if you want to limit the notifications from a group (ABM. You can get the last list of notifications from the Core SDK in the Javadoc. It has also one argument “alertData” set with the login if specified.“unknown login” or “wrong password”. Creating a Notification Policy Configuration File Use A configuration file (XML format) is used to define the notification policy. Nested Element filters all accept Nested Element Attribute Description Enables/disables all the notifications Possible values are: true (default) false (optional) .

0 can regularly send notifications to connected Java applications. 'failure'.admin Prerequisites You have determined a concept for the notification policy management The notification function has been implemented in your landscape by your project team and consultants Procedure To create a new configuration file: Edit the notification_policy. . By default. 'fatal' Specify the notification groups that will send notifications Possible values are: abm admin abm. this function is not enabled at installation time.xml.range accept Enables/disables the notifications with the ID within a defined range [lower. 'security'.sk file from the configuration folder of the Core Server Insert your settings according to the XML format Save your file as a new file Enabling the Notification Policy Function Use SAP CC 2. 'warn'. upper] Possible values are: true false Lower ID of the range Upper ID of the range Enables/disables a notification specified by its ID lower upper set accept id name accept pattern prettyName accept pattern level accept lowerLevel network groups Enables/disables the notifications by their name A regular expression about the name of the notifications Enables/disables the notifications by their pretty name A regular expression about the name of the notifications Enables/disables the notifications by their level Level values are: 'inform'.

It is impossible to guess the average size of the objects to cache because it is different for every SAP CC 2./CONFIG/MYNOTIFICATIONPOLICYFILE. That is why the instances of the Core Server are first started with a predefined size and why this should be fine configured. relevant pricing objects (offers and suboffers. Use This section explains how you can manually size these caches. EXAMPLE NOTIFICATIONPOLICY IMPORT .000 customers and to create all relevant and necessary business objects: 1.0 has three different caches which must be sized according to the volume of data (master data or transactional data): Subscription Cache Access Cache Rating Session Cache This cache is not used if the Business Scenario does not use the session-based rating and charging services of SAP CC NOTE Other caches such as the offer level cache exist but they are automatically sized.000 subscriber accounts.000 subscriptions. start the Setup Tool and use the notificationpolicy command with the import option.XML Restart all the instances of the Core Server Determining the Sizes of the Data Caches SAP CC 2.Prerequisites You have created a configuration file for your notification policy The notification function has been implemented in your landscape by your project team and consultants Procedure To import your policy from a file: From a Dispatcher instance. 1. The recommended method is to simulate the presence of 1. charges with price plans and charging plans including pricing macros or tier or translation tables). . This simulation is important and must model the future usage of the platform. Consult the Technical Reference Guide for details about the caches structures.0 platform.. The best way to determine the size of a cache is to have a sample of objects contained in the cache and determine the average size of these objects.

Rater. Taxer when relevant) with the default values for sizing the cache Write down the size S1 and the free memory FM1 for each cache and for each instance type Launch the Admin+ Tool Connect to the Core Server with the host command Log on as administrator with the user command Use the get command with the following parameters: SUBSCRIPTION_CACHE_SIZE. Guider. GUIDING_CACHE_SIZE and SESSION_MEMORY_SIZE Write down the current sizes of the data caches: Subscription cache. To sum up. Divide the previous result by the number of objects you created in the cache and multiply the result by the number of objects you plan to have in the future Nf.Prerequisites The system is up and running. the cache size is estimated as follows: Or: Divide this result by the number of instances with the same type Use these values when configuring the productive landscape Implementing the Notification Handler in Your Java Application . Updater. If the size changed. calculate the difference between the free memory at first launch and the free memory at second launch ( ). Activities Size your caches manually by applying the following method for each cache type: Start an instance of each type (Dispatcher. Add the result to the first computed size: You obtain the size of your cache Increase S2 and the total size of the JVM with this number to avoid the memory for the cache to be taken from another cache or from the JVM.000 for example) to be stored in the caches: subscriber accounts and subscriptions and accesses Restart all the instances of the Core Server Write down the size S2 and the free memory FM2 again Compute the memory needed for the newly created objects: If the size of the cache did not change. See the following sections to know how you can modify the size of the caches and the memory for the JVM. You have determined a model for your Business Scenario. apply the following formula . access cache (GUIDING_CACHE_SIZE) and rating session cache (SESSION_MEMORY_SIZE) Use the get command with the following parameters: SUBSCRIPTION_CACHE_FREE_MEMORY. GUIDING_CACHE_FREE_MEMORY and SESSION_FREE_MEMORY Create No typical objects (about 1.

From the Core SDK, use the com.highdeal.notification package of the Java API of SAP CC 2.0 for implementing the notification handling. Perform the following steps to implement the notification handler for Balance Alerts in your Java based application. Implement the NotificationHandler interface Instantiate the NotificationServiceClient class Implementing the Notification Handler Interface Create your own notification handler implementing the
com.highdeal.notification.NotificationHandler interface. This interface has only one

method invoked each time a notification is received:
void handleNotification(String clusterName, int instanceID, long timestamp, int uid, String... args);

In this method you receive all the information about the notification: clusterName – the name of the cluster for which the instance which has sent the notification is belonging to. instanceId – The id of the instance which has sent the notification timestamp – The date when the notification has been sent uid – The unique identifier of the notification args – The arguments of the notification To get the description of the notification, invoke the method:
NotificationDescription desc = NotifBook.searchNotificationDescription(uid); String notifName = desc.getName(); String notifPrettyName = desc.getPrettyName(); NotificationLevel notifLevel = desc.getSeverityLevel(); String[] notifArgNames = desc.getAdditionalInfoKeys();

This description contains the name, the pretty name, the level of severity and the name of the arguments of the notification.

CAUTION
Note that the thread invoking the handler is the one listening on the socket. So it must be freed quickly by using a thread pool to handle the received notification, otherwise some notifications may be lost if the listening thread is busy. Consult the classes NotificationDescription and NotifBook that are detailed in the package com.highdeal.notification.

Instantiating the Notification Service Client After implementing the notification handler, make it listen with a Notification Service Client. Search the instance map of the cluster for which you have to receive the notification.
InstanceMap map = NotificationServiceClient.searchInstanceMap(bootHostName, bootPort, bootMode.HTTP_BOOT_MODE);

The arguments bootHostName and bootPort defined the boot instance to be contacted to have the instance map. Usually it is the address of the dataupdating instance. The argument bootMode.HTTP_BOOT_MODE declares that the protocol is the XML/HTTP. Instantiate a “com.highdeal.notification.NotificationServiceClient” and connect this client with all the instances of the cluster using the instance map and you notification handler.
client = new NotificationServiceClient(); client.setNotificationHandler(notificationHandler); //an instance of your notification handler client.addAllConnections(map); client.connect(null, 10000);

Each time an instance of the Core Server sends a notification using the notification service, your notification handler will be invoked.

Master Data Scenario Chargeable Item Class Charged Item Class

Config. Sequence 1 (opt.) 2 3

Page [ [ [ ] ] ]

Related Transactional Data CDR (In) Chargeable Item (In) Charged Item (Out) Charged Transaction (Out) Rated Transaction (Out)

Page [ [ [ ] ] ]

Billable Item Mapping Charge Offer Subscriber Account Subscription Access

4 5 6 7 8

[ [ [ [ [

] ] ] ] ]

Billable Item

Setting up the Public Holidays
Use The Desktop Tool is a component of SAP CC 2.0. You have to configure and maintain the list of public holidays relevant for your business. They are used in the logic components Public Holidays Splitter and Public Holidays Comparison when the power users design price plans and charging plans. At the installation time, it is recommended to verify and set the public holidays to use in your business. During the live phase, it is recommended to regularly maintain the public holidays. Consult online help of the Desktop Tool from SAP Help Portal at:  SAP CC 2.0  Desktop Tool . Online help is directly accessible from the graphical user interface. Procedure Launch the and log on Export the current public holidays Edit the XML file and add or create your own public holidays Import the file in the Desktop Tool. It will update the Core Server and the database: Desktop Tool  Tools  Public Holidays  Import .

Each group has a numeric identifier. Setting up the Precision and Rounding for Rating and Charging (Advanced) Use When required by your business scenario. groupmod and groupdel commands Setting up the Rerating Function Use By default the rerating function is disabled in SAP CC 2. Several parameters are available and can be fine configured.NOTE You have to restart all the other Desktop Tool programs to take into account the changes. Procedure Launch the Admin+ Tool Connect to the Core Server using the host command Log on as administrator using the user command Use the grouplist.0 and is not available in the Desktop Tool. Prerequisites It is not possible to remove or modify groups that contain subscriptions. . Procedure The technology consultant has to: Launch the Admin+ Tool Log on as administrator Set up the TRANSACTION_PRECISION and TRANSACTION_ROUNDING_MODE parameters Set up the TRANSACTION_DETAIL_PRECISION and TRANSACTION_DETAIL_ROUNDING_MODE parameters Set up the COUNTER_PRECISION and COUNTER_ROUNDING_MODE parameters Set up the TAX_PRECISION and TAX_ROUNDING_MODE parameters Setting up the Batch Rating Groups Use If you have BART components installed you may need to manage batch rating groups according to your business needs so the power users or the external systems (from a CRM) can create their subscriptions. This is the default group. a codename and a description. You can always change the descriptions of all the groups. You can change its code name and its description to suit your needs.0. groupadd. It is recommended to define the greatest possible number of batch rating groups (the maximum number of groups is 99). you can set up the precision and rounding mode for the calculations in SAP CC 2. The code name is used to select the group in the Desktop Tool when creating subscriptions. You have to define your groups according to your business. You cannot remove the group identified by 0.

rif.0. Procedure Launch the Connect to the Core Server using the host command Log on as administrator using the user command Change the value of the RERATING_ENABLED parameter to true so the menu is available from the Desktop Tool Change the value of the RERATE_PROC_CLASS parameter to com.chargeditem.highdeal.rif.dbFile.0  Plan . Consult the Technical Reference Guide from SAP Service Marketplace at the following location:  Plan or SAP Business Suite Applications  SAP Convergent Charging  SAP CC 2.config.sk file is provided as template.highdeal. The system can generate some files that must be taken into account by the third-party billing system to manage the invoices.Prerequisites The rerating function has been implemented in your landscape by your project team and consultants. This implementation is only possible for the following transaction persistency processing modes: Charged Item Files Data Files Prerequisites Your Business Scenario includes only postpaid accounts in a batch mode environment.RerateProcessorShell according to the transaction persistency processing modes (Data Files or Charged Item Files) Launch the Log on as administrator Import a RIF configuration file using the rif command NOTE A default rif. The BART components are installed and configured (see the chapter about the BART Server).xml. Implementing the Rerating Function Use By default the rerating function is not implemented in SAP CC 2.  Setting up Chargeable Item Classes . Activities Using the Technical Reference Guide you can determine the way for transmitting and parsing the generated files in a third-party billing system.rater.RerateFileProcessor or com.

Activities The technology consultant has to: Determine the relevant chargeable item classes Determine the necessary properties for each class Implement the transmission of those data [page ] Configure the chargeable item classes in SAP CC so that the power users can design charges including price plans that will use these properties for the rating calculation: Desktop Tool  File  New  Chargeable Item Package . Procedure Start the Desktop Tool and log on Create a chargeable item package and add chargeable item classes for a service provider Save the chargeable item package(s) in the database NOTE You can group the classes in one or several packages according to the business of the service provider. Online help is directly accessible from the graphical user interface. NOTE Some of these properties can be used by the invoicing process in a third-party billing system. you can configure its structure (list of fields) and the generation method of each field. Setting up Charged Item Classes Use By default SAP CC 2. Classes can be defined and reused in SAP CC. They are sent by the network elements or the service applications that deliver these customer services. Consult online help of the Desktop Tool from the SAP Help Portal at:  SAP CC 2. Prerequisites Implementation has specified the data which are sent to SAP CC for being rated and charged. Different classes of chargeable items can be transmitted. . A catalog must exist in SAP CC for the service provider.0 for charging the usage of a customer service. Each chargeable item class is defined by a set of properties.Use Chargeable items are received by SAP CC 2. For each class.0  Desktop Tool .0 outputs charged items as result of the rating and charging processes. These properties are used by the charging process when executing the price plan of the charges applying on a chargeable item class.

Desktop Tool  File Setting up Charges Use Charges are used by SAP CC 2. Online help is directly accessible from the graphical user interface. Activities The solution consultant and the power user have to: Determine the relevant fees and list the charges to be created. These fields will be computed by SAP CC when executing price plans in charges List the fields that need to be generated by a price plan because they are not calculated by default by SAP CC or because they are not present in the incoming chargeable item Procedure Start the SAP CC Desktop Tool and log on. The charges apply on certain chargeable item classes.0 for managing fees related to the usage of a customer service.0  Desktop Tool  About Charged Item Class . Prerequisites You have configured all the necessary chargeable item classes for being able to design price plans. Desktop Tool  File  New  Setting up an Offer Use . Create the new charges and save them in the database: Charge. Activities The solution consultant and the power user have to: Determine the classes of charged items that SAP CC must output for the invoicing process Determine the contents of these classes and the method for generating each field of a class. Configure the charges in SAP CC so that the power users can design commercial offers. Procedure Start the Desktop Tool and log on.Consult online help of the Desktop Tool from the SAP Help Portal at:  SAP CC 2.0  Desktop Tool  About Charges . Maintain these charges. Commercial offers can be designed by reusing charges. Create the new charged item classes and save them in the database:  New  Charged Item Class. Consult online help of the Desktop Tool from the SAP Help Portal at:  SAP CC 2. Each charge includes a price plan and a default charging plan. A charge includes a price plan and a charging plan that must be configured for being executed by the rating process and the charging process. Online help is directly accessible from the graphical user interface.

NOTE You can create manually a subscription via the SAP CC Desktop Tool for test or training purpose. Manually create the new subscriber account and save it in the database: File  New  Subscriber Account. NOTE You can manually create a subscriber account via the SAP CC Desktop Tool for test or training purposes. Procedure . Desktop Tool  File Setting up a Subscriber Account (Implementation) SAP CC 2. Activities The power user has to: Determine the relevant offers and sub-offers to be created Determine the complete list of charges to be inserted in these offers Configure the offers in SAP CC so the power users can design charges including price plans that will use these properties for the rating calculation.0 uses subscriber accounts for storing balance management and account information. Consult online help of the Desktop Tool from the SAP Help Portal at:  SAP CC 2.0  Desktop Tool  About Offers . Procedure Launch the SAP CC Desktop Tool and log on. Provisioning functions must be implemented between your CRM application and SAP CC in order to manage properly these data.0 uses subscriptions for storing balance management and account information. Online help is directly accessible from the graphical user interface. Create the new offers and sub-offers and save them in the database:  New  Offer. Desktop Tool  Setting up a Subscription and Accesses (Implementation) SAP CC 2. Prerequisites You have configured all the necessary charges and charged item classes. Provisioning functions must be implemented between your CRM application and SAP CC in order to manage properly these data.Offers are used by SAP CC 2. Procedure Launch the Desktop Tool and log on.0 for managing the conditions of pricing agreements related to the usage of a customer service.

Manually create the new subscription and save it in the database: New  Subscription. SAP CC 2. determine the business service of SAP CC that you need for global charging or rating: Charging Session-based Charging Blank Charging Batch Charging Stateless Rating Specify the chargeable items (types and contents) that your network elements or the service applications will send to SAP CC according to the customer services that you will be able to charge.0 receives chargeable items from network elements or the service applications for charging the usage of a customer service. Charged Item Management Use By default. the BART Server is in charge of converting and transmitting to the Core Server all the incoming CDRs into chargeable items. These data records should include all the necessary elements for the charging process but also for the invoicing process. NOTE In case of batch mode charging. Some configuration activities are necessary at the installation time. Some configuration activities are necessary during the implementation phase and before the installation. Activities According to your business scenario.Launch the Desktop Tool and log on. Activities Set up the transaction persistency processing mode [page ] Set up the charged item file processor Create the charged item classes (master data) [page ] Create the charges in offers for configuring the content of fields of charged items that will be finally generated by SAP CC [page ] .0 generates charged items resulting from the charging process.0 Implement the generation and the transmission of chargeable items including local time date information Set up the chargeable item classes in the SAP CC Desktop Tool for being able to design the price plans of charges to apply on each usage [page ]. Your architecture must be able to manage time zones outside SAP CC 2. Desktop Tool  File  Chargeable Item Acquisition (Implementation) Use SAP CC 2.

0 generates charged items. The billing system is in responsible for converting these data for the right time zone when required by your business.0 to your external thirdparty billing system NOTE The charged items include date in local time. We recommend you to upgrade your platform with this new function. Activities Set up the transaction persistency processing mode [page ] . Prerequisites The configuration for managing charged items is available. SAP CC 2. Activities Set up the CIF for the Rater instances of Core Server [page ] Set up the CIF for the Bulkloader instances of the Core Server Set up the EIF Create billable item mapping via the SAP CC Desktop Tool (necessary charged item classes are automatically created) [page ] Create the charges in offers [page ] Procedures All the procedures are detailed in the section related to the settings for SAP CI [page ].Implement the load of the charged item files produced by SAP CC 2. In order to generate charged transactions. Some configuration activities are necessary at installation time or later. For testing this upgrade you can configure SAP CC to be able to generate both types of data and by taken into account the configurations of the offers. Billable Item Management Use SAP CC 2. Charged Transaction Management Use By default. CAUTION You cannot create new offers and configure them for generating charged transactions in files.0 is able to send billable items to SAP Convergent Invoicing. We recommend to upgrade your landscape (by migrating your old offers) and use the charged item file processor. some configuration activities are necessary at the installation time or later. They can only be configured for generating charged items. The generation of charged transaction is still possible for ascendant compatibility purpose.

Activities For test or training purpose. Online help is directly accessible from the graphical user interfaces. the correct implementation must be available and takes into account the tax settings for each subscriber accounts managed in SAP CC [page ]. Activities With the Desktop Tool.0  Desktop Tool  About Offers .Set up the transaction file processor or the data file processor Setting up the Tax Framework Use SAP Convergent Charging 2. This configuration is done at the installation time but can be changed later. Online help is directly accessible from the graphical user interfaces. Setting up the Taxes for the Accounts Use For test or training purpose.0  Desktop Tool  About Subscriber Accounts . Consult online help of the Desktop Tool from the SAP Help Portal at:  SAP CC 2. you can configure manually the subscriber accounts with the Desktop Tool. For a productive platform. Consult online help of the Desktop Tool from the SAP Help Portal at:  SAP CC 2.0 can manage simultaneously Value Added Taxes (VAT) and US Telecommunication Taxes (based on BillSoft EZTax technology). configure manually the charges in offers [page ]. Procedure Launch the Admin+ Tool and log on Change the TAX_FRAMEWORK parameter EXAMPLE CHANGE TO: VAT. the power user can set up the taxes for each subscriber account.EZTAX Setting up the Taxes for the Pricing Use The power user can set up the taxes for each charge in an offer. .

.0 (modification of existing External Accounts in order to use the new currency or creation of new External Accounts for the new currency). could then be defined using the same pricing logic defined in a single table and macro. in two different currencies.0. It may have consequences on the definition of External Accounts to be used in the SAP CC 2.0 is able to manage several currencies simultaneously. possible modification of charging mappings. This is possible only when the distinct currencies are used in distinct price plans and charged on distinct accounts. possible modification of creation of prepaid accounts or external accounts. for instance). design the pricing logic independently from the currency. SAP Recommendation: When possible. you have to consider whether batch or “on the fly” migration better fit your needs. Does the switch occur progressively or at the same time for all the subscribers? Which downtime is acceptable for the switching? It may have consequences on the sequence of needed modifications (activation of charges in the new currency in the subscription. but just differing on final computed amount and currency. Two charges. depending to the constraints. each case of currency reform must be managed as a new independent implementation project which depends on the way SAP CC 2.Managing a Currency Reform (Implementation) Use SAP CC 2. the configuration can be also designed in a way preparing and facilitating this future currency reform. Activities If the currency reform has an impact on the third-party invoicing system: It may have consequences on the dates or time frames for the currency switch (alignment with the production of invoices. if a currency reform is already known and planned.0. and so on). During the maintenance phase of SAP CC 2.0 is used and possibly integrated with other software products. There is no native support of currency reform that would enable to switch from one currency to another without switching the pricing definition and the used account(s). by using reusable business objects such as translations tables and pricing macros. Several points should be always taken into account and/or checked when starting a currency reform project. Indeed. During the initial implementation phase of SAP CC 2.

Procedure Change the value of the TRANSAC_PROC_CLASS parameter and apply the necessary settings for the selected function Advanced: Generating Charged Transactions and Charged Items Use For upgrade purpose. you can configure SAP CC 2.0 so that it generates both data files and charged item files according to the configurations of the offers present in the system. You can configure SAP CC 2. Once configured.highdeal.highdeal.dbFile. The TRANSAC_PROC_CLASS parameter can have the following values: Output Processing Mode Charged Item Files Transaction Files Data Files Customized Parameter Value Rerating Function Can be Implemented Yes No Yes com. It can also generate transaction files or data files. This configuration is available at the CIF level. We recommend you to upgrade your system to the charged item mechanism. NOTE The power users can only create offers that are compliant with the generation of charged items.0 so it generates charged item files and data files in parallel.tif. SAP CC will use the configurations of the charges in offers for generating the appropriate record (charged item or charged transaction) and storing it into files. SAP CC 2.Setting up the Transaction Persistency Processing Mode (TIF) Use By default.tif. The configuration is available at the Transaction Integration Framework (TIF) level.TransactionProcesso rShell com.0 generates charged item files. .highdeal.TransactionFileProcessor Consult your solution consultant or your technology consultant.TransactionFileProcessor com.tif.tfp. NOTE Consult the Technical Reference Guide about the advantages and limitations of these modes for managing the charged transaction persistency.chargeditem.

0 generates charged item files.highdeal. rollover policy) at post-installation time and during the productive phase.sk) about these settings Export your current configuration from SAP CC: setup cif export -login=<LGN> -password=<PWD> rater <MYFILE> Change the parameters Import the new configuration of the CIF: setup cif import -login=<LGN> -password=<PWD> rater <MYFILE> Restart the server Setting up the Transaction File Processor Use For compatibility purpose.\config\cif.config.Procedure Export the current configuration: setup cif export -login=<LGN> -password=<PWD> rater .highdeal.tif..config.rater.0 so that it generates transaction files as described in the Technical Reference Guide from SAP Service Marketplace..config. Procedure Consult the template file (..rater.rater.tif.cif.xml Restart all the rater instances of the Core Server NOTE You can configure SAP CC so that it generates transaction files by using com. Setting up the Charged Item File Processor (CIF) Use By default.TransactionFileProcessor as class name in the above procedure.dbFile. you can configure SAP CC 2.TransactionFileProcessor" /> <chargedItemTransactionProcessor> … </chargedItemTransactionProcessor> </dispatchTransactionProcessor> Import the new configuration of the CIF: setup cif import -login=<LGN> -password=<PWD> rater . You can configure this file management (path. .\config\cif. multithreading.xml.tfp.\config\my. SAP CC 2.xml Enclose the CIF configuration of the rater instances: <dispatchTransactionProcessor> <transactionProcessorWrapper class="com. The configuration is available at the Charged item Integration Framework (CIF) level.

Activities Set up the parameters for the SAP CC Core Server: POSTPAID_DB_FILE_PROCESSOR_TRANSAC_FORMAT. TFP_TRANSAC_FILTERS and TFP_TRANSAC_xxx Setting up the Data File Processor Use For compatibility purposes. NOTE The power users cannot easily maintain the offers created with SAP CC 1.0 so that it generates data files including prepaid and postpaid transactions as described in the Technical Reference Guide from SAP Service Marketplace. You can configure SAP CC 2. We recommend you to upgrade your system in order to use the charged item mechanism.0 so that it generates both transaction files and charged item files according to the configurations of the offers present in the system.0. POSTPAID_DB_FILE_PROCESSOR_TRANSAC_DETAIL_FORMAT and similar parameters. We recommend you to upgrade your system in order to use the charged item mechanism. The configuration is available at the Transaction Integration Framework (TIF) level. NOTE The power users cannot easily maintain the offers created with SAP CC 1. .0.The configuration is available at the Transaction Integration Framework (TIF) level.0 so that it generates both transaction files and charged item files according to the configurations of the offers present in the system. You can configure SAP CC 2. Activities Set up the parameters for the Core Server: TFP_TRANSAC_DETAILS. you can configure SAP CC 2.

SAP Convergent Charging 2.ashost SAP System Number used for determining the Gateway service: jco. Prerequisite The RFC destination has been created with the procedure relevant for your system landscape when installating SAP ERP / Convergent Invoicing.pool_capacity Maximum number of idle connections kept open by the destination A value of 0 has the effect that there is no connection pooling.peak_limit Description Maximum number of active connections that can be created for a destination simultaneously jco.destination.0 calls RFCs of SAP Convergent Invoicing by using the SAP JCo. Procedure Export the current configuration in a file: setup eif exportConfiguration -login=<LGN> -password=<PWD> CI ..sk) including the following parameters: Application server host or Gateway host: jco.client.client.client. You have to configure and maintain these communication settings.destination. jco.destination.destination Change the connection parameters according to your landscape changes Import the new configuration file: setup eif importConfiguration -login=<LGN> -password=<PWD> CI . SAP CC 2. Setting up the jco.client.destination Used to Connect to SAP CI Use SAP CC 2.destination .client.0 is provided with a template file (jco.user and jco.lang) Various communication settings: Parameter jco.\config\withCI\jco.\config\withCI\jco.client.0 can be configured to load billable items into SAP Convergent Invoicing (in SAP ERP system).passwd.. jco.sysnr And other parameters for the identification of SAP CC as a client application (jco.client.

For the configuration of the conversion.0  Operate . For error management. For error management.Setting up the Rater Instances (CIF) Use SAP CC 2. multithreading. The communication is ensured by the SAP JCo by using RFC procedures.sk) about these settings Export your current configuration from SAP CC: setup cif export -login=<LGN> -password=<PWD> rater <MYFILE> Change the parameters Import the new configuration: setup cif import -login=<LGN> -password=<PWD> rater <MYFILE> Setting up the Bulkloader Instances (CIF) Use SAP CC 2. file error management). Procedure Consult the template file (. consult the Operation Guide from SAP Service Marketplace at the following location:  Operate or  SAP Business Suite Applications  SAP Convergent Charging  SAP CC 2. You can configure this file management (path.bulkloader. roll over policy). multithreading. CAUTION Before being written in file. You can configure this file management (path. Procedure Consult the template file (.0 generates temporarily charged item files.config. buffering.0 loads into SAP Convergent Invoicing the billable items extracted and converted from the charged item files.xml.0  Operate .\config\withCI\cif.sk) about these settings Export your current configuration from SAP CC: setup cif export -login=<LGN> -password=<PWD> bulkloader <MYFILE> Change the parameters Import the new configuration: setup cif import -login=<LGN> -password=<PWD> bulkloader <MYFILE> Setting up Billable Item Mapping (Master Data) Use .\config\withCI\cif.rater.config. the charged items are validated by SAP Convergent Charging to ensure that they will be correctly converted into billable items. consult the Operation Guide from SAP Service Marketplace at the following location:  Operate or  SAP Business Suite Applications  SAP Convergent Charging  SAP CC 2..xml. consult the next section..

identify the billable item mapping object to be changed in the Desktop Tool and the charged item class that is used In SAP CC. identify if it is necessary to update a price plan or a charging plan for being able to generate the content of the new field in billable items Procedure From the management console. You can set the appropriate property or let the user make the final decision at the offer level. billable item classes can be changed in SAP Convergent Invoicing (in SAP ERP system) by the addition of some optional fields at the end of the structure. In some business cases. By default. NOTE For more information about the configuration of interfaces for managing billable item classes. Online help is directly accessible from the graphical user interface.SAP Convergent Charging uses billable item mapping objects for defining the way SAP CC generates billable items to SAP Convergent Invoicing (in SAP ERP system). The source transaction ID vaults the Charged Item Set ID. Consult the SAP Help Portal at: Preparation In SAP CI. Consult online help of the Desktop Tool from the SAP Help Portal at:  SAP CC 2. SAP CC 2. determine the changes in the billable item class Determine if the configuration of SAP CC must be updated according to its final use and the way to fill it in. Desktop Tool  File  New  Maintaining Billable Item Mapping Use Once released as productive.0 generates billable items with a dedicated source transaction type: CCCIT. it becomes necessary that SAP Convergent Charging takes these changes into account and is able to generate new version of billable items. Procedure Start the Desktop Tool and log on Create billable item mapping and save in the database: Billable Item Mapping.0  Desktop Tool  About Billable Item Mapping . In SAP CC. stop all the Bulkloader instances of the Core Server Delete the billable item mapping object Change the charged item class by adding the new field. The field name must be the same as the one in the billable item class: Desktop Tool  File  Open  Charged Item Class Map this field according to your business.  Industries in SAP ERP  SAP Telecommunications  Billing in Contract Accounts Receivable and Payable  Integration of SAP Convergent Charging . see the SAP Library for ERP Enhancement Packages. Save the updated charged item class in the database .

Check that the new field is present Map it to the field of the charged item class Save the new billable item mapping object in the database Restart the Bulkloader instances of the Core Server NOTE For testing purposes.CIConnector Update the mapping definition as described in the next section Setting up the Default Field Mapping Between CIT and BIT (Implementation) Use To ease the configuration of billable item mapping in SAP CC 2. map this field to the appropriate property or value source. you have to update the EIF configuration Create a new billable item mapping for the change billable item class. Please maintain SAP CC accordingly to your business. It may be necessary to update first the price plan and the charging plan so they output the right data. When relevant. A new field appears. . CAUTION The definitions of billable item classes in SAP CI can change.eif. Setting up the Updater Instances (EIF) Use SAP CC 2.ci.0. Procedure Set EIF_CONN_CLASS parameter to the value: com. you can set how it should be generated by default by SAP CC and if this field will be mandatory in SAP CI so SAP CC can automatically add this field when the power user creates a new billable item mapping.Update all the offers that include charges using this charged item class: Desktop Tool  File  Open  Offer Display successively all the charges and click the Refresh button in the Charged Item tab.highdeal. the power user has to create a new billable item mapping when the structure of a billable item changes. This configuration is done at installation time and should not be changed. it is recommended to create and maintain a list containing the fields defined in billable item classes present in SAP Convergent Invoicing.0 exchanges information on billable item classes managed by SAP Convergent Invoicing. If the field is new in the interface component in SAP CI. Select the right charged item class. For each field. All the charges in the offers must be updated.

Procedure Create a configuration file defaultFieldMapping.xml Verify and update the content of this file according to the configuration of billable item classes defined in SAP CI: The XML schema is basic and mostly includes the exportableItemMappingField tag that identifies a field in the generated billable items.sk file from an SAP CC installation. Prerequisites You know the configuration of billable item classes in SAP CI. ... the default way it is generated by SAP CC and if it is mandatory: <?xml version="1.Activities As technology consultant.Field generated by default with a value computed by SAP CC --> <exportableItemMappingField name="<FIELD2>"> <additionalInformation name="value" value="<KEYWORD>" /> <additionalInformation name="isMandatory" value="true" /> </exportableItemMappingField> </exportableItemMapping> For each exportableItemMappingField tag.Field generated by default with a constant --> <exportableItemMappingField name="<FIELD1>"> <additionalInformation name="constant" value="CCCIT" /> <additionalInformation name="isMandatory" value="true" /> </exportableItemMappingField> <!-. It is available in the folder: <HOME>\config\withCI\ or it can be exported from a running server using the and the eif command. EXAMPLE <?xml version="1. you have to initiate this configuration according to the configuration of SAP CI. As system administrator. You have the default_CI_EI_Mapping. you may have to update this configuration in SAP CC when a new field is created in SAP CI. add the additionalInformation tag with the name set to constant if SAP CC generates this field with a constant value or with the name set to value if SAP CC generates this field with a value computed during the rating or charging process according to the keyword. </exportableItemMapping> You may have to change some settings or add some field descriptions.xml.0" encoding="UTF-8"?> <exportableItemMapping externalSystemCode="CI"> <!-.0" encoding="UTF-8"?> <exportableItemMapping externalSystemCode="CI"> <exportableItemMappingField name="SRCTATYPE"> <additionalInformation name="constant" value="CCCIT" /> <additionalInformation name="isMandatory" value="true" /> </exportableItemMappingField> <exportableItemMappingField name="VKONT"> <additionalInformation name="value" value="externalAccountCode" /> <additionalInformation name="isMandatory" value="true" /> </exportableItemMappingField> .

TransactionFieldBook. It has no connection with the Core Server of SAP CC and can be installed separately.0 used by SAP Convergent Invoicing.tif.html file. Setting up a Destination Use .xml Restart all the instances of the Core Server The CT Server is an optional software component of SAP Convergent Charging 2. Import this new configuration in SAP CC Core Server by using the setup eif importDefaultMapping -login=<LGN> -password=<PWD> .\config\withCI\ defaultFieldMapping..NOTE The list of keywords is available in the Javadoc in the Core Server SDK or at the following URL: in the pnr.

The CT Server.0  Operate . see the Operation Guide from SAP Service Marketplace at the following location:  SAP CC 2. Setting up the Log Directory for the EZTax Log Files Use The CT Server generates EZTax log files in a directory. implements functions that are called up by an ABAP Backend. See the Prerequisites Using transaction SM59. The file includes all the necessary instructions for setting up the destination in the CT Server: Name of the registered destination: jco.server. Procedure Stop the CT Server Edit the ct. Procedure Stop the CT Server Edit the ct. 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). This directory also includes status files from BillSoft EZTax software. It is registered via the SAP Gateway and waits for inbound RFC calls.server. It is highly .progid Gateway host: jco. If an RFC connection is interrupted or terminated. as a JCo server program. the CT Server automatically registers itself again on the same SAP Gateway under the same program ID.repository_destination Program ID: jco. The CT Server registers itself under a program ID to an SAP gateway (not for a specific SAP system). you have defined a RFC destination with connection type T (TCP/IP connection) in the SAP system.config file located in the <home>/config/ folder. the connection takes place with the CT Server program. Once an RFC function has been executed. You have chosen the registration mode (“Registered server program” option under the “Technical settings” tab page) for this destination.gwhost Gateway service: jco.gwserv Restart the server section.config file located in the config folder Change the value of the EZTAX_LOG_DIRECTORY parameter Restart the server CAUTION Do not use the log directory for appending the EZTax log files in a unique tax journal.server. the CT Server waits for further RFC calls from the same or other SAP systems. For details about the content of this directory.server. service) and the registered CT Server (Program ID). The destination contains the required information about the SAP Gateway (host.

Procedure Stop the CT Server Edit the ct.recommended to stop the CT Server and move the EZTax log files to another directory of the host for working with and archiving. The file includes all the necessary instructions for setting up: The log file management of CT Server The BillSoft EZTax parameters (server path.config file located in the <home>/config/ folder. Setting up Other Basic Settings Prerequisite BillSoft EZTax software is installed. log file management) Restart the server .

Procedure Stop the graphical user interface Edit the core_tool. It will store some parameters of a user working session.0. You can set up these parameters and some other parameters listed in this section. string Not set Consult the template of configuration file Type Default Value Range of Values Parameter Parameter(s) frame. Setting up the Desktop Tool Use The Desktop Tool is a graphical component of SAP CC 2.width . All the graphical user interfaces of SAP Convergent Charging 2.SAP Convergent Charging includes several user interfaces.0 have a default configuration.config.sk template file Set the following parameters in the different sections Restart Parameter Parameter(s) Description default_language This parameter specifies which language is used for the graphical user interface. As system administrator or power users. you can configure these interfaces. When not set. You can configure the following interfaces: Desktop Tool BART Tool Simulation Tool Connector Administration Tool (CAT) The configuration files are located in the <HOME>/config/ folder of each program. The Desktop Tool can start running without any configuration file.config file or create such a file by copying the core_tool. the program uses the language of the Operating System or English. They create a configuration file at first launch time if you did not create a file before.

url=http://help. They can be configured to use local online help files or files located on a web portal (from SAP Help Portal or from a customer site). . integer Width: 900 Height: 700 1 to 65. the URLs are targeted to the SAP Help Portal. Type Default Value Range of Values string By default.sap.com/ Where C is the local drive letter and where myrootfoldername is the main folder that includes a copy of the documentation from the DVD. See example bellow for details A valid HTTP URL or FILE URL for each entry in the menu of the graphical user interface where the documents must be accessible These parameters specify the width and height of the window of the program.com/saphelp_cc20/helpdata/en/e2/c omporef/frameset.contents.url help.url=http://help.url=http://help.components.contents.height Description Type Default Value Range of Values Parameter Parameter(s) help.portal.sap.portal.sap.com/ EXAMPLE (LOCAL MACHINE) help.frame. Note: The Docu DVD is required for this configuration.535 EXAMPLE (WEB SITE) help.htm help.portal.com/saphelp_cc20/helpdata/en/e2/dkt/fr ameset.url help.components.htm help.components.contents.url Description These parameters specify which main topics are displayed when navigating in the Help menu of the Desktop Tool.htm help.url=http://help.url=file:/C:/myrootfoldername/StandardHTML/EN/e2/co mporef/frameset.htm help.sap.url=file:/C:/myrootfoldername/StandardHTML/EN/e2/dkt/fra meset.

url=file://myservername/foldername/StandardHTML/EN/ e2/comporef/frameset.help.config.url BART.url=http://help.sap. Parameter Parameter(s) Description xml.htm help.contents.verbose For troubleshooting or for testing purposes. Procedure Stop the graphical user interface Edit the bartTool.portal.com/ Where foldername is the main folder (or path) that includes a copy of the documentation from the DVD.config file or create such a file by copying the bartTool.components. Those files are xml files.portal. boolean false false or true Type Default Value Range of Values Setting up the BART Tool Use The SAP CC BART Tool is an optional component of SAP Convergent Charging needed for configuring SAP CC BART Server.htm help.url=file://myservername/foldername/StandardHTML/EN/e2/ dkt/frameset.contents.url Description These parameters specify which main topics are displayed when navigating in the Help menu of the BART Tool.EXAMPLE (SHARED NETWORD FOLDER) help.help. They can be configured to use local online . this parameter allows you to trace the XML communications exchanged between the SAP CC Desktop Tool and the SAP CC Core Server.sk file. Set the following parameters in the different sections Restart Parameter Parameter(s) BART.

string Not set Consult the template of configuration file Type Default Value Range of Values .com</BartHelpPortalURL> EXAMPLE (LOCAL MACHINE) <BartHelpContentsURL>file:/C:/myrootfoldername/StandardHTML/EN/e2/dkt/frameset.com/saphelp_cc20/helpdata/en/e2/bart/frameset. the URLs are targeted to the SAP Help Portal.sk file Set the following parameters in the different sections Restart Parameter Parameter(s) Description default_language This parameter specifies which language will be used for the graphical user interface. Note: The Docu DVD is required for this configuration.config.help files or files located on a web portal (from SAP Help Portal or from a customer site). Setting up the Simulation Tool Use The Simulation Tool is an optional component of SAP CC.sap. You can configure the final precision and rounding mode of the results of the rating calculation during the simulation.config file or create such a file by copying the sim_tool.htm </BartHelpContentsURL> <BartHelpPortalURL>http://help.sap. See example bellow for details A valid HTTP URL or FILE URL for each entry in the menu of the graphical user interface where the documents must be accessible EXAMPLE (WEB SITE) <BartHelpContentsURL> http://help. When not set. Type Default Value Range of Values string By default.htm</BartHelpC ontentsURL> Where C is the local drive letter and the myrootfoldername is the main folder that includes a copy of the documentation from the DVD. Procedure Stop the graphical user interface Edit the sim_tool. the program uses the language of the Operating System or English.

(e. truncates). 0.0) NEAREST: Rounding mode to round towards "nearest neighbour" unless both neighbours are equidistant.transaction_precision This parameter specifies the number of decimal positions to keep for rated transaction amounts.url Description These parameters specify which main topics are displayed when navigating in the Help menu of the Simulation Tool.contents.Parameter Parameter(s) Description Type Default Value Range of Values pns. Note: The Docu DVD is required for this configuration. the URLs are targeted to the SAP Help Portal.components.0.g. in which case round up (RAISE).transaction_rounding_mode This parameter specifies the method used to round the amounts of rated transactions.e. string 6 -1 to 6 -1: The precision of the currency is used. TRUNCATE RAISE. Parameter Parameter(s) Description pns.4 give 0.. (e. 0.g.0) Type Default Value Range of Values Parameter Parameter(s) help. 0. Note that this rounding mode never increases the magnitude of the calculated value.g. Always increments the digit prior to a nonzero discarded fraction. Note that this rounding mode never decreases the magnitude of the calculated value.0) RAISE: Rounding mode to round away from zero. The possible values are: TRUNCATE: Rounding mode to round towards zero. NEAREST . They can be configured to use local online help files or files located on a web portal (from SAP Help Portal or from a customer site). Never increments the digit prior to a discarded fraction (i. 0.5 give 1.portal.9 give 0.1 give 1. Type Default Value string By default.url help.url help. (e. TRUNCATE.

the program uses the language of the Operating System or English String Not set Consult the template of configuration file Type Default Value Range of Values Parameter Parameter(s) Description help. Procedure Stop the graphical user interface Edit the cat.portal. Setting up the Connector Administration Tool Use The CAT is an optional component of SAP CC needed for configuring the IEC.contents.com/saphelp_cc20/helpdata/en/e2/c omporef/frameset.portal.htm help. Type String . When not set.url=http://help.sk template file Set the following parameters in the different sections Restart Parameter Parameter(s) Description default_language This parameter specifies which language will be used for the graphical user interface.config.url These parameters specify which main topics are displayed when navigating in the Help menu of the CAT.contents.sap.sap.url=http://help. Note: The Docu DVD is required for this configuration.See example bellow for details Range of Values A valid HTTP URL or FILE URL for each entry in the menu of the graphical user interface where the documents must be accessible EXAMPLE help.url help.htm help.url=http://help.sap. They can be configured to use local online help files or files located on a web portal (from SAP Help Portal or from a customer site).config file or create such a file by copying the cat.components.com/ See also the examples from the Desktop Tool configuration.com/saphelp_cc20/helpdata/en/e2/simu/ frameset.

Default Value Range of Values By default.sap.sap.com/saphelp_cc20/helpdata/en/e2/cat/fr ameset.contents. .portal.0.com/ See also the examples from the Desktop Tool configuration. There is no configuration parameter for the Admin+ and the BART+ command line interfaces of SAP Convergent Charging 2. You can consult the chapter about these user interfaces [see page ].url=http://help.htm help. the URLs are targeted to the SAP Help Portal See example below for details A valid HTTP URL or FILE URL for each entry in the menu of the graphical user interface where the documents must be accessible EXAMPLE help.url=http://help.

sk file for detailed information Edit the bart. It communicates with the SAP CC Core Server and an external mediation system. database URI Save the file Restart the server .The SAP CC 2.config file Make sure you correctly type the following attributes: login. password.config. Procedure Consult the bart.0 BART Server based on NW AS Technology is an optional software component of SAP Convergent Charging used in a batch-mode for handling the acquisitions of CDRs and managing rating and charging sessions. It is configured by using the user interfaces: BART Tool and Bart+ Tool. Setting up the Connection to the Database Use You can configure database connection used by SAP CC BART Server.

config file Set the sql.log.failures. Procedure Consult the bart.config file Set up the bart.config file Set the instance_host and instance_port parameters Save the file Restart the server Setting up the HTTP Connection to the BART Server Use You can configure the following parameters to define the listening port of the BART HTTP Listen Server used to receive API requests and the number of dedicated threads that are available for handling simultaneous API calls.config. This file is usually created before an unexpected stop of the BART Server processes.file.config.sk file for detailed information Edit the bart. When the BART Server restarts.sk file for detailed information Edit the bart.threads parameters Save the file Restart the server Setting up the TCP/IP Connection for the Acquisition or Rerating Functions Use You can configure: For the acquisition function: the connection to the BART Server For the rerating function: the listening port and the number of dedicated threads that are available to handle simultaneous API calls to the services using the TCP/IP protocol Procedure .Setting up the Database Connection SQL Failure Management Use When the BART Database crashes during a rating session.sk file for detailed information Edit the bart. this parameter defines the directory of the file used for storing information on non-committed CDR modifications.port and bart.http.server.config.http.server.name parameter Save the file Restart the server Setting up the Connection to the Core Server Use You can configure the IP and the port number of the Core Server. Procedure Consult the bart. the SQL failure file is read and its content is committed to the database. Procedure Consult the bart.

collector.queue_size parameter Save the file Restart the server Setting up the Rerating Function Use You can configure: The address of the rerating service server (rerating.server.config file Set the bart.collector.name. log.errorfile. Procedure Consult the bart.size.server=%COLLECTOR_IP_ADDRESS.sk file for detailed information Edit the bart.backups. log. log.config.port parameter Set the bart.file.file. number of backups and maximum size of each backup log file.collector. Setting up the Logging Function Use The attributes described below can be configured according to the expected level of logs.port=2001) used for rerating subscriptions NOTE The server address is the same one that the one used for rating subscriptions: collector.Consult the bart. NOTE Refer to the SAP Convergent Charging configuration guidelines for more details regarding the log output parameters.config file Change the values of parameters in the log section (log.level.threads parameter Set the rerating.server.pool_size parameter Set the rerating.config.file. log.hostname parameter Set the bart.sk file for detailed information Edit the bart.server.name) Save the file Restart the server Setting up the Magic Number Pattern Use .

NOTE A magic number pattern must be defined for each CDR type (e.<n>. Integer 1 Non zero integer For each magic number: Parameter Parameter(s) Description Type Default Value Range of Values Parameter Parameter(s) Description magic_number. consumption_date. …) that is acquired by the SAP CC BART Server.call_duration). Type Default Value Range of Values String name. SMS...user_id.) or additional item fields prefixed by 'item' (for example item.g.sk file for detailed information Edit the bart. Procedure Consult the bart.config file Change the values of parameters in the magic number section Save the file Restart the server Parameter Parameter(s) Description Type Default Value Range of Values magic_number. MMS.item_name CDR name on which the magic number should be associated String cdr A unique CDR name Setting up the Scheduled Job Management . user_id .You can configure the deduplicate function to set CDRs which must be identified as duplicates.service_id magic_number.fields List of fields to concatenate to build the magic number It can contain standard item values (name.config.consumption_date.<n>.number Number of magic number patterns.

the number of rated CDRs and the number of erroneous CDRs. the number of rated CDRs and the number of erroneous CDRs. This event is triggered at a regular frequency (depending on the BART Server configuration parameters) and describes the Acquisition Acquisition Acquisition session stop event Rating session start event Rating session status event Rating Rating Rating Rating session stop event Job start event Job status event Job Job . acquisition and rating session events can be broadcasted through the use of XML messages that are generated at a regular frequency on the UDP network layer.config. the BART Server of SAP Convergent Charging 2. This event mainly contains the definition of the session being created. the number of newly acquired CDRs and the number of duplicated CDRs. This event is triggered each time a new rating session is started. This event is triggered each time an acquisition session is complete.Use You can fine configure: The maximum number of scheduled jobs that can be active at the same time The period between the output of two status events Procedure Consult the bart. This event is triggered at a regular frequency (depending on the BART Server configuration parameters) and describes the elapsed time of the session. This event is triggered each time a rating session is complete. the number of acquired CDRs and the number of duplicated CDRs. This event mainly contains the definition of the job being started. It contains the total duration of the session. This event is triggered at a regular frequency (depending on the BART Server configuration parameters) and describes the elapsed time of the session.0 is provided with an event broadcaster and with a file report handler.config file Set up these parameters Save the file Restart the server Jobs. The BART Server handles the following events grouped by functions (topics). By default. This event is triggered each time a job execution is started. It contains the total duration of the session. This event mainly contains the definition of the session being created.sk file for detailed information Edit the bart. Topic (Function) Acquisition Event Acquisition session start event Acquisition session status event Description This event is triggered each time a new acquisition session is started through the mediation chain.

txt ACQUISITION DESCRIPTION = Test JUNIT ACQUISITION MODE= Acquisition and de-duplicate mode NB CDR ACQUIRED = 961 NB CDR DUPLICATE= 39 NB CDR CONSOLIDATE = 950 STATUS= ended EXAMPLE An example of reporting file for a rating session follows: report_rating_05-11-15. Setting up the File Report Handler Use The file report handler of BART Server is sensitive to stop events from acquisition and rating sessions.txt ################################ ACQUISITION REPORT ################################ CREATION DATE = Tue Nov 15 21:34:10 CET 2005 ACQUISITION DATE = 2005-11-15 21:34:10.303 RATING DURATION = 2 sec RATING MAX CONSUMPTION DATE = 2005-11-29 17:53:32.config file Change the values of following parameters: folder: folder where to store the report file (default: <BART_HOME>/logs) filename: prefix for reporting file (default: report) fileSuffix: suffix for reporting file (default: .elapsed time of the job execution. Job Job stop event This event is triggered each time a job execution is complete.sk file for detailed information Edit the report. the BART Server produces a report file containing the details of the complete session.config. Procedure Consult the bart.717 ACQUISITION DURATION = 24 sec ACQUISITION SOURCE = somewhere_with_some_CDRs\source.287 RATING DESCRIPTION = null .txt ################################ RATING REPORT ################################ CREATION DATE = Tue Nov 29 17:53:32 CET 2005 RATING START DATE = 2005-11-29 17:53:32. It contains the total duration of the job execution. For each event received.txt) Save the file EXAMPLE See the following example of a report file for an acquisition session: report_acquisition_05-11-15.

password parameters with the values previously set in the Desktop Tool Save the file Restart the BART Server.highdeal. It will cipher the password and save the configuration file.handler. .config. You may have to change this password for security or test reasons.sk file for detailed information Edit the bart.bart.1 = com.login and cc. Procedure Launch the and log on with a user that has the User Administration role Change the password of the user reserved for the BART Server Consult the bart.config file Verify that the default parameter values are present: report.number = 1 report.config file in the configuration folder of the BART Server Update the cc.RATING MODE= most mode NB CDR RATED = 100 NB CDR IN ERROR= 0 STATUS= cleaned Enabling the Monitoring Function Use These parameters define the monitoring state: Activated or not.handler.FileReportHandler Changing the Password to Log on the Core Server Use The BART Server uses a user/password to log on the Core Server.handler.sk file for detailed information Check with the BART Tool that there is no running session Stop the BART Server Edit the bart.event. Procedure Consult the bart.config file Set the monitoring state parameter Set the communication settings for the monitoring function Set the technical settings for the monitoring function Save the file Restart the server Advanced: Resetting the Customized File Report Handler Procedure Do change the configuration only for customized event handlers View the bart.config.

size parameter allows you to set the size of the cache by giving the number of accesses handled by the cache Procedure Consult the bart.monitoring. Procedure Consult the bart.period parameters Save the file Restart the server Technical Configuration for CDR Consolidation Cache Management Use You can fine configure the consolidation cache management: The consolidation.monitoring.session.number and the acquisition.period Technical Configuration for Acquisition Sessions Use You can fine configure: The maximum number of concurrent running acquisition sessions The period between the output of two status events Detailed information on the generation of events is provided in the Technical Reference Guide from SAP Service Marketplace.sk file for detailed information Edit the bart.config file Set the acquisition.sk file for detailed information Edit the bart.period scheduler.cache.config.config file Set up these parameters Save the file Restart the server .session.monitoring.max.monitoring.job. Technical Configuration for the Monitoring Use For each function (topic).config.enable parameter allows you to enable or disable the consolidation cache The consolidation.cache.CAUTION You must restart immediately the BART Server to secure this procedure.session.period rating. you can configure the period between the generations of two status events: acquisition.session.

but changing the value of this parameter may alter the performance of processes. . CDR Acquisition Use SAP CC BART Server receives CDRs from network elements and sends them as chargeable items to the SAP CC Core Server. Furthermore. Procedure Consult the bart.number=10) which is set in the configuration file.size=100) for rerating subscriptions. you can change the value of the maximum number of concurrent rating sessions.queue. it must be less than or equal to the number of collecting threads. However.config. This section lists the configurations determined by the solution consultants and by the technical consultants of your project team.max. keep in mind that several rating sessions can be launched at the same time The size of a CDR commit block: It corresponds to the maximum number of CDRs rated through the Core Server before the result is committed to the BART Database. The number of session orders stored in memory (rerating.pool.config file Set these parameters Save the file Restart the server Technical Configuration for Rerating You can fine configure the following parameters: The number of threads (rerating.size=4) used for rerating subscriptions. (*) If necessary. CAUTION This parameter must not exceed the maximum number of concurrent rating sessions (rating. Furthermore.sk file for detailed information Edit the bart. the number of rating and rerating sessions running at the same time must not also exceed the maximum number of concurrent rating sessions (*). The acquisition is managed by the client application.Technical Configuration for Rating Sessions Management Use You can fine configure the rating session management: The maximum number of concurrent rating sessions The period between the outputs of two status events The number of concurrent threads per rating session: It must be chosen according to the number of collecting threads available on the SAP CC Core Server side. Keep in mind that a thread is used per subscription.session.

try { collector = new CDRServiceClient("BART_HOST". NOTE You can also use the Java API (XML/HTTP) or the XML API for managing the CDR acquisition for test or training purpose.printStackTrace().bart. The acquisition is managed by the client application. you have to: Specify and implement your CDR acquisition process according to the Java API (TCP/IP) Specification of SAP Convergent Charging and by using the Java class You can use the Java API (XML/HTTP) or the XML API for managing the acquisition for test purpose EXAMPLE CDRServiceClient collector. e. .out.println("InvalidAcquisitionException -> "+e).out.0  Development  BART Server Javadoc  com.startAcquisitionSession(session). } catch (CommunicationFailureException e) { System. } // build up the acquisition session AcquisitionSessionModel session = new AcquisitionSessionModel(… try { session = collector.out.println("OperationFailureException -> "+e).message . Activities As technology consultant. } catch (ServerUnavailableException e) { System.out. you have to: Specify and implement your CDR acquisition process according to the API specifications of SAP Convergent Charging and by using the class.highdeal. Consult online the SAP CC BART Server Javadoc from the SAP Help Portal:  SAP CC 2. Activities As technology consultant.2009).Consult online the SAP CC BART Server Javadoc from the SAP Help Portal:  SAP CC 2. CDR Acquisition with the Java API (TCP/IP) Use SAP CC BART Server receives CDRs from network elements and sends them as chargeable items to the SAP CC Core Server. } catch (InvalidAcquisitionException e) { System.message .highdeal.bart.0  Development  BART Server Javadoc  com.println("OperationFailureException -> "+e). } catch (Exception e) { System.println("Cannot initialise BART Collector client -> "+e).

Activities Specify and implement your CDR acquisition process according to the API specifications of SAP Convergent Charging and by using the Java classes of the Java package EXAMPLE // sender has to be instantiated as described in the SAP Convergent Charging documentation HTTPMessageSender sender = … StartAcquisitionSessionOp op = new StartAcquisitionSessionOp(). } catch (ServerUnavailableException e) { System. session).acquireCDR(cdrs. description. AcquisitionSessionModel.println("InvalidCDRException -> "+e).println("InvalidAcquisitionException -> "+e).send(op) this. } catch (Throwable t) { System. } catch (ServerUnavailableException e) { System. try { StartAcquisitionSessionResult opRes = sender.add(new CDRModel(.hci . } catch (InvalidAcquisitionException e) { System.println("Throwable -> "+t). } catch (CommunicationFailureException e) { System.println("StartAcquisition() completed").bart.println("OperationFailureException -> "+e).println("OperationFailureException -> "+e).stopAcquisitionSession(session).println("OperationFailureException -> "+e). } catch (InvalidCDRException e) { System. Vector cdrs = new Vector().out.out.println("Throwable -> "+t). String source = "BART Reference". } System. } catch (CommunicationFailureException e) { System. } System.println("StopAcquisition() completed"). op. } catch (ServerUnavailableException e) { .out.println("InvalidAcquisitionException -> "+e).out.setAcquisitionSession(session). } catch (Throwable t) { System.// build up some CDRs try { result = collector.out.out.session = opRes.out.out. CDR Acquisition with the Java API (XML/HTTP) Use For test or training purpose.out.println("Throwable -> "+t). AcquisitionSessionModel session = new AcquisitionSessionModel(source..out.getAcquisitionSession(). cdrs. } catch (InvalidAcquisitionException e) { System.out.out. } try { session = collector.ACQUIRE_AND_DEDUPLICATE_MODE ).println("OperationFailureException -> "+e). Consult online the SAP CC BART Server Javadoc from the SDK or from the SAP Help Portal at:  SAP CC 2..} catch (Throwable t) { System. String description = "Tests for BART User Guide".highdeal.0  Development  BART Server Javadoc  com. the BART Server can receive CDR acquisition from the HTTP Communication Interface (HCI) of SAP Convergent Charging.

0" encoding="utf-8"?> <envelope> <header transaction="most"> </header> <body> <startAcquisitionSession> <acquisition startDate="2005-01-11T14:22:03" source="bart. CDR Acquisition with the XML API Use For test or training purposes.0  Development  BART Server Javadoc  com.bart.out. }catch (OperationFailureException e) { System. Activities Specify and implement your CDR acquisition process according to the API specifications of SAP Convergent Charging and by using the XSD fragments provided in the documentation EXAMPLE OF HCI ENVELOPE SENT WITH THE HTTP CLIENT UTILITY PROGRAM API request sent through the http client utility: <HOME>/bin/http_client <BART_HOST> <BART_HOME>bart_run_rating_session.println("StartAcquisition() completed").out.out.highdeal. SAP CC BART Server can receive CDR acquisitions from the HTTP Communication Interface (HCI) of SAP Convergent Charging.xml" description="test source XML" mode="acquireAndDeduplicate"/> </startAcquisitionSession> </body> </envelope> EXAMPLE OF ANSWER <?xml version="1.println("ServerUnavailableException -> "+e).hci about the xsd fragments. } System.println("OperationFailureException -> "+e). Consult online the SAP CC BART Server Javadoc from the SDK or from the SAP Help Portal at:  SAP CC 2.System.out.xml" description="test source XML" mode="acquireAndDeduplicate"/> </startAcquisitionSessionResult> </body> </envelope> Supervision with the Event Handler Framework Use .xml <?xml version="1.println("InvalidAcquisitionException -> "+e). } catch (InvalidAcquisitionException e) { System.0" encoding="utf-8"?> <envelope> <header transaction="most"> </header> <body> <startAcquisitionSessionResult> <acquisition sessionID= “12002” startDate="2005-01-11T14:22:03" source="bart.

needed for initializing the handler. the property file and the subscribed topics Save the file Restart the server NOTE By default. A list of topics to which the handler will be sensitive.handler.config file by setting up the necessary parameters Set the number of customized event handlers (report.sk file for detailed information When relevant. create a bart.Jobs. Because event handlers follow a specific framework. the SAP CCBART Server is provided with a file report handler. Job topic: Refers to any events related to a job execution (start.config. Procedure Consult the bart. Activities Specify and implement your customized report handler according to the Java API specification of SAP Convergent Charging. The following settings are available: report. Setting up the Customized Event Handlers Use You can configure different report handlers that are active in the SAP CC BART Server including the default file report handler and customized report handlers.0  Development  BART Server Javadoc . A property file. An event handler is mainly defined by the following elements: A Java class implementing the event handler framework which describes how events are handled.config file based on this skeleton file Edit and change your bart. stop and status). NOTE BART Server is provided with a file report event handler. acquisition and rating sessions can be monitored through the use of events that are generated at a regular frequency. stop and status). Consult online the SAP CC BART Server Javadoc from the SDK or from the SAP Help Portal at:  SAP CC 2. stop and status) Rating topic: Refers to any events related to a rating session (start. Prerequisites You have developed an event handler based on the Event Handler Framework. The list of available topics are: Acquisition topic: Refers to any events related to an acquisition session (start.number = 1 .number) For each handler.handler. new handlers can be developed at reduced costs depending on specific customer business. These output files report the occurrence of acquisition and rating stop events. set the classname.

Consult online help of the SAP CC Javadocs from the SDK or from the SAP Help Portal at:  SAP CC 2.1 = com.highdeal.0  Development  BART Server Javadoc . a state (running or not running).report. Jobs are defined by a status (active or inactive). New jobs can be developed at reduced costs depending on specific customer requests.event.handler. Activities Specify and implement your customized event handler according to the Javadoc of SAP Convergent Charging.bart. a recurrence or a polling period.handler. .FileReportHandler Job Framework Use The SAP CC BART Server has its own scheduler for triggering jobs that must follow a framework.

SAP Convergent Charging is designed for managing and storing a large volume of data in the BART database. Setting up the Partitioning Configuration for MS SQL Server This table describes the package procedures to use for configuring the partitioning feature. This procedure allows creating a new directory. The partitioning will help the DBA to administrate the databases especially for purging and archiving the data as described in the Operations Guide. Procedure CONFIGURE Description This procedure allows the DBA to configure the global partitioning policy. This procedure fills in the PARTITION_PURGE table with the parameters specified as arguments.The SAP CC Diameter Server is an optional software component of SAP Convergent Charging used in a real time scenario for handling the mediation function in front of SAP CC and managing requests for rating and charging events or sessions. The procedures listed in this section enable you to configure: The number of days kept in the database The number of days or partitions that are created in advance How partition creation is triggered (manually or automatically) The directories used to store the tablespaces or filegroups NOTE You must be connected as DBA to your RDBMS to use the following procedures. RECOMMENDATION Update the partitioning configuration periodically to make the partition creation policy compliant with your real traffic. ADD_DIRECTORY NOTES . The partitioning is necessary to improve BART’s performances when storing a large number of CDRs in BART database. to resize an existing directory or to reactivate a removed one for storing filegroups.

New partitions are created if needed. default: ‘1GB’) extendSize (varchar. . REMOVE_DIRECTORY MANAGE_NEW_PARTITION This procedure allows the DBA to remove a directory which is no more used for storing new filegroups. This procedure fills in the PARTITION_PURGE table with the parameters specified as arguments.Each filegroup name is unique and is of the form BART_yyyymmdd where yyyymmdd is a date. default: ‘250MB’) REMOVE_DIRECTORY MANAGE_NEW_PARTITION directory (varchar) None Setting up the Partitioning Configuration for Oracle This table describes the package procedures to use for configuring the partitioning feature.000 characters at maximum) Initial size The size of the directory The directory to be removed ADD_DIRECTORY directory (varchar) fileSize (varchar. NOTE To automatically trigger partition creation. create a job in SQL Server which calls the MANAGE_NEW_PARTITION procedure. This procedure allows the DBA to manually trigger the creation of new partitions. Execute the following procedures with the required arguments: Procedure CONFIGURE Arguments partitionDays (integer) partitionAdvanceDays (integer) Description The number of days kept in the database (default: 40 days) The number of partitions which must be created in advance Pathname (2. You must create one directory at least at installation.CONFIGURE Description This procedure allows the DBA to configure the global partitioning policy. Procedure BART_ARCHIVE_PURGE.

This procedure activates the Oracle database scheduler for calling each day (at 2:00 AM). This procedure is equivalent to the START_SCHEDULER procedure except that the first execution of the MANAGE_NEW_PARTITION procedure is immediate. New partitions are created if needed. This procedure allows the DBA to manually trigger the creation of new partitions.REMOVE_DIRECTORY This procedure allows you to configure tablespace names. Resize the directory if the initial size is exceeded.STOP_SCHEDULER BART_ARCHIVE_PURGE. BART_ARCHIVE_PURGE.CONFIGURE Arguments partitionDays (integer) Description The number of days kept in the database (default: 40 days) . CONFIGURE_TABLESPACE BART_ARCHIVE_PURGE. You must create one directory at least at installation. the MANAGE_NEW_PARTITION procedure.ADD_DIRECTORY This procedure allows creating a new directory. BART_ARCHIVE_PURGE. This procedure allows the DBA to remove a directory which is no more used for storing new tablespaces. NOTES Each tablespace name is unique and is of the form BART_yyyymmdd where yyyymmdd is a date. to resize an existing directory or to reactivate a removed one for storing tablespaces. This procedure stops the MANAGE_NEW_PARTITION scheduling.RUN_SCHEDULER Execute the following procedures with the required arguments: Procedure BART_ARCHIVE_PURGE.BART_ARCHIVE_PURGE.START_SCHEDULER BART_ARCHIVE_PURGE.MANAGE_NEW_PARTITION BART_ARCHIVE_PURGE.

MANAGE_NEW_PARTITION none BART_ARCHIVE_PURGE. default: ‘250MB’) BART_ARCHIVE_PURGE.REMOVE_DIRECTORY directory (varchar) BART_ARCHIVE_PURGE.partitionAdvanceDays (integer) BART_ARCHIVE_PURGE.RUN_SCHEDULER none none none .STOP_SCHEDULER BART_ARCHIVE_PURGE. The suffix of the datafile. The size of the directory.ADD_DIRECTORY directory (varchar) The number of partitions which must be created in advance Pathname (2. The directory to be removed fileSize (varchar. CONFIGURE_TABLESPACE tablespaceprefix (varchar) tablespacesuffix (varchar) datafilesuffix (varchar) BART_ARCHIVE_PURGE.START_SCHEDULER BART_ARCHIVE_PURGE. default is “.000 characters at maximum) Initial size. it is located after the date of the form yyyymmdd. default is “BART_”. The maximal size is 128G. The suffix of the tablespace name. automatically increased by Oracle if needed The prefix of the tablespace name.dat”. default: ‘1GB’) extendSize (varchar.

.

xml file located in the configuration folder Set the following parameters in the different sections: . Each file includes detailed information.The SAP CC 2. Setting up the Quick Configuration Use For checking that the Diameter Server can run. Procedure Stop the Diameter Server Edit the serverConfig. It communicates with the SAP CC Core Server. few parameters must be set up.0 Diameter Server based on NW AS Technology is an optional software component of SAP Convergent Charging used in a real time scenario for handling the mediation function in front of SAP CC and managing requests for rating and charging events or sessions. You can configure the Diameter Server by editing the configuration files listed in the Installation Guide from SAP Service Marketplace.

Parameter URI OCSHostName OCSPort OperationTimeout Description IP address of the host that runs the Diameter Server IP address of the host that runs the SAP CC Core Server Port number of Core Server (usually 9000) Timeout (in ms) of the charging request Setting up the Basic Configuration Use The serverConfig.xml file located in the configuration folder Set the following parameters in the different sections NOTE The parameter RootLoggerLevel can be changed while The Diameter Server is running. five rotating log files are generated by the SAP CC Diameter Server. Setting up the Logging Configuration Use By default. Procedure Stop the SAP CC Diameter Server Edit the logging.xml file includes several sections: Stack identity parameters Capabilities exchange parameters Supported Application Ids Supported Vendor Ids Peer policy parameters Incoming messages handling parameters Routing table to handle proxiable requests Charging Stack parameters Log level (can be changed dynamically) You can set the parameter values accordingly to your business and your usage of SAP CC Diameter Server. Consult first the Technical Reference Guide from SAP Service Marketplace.properties file located in the configuration folder Set the parameters accordingly to your business . Diameter Server reads the server configuration file periodically and changes the log level according to the value set. Procedure Stop the SAP CC Diameter Server Edit the serverConfig. More precisely.

A system administrator must not change these settings. Procedure . Procedure Stop the SAP CC Diameter Server Edit the avpDictionary. Setting up the Service Dictionary Use Consult first the Technical Reference Guide from SAP Service Marketplace. This file is only read when the Diameter Server starts Set the parameters accordingly to your business and check the logs This section lists the configurations determined by the solution consultants and by the technical consultants of your project team. Procedure Stop the SAP CC Diameter Server Edit the serviceDictionary.xml file located in the configuration folder. A system administrator must not change these settings.xml file located in the configuration folder Set the parameters accordingly to your business and check the logs Setting up the AVP Dictionary Use Consult first the Technical Reference Guide from SAP Service Marketplace.xml file located in the configuration folder.Changing the Settings of the Service Dictionary Use The Service Dictionary is designed by the project team during the implementation phase. Procedure Stop the SAP CC Diameter Server Edit the serviceDictionary. This file is only read when the Diameter Server starts Set the parameters accordingly to your business and check the logs Changing the Settings of the AVP Dictionary Use The AVP Dictionary is designed by the project team during the implementation phase.

In a mock mode.Stop the SAP CC Diameter Server Edit the avpDictionary.xml file located in the configuration folder Set the parameters accordingly to your needs . EXAMPLE OF CONFIGURATION FILE <?xml version="1. the Diameter Server can simulate the answers of the charging requests that are normally sent to the Core Server.xml file located in the configuration folder Set the parameters accordingly to your business and check the logs CAUTION The Service-Parameter-Value AVP has to be defined in the dictionary since it is not supported in 3GPP any longer.Specific AVP Dictionary for Diameter Server --> <avpDictionary version="1. Developers and testers can fine configure these answers.0" encoding="UTF-8"?> <!-.0" date="2008-01-01T00:00:00"> <avpDesc name="Call-Type" code="943" type="UTF8String" vendorId="12084"/> <avpDesc name="Service-Parameter-Value" code="442" type="OctetString" vendorId="12084"/> <avpDesc name="Service-Information" code="873" type="Grouped" vendorId="10415"/> <avpDesc name="Service-Generic-Information" code="1256" type="Grouped" vendorId="10415"/> <avpDesc name="Deny-Reason" code="10027" type="Enumerated" vendorId="11"/> <avpDesc name="Play-Announcement-Id" code="10045" type="Unsigned32" vendorId="11"/> <avpDesc name="Subscriber-Profile" code="10008" type="Grouped" vendorId="11"/> <avpDesc name="Subscriber-Language" code="10009" type="UTF8String" vendorId="11"/> </avpDictionary> Setting up the Server for Development or Testing Purpose Use The SAP CC Diameter Server can run without the SAP CC Core Server. Procedure Stop the Diameter Server Edit its launch script and add the –mock option Edit the mockConfig.

0 uses scenario files for configuring SAP CC Import/Export Connector software. . Consult online help of the SAP CC Connector Administration Tool from the SAP Help Portal:  SAP CC 2. Create a new scenario and save it in a file: CAT  File  New  Scenario. Online help is directly accessible from the graphical user interface.Setting up a Scenario Use SAP CC 2. This section lists the configurations determined by the solution consultants and by the technical consultants of your project team.0  CAT  About Scenario . Procedure Start the Connector Administration Tool (CAT) and log on.

Consult online the SAP CC IEC Javadoc from the SAP Help Portal: CC 2. customize the reporting or customize the connection with the SAP CC BART Server.  SAP . Activities As technology consultant.Implementing Java Classes for Adding Functions Use You can customize your SAP CC Import/Export Connector program by adding your own Java classes. you have to: Specify and implement your Java classes according to the Java API Specification of SAP Convergent Charging. You can add new actions.0  Development  Import/Export Connector Javadoc .

Type Style
Example Text

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

Example text EXAMPLE TEXT

Example text

Example text <Example text>

EXAMPLE

Icon

Meaning Caution Example Note Recommendation Syntax

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

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

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

Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 © Copyright 2010 SAP AG. . 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. All rights reserved.