offline ure

Offline URE

Lesson Objectives

By the end of this lesson, you will be able to:• Configure the offline rater• Start/Stop the offline rater• Perform basic troubleshooting

Configuring the Offline Rater

Rater Configuration Notes

Starting and Stopping Offline Rater

Troubleshooting

Configuring the Offline Rater (1)

Perform these steps to configure the Offline Rater: 1. Set up the configuration environment. The installer must log in

as root, and then issue the following commands:

export OMNI_HOME=/home/omni

export SHM=202

2. Create a unit-specific OFRplatform file.

The OFRconf package and the OMAP tar file deliver a OFRplatform template which contains the default configuration setup. To create one for the unit, copy the file as follows:

cd $OMNI_HOME/ipf/conf

cp OFRplatform OFRplatform.<ce>

3. Edit the files as appropriate based on the parameters.

NOTE: For Offline Rater, all static parameters are relocated to the OFRplatform.static file. No changes should be made to this file on site, unless that change is provided as a workaround in the RDD or STF.


4. Modify the /etc/host file.

In the /etc/host file, ensure that the initial setup of the file looks like the following example:

# Do not remove the following line, or various programs# that require network functionality will fail.127.0.0.1 localhost.localdomain localhost172.16.120.186 ofr1 ofr1-a

5. Set up remote hosts.

The OFRconf package and OMAP tar file deliver a hosts.OFR template which contains the default setup for the /etc/hosts file.


To create a hosts file for the unit, follow these steps:

a. Copy the file as follows:

cd $OMNI_HOME/conf

cp hosts.OFR hosts.<ce>Edit the hosts.<ce> file as appropriate for the unit. Notice that only the host portion of the IP address should be edited. Included here is a line from the hosts.<ce> file, in which only the 224 should be changed. All other parameters enclosed between “<” and “>” are tokens, which will be substituted by the configureOFR script: <HSBN_CLASS_C_NETIC>.224 <CE1_HOST> <CE1_HOST2> <CE1_HOST>.<UNIT_DOMAIN>

NOTE: The hosts.OFR file can be prepared by first extracting it from the OMAP tar file. A single copy which contains all the host name and IP addresses for the site can be created and used for all DGUs.

b. IP and UDP services. The OFRconf package and OMAP tar file deliver a services.OFR template which contains the default setup for the /etc/services file. This file does not need to be modified.


6. Configure the SLU by performing these actions:

a. Log in as root.

b. Run the configureOFR application with these commands:

cd /home/omni/ipf/conf

./configureOFR <hostname>

c. Review the results of configureOFR The installer can use tools such as script to capture the output of the configureOFR script to ensure the script executed properly.

In addition, there is a log file, $OMNI_HOME/ipf/conf/.conflog, which logs the start and end of the configureOFR execution, as well as any warning and error events.

Rater Configuration Notes (1)

The following default configuration files are installed as part of the SLF rpm(s) (all in /home/omni/conf): • commonCfg.xml• ureCfg.xml• tspCfg.xml

• The oracle user name should be updated in both these files. • The oracle password, if not provided by the Security server, will also

need to be provided in these files (as DefaultOraclePassword)• Copy the /home/omni/bin /pps.CoreUREModules.Generic in

/home/omni/bin/pps.CoreUREModules.202.

Proper configuration must be done before offline URE can be run on the SLU.


For offline URE, add the following line if it is not present:

ccap

$OMNI_HOME/conf/commonCfg.xml• Update the parameter DefaultDatabaseInstance with the

Rating database instance if needed. This parameter is used to specify the Rating database instance for getting password from the Security server. The database instance must be provisioned in the Security server.

• Update the parameter DefaultDatabaseType with the Rating database type if needed. This parameter is used to specify the database type for getting password from the Security server for the Rating database.


$OMNI_HOME/conf/ureConf.xml

Update the following parameters:• AdminDbName• AdminDbType• BILLING_DB_ INSTANCE• BILLING_DB_ USER_NAME• BILLING_DB_TYPE• MaxLogFileSize• MaxNumberLogFile


HOST_CONTACTS table in the admin (unscaled or ORP) database:• Insert a row into HOST_CONTACTS to specify the Offline URE’s local host

login information (there must be one entry per host). • The fields host_ready, host_done, host_output, host_work and host_error must

be populated with valid directory paths which must exist on the offline SLU and have read/write permissions for sncpuser.

• Create the directory paths before running the offline URE if those directories do not exist on the SLU.

Example:• insert into HOST_CONTACTS(HOST_CONTACT_ID, HOST,

HOST_MODULE, HOST_LOGIN, HOST_PASSWORD, HOST_READY, HOST_DONE, HOST_WORK, HOST_ERROR, ARBOR_DETAIL, HOST_PROCESS_DELETE, HOST_FTP_DELETE, CHANGE_WHO, CHANGE_DT, HOST_OUTPUT)the following values (64, 'slfslu', NULL, 'sncpuser', 'sncpuser', '/home/sncpuser/ccap/usage/ready', '/home/sncpuser/ccap/usage/done', '/home/sncpuser/ccap/usage/work','/home/sncpuser/ccap/usage/error', NULL, 'N', 'N', 'Test', SYSDATE, '/home/sncpuser/ccap/usage/output');


PROCESS_SCHED table in the admin (unscaled or ORP) database:• Before running the Offline URE to process usage files, a row needs to

be in PROCESS_SCHED for scheduling offline rater task as either recurring or nonrecurring task.

• Example:

Insert into PROCESS_SCHED (process_name, task_name, task_cycle, task_mode, sched_start, task_intrvl, task_status, task_priority, slide_time, db_name, sql_query, debug_level, usg_version)

values (ccap01, ccap01, N, 1, SYSDATE - 1, 60, 0, 1, 0, FDFX300A, NULL, 1, 0)


$ORACLE_HOME/network/admin/tnsnames.ora:• The Billing database (BLUS or OR server) instance, as

specified with the parameter AdminDbName in ureCfg.xml, must have an entry in tnsnames.ora for the Offline URE to access the Billing database.

• The Rating database instance(s) must also have an entry in the file. Currently, the Rating database instance uses the following name convention:

sdp<rating DB id>_n<1/2>.world

where the <rating DB id> is the value for -ratingdb in the URE command line, for example, sdp9_n1.world.

• An entry is also needed for the Calling Circle database using the following naming convention:

ccd<calling circle DB id>_n<1/2>.world

where the <calling circle DB id> is the value defined for calling circle DB in server_definition, for example, ccd1_n1.world.


Environment variables:1. GFR_LOG_PRIORITY for CCAP logging:

• Set it to 5 for logging fatal error message only• 4 for all error messages• 3 for warning and error messages• 2 for informational messages as well as warning and error messages• 1 for debug messages plus messages for 2 and 0 for all messages

including trace messages. • It is recommended that GFR_LOG_PRIORITY is set to 2 in

production environment.

2. TZ: Set it to the appropriate time zone (for example, EST5EDT).

3. OAM_ENV_CONN_MA: Set it to FALSE if there is no UPA to connect to.

4. LD_PRELOAD: If sftp protocol is used for transferring files (system parameter URE/FTP_TRANSFER_PROTOCOL), this environment variable must be set to $OMNI_HOME/bin/libcrypto.so.


5. For running the Offline URE with UPA, the following environment variables must be se t in /home/sncpuser/profile/omnisetup.sh:

set ARBOR_ADMIN_DB_INST to <unscaled DB> or <ORP DB> set ARBOR_ADMIN_USER to <DB user name> set ARBORBIN to bin directory where executables are stored (e.g. /home/omni/bin) set ARBORLOG to a directory where log files are stored(e.g. /home/omni/Logs) set OAM_ENV_CONN_MA to TRUE set ISM_AGENT to 22021 set ISM_AGENT_JAVA to 22022 Set OA_ENV_RECONN_ATTEMPT_NUMBER to 10 Set OAM_ENV_RECONN_ATTEMPT_INTERWAIT 20 Set OAM_USE_PWE 0

All environment variables can be set in /home/sncpuser/profile/omnisetup.sh


System Parameters:• Some of the offline URE log messages are controlled with

the system parameter URE/LOGLEVEL. To get full traces, CHAR_VALUE for the parameter should be set to HIGH (the default is MEDIUM).

• Set INT_VALUE for parameter RTNG/OFFLINE_CDR to 1 if an RTB-style CDR file needs to be generated for offline usage files (the default is 0).

Starting and Stopping Offline Rater (1)

• The Offline URE has to be run from the /home/omni/bin directory.

NOTE: Offline processes( TSP, URE, IPCBM, and so on) should be started as user sncpuser on the Offline SLU because the

environment is set up correctly for user sncpuser by cinfigureOFR.

• To start TSP at the command line:• Set the environment variable OAM_ENV_CONN_MA to false

before starting it.• TSP must be started in non-omni mode with the user login as

follows:

tsp -nonomni -start -db_timeout 300 -log tsp_log• TSP must be running and ready to process messages before the

Offline URE starts.


The Offline URE must be started with the following options:• -C: This option indicates this is offline URE• -ratingdb <db_id>: This option provides the Rating database id the

URE runs on, where <db_id> is a valid Rating database id (1-99).• -instance <instance_id>: This option specifies the instance id for

this URE run, where <instance_id> should be an integer.• -ccapname <process_name>: This <process_name> should be

used to populate PROCESS_SCHED.process_name when scheduling the offline Rater task.

• If a log file is needed, use the option -log [<filename>] where <filename> should be just the base file instead of a full path.

• It is also recommended to turn off URE tracing using the option -trace-mask 0 in a production environment.

Example: Start the Offline URE on Rating database 9 as instance 1:

% ure -C -ratingdb 9 -instance 1 -ccapname ccap01 -trace-mask 0 -log UreLogFile


To start/stop TSP with UPA:• Ensure that environment variables are set in

/home/sncpuser/profile/omnisetup.sh (as mentioned previously in Rater Configuration Notes (8), point 5 for working with UPA).

To start:• execute_process -g application -p tsp01 -d start -t i -bp

tspccap• Here the name following -p should be unique if more than

one TSP is started on the same node.• This will actually be started as:

./tsp -nonomni -tspname tsp01 -SHM $SHM -db_timeout 300 -start -log CcapTspLog_tsp01

• $SHM is the value of environment variable in the command above. The log file will be CcapTspLog_tsp01 in /home/omni/Logs.


To stop:• execute_process -g application -p tsp01_0 -d stop -bp

tspccap

• TSP started with -p tsp01 will be stopped.• To start more than one TSP on the same node, ensure that

the name following -p is unique per TSP. • Execute_process -g application -p tsp02 -t I -bp tspccap -d

start• The number following -shm must be at least 10 apart from

the existing $SHM in the environment.• This will actually be started as

./tsp -nonomni -tspname tsp02 -SHM 700 -db_timeout 300 -start -log CcapTspLog_tsp02

Troubleshooting

The offline OMD debugger is a standalone executable called alt_omd, which is a part of the package and is installed in the /home/omni/bin directory.

In cases where there is a need to print the TSP table in shared memory, do the following:

1. Run omd, by typing the following:

/home/omni/bin/alt_omd TSP

2. At the prompt type:

DUMP-TABLE=<table name>

• Note that a table name must be in upper case as well as the command name DUMP-TABLE.

• Also the -dbg_mask 0xffef parameter can be used on the appropriate command line in the nodestart file in the /home/omni/conf directory.

Summary

This lesson has covered:• Configuration of the Offline Rater• Start/stop commands• Basic troubleshooting guidelines

offline ure

Documents