Installation of Report Runner Event Server is simple and straightforward. Following is a list of steps, one-by-one, that will take you from beginning to end:
1) Download the software
2) Run the setup executable name Report_Runner_Event_Server_Setup.exe
Note: If running in an environment where your machine is "locked down", you will need to use the "Run As Administrator" function or if on a Terminal Server (RDP), use "Install Terminal Server Application" from the Control Panel.
3) This is the first window you will see (after initialization process)
4) Enter your Program Files directory (default should normally be used), and click Next
5) Enter your Jeff-Net data folder
(default should normally be used), and click Next
Note: This directory MUST ALREADY EXIST
. You will not be able to continue. It's required that you've already installed Report Runner Batch previously. Within the existing Report Runner Batch AppData directory, this installer will add an Event Server folder (along with the Input, Processed, and Error directories).
6) Enter your short-cut folder (default should normally be used), and click Next
7) Select your installation options. Event Server "watches" for certain events to happen. One of the possible events is when a Batch XML file "hits" the Input queue. The first option below sets the amount of time between checking the Input queue for existing batches. The default setting of 5 seconds is more than adequate. The second option tells Event Server how many Batch XML files to process at one time. There is a maximum of
batches at a time. It's important to understand you must make sure the computer/server you are installing Event Server on is capable of processing
batches at a time. Event Server does not monitor the "power" of the server; it will simply try to run
batches at once if you instruct it to. The third and fourth options are separate time settings (like option 1) for the 3 add-ons to Event Server (Mail Rules, File Rules, and SQL Rules). These 3 add-ons require separate licensing. They default to 0, because this means the rules are disabled (not run). If you have purchased licensing for these 3 add-ons, select how often you would like to run these rules.
8) You are ready to INSTALL; this is your final confirmation before files start being copied; click >>INSTALL>> to begin
9) Once the installation is complete (after the main files are copied), you will see a message about setting and configuring the Report Runner Event Server Service (Start, Control Panel, Administrative Tools, Services, Report Runner Event Server Service).
NOTE: If you are running reports from network drives or exporting batches to network drive, it's important that you change the "Run As" permissions on the Event Server service itself. Otherwise, the batches will NOT work. By default, a Windows service uses the System account to run, and the System account does NOT have access to network resources.
16) Installation is complete, and click Finish
17) Now, let's verify the service, know where it is, and it works. Go to your Control Panel, Administrative Tools, open up Services, and find Report Runner Event Server.
Right-click, bring up the Properties, and look at the Logon tab
By default, services run as the Local System Account. Sometimes this account has access to do everything it needs on your server, sometimes it doesn't. You may need to modify it to use "This account", and specify a specific Windows ID and password (like your own). This ensures the service can access DSNs, databases, the mail server, and file locations that your batches require to run successfully.
18) You may be thinking, "How can I know the service is running?" Let's look at the log files that the service generates. Go back to your Control Panel, Administrative Tools, and open Event Viewer.
The JNRRB_ES log is the log that the service writes to. And it writes to it every few seconds. The service will write to this log file upon starting and stopping, and everytime it is processing batch XML files and rule packs.
All of this writing can generate large log files. These log files need to be maintained. Make sure you have set the log files to overwrite as needed.
If you do not, and the log file fills up, it will crash the service.
Make sure the log file is configured to overwrite as needed!
19) Last, but not least, let's take a look at the Report Runner Event Server Controller. If you haven't rebooted after installing, it can be manually started in your Start, Programs, Startup folder. Once you start it, you'll see a [JN] icon in your system tray, in the lower right-hand corner of your monitor. If you right-click on the [JN] icon, you'll see options to control the service and to Display Monitor. Click on Display Monitor.
This option displays a really cool utility to monitor your various Event Server queues (Input, Error, and Processed). It also give you a neat way to monitor active batches and system resources.
Common Installation Errors/Issues:
- If service will not start, check your logon credentials as discussed in #17 above
- If service will not start or it starts and crashes quickly, check your log file settings as discussed in #18 above
- If you are licensed for rule packs and they are not running or if they are not editable within Report Runner Batch (Tools menu), you may have set the scan time for the rules to zero (0) when you were installing Event Server. Either rerun the Event Server installer or you can manually edit these scan times (IntervalMinutesMail and IntervalMinutesFileSQL) in JNRR.INI (found in your Jeff-Net\Report Runner Program Files directory). These rules will also not process unless your license is set to allow them.
- If your system seems overloaded running batches (CPU pegged at 100%), try reducing the maximum XML batches that can be processed. Either rerun the Event Server installer or you can manually edit the max setting (MaxBatchProcesses) in JNRR.INI (found in your Jeff-Net\Report Runner Program Files directory).
Interested in the Mail, File, and/or SQL Rule Add-Ons for Event Server?