Accessing 6.5 web service

Rhythmyx Technical Discussion
1

Hi There

I am trying to add a web reference in a .NET project to Rhythmyx, but I get the following error:

<?xml version=“1.0” encoding=“utf-8” ?>

  • <PSXLogErrorSet class=“Request handler not found” host=“uslcms01” port=“39992” protocol=“http” root="/Rhythmyx" rxroot=“http://uslcms01:39992/Rhythmyx”>
    <Error id=“0”>A handler could not be found to handle the request for (/Rhythmyx/WebServices/6.0.0/design/rhythmyx.wsdl) submitted by session id .</Error>
    </PSXLogErrorSet>

Note that Rhythmyx is running on an internal machine uslcms01 port 39992, and we can access the content explorer OK.

I am using this URL for the web reference

http://uslcms01:39992/Rhythmyx/WebServices/6.0.0/design/rhythmyx.wsdl

Thanks for any help

2

James,

You have the wrong URL for the WSDL. For the content service, your URL will be something like this:

http://10.10.10.103:9932/Rhythmyx/webservices/contentSOAP?wsdl

(I know that the Documentation is confusing: it’s talking about “File Locations” which are not the same as URLs).

In the currently shipping version (6.5) and perhaps some earlier versions, these URLs don’t work properly: This is a known bug and it will be fixed in 6.5.1.

3

Thanks for this David - Is there any way we can work around the issue - using the URL you suggested we get the following now - is this the known bug?:

AXIS error
Sorry, something seems to have gone wrong… here are the details:

Fault - makeTypeElement() was told to create a type “{urn:www.percussion.com/6.0.0/content}>PSKeyword”, with no containing element
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: makeTypeElement() was told to create a type “{urn:www.percussion.com/6.0.0/content}>PSKeyword”, with no containing element
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:USLCMS01

And finally the inevitable question - do you know when 6.5.1 will be available?

Thanks

4

Yes, that’s the known bug.

6.5.1 is due any day now. There are still a couple of bugs awaiting QA verification. Check back with Tech Support for an update.

Dave

5

We’ve upgraded to 6.5.1, but are still having some difficultiesa accessing the webservice. Looking at the content.wsdl file there seems to be no wsdl:service sections? Is this right?

Most of the examples I have looked at on the web include this section, and the code I am using at the moment to access contentSOAP?wsdl is complaining that there is no definitions/service node.

Any ideas?

Thanks

***** Actually I see they are in the rhythmyx.wsdl file, so perhaps the SOAP client is not processing the imports correctly.

6

When adding a web reference we get a list of methods, but the following error prevents us from adding the web reference:

The document was understood, but it could not be processed.

Any idea what could be wrong - should we just download the wsdl files and use them statically a la the loader example?

7

James,

I’ve not had a chance to look at this since 6.5.1 was released. However, we know that downloading the schemas / WSDL and adding them works, so I’d suggest you go that route for now.

Dave

8

I am having the exact same problem. Excuse my ignorance but how do you download the schemas / WSDL and add them?

Thanks,
Mike

9

Look at the /Rhythmyx/WebServices/6.0.0/design folder on the server (Note: this is a file location on the server, NOT a URL). It contains all of the files you will need.

Also, the “6.0.0” is the version of the API, not the version of the server implementation. Right now, there are no other API versions.

Dave

10

[QUOTE=dbenua;13917]Look at the /Rhythmyx/WebServices/6.0.0/design folder on the server (Note: this is a file location on the server, NOT a URL). It contains all of the files you will need.

Also, the “6.0.0” is the version of the API, not the version of the server implementation. Right now, there are no other API versions.

Dave[/QUOTE]

Dave,

After we download all the files, how exactly are we to use them/add them?

Thanks.