Controlled Shutdown

[garry r fisher]

Hi,

We don’t have anything like the number of interfaces that the American’s appear to have. A normal config for us would be 3 sites (test, development and production) with possibly 10 processes to a site.

The other day I had to shutdown all the interface cleanly and to do this I stop the inbound threads first, ensure all the backlogs are processed and then stop the process. This was quite long winded and I’m sure those of you with far more interfaces/processes than me know what i’m talking about.

So my question is – How do other people manage a controlled shutdown? Do you do it manually (as me) or do you have scripts and have clever do these scripts need to be?

Thanks

Garry

Topic

[James Cobane]

Garry,

One easy way to shutdown the interfaces easily is to set up a ‘view’ in Netmonitor that contains all of your inbounds, and then another that contains all of your outbounds.  Then you can easily shutdown all of the inbounds in ‘one-click’ by controlling them from the view; likewise you can then shutdown all of the outbounds when the recovery database is clear.

Hope this helps.

Jim Cobane

Henry Ford Health

[Jim Kosloskey]

Gary,

You could also set up ‘Groups’ in the NetConfig so that all of your inblund threads are in one group and all of your outbounds in another group.

You could also have groups related to specific integrations, applications, etc. because every thread can be amember of multiple groups.

Some folks to deploy scripts and I suspect they need to intelligent enough to know when the Recovery (and perhaps Error) DBs are clear enough to proceed.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[garry r fisher]

Hi Jim and Jim.

Thanks for the advise. That makes sense and I’ll give it a go.

Regards

Garry

[Author]

Replies