Os4x create enterprise sendjob - Revision history

Admin: /* Execution syntax */

2021-12-02T07:07:32Z

Execution syntax

2021-09-27T12:15:13Z

Create OS4X Enterprise send jobs in batch mode

2014-12-04T14:41:30Z

Formatting the information

2014-12-04T14:36:14Z

File(s)

2014-12-04T13:17:28Z

File(s)

2013-02-22T16:20:05Z

Execution syntax

2011-04-01T15:04:42Z

Example

2011-04-01T15:04:13Z

2011-04-01T15:03:31Z

Create OS4X Enterprise send jobs in batch mode

2011-04-01T14:47:11Z

Sending two file from user "test" to user a recipient without a configured send plugin group, with verbose output

@@ Line 85: / Line 85: @@
 *-x: the above described XML file
 *-d: verbose mode, don't run any program in the background, display more information
 === Examples ===

← Older revision		Revision as of 12:15, 27 September 2021
Line 3:		Line 3:

	Executing the binary is possible with a valid OS4X Enterprise and OS4X Enterprise Lite license.		Executing the binary is possible with a valid OS4X Enterprise and OS4X Enterprise Lite license.
		+
		+	Since OS4X release 2021-08-23, this binary can be called as "<code>os4x_create_enterprise_recjob</code>" (which is a symlink to "<code>os4x_create_enterprise_sendjob</code>" to create a receive job instead of a send job.

	== What you need ==		== What you need ==

@@ Line 57: / Line 57: @@
        <filename>os4x_licinfo</filename>
        <absolute_filename>/opt/os4x/bin/os4x_licinfo</absolute_filename>
-       <file_comment>filecomment</file_comment>
+       <file_comment>Filetransmitted with fixed record length of 128 bytes</file_comment>
        <compression/>
        <plugin_output/>
      </job_file>
 </OS4X_sendjob>

@@ Line 30: / Line 30: @@
 *compression: depending on your recipient, you may add an information about how the file is being compressed. This attribute may be overwritten by compression plugins in the OS4X job process lifecycle.
 *plugin_output: Files may be created by plugins or tools, which may create their own output (such as converts, exporters etc.). This node may contain textual information for the file (which may be analyzed by another plugin for further tasks).
-*os4xeq_params: an optional string containing parameters used for enqueueing files to the OS4X send queue (see parameters of program "[[OS4X_Core_binaries#os4xeq|os4xeq]]").
+*os4xeq_params: an optional string containing parameters used for enqueueing files to the OS4X send queue (see parameters of program "[[OS4X_Core_binaries#os4xeq|os4xeq]]"). Supported parameters are (generally spoken) all other than "<code>-p</code>", "<code>-f</code>", "<code>-v</code>", "<code>-c</code>", "<code>-i</code>" and "<code>-j</code>".
 == Formatting the information ==

@@ Line 30: / Line 30: @@
 *compression: depending on your recipient, you may add an information about how the file is being compressed. This attribute may be overwritten by compression plugins in the OS4X job process lifecycle.
 *plugin_output: Files may be created by plugins or tools, which may create their own output (such as converts, exporters etc.). This node may contain textual information for the file (which may be analyzed by another plugin for further tasks).
 == Formatting the information ==

@@ Line 78: / Line 78: @@
 The parameters are:
 *-C: optional config file in case you don't want to use the default "<code>/etc/os4x.con</code>"
-*-i: the server ID overriding the configured one in "<code>/etc/os4x.con</code>"
+*-i: the server ID overriding the configured one in "<code>/etc/os4x.conf</code>"
 *-x: the above described XML file
 *-d: verbose mode, don't run any program in the background, display more information

@@ Line 82: / Line 82: @@
 *-d: verbose mode, don't run any program in the background, display more information
-=== Example ===
+=== Examples ===
-The examples are using the XML file from above. The user "test" exists in the databse, also the recipient user with the database index value "3".
+These examples are using the XML file from above. The user "test" exists in the databse, also the recipient user with the database index value "3".
 ==== Sending two file from user "test" to user "test" ====

@@ Line 1: / Line 1: @@
 = Create OS4X Enterprise send jobs in batch mode =
 OS4X Enterprise offers a wide range to automatism, and incoming jobs execute configurable plugins dynamically depending on the recipient. But what about outgoing jobs? That's where this tools fills the gap.
 == What you need ==

@@ Line 85: / Line 85: @@
 ==== Sending two file from user "test" to user "test" ====
 <pre>
-imac-i7:bin os4x$ ./os4x_create_enterprise_sendjob -x /tmp/os4x-1.xml
+imac-i7:bin os4x$ /opt/os4x/bin/os4x_create_enterprise_sendjob -x /tmp/os4x-1.xml
 </pre>
 No more output will be written.
@@ Line 91: / Line 91: @@
 ==== Sending two file from user "test" to user "test" with verbose output ====
 <pre>
-imac-i7:bin os4x$ ./os4x_create_enterprise_sendjob -d -x /tmp/os4x-1.xml
+imac-i7:bin os4x$ /opt/os4x/bin/os4x_create_enterprise_sendjob -d -x /tmp/os4x-1.xml
 License valid
 Enabled verbose mode
@@ Line 106: / Line 106: @@
 <pre>
-imac-i7:bin os4x$ ./os4x_create_enterprise_sendjob -d -x /tmp/os4x-3.xml
+imac-i7:bin os4x$ /opt/os4x/bin/os4x_create_enterprise_sendjob -d -x /tmp/os4x-3.xml
 License valid
 Enabled verbose mode

@@ Line 115: / Line 115: @@
 ERROR: No plugin group defined as send plugin group for recipient -> aborting job.
 </pre>
-An OS4X send job has been created, but it has reached the status "aborted". You may reconfigure the corresponding recipient (i.e. at company level) and restart the job.
+An OS4X send job has been created with the ID 638, but it has reached the status "aborted". You may reconfigure the corresponding recipient (i.e. at company level) and restart the job.