topic Re: Images in Stored Procedure URL Display Portlet in Developers

Images in Stored Procedure URL Display Portlet

DavidPhillips2 — Thu, 16 Apr 2015 16:52:53 GMT

In SAS 9.2 I have a stored procedure that I am displaying in a URL display portlet. What is the best location to store images such that I can call them in the stored processes.

I wasn’t sure if this should be in the stored processes section or SAS / Graph and ODS Graphics.

The display code is:

<IMG SRC="/SASStoredProcess/do?_program=

/WebApps/Utilities/Sales+by+Product&XPIXELS=

400&YPIXELS=300">

SAS Stored Processes: Embedding Graphics

Re: Images in Stored Procedure URL Display Portlet

Quentin — Thu, 16 Apr 2015 18:00:25 GMT

What do you mean by call them [images] in the stored process?

you want the stored process to generate an image (graph or whatever) and display it?
you want the stored process to generate an html page that includes a link to an image already sitting on your web server (like a logo)?
something else?

Re: Images in Stored Procedure URL Display Portlet

DavidPhillips2 — Thu, 16 Apr 2015 18:03:01 GMT

I want to display a logo.

Re: Images in Stored Procedure URL Display Portlet

Quentin — Thu, 16 Apr 2015 18:42:38 GMT

If you want to have, for example, a SAS procedure (GPLOT, SGPLOT, PROC TABULATE, etc) create a little html page that incorporates an image, I would put the image file somewhere that the SAS server can see. Then use the style template or proc syntax or whatever to display the image.

This paper for example describes how PROC REPORT can insert images into output.

http://www2.sas.com/proceedings/sugi27/p187-27.pdf

This paper has examples of inserting logos with SGPLOT

https://support.sas.com/resources/papers/proceedings11/277-2011.pdf

HTH.

Re: Images in Stored Procedure URL Display Portlet

DavidPhillips2 — Thu, 16 Apr 2015 18:48:19 GMT

On the same server that the stored procedure is being called from.

PUT "<tr><td><IMG SRC='https://myserver/banner.jpg'><td><tr>";

This link http://support.sas.com/kb/34/138.html did not work for me but might be useful for someone else.