1. Configuring Pipeline Rating and Discounting
  2. Installing Pipeline Manager
  3. Testing Pipeline Manager

75 Testing Pipeline Manager

This chapter describes basic start, stop, and configuration tests for Oracle Communications Billing and Revenue Management (BRM) Pipeline Manager.

About Testing Pipeline Manager

To test Pipeline Manager, follow the procedures in these sections:

Note:

To perform a test start and stop of the Pipeline Manager database, contact your database administrator.

  1. Starting Pipeline Manager

  2. Testing Pipeline Manager without a Database Connection

  3. Testing Pipeline Manager with a Database Connection

  4. Testing Single and Multiple Pipeline Rating with BRM

Starting Pipeline Manager

You start Pipeline Manager by using one of the following methods:

  • The pin_ctl utility.

  • The ifw command from the pipeline_home directory: 

    % pipeline_home/bin/ifw -r RegistryFile
  

    where RegistryFile is your registry file name.

Note:

When Pipeline Manager cannot establish a connection with the Pipeline Manager database (most likely because the database is down), you receive an error message and the Pipeline Manager startup is canceled.

If there are startup issues, the system stops and sends notifications to the process log and stdout.

Note:

The path and file name of the process log are defined in the ProcessLog section of the startup registry.

Stopping Pipeline Manager

You stop Pipeline Manager by using the pin_ctl utility, or a semaphore.

Testing Pipeline Manager without a Database Connection

To test Pipeline Manager without database access:

  1. Go to the system directory.

  2. Source the source.me.sh for the shell: 

    % source source.me.sh

    Note:

    The source.me.sh is for a bash shell. If you use a C shell, enter source.me.csh.

  3. Go to the pipeline_home directory.

  4. Start Pipeline Manager with the simple.reg registry file: 

    bin/ifw -r pipeline_home/samples/simple/simple.reg

    The system starts without a database connection and two sample EDR files are processed.

  5. To confirm that the sample EDR files are processed, go to the pipeline_home/samples/simple/data/out directory and open the output file.

  6. If an error occurs:

    • An output reject file is created in the pipeline_home/samples/simple/data/rej directory.

    • The input file is moved to the err directory. You can find it in the pipeline_home/samples/simple/data/err directory.

  7. Stop Pipeline Manager.

Testing Pipeline Manager with a Database Connection

To test Pipeline Manager with database access:

  1. Go to the system directory.

  2. Source the source.me.sh for the shell: 

    source source.me.sh

    Note:

    The source.me.sh is for a bash shell. If you use a C shell, enter source.me.csh.

  3. Open the pipeline_home/samples/simple/simple.reg file by using a text editor such as vi.

  4. In the ifw.DataPool.PrefixDescData section:

    • Comment out the Source parameter entry with the File value and uncomment the entry with the Database value.

    • Be sure that the DataConnection parameter is set to ifw.Datapool.Login.

  5. Be sure that the DBC module is configured with values for the UserName, PassWord, and DataBaseName parameters.

  6. Save the file.

  7. Start Pipeline Manager with the simple.reg registry file. 

    bin/ifw -r pipeline_home/samples/simple/simple.reg

  8. If you previously tested Pipeline Manager without a database connection, move the done EDR files from the /samples/simple/data/done directory to the /samples/simple/data/out directory and rename the file to *edr.

    The system is running without a database connection; and it processes two sample EDR files.

  9. To confirm that the sample EDR files are processed, go to the pipeline_home/samples/simple/data/out directory and open the output file.

  10. If an error occurs:

    • An output reject file is created in the pipeline_home/samples/simple/data/rej directory.

    • The input file is moved to the err directory.

      You can find it in the pipeline_home/samples/simple/data/err directory.

  11. Stop Pipeline Manager.

Testing Single and Multiple Pipeline Rating with BRM

This test uses the whole range of Pipeline Manager functions. To perform a wireless test run:

  1. Go to the system directory.

  2. Source the source.me.sh for the shell: 

    source.me.sh

    Note:

    The source.me.sh is for a bash shell. If you use a C shell, enter source.me.csh.

  3. Run the pipeline_home/conf/pricingdata/Oracle/insertWIRELESS_SAMPLE.pl script. 

    insertWIRELESS_SAMPLE.pl

    Note:

    If you ran this script in a previous test, you do not have to run it again.

  4. Open a sample wireless registry file.

    For single pipeline testing: pipeline_home/conf/wireless.reg.

    Note:

    To isolate potential problems, perform a single pipeline test first.

  5. Be sure that the DBC module is configured with values for the UserName, PassWord, and DataBaseName parameters.

  6. Start Pipeline Manager.

    For single pipeline testing, use the wireless.reg registry file: 

    bin/ifw -r conf/wireless.reg

  7. Create sample CDRs.

    See "Creating a Sample CDR File".

    Note:

    Use the file naming format teststring.edr, where string is any string. The CDRs must match your BRM data (service, origin, timestamps).

  8. Stop Pipeline Manager.

Creating a Sample CDR File

Your sample CDR must be formatted using:

  • Plain ASCII

  • Semi-colon-separated

  • One record per line

All lines, including the last record, must end with a NL (new line) character.

Example 75-1 Sample Format:

service-code;a-number;b-number;start-time;duration;vol-sent;vol-recieved;callclass;cell-id;apn
  

Table 75-1 describes CDR field formats and restrictions:

Table 75-1 CDR Field Formats

Field Description and Format

service-code

The service code.

Maximum length: 3 characters.

The following service code values are predefined in the sample charge:

  • TEL

  • GPR

  • SMS

  • WAP

  • DAT

  • FAX

a-number

The call's originating number.

Maximum length: 40 characters.

Sample value: 00491729183333

b-number

The call's target number.

Maximum length: 40 characters.

Sample value: 004941067600

start-time

The call start time.

Format: YYYYMMDDHHMISS

Sample values: 20011114184510 (for '14.11.2001 18:45:10')

duration

The call duration in seconds.

Maximum length: 11 digits.

Sample value: 300 (for 5 minutes)

vol-sent

The number of bytes sent in the call.

Maximum length: 11 digits.

Sample value: (1024 for 1 KB)

vol-received

The number of bytes received in the call.

Maximum length: 11 digits.

Sample value: (1024 for 1 KB)

(Optional) callclass

The class of call.

Maximum length: 5 characters.

The following call class values are predefined in the sample charge:

  • Conf = Conference Call

  • Mail = Mailbox Inquiry

  • MOC = Mobile-Originated Call (Outgoing Roaming)

  • MTC = Mobile-Terminated Call (Incoming Roaming)

apn

The access point name for the call.

Maximum length: 64 characters.

Sample use: specifying the URL for GPRS

Example 75-2 Sample CDR Records

TEL;00491729183333;004941067600;20011114184510;300;0;0;;;
TEL;00491729183333;004941067600;20011114184510;300;0;0;Mail;47113;
TEL;00491729183333;004941067600;20011114184510;300;0;0;Conf;98765;
TEL;00491729183333;004941067600;20011114184510;300;0;0;MOC;238476;
TEL;00491732410;004941067600;20011114184300;300;0;0;NORM;123456;
TEL;00491732411;004941067600;20011114184300;270;0;0;NORM;123456;
TEL;00491732412;004941067600;20011114184300;110;0;0;NORM;123456;
DAT;00491732413;004941067600;20011114184300;50;0;0;NORM;123456;
FAX;00491732414;004941067600;20011114184300;12;0;0;NORM;123456;
TEL;00491732415;004941067600;20011114184300;1;0;0;NORM;123456;
SMS;00491732416;004941067600;20011114184300;63;0;0;NORM;123456;
TEL;00491732417;004941067600;20011114184300;37;0;0;NORM;123456;
TEL;00491732418;004941067600;20011114184300;132;0;0;NORM;123456;
TEL;00491732419;004941067600;20011114184300;60;0;0;NORM;123456;
GPR;00491732410;0049;20011114184510;300;78965;5054;;001121;hamburg.portal.com

Troubleshooting

If you cannot start Pipeline Manager, it can be due to the following problems or errors:

Note:

Error messages are written into the process log file and into the pipeline log files.

  • The user environment is not set correctly.

    Solution: Correct the errors in the environment settings.

  • The registry contains errors.

    Solution: Check the registry for type errors, missing brackets, missing or incorrect entries, and so on.

    Note:

    Registry entries are case-sensitive.

  • Paths are missing.

    Solution: Create the missing paths according to the definition in the startup registry.

  • A lock file already exists.

    Solution: If the BRM framework has not been stopped correctly, a lock file already exists. Delete the lock file and then stop and restart Pipeline Manager framework.

  • The database is not opened/the listener has not been started.

    Solution: Open the database and start the listener.

  • The database entries contain errors.

    Solution: Check the created database schemes.