The HTTP Bundle is capable of maintaining several HTTP servers. This feature is useful to group functionally-related Web applications and resources under separate name-spaces and network address. You can also set up the server instance to use primary and secondary ports different from the ones of the default server. For each server, there is a separate HTTP Service in the OSGi framework and you can directly register Web content with the service of interest.

To differentiate between the servers, you can use the "name" property of the corresponding HTTP Service. The primary HTTP server has the reserved name "default" and its HTTP Service supports plain and secure connection in the same time if both connection types are active. As the additional HTTP Services have the lowest ranking, bundles requesting the HTTP Service without filtering will get the one of the primary server. In addition, the "root directory" feature is available only through the primary server address and port.

You can create both type of servers – plain and secure, and configure each one through the conventional settings for the type. Refer to the following instructions for each type:

• To have a new plain server instance, create a configuration from the mbs.http.plain factory and populate its settings – refer to HTTP Plain Server Configuration.
• To create a secure HTTP server, set the mbs.http.secureConnection system property to true (refer to the OSGi HTTP Bundle's System Properties). Then, create a configuration from the mbs.https.secure factory and populate its settings – refer to HTTP Secure Server Configuration.