BRlistener.exe: Difference between revisions

From BR Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 1: Line 1:
The '''BRListener.exe''' file is a C++ application which serves as the [[connection agent]] for the server side of [[Business Rules!]] [[Client Server]] installations.


GENERAL: You must be logged in as [[Administrator]] in order to run Setup (BRListener.exe). (Or [[superuser]] for Linux)
The '''BRListener.exe''' file is a C++ application which serves as the connection agent for [[Business Rules!]] [[Client Server]] installations.


In order to run BRListener.exe, [[BRListener.conf]] must be properly configured.
GENERAL: You must be logged in as Administrator in order to run BRListenerInstaller.exe, or superuser/sudo on Linux.  


Copy BRListener.exe to the proper [[System32]] folder.
=== Installation Procedure On Windows ===


If you have a BR Service running:
# 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.
# The normal way to install BRlistener.exe no longer uses Installshield.
# Prepare your brlistener.conf file and place it in the Windows directory.
# Place either the 64 bit BRlistener.exe in the System32 directory or the 32 bit BRlistener.exe in the SysWOW64 directory.
# As administrator.. execute the corresponding 64 or 32 bit BRlistenerInstaller program with no parameters.
# if your brlistener.conf file specified a log file you should have listener startup messages in it that will confirm its status.
That's it. You're good to go.
 
=== Uninstall Procedure ===
 
# Run BRlistenerInstaller.exe /RELEASE
# Manually remove the brlistener.conf and BRlistener.exe files installed above.


# 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.
=== Multiple Listeners ===
# 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.


The listeners recognize a qualifying prefix on [[brlistener.conf|CONF]] file statements. This supports having different listeners active at the same time. This permits testing in production client-server environments.
On rare occasions it is necessary to operate with 2 different versions of BRlistener.exe. In this case the following brlistener.conf statements will enable this capability. The listeners recognize a qualifying prefix on [[brlistener.conf|CONF]] file statements. This supports having different listeners active at the same time which permits testing in production client-server environments. The following brlistener.conf statements refer to BRlistener version numbers.


  @release = 1.2        PORT=8555
  @release = 1.2        PORT=8555
  @release = 2.0        PORT=8557
  @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:
The full syntax for the Windows brlistenerinstaller is:


brlistenerinstaller [/RELEASE] [/ALTERNATE alternate] [brlistener-path]
brlistenerinstaller [/RELEASE] [/ALTERNATE alternate] [brlistener-path]
[/RELEASE] removes the service in Windows. It does not remove any programs.
[/RELEASE] removes this service.
 
[/ALTERNATE alternate] uses an alternate service name. This will result in a service named BR_Listener-(alternate).
[/ALTERNATE alternate] uses an alternate service name. This will result in a service named BR_Listener-(alternate).
[brlistener-path] The default path is described above in step 4 above. This can be overridden with the brlistener-path parameter, and should be used to distinguish between the two BRlistener.exe files.


The second brlistener must be installed using the ALTERNATE keyword followed by a number. Under Linux this is handled by naming the listeners differently.  
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
=== 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.
Multisession refers to the ease of accessing multiple ''sequential'' client server sessions. When MULTISESSION is specified in a brlistener.conf label definition, 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.   
[BRclient] communicates with [BRlistener] over TCP encrypted by TLS.   

Latest revision as of 04:12, 20 March 2023

The BRListener.exe file is a C++ application which serves as the connection agent for Business Rules! Client Server installations.

GENERAL: You must be logged in as Administrator in order to run BRListenerInstaller.exe, or superuser/sudo on Linux.

Installation Procedure On Windows

  1. 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.
  2. The normal way to install BRlistener.exe no longer uses Installshield.
  3. Prepare your brlistener.conf file and place it in the Windows directory.
  4. Place either the 64 bit BRlistener.exe in the System32 directory or the 32 bit BRlistener.exe in the SysWOW64 directory.
  5. As administrator.. execute the corresponding 64 or 32 bit BRlistenerInstaller program with no parameters.
  6. if your brlistener.conf file specified a log file you should have listener startup messages in it that will confirm its status.

That's it. You're good to go.

Uninstall Procedure

  1. Run BRlistenerInstaller.exe /RELEASE
  2. Manually remove the brlistener.conf and BRlistener.exe files installed above.

Multiple Listeners

On rare occasions it is necessary to operate with 2 different versions of BRlistener.exe. In this case the following brlistener.conf statements will enable this capability. The listeners recognize a qualifying prefix on CONF file statements. This supports having different listeners active at the same time which permits testing in production client-server environments. The following brlistener.conf statements refer to BRlistener version numbers. 

@release = 1.2        PORT=8555
@release = 2.0        PORT=8557

The full syntax for the Windows brlistenerinstaller is: 

brlistenerinstaller [/RELEASE] [/ALTERNATE alternate] [brlistener-path]

[/RELEASE] removes the service in Windows. It does not remove any programs.

[/ALTERNATE alternate] uses an alternate service name. This will result in a service named BR_Listener-(alternate).

[brlistener-path] The default path is described above in step 4 above. This can be overridden with the brlistener-path parameter, and should be used to distinguish between the two BRlistener.exe files.

The second brlistener must be installed using the ALTERNATE keyword followed by a number. Under Linux this is handled by naming the listeners differently.

Multisession Mode

Multisession refers to the ease of accessing multiple sequential client server sessions. When MULTISESSION is specified in a brlistener.conf label definition, 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.

Retrieved from "http://brwiki2.brulescorp.com/brwiki2/index.php?title=BRlistener.exe&oldid=11411"