I am new to Tridion docs and have a requirement to retrieve translation jobs and their associated metadata file. Does anyone have any examples of the best approach in Java?
I am new to Tridion docs and have a requirement to retrieve translation jobs and their associated metadata file. Does anyone have any examples of the best approach in Java?
Welcome Saul!
The generic answer is TD14SP1 - Using .SVC Web Service in Java
More potential help, requires more details? :-)
Best wishes,
Dave
Dave:
I am a contractor trying to build an application that will retrieve TranslationJobs. The version of Trdion Docs used by the client is:
SDL Tridion Docs - Content Manager - Build 13.0.4630.2
As for the Identity Provider, I believe it is ISHSTS.
I did try to generate the service in C# using the following command:
svcutil.exe https://xxx.sdlproducts.com/ISHWS/Wcf/API25/Application.svc?wsdl
Unfortunately, when I look at the app.config file, I see the following issue for the endpoint:
<endpoint address="">xxx.sdlproducts.com/.../Application.svc"
binding="customBinding" bindingConfiguration="CustomBinding_Application1"
contract="Application" name="CustomBinding_Application1" />
The contract attribute is invalid. The value 'Application' is invalid according to its datatype 'clientContractType'.
The enumeration constraint failed.
Saul
Thanks Saul...
I think regarding WS-Trust/WS-Federation security, that the Windows .NET world is easier to work with. You might find more information on how to do stuff in https://github.com/sdl/ISHRemote/tree/master/Source/ISHRemote/Trisoft.ISHRemote which is a C#-based PowerShell library on top of the ISHWS. The starting point is the New-IshSession cmdlet and in turn the IShSession object regarding authentication and proxies.
PS: It is up to you if you want to edit the URL in your code example as it is leaking a bit.
Thanks for your response. My preference is still to access SDL through Java if possible as all of our other products are Java based.
Dave:
Thanks for pointing out the URL issue. Can you explain why I am getting the error in the ApplicationService. Where is the clientCopntractType set?
Saul
Nevermind. I fixed the issue. Turns out I had a blank space.
It is still my preference to access SDL through Java whenever it is an option, especially given that all of our other products are Java-based.