IBM Tivoli Enablement Tools
ITIM WS SOAP Response fails Validation
Hello, We are observing a similar issue as indicated by ggotti in the thread with title - Re: Web Services Wrappers for ITIM API. In our environment, we have an additional component that validates the SOAP response before passing it on to the Service Consumer. The intermediate component indicates that the SOAP response provided by ITIM for the login request is failing validation of the WSDL. To summarize the clientSession element of the loginResponse needs to be in the clientSession#http://model.ws.itim.ibm.com' instead of 'clientSession#http://services.ws.itim.ibm.com' Our environment versions are ITIM Web Services Wrapper version is: 1.32 Web Services build number is: 180 Web Services target type is: ITIM51 ITIM version is: 5.1 Detailed ITIM version info: ITIM Version: 5.1.0.4 ITIM Fixpack level: FP0004 ITIM Build number: 201009100615 ITIM Build date: September 10 2010 ITIM Build time: 06:15:48 EDT I noticed that our build number is 180. Tthe forum mentioned that if it is less than 189 then earlier verion is being used. As this is the case, can you please advise as to how we can obtain the latest build and the instructions to apply that build for our current version. Thanks in advance for your assistance.
Related Links
Comment and issues for the ITIM DocTool
ISIM Web Services -Single SIgn on
Working entry comming as null when AL is run
ITIM Adapter Development Tool - Loop Connector hasn\'t Hooks tab
Out of memory while running ITIMDocTool_HTML.sh
Webservice call from TDI via isim
ITIM- Java client not able to get the PlatformContext object using new InitialPlatformContext(env)
ITIM WS SOAP Response fails Validation
Custom adapter Test connection AL Error CTGIMT603E for webservice connection
Web Services Wrappers for ITIM API- New Application
Thread safety of client API
Webservices exception
Error while testing connection to ITIM Web Services v1.32
ISIM 6.0 webservice date issue
Web Services call to trigger Recon in TIM
Two loops in ITIM workflow are not working one by one