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; } } }

Change in Templating.cfg needs restart?

Log

Hi All,

We are facing a problem with the templating.cfg at our client place. When we saw the copy of the file we understand that some of the tags were not properly formed. Along with that we have some more data categories and types to add.

What we wanted to know is, for each change in templating.cfg, do we have to restart the teamsite server? Or anyother specific service to be restarted?

Can anyone tell whats the service to be restarted, if any OR Server to be restarted?

Thanks in Advance
Logesh

Find more posts tagged with

Comments

megamala

I think its not necessary to restart any services. When you chang and save the templating.cfg, it should apply the changes (without restarting any IWServices).

MM Guptha

whysguy

Hi Logesh,

You should only need to reset the services when changing iw.cfg, submit.cfg, autoprivate.cfg, and the roles files.

I hope that helps.

- Billy

herald10

Just do an iwreset without any flags. That should reflect all the latest changes in templating.cfg

Log

Hi Thanks All

LooseCannon

It's not necessary to run iwreset after modifying templating.cfg

Maninder_IBM

You do realise that iwreset stops the service? It will cause the users to get bombed out.

JonathonG

"iwreset -a" and "iwreset -ui" stop the services
Plain "iwreset" does not stop any services, but does instruct the iwserver process to re-read configuration information

Jonathon
Independent Interwoven Contractor

Maninder_IBM

But does plain iwreset pick up everything in the iw.cfg?

LooseCannon

No, not everything...

A change to the proxy remap section, for example, wouldn't be recognized after running iwreset.