Custom Reports

TADDM 7.3.0.1 (FP1) Special Note

TADDM 7.3 FP1 switched the underlying web server from Tomcat to WebSphere Liberty Profile. With this change there was a bug that affects installation of custom reports. APAR IV73344 was created to address this issue. It is recommended to apply this APAR. There is a work-around to this issue. After you upload the new report into TADDM, go to the storage server and copy the .rptdesign file from dist/external/wlp/usr/servers/TADDM to dist/apps/birt-viewer/WEB-INF/report. If you do this then the reports should execute.

Server Affinity with Logical Connections

Reports connections to and from components in a specific scope, including logical connections where one side of the connection may not be discovered yet. When scopes are created for business applications, this report can be used to identify external components that should be included in an application, but have yet to be identified by the application team. It can be used to keep the application team honest and also to alert them of connections that they might not be aware of.

The following ports related to known connections are excluded by default (you can change this via parameter):

• 22 – SSH (you will always see SSH connection from the TADDM server without this excluded)
• 53 – DNS

Tested with TADDM 7.2.2 FP2, 7.3.0.0, 7.3.0.1 (with IV73344)

These reports do not work with TADDM 7.3.0.1 that runs with Websphere Liberty Profile by default. See special note above about required APAR.

taddm_server_affinity_byScope_withLogConn.rptdesign

This report is similar but akes a single host as the parameter and includes business application membership. This report is only supported on TADDM 7.3. Same as above, if using 7.3.0.1 you must first install the IV73344 APAR.

taddm_server_affinity_byHost_withLogConn.rptdesign