Restore IIB AdminEvents capabilites to ACE

After discussion through the Early Experience Program earlier this year, this feature was delivered as part of ACEv12.0.8.0:

https://www.ibm.com/docs/en/app-connect/12.0?topic=wniv1-new-function-added-in-version-120-modification-packs-fix-packs#v12080__adminlogs

Status is updated to Delivered.

RFE Review. Thank you for taking the time to submit this idea for enhancement which overall we agree would benefit the product. In IBM Integration Bus v10, there were three separate categories of events which could be generated by the product:

1. OperationalEvents (this category included Message flow statistics, resource statistics and workload management information)

2. AdminEvents (this category included configuration changes such as Create/Change/Delete of an Integration Server, and Create/Change/Delete of a message flow, and operational state changes such as Start/Stop of an Integration node and Start/stop of a message flow)

3. BusinessEvents (this category describes the publication of Business monitoring events which were distributed in order to help track business level situations through integration with the WebSphere Business Monitor product and more latterly the built-in Business Transaction Monitoring feature of IIB/ACE).

This RFE specifically relates to the AdminEvents category (OperationalEvents and BusinessEvents are already available in ACE). The style of IIBv10 events generated in the AdminEvents category used to look like these examples:

<Broker uuid="integrationNodeUuid" label="integrationNodeName" version="1">

<ExecutionGroup uuid="integrationServerUuid">

<Start>

<MessageFlow uuid="messageFlowUuid"/>

</Start>

</ExecutionGroup>

</Broker>

<Broker uuid="integrationNodeUuid" label="integrationNodeName" version="1">

<StatusChange state="Stopped"/>

</Broker>

These XML structures reflect the architecture of the product at that time:-

(i) They contained UUIDs for the deployed artifacts which as a concept has been removed from ACE for very good reasons (better enabling cloning of deployed content) as part of the work to speed up and restructure the product's deploy chain.

(ii) The event formats were defined prior to the introduction of the product concepts of Applications and Libraries (WMBv8) which is information not included in the XML

(iii) The naming of the product components has been superceeded (eg A "Broker" is now an integration node, and an "ExecutionGroup" is now an integration server.

We highlight this, because whilst we agree that implementing an admin event capability in ACE would improve the product, we would be unlikely to position this as a direct replacement for the feature of IIBv10 discussed above because there are several elements of the structure of those messages which would now be out-dated.

Also worthy of note is that in-line with the increased focus on container based architectures, we have invested in both a Web-UI based administration log which details all administrative and status changes made to the product, and an associated ability to record admin events to file as part of an audit log. These existing features may be suitable for the majority of our users needs in this area, particularly if seriously considering a future move to containers. Also in a similar functional area is our capability to send log events to an external ELK stack. More on this capability here: https://www.ibm.com/docs/en/app-connect/12.0?topic=pmwm-configuring-integration-servers-send-logs-events-logstash-in-elk-stack

So - in summary we are moving this enhancement request to a status of Future Consideration and would happily receive feedback from users on the above commentary to help shape any future delivery in this functional area.