rwdiag includes keywords that enable you to do the following:
Locate a Reports Server or bridge running on the network.
List all running Reports Servers or bridges on the network.
Monitor packets on the network broadcast by Reports Servers or clients.
rwdiag.bat | rwdiag.sh {-find serverName | -findAll |-monitor [-log log_file_name]} [-conf config_file_name] [-timeout seconds]
Where
rwdiag.bat is the script for Microsoft Windows.
rwdiag.sh is the script for UNIX.
-find serverName finds the Reports Server with given name running on the current network.
-findAll finds and lists all Reports Servers and bridges on the network.
-monitor lists the packets broadcast on the network. To stop monitoring, press q and Enter. This option is not supported when the discovery mechanism specified in the network configuration file is a naming service.
-log log_file_name specifies a log file to which the monitor output is written. If not specified, the monitor output is displayed on the screen. The file name can be an absolute path. If just a file name is specified, the log file is created in the current folder.
-conf config_file_name specifies a custom configuration file. If not specified, rwnetwork.conf is the default file name. The settings such as discovery mechanism (broadcast or naming service) and port numbers are taken from this file. The utility assumes the configuration file is located in ${DOMAIN_HOME}/config/fmwconfig/components/ReportsToolsComponent/<reports_tools_name>/. If a non-existent file is specified, the file is created with the default settings in rwnetwork.template.
-timeout seconds specifies the timeout value in seconds. If not specified, the default value is 10 seconds. Timeout is the length of time the client waits for a response from the server after broadcasting the request packet. This option is ignored when the discovery mechanism specified in the network configuration file is naming service.
The host information is not available when using a naming service discovery mechanism.
Time taken to locate the server is not displayed for a naming service discovery mechanism because the lookup is based upon the Reports Server name in the naming service. The utility does not need to await response from the server. Hence, the time taken is not relevant for a naming service.
Bridges cannot be located using a naming service because they do not bind to the naming service. Only Reports Server implementations are bound to the naming service.
The timeout value in the configuration file is ignored. Only the value specified in the command line is taken into account. If not specified in the command line, the default value is 10 seconds.
If the Reports Server you try to locate is not found, the utility generates a REP-50504 message, which states that the server was not found.