Idea Delivered

Web UI Publish Queue - Delete multiple events

In the Web InfoShare, we need to be able to delete multiple stalled publish events. Currently, in TD 14 SP3, we can only select one event at the time. 

  1. Go to Event Log > Publish, and select Show Busy, for example.
  2. If multiple publications have failed these will be listed and will clog the view.
  3. Provide an option to do a multiple selection before you click Delete, or an advanced Delete 
Tatyana Morkot
Parents

  • Hi all,

    I hope I can give some quick background on the below helpful answers,

    Event Log by itself is a centralized 'logging' system, so on top of logging onto the file system in every server of your scaled out environment. This way many users (if not all users) get visibility on what is technically happening on the various servers. It is however still a logging system, some people see Event Log as "the queue" which is technically incorrect. Regarding clean up of busy events, please have a look at Standard SQL Server Database Job - RWS Documentation. Of course if you are automating publishing - and in turn cancelling - you can also automate the clean up of your event when cancelling using the API.

    "The queue" is called BackgroundTask but even then it is not a single queue. It is a complex matrix of small (executed in seconds) to large messages (taking 12+ hours to execute). Handlers, servers hosting handlers and grouping handlers to achieve fairness and throughput - even upon retries. Most handlers are fire-and-forget meaning that you cannot really stop them from executing (unless you use the operating system's process id to kill the process), upon several failures as configured in settings background task xml they will stop. Some handlers like "publish", have several check points to verify if the requested publish operation is not cancelled (so Cancel of a Publish of a PublicationOutput). See Admin.XMLBackgroundTaskConfiguration.xml - RWS Documentation or Background task component - RWS Documentation for more info

    -Dave

Comment

  • Hi all,

    I hope I can give some quick background on the below helpful answers,

    Event Log by itself is a centralized 'logging' system, so on top of logging onto the file system in every server of your scaled out environment. This way many users (if not all users) get visibility on what is technically happening on the various servers. It is however still a logging system, some people see Event Log as "the queue" which is technically incorrect. Regarding clean up of busy events, please have a look at Standard SQL Server Database Job - RWS Documentation. Of course if you are automating publishing - and in turn cancelling - you can also automate the clean up of your event when cancelling using the API.

    "The queue" is called BackgroundTask but even then it is not a single queue. It is a complex matrix of small (executed in seconds) to large messages (taking 12+ hours to execute). Handlers, servers hosting handlers and grouping handlers to achieve fairness and throughput - even upon retries. Most handlers are fire-and-forget meaning that you cannot really stop them from executing (unless you use the operating system's process id to kill the process), upon several failures as configured in settings background task xml they will stop. Some handlers like "publish", have several check points to verify if the requested publish operation is not cancelled (so Cancel of a Publish of a PublicationOutput). See Admin.XMLBackgroundTaskConfiguration.xml - RWS Documentation or Background task component - RWS Documentation for more info

    -Dave

Children
No Data