• Print |
• E-mail  |
• Bookmark

After you deploy the SAS^® BI Dashboard Web application to a separate instance of Tomcat than where the SAS^® Information Delivery Portal is deployed, the following error might occur in the browser:

HTTP Status 404 -/Portal

The requested resource (/Portal) is not available.

In addition, the Tomcat log might include the following error:

[main] INFO  com.sas.bi.dashboard.context.DashboardServices - Could not 
find TCPIPConnection for: BIP Service

These errors occur after you select the Edit Dashboard or the Manage Dashboard icons and you then click either Cancel, OK or <=Portal to return to the portal.

The problem occurs because the application uses the wrong URL to return to the portal. The Tomcat instance is using the host and port where SAS BI Dashboard is installed to invoke the portal rather than using the host and port where the portal is deployed.

The problem also occurs if the portal context name is changed from Portal to something other than that name. When such a name change is implemented, SAS BI Dashboard attempts to return to /Portal, and the attempt fails.

Select the Hot Fix tab in this note to access the hot fix for this issue.

After you apply the hot fix, complete the following steps so that the functionality works correctly:

1. Edit the BIDashboard.config file that is located in SAS-configuration-file\Lev1\SASBIDashboard.
2. If the portal context name has changed, add the following parameter at the bottom of the BIDashboard.config file:
   Portal.root=/new-portal-name/

In this parameter, new-portal-name specifies your site-specific portal context name.

3. If a separate instance of Tomcat is involved, include the complete URL in the parameter, as shown in this example:
Portal.root=http://host-name:port-number/new-portal-name

In this example, host-name, port-number, and new-portal-name specify your site-specific values.

4. Restart Tomcat.

Operating System and Release Information

A fix for this issue for SAS BI Dashboard 9.1.3 is available at: