nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Stopping TeamSite before an upgrade

brizrobbo

Hi Guys,

Here's a question which I have pondered often, but never had a definitive answer:

In all the doco I have read over the years, it never actually mentions that you should stop teamSite before you run an upgrade or a patch. It only ever mentions that you should re-boot the server after the upgrade has occurred.

I think it probably doesn't matter ... but what are your experiences? I always stop TeamSite/Apache/OpenDeploy before I upgrade, more out of habit (and good practice??) than anything else. Has anyone just applied the upgrade/patch on a running server?

Just a thought!

Cheers.

Find more posts tagged with

Comments

Pauliw

I believe, the upgrade or the patch would defenetly , stop or handle TeamSite / other services when ever required. It might have its reasons to keep the port alive or services up during the upgrade.

nipper

I usually do nto stop the services. The upgrade will do that for you. That being said, it never hurts to stop it yourself.

brizrobbo

Thanks for that. I have always stopped services before I have upgraded, so I never knew that the upgrade process itself would stop the services if they weren't stopped already. Good to know!

Nevertheless, I think the doco could be more explicit. Smiley Tongue

brizrobbo

Update:

I have just seen this in one of the TeamSite 8.0 install screens:

"It is strongly recommended that you keep all currently installed programs running during this installation session so that port usage can be checked."

I guess that explains it then. :-)

nipper

Yea makes sense. THe installer needs JBOSS, though it likely will restart it if it is off.