3.3 How Directors Work Monitoring Multiple Systems
Figure 3–1 shows an example of two systems running SEA processes, a UNIX system and a Windows system, each running a single Director, and communicating with each other over a network.
Figure 3–1 Interaction Between Two Systems Running SEA
- Web interface #1 is a web browser running on the UNIX system, directly connected to the local Director on the same system (http://localhost:7902). It also can communicate with the WCCProxy on the Windows system through the UNIX Director. This enables you to view the output produced by either system, such as analysis results, using the same web interface.
- Web interface #2 also is running in a browser on the UNIX system, but it has directly connected to the Director on the Windows system (http://win.sys.name.here:7902). Using this web interface you can, if desired, connect back to the UNIX WCCProxy as well, but the UNIX Director need not be running at all.
- A telnet session initiated from the Windows system has logged on to the UNIX system, and the user has issued the wsea report command to view the results of automatic analysis. The CLI process connects to the UNIX system's Director, which returns the current report data to the CLI process. The report text is then displayed to the user. Note that it is not necessary to have the Director running on the Windows system for this type of remote connection.
- A user wants to perform manual analysis on the "thisBinary.errlog" file that was transferred from a UNIX system to the Windows system via FTP. The user issues the wsea analyze input thisBinary.errlog command from the Windows system. The Director is not needed for manual analysis, so there is no interaction with the local Director.
- Web interface #3 is a web browser running on the Windows system. This interface is directly connected to the local Director on the same system (http://localhost:7902) the same way that web interface #1 connects to its local UNIX Director.