Hello WSRR community. I'm using a Manual SOAP Endpoint object to add new Available Endpoints to an SLD without having to upload a new WSDL document. This achieves what we need when we query the new information through the REST API; however, if we are relying upon DataPower's (firmware v5.0.1) built-in WSRR objects (Saved Search Subscription or Subscription Object) it only sees the original URL that was in the uploaded WSDL. My understanding is that these DataPower objects only look at WSDL Document objects; so, this makes sense.
My question is this. Is there a way using the out of the box WSRR Subscription objects to pull down a WSDL Document that references the URL (in the Services section) that contains the URL that was added as a Manual SOAP Endpoint? Or, is the only way to accomplish this by upload a WSDL with the desired URL?
This topic has been locked.
1 reply Latest Post - 2013-01-03T21:58:03Z by venkatghatti
Pinned topic Manual SOAP Endpoints and DataPower WSRR Subscription objects....
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-03T21:58:03Z at 2013-01-03T21:58:03Z by venkatghatti
venkatghatti 06000213QE1 PostACCEPTED ANSWER
Re: Manual SOAP Endpoints and DataPower WSRR Subscription objects....2013-01-03T21:58:03Z in response to SystemAdminHi,
I guess the manual endpoint model is not supported yet by other Websphere Tools. I have noticed the same behavior in the case of Websphere Message Broker v8. WSRR Endpoint Lookup primitive does not works with manual endpoints. We have to rely on 'Registry Lookup' to fetch manual endpoints.