Skip to main content
Mitratech Success Center

Deploying BOSS XI and Configuring URLs

This section describes the requirements for deploying BOSSXI.war for Business Objects Single Sign-on (BOSS), and how to verify that it is deployed successfully.

It also describes how to construct URLs to access the main Business Objects login page and to Business Objects documents (reports). These conventions can be used when defining URLs, for example, in a TeamConnect portal pane on a home page.

For more information about supported platforms for deploying a custom Business Objects application such as BOSS, see the Business Objects documentation.

For more information about how to deploy an application on your application server, see the vendor's documentation.

Support for Business Objects XI

Business Objects XI is supported for single sign-on (BOSS) with TeamConnect 5.1. BOSS has been certified using WebSphere, Apache Tomcat and WebLogic to deploy BOSSXI.war as an application.

Since BOSS is delivered as a J2EE application, you must deploy it as such on an application server. BOSS cannot be deployed on IIS.

Requirements for Deploying BOSSXI.war

  • BOSSXI.war for Business Objects XI does not have to be deployed on a Business Objects node. You must simply deploy it on your application server.
  • Both the Business Objects server and the application server must be on the same domain (for example,
  • If BOSS and Business Objects are deployed on the same machine, then it is not required to have a domain name in the Cookie Domain field of Business Objects WebIntelligence Settings in TeamConnect's system settings screen. Also, URLs to BOSS do not need to include a fully qualified domain name. You can simply specify the machine name in the URL.
  • From the file for Business Objects, you must set the trusted.auth.user.retrieval variable to WEB_SESSION.
  • Once you have verified that BOSS has been deployed successfully, you must configure the Business Objects WebIntelligence Settings in TeamConnect's System Settings on the Admin menu. For details, see BusinessObjects WebIntelligence Single Sign-on, provided on your 5.1 installation media.

Verifying Successful BOSS Deployment

To verify whether BOSSXI.war is deployed successfully, open a browser window and type in the following URL. Replace the properties in brackets with the application's property values:


If you see the page below, then BOSSXI.war has deployed successfully.


Constructing URLs to Business Objects Pages

When providing URLs to end users so that they can access Business Objects documents through TeamConnect (for example, in a portal pane on their home page), you must construct the URLs as described in "OpenDocument Parameters" in the BusinessObjects Enterprise XI Release 2 .NET SDK or Java SDK. This information can be accessed at one of the following locations:

The following examples can help you construct the proper URLs. Note that if BOSS is not deployed on a Business Objects node, then the <hostname> must include the fully qualified domain name of the server.

Caution: Do not use a token in your URL. This will invalidate the link .

For details about adding Business Objects URLs to TeamConnect portal panes, see Adding WebIntelligence URLs.

URLs When Business Objects Deployed on IIS

The following are examples of valid URL construction when the Business Objects server is deployed on IIS.

  • URL to Business Objects server main login page:
  • Example URL to Business Objects document:
    http://<hostname:port>/businessobjects/enterprise115/InfoView/scripts/ opendocument.aspx?sType=wid&iDocId=2179
URLs When Business Objects Deployed as J2EE Application

The following are examples of valid URL construction when the Business Objects server is deployed on your application server.

  • URL to Business Objects server main login page:
    http://<hostname:port>/businessobjects/enterprise115/desktoplaunch/InfoView/ main/main.jsp
  • Example URL to a Business Objects document:
    http://<hostname:port>/businessobjects/enterprise115/desktoplaunch/opendoc/ openDocument.jsp? sDocName=T21CUN03_Case_Aging_1st_party&sType=rpt&sKind=FullClient
  • Was this article helpful?