LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (August 2003, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Fri, 8 Aug 2003 22:16:35 -0400
Reply-To:   Don Henderson <donaldjhenderson@HOTMAIL.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   Don Henderson <donaldjhenderson@HOTMAIL.COM>
Subject:   Re: weblogin.sas
Content-Type:   text/plain; charset="iso-8859-1"

Tony,

A few comments on these questions.

----- Original Message ----- From: "Tony" <hztangli@YAHOO.COM> Newsgroups: bit.listserv.sas-l To: <SAS-L@LISTSERV.UGA.EDU> Sent: Friday, August 08, 2003 7:39 PM Subject: weblogin.sas

> Hi there, > The other day I played with SAS/IntrNet,come across some questions: > 1.In the source code of sample.weblogin.sas bundled with the product,I > found two macro variables called _hiddenfields and _userprogram.Because > they begin with underscore,I assume they are reserved macro variables > created by broker or application server.But I couldn't find any document > about these two macro variables on sas website.My question is: > How many other reserved macro variables could be created by broker which > are also not documented?To know all these macro vars will definitely help > developer and programmer a lot.

As described in (for example):

http://support.sas.com/rnd/web/intrnet/dispatch12/reffield.html#_FLDWDTH

variables that begin with _ are not split into multiple fields if the values are too long. This is a fairly common technique used by those who are aware of it to force potentially long values to not be split up into multiple fields. I would suspect that these two fields are not special. The programmer who wrote the weblogin facility probably choose those names so the values would not be split.

> 2.I add auth=host and REQUEST LOGIN=sample.weblogin.sas in appsrv.sas.Then > I tried to send a simple html form to invoke a dispather program.The > weblogin.sas run first and ask me to enter username and password.I > intentionly enter wrong username and password,then I got similar web > page.I check the source code and found all the form elements I previouly > submit become hidden type.I guess this is automatically handled by broker > or application server.But I couldn't find any document about this kind of > mechanism.

Yes this is handled automatically by the facility. I am not sure I understand the point of your question however. It seems that you are saying it performs as you expect, but you still want the internals documented? When I was at SAS, effort was concentrated on documenting how to use the software instead of publishing to the user community the software internals.

> 3.Regarding the magic appsrv_session function, SAVE libref or SAVE_ > whatever macro,I know how to use them and I only have whatever document > avalaible on sas website.I couldn't find any detail document.Does anyone > know what's going on behind scene ?

The documentation on the web site, combined with SUGI papers, as well as course notes is probably all there is. I just did a search on support.sas.com for

+intrnet +_save

and got a number of informative hits. You might want to check those out.

A short summary of what is going on is that when you use appsrv_session it creates a persistent work library for your IntrNet requests. You can save data sets, catalogs, etc. to that library. In addition the Application Server provides a facility to save anymacro variable across those sessions by copying them to macro variables prefixed with "SAVE_" which results (I believe) in their being saved to the SAVE library and then restored for you.

> 4.By my understanding,SAVE libref is associated with specific sas server > when sesssion is created.How does Intelligent Load Balancing by > loadmanager work together with session management?

Once you assign a session, any followon requests need to use the session to create links, forms, etc. That is documented on the web site. That means that once a session is assigned, all further requests that use the session will go to that server. The first request (the one that created the session), was assigned to a server by the load manager. While not a perfect load balancing scheme, it does balance the user sessions, if not all the jobs.

> 5.I did reply to Don and David's response regarding %save2gm macro, > but somehow my message was not posted.What I need is exactly what this > macro seem to offer.I want to setup a web server(apache) directory so that > user can use web browser to save html file or report links to that > directory and retrieve links later.I'm not a apache expert,is it possible > to do that with apache and how?

There are many facilities you can use to upload, via a browser, files/content to a server. However you need software on the server to handle the upload. The %save2gm macro was written to leverage the SAS Collaborative Server (now Intraspect). If you want similar functionality, you will need to identify what server software you will want to use and then determine whether it already has a browser based mechanism to do an upload. I do not know enough about Apache to know if it has such a facility.

> TIA, > Tony >

HTH, -don h.


Back to: Top of message | Previous page | Main SAS-L page