APAR status
Closed as program error.
Error description
ibmint apply overrides command is not able to override properties when overrides are configured at WorkDir level. Also, Customer should not use Default App name in Overrides File as override configuration is first applied and then Integration Server is created along with the Default Application folder.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All Users of IBM App Connect Enterprise v12 who use "ibmint apply overrides" command to apply Top-Level work directory overrides Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The existing "ibmint apply overrides" command works for Applications and Libraries but does not handle Top-Level flow overrides correctly due to those overrides being renamed and moved in various ways during deployment. For example, Top-level flows have a "broker.xml" file that appears in the expected META-INF directory in the BAR file. But this "broker.xml" file is moved and renamed when using mqsibar command to unpack the BAR file. This results in "broker.xml" file becoming "*_bar.brokerxml" and therefore not being picked up by the ACE code scanning for "broker.xml" file. Also, If the Integration Server is started with a Default Application name (say "TopLevelFlows"), then the contents are moved into a directory of that name but the "*_bar.brokerxml" file is not renamed to "broker.xml" nor placed in META-INF folder. None of this prevents the Product from working but does makes it harder to apply overrides. In addition to the above, using an overrides file containing no Application or Library specifier such as Conflict#HTTP Input.URLSpecifier=/appliesToAllFlowsNamedConflict would make this to be recursively applied to all the files named "broker.xml" in the run directory, but this would not catch files with name "*_bar.brokerxml" nor "*.brokerxml" and so would not help with Top-Level flow overrides. Also, In cases where there is an Application with a flow of the same name and we're using an Application-specific override as well in addition to the above such as Conflict#HTTP Input.URLSpecifier=/appliesToAllFlowsNamedConflict /AppWithFlowNamedConflict/Conflict#HTTP Input.URLSpecifier=/someOtherValue then presently, there is no guarantee of ordering and so the first override may be applied second
Problem conclusion
The Product has been modified to handle Top-Level work directory overrides correctly --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v12.0 12.0.9.0 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT43088
Reported component name
APP CONNECT ENT
Reported component ID
5724J0560
Reported release
C00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-02-10
Closed date
2023-06-28
Last modified date
2023-06-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
APP CONNECT ENT
Fixed component ID
5724J0560
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C00","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 June 2023