Dll - Revision history

John: /* Exceptions= */

2016-12-09T18:40:13Z

Exceptions=

← Older revision		Revision as of 18:40, 9 December 2016
Line 57:		Line 57:
	If the BRconfig file is not present in the BR executable directory then BR looks for it in the current working directory at the time of BR invocation.		If the BRconfig file is not present in the BR executable directory then BR looks for it in the current working directory at the time of BR invocation.

	The SPOOLPATH :OS-fullpath configuration statement specifies where print spool files are temporarily stored during printing. SPOOLPATH defaults to a spool directory that runs off of the BR root of the first drive statement. If no such spool directory exists and SPOOLPATH is not specified then BR creates one. For example:		The [[SPOOLPATH]] :OS-fullpath configuration statement specifies where print spool files are temporarily stored during printing. SPOOLPATH defaults to a spool directory that runs off of the BR root of the first drive statement. If no such spool directory exists and SPOOLPATH is not specified then BR creates one. For example:

	DRIVE J:, C:\BR, x, \MYAPP		DRIVE J:, C:\BR, x, \MYAPP
Line 86:		Line 86:

	BRconfig.sys INCLUDE statements are relative to the location of the file containing the INCLUDE statement (the parent). CONFIG command INCLUDE statements are relative to the current directory at the time the command is issued.		BRconfig.sys INCLUDE statements are relative to the location of the file containing the INCLUDE statement (the parent). CONFIG command INCLUDE statements are relative to the current directory at the time the command is issued.


	===Licensing Restrictions===		===Licensing Restrictions===

Laura at 18:13, 19 September 2014

2014-09-19T18:13:54Z

@@ Line 1: / Line 1: @@
 BR functions with a Dll structure.
 As of Release 4.3 Business Rules! is structured with the following modules:
@@ Line 33: / Line 35: @@
 The client can be accessed from within a browser by initiating it with HTML which can specify an embedded window or a separate independent window. In all cases opening a window with PARENT=NONE creates a separate window.
 <noinclude>

Laura at 18:04, 19 September 2014

2014-09-19T18:04:23Z

← Older revision		Revision as of 18:04, 19 September 2014
Line 36:		Line 36:
	<noinclude>		<noinclude>
	[[Category:Basics]]		[[Category:Basics]]
			[[Category:Files]]
	</noinclude>		</noinclude>

Laura at 17:59, 19 September 2014

2014-09-19T17:59:28Z

← Older revision		Revision as of 17:59, 19 September 2014
Line 35:		Line 35:

	<noinclude>		<noinclude>
	[[Category:~~Disambiguation~~]]		[[Category:Basics]]
	</noinclude>		</noinclude>

Laura: Created page with "BR functions with a Dll structure. As of Release 4.3 Business Rules! is structured with the following modules: *brserver.exe - The BR Server module accessed by Client-Serve..."

2014-09-19T17:59:06Z

Created page with "BR functions with a Dll structure. As of Release 4.3 Business Rules! is structured with the following modules: *brserver.exe - The BR Server module accessed by Client-Serve..."

New page

BR functions with a Dll structure.

As of Release 4.3 Business Rules! is structured with the following modules:

*brserver.exe - The BR Server module accessed by Client-Server configurations. Brserver.exe also operates as what is now viewed as the Standard Model. If it is invoked by brlistener, then it acts as brserver. If it is simply executed, it acts as brcombined. However, when operating as the standard model, it needs to have brclient.dll in the same directory as brserver.
*brclient.exe - The program that the user accesses in Client-Server configurations.
*brclient.dll - The client processing program that correlates with the brserver edition.
*npbrclient.dll - The standard (non-IE) browser plugin dll
*iebrclient.dll - Internet Explorer plugin dll

Client installation is done by placing brclient.exe and brclient.dll on the client system and referencing brclient.exe in an icon. Server installation is done by placing brserver.exe and brclient.dll on the server and referencing brserver.exe in the brlistener.conf file. Exe files may be renamed as desired. The name of the released brclient.dll modules will be lengthy and must not be changed because BR relies on the DLL names for version identification.

You will need one of the following possible configurations:
*Workstation Standard Model
**Server executable
**Workstation Client dll
*Linux Terminal Support
**Server executable
**Linux Client dll ( .so )
*Client Server Model
**On Client Machine-
***Client executable
***Workstation Client dll
**On Server
***Server executable
***Workstation Client dll
***BR Listener installed
***[ Linux Client dll for Linux terminal access ]

Servers, clients, debug models and release models can be intermixed. However dlls must be the in same bit class (32 or 64) as the modules that call them. Put your BR bmp files ( drawsunk.bmp, startup.bmp etc. ) in the BR server executable directory. When client DLLs are transferred from the server to the client they are stored in \users\-name-\AppData\Local\ADS\ and the full pathname to the most recent is stored in the registry at HKEY_CURRENT_USER\ Software\ADS\BusinessRules!\CurrentClient.

Updates will pertain to Processor DLLs while the user interfaces will remain as installed. Client DLLs will be automatically uploaded when corresponding server DLLs are accessed in the event they are not already present on the client.

The client can be accessed from within a browser by initiating it with HTML which can specify an embedded window or a separate independent window. In all cases opening a window with PARENT=NONE creates a separate window.

<noinclude>
[[Category:Disambiguation]]
</noinclude>