BMC TrueSight Infrastructure Management systems propagate events and component status changes from BMC TrueSight Infrastructure Management Server to the BMC TrueSight Operations Management Report Engine. The BMC TrueSight Operations Management Report Engine then aggregates and summarizes the events and component status changes, and stores the processed data in the Reporting Database.
Deployment scenarios
BMC TrueSight Operations Management Reporting can be deployed for following scenarios:
Scenario 1: Collecting only Event and Impact data from BMC TrueSight Infrastructure Management Server
For event and impact reporting, BMC TrueSight Infrastructure Management Server propagates events and component status changes from one or multiple BMC TrueSight Infrastructure Management Server Cells into single BMC TrueSight Operations Management Report Engine.
Scenario 2: Collecting Event, Impact, and Performance data from BMC TrueSight Infrastructure Management Server
To collect event, impact, and performance data, you must use separate BMC TrueSight Operations Management Report Engine for each instance of BMC TrueSight Infrastructure Management Server.
Note
If you want to collect only performance data, do not register BMC TrueSight Infrastructure Management Cell.
Scenario 3: Collecting data from BMC TrueSight Infrastructure Management Server and Remote Cell
Register the remote cell to receive event and impact data. However, to collect data from the remote cell, you must have at least one instance of BMC TrueSight Infrastructure Management Server configured with the Report Engine.
Related topics
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
3 Comments
Frank Oberlaender
Manisha Moon
Frank Oberlaender
Hi Manisha, thanks for the other link, and yes, there is explanation about that additional communication.
I gather it's is a question about the intention of this chapter then.
I was seeking the information which ports and connections I need to declare with the FW administrator of the customer. Some other docs (like TSIM) have a chapter called "Network Ports" or similar. As I didn't see it here, I thought this is the right chapter, just named differently.
So I expected to find here all ports needed by reporting.
Maybe worth then to consider to add such a chapter for TS reporting as well.
And there is another point regarding port usage that is a bit misleading in the existing chapters:
If - like for me - my deployment scenario is to report on events only, I would assume I wouldn't need to open a FW for the connection from reporting engine to the TS DB (which is only for performance data, which I don't need).
However the installer of TS reporting engine asks for this port regardless of the deployment scenario/usecase, and won't proceed if this is not free.
So essentially this communication is a prereq for all above scenario's.
regards
Frank