Pipeline Does Not Work When Configuring Multiple Instances (Doc ID 1085483.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 to 7.4.0.0.0 [Release 7.3.0 to 7.4.0]
Information in this document applies to any platform.

Goal

After adding multiple instances of DIA_CDR_PlaybackPipeline, the pipeline does not work anymore.

This means that pipeline does not process all CDRs and that CPU usage of ifw processes goes up to 200%.

The following lines were added to registry file, in order to make multiple instances of the "DIA_CDR_PlaybackPipeline" pipeline:

DIA_CDR_PlaybackPipeline
{
  NumberOfInstances = 20
  InstanceSpecificRegistries
  {
    Entry1 = TransactionManager.BinaryLogFileName
    Entry2 = PipelineLog.Module.ITO.FileName
    Entry3 = Output.OutputLog.FilePrefix
  }
  ...
}


How should we set multiple instances on that pipeline to make it work?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms