Which Clients Can Use SAS Stored Processes?

You can use JMP to run stored processes and view results. See Using JMP for more information.

The SAS Add-In for Microsoft Office is a Component Object Model (COM) add-in that extends Microsoft Office by enabling you to dynamically execute stored processes and embed the results in Microsoft Word documents, Microsoft Excel spreadsheets, and Microsoft PowerPoint presentations. Also, within Excel, you can use the SAS add-in to access and view SAS data sources or any data source that is available from your SAS server, and analyze SAS or Excel data by using analytic tasks. For more information about using stored processes with the SAS Add-In for Microsoft Office, see the SAS Add-In for Microsoft Office Online Help, which is located within the product.

You can use SAS BI Dashboard to execute stored processes and to include stored processes or stored process results in a dashboard. When a dashboard has an indicator that was configured with stored process indicator data, users can see output from that stored process if it belongs to the displayed dashboard. See SAS BI Dashboard: User's Guide for more information.

SAS BI Web Services provide a Web service interface to SAS Stored Processes. Starting with SAS 9.3, all stored processes are available individually for execution using Web services, without any action required from the user. For more information about using stored processes with SAS BI Web Services, see the SAS BI Web Services: Developer's Guide.

SAS Data Integration Studio enables its administrators to publish jobs as stored processes. SAS Data Integration Studio can generate code that converts a job into a stored process, which is saved to a file and can be executed later by the SAS Stored Process Server. Metadata about the stored process is saved in the current metadata repository. For more information about using stored processes with SAS Data Integration Studio, see the SAS Data Integration Studio product Help.

SAS Enterprise Guide provides an integrated solution for authoring, editing, and testing stored processes. You can create stored processes from existing or new SAS code and create stored processes automatically from SAS Enterprise Guide tasks. Metadata registration and source code management are handled from one interface. SAS Enterprise Guide also has the capability to execute stored processes, which enables you to modify and test your stored process without leaving the SAS Enterprise Guide environment. For more information about using stored processes with SAS Enterprise Guide, see the SAS Enterprise Guide product Help.

The SAS Information Delivery Portal provides integrated Web access to SAS reports, stored processes, information maps, and channels. If you have installed the SAS Information Delivery Portal, you can make stored processes available to be executed from the portal without the need for additional programming. The SAS Information Delivery Portal includes the SAS Stored Process Web Application. For more information about using stored processes with the SAS Information Delivery Portal, see the SAS Intelligence Platform: Web Application Administration Guide.

Stored processes can be used to implement information map data sources. Stored processes can use the full power of SAS procedures and the DATA step to generate or update the data in an information map. For more information about stored process information maps, see the SAS Information Map Studio product Help.

The SAS Stored Process Web Application is a Java Web application that can execute stored processes and return results to a Web browser. The SAS Stored Process Web Application is similar to the SAS/IntrNet Application Broker and has the same general syntax and debugging options as the Application Broker. For examples of this component, see Using the SAS Stored Process Web Application Pages. The SAS Stored Process Web Application is included with the SAS Web Infrastructure Platform, which is a component of SAS Integration Technologies.

You can use SAS Web Report Studio to execute stored processes and to include stored processes or stored process results in a report. For more information about using stored processes with SAS Web Report Studio, see the SAS Web Report Studio: User’s Guide, the SAS Intelligence Platform: Web Application Administration Guide, and the SAS Web Report Studio product Help.

The Stored Process Java API is a Java application programming interface (API) that enables you to execute stored processes from a Java program. This API is commonly used in JSP pages, but can also be used from servlets, custom tagsets and other Java applications. The Stored Process Java API is part of SAS Foundation Services; you must deploy SAS Foundation Services in order to use the Stored Process Java API. If you want to register new stored processes and modify metadata for existing stored processes programmatically, use the com.sas.services.storedprocess.metadata API. See the API Javadoc at http://support.sas.com/rnd/javadoc/93 for more details.

The Stored Process Windows API is a Microsoft .NET application programming interface (API) that enables you to execute stored processes from within the .NET framework (using C# or VB.NET, for example). This API is used by both SAS Enterprise Guide and SAS Add-In for Microsoft Office, and can be used to write ASP.NET or Windows applications. The Stored Process Windows API is part of SAS Integration Technologies; you must deploy SAS Integration Technologies in order to use the Stored Process Windows API.