Applications can be hosted in a variety of hosts. This includes but not limited to ASP+, Internet Explorer, EXEs, NT Services and Windows 2000 Component Services (aka COM+ Service).
Applications hosted in ASP+ can receive messages on the HTTPChannel. An ASP+ application is configured in IIS Internet Services Manager and ASP+ configuration files. The NGWS runtime remoting configuration file is loaded automatically when the first Remoting message (e.g. SOAP) arrives in the application via the HTTPChannel. IIS by default listens on port 80 for HTTP.
Application Hosted in ASP+
COM+ 1.x Applications and NGWS runtime applications can be hosted in Windows 2000 Component Services. These applications can use services such as Automatic Distributed Transactions, Object Pooling etc.
Applications hosted in Windows 2000 Component Services can receive messages through ASP+. An ASP+ application is created that routes the message to the Windows 2000 Component Services Application via COM Interop. The NGWS runtime remoting configuration file is loaded when the first Remoting message arrives in the ASP+ Application.
Figure: Hosting in Windows 2000 Component Services (aka COM+ Services)
Applications hosted in an EXE must load the NGWS runtime remoting configuration file using an API. The HTTP TCP Listener can listen on any port for HTTP. Effectively any process that hosts the NGWS runtime, running on the machine can receive and send HTTP messages.
Figure: Hosting in an EXE
Applications hosted in an NT Service must load the NGWS runtime remoting configuration file using an API. The HTTP TCP Listener can listen on any port for HTTP. Effectively any NT Service host the NGWS runtime, running on the machine can receive and send HTTP messages.
Hosting in an NT Service