Hi @Cassidamius   To take a step back, what SAS component are you looking to use? Is it some SAS Foundation based programs that previously worked in batch, or is it one of the newer solutions that uses something like ESP?   There are ways of designing a solution such as the one you're talking about, and while there are a few hacky ways that allow SAS foundation to process streaming data (named pipes etc), it's not really the ideal solution. Some level of caching will always need to be done somewhere. The ultimate design will be highly dependent on the component that's been passed on to you, so if you're able to share more detail on it, we'll be able to give you a more detailed answer.     Nik ... View more

Hi @Vince_SAS,   Sorry to hijack this thread but I think this question is relevant enough for the OP. It's also one I've been arguing about with a colleague for a couple of weeks now, but haven't got round to testing yet. The documentation on this subject states the following:   A session exists in the server process where it was created. All stored processes that access that session must execute in the same server process. Load balancing and other execution dispatching features are typically ignored when using sessions that might have an impact on application performance and scalability.    Does this mean that when a session is created when a particular client executes a session-using STP, the normal load balancing for subsequent requests is ignored and some kind of session affinity for that multibridge process takes precedence over the LB for connections from that client? Or does the client continue to get redirected to available multibridge processes by the spawner as usual depending on the configured load balancing algorithm, and the session will only be reused if the request lands on the same multibridge process where the session was initially saved?   Hope that makes sense. Maybe it's just me but the way that paragraph is worded could suggest either of those...   Thanks Nik ... View more

You'll need to provide the context of your STP execution environment to get a more detailed answer. Enterprise Guide, Stored Process Web App, AMO?   In any case I'd suggest you run the following code as a stored process in the same execution environment:   proc options option=jreoptions; run; It may be that the user that your STP is executing under can not find the specified Java path, that your STP server is misconfigured, or that the version of java is wrong. I just googled your error and the same solution is an answer on this forum from a couple of months ago.   Good luck. ... View more

What @Tom suggests is the correct approach, and should prompt your end user to download a .csv file. I'd code it slightly differently, so I'm including the following code in case the variation helps you understand what's going on.   /* filename to write temp file to if you want an intermediate file for whatever reason */ filename mygenfn temp; /* then insert code here to write your csv to that tem filename above */ /* set the headers same as @Tom did */ %let RV=%sysfunc(stpsrv_header(Content-type,application/vnd.ms-excel)); %let RV=%sysfunc(stpsrv_header(Content-disposition,attachment; filename=something.csv)); /* bytestream out to _webout for the browser to download */ data getout; length data $1; infile mygenfn recfm=n; file _webout recfm=n mod; input data $char1. @@; put data $char1. @@; run;   I've also used variations on the above data step, including put _infile_ instead of put data $char1. @@. Same idea. This post might also give you something to think about depending on what you're trying to do. It's where I copied my answer above from.   Nik ... View more

If you're not looking to deploy a middle tier, then I would suggest you deploy the '(Optional) Metadata Server' node first, and the 'Server and Middle Tier' node second, making sure that the second time round you deselect any Middle Tier components that you don't need, as well as the Metadata components.   I have to say that I haven't tried it with this particular default plan, but would be the approach I would take if I was in your position.  ... View more

I disagree Tom. In my experience SAS tools are awesome at data capture, but you have to take a slightly different approach. It's one of the reasons we maintain this library.    @RS1 if you want to apply that kind of styling to your prompts, traditionally you'd have to write some .jsp and deploy it within your SAS Stored Process webapp. However, I don't think your prompts are that far away from what you're after; you'll probably achieve the effect you're after by simply removing the nobanner word from your URL and adding slightly better descriptions to your prompts.   Good luck.   Nik ... View more

Hi,   @JuanS_OCS actually answered your question, albeit indirectly.   The HTML you are writing with your put statements will actually be resolving to something like  <script src=""D:\whatever\your\path\was/src/jsgrid.core.js""></script> This is obviously wrong, as your browser needs to load your library from a web server, not a location on your disk. Imagine it being typed into the address bar.   What you need to do is copy your src directory with all the .js files you want to load into your Config\LevX\Web\WebServer\htdocs directory so that they are served up by the web server (assuming SAS 9.4). Then doing something like    put "<script src=""/src/jsgrid.load-indicator.js""></script>" for each of your includes ill load your library correctly.   I don't agree with the design pattern of using STPs and put statements to generate HTML when you've got an actual web server / reverse proxy available with your environment, but that's a different conversation altogether.   Nik  ... View more

Technically this is completely off topic as it doesn't use ODS or SAS/GRAPH, but I spent almost an hour doing it so I can't not post it now. Here's the same in JavaScript, using a slightly modified version of the original SAS code to create the SVG, and vivus.js to animate it:     The SAS code to generate the SVG looks like:   data _null_; length shapeID $ 20. x 8 y 8; gh = 40; * grid height ; gw = 30; * grid width ; file "/pub/ht/bunny/my.svg"; * target SVG location and write header ; if _n_ eq 1 then put '<svg width="' gw +(-1) '0" height="' gh +(-1) '0" viewBox="0 0 ' gh gw '" id="bunny">'; infile "/pub/programs/EB.txt" lrecl=1000 end=EOF; * File contains points to plot from math-aids.com; input; if _infile_=:'Shape' then do; shapeID=_infile_; if _n_ gt 1 then put '"/>'; * unless its the first element we will need to close last one ; if shapeID in ('Shape 16' 'Shape 17' 'Shape 21' 'Shape 22' 'Shape 3' 'Shape 4' 'Shape 5' 'Shape 6' 'Shape 9' 'Shape 10' 'Shape 11' 'Shape 12') then put '<polygon fill="none" stroke="#FF8A65" stroke-width="0.2" points="' @; * if this is a polygon then it is a polygon, else it is a polyline ; else put '<polyline fill="none" stroke="#FF8A65" stroke-width="0.2" points="' @; end; else do; i=1; do while(scan(_infile_, i, ' ')^=''); x=scan(_infile_, i, '(), ') + ((gw / 2)); put x +(-1) ',' @; y=((gh / 2) - scan(_infile_, i+1, '(), ')); put y @; i+2; output; end; end; if EOF then put '"/></svg>'; run;    The Vivus JS constructor to animate it looks like:   new Vivus('bunny', { type: 'oneByOne', duration: 800, pathTimingFunction: Vivus.EASE_OUT, });   If anyone wants to see the generated SVG or have a play around with the JavaScript code, the example is up on JsFiddle: http://jsfiddle.net/m3xswhnz/.   Hurray for long weekends.   Nik ... View more

It depends on how many steps there are in your deployment plan and where this step sits within that deployment plan.   If you're attempting the entire of your Lev2 deployment again then feel free to delete your /appdata01/sas9.4/config/biserver/Lev2 directory completely and rerun the 'configuration' step of the SDW deployment. If it's a more complex multi-step deployment, you know what you're trying to do and you just need to get past this individual error in this deployment step, you'll progress by making sure that the /appdata01/sas9.4/config/biserver/Lev2/WebInfrastucturePlatformDataServer/data directory is completely empty. However, it's more than likely that you'll hit other errors as a result of your failed 1st attempt.   You probably just want to delete your /appdata01/sas9.4/config/biserver/Lev2 directory and rerun the configuration step of the SDW.   Nik   ... View more

A few lines above your failure, it looks like initdb is failing as your data directory is not empty:     [exec] initdb: directory "/appdata01/sas9.4/config/biserver/Lev2/WebInfrastructurePlatformDataServer/data" exists but is not empty [exec] If you want to create a new database system, either remove or empty [exec] the directory "/appdata01/sas9.4/config/biserver/Lev2/WebInfrastructurePlatformDataServer/data" or run initdb [exec] with an argument other than "/appdata01/sas9.4/config/biserver/Lev2/WebInfrastructurePlatformDataServer/data".   This normally happens because that location has already been initialised as a repo for your WIP Data Server (Postgres), likely by a previous deployment wizard run. Is this a second attampt at a configuration, or that step of the configuration?  ... View more

I do. Further to that, if the developer states that it's only ever run locally then there may be a couple of things you could try. You say logging on to the remote server and running Foundation from where it was installed works. So, if mapping that remote SASFoundation location to a drive letter on your client and then running it doesn't work, then this would be my approach:   1. Try logging on directly to the remote server, but accessing your SASFoundation via a UNC path to the local server as you did remotely before (\\localserverimloggedinto\SASFoundation\whatever). I'd probably expect it to fail. 2. Log on to the remote server and map that same UNC path (referring to the server itself) to another drive letter, effectively remapping SASFoundation's installed location (kind of similar to moving it). Try running it.   If step 1 works then there may be something you need in the registry (which I seriously doubt). If step 1 fails but step 2 works, then it means that your lib may depend on a hardcoded path somewhere that it looks up locally at runtime, while at the same time disliking UNC paths (as a lot of apps do).   My solution to this problem either way would be to either remap your SASHOME to an arbitrary drive letter that can be shared by all your client machines (ie. they can all remotely map it identically as G:\SASFoundation or something) and then reinstalling your PROC LCA directly to that 'remounted' arbitrary drive letter foundation location, or even better, reinstalling all of SASFoundation from scratch onto a path which you can replicate via mapping the remote location onto the same drive/letter on each of your client machines.   I'd expect this to work, but I'm almost certain that you won't need to go to all that trouble - just mapping your SASFoundation to a drive letter and launching from there should do the trick. Lots of windows apps, especially older ones, don't like UNC paths. Nik ... View more