Date: Mon, 26 Mar 2001 22:07:25 +0000
Reply-To: mauro.morandin@MATRIX-ONLINE.IT
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: mauro.morandin@MATRIX-ONLINE.IT
Organization: Mailgate.ORG Server - http://www.Mailgate.ORG
Subject: Re: SAS/Intrnet
Content-Type: text/plain; charset=us-ascii
Hi,
I have to disagree with Sigurd, since it is not a good idea to have
SAS/Intranet on NT
and your data on UNIX, simply because if you put SAS/Intranet on NT
1. You need to have SAS also on the WinNT server (new license)
2. If you dont install SAS/Intranet on UNIX what you have is a web
server
which at each request calls the broker which starts or uses a SAS
session
on the NT server, which connects to a UNIX SAS session to submit a
query,
which returns the resultset to the SAS session on NT which
formats the output and
delivers a HTML document back to the broker which passes it on to
the webserver
which sends it to the client's browser. Hhmmmm!!!
This is an extremely weak design.
3. If you put SAS/Intrnet on WinNT you will not be able to use MDDB
report viewer because
MDDB Report Viewer is part of SAS/Intrnet but you have
SAS/MDDB licensed on UNIX,
so that's where SAS/Intrnet MUST be.
I don't know what your SCL application does, but
if what you need is to be able to do interactive multidimensional
analysis then MDDB Report
Viewer does the job for you. You need SAS/Intrnet, SAS/MDDB and a
EIS Metabase and the
software is already done, all you have to do is to configure it.
An expert consultant should take not
more than half a day to install SAS/Intranet and to set up MDDB
Report Viewer.
The bad thing about MDDB RV is that it is a black box and you
cannot change the way it works. It's
not customizable. Either you like it as it is, or nothing. Then,
and this depends on your metabase, it
sometimes has performance problems.
On the other side WebEIS does the same thing and is much nicer
AND you can integrate WEBEIS multidimensional navigation very easily into WebAF
applications. You can call remote SCL classes via ROCF in WebAF. If you have a
well designed SCL application in which data manipulation logic and
visualization logic are clearly separated you could take the SCL which does
data manipulation, put it on the UNIX server and rewrite the visualization
logic in Java/WebAF. So you could reuse part of the code which
was originally written in SCL, and that's what WebAF was designed for. But as I
said earlier I don't know
what the SCL does, how complex it is, and probably you have to rewrite a good
part of it in Java.
And what if you discover that Java is so damned slow on your clients and you
have problems with the different browsers (Netscape, IE) and the Java Virtual
machine fills up your clients memory because
SAS Web Application tools still use JDK1.1.8 while JDK1.4 Merlin is beta and
has such nice features which
you will able to use in 2005 with ADS 5.0. I cannot reccomend Java for writing
complex client applications which will run as applets inside a browser, too
slow and clumsy (Jdk 1.1.8 1.1.8 1.1.8 you see!!!).
If you have problems with a simple AF application don't try SAS/Intranet, it
will get worse, spend your money to improve what you have. Going Intranet means
rebuilding almost everything and it's not worth if you don't have the need to
go Intranet. Why do you need to go Intranet? Is there something you can't do
with AF?
Do you want to save the money of a hundred SAS client installations?
Good luck!
ciao
mauro
> [Previous] [Next] [Reply] [Index] [Home] [Find]
>
> * Newsgroups: comp.soft-sys.sas
> * From: HERMANS1@WESTAT.COM (Sigurd Hermansen)
> * Subject: Re: SAS/Intrnet
> * Date: 21 Mar 01 16:00:54 GMT
> * Reply-To: Sigurd Hermansen <HERMANS1@WESTAT.COM>
>
> ------------------------------------------------------------------------
>
> The decision to put SAS/Intrnet on one platform or another depends largely
> on expected volume of traffic from the net, and not as much on the location
> of data. SAS/Intrnet acts as a "broker" of queries. For example, it can
> insert values of macrovariables into program templates, forward programs to
> a SAS server (say, a separate Unix server), and transfer HTML/etc. back to a
> Internet browser. A relatively small NT machine may prove more than
> adequate to handle net traffic and much cheaper to license for SAS Intrnet.
> Last time I looked, SI charged about five times as much for a Unix
> SAS/Intrnet license as for a NT license. Hopefully this level of
> discrimination will change as Linux and smaller Unix boxes become recognized
> as equivalent in function to NT Web brokers. Separating the broker function
> from the server function also increases data security somewhat. Sig
>
> -----Original Message-----
> From: Ravi, Prasad [mailto:Prasad.Ravi@PFIZER.COM]
> Sent: Wednesday, March 21, 2001 9:51 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: SAS/Intrnet
>
> In this scenario it seems like it make sense to install SAS/IntrNet on
> your UNIX server since your data resides on this, hopefully your programs
> are also on the Unix server. You don't have to install that software on
> both NT and UNIX servers, hopefully all your users have UNIX access.
> SAS/IntrNet comes with htmSQL and Application dispatcher components, which
> can query your data and generate reports on the web. Also you have to have
> SAS/SHARE product to use SAS/IntrNet software.
>
> Further you can invite local SAS/IntrNet representative to examine all
> possible options for your case, they will recommend what would be the best
> thing for you .
>
> -----Original Message-----
> From: Jit Bhattacharya [mailto:jit.bhattacharya@PRUDENTIAL.COM]
> Sent: Wednesday, March 21, 2001 9:22 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: SAS/Intrnet
>
> Mike Davis and Ming gave me some tips on SAS/Intrnet - but I guess I need to
> go
> into some details - problem is, I do not know them all, but I will try.
>
> Our company has a Unix server with 4 processers and about 100 GB of space -
> we
> have very large datasets. we are also thinking about allocating an NT
> machine to
> act as a web server. Our intent is to explore possibilities to use
> SAS/Intrnet.
> Currently we have a SAS/AF application that is used by 100 users to access
> the
> Unix datasets. Our experience with this 'fat client' has not been all
> positive,
> so we are thinking of switching to SAS/Intrnet, if feasible. Our datasets
> have ,
> on average, 4 million obs, with some with as many as 50 million obs. Our
> current
> application enables drilldown on MDDBs that are viewed with an EIS object.
> We
> would like to have this capability with Intrnet. other than this, our basic
> need
> is for users to choose certain parameters, and start SCL/SAS code to show a
> report. We wanted to know what are the implications of moving to Intrnet. I
> would say, at any given time, not more than 7-8 users would run reports.
> Should
> we be getting Appdev Studio? or can we do without it?
>
> Jit
>
> ------------------------------------------------------------------------
> [Previous] [Next] [Reply] [Index] [Home] [Find]
> Mailgate.ORG is maintained online by Dario Centofanti
--
matrix srl linux solution provider
via postioma di salvarosa 25b tel +39-0423-724620
31033 castelfranco veneto (tv) fax +39-0423-770798
http://www.matrix-online.it info@matrix-online.it
--
Posted from flat-pool13-mdm036.aruba.it [62.149.152.38]
via Mailgate.ORG Server - http://www.Mailgate.ORG
| 
