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

deployment features

niniti

TS672, OD620, winserver2008
-------------------------------------
Filters
Comparison rules
Transfer rules
Permission rules
Use with access control lists (ACLs)
Deploying symbolic links
Parameter substitution
Deploying TeamSite extended attributes (EAs)
Use with adapters
Use with DataDeploy

Are these deployment features are configured in deployment element or definition element ? Or are they separate element directly under deploymentConfiguration element ?
Filters is configured in definition element under source and target both and odnodes.xml as well.
This information is not specified in manual that under what element are these deployment features configured.

Thanks

Find more posts tagged with

Comments

Adam Stoller

TS672, OD620, winserver2008
-------------------------------------
Filters
Comparison rules
Transfer rules
Permission rules
Use with access control lists (ACLs)
Deploying symbolic links
Parameter substitution
Deploying TeamSite extended attributes (EAs)
Use with adapters
Use with DataDeploy

Are these deployment features are configured in deployment element or definition element ? Or are they separate element directly under deploymentConfiguration element ?
Filters is configured in definition element under source and target both and odnodes.xml as well.
This information is not specified in manual that under what element are these deployment features configured.

Thanks

Read the manuals, read the DTDs and get some training. The reason a number of these items exist in multiple locations is that they are needed for different reasons and/or in different situations such that a single location is insufficient.