About Installation and Removal

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

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.

ACS Packages

An installation of ACS includes the following packages, on the:

SMS:
- acsSms
- acsCluster (for clustered SMS)
SLC:
- acsScp
VWS:
- acsBe

Installing acsSms Packages on a Clustered SMS

Raw Devices

ACS can allocate tablespace storage based on raw (without a file system) partitions. This enhances the performance of ACS on the SMS.

If you are using the raw devices option, you must create the raw partitions before installing the database using tools such as the system’s format command.

The raw devices file (which you will be prompted to complete during the installation) must contain the full paths of the device files for the appropriate partitions.

The partitions must be at least as big as the required datafile sizes listed in the sizing file used by the installation.

Raw Devices Configuration

Follow these steps to configure raw devices:

Note:

This is required only if the installation uses raw devices in place of datafiles.

If your database sizing was set to large, create disk partitions of the following sizes:
- 2501 MB
- 1501 MB
- 1501 MB
For more information about the format command, see man format.

If your database sizing was set to medium, create disk partitions of the following sizes:
- 7002 MB
- 5002 MB
- 4002 MB
- 201 MB
- 101 MB
- 2 MB
For more information about the format command, see man format.
Edit the acs_devices.sh file specified above.
Change the line:
```
ACS_DATA_DATAFILE=
```
to
```
ACS_DATA_DATAFILE=/dev/did/rdsk/partition
```
Where:
partition is the name of the partition (for example. d8s0).
Check the device files for the new partitions are readable and writable by the oracle user prior to commencing/continuing the installation.
Example Command:
```
chmod ugo+rw /dev/rdsk/d8s*
```

Example acs_devices.sh file

This is an example acs_devices.sh file.

#!/bin/sh
#
##########################################################################
# The following file is the structure required for knowledge of
# raw device utilisation.
##########################################################################
 
##########################################################################
# Raw device specification for datafile paths.
##########################################################################
ACS_DATA_DATAFILE=/dev/did/rdsk/d14s0
ACS_INDEX_DATAFILE1=/dev/did/rdsk/d14s1
ACS_INDEX_DATAFILE2=/dev/did/rdsk/d14s2

export ACS_DATA_DATAFILE ACS_INDEX_DATAFILE1 ACS_INDEX_DATAFILE2
##########################################################################

Checking the Installation

Refer to these checklists to ensure that ACS 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.

Checklist for SMS

Follow the steps to ensure ACS has been installed on an SMS machine correctly:

Log in to SMS machine as root.
Check the following directory structure exists with subdirectories:
- /IN/service_packages/ACS
- /IN/html/Acs_Service
Check that directories contain subdirectories and that all are owned by:
- acs_oper user (group oracle)
Log into the system as acs_oper.

Note:
This step is to check that the acs_oper user is valid
Enter sqlplus /. No password is required.

Note:
This step is to check that the acs_oper user has valid access to the database.
Check the entries of the /etc/inittab file.
Inittab Entries Reserved for ACS on SMS:
1. acs0 /IN/service_packages/ACS/bin/acsCompilerDaemonStartup.sh (runs acsCompilerDaemon).
2. acs1 /IN/service_packages/ACS/bin/acsStatisticsDBInserterStartup.sh(runs acsStatisticsDBInserter).
3. acs2 /IN/service_packages/ACS/bin/acsProfileCompilerStartup.sh (runs acsProfileCompiler).
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 for SMS.

Checklist for SLC

Follow the steps in this checklist to ensure ACS has been installed on an SLC machine correctly.

Log in to SLC machine as root.
Check the following directory structure exists with subdirectories:
- /IN/service_packages/ACS
Check that directories contain subdirectories and that all are owned by:
- acs_oper user (group oracle)
Log into the system as acs_oper.

Note:
This step is to check that the acs_oper user is valid
Enter sqlplus /. No password is required.

Note:
This step is to check that the acs_oper user has valid access to the database.
Check the entries of the /etc/inittab file.
Inittab Entries Reserved for ACS on SLC:
- acs3 /IN/service_packages/ACS/bin/acsStatsMasterStartup.sh (runs acsStatsMaster).
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 for SLC.

Process list for SMS

If the application is running correctly, the following processes should be running on each SMS:

Started from the inittab:
- acsCompilerDaemonacs
- StatisticsDBInserter
- acsProfileCompiler

Process list for SLC

If the application is running correctly, the following processes should be running on each SLC:

Started from the inittab:
- acsStatsMaster
Started during SLEE startup:
- slee_acs

System Manifest

Advanced Control Services (ACS) consists of several software processables and directories.

SMS Packages

The ACS application on the SMS will have the following directory structure in the directory /IN/service_packages/ACS.

Directory	File	Description
/bin	This directory contains run-time service processables and shell scripts.
	acsCompilerDaemonStartup.sh	Start up script.
	acsStatisticsDBInserter Startup.sh	Start up script.
	acsProfileCompiler Startup.sh	Start up script.
	acsLogCleanerStartup.sh	Start up script.
	acsDbCleanup.sh	Start up script.
	acsAddCallPlan	NA
	acsAddCustomer	NA
	acsAddGeography	NA
	acsAddServiceNumber	NA
	acsDecompile	NA
	acsMonitorCompiler	NA
	acsProfile	NA
	acsScheduleCallPlan	NA
	acsSetupAnnouncement	NA
/db	This directory contains install-time database scripts.
/etc	This directory contains run-time configuration files.
/etc/inittab	This directory contains background processes.
	acsCompilerDaemon	Background process.
	acsStatisticsDBInserter	Background process.
	acsProfileCompiler	Background process.
/lib	This directory contains run-time shared libraries and install-time shell scripts.
/tmp	This directory contains run-time and install-time log files.
	acsCompilerDaemon.log	Error log file.
	acsStatisticsDBInserter.log	Error log file.
	acsProfileCompiler.log	Error log file.
	acsLogCleaner.log	Error log file.
	acsDbCleanup.sh.log	Error log file.
/tmp/archive	This directory contains archived log files.

SLC Packages

The ACS application on the SLC will have the following directory structure in the directory /IN/service_packages/ACS.

Directory	Directory Files	Description
/bin	This directory contains run-time service processables and shell scripts.
	acsStatsMasterStartup.sh	Start up script.
	acsDecompile	NA
	acsLogCleanerStartup.sh	NA
	acsProfile	NA
	acsStatsLocalSLEE	NA
	acsSLSStartup.sh	NA
	cmnPushFilesStartup.sh	NA
	pinLogFileCleanup.sh	NA
	acsTriggerIF	NA
	acsTriggerIF.sh	NA
/db	This directory contains install-time database scripts.
/etc	This directory contains run-time configuration files.
/etc/inittab	This directory contains background processes.
/etc/inittab	acsStatsMaster	Background process.
/install	This directory contains install-time scripts for optional SLEE rc.d auto-start.
/lib	This directory contains run-time shared libraries and install-time shell scripts.
/tmp	This directory contains run-time and install-time log files.
/tmp	acsStatsMaster.log	Error log file.
/tmp/archive	This directory contains archived log files.