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

TS 7.3.1 Dependency Migration tool / iw-store/default migration

Tim__D

I'm moving from TS 6.7.2 SP2 --> TS 7.3.1. I've RTFM Smiley Happy

and have some additional questions.

* I notice a new branching structure UI wise in TS 7.3.1. configuration/locales configuration/users and roles..

Is my 6.7.2 SP2 iw-store good to go?

* Regarding the Dependency Migration tool.

I'm not running SitePub or LS. Do I run this on any branches that have DCR's or does this do non-templated files as well?

Do I run it on a mounted and active /iw-store or on an inactive store. I was thinking active but was not 100% sure.

In the TS 7.3.1 doc is says "NOTE TeamSite only supports a single Workarea per branch. In TeamSite,
there should only be one Workarea per branch; other Workareas should be
removed. The Dependency Migration tool does not by default migrate more
than one Workarea because of this condition; however, these workareas
can be migrated using the Migration tool's -w option. If you need to use
multiple Workareas, contact Autonomy Support."

Is this for real Smiley Sad

Find more posts tagged with

Comments

nipper

The 1 WA per branch is a SP limitation

Reportedly you can use the SP dependency step from the workflow in non-SP workflows. If you try that, you need to run the dependency tool on the workarea

You very well not need to do the dependency migration tool

Andy

Tim__D

The 1 WA per branch is a SP limitation

Reportedly you can use the SP dependency step from the workflow in non-SP workflows. If you try that, you need to run the dependency tool on the workarea

You very well not need to do the dependency migration tool

Andy

So running the "dependency migration tool" is elective. I see.. But of you want to use SP workflows or globalized content management features you need to run it is that correct?

If I run it do I need to move to a single workarea model or can I still use multiple workareas (running it in one and doing a get latest in the other of course)?

nipper

That I have not tried. I would think that running it on 1 workarea and get latest should work.

I am surprised that you are runing with multiple workareas, the vast majority of my customers run with a single workarea and the ones that have multiple do not use all of them consistently.

pass.png

imageTest.rptdesign

Tim__D

That I have not tried. I would think that running it on 1 workarea and get latest should work.

I am surprised that you are runing with multiple workareas, the vast majority of my customers run with a single workarea and the ones that have multiple do not use all of them consistently.

Yes that does not surprise me. Our environment is not much different. One workarea is for actual work. The others are usually 1 is for manual or automated merging only and authors do not have permission to use them.

About the first question..

So running the "dependency migration tool" is elective. I see.. But of you want to use SP workflows or globalized content management features you need to run it is that correct?

Is running this utility elective?

Is it required if you want to use dependency management and globalized content management?

Does it work for non-structured DCR content or does it also work for non-structred html / jsp files as well?

nipper

Is running this utility elective?

Is it required if you want to use dependency management and globalized content management?

Does it work for non-structured DCR content or does it also work for non-structred html / jsp files as well?

Yes it is elective

You will need to exec it if you want the dependency manager (and I think the globalization piece as well)

I also *think* it is only for structured content, but you can try it.

Tim__D

Yes it is elective

You will need to exec it if you want the dependency manager (and I think the globalization piece as well)

I also *think* it is only for structured content, but you can try it.

Thanks. As a test I created a simple HTML page with some images in a new branch on an otherwise blank iw-store. Then clicked on the image and selected "Find Associated Files". I also did this for the html file. On both the image and the html file it found nothing. This is the behavior out of the box for unstructured content with no configuration. As I learn more I'll try and update this thread.

blueCircle.png

imageTest.rptdesign

Adam Stoller

The dependency migration tool is supposed to work for DCRs and SP pages.
You are supposed to run it if you want to be able to use the Find Associated Files menu option.
Having the dependencies can be valuable down the road - it is unlikely to hurt anything if you don't have it and you never used SP.

I've only tried running it twice - once I got a bunch of errors but was taken off the project before I had sufficient time to try to debug it; the second time I tried was premature as there were a bunch of customizations (including scripts for DCTs, etc.) that had not yet been migrated and I wasn't involved in that part of the project (and again, I was off the project before that had been completed).

The major aspect of the dependency piece is, as has been stated, for SP - especially for people coming from a pre-7.2.0 environment in which there used to be an EA that got set to show some of the dependencies. As of 7.2.0 - that EA is no longer created or updated - so you need to have the dependencies migrated if you want to utilize that information (which the first project I was on did, for various reasons)

Sony Pictures BeX.rptdesign

Tim__D

The dependency migration tool is supposed to work for DCRs and SP pages.
You are supposed to run it if you want to be able to use the Find Associated Files menu option.
Having the dependencies can be valuable down the road - it is unlikely to hurt anything if you don't have it and you never used SP.

I've only tried running it twice - once I got a bunch of errors but was taken off the project before I had sufficient time to try to debug it; the second time I tried was premature as there were a bunch of customizations (including scripts for DCTs, etc.) that had not yet been migrated and I wasn't involved in that part of the project (and again, I was off the project before that had been completed).

The major aspect of the dependency piece is, as has been stated, for SP - especially for people coming from a pre-7.2.0 environment in which there used to be an EA that got set to show some of the dependencies. As of 7.2.0 - that EA is no longer created or updated - so you need to have the dependencies migrated if you want to utilize that information (which the first project I was on did, for various reasons)

Thanks for the advice. I have other questions but I think I'll try it out and see what happens. IT moving the iw-store over now. Honestly what I'm most concerned about is having to move to a single workarea model and having to run it on every branch to keep the iw-store in compliance with TS 7.3.1

Hopefully, that is not the case based on some previous responses.

Tim__D

So I've got TS 7.3.1 OD 7.3.1 and Search 7.3.1 installed and the iw-store moved over.

I've now tried to run the "iw_migrate_dependencies.ipl" on a new branch I just created. Interestingly its in the iw-home/install/livesite/install_scripts/ folder. Anyway, when I ran it with the -w option on a workarea I got pages of errors. I'm going to have someone with root access run it to see if that makes any difference.

Perhaps this feature only applies to TeamSite when you're running SP, LS etc..?