A fix is available
APAR status
Closed as fixed if next.
Error description
When configuring processing rules through the Web GUI, it's possible the configuration can get into a state where 2 processing rules reference the same action. This issue seems to occur when a user renames a processing rule after dragging actions into the processing rule. For example the processing policy could have 1 request rule, A, which contains a transform action referencing a stylesheet 1.xsl and then another request rule, B, could be created. When B is created it's possible that a transform action could be created in rule B which references the same transform action. If the user sets the transform action to reference another stylesheet 2.xsl, this will create a conflict when applied that will make rule A also transform using 2.xsl.
Local fix
Name the processing rule and then click out of the name field and then proceed with creating the action.
Problem summary
Naming collisions may occurr in certain cases on policy actions. Fix will be available in next major releases. For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
IT02485
Reported component name
DTPWR INTGRAPL
Reported component ID
DP905XI52
Reported release
500
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-06-11
Closed date
2014-07-01
Last modified date
2014-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R700 PSN
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSHT9H","label":"WebSphere DataPower Integration Appliance XI52"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.0.0"}]
Document Information
Modified date:
25 September 2021