Page 1 of 2

Client Server 4.2

Posted: Thu Sep 03, 2009 8:11 pm
by TheMrkeys
I've never tried the CS model and wanted to give it a shot. I could not find the install.exe referenced in the wiki. I'm also a little bothered by the instructions to place files in the windows and system32 directories. Does anyone have cliff notes on getting the cs model up and running?

Posted: Thu Sep 03, 2009 8:20 pm
by Susan Smith
Ryan,

I don't have any information about C/S for you, but I just wanted to say welcome to the forum! Steve Koger and his group seem to have a lot of experience with C/S, so perhaps one of them will jump in when they see this.

-- Susan

Posted: Fri Sep 04, 2009 5:59 am
by gordon
INSTALL.EXE can be found at the bottom of 418g_winsvr.zip on the web site download section ( http://www.ads.net/brules/download.html )

Posted: Fri Sep 04, 2009 7:31 am
by bluesfannoz
I had spent some time trying to find it myself. Seems odd you don't have it available on the FTP. Ryan, since the Brlistener runs as a Service. I am not sure there would be anyplace else it could be placed and function properly. An Administrative user should be the only one installing it anyway.

Steve
gordon wrote:INSTALL.EXE can be found at the bottom of 418g_winsvr.zip on the web site download section ( http://www.ads.net/brules/download.html )

Re: Client Server 4.2

Posted: Fri Sep 04, 2009 5:13 pm
by Gabriel
If you are unable to get it working from all the helpful people in the forum, feel free to call me with any remaining questions you have. I use CS extensively now, and I even use it over the internet (though thats not officially recommended). And if it weren't for the wonderful folks at MACS willing to give me a call and help answer some questions, it would have been much harder for me to figure at as well. So I'm perfectly happy to "pay it forward" and answer any questions you might have about getting CS working.

Gabriel Bakker
Sage AX
469 223 5476
TheMrkeys wrote:I've never tried the CS model and wanted to give it a shot. I could not find the install.exe referenced in the wiki. I'm also a little bothered by the instructions to place files in the windows and system32 directories. Does anyone have cliff notes on getting the cs model up and running?

Posted: Tue Feb 09, 2010 6:37 am
by GomezL
I decided to give CS a try.

I found brlistener.exe and install.exe (Is there a 4.2 version?)

I copied them to C:\WINDOWS\SYSTEM32

I created a BRlistener.conf

If I run Brlistner.exe directly, I get a log file:

02/09/2010 07:35:34
Log level set to 10.
02/09/2010 07:35:34
The port has been set to 8555. Note that port changes only take effect on listener restart.
02/09/2010 07:35:34
The configuration file C:\Documents and Settings\clsadmin\WINDOWS\brlistener.conf has been read.


BRlisterner.conf ius configured as follows:

LOGFILE=D:\BRListner.log
loglevel=10
port=8555
[LABEL=SUPPORT STARTDIR=E:\VOL2\SUPPORT\WBWIN EXECUTABLE=E:\VOL2\SUPPORT\WBWIN\brserver420-2009-06-20.exe]

My problem is when I run install, I get the following message:
Couldn't find BRLISTENER.exe in the specified (Or System) Directory

Posted: Tue Feb 09, 2010 7:32 am
by Gabriel
What OS are you running on?

Under Windows Vista 64 bit I have to put BRListener.Exe under the folder: c:\windows\syswow64

And BRListener.Conf under c:\windows.

Under Windows XP Pro I have to put BRListener.Exe under the folder c:\windows\System32

And BRListener.Conf under c:\windows again.

These are the only OS's I've tried it under, but hopefully something in here will help with whichever OS you're trying to run it under... If its a 64 bit OS, try to find some sort of a "system 64" folder (or in my case under Vista "sysWow64").

Gabriel

Posted: Tue Feb 09, 2010 8:10 am
by GomezL
Windows Server 2008.

C:\Windows\SysWow64

That was the trick!

** Note: sysWOW64 is a strange name for this folder.
sysWOW64 = 32 bit applications for 64 bit OS. I suppose it would be nice to have a 64 bit BRlistener.exe for SYSTEM32, but no big deal.


After some fiddeling:

This is the "Correct Configuration"

LOGFILE=D:\BRListner.log
loglevel=10
port=8555
[ LABEL=SUPPORT STARTDIR=E:\VOL2\SUPPORT\WBWIN EXECUTABLE=E:\VOL2\SUPPORT\WBWIN\ ]

BRServer.exe must be called that, not Brserver420-2009-06-20.exe

I also found that the startup command IS case sensitive!

LABEL=SUPPORT means SUPPORT, not Support

Posted: Tue Feb 09, 2010 8:41 am
by bluesfannoz
Good info Luis and Gabe! I had not yet needed to install it on a 64 Bit server. But now I will know where to put it!

As for the 64 Bit version of brlistener request. For those listening.. don't forget the intel version of Brlistener for the MAC is not done yet either.. and I made that request 2 years ago...

GomezL wrote:Windows Server 2008.

C:\Windows\SysWow64

That was the trick!

** Note: sysWOW64 is a strange name for this folder.
sysWOW64 = 32 bit applications for 64 bit OS. I suppose it would be nice to have a 64 bit BRlistener.exe for SYSTEM32, but no big deal.


After some fiddeling:

This is the "Correct Configuration"

LOGFILE=D:\BRListner.log
loglevel=10
port=8555
[ LABEL=SUPPORT STARTDIR=E:\VOL2\SUPPORT\WBWIN EXECUTABLE=E:\VOL2\SUPPORT\WBWIN\ ]

BRServer.exe must be called that, not Brserver420-2009-06-20.exe

I also found that the startup command IS case sensitive!

LABEL=SUPPORT means SUPPORT, not Support

Posted: Tue Feb 09, 2010 11:59 am
by GomezL
I was getting an error 10054, turns out my Executable was configured wrong.

I changes by BRListner.conf as follows:

LOGFILE=D:\BRListner.log
loglevel=10
port=8555
[ LABEL=SUPPORT STARTDIR=E:\VOL2\SUPPORT\WBWIN EXECUTABLE=E:\VOL2\SUPPORT\WBWIN\brserver420-2009-06-20.exe ]

Posted: Tue Feb 09, 2010 12:13 pm
by gordon
With respect to "BRServer.exe must be called that, not Brserver420-2009-06-20.exe", you CAN specify the executable in addition to the path. Here is the brlistener.conf from my server showing a variety of applications available FOR 2 LEVELS of BR. Also note that you can put your parameters on separate lines for readability.

logfile=/ads/sys/br.d/errorlog
loglevel=10
[
LABEL=ORD
MULTISESSION
STARTDIR=/ads/sys/br.d
EXECUTABLE=/ads/sys/br.d/brserver
CONFIG=brconfig.ord
]
[
LABEL=INT
MULTISESSION
STARTDIR=/ads/sys/br.d
EXECUTABLE=/ads/sys/br.d/brserver
CONFIG=brconfig.int
]
[
LABEL=INT1
STARTDIR=/ads/sys/br.d
EXECUTABLE=/ads/sys/br.d/brserver
CONFIG=brconfig.int1
]
[
LABEL=dan
STARTDIR=/home/dan/test
EXECUTABLE=/home/dan/test/brserver
STDERR=/home/dan/test/stderr
]
[
LABEL=MACTEST
STARTDIR= /home/dan/br/unixbuild
EXECUTABLE= /home/dan/br/unixbuild/wb
STDERR= /home/dan/br/unixbuild/stderr
]
[ LABEL=BR
STARTDIR= /ads/sys/br.d
EXECUTABLE = /ads/sys/br.d/brserver
CONFIG = brconfig.svr
STDERR=/ads/sys/br.d/stderrorlog
]
[ LABEL=BR418I
STARTDIR= /ads/sys/br.d
EXECUTABLE = /ads/sys/br.d/brserver418i
CONFIG = brconfig.svr
]
[ LABEL=BR418I_INT
STARTDIR= /ads/sys/br.d
EXECUTABLE = /ads/sys/br.d/brserver418i
CONFIG = brconfig.int
]
[
LABEL=BR418I_ORD
MULTISESSION
STARTDIR=/ads/sys/br.d
EXECUTABLE=/ads/sys/br.d/brserver418i
CONFIG=brconfig.ord
]

Posted: Wed Feb 10, 2010 7:42 am
by GomezL
I am making good progress.

I decided to Map a network drive as my "TEMP" folder.

LET SETENV("TEMP","J:\TEMP")

This took care of most of my Server/Client issues.

I still need to deal with "My Documents", I suppose that should stay on my "C Drive".

I do have a problem, I start my application in S:\SUPPORT\WBWIN
S: is mapped to the server

IN BR, I am using the "F Drive". "F:\CLSINC"

When I type SYS DIR, I get a DIR of the S:\SUPPORT\WBWIN folder, not the F:\CLSINC it's S:\CLSINC for the client and E:\VOL2\CLSINC for the server.

Posted: Wed Feb 10, 2010 9:35 am
by dmeenen
When I type SYS DIR, I get a DIR of the S:\SUPPORT\WBWIN folder, not the F:\CLSINC it's S:\CLSINC for the client and E:\VOL2\CLSINC for the server.

Luis,
We resolved this issue by setting up a global.fil and putting in the physical drive mapping to the server
c:\macs\vol002 in the file.
whenever we need to do a system call
read the global.fil and use the c:\macs\vol002 in a variable to do the system call with the variable.

Hope this helps.

Posted: Wed Feb 10, 2010 9:50 am
by GomezL
I figured that I will end up having to write special code, although so far I have been able to pretty much "Cheat".

I moved BRCLIENT.exe to S:\CLSINC and now it defaults to the "Correct Location".

Posted: Wed Feb 10, 2010 1:10 pm
by GomezL
I was reading about:

CLIENT_CURRENT_DIR S:\CLSINC / @S


This sounds like what I wanted, although I haven't quite figured out that part yet.


I Setup SpoolCmd to use my client for printing. This way I can print to HTML, Extel, etc.

SpoolCmd @ S:\CLSINC\Batch\WinSpool.cmd [SPOOLFILE] [QUEUE] [PRINTER] \\CLS-APP OUTPUT [WSID] [PROGRAM]