Example: Adding SAS Web Report Studio :: SAS(R) 9.3 Intelligence Platform: Web Application Administration Guide, Third Edition

Overview

This example uses the instructions from Adding Custom Web Applications in order to illustrate how you might add SAS Web Report Studio to the SAS Information Delivery Portal. When you follow the instructions that are provided here, you will implement either or both of these as stand-alone applications that have the following characteristics:

Authorized users can access the SAS Web applications that you add to the portal without an additional prompt for their logon credentials. Applications that support single sign-on have the following characteristics:

invoked from the portal, but executed remotely
support single sign-on
use Metadata Server authentication
use the SAS Foundation Services API

The following sections describe these steps to add SAS Web Report Studio to the SAS Information Delivery Portal. If you want to add one or the other application, but not both, follow the instructions only for the application that you want to add.

Step 1: Design and Code the Web Application

You do not need to perform this step when you add SAS Web Report Studio. By default, SAS Web Report Studio is designed to support single sign-on invocation, and do not require additional code.

Step 2: Deploy the Web Application to the Web Application Server

If you have already installed and configured SAS Web Report Studio, their enterprise archive (EAR) files should be deployed into the Web application server.

If you have not installed the applications, you can do so by using the SAS Deployment Wizard. You can also manually configure and deploy the applications.

The EAR files that should be deployed are located in the SAS-configuration-directory\Lev1\Web\Staging directory.

Step 3: Ensure That the Appropriate Group Metadata Exists in the SAS Metadata Repository

If you have administrative permissions, you can share a Web application with a user group that is defined in SAS metadata. You can share pages with any of the following groups:

a PUBLIC group, which contains all portal users. It is convenient to share pages with the PUBLIC group because all users in that group, by default, have access to the Web applications
Portal Web Report Studio Users

For details about defining groups, see “User Administration” in the SAS Intelligence Platform: Security Administration Guide.

Step 4: Add the Application's Metadata to the SAS Metadata Repository

There are two ways to define a Web application in metadata:

Create the Web application in the SAS Information Delivery portal
Create the Web application by running a SAS program

To run the SAS program, follow these steps:

Make a backup copy of the SAS program LoadWebApplicationExample.sas, which is located in the SAS-configuration-directory\Lev1\Web\Applications\SASPortal4.3\sasJobs directory.
In LoadWebApplicationExample.sas, specify the following application-specific variables for either SAS Web Report Studio:
```
%let groupOrUserName=PUBLIC;
%let identityType=IdentityGroup
%let webappName=SAS Web Report Studio;
%let webappDescription=The SAS Web Report Studio Web application;
%let webappURI=/SASWebReportStudio/logonFromPortal.do;
```
Notes:
- In this example, webappURI is specified as a relative location within your Web application server. For example, if SAS Web Report Studio if installed on JBoss, the line %let webappURI=/SASWebReportStudio/logonFromPortal.do; would be resolved to:
  http://<PortalJBOSSHost>:8080/SASWebReportStudio/ logonFromPortal.do
  
  If SAS Web Report Studio were installed on a remote system instead, you would specify the location as a fully qualified URL that includes the remote host and port, such as:
  %let webappURI=http://<remotePortalJBOSSHost>:8090/ SASWebReportStudio/logonFromPortal.do
- For complete descriptions of the variables in LoadWebApplicationExample.sas, see Adding Custom Web Applications .
Save your changes and run the LoadWebApplicationExample.sas program.
If applicable, repeat these steps a second time.

Step 5: Implement Authorization (Access Control) for the Web Application

If you have correctly installed and configured SAS Web Report Studio, no additional steps are required for access control.

Note: When you implement authorization, access to content is controlled only from within the SAS Information Delivery Portal. Users outside of the portal can use the Web application's URL to access the Web application.

For general information about access control, see Understanding Portal Authorization.

Step 6: Make the Web Application Available in the Portal

When you share a Web application with a group, the Web application becomes available to members of that group. Members can search for and add the Web application to their collection portlets.

You have other options for making your application appear in the SAS Information Delivery Portal:

You can edit a collection portlet in order to add the Web application to the portlet. You can share the portlet with a group, including the PUBLIC group. Group members can search for and add the portlet to their pages.
After adding the Web application to a portlet, you can add the portlet to a page that has been shared or that you intend to share with a group.

Although the portal administrator can edit any portlet or page in the portal, this is not a good practice. The group content administrator should edit the portal content. If you logged on as a group content administrator, you can edit only portlets and pages that you have created, or portlets and pages that have already been shared with the group for which you are administrator.

Note: All portal users can create and add Web applications to their collection portlets. Only users who are authorized as a content administrator for a group can share a Web application with the group, or can edit a shared Web application.

For instructions about adding or sharing portlets and pages, see the online Help that is provided with the portal.

Step 7: Update or Remove the Web Application

After you have created a Web application, you can edit it, remove it from a portlet, and delete it permanently from metadata. You can edit or delete any Web application that exists in metadata (including Web applications that were created by running LoadWebApplicationExample.sas).

Any changes that you make to a shared Web application are seen by all users who can access the Web application. If you permanently delete a shared Web application, the Web application is removed from all portal views.

For instructions about editing, removing, or permanently deleting a Web application, see the online Help that is provided with the portal.