6 Background Processes

Overview

Introduction

This chapter explains the processes that are started automatically by Service Logic Execution Environment (SLEE).

Note: This chapter also includes some plug-ins to background processes which do not run independently.

c_rehash

Purpose

c_rehash is an openssl (on page 2) utility that takes a certificates directory as an argument. For each certificate file in the directory c_rehash creates a symbolic link to the certificate file, where the symbolic link name is the hash value of the certificates file. This enables fast certificate lookup for programs that search using the certificate hash value.

Location

c_rehash is located in the following directory on SLC and VWS nodes:

/IN/services_packages/DAP/bin

Startup

c_rehash is run by the dapReadyCertificates.sh script.

Configuration

This binary has no specific configuration. dapReadyCertificates.sh uses the variable DEFAULT_C_REHASH_PATH to define the location of c_rehash. The default value for the DEFAULT_C_REHASH_PATH variable is /IN/service_packages/DAP/bin.

dapIF

Purpose

dapIF is a SLEE interface. It is the main Oracle Communications Convergent Charging Controller Data Access Pack DAP client that sends and receives XML requests to external ASPs. It listens for SLEE requests and messages from ASPs.

It can trigger a PI command from a control plan using the DAP Send Request feature node when communicating with an ASP using the PIXML protocol.

Location

This binary is located on SLC and VWS nodes.

Startup

The interface is started by the SLEE, through the /IN/service_packages/DAP/bin/dapIF.sh shell script.

Configuration

dapIF is configured in the DAP section of eserv.config and the DAP Resources screen.

For more information about the:

  • eserv.config parameters, see DAP eserv.config configuration
  • DAP Resources screen, see Resources

Command line parameters

dapIF accepts the following command-line parameters at start up.

dapIF [-u usr/pwd|--user usr/pwd]

Note: Either the -u or the --user option can be used. 

-u usr/pwd
Syntax: -u usr/pwd
Description: The userid and password combination to use to log into the local Oracle instance.
Type: String
Optionality: Optional (default used if not set).
Allowed:  
Default: /
Notes: Cannot be used with the --user /usr/pwd option.
Example: -u smf/smf 
--user /usr/pwd
Syntax: --user usr/pwd
Description: The userid and password combination to use to log into the local Oracle instance.
Type: String
Optionality: Optional (default used if not set).
Allowed:  
Default: /
Notes: Cannot be used with the -u usr/pwd option.
Example: --user smf/smf

Failure

In case of failure alarms will be raised to the syslog.

Output

There is no output from this process.

dapMacroNodes

Purpose

This slee_acs plug-in provides the DAP macro nodes.

The nodes provided are:

  • Send Request
  • DAP Request

For more information about:

  • Macro node libraries, see ACS Technical Guide
  • The CPE, see CPE User's Guide

Location

This library is located on SLCs.

Startup

If dapMacroNodes is configured in acs.conf, it is made available to slee_acs when slee_acs is initialized. It is included in the acsChassis section of acs.conf in a MacroNodePluginFile entry as follows: 

acsChassis MacroNodePluginFile dapMacroNodes.so

Configuration

dapMacroNodes is configured in the DAP section of eserv.config. For more information, see DAP eserv.config configuration .

dapTypeConversion

Purpose

This SLEE-ACS plug-in provides conversions from ACS profile fields to types usable by DAP.

Location

Located on SLCs.

Startup

This library will be loaded based on configuration made by the packages on install.

Configuration

This library has no specific configuration.

ldapIF

Purpose

The ldapIF process is the main process in the LDAP IF component. It is a SLEE interface process. It accepts SLEE request messages initiated from DAP Request nodes within slee_acs control plans and translates them into LDAP requests to be sent over TCAP to waiting LDAP servers. The response is returned via the reverse path back to the DAP Request node.

Location

This binary is located on SLC nodes.

Startup

This task is started by the SLEE, by the following lines (or similar) in SLEE.cfg:

INTERFACE=ldapIF ldapIF.sh /IN/service_packages/DAP/bin
EVENT

Notes:

  • ldapIF.sh is a shell script which starts the ldapIF process.
  • The above are defaults and may vary.
  • Only a single instance of the ldapIF process will be started.

Configuration

Global configuration for ldapIF is in eserv.config (or wherever the ESERV_CONFIG_FILE environment variable indicates). The ldapIF can run without explicit configuration by using internal default configuration settings. Sending a SIGHUP signal to the ldapIF will force it to reload the eserv.config configuration.

For more information regarding ldapIF global configuration via eserv.config, see Global Configuration . For more information about causing ldapIF to reload its configuration, see Loading eserv.config configuration changes .

The ldapIF also uses per-ASP and per-operation settings. These are read from the SLC database (which contains copies of data replicated from the primary configuration on the USMS nodes). This database configuration is reloaded periodically as part of the normal ldapIF processing.

For more information regarding ldapIF service configuration via the DAP GUI, see DAP Resource Configuration .

Example configuration

For an example of an LDAP IF configuration section of an eserv.config file, see Example eserv.config file section .

Failure

The ldapIF will be monitored by the SLEE watchdog. The watchdog will restart ldapIF if it fails to respond to regular heartbeat events. For more details about how the watchdog monitors SLEE processes, see the SLEE Technical Guide.

ldapIF generates standard SMS alarm log messages to alert operators to any misconfiguration or abnormal processing. For more information about the alarms generated by ldapIF, see LDAP Interface for DAP Alarms Guide.

Output

The ldapIF process writes error messages to the system messages file. Under normal processing it will echo all alarm messages to STDERR. As a SLEE process, this will be merged with all SLEE output.

See Debug output for more information.

Status reports

At any time, you can send ldapIF a SIGUSR1 which will cause it to generate a status output listing to STDOUT. This will usually be redirected to /IN/service_packages/DAP/tmp/ldapIF.log file.

Sample output is:

** Connection Status ** ASP: LDAP1 Host: parker, port: 389
Connection state: IDLE** Connection Status ** ASP: LDAP2 Host:
grimm, port: 389 Connection state: READY Time connected: 11s Number
of pending (unsent) requests: 0 Number of requests waiting for
response: 0 Total requests processed: 30

Note: Generating the status report will not affect the connections, and can be done safely while the system is under production load.

libdapChassisActions

Purpose

This slee_acs plug-in implements the chassis actions which are used by the DAP macro nodes when they need to interact with components outside slee_acs.

Location

This library is located on SLCs.

Startup

If libdapChassisActions is configured in acs.conf, it is made available to slee_acs when slee_acs is initialized. It is included in the acsChassis section of acs.conf in a ChassisPlugin entry. 

acsChassis ChassisPlugin libdapChassisActions.so

Configuration

This binary has no specific configuration.

libDAPManager.so

Purpose

The libDAPManager.so is a combined connection manager and XML interface. A DAP client will use libDAPManager.so to communicate with an ASP.

Start-up

The library is linked at run time by a DAP client.

Location

libDAPManager.so is located wherever a DAP client is installed (for example, on SMS, SLC or VWS.

eserv.config configuration

libDAPManager has configuration available in the DAP section of eserv.config. For more information, see DAP eserv.config configuration .

Command line parameters

Command line parameters for libDAPManager.so are the same as those for dapIF. Refer to Parameters.

Failure

In the event of a failure, alarms will be written to the system log.

Output

There is no output from this process.

openssl

Purpose

openssl is used by dapReadyCertificates.sh and c_rehash to concatenate and rehash certificate files, creating links to the certificate files by hash value so that DAP can quickly find the certificates that it requires.

Location

openssl is part of the operating system installation. It is used on the SLC and VWS nodes. Depending on the operating systems version openssl is present as one of:

  • /usr/sfw/bin/openssl
  • /usr/bin/openssl with a symbolic link from /usr/sfw/bin/openssl to /usr/bin/openssl

Startup

openssl is started by dapReadyCertificates.sh .

Note: dapReadyCertificates.sh attempts to use openssl at the location configured in the openSSLPath parameter in the eserv.config file.

Configuration

openssl has some configuration which is set when used by dapReadyCertificates.sh . To configured this process, use the configuration available to dapReadyCertificates.sh.

sqlite3

Purpose

sqlite3 is an embedded SQL database engine which reads and writes directly to the database file on disk. Programs that link with the sqlite3 library can have SQL database access without running a separate RDBMS process.

It handles the DAP pending queue.

Location

This binary is located on the SMS node.

Configuration

sqlite3 accepts the following command line parameters.

/IN/service_packages/DAP/bin/sqlite3 path/pendingRequests.db
'<VACUUM|PRAGMA integrity_check>;'

To resize the database after a lot of data has been removed, run VACUUM as acs_oper.

To raise alarms about malformed db files, use PRAGMA integrity_check.