Re: {bb} Howto: Multiple BB-clients on the same client???

On Fri, Mar 30, 2007 at 10:07:07AM -0600, [email protected] wrote:
> I'd like to do some BB-client custom code (ext) development work without
> interrupting my 'production' BB-Server. I was thinking that I could
> leave the currently running 'production' BB-Client pointing to my
> 'production' BB-Server, and set up a second (development) BB-Client to
> point (send information) to my BB-Development-Server.  Is this possible?
>  or is there a better way to create/test client products in product
> environments?

Unix: All you need to do is set "$BBDISP" to point at your dev box.

You can do that in the existing client, no reinstall of the client
necessary... just hardcode it into the ext script until you're ready to
go live with it. Of course, doing development work on a development box
is good practice, but as long as your test doesn't do anything
dangerous, you'll be OK. 

You can execute the script directly from the command line until it's doing 
what you want. Just set your environment variables, thus:

BBHOME=<path to directory holding runbb.sh>
export BBHOME
. $BBHOME/etc/bbdef.sh
BBDISP=<dev server hostname>
export BBDISP

The sequence matters, because you want everything to be the same except
BBDISP.

What happens is, when you run the script, the BB client runs once,
delivers the information where it's told, and unloads. Do remember that
your test will turn "purple" after 30 minutes, so you may want to clean
out your history information under bbvar every time you get finished
experimenting.

> 
> I ALSO have the need to do this scenario with  both unix and Win
> BB-Client development work. I'm guessing that the techniques on UNIX,
> WIN would be different?   How so?? Do I have to create a separate user
> for each BB-Client instance?  It seems logical that each instance will
> have to have it own PATH. Is there a socket issue?

I have no recent knowledge of the Windows client, though I expect to get
some fairly soon... it shouldn't be difficult, though. Anyone?

Of course, depending on what the test is, it'd be simple enough to
emulate the test on a separate machine. 

As regards sockets, the only place that's a concern is on the server
side. If your test server instance is on a different machine/IP, that's
all you need. The clients will simply open outgoing ports as needed...
unless you're using an unusually large number of outgoing connections,
you shouldn't have any problem.

-- 
Richard Beals
Confuser of Software
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:[email protected] with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.