Latest post Thu, Oct 26 2017 9:51 PM by AndrewMoore. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • Wed, Jul 9 2014 9:23 PM

    iNEWS Web Service - Callbacks from Notification Service

    Having a few problems in receiving callbacks to the Notification Service.

    Can anyone help with the following queries?

    1) We are not clear if serviceUrl should contain the URL with the WSDL or not (we have tried both).

    e.g.

        "http://inewswebserver/notification-service" or

        "http://inewswebserver/notification-service?wsdl"

    Can anyone confirm the format of the service URL "http://inewswebserver/notification-service?wsdl" is correct?

     

    2) We've seen requests back, but only some periodically and only simple GET requests for the path we have registered and on one occation for "http://inewswebserver/notification-service?xsd=1".

    To help troubleshoot, we've been monitoring all incoming packets, but we're not sure why we've only seen request sometimes after triggering a change. Would it be possible to provide clarification on why we might be seeing this behaviour?

     

    3) We are not clear if it's okay disconnect after calling watchQueueForChanges.

    Can you confirm if we do disconnect immediately after will we still continue to receive callbacks to the webservice we have registered - or will we need to stay connected (with an active session) - to keep receiving notifications? 

     

     

    4) Please can someone provide us with a way to view information about why our service is not being called back (e.g. errors in the WSDL) or be available for a conference call tomorrow to discuss and provide the necessary detail?

     

    Thanks for any assistance.

  • Thu, Jul 10 2014 1:08 PM In reply to

    • fiatala
    • Not Ranked
    • Joined on Fri, Jun 7 2013
    • Posts 16
    • Points 165

    Re: iNEWS Web Service - Callbacks from Notification Service

     

    1 - Include the WSDL: http://inewswebserver/notification-service?wsdl

    2 - The expectation is for the callback to fire every time something in the watched queue is modified or when search results are available. The iNEWS WSAPI-side client to your notification service is instantiated at first attempted use (first story update/search result). I believe it is retained until the iNEWS session is terminated or possibly when the socket times out, but it's possible that it's disposed immediately after use. Specifics can be investigated further as needed.

    3 - Do not disconnect. The pool of queues being watched is purged at disconnect. The next time you connect you will have an empty watch pool and you will also revert to the default update polling behavior.

    4 - Discussed via e-mail.

     

  • Thu, Oct 26 2017 9:51 PM In reply to

    Re: iNEWS Web Service - Callbacks from Notification Service

    I know this thread is old but I was having the same results as issue #2. 

    carlp_online:

    2) We've seen requests back, but only some periodically and only simple GET requests for the path we have registered and on one occation for "http://inewswebserver/notification-service?xsd=1".

    To help troubleshoot, we've been monitoring all incoming packets, but we're not sure why we've only seen request sometimes after triggering a change. Would it be possible to provide clarification on why we might be seeing this behaviour?

    I was getting GET calls for the WSDL then the referenced XSD types. Once the server gets a valid copy of both those files it will do a POST with the queue that has changes. My issue was the paths for the WSDL and related XSD were giving the server 404 so it would never POST. Its now working as expected.

Page 1 of 1 (3 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller