Skip to Content
As of now we have been Activating and Deactivating the Communication Channel from the IB Configuration for the Communication Channel to function.  Hence, the traditional way of doing it would have been IB Configuration -> Configuration Scenario -> Service/System -> Communication Channel.  Eg :  image So, every time a channel had to be Activated/Deactivated, even if just starting and stopping the channel would have proved efficient.  But now with the latest SP, this feature has been included in the Runtime Workbench.  The channels can directly be started or stopped from the RWB. There is no need for the channel to be Activted and Deactivated each and every time.  The biggest advantage of this would be, imagine you have placed a file a on the FTP Server with some polling interval and you do not delete the file, neither do you deactivate the the Channel from the IB configuration. This would keep polling the file and would overload the Server.  But now, just a simple Start/Stop button in the Communication Channel in RWB would prevent this. image Channels with Green LED indicate that the Channel is Active in the IB Configuration.  Channels with Yellow LED indicate that the Channel is Inactive in IB Configuration.
To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Yann L'Hénoret
    As my requirement is to activate/desactivate many communication channels several times a day, isn’t there any means of scheduling that part?

    Regards
    Yann

    (0) 
  2. Yann L'Hénoret
    Hi,

    This is an interesting feature, but isn’t there any means to schedule it, as it can become a nightmare when several communication channels are involved several times a day

    (0) 

Leave a Reply