ONYX:9.0:Utilisation:Les principaux menus d'administration/en - Historique des versions

Jdieu le 7 janvier 2025 à 09:10

2025-01-07T09:10:47Z

2025-01-07T09:10:38Z

2025-01-07T09:10:27Z

2025-01-07T09:10:10Z

2019-08-28T13:55:30Z

2019-08-28T13:55:23Z

2019-08-28T13:55:15Z

2019-08-28T10:33:52Z

2019-08-28T10:24:58Z

2019-08-28T10:14:59Z

← Version précédente		Version du 7 janvier 2025 à 09:10
Ligne 66 :		Ligne 66 :


−	===Scanfolder Robots===	+	===Scanfolder Robots (Foundation level)===

@@ Ligne 50 : / Ligne 50 : @@
 Most sections will be seen in detail in this documentation, in their corresponding application contexts.
-==Managing Robots==
+==Managing Robots (Foundation level)==
 [[Fichier:OX S GestionRBT.png|centré|sans_cadre|824x824px]]

← Version précédente		Version du 7 janvier 2025 à 09:10
Ligne 17 :		Ligne 17 :
	[[Fichier:OX S Menu AdminCnct.png\|centré\|sans_cadre\|739x739px]]		[[Fichier:OX S Menu AdminCnct.png\|centré\|sans_cadre\|739x739px]]

−	==Configuration management==	+	==Configuration management (Intermediate level)==

@@ Ligne 1 : / Ligne 1 : @@
 <languages/>
-==Introduction==
+==Introduction  (Foundation level)==
 [[Fichier:OX S admin connect.png|centré|sans_cadre|733x733px]]

← Version précédente		Version du 28 août 2019 à 13:55
Ligne 63 :		Ligne 63 :


−	From the perspective of ONYX Server, a robot is an ~~input~~ point in the solution, in other words it is a way for a third-party application to send an execution query. Robots are programs executed as background tasks (Service mode under Windows) to monitor data input, in a folder in the case of Scanfolder robots, or on a network port in the case of listening Servers. Each input file is successively put through the Workflow execution engine to be processed appropriately.	+	From the perspective of ONYX Server, a robot is an entry point in the solution, in other words it is a way for a third-party application to send an execution query. Robots are programs executed as background tasks (Service mode under Windows) to monitor data input, in a folder in the case of Scanfolder robots, or on a network port in the case of listening Servers. Each input file is successively put through the Workflow execution engine to be processed appropriately.

← Version précédente		Version du 28 août 2019 à 13:55
Ligne 57 :		Ligne 57 :
	This interface manages all the robots configured in the solution, whether they are Scanfolder robots or listening servers.		This interface manages all the robots configured in the solution, whether they are Scanfolder robots or listening servers.

−	Upon first installation, the list is blank but it gives access to the ONYX server ~~input~~ points creation/edition menus:	+	Upon first installation, the list is blank but it gives access to the ONYX server entry points creation/edition menus:

@@ Ligne 8 : / Ligne 8 : @@
 • all the settings of the solution,
-• input points creation and configuration in Onyx Server (Scanfolder robots, listening servers, processing queues),
+• entry points creation and configuration in Onyx Server (Scanfolder robots, listening servers, processing queues),
 • execution and routing rules (Workflows) of the output and transfer points of the documents.

← Version précédente		Version du 28 août 2019 à 10:33
Ligne 1 203 :		Ligne 1 203 :


−	Example: the following ~~commads~~ add a spooled file in hold in the INPUT_DATA queue which is owned by the mapadmin user. this spooled file has 15 days of retention time defined in its attributes and it will switch to save status once processed.	+	Example: the following commands add a spooled file in hold in the INPUT_DATA queue which is owned by the mapadmin user. this spooled file has 15 days of retention time defined in its attributes and it will switch to save status once processed.

@@ Ligne 972 : / Ligne 972 : @@
 The four types of events are:
--	Shell_queue: a queue changes status (form Suspended to Ready and vice versa).
+-	Shell_queue: a queue changes status (from Suspended to Ready and vice versa).
 -	Shell_device: a device changes status (from Suspended to Ready and vice versa)

@@ Ligne 919 : / Ligne 919 : @@
 The page unit depends on the type of printer and counter. It is used to check that all the pages of a spooled file were printed.
 If the printer prints documents sheet per sheet (cutsheet), which corresponds to most laser workgroup printers, then the printer counts per physical page. This does not raise any compatibility issues because Mapping also counts per page. the page unit is 1 (by default).
-However, in continuous paper printers which use paper rolls (continuous paper laser, impact or thermal printers), the counter is defined in printed distance (usually in inches). The size of the paper must then be calibrated by specifying the page unit. for instance, on a thermal printer which prints 4 inches long labels, a page unit of 4 must be defined.
+However, in continuous paper printers which use paper rolls (continuous paper laser, impact or thermal printers), the counter is defined in printed distance (usually in inches). The size of the paper must then be calibrated by specifying the page unit. For instance, on a thermal printer which prints 4 inches long labels, a page unit of 4 must be defined.