Question 4 of 4: Development instance of TeamSite on same server as Production

As this question is a little less specific to my situation, I'll post the background below but it is less relevant to this question.

As my other questions may require TeamSite development, it is possible to host a second instance of TeamSite/SitePub/LiveSite on the same server as the production installation? Are there licensing implications in doing so?

This would allow me to implement the suggestions I hopefully receive from my other questions and test them and not impact other users while doing so....

Thanks in advance.

If you have reviewed my other questions, this section is the same:

<about>

Background: A vendor has designed HTML for a new site and we need to manage the pages in TeamSite. We have componentized the common aspects of the pages. The vendor developed the pages without consideration for requirements/restrictions of TS. Being a responsive design, we want to match the HTML provided by the vendor as closely as possible. This way, if the design doesn't work, we can push back to the vendor and request they fix it.

Products/Versions/Current Methodology: We are using TeamSite 7.4.1 with SitePublisher. No customizations have been made to the installation. The pages are currently based on custom fixed area layouts used in a template with various components which are then used to create pages using the same general format (c-clamp etc). NOTE: The pages are typical static marketing type pages and are therefore "invariant" with respect to each request, so we are deploying the HTML generated and NOT using the LSDS.

My background: I am an application architecture and have many years of experience. I know countless languages such as Java as well as technologies like XSL, XML, javascript etc. However, often I know only enough to be dangerous and not enough to say I'm an expert.

</about>

Find more posts tagged with

Comments

nipper

TeamSIte is installed only once on a server. End of discussion.

You need training (specifically SitePublisher training) judging from your other questions.

Your choices here are to either buy a development instance of TeamSite (certainly the most common approach) or use a different branch for development. The latter will not insulate you completely, because there are a number of shared items you will have to contend with. But it will cover 70% of the issues.

Adam Stoller

WGM wrote:

As my other questions may require TeamSite development, it is possible to host a second instance of TeamSite/SitePub/LiveSite on the same server as the production installation? Are there licensing implications in doing so?

This would allow me to implement the suggestions I hopefully receive from my other questions and test them and not impact other users while doing so....

Thanks in advance.

I've read your other posts, and don't have specific answers to those questions (sorry) - however this one is pretty easy to answer: "no" - you cannot have more than one instance of TeamSite installed on a single server instance (if you have multiple VM's running on a physical server, you can have a distinct TeamSite installed in each of the VM's - but you cannot have two TeamSite's installed on the same VM)

The same applies to SitePublisher, since that is a module of TeamSite.

LiveSite - which comprises both LSCS (content-services) and LSDS (display-services, which you indicated you are not using) can have multiple instances installed on a given server - at least in terms of the runtime environment (as opposed to the authoring environment which is the TeamSite server, see above). So, you could (I believe) have a single TeamSite server send content to multiple LSCS runtime environments - whether or not this help you without being able to have multiple TeamSite servers running on the same [physical] server is debatable.

Most organizations have at least two TS/SP/LS environments set up: DEV & PROD.

Some organizations have more than two (e.g.: DEV, STAGE, PROD)

Consultants who do this kind of thing full-time and have invested the money in it will have their own TS instance on their laptops (sometimes several, in different VMs).

I did work at one customer site where there was a DEV TS server, but the developers (of which I was not, in this particular case) had their own LSCS (and possibly LSDS?) instances running on their laptops so that they could test things out against their own environment without affecting all the other developers. As I wasn't directly involved in development on that project, nor was I involved in setting up the environments on the other developer's laptops - I cannot provide any detailed information about how it was set up (sorry).

Bottom line though: there should be at least two TeamSite servers so that developers can restart services as needed on the DEV server without affecting users who are working on the PROD server.

WGM

Thanks. Normally we have a dev, qa, prod model. However, the cost of licensing one instance of TS was all the project could bare at this point. We will be doing a larger project next year and I will recommend they look into a dev server license.

nipper

WGM wrote:
Thanks. Normally we have a dev, qa, prod model. However, the cost of licensing one instance of TS was all the project could bare at this point. We will be doing a larger project next year and I will recommend they look into a dev server license.

FYI, there is a developer instance for TeamSite. It is not the level to buy a nice house, just a really nice car (typically). You should look into it.

Reji Varghese

Doesnt a "Development environment" license come included with a "Production" license ?

Atleast in one of my previous projects, thats how the deal was made Smiley Happy

Default Unit.jpg

Adam Stoller

A lot depends on when the purchase was made and through whom - different sales reps (over the various years and organizational changes [Interwoven > Autonomy > HP]) sometimes make different deals or are guided by different hi-level corporate strategies and/or mandates.

Check your existing sales agreement / licensing paperwork and/or talk to your sales rep.