OS4X Core binaries

os4xeq / os4xeq2

Add a file to the send queue or enqueue an EERP message to the EERP queue. If the addressed partner is configured for OFTP2, special file handling is available for the following virtual filenames:

• ODETTE_CERTIFICATE_REQUEST: request certificate from remote partner
• ODETTE_CERTIFICATE_DELIVER: send the configured certificate to the partner (also used by updating certificate)

The used cipher suite for automatic certificate is "#1: 3des_ede_cbc_3key, RSA, SHA-1'.

When an existing send queue entry already exists (server ID doesn't matter!), then it will be checked if it's blocked. If it's blocked, it will be unblocked, otherwise it will be removed and newly added. If any process is running for that send queue entry (i.e. a process in the status "taken by send queue"), it will recognize that its send queue entry was removed and it will cleanly shut down.

The parameter "-m" accepts a relative filename (without path information) for moving or copying the resulting file (which is then added to the send queue) to the OS4X's temporary directory with the given name.

input parameters

• -h: printf this help text
• -C <configfile>: use given config file (default: /etc/os4x.conf)
• -p <partner shortname>
• -f <filename with absolute path>
• -v <virtual filename>
• -c <comment (max. 255 chars./without special chars.)>
• -q <alternative SSID for this file (originator)>
• -r <alternative SSID for this file (destination)>
• -s <alternative SFID for this file (originator)>
• -t <alternative SFID for this file (destination)>
• -w <alternative password for this file (originator)>
• -x <alternative password for this file (destination)>
• -u <priority, default: 0>
• -i <server ID, default: 0>
• -P: add file passive to send queue (let partner fetch it from remote)
• -d: <optional file description in OFTPv2 session>
• -m <filename> move temporarily created OFTP2 file to OS4X's temporary directory with the given name
• -V: print out version and exit
• -F <n>: send file in fixed record length mode with n bytes maximum record length; overrides binary data transfer mode
• -G <n>: send file in variable record length mode with n bytes maximum record length; overrides binary data transfer mode

In order to enqueue an EERP message, the following parameters are available:

• -E: activate EERP mode (instead of file mode)
• -T <timestamp in format HHMMSSCCCC, i.e. 1435570001>
• -D <datestamp in format YYYYmmdd, i.e. 20081230>
• -z <destination SFID>
• -o <originator SFID>

examples

• enqueue the file '/tmp/testfile' to partner 'c-works', using virtual filename 'testfile':

./os4xeq -p c-works -f /tmp/testfile -v testfile

• enqueue the file '/tmp/testfile' to partner 'c-works', using ENGDAT light virtual filename 'ENG061229153952001001':

./os4xeq -p c-works -f /tmp/testfile -v ENG061229153952001001

• enqueue the file same file '/tmp/testfile' to partner 'c-works', using ENGDAT light virtual filename 'ENG061229153952001001', but with increased priority (5):

./os4xeq -p c-works -f /tmp/testfile -v ENG061229153952001001 -u 5

• enqueue the file '/tmp/testfile' to partner 'c-works', using ENGDAT light virtual filename 'ENG061229153952001001', with comment 'this is a testcomment':

./os4xeq -p c-works -f /tmp/testfile -v ENG061229153952001001 -c "this is a testcomment"

• enqueue the file '/tmp/testfile' to partner 'c-works', using ENGDAT light virtual filename 'ENG061229153952001001', added passively, so partner must fetch the file (no active send):

./os4xeq -p c-works -f /tmp/testfile -v ENG061229153952001001 -P

Certificate exchange:

• request certificate from OFTP2 partner 'c-works':

./os4xeq -p c-works -f /tmp/testfile -v ODETTE_CERTIFICATE_REQUEST

• send my certificate to OFTP2 partner 'c-works':

./os4xeq -p c-works -f /tmp/testfile -v ODETTE_CERTIFICATE_DELIVER

Enqueue an EERP to a given partner:

./os4xeq2 -E -p PARTNER_TESTNAME -v TESTFILE -T 1800652001 -D 20081012 -z DESTSFID -o ORIGSFID

os4xlic

This tool displays the OS4X ID, an installation specific hash value, which identifies this copy of OS4X.

input parameters

• -h: help text
• -I: display OS4X ID only (without headers)
• -v: display version information and exit

examples

localhost:~/tmp username$ ./os4xlic 
OS4X license tool v2.0

your OS4X ID is:
8b6c03222dc17af20d4c022d6cf92d502cb8d51b230467582b8d111a39e7b0bcv2

(all in one line)

localhost:~/tmp username$ ./os4xlic -I
8b6c03222dc17af20d4c022d6cf92d502cb8d51b230467582b8d111a39e7b0bcv2

os4x_licinfo

Display the information encoded in an OS4X license file.

input parameters

• -h: help text
• -C configfile: use given config file (default: /etc/os4x.conf)
• -f license file: use the given license file as input
• -d: display end date of validity
• -I: display licensed OS4X ID
• -p: display amount of licensed partners
• -a: display licensed functions
• -A: display licensed functions, as numeric value
• -v: display version information and exit

examples

localhost:~/tmp username$ ./os4x_licinfo -I
8b6c03222dc17af20d4c022d6cf92d502cb8d51b230467582b8d111a39e7b0bcv2

localhost:~/tmp username$ ./os4x_licinfo -f /opt/os4x/bin/license.key -d
20080331

os4xped

In order to administrate basic partner information in the OS4X database, this command line tool can be used from external programs (i.e. SWAN 2.x, DDX, etc.). The main key is the partner shortname which must be unique. If no partner exists for the given shortname it will be created. If exactly one partner entry exists for the given shortname it will be used for changing configuration entries. If multiple partner entries exist for the given shortname the program aborts.

input parameters

• -h: help text
• -C configfile: use given config file (default: /etc/os4x.conf)
• -s <partner shortname>: shortname of partner

all other parameters are optional:

• -l <partner longname>: long description of partner
• -a <partner SSID>: partner's SSID
• -b <partner SFID>: partner's SFID
• -c <partner password>: partner's password
• -d <my SSID>: my SSID
• -e <my SFID>: my SFID
• -f <my password>: my password
• -g <his hostname/ip address>: his TCP/IP address
• -i <his ISDN number>: his ISDN number
• -p <his tcp/ip port>: his TCP/IP port
• -t <connection type>: 1 - network / 2 - ISDN

examples

localhost:~/tmp username$ ./os4xped -s testshortname -l "this is the long description" -c NEWPWD -i 4711 -t 2
OS4X partner edit v1.4
company 'testshortname' successfully changed

localhost:~/tmp username$ ./os4xped -s testshortname -a "O001300 NEW SSID" -b "O001300 NEW SFID" -t 1 -g os4x.remotedomain.com -p 3317
OS4X partner edit v1.4
successfully inserted new company

os4xpoll

Connect to a given partner and retrieve downloadable files (if any are given by partner).

input parameters

• -p <partner shortname>
• [-a <alternative partner's SFID for authentification>]
• [-n]: no not daemonize
• -h: this help text
• -C <configfile>: use given config file (default: /etc/os4x.conf)
• -v: display version

examples

localhost:~/tmp username$ ./os4xpoll -v
OS4X poll version 2 build 20080513

localhost:~/tmp username$ ./os4xpoll c-works

localhost:~/tmp username$ ./os4xpoll -C /etc/os4x.conf -p c-works

In order not to daemonize the process (i.e. to count received files via returncode):

localhost:~/tmp username$ ./os4xpoll -C /etc/os4x.conf -p c-works -n

os4xrd / os4xrd2

The main OS4X receive daemon which is responsible for accepting OFTP sessions. This daemon starts several processes:

• os4xrd: the management process which manages all subsequent child processes
• os4xrd_tcpip: main receive process for incoming TCP/IP connections. After having accepted a connection, this processes creates a new child process:
  • os4xrd_tcpip_active: an active TCP/IP OFTP connection
• os4xrd_tcpip_tls: main receive process for incoming TLS secured TCP/IP connections. After having accepted a connection, this processes creates a new child process:
  • os4xrd_tcpip_active: an active TLS secured TCP/IP OFTP connection
• os4xrd_capi_[number]: main receive process for incoming ISDN connections. The number is the index value of the CAPI configuration row. After having accepted a call, this processes creates a new child process:
  • os4xrd_capi_[number]_active: an active CAPI OFTP connection

This behaviour in changed process names is not available on HP/UX!

input parameters

• -h: help text
• -C <configfile>: use given config file (default: /etc/os4x.conf)
• -f start forced
• -v: display version
• -i <serverID>: start as server with ID <serverID> (default: 0)

os4xsqd / os4xsqd2

The send queue daemon checks new entries in the send queue, trying to send them. During processing, the daemon starts the following processes:

• os4xsqd: the management process which manages all subsequent child processes:
  • os4xsqd_tcpip_active: an active OFTP connection process, running a TCP/IP connection
  • os4xsqd_tcpip_tls_active: an active OFTP connection process, running a TLS secured TCP/IP connection
  • os4xsqd_capi_active: an active OFTP connection process, running an ISDN connection

This behaviour in changed process names is not available on HP/UX!

input parameters

• -h: help text
• -C <configfile>: use given config file (default: /etc/os4x.conf)
• -f start forced
• -v: display version
• -i <serverID>: start as server with ID <serverID> (default: 0)

os4xupdate

Check the integrity and signature of an update file and execute it.

input parameters

• -h: printf this help text
• -C <configfile>: use given config file (default: /etc/os4x.conf)
• -f <filename with absolute path>
• -V: print out version and exit

examples

./os4xupdate -f /opt/os4x/incoming/OS4X_UPDATE

./os4xupdate -C /usr/local/os4sx/os4x.conf -f /tmp/manually_received_update_file

shox

The OS4X shell. Start programs with parameters outside OS4X as if they were started inside OS4X events or other states.

input parameters

• -h: this help text
• -C <configfile>: use given config file (default: /etc/os4x.conf)
• -e <executable>: executable to be started
• -p <parameters>: parameters to give the executable
• -v|V: print out version and exit

examples

/opt/os4x/bin/shox -e set

/opt/os4x/bin/shox -C /usr/local/os4x/os4x.conf -e /bin/ls -p "-l /tmp"