How to deploy Qaaws queries and Xcelsius in multi server architecture

[Former Member]

Hi Experts ,

I have developed a very good looking dashboard which uses qaaws queries (Dev ) to get the data in to it . I have deployed these qaaws queries to another server (UAT ) using deploy option in Query as a Web service . But still the webservice URL pointing to my DEV server .

Also , I saved my xcelsisu file to the BO platform (in DEV) and then I imported this file in to my UAT server using import wizard . Now I opened this xcelsius file in the UAT server . In datamanager , Still I can see my webservice URL's pointing to DEV server .

How can I deploy Qaaws and Xcelsius in a mult server Architecture . We have different servers for each environment ( Dev, INT,UAT , PRD )

Need some one help to getout of this problem .

Please note that my output of Xcelsius is in PDF file .

Many thanks in advance.

Regards,

Dirasa

[Former Member]

The solution that we've come up for this same exact situation is just how Bruce explained it. We migrated the QaaWs and Xcelsius dashboard to our QA server (from Dev).

From there QaaWs designer, we would simply re-edit the QaaWs, and a message would pop up alerting us that the current QaaWs was pointing to the Dev servers still, and would ask if you want to keep this QaaWs pointing to Dev. Once you click No, and just re-publish the QaaWs, the WSDL URL will change and point to the new server.

As for the Xcelsius, it is exactly how Bruce explained it, once you remove the static reference to a particular BO server, the dashboard will look for the QaaWs in its current BO environment.

So when moving Xcelsius Dashboards leveraging QaaWs, all you have to do is re-publish the QaaWs (assuming that you've changed ur Universe Connection too).

[Former Member]

You can also try the Life Cycle Manger to move QaaWS from one server to another server. I have seen that's the easiest way to transport from one box to another.

Since you are trying to deliver the dashboards in pdf file, I believe you should maintain the full path of the QaaWS in the flash file.

Anil

[Former Member]

There are several options, and an approach to make the QaaWS services environment independent

1. When you use the QaaWS clinet builder and use the option to Copy to another server, you'll need to select the Advanced Parameters button on the 1st screen and change the server environment referernce.

2. QaaWS services can be captured adn moved with the import wizard and Bair files. You may want to consider this option if you also want to capture adn contriol the QaaWS defintions for change,manangement, release management and source code control and rollback. Moving to an new BusinessObjects environment with Import wizard may require changnig the server environment reference with the AqqWS client connected to the target environement after it is moved.

We have found an approach to make the QaaWS data connections in Xcelsius BO environment indendent and relatively referenced, so when you move Xcelsius dashboards sourced with QaaWS between BO environements you don't need to redefine the data connection in Xcelsius

In Xcelsius data connections, after you paste the QaaWS WSDL on the definition tab, and import the Web Service URL field is populated with a full web service URL path http://BusinessObjectsServer/dswsbobje/qaawsservices/queryasaservice

We have found the after the import you can edit the web service URL and remove the BO server reference at the beginning and start it with /dswsbobje/qaawsservices/queryasaservice .

Xcelsius dashboards in the BOE with QaaWS data connections still works to supply data to the dashboard. When the dashboard run the BOE must assume that without an explict server reference, that it must be the current BO environment. Another advantage of this approach is it avoids the need for a crossdomain.XML file on the BO web server.

[Former Member]

Hi,

I think you created a QAAWS based on a universe. In universe clickon the parameters icon. In this change the connection settngs from your develeopment to production connection. save and export the universe.

This will make the QAAWS to point to the production query.

Hope this helps.

uma