In order to run BRListener.exe, BRListener.conf must be properly configured.
Copy BRListener.exe to the proper System32 folder.
If you have a BR Service running:
- Stop the BR Service on the machine where you intend to install. If your previous installation was done using InstallShield, use "stop BR service" from the Programs/BR Service icon list.
- You can also stop the BR Service by going to start, run, and typing "install /release".
- If your previous installation was done using InstallShield, you can remove it by using the Add/Remove Programs feature in the Control Panel. In this case, your BRConfig.sys and license file will not be removed. This is to make them available for subsequent use.
- When you run install, installation will modify your BRListener.conf file if your target directory is different from the one previously specified.
- BRListener (4.13) was changed to allow multiple label statements. It works in conjunction with a new build of the Client (4.12c).
The listeners recognize a qualifying prefix on CONF file statements. This supports having different listeners active at the same time. This permits testing in production client-server environments.
@release = 1.2 PORT=8555 @release = 2.0 PORT=8557 @release < 2.0 EXECUTABLE = /ads/sys/br.d/brserver @release >= 2.0 EXECUTABLE = /ads/sys/br.d/brserver.new
The full syntax for the Windows brlistenerinstaller is:
brlistenerinstaller [/RELEASE] [/ALTERNATE alternate] [brlistener-path]
[/RELEASE] removes this service. [/ALTERNATE alternate] uses an alternate service name. This will result in a service named BR_Listener-(alternate).
The second brlistener must be installed using the ALTERNATE keyword followed by a number. Under Linux this is handled by naming the listeners differently.
Persistent Login – Brlistener Release 2.0 in MULTISESSION Mode
A Client session ID is stored in the registry on the client side and associated with the user login name. This is maintained in memory by the BRlistener along with the user's login-name and password. The listener first checks the user's client session ID before prompting for login info.
[BRclient] communicates with [BRlistener] over TCP encrypted by TLS.