Control Hub vs TeamSite

Does anyone here have experience using Interwoven's control hub?

I would like to know the benefits of the control hub over TeamSite.
How is control hub different from TeamSite?
Can't I use TeamSite to do the same stuff as control hub?

Thanks
K

Find more posts tagged with

Comments

Bill Klish

My client is beginning to explore this same question as well.

From a technology perspective control hub is a stripped down TeamSite (basically no templating). There is something to be said with having a packaged solution already created that is supported by Interwoven versus building the solution yourself. Keep in mind that Interwoven is marketing control hub to customers who may or may not have TeamSite.

That being said, we are going to continue to research more on this issue and we haven't come to a conclusion as of yet. I am in the process of beta testing the next release of control hub to see what it offers to weigh the buy it vs. build it situation we are in.

kajjubee

Thanks bk99d, I was under the impression that control hub is upgraded TeamSite turbocharged (TeamSite plus something). I think templating is supported ( from the documentation) From my understanding you can do anything you could do in TeamSite plus this content provisioning. In the docs you see a section for upgrading from TeamSite to control hub, so its definitely a scale up.

Regards
K

Adam Stoller

Thanks bk99d, I was under the impression that control hub is upgraded TeamSite turbocharged (TeamSite plus something). I think templating is supported ( from the documentation) From my understanding you can do anything you could do in TeamSite plus this content provisioning. In the docs you see a section for upgrading from TeamSite to control hub, so its definitely a scale up.

Regards
K

I'm with bk99d on this - I think your impression is incorrect. The primary purpose of ControlHub as I recall (having heard about it but never used it) is to version distributions - as such you get the basic TS versioning capabilities and at least some level of workflow processing, but I don't think there's any templating functionality - nor would I think of ControlHub as an upgrade from TeamSite.

However - I'm willing to be informed that I'm wrong about this from any of the official folks...

deepakb

Below is the note from the Control Hub admin document in the Migrating TeamSite to ControlHub section

Note: This release of ControlHub is not a replacement for TeamSite when used for Web content creation, collaboration and management. If you currently have TeamSite installed, and are using it for these purposes, you should install ControlHub on a different host.

Clearly ControlHub is a tool for aggregating point for manging updates from multiple development system and not facilitating Web content Creationg through Templating, Workflows.

kajjubee

Can anyone from Interwoven confirm this please?

Thanks
K

Migrateduser

ControlHub is based off of TeamSite technology for the use of aggregating code and content changes from many repositories (TeamSite, SCM's like CVS, ClearCase, MKS, etc), synchronizing and versioning the changes, and then deploying the changes through test, pre-production, and production stages. It is part of the Content Provisioning Solution from Interwoven which includes OpenDeploy.

The differentiating points from TS include the following:

1) Out of the box configurable workflows for provisioning and rollback
2) new features in the UI including a deployment tab and the ability to monitor and initiate OD deployments directly from the ControlHub UI.
3) Direct link from the CH UI to OD Admin UI
4) Configuration 'wizard' tool for creating OpenDeploy and ControlHub configuration files for SCM provisioning to websphere and weblogic
5) Documented best practices for application provisioning

Templating is included starting in version 2.1.

Mariam