Change view of threads

This topic has 3 replies, 3 voices, and was last updated 11 years, 2 months ago by Mark Thompson.

Creator

Topic
May 15, 2014 at 2:42 pm #54210
Jim
Participant
The interface team is developing new interfaces almost daily and we have numerous development sites in varying stages and all are being fed data from differing sources. We would like to be able to configure a process during development from sending messages to other defined routes. This would prevent the recovery databases from filling up with useless messages that have to be manually cleared.

Does anybody know of a way to accomplish this without having to remove the threads not being developed?

Thank you,

Jim
Creator

Topic

Viewing 2 reply threads

Author

Replies
- May 15, 2014 at 2:50 pm #80610
  Kevin Crist
  Participant
  If we have threads like this we usually just put in the generic hcitpsmsgkill. We have a lot of applications that don’t have test systems so we kill those so they dont just sit in the recovery database.
- May 16, 2014 at 12:36 pm #80611
  Jim
  Participant
  Thanks Kevin but I was looking to not modiy 10-30 threads per developmnet site. I was thinking of something similar to the change view option where I could select the threads where I don’t want to send messages.
  
  Jim
- May 16, 2014 at 1:26 pm #80612
  Mark Thompson
  Participant
  Jim
  
  Check out the little known and even less used feature called “Forwarding”.
  
  Create a single bit_bucket thread. For each thread where you want to kill messages, put the bit_bucket thread in NetConfig (Outbound Tab) Forward Thread field. In NetMonitor you can Start Forward and Stop Forward on each thread.
  
  Switching for each forwarded thread can be scripted using something like:
  
  hcicmd -p processname -c “threadname1 fwd_start”
  
  hcicmd -p processname -c “threadname2 fwd_start”
  
  - Mark Thompson
  HealthPartners
Author

Replies

Viewing 2 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.