Skip to Content
author's profile photo Former Member
Former Member

QAAWS does not work after upgrade to BOXI R3.1

We had BOXI R2 and Xcelsius 2008 and there were some refresh problem in Xcelsius which we understood would be fixed by upgrading to BOXI R3.1 fix pack 1.3. Therefore we have upgraded and one of the errors we have come across is that QAAWS no longer works, giving the following error:

java.lang.NullPointerException

The old queries would generate a URL that would show the WSDL, however if a new query is created the WSDL does not appear to be generated. Is this why QAAWS is not working or is there another reason?

Thanks for your help.

Jason

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Mar 18, 2009 at 01:31 PM

    In QaaWS, you should still see a URL generated for the web service. This is your WSDL URL. I'm running XI 3.1 and validated this yesterday.

    Have you tried re-creating the web service in QaaWS since the upgrade?

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 18, 2009 at 01:51 PM

    Brian,

    I have tried re-creating the web service for an exisiting query in QaaWS after the upgrade and the new WSDL does not appear to be created (i.e. the same problem as creating a brand new query).

    Regards

    Jason

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 18, 2009 at 02:22 PM

    Brian,

    I have the same view.

    In BOXI R2 if you took the the URL and pasted it into internet explorer you would see the WSDL. In BOXI 3.1 this does not occur. A list of newly define queries, or queries that have been re-run in BOXI 3.1 are displayed. The list contains links, but navigating using these links does not display the WSDL.

    I am not sure if not being able to see the WSDL is causing my problem but it would explain the 'null' error. I can also see that QAAWS now creates the URLs with a new format when compared to the BOXI R2 URLs, may be this is causing the problem?

    Regards

    Jason

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Jason,

      That URL should be used directly in Xcelsius. That IS your WSDL URL. I was able to use that URL in Xcelsius to produce a dashboard.

      You should be able to produce the same. I'm not familiar with any older versions of BOBJ / Xcelsius, so I may be missing the purpose of your question.

      Hope that helps!

      /Brian

  • author's profile photo Former Member
    Former Member
    Posted on Mar 18, 2009 at 02:52 PM

    Brian,

    I understand that the URL provides a link to the WSDL, which then can be used within Xcelsius, but unfortunately when I use one of the new URLs within Xcelsius to try and 'Import' (using the data manager) I get an 'Unable to load URL' message. Hence my comments about the WSDL not being displayed and new URL format possibly causing the problems with the new and old queries?

    Thanks for your help

    Jason

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.