Hi,
I'm new to TeamSite and thus need some understanding to the use of an additional Staging Server in a TeamSIte CMS environment.
We are using TeamSite 6.7 with LiveSite 3.0.
With reference to the LiveSite SP1 installation document (Page 10 Figure 1)

It has a TeamSIte Development Server where TeamSite Control Center will sits and a Production Server where the content and LiveSite Runtime will sits.
The understanding is that all the content created in TeamSite will be submitted to TeamSite STAGING area and the workflow will allow approving user to preview and approve the content based on the STAGING AREA content.
Is this correct?
This will coincide with the Deployment Configuration specified in the LiveSite Runtime installation guide that, the path of the "exploded" iw-runtime.ear (on the Production) is specified in the odbase.xml on the development server.
However, we were advise to use a Staging Server to host the content for preview before pushing the content to the Production.
(ie. an additional runtime server for the purpose of hosting staging content)
Is this the common or best practice?
If so, what is the logic for using such a process?
And, what will the odbase.xml path be if there is a Staging and Production server, should the
be set to the Staging or the Production server?
I would greatly appreciate any advise on this.
Thanks.
Han Ming