Skip to end of metadata
Go to start of metadata

Product versions:
Xcelsius 2008
BusinessObjects Enterprise XI 3.1 SP3

Table of contents

This article is part of a series


This article explains the detailed steps to activate the Xcelsius servers after the Service Pack 3 for BusinessObjects Enterprise XI 3.1 is installed. As mentioned in this article, the servers are not enabled by default to avoid confusion with customers who are not using Xcelsius. Therefore the configuration requires a few manual steps that are explained here.
Two important facts :

  • No dashboard migration is required
  • Activation is done from BOE server after the SP3 installation

No dashboard migration is required

Which ever upgrade path you followed, you decide on the server side to enable the Xcelsius servers or not. The switch is on the server side (BOE) and is totally transparent for the dashboard(s). The QaaWS WSDL interface remains the same, so you do not have to re-publish your Web Service and update the dashboard.
As long as the dashboard can run against your BOE XI 3.1 (any version prior to SP3), it will run as is against the SP3. You do not have to re-publish it from Xcelsius Designer, and you do not have to update it with Xcelsius 2008 SP3.

Activation on BOE after the SP3 installation

XI 3.1 SP3 comes in 2 possible formats : a full install (new landscapes) and a patch install (existing landscapes). Both will install all the necessary files on the server. Neither will not pre-configure new Xcelsius servers. Hence, you will not see the Xcelsius servers from the CMC right after the installer run. This is to avoid confusion with administrators who are not familiar with Xcelsius and/or want to keep the impact of a Service Pack upgrade as low as possible.

Once the installation is completed, 3 steps are required for a patch install scenario, and only 2 steps for a full install.

  1. (skip if you ran a full install) run the following command line on each machine that may host an Xcelsius server to activate the new server types
    "INSTALLDIR\BusinessObjects Enterprise 12.0\win32_x86\scripts\AddNode.bat" -name NODENAME -update -cms cmsName:cmsPort
    -user Administrator -password Password123
    NODENAME is the name of the Server Intelligence Agent (can be obtained from the Central Configuration Manager)
    Run it with administrative privileges on Windows Vista, 2008 or 7
    INSTALLDIR/....bobje/ -name NODENAME -update -cms cmsName:cmsPort -user Administrator -password Password123
  2. add the new Xcelsius servers from the Central Management Console (CMC)
  3. configure the Query As A Web Service end point within the dswsbobje web application
    open DSWSBOBJE_INSTALLDIR/WEB-INF/web.xml file and add these lines
            <description>Qaaws Runtime Query Accelerator</description>

After a restart of the dswsbobje web application and a start up of the 2 Xcelsius servers, all QaaWS queries will be redirected to those new servers. You do not need to restart the entire BOE cluster.

  • No labels


  1. Unknown User (b0ge8nj)

    After performing the steps to enable Xcelsius, I'm getting "org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found" when verifying the service using http://server:8080/dswsbobje/services/Session.&nbsp; Any suggestions?

  2. It beats me, why those Services are not ACTIVATED/CONFIGURED by default. With the same reasoning one could argue, that new functionality will not be activated by default (such as Input controls for Webi) to not confuse the users...

    I hope that this issue will be solved with the upcoming SPs.

  3. Hello guys,

    after performing step 2 +3 and verifying the service using http://server:port/dswsbobje/services/Session.&nbsp i get the following message:

    "Please enable REST support in WEB-INF/conf/axis2.xml and WEB-INF/web.xml" is this a final test or are there any other test cases.

    Thx Martin

  4. Unknown User (d6gucpv)

    How much activity (CPU and Memory) should we notice when refershing against QaaWS post implementing steps above?  I followed the steps above and retarted Tomcat, yet when I refresh using QaaWS...I see zero activity associated with xcproc, xccache.exe or java.exe