Testing the Installation

After you install the client and server components of the SAS Design-Time Controls, you can test the installation.

Testing the SAS server components
Testing the client components
Testing the Web server components

Testing the SAS Server Components

Test to see if your SAS/IntrNet Application Server is running. Invoke your Web browser and enter a URL like the following:
```
   http://myserver/cgi-bin/broker.exe?_service=default&_program=status
```
A Web page that indicates that the server is functioning properly should be returned.
Test to see if the WEBSDK1 catalog is installed and accessible. Enter a URL like the following:
```
   http://myserver/cgi-bin/broker.exe?_service=default&_program=sashelp.websdk1.member1.scl&wrtform=y
```
A Web page that consists of a single selection list box should be returned. The list box should contain a list of data set names. If you see this list, then the WEBSDK1 catalog is installed and functioning correctly. If you see the following message
```
   The program sashelp.websdk1.member1.scl is not available: 
   ERROR: Catalog SASHELP.WEBSDK1 does not exist.
```
then you might have installed the WEBSDK1 catalog incorrectly. You will need to repeat the steps for setting up the SAS server components.

If you see the following message
```
   sashelp.websdk1.member1.scl is unavailable, sashelp was not found in a
   proglibs or adminlibs statement.
```
then you need to modify your PROC APPSRV code to allow access to the WEBSDK1 catalog.

Testing the Client Components

Make sure that your SAS/IntrNet Application Server is running.
Start your HTML editor and begin editing a new HTML page.

Note to FrontPage 98 users: FrontPage 98 hides Design-Time Controls unless you turn on paragraph tags. Find the toolbar icon for paragraph tags and make sure that it is selected before you proceed. In addition, FrontPage 98 requires a patch in order to make SAS Design-Time Controls function properly. For more information about the patch, see the Client Requirements for the SAS Design-Time Controls
Access the list of Design-Time Controls. To access the list of controls in FrontPage 2000
1. Select Insert Advanced Design-Time Control from the menu bar. The Insert Design-Time Control dialog box is displayed with a list box that initially contains no items.
2. Select the Customize button and you should see the list of the controls that are installed with the SAS Design-Time Controls package.
3. Check all of the check boxes that are next to the SAS controls and then select the OK button. The controls should now appear in the initial list box.
Insert a SAS Table Control by selecting it from the list of available controls. At this point, you should see a SAS table icon inserted into the Web page or appearing in a floating dialog. If an icon does not appear, refer to the SAS notes on support.sas.com.
Access the properties dialog for the Table Control. To access the Properties dialog in FrontPage 2000, double-click on the icon. Other editors might require that you to select a properties button or select an option on the icon's pop-up menu. A slight delay occurs before the Properties dialog appears because the control connects to SAS and loads a list of available data sets.
Examine the drop-down list that is provided for the Data Set Name field on the Dataset tab in the Properties dialog. This drop-down list should display several data set names. If it does, then your client components are functioning properly.
If the drop-down list of data set names is empty, then look at the values for the fields on the Connection tab of the Properties dialog. Make sure that these values are correct. If these fields contain incorrect values or blanks
1. Close down the Properties dialog and exit the HTML editor.
2. Follow the steps on the Default Connection Information page to set the correct connection information.
3. Repeat the steps for testing the client components.

Testing the Web Server Components

The next step is to test the Web server components that enable JSP and ASP support.

Make sure that your SAS/IntrNet Application Server is running.
Start your HTML editor and edit a new HTML page.
Insert a SAS Table Control. Invoke the Properties dialog and choose the data set SASHELP.RETAIL from the Data Set Name drop-down list on the Dataset tab.
Close the Properties dialog and save the HTML page.
Preview the HTML page in your Web browser to ensure that the HTML table is properly generated. You should see a table that displays the SASHELP.RETAIL data set.
Look at the address or location line in your Web browser and see if the URL begins with http. If the URL does not begin with http, then you are not viewing the Web page from a Web server; you are viewing a page that is a local file. If you are not viewing the page from a Web server, then publish this page to your Web server. After you are able to view the page in the browser and the URL begins with http, you can proceed to the next step.
Replace the static display of the RETAIL data set with a dynamic display using an ASP or JSP. Edit the same HTML file and open the properties for the SAS Table Control.
Select the Connection tab in the Properties dialog.
In the Perform SAS processing field, the default value is once when building this page.
- If you want to test ASP support, select when Active Server Page is invoked from the drop-down list for this field.
- If you want to test JSP support, select when Java Server Page is invoked from the drop-down list for this field.
Save the property changes.
Inspect the HTML source code for the page you are editing to verify that the output from the control is ASP or JSP code and not HTML.
- If you specified to perform processing when an Active Server Page is invoked, then you should see a block of code that starts like the following:
```
   <%sub displayURL(URL) 
   Dim AppServer, HTML
```
- If you specified to perform processing when a JavaServer Page is invoked, then you should see a block of code that starts like the following:
```
   <%{
   appserver.AppServer IappServer = new appserver.AppServer();
```
Save the Web page with an extension of .asp to test Active Server Page support and an extension of .jsp to test JavaServer Page support. Make sure that the extension you choose matches the processing mode you select on the Connection tab in the Properties dialog.
View the ASP or JSP in your Web browser. Make sure that the URL in the address or location line begins with http or else the page will not display properly. If the URL does not begin with http, then publish the page to your Web server.

If you see the same table that you saw in the static HTML page, then ASP and JSP support is properly enabled. If you do not see the same table displayed, then you might not have installed the Web server components properly. For information on installing the Web server components, see Web Server Components.