Recycle both processes after making a change?

[Peter Heggie]

If an interface consists of a source thread in a source process and a destination thread in a destination process, do we need to restart the destination process if we make a change in a filter or translate or inbound tcl in the source process?

The reason I am asking is because we have a main HIS inbound thread in a process that also contains some of the destination threads. I want to move the destination threads to an ancillary-specific process, leaving only the inbound thread in the inbound process. And when a component of the inbound thread is changed, I don’t want to have to restart any of the destination processes.

Peter Heggie
PeterHeggie@crouse.org

Topic

[Jim Kosloskey]

Peter,

I am not sure of the answer if you are using cross-process routing since we don’t use that here very much.

If you are using localhost threads in between the processes then I believe you only need to cycle the ‘Source’ process.

Mostly we do what you describe with sites and then the answer is just the Source Site Process.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Kevin Crist]

From my experiences we only have to restart the source process.

[Max Drown (Infor)]

Peter, you just have to bounce the process where the code resides. When a process is bounced, it loads all of the scripts, xlates, etc. into memory. So, when you change the files, the memory needs to be refreshed with the change.

-- Max Drown (Infor)

[Peter Heggie]

thanks Max – that makes sense. With queueing mechansisms between threads, I expected them to be isolated from each other.

Peter Heggie
PeterHeggie@crouse.org

[Author]

Replies