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

TeamSite Front Office Client

artor

Hi All,

I wannt to ask a question regarding TeamSite Front office server and client , well we want to use TeamSite as for version control but due to Teamcode support is off from interwoven, we exploring teamsite front office client, if we put the code in each workarea for each developer and map that workarea for each user through teamsite front office client, so please tell me this approach would be beneficial as teamsite being a version control or not?
and how effective Team Client works with this approach? Does anybody explore TeamClient? Is there any other who using teamsite as a versio control please let me know.
I know its a kind a debating question but I have a very good feedback from this forum all time and hopefully i would get good feedback in this regards as well.

Regards,

Find more posts tagged with

Comments

Dwayne

TeamCode and TFO were designed to support two very different sets of users. My first reaction to your suggestion was ugh - no way!

The "selling point" of TFO is integration with the MS Office product suite. TeamCode was intended for software developers, rather than content authors, to manage their source files. I certainly don't see a Java programmer using MS Word to manage their .java files! So, in that sense, TFO seems like a lot of overhead for little to no gain.

The only thing that TFO provides that might prove useful for software developers is the briefcase. (I think that's what it was called - it's been a while since I used it). Basicly a local repository of "checked out" files, so that the developer can work "off line" from the TeamSite server. But even that seems of fairly limited usefulness, if I'm understanding your environment correctly.

It really sounds to me like you should be engaging your sales rep with this sort of question. Without knowing in a fairly detailed way just what it is you're trying to accomplish, we'll just be taking blind guesses.

--

Current project: TS 5.5.2/6.1 W2K

artor

Hi Dawyne,

Because TeamCode is ending and so there is no way that developer team use Teamsite for version control in order to check In and check out because what TFOC client sound to me its like a brief case and all you can check out and check in the files like a file system. So if you know any other approch that teamsite could work with developer team from outside the box(IDE) as a version control.
Otherwise I would jump on this conclusion that teamsite is not appropriate for version control.

Regards,

Adam Stoller

It all depends on what you need to do and what else you have on hand.
Interwoven uses TeamSite for version control of the Interwoven products - so it can certainly be used as such - however, if you're not also doing web development and/or don't already have TeamSite, then it's probably overkill and/or under-featured as a full-fledged SCM system (like ClearCase). If all you're looking for is version control (without a lot of bells and whistles) than something like CVS is probably a very good selection.

If you do already have TeamSite and are also doing web development - there's no reason why you couldn't use TeamSite as a version management system - but it still wouldn't be an IDE - just a version management system.

Rule 1: Figure out what you need to do
Rule 2: Figure out how you want to do it
Rule 3: Pick an application that supports Rules 1 & 2

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

Migrateduser

Our code developers use ClearCase and our creative folks use TeamSite. We had Interwoven Consulting Services in a couple months ago to specifically analyze and design a workflow that would combine the two processes, while still allowing the developers to use ClearCase for version control. The end result was that TeamSite really can't interact with ClearCase very well and so the results of the analysis were not what we had hoped for.

Front Office is almost a decent product. We were very hopeful that TFO would resolve a lot of our issues with file locking remotely and permission issues for people who develop on their own PCs and then FTP or Samba their files into TeamSite, which is every single one of our users. The problem with TFO is that if you choose to initiate workflow whenever you check a file in, it kicks off a workflow for each file individually. There's no way to use TFO to start a workflow with a set of files you check in, at least not back when we tried it. If that has changed recently, I'd like to know about it.

TeamCode, as far as I understood it, was not really a separate product, but a way of organizing your branching structure for code development purposes. You could probably get an Interwoven consultant to come in to your site for a week and help you design your branching structure for you to do code development.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

To follow up on what Smitty was saying, there is an article in the technical library that describes branching strategies. It was originally written to complement TeamCode, but most of the ideas are still relevant, even without TeamCode.
Here's the link:
http://devnet.interwoven.com/site.fcgi/techlib/049531

hth,

lissa

artor

TeamCode is ending its life and there is no more support available for this product with TeamSite 6.1 as I came to know through Interwoven suppor team. and as you guys said TFO is more suitable for Busieness user and its not more advanced to make TS as a true version control fair enough I have a meeting with Interwoven consultant next week that what could be the good approach in order to have all developer team such as Web Development Team and Content Management Team in one roof like TeamSite 6.1 for version control.

As far as Branching strategy is very clear to me that how many branch that we keeps in our organization as for development and it is also suggested by Interwoven in white paper.
Branch
1.Development____Edition
|____Staging
|____WorkArea_____User 1
|______Project
|_____jsp
|_____html
|_____images
|_____WEB-INF
| |___src
| | |____com
| | |___org_____all source files
| |___lib
| |___etc
|
|_____Business Template
|____financial
|____data
|____presentation
|____datacapture.cfg

2. Integration________same as above
3. QA Testing_________same as above

This is the small approache I am following in order to use TeamSite as a version control and each workarea related to User1 for developer mouting to their local machine and each user can make changes in their private workarea seperately either copy to local machine or mapping drive which prevent them to make changes in other workarea and they can also get the latest copy from staging area as well.
Just want to have your comments in this approach could be feasible to make teamsite as an appropriate version control or it could lead some more problems because in this approach Java development team and content developer team can work togther.
So please advise me about this approach.

Regards,