Badkey Corner | Differences between Domino and xSP Domino

Saturday 6th, September 2008

Differences between Domino and xSP Domino09/06/2008 03:44 PM

The Domino server includes hosting features (xSP model) that allow multiple groups of users to be independently hosted by a single logical Domino server or cluster of servers in order to allow Notes- and Web-based clients to access their data from the same physical server securely using Notes/Domino or standard Internet protocols.

This model allows you to build a hosting environment that helps you run an ASP (Application Hosting Provider) or xSP service to provide a secure and shared environment—after all, a shared environment reduces the total cost.

Using a Notes client to connect to a Domino xSP server environment is NOT considered a supported configuration. An xSP server should be used only to offer pure Internet protocol-based access to a specific set of applications on Domino servers. Only Domino Web Access, POP3, and IMAP mail clients are supported under the xSP configuration. Domino Access for Microsoft Outlook is not a supported configuration as well. More @IBM Reference #: 1116281

Most of the features and power of Domino are available in the xSP configuration. However, in order to provide the security model which hides all users and applications in one organization from another, some constraints have been applied to the xSP configuration. The differences between an xSP and a non-xSP configuration are as follows:

- The design focus for the xSP feature was the use of Internet clients by end users. However, in order to support DOLS, testing was also performed with applications using Notes IDs and the Notes APIs. As a result, with some constraints, the Notes client may work for some applications.
- The Domino Directory is virtualized.
- Once the first server is installed, the xSP configuration cannot be changed to a non-xSP configuration, and vice versa.
- The Domino hierarchical naming scheme is fixed so that every name contains a common name and an organizational name. Organizational units are not supported.
- The use of Internet Site documents is mandatory.
- The Domino Directory is xACL-enabled and the User Activity Logging Confidential option is enabled.
- The use of ACL files is mandatory.
- The central authority uses the Admin client for administration. Some administration can be granted to organizational admins, but they must use the Web admin tool. If organizational admins will manage users, the CA must be configured and used.
- Global Web settings are global Web rules that are added so that common Web server files are shared by all organizations.
- Most databases and templates in the data directory have their ACLs modified to prevent access by any end user.

A number of default security settings are different in an xSP environment:
Typeahead is disabled.
MailLookupExhaustive is disabled.
MailAddressLookup is enabled.
ConvertNotesAddress is enabled.
HTTP_DatabaseBrowsing is disabled.
HTTP_AsynchronizeAgents is enabled.
WhiteList is enabled.
ServerCheckPasswords is enabled.
LdISite is enabled.
The ASP admins name is added to a number of security fields by default.

The Badkey Team

Technorati: Domino Lotus Notes

			Welcome to Badkey Corner The Badkey website is a website on security, IBM/Lotus Domino and Linux. The Badkey Corner Team RSS Feed and Curriculum Vitae
				Full Archive CentOS 5