IT33583: UUIDS IN MONITORING EVENT APPEAR AS NULLS.

APAR status

• Closed as program error.

Error description

• UUIDs are not populated in the monitoring event in App Connect
  V11.
  Provide new eventFormat of WMB_UUID which contains zeros
  for the UUID.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of App Connect Enterprise version 11 or 12 using
  Record and Replay with version 10 compatible DataCapture stores.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When using WMB format monitoring events the UUID values are not
  included in monitoring events. Additionally since the UUIDs for
  Integration Server and Integration Node are not used in App
  Connect Enterprise version 11 or 12 it is not possible to
  distinguish events from different Integration Servers or
  Integration Node's in DataCapture stores.
  

Problem conclusion

• <span style="background-color:rgb(255, 255, 255)">App
  Co</span><span style="background-color:rgb(255, 255, 255)">nnect
  enterprise versions</span><span style="background-color:rgb(255,
  255, 255)"> 11 and 12 no longer use UUID's to identify
  Integration Nodes or Integration Servers therefore a new version
  of the schema for the DataCapture store tables has been
  introduced that removes these obsolete fields and instead
  introduces Integration Node hostname</span><span
  style="background-color:rgb(255, 255, 255)"> and Integration
  Server hostname</span><span style="background-color:rgb(255,
  255, 255)"> fields. </span>
  
  The V2 version (DataCaptureSchema_v2.sql) files should be used
  in preference to the original versions (DataCaptureSchema.sql)
  when creating the DataCapture store. The original version should
  be used only for compatibility purposes.
  
  Additionally this fix adds an environment variable:
  MQSI_EVENTMON_USE_OPTIONAL_WMB_ATTRS
  
  When this env var is set to any non-null value AND when the
  output format for events is set to WMB it will result in the
  messageFlowData elements being populated with UUID attributes.
  Note that these UUIDs are fixed at all zeroes since these
  objects no longer actually have UUIDS internally in ACE.
  
  For example:
  
  Before:
  
  <wmb:messageFlowData>
              <wmb:broker wmb:name="EVENT_TEST" />
              <wmb:executionGroup wmb:name="default" />
              <wmb:messageFlow
  wmb:uniqueFlowName="EVENT_TEST.default.httpEcho.httpEcho"
  wmb:name="httpEcho" wmb:threadId="1823762" />
              <wmb:node wmb:nodeLabel="HTTP Input"
  wmb:nodeType="ComIbmWSInputNode" />
  </wmb:messageFlowData>
  After:
  
  <wmb:messageFlowData>
              <wmb:broker wmb:name="EVENT_TEST"
  wmb:UUID="00000000-0000-0000-0000-000000000000" />
              <wmb:executionGroup wmb:name="default"
  wmb:UUID="00000000-0000-0000-0000-000000000000" />
              <wmb:messageFlow
  wmb:uniqueFlowName="EVENT_TEST.default.httpEcho.httpEcho"
  wmb:name="httpEcho"
  wmb:UUID="00000000-0000-0000-0000-000000000000"
  wmb:threadId="1824822" />
              <wmb:node wmb:nodeLabel="HTTP Input"
  wmb:nodeType="ComIbmWSInputNode" />
  </wmb:messageFlowData>
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.17
  
  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 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

  5724J0550

Applicable component levels