Dev:Partner creation processes - Revision history

Stefanseiler: /* 1. Pre-Login process */

2025-12-15T10:07:36Z

1. Pre-Login process

← Older revision		Revision as of 10:07, 15 December 2025
Line 58:		Line 58:
	After a remote digital is registered as known business participant with its user(s) and the remote authentication is enabled on the remote digital, the user can log-in using the portals for which this user is registered		After a remote digital is registered as known business participant with its user(s) and the remote authentication is enabled on the remote digital, the user can log-in using the portals for which this user is registered

	====== 1. Pre-~~Login~~ process ======		====== 1. Pre-Authentication process ======
	The user navigates his browser to the portal startup page, which:		The user navigates his browser to the portal startup page, which:

Stefanseiler: /* How digital creation generally works */

2025-12-10T14:06:18Z

How digital creation generally works

← Older revision		Revision as of 14:06, 10 December 2025
Line 52:		Line 52:
	# The endpoint invoked is an app operating under the remote realm concierge digital, which		# The endpoint invoked is an app operating under the remote realm concierge digital, which
	#* issues a [https://aw.b-op.org/mediawiki/index.php/Realm_Root_Executor_Agent_(RRE) RRE-Command] to create the new digital from a digital creation template, which controls the creation process.		#* issues a [https://aw.b-op.org/mediawiki/index.php/Realm_Root_Executor_Agent_(RRE) RRE-Command] to create the new digital from a digital creation template, which controls the creation process.
			#* Builds trust relations with the intended digitals (other PAX portals, SARA)
	#* returns synchronously the result of the operation (OK/NOK, creation info)		#* returns synchronously the result of the operation (OK/NOK, creation info)

Stefanseiler: /* Distributed infrastructure */

2025-12-10T14:05:16Z

Distributed infrastructure

← Older revision		Revision as of 14:05, 10 December 2025
Line 6:		Line 6:
	A typical setup for Kordeus.PAX ecosystem looks like this:		A typical setup for Kordeus.PAX ecosystem looks like this:

	* '''~~Airline realms~~''' - This realm hosts the core digitals of the airlines and the operation center digitals. This realm runs the backend applications (SARA, Admin-Tools)		* '''Medical Operations Realm''' - This realm hosts the core digitals of the airlines and the operation center digitals. This realm runs the backend applications (SARA, Admin-Tools)
	* '''~~Partner realms~~''' - These realms host their business partners, holding the data of them (PAX, Travel Partners, Delivery Partners)		* '''Medial Cloud Realm(s)''' - These realms host their business partners, holding the data of them (PAX, Travel Partners, Delivery Partners)
	* '''Portal ~~realms~~''' - These realms are operating the portals and are focused on being publicly accessible. Typically they are one realm per portal to scale performance and keep these portals independent from each other.		* '''Portal Operation Realms''' - These realms are operating the portals and are focused on being publicly accessible. Typically they are one realm per portal to scale performance and keep these portals independent from each other.

	== Digital creation ==		== Digital creation ==

Stefanseiler: /* Distributed infrastructure */

2025-12-10T14:04:07Z

Distributed infrastructure

← Older revision		Revision as of 14:04, 10 December 2025
Line 1:		Line 1:

	== Distributed infrastructure ==		== Distributed infrastructure ==
			[[File:Example Realm Setup.png\|thumb\|Example Realm Setup]]
	[[Kordeus.PAX]] operates in a distributed data ecosystem, which means that different b-op digitals can reside wherever they want to reside and still the network functions as if they were working together as one system according to their trust-relations.		[[Kordeus.PAX]] operates in a distributed data ecosystem, which means that different b-op digitals can reside wherever they want to reside and still the network functions as if they were working together as one system according to their trust-relations.

Stefanseiler at 12:37, 10 December 2025

2025-12-10T12:37:40Z

← Older revision		Revision as of 12:37, 10 December 2025
Line 1:		Line 1:

			== Distributed infrastructure ==
			[[Kordeus.PAX]] operates in a distributed data ecosystem, which means that different b-op digitals can reside wherever they want to reside and still the network functions as if they were working together as one system according to their trust-relations.

			A typical setup for Kordeus.PAX ecosystem looks like this:

			* '''Airline realms''' - This realm hosts the core digitals of the airlines and the operation center digitals. This realm runs the backend applications (SARA, Admin-Tools)
			* '''Partner realms''' - These realms host their business partners, holding the data of them (PAX, Travel Partners, Delivery Partners)
			* '''Portal realms''' - These realms are operating the portals and are focused on being publicly accessible. Typically they are one realm per portal to scale performance and keep these portals independent from each other.

	== Digital creation ==		== Digital creation ==
	There are multiple parties in the Kordeus.PAX ecosystem, which can create digitals for partners, to allow a distributed collaboration model.		There are multiple parties in the Kordeus.PAX ecosystem, which can create digitals for partners, to allow a distributed collaboration model.

Stefanseiler at 12:31, 10 December 2025

2025-12-10T12:31:43Z

← Older revision		Revision as of 12:31, 10 December 2025
Line 1:		Line 1:
	~~Tehre is no portal which is used to create digitals~~. ~~Instead it means pages of~~ PAX~~-Portal and MOC-SARA~~, which ~~have the power to~~ create digitals ~~on target realms with predefined configurations~~.
			== Digital creation ==
			There are multiple parties in the Kordeus.PAX ecosystem, which can create digitals for partners, to allow a distributed collaboration model.

			====== Which digital type can create others? ======
	{\| class="wikitable"		{\| class="wikitable"
	~~\|+Which digital type can create others?~~
	\|-		\|-
	!Created digital type ➡️		!Created digital type ➡️
Line 26:		Line 29:
	\|🔑 Login		\|🔑 Login
	\|}		\|}
	Creation of a new digital means that ~~as well a~~ user ~~is created~~. ~~In the SAR~~-~~Collaboration~~, ~~this means~~, ~~that these users~~ are ~~propagated to the known other portals, so these digitals can login at the desired portals as well.~~		Creation of a new digital means that it is deployed with:

			* at least one user
			* trust relations are established with other players (e.g. other known PAX-Portal digitals, Operation center digitals or Travel partner digitals)
			* applications deployed, which are required for operations

	=== How digital creation generally works ===		=== How digital creation generally works ===

Stefanseiler: Stefanseiler moved page SARA.PartnerCreationPortal to Dev:Partner creation processes without leaving a redirect

2025-12-10T12:28:18Z

Stefanseiler moved page SARA.PartnerCreationPortal to Dev:Partner creation processes without leaving a redirect

← Older revision	Revision as of 12:28, 10 December 2025
(No difference)

Stefanseiler: /* How digital creation generally works */

2025-12-09T14:34:15Z

How digital creation generally works

← Older revision		Revision as of 14:34, 9 December 2025
Line 34:		Line 34:
	# With this api-key and a json which holds the information of the digital to create (type, email, ... ) it invokes the endpoint and waits for a creation response.		# With this api-key and a json which holds the information of the digital to create (type, email, ... ) it invokes the endpoint and waits for a creation response.
	# The endpoint invoked is an app operating under the remote realm concierge digital, which		# The endpoint invoked is an app operating under the remote realm concierge digital, which
	#* issues a RRE-Command to create the new digital from a digital creation template, which controls the creation process.		#* issues a [https://aw.b-op.org/mediawiki/index.php/Realm_Root_Executor_Agent_(RRE) RRE-Command] to create the new digital from a digital creation template, which controls the creation process.
	#* returns synchronously the result of the operation (OK/NOK, creation info)		#* returns synchronously the result of the operation (OK/NOK, creation info)

Stefanseiler: /* How digital creation generally works */

2025-12-09T14:32:10Z

How digital creation generally works

← Older revision		Revision as of 14:32, 9 December 2025
Line 29:		Line 29:

	=== How digital creation generally works ===		=== How digital creation generally works ===
			The local digital

			# receives a digital creation api-key per target realm in which to create a local digital which allows
			# With this api-key and a json which holds the information of the digital to create (type, email, ... ) it invokes the endpoint and waits for a creation response.
			# The endpoint invoked is an app operating under the remote realm concierge digital, which
			#* issues a RRE-Command to create the new digital from a digital creation template, which controls the creation process.
			#* returns synchronously the result of the operation (OK/NOK, creation info)

	=== How login works in distributed environments (here: Kordeus.PAX) ===		=== How login works in distributed environments (here: Kordeus.PAX) ===

Stefanseiler: /* See also */

2025-12-09T14:25:39Z

@@ Line 1: / Line 1: @@
-This portal is a kordeus portal, which allows the creation of digitals on target platforms with predefined configurations. It allows authorized users to create digitals from Digital Creation Templates.
+Tehre is no portal which is used to create digitals. Instead it means pages of PAX-Portal and MOC-SARA, which have the power to create digitals on target realms with predefined configurations.
 {| class="wikitable"
 |+Which digital type can create others?
@@ Line 25: / Line 25: @@
+|
 |🔑 Login
 |}
 == See also ==
 * [[Kordeus.PAX]]