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

Spliting odnodes.xml to mapped files?

Migrateduser_427

Hello all,

We are using map files for TeamSite branch to file list deployments, and since those have worked for us so well, I have a question.

Has anyone done or thought of how to split the odnodes.xml replication farms into separate files and map them to nodes in odnodes.xml?

I am not even sure it is possible, however the file is getting very heavy for us to maintain when adding or removing nodes.

Find more posts tagged with

Comments

Adam Stoller

Hello all,

We are using map files for TeamSite branch to file list deployments, and since those have worked for us so well, I have a question.

Has anyone done or thought of how to split the odnodes.xml replication farms into separate files and map them to nodes in odnodes.xml?

I am not even sure it is possible, however the file is getting very heavy for us to maintain when adding or removing nodes.

I've never tried it - but you might be able to extend the DOCTYPE header to include externally defined entities ... (see this thread for an example for extending DCTs)

Note - this is not "officially supported" by Interwoven (as far as I know) - but if it works:

Migrateduser_427

Thanks ghoti! Good idea!

We will look into that an post here my findings.