on 09-20-2013 3:16 PM
Hello Halsen,
There are some bugs with this functionality which have been resolved with the newer SP releases (SP07 on). See the notes below for more details:
1) 1897804 Disabled buttons in NWA Channel Monitor
2) 1902810 Disabled buttons for channel in Administrative Error status
As a workaround, you can use the old functionality in the Runtime Workbench (http://<server>:<port>/rwb).
Regards
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark Smyth,
The old functionality of Runtime Workbench is working fine. I'll ask for Basis team to apply the SP07 on PI 7.31. So I will post the result here.
Regards,
Halsen
Hi Halsen Nagasawa,
The communication Channel is functioning correctly.when you hit the stop button only then you will be able to see the start button.
Thanks,
Ankit Baid
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ankit Baid,
The first screenshot is the channel working after be created, then I pressed the "stop" button and the Start do not become active (second screenshot).
Regards
Halsen Nagasawa
Hello Halsen,
As I can see from the screenshot you provided, the communication channel is already successfully started. Since the channel is started, the button 'Start' is inactivate (it is not possible to start the channel when it is already started, correct?) and the button 'Stop' is active. If the channel would have been stopped, you would be able to observe the opposite behavior: the button 'Stop' would be inactivate and the button 'Start' - active.
The exception here is if you would have enabled external control for the communication channel: in this case both buttons 'Start' and 'Stop' will be inactivate - since starting and stopping of the channel is considered to be managed from external applications.
Regards,
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Halsen,
try to clear the cache.
--> close the communication channel monitoring and open again.
--> if you are facing the same issue. try to restart the server.
sometimes it will work.
Regards
Bhargava krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.