Difference between revisions of "Subprovider"
Jump to navigation
Jump to search
| Line 48: | Line 48: | ||
* Subproviders are sharing their physical resources (CPU power and RAM). A heavy load of a single Subprovider leads into heavy load of all Subprovider-instances. | * Subproviders are sharing their physical resources (CPU power and RAM). A heavy load of a single Subprovider leads into heavy load of all Subprovider-instances. | ||
* upon restricted administration possibilities, it is strongly recommended to manage the complete administration by a employee of the main provider. | * upon restricted administration possibilities, it is strongly recommended to manage the complete administration by a employee of the main provider. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 09:12, 18 April 2011
Contents
the Subprovider feature
A Subprovider is a way to host multiple regify-provider instances on a single system. In fact, all Subprovider instances of a regify-provider, each visible with different customizing to the customers, is running on the same hardware / virtual host.
individual Subprovider features
The following settings are customizable individual for each Subprovider:
- page-Design by using individual CSS files and images for each Subprovider
- header and footer content
- e-mail templates are completely individual (css-design and text-content)
- customized logo in regify-client (logo in right upper corner)
- customized standard-template for all mails sent using standalone-client, Outlook addin, Thunderbird addin, Lotus Notes addin
- shop-pages for premium-membership of single users and group-administrators
- blacklist for mail-addresses, domains and sub-domains that are rejected from registering
- Terms And Conditions (German 'AGB')
- customizable authentication form (Subprovider authentication-level can vary)
- used HTTP header meta-information
- individual configuration as community-provider or corporate-provider
- selection of active and inactive portal-options for end-users
The following functions and settings are shared between all Subprovider (not individual):
- language-specific sentences
- maintenance-state
- local paths for downloads, log-files, obligatory attachments and temporary files
- clearing-connection is always shared between all Subproviders
- proxy-settings
- local time-settings (difference to UTC-0)
- premium-time offered as trial period
- number of days a registration, invitation or added mail-address is active/valid
- length of passwords and unlock-codes
- PDF settings
- emergency SMS settings (they all will go to the administrator of the main provider)
- some specific authentication-settings
- settings for intrusion detecting system (IDS)
- the definition of administrative accounts is only available to administrators of the main provider
- a Subprovider is able to administrate many functions inside of his domain (user-data, groups etc.), but some functions are still only available to the main providers master-administrators.
prerequisites
In order to manage a Subprovider, the following prerequisites are needed on the hosters side:
- individual IP address for each Subprovider
- individual domain for each Subprovider (A record in DNS entry)
- specific SSL certificate for the desired domain
other important information
- a Subprovider stores his user-data and transaction information in the same database as the main provider. There is no physical separation of the data. Upon this, a later separation into a new provider-instance needs extreme effort.
- Subproviders are sharing their physical resources (CPU power and RAM). A heavy load of a single Subprovider leads into heavy load of all Subprovider-instances.
- upon restricted administration possibilities, it is strongly recommended to manage the complete administration by a employee of the main provider.
