Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
An iRules module included in the registry, defines three iRules. The iRules seems to be working fine. The problem is that the INIT_SCRIPT section (there is an INIT_SCRIPT for each iRule) is also executed as a part of the last iRule.
One would expect to get an INIT_SCRIPT line only once in the pipeling log file for each EDR that travels through the pipeline. But below is the result:
17.01.2003 10:56:34 mark ifw IFW NORMAL 00000 - (ifw.Pipelines.DEV.Functions.PreProcessing.FunctionPool.ROAMGPRS_PREPROCESS.Module.GPRS_TapIn_OutRoaming.GPRS_TapIn_OutRoaming) *** Running INIT_SCRIPT for GPRS_OutRoaming (19)
17.01.2003 10:56:34 mark ifw IFW NORMAL 00000 - (ifw.Pipelines.DEV.Functions.PreProcessing.FunctionPool.ROAMGPRS_PREPROCESS.Module.GPRS_TapIn_OutRoaming.GPRS_TapIn_OutRoaming) *** Running INIT_SCRIPT for GPRS_TapIn_OutRoaming (98)
So, for the iRule GPRS_TapIn_OutRoaming there are printouts from two INIT_SCRIPT sections. This is incorrect.
The iRules module is currently defined in this registry extract as follows:
ModuleName = FCT_IRules
Active = True
Source = DATABASE
DataConnection = ifw.DataPool.IntegrateLogin
GPRS_InRoaming = ./customer/iScript/IRL_GPRS_InRoaming.irl
GPRS_OutRoaming = ./customer/iScript/IRL_GPRS_OutRoaming.irl
GPRS_TapIn_OutRoaming = ./customer/iScript/IRL_GPRS_TapIn_OutRoaming.irl
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms