I don't think that Java dump tells us anything... Whenever you get a "CA Clarity PPM :: Error 500 - Internal Server Error" that just means "something has gone wrong" and you need to go look in the app_niku.log on the server (or thru the NSA) to get the real error message. .. Note that If the "write" was generating a sensible error message (like you've not used the correct login credentials, or your XML is missing something mandatory), then you do normally get a sensible error returned in the XML from the call (so your calling client can trap this and handle it). What you have with that java dump looks a bit more serious than that. When I'm trying to develop code to write things thru XOG I will usually read it first from the application and write back exactly the same information (just to prove everything that is non-XOG is working OK)... then I'll start to change the information that I'm writing as I need to.... Is the stuff between your tags in the above looking like the same XML you get when you read skills out of the system (it looks ok to me based on the example skills write XOG files)? If so then the problem is probaby not in the XOG bit of the XML, maybe elsewhere in the XML call to the webservice??? Useful to know whats in the app_niku.log though.... -- Anyway, your original question was about READING data from Clarity not writing it, I've solved that one! :-)