In the end, the execution of a stored process using the SAS Stored Process Web Application boils down to a URL something like this:
http://server:port/SASStoredProcess/do?_program=.
Sometimes people add an HTML link to their existing Web application with the URL shown above, and just let the WebApp do all of the work. Other times they use the built-in Java methods to make the HTTP call to the URL shown above (and thus execute the stored process), read the output stream, and do whatever they like with the output from the stored process. The latter works well if the stored process creates "streaming" HTML output without graphic images, XML, RTF, and PDF output.
If you really need to write more robust Java code to handle stored processes, you might find this information useful:
http://support.sas.com/kb/26/054.html
Note that the code shown in the sample will work with SAS 9.1.3, but not SAS 9.2, as the API has changed between SAS 9.1 and SAS 9.2.
With both SAS 9.1 and SAS 9.2 we ship some sample JSP files that illustrate how to execute a stored process. They can be found under the /SASStoredProcess/jsp/examples/ tree.
For SAS 9.1 running the Tomcat server on Windows, the path is typically:
\webapps\SASStoredProcess\jsp\examples
For SAS 9.2 running the JBoss server on Windows, the path is typically:
\server\SASServer1\deploy_sas\sas.storedprocess9.2.ear\sas.storedprocess.war\jsp\examples\
If you need further help, I suggest you open a track with our Technical Support department:
http://support.sas.com/ctx/supportform/index.jsp
Most of our users are able to use the SAS Stored Process Web Application to meet their needs. If it doesn’t work out for you, we would be interested in knowing the shortcomings, and hear suggestions on how we can fix them.
Vince DelGobbo
SAS R&D
