Forums (Obsolete)

Member

anshuman.shandilya-aonhewitt - 6/15/2013 10:52:47 AM

kentico license help

Hi,

I am using kentico 7. My website setup is like I have one domain name (www.xyz.com).
Then I have multiple sites under sitemanager in kentico, and each site has one web application under same domain name in IIS. So sites are like www.xyz.com\client1 & www.xyz.com\client2. But the catch is that every web application in IIS is pointing to same kentico code base and cms database. In this scenario, do I need
1 server, 1 website ultimate license
OR
1 server, unlimited website ultimate license.

Please suggest

Thanks
Anshuman

Member

kentico_sandroj - 6/15/2013 11:28:55 AM

RE:kentico license help

Hello,

If you run a single website that uses one main domain and several domain aliases that point to the same website (same content), you need only 1 Website License. However, if you use several domains that point to different websites (different content), you need to have an appropriate number of website licenses.

Please see the licensing FAQ for more information.

Regards,
Sandro


Member	anshuman.shandilya-aonhewitt - 6/15/2013 12:15:05 PM RE:kentico license help Hi, Thanks for the quick response. This is really helpful. Regards, Anshuman

Kentico Legend

Brenden Kehren - 6/15/2013 11:44:05 AM

RE:kentico license help

The license would go by the number of sites you have per installation/code base. So if you have one install with 10 websites in it then you'd need 10 licenses OR 1 server with 10 site license. If your an individual business and will be having 1 to many sites, the 1 server unlimited licenses is the best bet.

What is confusing me is you mention you have the main website in IIS (main Kentico code base) and several applications under the parent site. Are those child sites new code base instances? If not, then there really is no reason to have 10 different sites in site manager. Have one site and in your content tree, create new nodes for each new client. You can set permissions for each node which would include adding a new Role and assigning that new role to the new node in the site. With this setup you may have to create a custom webpart for registering that gathers the "client" name from the url and assigns that specific role to the person when they register. This way would only require one license vs. the number of clients who would need a portal.

This is just a suggestion and it would depend on the business needs/requirements. I am a freelance consultant, Kentico Certified Developer and Certified Kentico Partner if you'd like help, please let me know.

Member

anshuman.shandilya-aonhewitt - 6/15/2013 12:25:26 PM

RE:kentico license help

Hi,

Thanks for your insight in this. But I have few queries, if we create new node for every new client.

1) As we have new site for every client, we apply client specific CSS on the new site. All the classes in our CSS remain same for every client (site) but we change the attributes (eg. color from red to green). If we have different/new node in the same website, then how we apply different only on the node.

2) We have created global custom settings and then we override one or more settings for every site/client. If we have a new node for a client then perhaps we have to create new set of settings for each client.

3) Also we load users specific to site/client. If we create new node in the same site then we have to map users with a client id in a separate table.

Can I get your valuable insight regarding these points

Regards
Anshuman

Kentico Legend

Brenden Kehren - 6/15/2013 10:19:26 PM

RE:kentico license help

anshuman.shandilya-aonhewitt wrote: 1) As we have new site for every client, we apply client specific CSS on the new site. All the classes in our CSS remain same for every client (site) but we change the attributes (eg. color from red to green). If we have different/new node in the same website, then how we apply different only on the node.

Assume you have www.abc.com which has a style sheet named abc.css in Development>Stylesheets. In that stylesheet simply use a few import statements and import the main site and sub site stylesheets. Then create your new node and make it a master page and select the xyz stylesheet in the general properties.

anshuman.shandilya-aonhewitt wrote: 2) We have created global custom settings and then we override one or more settings for every site/client. If we have a new node for a client then perhaps we have to create new set of settings for each client.

What kind of settings are you changing? Site setting? Web part settings?

anshuman.shandilya-aonhewitt wrote: 3) Also we load users specific to site/client. If we create new node in the same site then we have to map users with a client id in a separate table.

There is no need to do this assuming you have a 1 to 1 relationship. If one login can only belong to one "site" then just add a new field to the cms_user table and store that client id in there. If you don't want to store it in the cms_user table, then use the cms_usersettings. Either way, as long as it is a 1 to 1 relationship, no need for a x-ref table. Permissions can also be set to so only users of a particular role can access their node.

Again, I'm just thinking outside the box especially since they are sub sites of the main site. Kentico is very flexible and can be configured many ways.