Configuring the Web ContainerAdded by IBM on October 5, 2011 | Version 1 (Original)
|The Web Container provides a runtime environment for Web applications in which Web applications can be run both disconnected and connected.
The Web Container provides a runtime environment for Web applications in which Web applications can be run both disconnected and connected.
Configuring the web containerParent topic: Managing client configurations
The default configuration for the web container listens only for HTTP requests received on localhost on a port dynamically selected during platform startup. If you need to make changes to this configuration, refer to the contents of this section.
Configuring the Virtual Host properties
The Web Container provides administrators with the capability to restrict access to Web applications to a specific port or list of ports. Refer to this section if you need to restrict access to certain Web applications.
Configuring the web container to use a dynamic port
When using the Lotus
® Expeditor on the desktop, the secure hypertext transfer protocol (HTTPS) is a communications protocol used to encrypt data between computers over the Web.
Configuring the Web Container using the SocketConfigService
Third-party bundles can use the com.ibm.pvc.webcontainer.service.SocketConfigService service to dynamically configure the Web Container ports at run time. Review this section if you need to dynamically configure the Web Container ports at run time.
Enabling and configuring the Channel Framework
The Channel Framework Architecture (CFA) is a highly flexible and scalable solution for client and server transports and provides common networking services, protocols, and I/O operations for the Expeditor Web Container.