Deploy/ Undeploy ISD - what really happens under the covers?
Posted: Thu Feb 02, 2017 2:10 pm
Ok so I've scrubbed the IBM docs before coming here to ask, in my opinion some form of this should be documented, if it is please point me there. Here goes:
I get it when ISD applications are deployed, The services are generated along with additional artifacts, depending on the binding that was selected. and picked up by WAS to run. What I am wonder is what happens when the applications UNdeployed? are the services simply run down? and when the the app is re-deployed, does it just update the services that were there already and re-start them?
On a related note, since the docs don't really give you a good idea on how to wind everything down and spin it back up in terms of the sequencing, I'll take a stab at it and please course correct me as required:
Shutdown sequence for a given app:
1. disable the information providers (in this case DataStage jobs) for a given app you are about to undeploy (which if it's DataStage the always running jobs should stop running verifiable in Director).
2. undeploy the application
Startup sequence for a given app:
1. deploy the application (if new services created they get deployed)
2. enable the information providers for the given app you just (re)deployed (which if it's DataStage the always running jobs should now be running verifiable in Director).
DataStage Engine re-cycle:
1. disable the information providers (jobs) so the jobs stop running
2. DataStage engine is shutdown and re-started
3. enable the information providers (jobs) so the jobs start running
Information Server recycle:
1. disable the information providers (jobs) so the jobs stop running
2. re-start information server via the standard shutdown sequence which is DSEngine first, ASB agents next, WAS third, and the Repo tier if required. Restart, sequence is reverse of what I just described.
3. ISD and it's apps and services should all be running automatically after the IS restart, no need to manually enable information providers?
TIA,
ff
I get it when ISD applications are deployed, The services are generated along with additional artifacts, depending on the binding that was selected. and picked up by WAS to run. What I am wonder is what happens when the applications UNdeployed? are the services simply run down? and when the the app is re-deployed, does it just update the services that were there already and re-start them?
On a related note, since the docs don't really give you a good idea on how to wind everything down and spin it back up in terms of the sequencing, I'll take a stab at it and please course correct me as required:
Shutdown sequence for a given app:
1. disable the information providers (in this case DataStage jobs) for a given app you are about to undeploy (which if it's DataStage the always running jobs should stop running verifiable in Director).
2. undeploy the application
Startup sequence for a given app:
1. deploy the application (if new services created they get deployed)
2. enable the information providers for the given app you just (re)deployed (which if it's DataStage the always running jobs should now be running verifiable in Director).
DataStage Engine re-cycle:
1. disable the information providers (jobs) so the jobs stop running
2. DataStage engine is shutdown and re-started
3. enable the information providers (jobs) so the jobs start running
Information Server recycle:
1. disable the information providers (jobs) so the jobs stop running
2. re-start information server via the standard shutdown sequence which is DSEngine first, ASB agents next, WAS third, and the Repo tier if required. Restart, sequence is reverse of what I just described.
3. ISD and it's apps and services should all be running automatically after the IS restart, no need to manually enable information providers?
TIA,
ff