2 Creating and Configuring the Duplicate Check Cartridge Node

This chapter describes how to create and configure the Oracle Communications Offline Mediation Controller duplicate check enhancement processor (EP) cartridge node to check for duplicate records while processing call detail records (CDRs).

Before reading this chapter, you should be familiar with:

  • Offline Mediation Controller cartridge concepts and Node Programming Language (NPL).

About the Duplicate Check EP Cartridge Node

The duplicate check EP node creates the partitions as configured based on the CDR timestamp. The partitions are created for the configured time period. When a CDR is processed, the duplicate check node creates the partition in the memory and adds the duplicate check keys in the partition and in the duplicate check file.

When new CDRs are processed, the duplicate check node compares the keys in the CDR with the keys in the partition. If the key already exists, the record is rejected and written to a file in the duplicate record storage directory, and the information related to the duplicate records are written to a log file. If the key does not exist, it is added to the partition and the duplicate check file.

Creating a Duplicate Check EP Node

To create a duplicate check EP node:

  1. Log on to Offline Mediation Controller Administration Client.

    The Node Hosts & Nodes (logical view) screen appears.

  2. In the Mediation Hosts table, select a host.

  3. In the Nodes on Mediation Host section, click New.

    The Create a Node dialog box appears.

  4. Select Wireless and click Next.

  5. Select Enhancement Processor (EP) and click Next.

  6. Select Duplicate Check EP and click Finish.

    The New Node dialog box appears.

  7. In the Name field, enter a name for the node.

  8. From the Rule File list, select the rule file that matches the type of input file processed by the EP node.

    To edit the rule file, see "Configuring the NPL Rule File for Duplicate Check EP".

  9. Click the General tab and do the following:

    1. From the Debug list, select one of the following:

      To log short debug messages in the node log file, select OFF.

      To log detailed debug messages in the node log file, select ON.

    2. In the Max Log File Size field, enter the maximum size in bytes for the log file. When the log file reaches its limit, the node closes the file and opens a new file. The minimum value is 50000 and the maximum value is 2000000000.

    3. Select the Enable Statistics check box, which enables node statistics.

    4. Select the Enable bulk read/write check box, which enables the node to read or write records in bulk.

    5. In the Read Timer field, enter the number of seconds Offline Mediation Controller waits before checking for incoming records. The minimum value is 1 and the maximum value is 3600.

    6. In the NARs Per File field, enter the maximum number of NARs allowed in an output file. The minimum value is 1 and the maximum value is 10000.

    7. In the Idle Write Time field, enter the number of seconds Offline Mediation Controller waits before transferring the NAR output file to the output directory of the processing node, whether or not it has reached its maximum size. The minimum value is 1 and the maximum value is 3600.

    8. Select the Backup NAR Files check box, which enables the node to back up each processed NAR file.

    9. If you selected Backup NAR Files, enter the number of days to retain the backup NAR files in the NAR File Retention Period field.

    10. Select the Input Stream Monitoring check box, which enables the node to monitor the input stream of records and trigger an alarm if no input records arrive for the set interval.

    11. If you selected Input Stream Monitoring, enter the duration of time that the node waits for the input stream of records before triggering an alarm if there is no input in the Interval field; select the time period: Day, Hour, or Minute.

  10. Click the Threading Options tab and do the following:

    • In the Number of Processor Threads list, select the number of processing threads. The maximum value is 20.

  11. Click the De-Duplication tab and do the following:

    1. Do one of the following:

      To use a scratch directory to store the duplicate check files containing the keys, select the Use Scratch Directory check box.

      To use a different directory from the scratch directory to store the duplicate check files containing the keys, enter the path of the directory in the Storage Directory field.

    2. From the Partition Size list, select the type of partition: Daily or Hourly.

    3. In the Retention Limit field, enter how long to retain the partition based on the type of partition. For example, if the type of partition is Daily, the value is in days.

    4. In the Number of Partitions in Memory field, enter how many partitions to retain in memory.

    5. In the Duplicate Records Storage Directory field, enter the path of the directory where all the files containing duplicate records are stored.

    6. From the Duplicate Records Push Time Unit list, select the time unit for the time that the node waits before the file containing the duplicate records is moved from the scratch directory to the storage directory.

    7. In the Duplicate Records Push Time Period field, enter the duration of time that the node waits before the file containing the duplicate records is moved from the scratch directory to the storage directory.

    8. In the Number of Duplicate Records per file field, enter the maximum number of duplicate records to store in the file. The minimum value is 1 and the maximum value is 10000. The default is 2000.

  12. Click the Destination tab and do the following:

    1. Select the Enable check box, which enables the connection between the EP node and any destination cartridge node.

    2. From the Routing list, select one of the following:

      If the Enable check box is not selected, Routing is set to None.

      To enable multicast routing between the EP node and the destination cartridge node, select Multicast.

      To enable round-robin routing between the EP node and the destination cartridge node, select Round Robin.

  13. Click Save.

Configuring the NPL Rule File for Duplicate Check EP

To configure the NPL rule file for duplicate check EP:

  1. Log on to Offline Mediation Controller Administration Client.

    The Node Hosts & Nodes (logical view) screen appears.

  2. In the Mediation Hosts table, select the mediation host that contains the duplicate check EP node.

  3. In the Nodes on Mediation Host section, select the duplicate check EP node that you want to configure, and click Edit.

    The Node dialog box appears.

  4. From the Rule File list, select one of the sample NPL rule files.

  5. Click Edit for the selected rule file.

    The NPL Editor dialog box appears.

  6. In the configuration block, do the following:

    • Add the following entry, which defines the CDR fields to be used as the duplicate check keys:

      DUP_CHECK_KEYS "FieldName1 FieldName2 ...";
      

      where FieldNameX is the name of the field in the CDR.

      For example:

      DUP_CHECK_KEYS "calling_number session_id seq_no";
      
    • Add the following entry, which defines the event timestamp based on which the partition is created:

      DUP_CHECK_EVENT_TIME_FIELD "TimestampField";
      

      where TimestampField is the name of the timestamp field in the CDR.

      For example:

      DUP_CHECK_EVENT_TIME_FIELD "start_time";
      
  7. Compile and save the file.

  8. Close the NPL Editor dialog box.

  9. Click Save.

    The configuration is saved.