Watson Supply Chain Ideas

Use this form to submit an idea for a new product feature. The product team will review your input and provide status updates as decisions are made regarding the request.

Before you submit a new idea, please view requests that have already been submitted. If your idea has already been submitted, you can add comments or vote on the existing idea, thereby indicating your agreement with the idea. We may use this information to help prioritize development of new features.

 

Submit ideas for Watson Marketing and Watson Commerce products

Adding in additional triggers for alt.comm.outbound

The idea behind this is to allow alt.comm.outbound to be triggered for other situations.  Such as TCP timeouts after a session had been initiated.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 10 2018
  • Declined
How will this idea be used?

A new parameter in the netmap entry can be used in a list format such as the ciphers are used to allow certain types of errors to trigger the alt.comm.outbound.

What is your industry? Government
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    Chris Sanders commented
    07 Sep 14:51

    Thank you for opening this enhancement request with IBM.  I have reviewed the request with my development team.  Given your use case we don't believe that an alt.comm.outbound change would provide the capability that you are seeking.  Since Sterling Secure Proxy is involved in this connection this capability would need to be handled in the SSP configuration instead of directly in C:D.  Because of that I will need to reject this request, but I would suggest opening an enhancement request with the SSP team to see if they might be able to meet your needs.  Thank you for taking the time to open this request and please don't hesitate to open a new one if you think of additional enhancements.


    Sincerely,

    Chris Sanders

    Connect:Direct Offering Manager

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    07 Sep 15:07

    The SSP is on the remote side.  Because they were having issues alt.comm.outbound was not triggered therefore we took a production outage.  This also would not pertain just to the remote node being a SSP.