In the Spotlight October 2012
In TKU October 2012 and TKU September 2012 important performance and architectural updates were made in the Microsoft Internet Information Services - Extended Discovery pattern.
Performance improvements
- New pattern configuration section allows the user to choose the depth of discovery they wish to perform and model only the required SoftwareComponent and/or Detail nodes, which helps to avoid creation of potentially a large number of redundant nodes and assists in maintaining pattern performance.
- Only 'Microsoft IIS Website' and 'Microsoft IIS Web Application' SoftwareComponent node creation is enabled by default as these entities if discovered are synced to the CMDB and are of most use in Collaborative Application Mapping
- Big improvement was made in the approach to the parsing of IIS xml config files. The patterns now split xml files into small chunks (XML DOM nodes) and then obtain information from those using regexes or 'local' xpath queries.
Architectural improvements
- The value of the 'name' attribute for IIS 6 'Web application' Detail/SoftwareComponent was changed
- from: "Microsoft IIS Web Application <Application_Name>"
- to: "Microsoft IIS Web Application <Virtual_Path> on <Website_name>".
This was done in order to make such Detail/SC nodes distinguishable and avoid a big number of similar Details/SCs due to the fact that AppFriendlyName property is not unique and is often left as a default value.
- Added 'Application Pool' modelling as Detail nodes
- IIS 6 'Virtual Directory' Detail is linked directly to 'Website' Detail
- Added "Secure Binding Addresses" attribute for IIS 7 Website
- IIS 6 and IIS 7 architecture
- IIS 6 Website Detail architecture
- IIS 7 Website Detail architecture
SoftwareComponent node architecture
IIS7 and IIS6: 'Microsoft IIS Website' SC -ContainedSoftware> 'Microsoft IIS Webserver' SI
IIS7 and IIS6: 'Microsoft IIS Web Application' SC -ContainedSoftware> 'Microsoft IIS Webserver' SI
Detail node architecture
IIS7 and IIS6: 'Application Pool' DT -Detail> 'Microsoft IIS Webserver' SI
IIS7 and IIS6: 'Web Application' DT -Contained> 'Website' DT -Detail> 'Microsoft IIS Webserver' SI
IIS7: 'Virtual Directory' DT -Contained> 'Web Application' DT -Contained> 'Website' DT -Detail> 'Microsoft IIS Webserver' SI
IIS6: 'Virtual Directory' DT -Contained> 'Website' DT -Detail> 'Microsoft IIS Webserver' SI
Detail/SoftwareComponent attributes
- 'Website' Detail/SoftwareComponent
Attribute name | IIS6 | IIS7 | Comments |
|---|---|---|---|
Name | yes | yes | example: Microsoft IIS Website newsite.com |
Binding Addresses | yes | yes | example: :81:, 172.17.55.139:81:www.site.name, [fe80::6827:4c3b:f9e9:be7e]:80:www.site.name |
Secure Binding Addresses | yes | yes | for 'https' protocol |
Location | yes | no | example: /LM/W3SVC/1542439402, used in IIS 6 for creation link between Websites, WebApps and VirtDirs |
Application Pool | yes | no |
- 'Web application' Detail/SoftwareComponent
Attribute name | IIS6 | IIS7 | Comments |
|---|---|---|---|
Name | yes | yes | example: Microsoft IIS Web Application /vdir_webapp on newsite.com |
Application Pool | yes | yes | |
Virtual Path | yes | yes | is a path related to Website, thus full url to WebApp is: '<website_name>/<Virtual Path>', example 'newsite.com/vdir_webapp' |
Location | yes | no | example: /LM/W3SVC/1542439402/root/vdir_webapp, used in IIS 6 for creation link between Websites, WebApps and VirtDirs |
Physical Path | yes | no | example: C:\some\path\to\webapp |
Application Name | yes | no | created from AppFriendlyName property of IIsWebVirtualDir or IIsWebDirectory DOM node |
- 'Virtual Directory' Detail/SoftwareComponent
Attribute name | IIS6 | IIS7 | Comments |
|---|---|---|---|
Name | yes | yes | example: Microsoft IIS Virtual Directory /vdir_vdir on newsite.com |
Virtual Path | yes | yes | |
Physical Path | yes | yes | example: C:\some\path\to\virtdir |
Location | yes | no | example: /LM/W3SVC/1542439402/root/vdir_vdir, is used in IIS 6 for creation link between Websites, WebApps and VirtDirs |