Hi friends,
Is there any sequence to start WM8 components. or we can start without sequence.
normally, I start in following sequence.
IS, Browker, MWS, then Analytical engine, Prediction Engine, Data Collector
Is there any best practice to start all components sequence wise.
Thanks,
Sha
You are in the right path…Its beetter follow the same sequence you did…as always IS first…
IS, Broker, MWS and then its components (ofcourse make sure DB also running)
HTH,
RMG
I usually start with Broker first, since it doesn’t depends on anything and a lot of components depends on it including IS. Then IS > MWS > the rest…
Thanks for sharing your thoughts!..
Usually in my experience IS should start first and then Broker->MWS other routines which ever works with out any issues:
I would start with Broker, as IS depends heavily on it and tries to sync to Broker in startup. Starting IS after the Broker I experienced problems (at least with previous WM versions including 7.1.2). Usually I do
Broker, MWS, IS, AE, DC, PE
Shutdown the other way round.
Thanks for sharing your thoughts!..May be I didn’t faced any issues that’s why: will follow your advices next time!
Happy Thanksgiving!
-RMG
I think the fact that there’s no issue when starting IS first is because the IS usually take a little while to get to the point it needs Broker connectivity.
If the Broker server didn’t take that long to get started after the IS, it usually start up and running almost instantly due to the OS specific code base nature.
In the end I guess is the usual case of whatever works for you. 
We just found that some IS packages do NOT get initialize properly if Broker is not up first.
I had always heard (and read) IS->Broker->MWS, but why IS before Broker? As someone noted, Broker has no dependencies (and we just learned IS does…)
Once IS has been configured with Broker server connection, it become a client of it.
Therefore it creates a reason to start Broker server before IS.
As v8 mentioned, it may not hurt to start IS first and Broker afterwards if Broker comes up fast enough and IS slow enough. But imho there is no reasen to start Broker not first. In contrary as most components are clients to the Broker, Broker should start first, so clients can connect.
Nevertheless the standard components should be able to recover if Broker comes up later, because that’s nearly the same behviour like an outage or failover of the Broker. If you have packages which do not load properly without Broker, you may check the reason for this and correct it to avoid problems in failover scenarios.
Agreed with you all…
Broker–>IS–rest of components will flow…
I usually follow the sequence below:
Broker > IS > Analytic Eng > Prediction Eng > Data Collector > MWS
The reason for starting MWS lastly is just to avoid having users hitting any page requiring the AE to be running, and then receiving an error message requiring them to contact the System Administrator.