Date: Wed, 5 Dec 2001 14:22:06 +0100
Reply-To: Søren Damgaard Laursen <sdl@TDK.DK>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Søren Damgaard Laursen <sdl@TDK.DK>
Organization: TDC Internet
Subject: Re: Q about Microsoft NLB and Sas/IntrNet
Hi Francesco
Thanks for your quick response, but 'unfortunately' I know all of these
things allready.
I was just wondering if the was any speciel considerations to take into
account regarding Sas/IntrNet, loadmanager, etc. when we want to use these
technologies on a web server cluster.
Regards
Søren
"Francesco" <francesco@nospamonetel.co.uk> wrote in message
news:3c0e0499@212.67.96.135...
> Hi Soren, you install the Load Manager on the machine where the web server
> resides, in your case your Win 2000 Box. On Windows, simply click in the
SAS
> program group -> IntrNet -> Create New IntrNet Service and then select
> 'Configure the Load Manager'. This will create a Directory which will
> contain
> the Load Manager log as well as Load Manger program group which contains
> icons to stop and start the load manager either interactively or as a
> Windows
> service.
>
> To use the Load Manager you then have to create one (or more if you need
> them)
> Pool Service, again from the Create New IntrNet Service icon. Just follow
> the
> simple steps. The last step in the wizard will show you the text to be
> included in
> your broker.cfg file. Something like this:
>
> PoolService default
> ServiceDescription "Default Pool Service"
> ServiceAdmin "Admin Name"
> ServiceAdminMail "adminmail@company.com"
> Server servername
> ServiceTimeout 3600
> Port 10
> MinRun 3
> IdleTimeout 30
> FullDuplex True
> ServiceLoadManager loadmanager_server:5001
> SasCommand "\"d:\\Program Files\\SAS Institute\\SAS\\V8\\sas.exe\" +
> \"d:\\SAS Services\\default\\appstart.sas\" +
> -rsasuser -noterminal -nolog -SYSPARM "
> # Uncomment the following lines if Spawner is used to start
> # the SAS system (required if Load Manager is not running
> # on this node.)
> # SpawnerPort [port]
> # Username [username]
> # Password [password]
>
> All you have to is to change 'servername' to your UNIX box where the
> SAS server of the application dispatcher resides and this should work.
> Please note that, unlike socket services, you do not specify a port for
> the Pool Services. The Load Manager will assign automatically ports
> whenever a SAS server is started. The only port you have to specify
> esplicitly id the port used by the Load Manager (5001 in the example
> above).
>
> There are loads of other options that can be set, but I send you the
> documentation for them.....
>
> Hope this helps.
>
> Regards, Francesco
> Nemesi Ltd.
> United Kingdom
>
> "Søren Damgaard Laursen" <sdl@tdk.dk> wrote in message
> news:3c0df6ca$0$25384$edfadb0f@dspool01.news.tele.dk...
> > Hi there,
> >
> > In the near future we are considering moving our web-application based
on
> > win nt web-server and DEC Unix as a backend using Sas/Intrnet and load
> > manager, over to a windows 2000 Cluster utilizing Network Load
Balancing -
> > but still maintaining the unix as backend, of course!. This cluster
> consists
> > of two identical servers.
> >
> > Does anyone have any experience regarding the technical setup of the
> > broker.cfg and the loadmanager.
> >
> > More specifically:
> > Do we install the loadmanager on one server or both? Or should we
install
> it
> > on a different server outside the cluster?
> > Are the broker.cfg identicial on the two servers?
> >
> > Any other tips are welcome..
> >
> > Thanks in advance
> > Søren Laursen
> > TDC Services IT.
> >
> >
>
>
| 
