Custom Input Forms for SAS^® Stored Processes are discussed in the Specifying Custom Input Forms section of the SAS^® 9.2 Stored Processes: Developer's Guide.

This Usage Note provides some additional tips for creating and troubleshooting Custom Input Forms for SAS Stored Processes that are executed using the SAS Stored Process Web Application. The information in this Usage Note references the JBoss Application Server, but the approach is similar on other Web Application servers.

If you cannot explode your sas.storedprocess9.2.ear file or chose not to do so, then see Rebuilding the SAS Web Applications in the SAS^® 9.2 Intelligence Platform: Web Application Administration Guide, Third Edition. Otherwise, see the next section.

Tips for Creating a JSP file in an exploded directory

The following steps describe how to create a custom form in a directory after the sas.storedprocess9.2.ear file has been exploded.

Disclaimer: If you create a Custom Input Form in an exploded directory (as described below) be sure to make a backup copy of the JSP file. If a new sas.storedprocess9.2.ear file is deployed, the custom JSP file will be lost, so you will need to recreate the JSP file using the backup copy.

1. The SAS Stored Process Web Application looks for a custom input form if you add the parameter _ACTION=FORM to the Web application URL. Custom input forms are JSP files under the input folder in the SASStoredProcess directory on the JBoss Application Server.
2. On your JBoss Application Server, check to make sure that your sas.storedprocess9.2.ear file is exploded so you can view the subdirectories. The directory path for your custom JSP file should be similar to the following:
   .../SASServer1/deploy_sas/sas.storedprocess9.2.ear/sas.storedprocess.war/input/
3. If the directory is not exploded, then see Usage Note 37052 about instructions for manually unpacking (exploding) SAS^® Web application .ear files
4. There are sample JSP files under the above directory that you can view and use as models for creating other custom JSP files.
5. The location of the JSP file must correspond exactly with the location of the associated SAS Stored Process in the SAS^® Metadata Repository. This location is case sensitive.

   As an example, suppose you have a SAS Stored Process called teststp that is located under the Folders tab in SAS^® Management Console at:

   SAS Folders ► TestDir ► teststp

   Then, the location of the corresponding JSP file on your JBoss Application Server must be at:

   /sas.storedprocess.war/input/TestDir/teststp.jsp

   which is under the following directory:

   .../SASServer1/deploy_sas/sas.storedprocess9.2.ear

Troubleshooting Tips

If your SAS Stored Process is not using the Custom Input Form (JSP file) that you created, the following troubleshooting tips should be helpful.

1. Go to the Welcome page for the SAS Stored Process Web Application. For example: http://your.server:8080/SASStoredProcess/do
2. Select List Available Stored Processes
3. Drill down and select the SAS Stored Process that you want to execute. Then, right–click and select Open in New Window.
4. In the newly opened Web browser window, note the URL address at the top of the window.
5. Modify the URL address as follows:
   1. Change the _action= parameter to contain ONLY the following:
      _action=form
   2. Add the following at the end of the URL:
      &_debug=trace

      The new URL will be similar to the following: http://your.server:8080/SASStoredProcess/do?_action=form&_program=/TestDir/teststp&_debug=trace

6. At the bottom of the trace output, you should see a message that is similar to the following:

       >>> Checking for customizer /input/TestDir/teststp.jsp
    

   The SAS Stored Process Web Application is trying to find the JSP file at this location on your JBoss Application Server. This location must exactly match the physical location of the teststp.jsp file on your JBoss Application Server (under the sas.storedprocess.war/input/ directory). This path is Case Sensitive.

Operating System and Release Information