Groups: Administration
Joined: 11/3/2005(UTC) Posts: 2,253
Thanks: 28 times Was thanked: 60 time(s) in 59 post(s)
|
UWS Brief Architecture and Component OverviewAll files mentioned below are located in the "%ProgramFiles%\UltiDev\Web Server" folder, unless stated otherwise. UWS Components and Utilities
- UWS Explorer (UWS.Explorer.exe) is a Windows UI utility allowing end users to manage applications hosted by UWS service. UWS Explorer is a primary tool to manipulate UWS application configuration file, "UWS.Configuration.xml" file located in "%programdata%\UltiDev\WebServer". Also, UWS Explorer displays state of other components, like UWS service and UWS host processes.
- UWS Monitoring service, (service name "UltiDev Web Server Pro", file name "UltiDev.WebServer.Monitor.exe") is similar to IIS service: it does not host applications itself, but rather monitors health and manages life cycle of external UI-less processes that do actual applications hosting. When service is shut down or restarted gracefully, it will also shut down and restart all host processes. If service crashes, the system will make several attempts to restart it. After getting restarted service will reconnect with host running processes without any impact on the uptime. "UltiDev.WebServer.Monitor.exe" can be started as a regular program for troubleshooting purposes. To run "UltiDev.WebServer.Monitor.exe" in interactive mode please stop "UltiDev Web Server Pro" windows service, uncomment <trace> section in the "UltiDev.WebServer.Monitor.exe.config" file and run "UltiDev.WebServer.Monitor.exe" as Administrator/Elevated program.
- UWS host processes (UWS.AppHost.ClrX.XXXX.exe) are programs started by UWS service and where applications are loaded and where incoming requests are received. Host processes differ by CLR version and bitness. Host processes will exit if UWS service has not communicated with the host for some time, but normally hosts stay running in memory for very long time. When host is recycled from the UWS Explorer, a new host process gets spawned, the old one stops listening to inbound requests but finishes serving received requests, and new host starts listening to the inbound requests. Multiple host processes of the same CLR and bitness may be started under different user security accounts, to host one or more application each. Running fewer applications per host means better application stability due to their independence from misbehaving applications, but it also means higher memory usage, as .NET Framework is loaded in each process.
- UWS Interactive Server (UWS.InteractiveServer.ClrXXXX.exe) are regular Windows programs that can be started from Windows Explorer or from a command line, and play a role of an interactive host process running in the security context of the currently logged in user. It is intended to be used for application debugging and testing purposes, and not for permanent hosting. When run by non-Admin/non-elevated user, Interactive Server can only listen to loopback IP addresses, like 127.0.0.1, [::1] and localhost. However, when started by an Administrator/Elevated user, Interactive Server can accept external requests.
- Configuration repair utility (UWS.Reg.Repair.exe) can be used to repair UWS after it stopped working due to some external factors, like other programs and components being installed or changed. It can also be used to add UWS as an installation prerequisite component to Visual Studio and InstallShield if they were installed after UltiDev Web Server Pro.
- Application command line registration utility (UWS.RegApp.exe) is to be used primarily by installers of applications bundled with UWS. It registers applications with UWS Service the same way they are registered manually with UWS Explorer or programmatically using .NET or COM API.
- Application Locator/Redirector web application (Redirector folder, http://localhost:7756/) is a web application hosted by UWS that allows redirect to any application hosted by UWS, using application's ID. Application Locator determines application address and port (even for ports assigned by UWS upon application's installation) and redirects to the application. Application Locator/Redirector could be used via links like "http://JohnsDesktop:7756/GoToApplication.aspx/A90312B2-B322-48b3-8A40-34745EF11676", where the last part is application ID.
- UWS Application Configuration API has .NET and COM interfaces. .NET API assembly can be added to Visual Studio projects by looking for UWS.Configuration assembly in the Assemblies list. COM API can used by either by adding reference to "UltiDev Web Server application configuration API for .NET and COM clients" type library, or by instantiating an object of "UltiDev.WebServer.MetabaseComServer.1" ProgId.
- Visual Studio web server replacer utility (WebDevReplacer.exe) allows replacing and restoring default internal Visual Studio debug web server (Cassini/WebDev.WebServer) with UWS Interactive Host. Next time you hit F5 in Visual Studio, UWS Interactive Host will run.
- Static file extension to MIME type map (UserFileExtMimeTypeMap.example.txt, SystemFileExtMimeTypeMap.txt) provide mapping of static file extensions to MIME types. The effective map is the combination of the two. Please only modify "UserFileExtMimeTypeMap.example.txt". UWS service needs to be restarted for MIME type changes to take effect. If you have added something to UserFileExtMimeTypeMap.example.txt, please let us know so we could update the MIME type map for the next release of the product.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
|