APAR status
Closed as program error.
Error description
If a Business Transaction Definition (BTD) is created in the WebUI and the Event source address of the monitoring event has characters that need to be escaped, for example brackets, then BIP2761E and BIP2763E errors are reported on start-up of the integration server. These messages report the Business Transaction Definition (BTD) monitoring events do not exist because a defect exists where the wrong URI is returned from the BTDs.
Local fix
Once this APAR is applied, any Business Transaction Definitions created that experience this issue will need to be deleted and recreated to resolve the problem.
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus v10.0 creating Business Transaction Definitions in the web user interface. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: Using the web user interface (WebUI) it is possible to create a Business Transaction Definition (BTD). As part of constructing this definition message flows from the integration server, applications, services or REST APIs can be selected. The monitoring events from such flows can then be used as the Start, End, Rollback or Progress points for the Business Transaction. Once saved, the BTD becomes active on one of the integration servers and the recording of the monitoring events begins. To do this, the integration server looks up the monitoring event definitions using the URI. A defect existed such that the wrong URI was returned for the monitoring events if the Event source address of the monitoring event contains characters that need to be escaped, for example brackets. This resulted in BTD monitoring event URIs being unable to be found and on start-up of the integration server BIP2761E/BIP2763E errors report that the monitoring events do not exist. There are a number of resource name changes between WebSphere Message Broker and IBM Integration Bus Version 9.0. For details visit http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e tools.mft.doc/bb23814_.htm
Problem conclusion
The product has been corrected to return the correct monitoring event URIs. Once this APAR is applied, any Business Transaction Definitions created that experience this issue will need to be deleted and recreated to resolve the problem. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.9 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
IT19436
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-27
Closed date
2017-05-25
Last modified date
2017-05-25
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
INTEGRATION BUS
Fixed component ID
5724J0540
Applicable component levels
RA00 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020