OS4X Enterprise - Job management - Revision history

Admin: /* XML view */

2019-04-11T12:58:14Z

XML view

2018-09-11T14:46:11Z

Requirements

2018-09-11T14:44:43Z

Managing jobs interactively

2017-08-08T13:58:44Z

Restart job

2017-08-08T13:57:04Z

Restart job

2017-08-08T13:27:28Z

2012-05-01T11:27:10Z

Managing jobs interactively

2012-05-01T11:22:55Z

2012-02-14T11:02:19Z

Cancel job

2012-02-14T11:02:05Z

Restart job

@@ Line 73: / Line 73: @@
 ==== XML view ====
 Displaying and editing XML entries of OS4X jobs is possible via links in the job detail view. There are three access modes available:
-*XML: interpreted form, formatted via a stylesheet saved in the database. This output is a human-readable view of the XML content.
+*XML: interpreted form, formatted via a stylesheet saved in the database. This output is a human-readable view of the XML content. The default view contains a selected view of items; if all nodes are required, the icon "<i class="fa fa-eye" aria-hidden="true"></i> Show all nodes" is capable to view all nodes.
 [[Image:Job-actual-xml-html-view.png]]
 *source: Sourcecode of the XML for professional interpretation.

@@ Line 1: / Line 1: @@
 == Requirements ==
-In order to manage OS4X Enterprise jobs, OS4X Enterprise must be enabled via "Configuration" -> "OS4X Enterprise" -> "[[OS4X_Core_configuration#is_OS4X_Enterprise_installed.3F|Is OS4X Enterprise installed?]]". After enabling this checkbox, the menu on the left panel expands and the category "Jobs" contains "Send jobs" and "Receive jobs":
+In order to manage OS4X Enterprise jobs, OS4X Enterprise must be enabled via "Configuration" -> "OS4X Enterprise" -> "[[OS4X_Core_configuration#is_OS4X_Enterprise_installed.3F|Is OS4X Enterprise installed?]]". After enabling this checkbox, the menu on the left panel expands and the category "Jobs" contains "Send jobs", "Receive jobs" and "All jobs":
 [[Image:Os4x-menu-jobs.png]]

@@ Line 30: / Line 30: @@
 == Managing jobs interactively ==
-Given a job list (either send of receive jobs), the web interface shows a table of all jobs:
+Given a job list (either send, receive or all jobs), the web interface shows a table of all jobs:
 [[Image:Sample-joblist-receive-jobs.png]]

@@ Line 84: / Line 84: @@
 === Restart job ===
-This binary "[[os4xrestart]]" is internally used by the web interface to restart jobs.
+This binary "<code>[[os4xrestart]]</code>" is internally used by the web interface to restart jobs.
 === Cancel job ===

@@ Line 84: / Line 84: @@
 === Restart job ===
-The binary
+This binary "[[os4xrestart]]" is internally used by the web interface to restart jobs.
 === Cancel job ===

← Older revision		Revision as of 13:27, 8 August 2017
Line 112:		Line 112:
	</pre>		</pre>
	This binary is internally used by the web interface.		This binary is internally used by the web interface.
		+
		+
		+	[[Category:OS4X Enterprise]]

@@ Line 33: / Line 33: @@
 [[Image:Sample-joblist-receive-jobs.png]]
 The columns contain links to more actions:
-*job number (left): link to job overview and management
+*info icon (left): link to job overview and management
 *sender / receiver: all separate entities (recipient, department, location and partner) are links to the corresponding "edit" pages
 *status: a link to display only jobs of exactly that status
 === Job details ===
-When clicking on the job number or date (tooltip'ed as "''show job #...''"), the job details get displayed:
+When clicking on the job info icon, the job details get displayed:
 === Details and actions ===

← Older revision		Revision as of 11:22, 1 May 2012
Line 71:		Line 71:

	The actual plugin status shows the status of the job and, if in execution of a synchronous or asynchronous plugin, the actual plugin name.		The actual plugin status shows the status of the job and, if in execution of a synchronous or asynchronous plugin, the actual plugin name.
−
−	~~==== Plugin logs (graphical) ====~~
−	~~[[Image:Job-view-details-plugin-logs.png]]~~
−
−	~~If GD2 is available as PHP extension on the webserver, a graphical view of the plugin logs is available for scrolling through them.~~

	==== Plugin logs (textual) ====		==== Plugin logs (textual) ====

@@ Line 113: / Line 113: @@
 The binary
   os4xcancel
-sets a cancel bit in the database to abort the job after the actual plugin being executed. If the actual plugin being executed is an asynchronous plugin, this asynchronous plugin will be executed with the parameter "''-c''" and the job number in order to let it abort cleanly. See [[OS4X_Server-side_plugin_philosophy|OS4X Server side plugin philosophy]].
+in the configured [[OS4X_Core_configuration#binary_installation_directory|binary installation directory]] sets a cancel bit in the database to abort the job after the actual plugin being executed. If the actual plugin being executed is an asynchronous plugin, this asynchronous plugin will be executed with the parameter "''-c''" and the job number in order to let it abort cleanly. See [[OS4X_Server-side_plugin_philosophy|OS4X Server side plugin philosophy]].
 The only paramater is either the job number (in numeric format) or an XML file describing the OS4X job with a standard XML schema:

@@ Line 97: / Line 97: @@
 The binary
   os4xrestart
-manages the job to use its initial XML to restart the job with the configured plugin group of the recipient.
+in the configured [[OS4X_Core_configuration#binary_installation_directory|binary installation directory]] manages the job to use its initial XML to restart the job with the configured plugin group of the recipient.
 *Outgoing jobs: restart the send plugin group of the recipient
 *Incoming jobs: restart the receive plugin group of the recipient