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

OS Platform benefits

stevekrys

We have a TS installation as part of a larger eCommerce system. We use a BEA app server to drive functionality (MVC architecture) and this lives on a UNIX Solaris server. TS is used to produce front end jsp files and this lives on an NT server. We use an NFS mount (DiskShare) to connect the platforms. Source code for the back end is versioned in CVS on a UNIX server. We have have a build release engineer who runs scripts on a dedicated build machine (UNIX) that pull jsp pages from TeamSite editions and java, ejb, etc from CVS.

We have had issues with the NFS mount breaking in the past. Plus, we have separate reporting for CVS file changes and TS file changes because of the different platforms each system lives on.

It seems to make just plain good sense to move TS to UNIX (makes no difference to our end users), but I need to justify the expense of a box and effort to migrate the existing repository making sure we retain permissions, etc. Any one with experience doing this that can offer some input on other benefits to moving to UNIX that I'm sure I'm missing? Thanks.

Find more posts tagged with

Comments

gzevin

I am not sure that you will be able to retain the permission model that you have built in NT. All the scripts, etc will have to change.

Think twice,

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

ts_user

We went through a similar exercise where we had to justify the move to Solaris. We are currently on Win 2k ( don't know why we landed there on the first place). One of the main justification for our move was stability. We are currently facing a lot many problems and sometimes end up rebooting the server in the middle of the day. We have two implementations of TeamSite and Solaris provides us an option to consolidate both installations on to one server.
Migrating the backing store would be the biggest challenge. There are no ready made tools available for the migration. You would have to use a combination of Opendeploy/ Custom scripts for migration and setting the extended attributes and permissions/locks after migration.
In my personal opinion, the product behaves very well on Solaris than windows. Not sure what interwoven uses for their internal development? Eagerly waiting for Linux version of TeamSite which would help justifying the project so much easy Smiley Happy

Adam Stoller

FYI - OpenDeploy6 provides functionality for transferring EAs from one TeamSite area to another TeamSite workarea (same or different servers) without requiring a home-grown DNR script.

You're waiting for a Linux version, I'm waiting for a MacOS-X version - I think we'll both be waiting a long time ;-)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ts_user

I do not see the reason why Interwoven does not want to support TeamSite on Linux platform? They already do that for Opendeploy and also not so extensively used AIX platform. I am sure most customers would love to migrate from Windows and also Solaris to Linux once it gets released, our company being one of them Smiley Happy

Adam Stoller

OD is a simpler product than TeamSite - thus it takes less effort to port the OD code to other platforms.
AIX is IBM and IBM has/had a strong working relationship with Interwoven and thus it made sense (and dollars-and-cents :-) to port TeamSite to AIX.

Linux, to the best of my understanding is still a fluctuating OS - it's prevalent but in several different flavors. I think there is definitely a strong desire for many folks (including a number of Interwoven Engineers) to include Linux as a supported OS but there's more to the cost than just porting the code: which version of which flavor of linux becomes supported, extending the already stressed-out QA team to test and sign-off on it, etc.

MacOS-X has the advantage of only being a single flavor, but the disadvantage of having less proponents behind it - probably the only way this will happen is if Apple puts up some $$'s and engineering resources to work with Interwoven to create the port.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

stevekrys

Thanks. Just knowing that others have gone through the same issue at least makes me feel better. Now, if I can just come up with some quantifying numbers that let the business know that you will be better off if we switch platforms to UNIX!