IIS configuration - Revision history

Thomas Linder Puls: category

2016-03-04T09:52:00Z

Thomas Linder Puls: Skype conflict

2014-08-01T11:37:10Z

Skype conflict

← Older revision		Revision as of 13:37, 1 August 2014
Line 91:		Line 91:

	Anonymous/Windows access is controlled from the '''Authentification''' icon		Anonymous/Windows access is controlled from the '''Authentification''' icon

			=== Skype HTTP/HTTPS Conflict ===
			{{:Include/SkypeHTTPConflict}}

	=== See also ===		=== See also ===

Thomas Linder Puls: links/line breaks

2014-08-01T10:55:02Z

links/line breaks

← Older revision		Revision as of 12:55, 1 August 2014
Line 1:		Line 1:
	This tutorial describes how to perform various configurations of the Microsoft Internet Information Services (IIS).		This tutorial describes how to perform various configurations of the Microsoft Internet Information Services (IIS).

	The tutorial will be based on the settings needed for the <vp>jsonRpcService_isApi</vp> in the <vp>webRPC</vp> example directory, but most of these things will be relevant and easily adjusted to other related cases.		The tutorial will be based on the settings needed for the <vp>jsonRpcService_isApi</vp> in the <vp>webRPC</vp> example directory (see [[Web Services]]), but most of these things will be relevant and easily adjusted to other related cases.

	The <vp>jsonRpcService_isApi</vp> project creates is an ISAPI plug-in (dll), which implements a JSON-RPC service. The example also contains some related HTML, CSS and JavaScript files that must be accessible to the client browser. So the IIS needs to be configured for two purposes:		The <vp>jsonRpcService_isApi</vp> project creates is an ISAPI plug-in (dll), which implements a JSON-RPC service. The example also contains some related HTML, CSS and JavaScript files that must be accessible to the client browser. So the IIS needs to be configured for two purposes:
Line 48:		Line 48:
	[[Image:IISM_add_webRPC_1.png]]		[[Image:IISM_add_webRPC_1.png]]
	[[Image:IISM_add_webRPC_2.png]]		[[Image:IISM_add_webRPC_2.png]]

	The '''Alias''' defines name relative to the '''Path''' in the WEB, and '''Physical path''' defines the disk location that this path corresponds to, in this case		The '''Alias''' defines name relative to the '''Path''' in the WEB, and '''Physical path''' defines the disk location that this path corresponds to, in this case
	'''http:<nowiki />//localhost/webRPC''' will correspond to '''C:\webRPC\web''', which is where the html, css and JavaScript files for the example are placed (in my case).		'''http:<nowiki />//localhost/webRPC''' will correspond to '''C:\webRPC\web''', which is where the html, css and JavaScript files for the example are placed (in my case).
Line 90:		Line 91:

	Anonymous/Windows access is controlled from the '''Authentification''' icon		Anonymous/Windows access is controlled from the '''Authentification''' icon

			=== See also ===

			[[Web Services]]

	[[Category:Tutorials]]		[[Category:Tutorials]]

Thomas Linder Puls: extend

2014-08-01T10:47:40Z

extend

← Older revision		Revision as of 12:47, 1 August 2014
Line 48:		Line 48:
	[[Image:IISM_add_webRPC_1.png]]		[[Image:IISM_add_webRPC_1.png]]
	[[Image:IISM_add_webRPC_2.png]]		[[Image:IISM_add_webRPC_2.png]]
			The '''Alias''' defines name relative to the '''Path''' in the WEB, and '''Physical path''' defines the disk location that this path corresponds to, in this case
			'''http:<nowiki />//localhost/webRPC''' will correspond to '''C:\webRPC\web''', which is where the html, css and JavaScript files for the example are placed (in my case).

	=== ISAPI setup ===		=== ISAPI setup ===

			For the example the path '''http:<nowiki />//localhost/webRPC/jsonrpc''' should run the <vp>jsonRpcService_isApi</vp> ISAPI dll. So we add an application below the webRPC virtual directory:

	[[Image:IISM_add_jsonrpc_1.png]]		[[Image:IISM_add_jsonrpc_1.png]]

			Make sure that the application uses the desired Application Pool. We don't intend to use the physical path, but the IIS will place a web.config file in that directory. It could be a good idea to create an otherwise empty an unused directory for the purpose, but here we just use the example root directory:
	[[Image:IISM_add_jsonrpc_2.png]]		[[Image:IISM_add_jsonrpc_2.png]]

			With the application in place it is time to configure the ISAPI. Select '''Handler Mappings''':

	[[Image:IISM_handlerMapping_1.png]]		[[Image:IISM_handlerMapping_1.png]]

			And then add a "Script Map", matching everything and pointing to the ISAPI dll:

	[[Image:IISM_handlerMapping_2.png]]		[[Image:IISM_handlerMapping_2.png]]
	[[Image:IISM_handlerMapping_3.png]]		[[Image:IISM_handlerMapping_3.png]]


			The JSON-RPC requests does not belong to "script" files on our disk so we have to switch off the switch off "Invoke handler only if request is mapped to''' setting in the '''Request Restrictions...''' :

	[[Image:IISM_handlerMapping_4.png]]		[[Image:IISM_handlerMapping_4.png]]

			When OK-ing the changes you should also say OK to this dialog (if it appears):

	[[Image:IISM_handlerMapping_5.png]]		[[Image:IISM_handlerMapping_5.png]]

			=== User Rights ===

			When the IIS run it will access various files as a certain Windows user, this user must have sufficient rights to the files.

			Which user is determined like this:

			* If a '''Connect as..." user is set for the virtual directory or application then that user will access the files
			* Otherwise (if '''Pass-through authentication is used):
			** If annoymous access is allowed to the virtual directory/application then some IUSER_... is will access the files
			** If some Windows authentification is used the windows user from the connection will will access the files

			Anonymous/Windows access is controlled from the '''Authentification''' icon

	[[Category:Tutorials]]		[[Category:Tutorials]]

Thomas Linder Puls: extend

2014-07-31T15:25:04Z

extend

← Older revision		Revision as of 17:25, 31 July 2014
Line 50:		Line 50:

	=== ISAPI setup ===		=== ISAPI setup ===

			[[Image:IISM_add_jsonrpc_1.png]]
			[[Image:IISM_add_jsonrpc_2.png]]

	[[Image:IISM_handlerMapping_1.png]]		[[Image:IISM_handlerMapping_1.png]]

Thomas Linder Puls: extend

2014-07-31T15:19:48Z

extend

@@ Line 8: / Line 8: @@
 All IIS configuration takes place in the '''Internet Information Services Manager'''.
 === Application Pool ===
@@ Line 20: / Line 34: @@
 [[Image:IISM_addAppPool_1.png]]
 [[Image:IISM_addAppPool_2.png]]
 Notice that by default (on a 64 bit platform) the application pool cannot run 32 bit programs, so you may need to switch this "Advanced Setting" on:
@@ Line 25: / Line 41: @@
 [[Image:IISM_32bit_1.png]]
 [[Image:IISM_32bit_2.png]]

Thomas Linder Puls: Init

2014-07-31T12:25:37Z

Init

New page

This tutorial describes how to perform various configurations of the Microsoft Internet Information Services (IIS).

The tutorial will be based on the settings needed for the <vp>jsonRpcService_isApi</vp> in the <vp>webRPC</vp> example directory, but most of these things will be relevant and easily adjusted to other related cases.

The <vp>jsonRpcService_isApi</vp> project creates is an ISAPI plug-in (dll), which implements a JSON-RPC service. The example also contains some related HTML, CSS and JavaScript files that must be accessible to the client browser. So the IIS needs to be configured for two purposes:
* A file provider
* An ISAPI service

All IIS configuration takes place in the '''Internet Information Services Manager'''.

=== Application Pool ===

The ISAPI service must run in a suitable Application Pool. Application Pools provide process isolation between various parts of the IIS, which gives the following advantages:
* It makes the overall IIS more robust as problem in one application pool is less likely to have impact on the other application pools (exhausting the entire system will of course cross interfere)
* Each pool can have different settings (of for example .net platform)
* Each pool can be restarted independent of the other pools

To create an application pool, select "Add Application Pool..." in the context menu on the '''Application Pools'''. Pools suitable for Visual Prolog programs, does not require any .net platform, and it is recommended to have no .net support at all to minimize the interference risks. You give it a name and (unless you for other reasons need it) select "No Managed Code" (the rest you leave as it is):

[[Image:IISM_addAppPool_1.png]]
[[Image:IISM_addAppPool_2.png]]

Notice that by default (on a 64 bit platform) the application pool cannot run 32 bit programs, so you may need to switch this "Advanced Setting" on:

[[Image:IISM_32bit_1.png]]
[[Image:IISM_32bit_2.png]]

← Older revision		Revision as of 11:52, 4 March 2016
Line 99:		Line 99:
	[[Web Services]]		[[Web Services]]

	[[Category:~~Tutorials~~]]		[[Category:Internet]]