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.1 & database dependencies

droog

Just started my analysis on upgrading our Teamsite 6.7.1 SP1, Windows 2003, environment to Teamsite 7.1. Is it me or did this just become unnecessarily more complicated? I ONLY want to upgrade Teamsite and OD to 7.1. I feel like I am getting a large suite of products that I am being forced to install. I am basing this on a few things:

1) New database requirements for the event subsystem. I don't think I can even get around the install without providing a new database. Unless there is a need for Teamsite to use a new DB structure (we don't use livesite, reporting or search) why is this needed?

2) The proprietary IWOV installer. I may be a isolated from the rest of the industry, but are other software companies requiring proprietary software to open their proprietary install package?

Thoughts?

Find more posts tagged with

Comments

nipper

1) New database requirements for the event subsystem. I don't think I can even get around the install without providing a new database. Unless there is a need for Teamsite to use a new DB structure (we don't use livesite, reporting or search) why is this needed?

I certainly agree with this. I understand that the default DB was not ready for prime time, but there are cases when you can turn off the event subsystem and run things without a DB. It is even worse with Derby and MySQL off the list.

As to the installer, I kind of like it, though it is far from bug-free. It seems to be a very functional package.

Rick Poulin

1) New database requirements for the event subsystem. I don't think I can even get around the install without providing a new database. Unless there is a need for Teamsite to use a new DB structure (we don't use livesite, reporting or search) why is this needed?

They've ripped out the DerbyDB which was packaged with TS in previous versions. Though I doubt it uninstalls the one you've already got, I would expect that they're trying to drop support for it entirely and this is their way of forcing people down that path.

2) The proprietary IWOV installer. I may be a isolated from the rest of the industry, but are other software companies requiring proprietary software to open their proprietary install package?

Are you somehow used to being able to crack open install packages and mess around with them? That hasn't been my experience. But for the record, you actually can (to some degree) look at what's in the iwpkg files as they're just standard ZIP files. However, most of the installation logic is stored within Java classes, and while you could decompile them, I don't expect you'd find anything very interesting in there.

mart2001

If they drop off MySQL, then why when you run the installer, and click on custom database, it gives you examples of jdbc connection string using MySQL? Hmm....

I certainly agree with this. I understand that the default DB was not ready for prime time, but there are cases when you can turn off the event subsystem and run things without a DB. It is even worse with Derby and MySQL off the list.

As to the installer, I kind of like it, though it is far from bug-free. It seems to be a very functional package.

nipper

I do not expect that they are testing against mysql, with Sun being purchased by Oracle, I wonder how much support there will be for MySQL (or has GNU or someone else picked it up?)