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

Install path

Jenni

Hi All,

Thanks in advance.

We are trying to install teamsite 7.2.1 at

\iw-home. But the teamsite is getting installed on

\iw-home\TeamSite by default. Note that we are not specifying the directory 'TeamSite' anytime during our install. We cannot have the directory 'Teamsite' as the perl scripts (from older version of TS) are referring to

\iw-home. My question is, Is there a way we can have TS installed without it creating a 'Teamsite' directory?

Thanks!

Find more posts tagged with

Comments

nipper

Hi All,

Thanks in advance.

We are trying to install teamsite 7.2.1 at \iw-home. But the teamsite is getting installed on \iw-home\TeamSite by default. Note that we are not specifying the directory 'TeamSite' anytime during our install. We cannot have the directory 'Teamsite' as the perl scripts (from older version of TS) are referring to \iw-home. My question is, Is there a way we can have TS installed without it creating a 'Teamsite' directory?

Thanks!

Cannot be done.

Upgrade from existing 6.7.X in \iw-home will work.

Perl scripts should have used the iwgethome() perl module to prevent things like this.

Get ready for a *lot* of editing.

nipper

In 7.X you specify the parent (D:\Interwoven\) and it creates TeamSite, OpenDeployNG, etc underneath.

Jenni

Hi Nipper,

Thanks for the reply. We are on 64 bit Win 2008 VM and the only supported version of TS is 7.2.1. So we are unable to install TS 6.7.x versions. Do you have any other pointers?

We are thinking of creating a sym link (eg.

\iw-home ->

\iw-home\Teamsite).

Do you see any issue with this approach?

Thanks!

nipper

Make it /Interwoven/ instead of iw-home, if you are searching for /iw-home in a bunch of files to see if they need to be updated, you will never know if you fixed it or not. Easier to change /iw-home to /Interwoven/TeamSite than to change /iw-home to /iw-home/TeamSite

Yea the shortcut should work, have done that on Unix before.

But I would try to get the iw-home fixed in the Perl. There is a perl module that will get iw-home and set a variable. Use it.

Of course that does not help on the shebang line,

Migrateduser

Hi Nipper,

Thanks for the reply. We are on 64 bit Win 2008 VM and the only supported version of TS is 7.2.1. So we are unable to install TS 6.7.x versions. Do you have any other pointers?

We are thinking of creating a sym link (eg. \iw-home -> \iw-home\Teamsite).

Do you see any issue with this approach?

Thanks!

I am doing the exact same upgrade/install on a VM as your are. Follow Nippers advice and keep the default install and replace the hardcoded entries in your files.

Jenni

Thanks for the input everyone.

Migrateduser

One of the negative side effects I have encountered is if you had a hard coded iwhome path are that old workflows that came over may not work if you are referencing the old path. And you will also have issues if your datacapture.cfg had hard coded iwhome references they will throw an error.

Migrateduser

I just figured out a workaround. Make a symbolic link.

mklink /D e:\iw-home e:\Interwoven\TeamSite

My old workflows are working again. They would hang before this.