BusinessObjects Board

Dashboard not getting updated after a universe change SAP 4.

Hi guys

We currently have a Products dashboard which is based on a webi query (QAWBS) . The business recently added a new product code so I made a universe change to include the new product .

Now I checked the Webi query which is the source to the dashboard and its showing the new product. This product appears in the dropdown prompt when the query is run.

Now when I check my dashboard, it does not reflect the new product in the dropdown …

Any ideas why??


nutty (BOB member since 2015-10-19)

Is your connection set to refresh the WebI every time? When you look in the input values in the left column, is “refresh” set to true? What about “get latest instance”?

If you don’t set any of these options, the connection will return the values as of the last time you saved the report.


Lugh (BOB member since 2009-07-16)

Hi Lugh
How do I check the input values… You mean in the webi report? Sorry I am not much familiar with dashboards …


nutty (BOB member since 2015-10-19)

When you set up a connection in the dashboard, at the bottom of the first tab there are two lists of values. The left hand list is input values (data you send TO the WebI report), the right hand list is output values (data you receive FROM the WebI report).

The input values start with the obvious options, like login name, password, and prompt values. Below that you should have the options for “refresh” and “getfromlatestinstance”.


Lugh (BOB member since 2009-07-16)

Hi Lugh

Basically its a different issue all together which I just discovered. The dashboard was not getting updated because one of the scheduled report kept getting failed which I have rectified.

The main issue is when I open the Webi source query which has been published as a web service query for the dashboard in rich client, I get this error as the screenshot attached below.

Even when I go to ‘Manage server’ and try creating a new connection,I specify the host name and the URL gets generated , until I remove ‘80’ from /8080 in the url, green tick does not appear.

And when I try to point it to the new connection, I get the same error.

I even checked the data connections in the Dashboard designer and strange thing is both my pre-production and production dashboards are pointing to the Dev server location. I have checked the production dashboard and its displaying the production data but I cant understand why the URL is pointing to the Dev location.
Capture12.zip (21.0 KB)


nutty (BOB member since 2015-10-19)

Do you have a BO admin, or are you stuck with that role, too? If you have an admin, get them to make sure everything is set up correctly for the web service to be available. There are a bunch of little things that have to be checked, so I don’t want to go through them all here.

In the connection specification, there are two URLs. The first one is the WSDL. This is the URL you use to retrieve the web service definition, so that you can set up all the connection parameters. The second one is the Website URL. This is the URL that the connection uses to actually retrieve the data. When you initially create the connection, the Website URL is automatically filled in to match the WSDL URL. However, it doesn’t have to stay that way. When you move the dashboard from one environment to another, you need to update the Website URL to point to the correct server. Do not change the WSDL URL, because then you have to reconfigure all the connection information again.

The port keeps changing from 8080 to 80 because you are using http instead of https. I’m guessing you should change to https, since you almost definitely want your information to be encrypted.


Lugh (BOB member since 2009-07-16)

Hi Lugh
I am the one responsible for this too. This dashboard was developed by a different person previously who has now left.
The website URL looks like this:

/dswsbobje/qaawsservices/queryasaservice/biws?cuid=—authType=secEnterprise&locale=en&timeout=60&ConvertAnyType=true

What do I change in that?


nutty (BOB member since 2015-10-19)

You don’t change any of that part. All of that is automatically generated to call the right bit from BO.

You’ll need to read up on the documentation around exposing web services in your BO environment. Make sure that the web services on your production server can actually be reached.

Once you do that, you need to make sure all the connections in your dashboard are actually pointing to your production server. That involves changing the server name in the URL, the bit that comes before the bit you posted.


Lugh (BOB member since 2009-07-16)

Thanks Lugh
Does it mean my producton dashboard is using Dev web server but using the production universe and webi query to generate the content?

We are going to do a platform upgrade soon on Dev so thinking it might have an impact on our Production and Pre-production dashboard?


nutty (BOB member since 2015-10-19)

When you enter the URL into the WSDL URL parameter, the dashboard goes out at that time and retrieves the definition of the web service. It finds out what all the methods are, what filters can be applied, etc. This allows you to set up the connection.

If you migrate the web service from environment to environment properly, such that it retains the CUID, that definition doesn’t change. Hence, you do not need to update the WSDL.

When the dashboard actually runs, it doesn’t reference that WSDL URL at all. That job is long done. It references the Website URL instead. This is when it sends the current parameters (as set up in the input values column) and returns the data (as set up in the output values column). Because the definition of the web service is the same in both Dev and Prod, the structure of the parameters and return values matches what is expected.

Upgrading the Dev environment shouldn’t have any impact at all on the structure of the web services. However, you will definitely want to test the dashboard to make sure of that.


Lugh (BOB member since 2009-07-16)

Thanks Lugh
Yes we did a small test to check the dependency of the web server on Prod dashboard. We shut down Tomcat on Dev box and tested the prod Dashboard and as expected, the Dashboard stopped working…


nutty (BOB member since 2015-10-19)