I2Rest Gates - Revision history

Pavel.lobko at 11:32, 9 July 2020

2020-07-09T11:32:16Z

Alexei.baranov at 18:51, 21 May 2020

2020-05-21T18:51:37Z

Alexei.baranov at 18:51, 21 May 2020

2020-05-21T18:51:27Z

Alexei.baranov at 18:51, 21 May 2020

2020-05-21T18:51:05Z

Alexei.baranov at 18:50, 21 May 2020

2020-05-21T18:50:18Z

Pavel.lobko: /* Management Gate */

2020-05-21T12:11:35Z

‎Management Gate

Alexei.baranov: /* Main Gate */

2020-04-08T12:45:46Z

‎Main Gate

Alexei.baranov at 18:39, 2 April 2020

2020-04-02T18:39:29Z

Alexei.baranov at 18:39, 2 April 2020

2020-04-02T18:39:03Z

Alexei.baranov at 18:38, 2 April 2020

2020-04-02T18:38:43Z

← Older revision		Revision as of 11:32, 9 July 2020
Line 1:		Line 1:
	{{DISPLAYTITLE:i2Rest Server Architecture}}		{{DISPLAYTITLE:i2Rest Server Architecture}}
−	~~<Couple of words about the server's purpose, platform and main goal>~~
−
	__TOC__		__TOC__

← Older revision		Revision as of 18:51, 21 May 2020
Line 1:		Line 1:
	{{DISPLAYTITLE:i2Rest Server Architecture}}		{{DISPLAYTITLE:i2Rest Server Architecture}}
−
	<Couple of words about the server's purpose, platform and main goal>		<Couple of words about the server's purpose, platform and main goal>

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:i2Rest Server Architecture}}
-= i2Rest Server Overview =
 <Couple of words about the server's purpose, platform and main goal>

@@ Line 2: / Line 2: @@
 = i2Rest Server Overview =
 <Couple of words about the server's purpose, platform and main goal>
 = i2Rest Gates =

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:i2Rest Gates}}
+{{DISPLAYTITLE:i2Rest Server Architecture}}
 = i2Rest Gates =
 i2Rest  Server is a high-performance multi-threaded server which has three separate "'''''Gates'''''" allocated for processing requests of various types. Each gate itself is a server with its own listener, internal queue for incoming requests, and a number of "worker" threads to process this queue. Gate servers can communicate with each other and they have a shared memory with common resources.

← Older revision		Revision as of 12:11, 21 May 2020
Line 29:		Line 29:

	== Management Gate ==		== Management Gate ==
−	<div id="management_gate"></div>This gate provides access to the set of [[~~i2Rest API#management_functions~~\|i2Rest Management APIs]]. Access to this gate requires access token with '[[i2Rest scopes#management_functions\|management_functions]]' in its scope. Management Gate endpoint and Main gate endpoint must be different for the security reasons. If you plan to use [[i2Rest Client]] command to execute management functions from the terminal of the same IBM i where i2Rest Server is running, it is recommended to use <tt>file:</tt> endpoint here.	+	<div id="management_gate"></div>This gate provides access to the set of [[Management_APIs\|i2Rest Management APIs]]. Access to this gate requires access token with '[[i2Rest scopes#management_functions\|management_functions]]' in its scope. Management Gate endpoint and Main gate endpoint must be different for the security reasons. If you plan to use [[i2Rest Client]] command to execute management functions from the terminal of the same IBM i where i2Rest Server is running, it is recommended to use <tt>file:</tt> endpoint here.

@@ Line 12: / Line 12: @@
 == Main Gate ==
-<div id="main_gate"></div>This gate is used for serve requests from common clients. It is recommended [[gate object|to setup]] secured https url for this gate. All OpenAPI calls for i2Rest [[i2Rest API#run_command|run_command]] and [[i2Rest API#run_program|run_program]] APIs must go to this gate. API run_command requires mandatory authentication with OAuth2, while run_program APIs does not necessarily require OAuth2 authentication. You can define it in pcml file describing particular run_program API. Upon receive request without required OAuth2 authentication token, Main Gate will respond to client with 401 Unauthenticated response code. In this case client can start one of available OAuth2 flows to obtain authentication token.
+<div id="main_gate"></div>This gate is used for serve requests from common clients. It is recommended [[gate object|to setup]] secured https url for this gate. All OpenAPI calls for i2Rest [[i2Rest API#run_command_API|run_command]] and [[i2Rest API#run_program_API|run_program]] APIs must go to this gate. API run_command requires mandatory authentication with OAuth2, while run_program APIs does not necessarily require OAuth2 authentication. You can define it in pcml file describing particular run_program API. Upon receive request without required OAuth2 authentication token, Main Gate will respond to client with 401 Unauthenticated response code. In this case client can start one of available OAuth2 flows to obtain authentication token.
 === Session ===

← Older revision		Revision as of 18:39, 2 April 2020
Line 1:		Line 1:
	{{DISPLAYTITLE:i2Rest Gates}}		{{DISPLAYTITLE:i2Rest Gates}}
−	~~= i2Rest Server Gates =~~

	i2Rest Server is a high-performance multi-threaded server which has three separate "'''''Gates'''''" allocated for processing requests of various types. Each gate itself is a server with its own listener, internal queue for incoming requests, and a number of "worker" threads to process this queue. Gate servers can communicate with each other and they have a shared memory with common resources.		i2Rest Server is a high-performance multi-threaded server which has three separate "'''''Gates'''''" allocated for processing requests of various types. Each gate itself is a server with its own listener, internal queue for incoming requests, and a number of "worker" threads to process this queue. Gate servers can communicate with each other and they have a shared memory with common resources.

← Older revision		Revision as of 18:38, 2 April 2020
Line 1:		Line 1:
		+	{{DISPLAYTITLE:i2Rest Gates}}
	= i2Rest Server Gates =		= i2Rest Server Gates =