IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for Watson Supply Chain solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Submit ideas for other Watson Customer Engagement Products:

Watson Marketing
Watson Campaign Automation
Watson Commerce

The ability to use troubleshooter for resending AS2 failures when failure is due to network outages

If 100 DirectAS2SendSyncMDN BP fail due to network outage at the moment there is no easy way to resubmit them.IBM support wrote:

The troubleshooter doesn't display the failures of DirectAS2SendSyncMDN because of the default onfault in the Business Procees, the Business Process will be completed with Errors. The Troubleshooter displays the processes which are either Halted or Interrupted Business Processes.

 

They have recommended few things in order to get the the failures under Troubleshooter. i.e. to create a custom Business Process with an intelligence to kick the onfault only in case of only successful retries and not failure retries. In this case, if there is a successful retry the onfault gets kicked off and business process will be completed successfully though the entry is red. If there is a failure retry or just a failure for any other reason, the onfault doesn't get kicked at all and the process will be available in halted mode and can be accessed through troubleshooter."

 

 I wrote back

This is not a good answer as if 100 BP failed and need to be restarted this "Other option would be to do it manually by using EDIINT Search screen and find the pending and failure entries for that relationship, collect all the BP Id's and use controllerworkflow to restart each ID or use the UI to do the same." would take a lot of time

And writting a BP like this "to create a custom Business Process with an intelligence to kick the onfault only in case of only successful retries and not failure retries. In this case, if there is a successful retry the onfault gets kicked off and business process will be completed successfully though the entry is red. If there is a failure retry or just a failure for any other reason, the onfault doesn't get kicked at all and the process will be available in halted mode and can be accessed through troubleshooter."

This is what IBM should do because I can't be the only customer that occassionaly has to resend 100 AS2 failures that originally failed due to a network outage

 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 10 2018
  • Needs review
How will this idea be used?

Resending document with the BP DirectAS2SendSyncMDN when many have failed due to network outage.

When network is back via the troubleshooter they can be selected and resumed or restarted and therefore easily resent

What is your industry? Life Sciences
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 25, 2018 09:08

    Update

    BTW if this ./ControllerWorkFlow.sh -e I N DirectAS2SendSyncMDN T "09/24/2018 4:55:00 AM" "08/24/2018 5:13:00 PM" functionality was added to the troubleshooter or in parallel to the troubleshooter then that would be a solution to this issue

     

    I had a router failure that resulted in 85 DirectAS2SendSyncMDN BPs failing .. Fortunately I found out about the above command which I had to run in Linux , but not all customers would know about this and it seems to me that it should be part of the SI UI