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

Experience with 7.1?

jwl

Hi,

With TS 7.1 out now I'm wondering what people's experiences with it have been. Are there any issues which you'd like others to know about before recommending it simply "because it's the latest"?

Many thanks
John

Find more posts tagged with

Comments

curiousmaverick

Well I can surely tell you that installation is really painful.

Bhargav Coca

Well I can surely tell you that installation is really painful.

Care to share your nightmares?

Migrateduser

Well I can surely tell you that installation is really painful.

I'd have to agree with that. The installation is the most painful I've experienced since 5.1. In particular, there are certain errors that don't get reported in the UI and one has to go digging in \Interwoven\iwinstall\log\installer.log to figure out what went wrong.

I opened a document defect for page 29 of the install guide as well. Here was my question:
[INDENT]Page 29 of the Web Solutions Authoring Components
Installation Guide Version 7.1.0 Document Revision 01 has the following
instruction:

Add an OpenDeploy user called livesite-od and assign the master role to that user.
(See the section about roles and authorization in the OpenDeploy Administration
Guide.) Windows requires the form domain-name\\livesite-od, and UNIX requires the
form livesite-od.

Give that there is no master role for OpenDeploy, I assume that the above should
say to assign the od-admin role to the user. Also, the prerequisites do not
specify the creation of the underlying OS user. Are there any particular
requirements for that user (e.g., must that be the name, do they need to belong to
a particular group, etc.). Lastly, I can't find any other references to this user
in the other install guides. What is this account actually used for?
[/INDENT]

and here is the answer:
[INDENT]Yes, you are right. the user needs to be assigned as od-admin role. It does not really need to be the same name and does not need to be in a particular group. You just need to make sure you provide the correct user name when you do the TS installation. There is a step asking you to enter the OpenDeploy Admin Username and Web Services connection information.

This account is a proxy user account that LiveSite uses to authenticate with OpenDeploy.[/INDENT]

Another thing to be aware of is that the 7.1 SitePublisher Developer's Guide is not available yet. The 6.7.2 guide still seems to be pretty well on target, but it does not include any information on interacting with LSCS or on building components in .NET.

nipper

Overall I like it. I have one LS implementation in production and others moving quickly.

The LiveSite enhancements are quite nice and if you are doing multi-language websites, YOU MUST USE 7.1. It offers some things that will significantly impact you implementation. These impact the way you implement things, so if you start with 6.7 and move to 7, there will be significant rework.

Quality of release wise, it is pretty solid. A few bugs but no show stoppers.

The install is a serious pain. But once you figure out how it works, it is not that bad. There are a few threads on it.

Andy

nipper

.......

This account is a proxy user account that LiveSite uses to authenticate with OpenDeploy.

........

This is to get rid of the passphrase (I think). That file is a serious pain in the a$$ when it does not work. I have a set of 6.7.2 Dev and Prod servers. I have to reset the passphrase on the dev server every few months, though the prod has never had to change.

Crsb

7.2 is coming out soon Smiley Happy

mart2001

I agree that TS 7.1 install is a pain, especially for Linux. If you have to uninstall and use the manual mode, it does not totally uninstall. Then when you try to re-install, they are looking for some libraries that they can't find. Since they are suppose to only support Redhat, why did they not go the rpm route instead of the universal installer? I am still trying to install it, although it says the install completed. But my TeamSite GUI isn't up...

jwl

Thanks one and all for your feedback.
Are the TS7.1 installation pains mostly associated with LiveSite? Is the installation of 7.1 itself OK, if LS isn't being installed?
Thanks again
John

Migrateduser

Nope. The core TeamSite installation is where I was running into issues. The LiveSite installation seemed a little smoother.

Migrateduser

They dont have the 7.1 developers guide out yet. Of interest is the FAL stuff since there are new abilities and nothing is documenting them yet.

Migrateduser

Chiming in:

We just finished installing TS 7.1, OD 7.1, CSSDK and TS Search on a Solaris LDOM. It's our development server.

Overall, the install was OK. It's a mixed bag of command line and graphic installs. They seem to want to make it easy, but as the admin that I worked with (who'd never done a TeamSite install before) said:

"All in all an unimpressive installation experience. The "how to install software" problem was solved years ago. For Solaris this should be as simple as: pkgadd -d IWteamsite""

Some thoughts / observations:
- The last install I did was 6.7.1. This 7.1 install introduced a db administration back end that required that I engage with our DBA group, figure out the connection info from the Solaris machine to the db, etc. I was suprised that there's little to no info on taking ownership of this new db component. I've got a Support ticket open asking for some schema info, sizing info and pruning info.

- We ran into one ZFS file system issue where, once a week for the first 2 weeks of the install, the TeamSite memory monitor shut down the backing stores due to a lack of available memory. We think ZFS was memory hungry (found a post via Google of someone with the same ZFS / TS issue), so we put a cap on the ZFS memory usage and that seemed to fix it.

- Not so much an install issue, but the LDOM performance is less than optimal, so we're not considering that for production.

- It should be noted that the 7.1 OpenDeploy Admin interface into the Content Center is a subset of the capabilities available in the OpenDeploy Admin package. We thought we wouldn't need to install OD Admin, but that's not the case.

- The UI for the LDAP integration adding of users is nice, but the revamped UI for user administration seems, at first glance, more difficult to get work done with. With 6.7.1, I could really quickly set up a new user based on an existing user's group memberships and I can't yet figure out how that'll be done efficiently in the new UI. May have to code up a back-end utility there.

- Absolutely love the idea of being able to rotate logs without stopping TeamSite. I think I was on that feature request for 5 years.

- Looking forward to testing out Search. I'm not positive, but I don't think that the last Search install we did (6.7.1 SP2 on a dev server) had a cross-branch search, which made Search seem barely useful. It shows the cross-branch capability now, so I'm looking forward to testing that.

We didn't install any SitePublisher / LiveSite components, so I can't comment there.

Hope that's helpful.

nipper

"All in all an unimpressive installation experience. The "how to install software" problem was solved years ago. For Solaris this should be as simple as: pkgadd -d

IWteamsite""

Yea esp because we all know MSFT and Linux support pkgadd.... Smiley Tongue

- Absolutely love the idea of being able to rotate logs without stopping TeamSite. I think I was on that feature request for 5 years.

Well more than 5 years I can tell you

- Looking forward to testing out Search. I'm not positive, but I don't think that the last Search install we did (6.7.1 SP2 on a dev server) had a cross-branch search, which made Search seem barely useful. It shows the cross-branch capability now, so I'm looking forward to testing that.

It was available through the cssdk, but not TS itself.

me