8 About Installation and Removal

This chapter provides information about the installed components for the Oracle Communications Convergent Charging Controller application described in this guide. It also lists the files installed by the application that you can check for, to ensure that the application installed successfully.

This chapter contains the following topics .

Installation and Removal Overview

For information about the following requirements and tasks, see Installation Guide:

  • Convergent Charging Controller system requirements
  • Pre-installation tasks
  • Installing and removing Convergent Charging Controller packages

CCS Packages

An installation of Charging Control Services includes the following packages, on the:

  • SMS:
    • ccsSms
    • ccsCluster (for clustered SMS
    • ccsDapSms
  • SLC:
    • ccsScp
  • VWS:
    • ccsBe
    • ccsVoucherBe

Checking the Installation

Refer to these checklists to ensure that CCS has installed correctly:

The end of the package installation process specifies a script designed to check the installation just performed. They must be run from the command line.

Check SMS Procedure

To ensure CCS has been installed on an SMS machine correctly
  1. Log in to SMS machine as root.
  2. Check the following directory structure exists with subdirectories:
    • /IN/service_packages/CCS
    • /IN/html/Ccs_Service
    • /IN/html/Ccs_FeatureNodes
  3. Check the directories contain subdirectories and that all are owned by:
    • ccs_oper user (group esg)
  4. Check for obvious errors in log files:
    • /IN/service_packages/CCS/ccsSms.install.log
    • /IN/service_packages/CCS/ccsScp.install.log
  5. Log into the system as ccs_oper.

    Note:

    This step is to check that the ccs_oper user is valid.
  6. Enter sqlplus /

    No password is required

    Note:

    This step is to check that the ccs_oper user has valid access to the database.
  7. Ensure that the required CCS tables have been added to the database. For a list of the tables which should have been added, see CCS database tables.
  8. Check the entries of following file:

    /etc/inittab

    Inittab Entries Reserved for CCS on SMS:

    1. ccs3 /IN/service_packages/CCS/bin/ccsBeOrbStartup.sh

      (runs ccsBeOrb)

    2. ccs4 /IN/service_packages/CCS/bin/ccsCDRLoaderStartup.sh

      (runs ccsCDRLoader)

    3. ccs5 /IN/service_packages/CCS/bin/ccsSSMDispatcherStartup.sh

      (runs ccsSSMDispatcher)

    4. ccs7 /IN/service_packages/CCS/bin/ccsCDRFileGeneratorStartup.sh

      (runs ccsCDRFileGenerator)

    5. ccs8 /IN/service_packages/CCS/bin/ccsProfileDaemonStartup.sh

      (runs ccsProfileDaemon)

    6. cc10 /IN/service_packages/CCS/bin/ccsChangeDaemonStartup.sh

      (runs ccsChangeDaemon)

  9. Check that the processes listed in the process lists are running on the relevant machine. For a list of the processes which should be running, see Process list - SMS.
  10. Tail logs for the processes listed in process list to ensure there are no errors.

Check SLC Procedure

To ensure CCS has been installed on an SLC machine correctly
  1. Log in to SLC machine as root.
  2. Check the following directory structure exists with subdirectories:
    • /IN/service_packages/CCS
  3. Check the directories contain subdirectories and that all are owned by:
    • ccs_oper user (group esg)
  4. Log into the system as ccs_oper.

    Note:

    This step is to check that the ccs_oper user is valid.
  5. Enter sqlplus /

    No password is required

    Note:

    This step is to check that the ccs_oper user has valid access to the database.
  6. Ensure that the required CCS tables have been added to the database. For a list of the tables which should have been added, see CCS database tables - SCP.

Check VWS Procedure

To ensure CCS has been installed on a VWS machine correctly:
  1. Log in to VWS machine as root.
  2. Check the following directory structure exists with subdirectories:
    • /IN/service_packages/CCS
  3. Check the directories contain subdirectories and that all are owned by:
    • ccs_oper user (group esg)
  4. Check for obvious errors in log files:
    • /IN/service_packages/CCS/ccsBe.install.log
  5. Log into the system as ccs_oper.

    Note:

    This step is to check that the ccs_oper user is valid.
  6. Enter sqlplus /

    No password is required

    Note:

    This step is to check that the ccs_oper user has valid access to the database.
  7. Ensure that the required CCS tables have been added to the database. For a list of the tables which should have been added, see CCS database tables.
  8. Check the entries of following file:

    /etc/inittab

    Inittab Entries Reserved for CCS on VWS:

    1. ccs8 /IN/service_packages/CCS/bin/updateLoaderWrapper.sh

      (only used if smsExtras is installed to run an instance of updateLoader. For more information about updateLoader, see Service Management System Technical Guide)

      Note:

      To define a TZ that the NOTICE messages by updateLoader are logged in, add DEBUG_TZ environment variable in the updateLoaderWrapper.sh script before the exec statement. For example: export DEBUG_TZ=Asia/Kolkata
    2. cccs9 /IN/service_packages/CCS/bin/ccsMFileCompilerStartup.sh

      (runs ccsMFileCompiler)

    3. cc10 /IN/service_packages/CCS/bin/cmnPushFiles-ccsVWARSExpiry.sh

      (runs an instance of cmnPushFiles for ccsVWARSExpiry)

    4. cc11 /IN/service_packages/CCS/bin/cmnPushFiles-ccsRewards.sh

      (runs an instance of cmnPushFiles for ccsRewards)

    5. cc12 /IN/service_packages/CCS/bin/cmnPushFiles-ccsExpiryMsgs.sh

      (runs an instance of cmnPushFiles for ccsExpiryMessageGenerator)

    6. (runs an instance of cmnPushFiles for ccsExpiryMessageGenerator)

      (runs ccsChangeDaemon)

  9. Check that the processes listed in the process lists are running on the relevant machine. For a list of the processes which should be running, see Process list - VWS.