Utility files

SecureTransport includes the utility files listed in the following table:

Utility file Description
bounce Bounces the SecureTransport protocol servers. If run on a primary server of a cluster, it will also bounce all the secondary servers.
collect_support_information Collects information for Axway Global Support as specified on the Support Tool Configuration page.
gencsr Generates a key pair and the associated certificate request file. Users can submit the CSR file to a CA to get a CA-issued certificate.
log_export Export server log or File Tracking (transfer log) entries from the database in CSV or DBF format.
mkadmin Adds a new administrator account or changes the password of an existing administrator account. Changes are automatically synchronized across all servers in a Standard Cluster or Enterprise Cluster, unless the -sync=n option is present.
repconv

Updates repository encryption by decrypting files encrypted in a previous version of SecureTransport and encrypting them for the current version. Can also change the cipher algorithm and certificate SecureTransport uses to encrypt files and decrypt files and folders.

Note On Windows systems, the repconv tool cannot process files with special characters in their names (such as Japanese, Chinese, or Cyrillic characters).
Note Starting with SecureTransport 5.4 Patch 32, Axway is deprecating "repconv" utility ability to convert any files encrypted by pre-5.2 SecureTransport releases to SecureTransport 5.2 (and later) repository encryption. After installing SecureTransport 5.4 Patch 32, users will no longer be able to convert files encrypted by pre-5.2 SecureTransport releases to SecureTransport 5.2 (and later) repository encryption. SecureTransport customers who still have files encrypted by pre-5.2 SecureTransport releases, are required to convert those to current SecureTransport repository encryption prior applying SecureTransport 5.4 Patch 32. The "repconv" utility decrypt and encrypt features continue to work as previously did with SecureTransport 5.4 Patch 32.
show_ports Displays the ports on which the servers are configured to run.
Start scripts
start_admin Starts the Administration Tool server.
start_all Starts all SecureTransport servers.
start_as2d Starts the AS2 server.
start_db Starts the embedded database server.
start_ftpd Starts the FTP server.
start_httpd Starts the HTTP server.
start_pesitd Starts the PeSIT server.
start_sshd Starts the SSH server.
start_tm Starts Transaction Manager.
Stop scripts
stop_admin Stops the Administration Tool server.
stop_all Stops all SecureTransport servers.
stop_as2d Stops the AS2 server.
stop_db Stops the embedded database server.
stop_ftpd Stops the FTP server.
stop_httpd Stops the HTTP server.
stop_tm Stops Transaction Manager.
stop_pesitd Stops the PeSIT server.
stop_sshd Stops the SSH server.

Status scripts

Note In order for the status scripts to work, you need to have the admin server up an running.
status_ftpd Checks the status of the FTP server.
status_ socks Checks the status of the SOCKS5 proxy. Only available on Edge.
status_httpd

Checks the status of the HTTP server.

 

The following example is applicable to status_ftpd as well: you can expect the same messages with either in the place of status_httpd.

  • status_httpd returns 'httpd is disabled', when all http listeners are disabled.
  • status_httpd returns 'httpd is functional', when at least one http listener is enabled, and it is functional.
  • status_httpd returns 'httpd is down', when at least one http listener is enabled, and it is stopped or it is not functional.
status_as2d Checks the status of the AS2 server.
status_pesitd Checks the status of the PeSIT server.
status_sshd

Checks the status of the SSH proxy.

 

The following example is applicable to status_as2d and status_pesitd as well: you can expect the same messages with either in the place of status_sshd.

  • status_sshd returns 'sshd is disabled', when all ssh listeners are disabled, and there are no functional listeners.
  • status_sshd returns 'sshd is functional', when at least one SSH listener is functional.
  • status_sshd returns 'sshd is down', when at least one SSH listener is enabled, and there are no functional SSH listeners.
status_admin Checks the status of the Admin server.
status_tm Checks the status of the Transactional manager.
status_db

Checks the status of the Database.

 

The following example is applicable to status_admin, status_socks, and status_tm as well: you can expect the same messages with either in the place of status_db.

  • status_db returns 'db is functional', when the service is functional.
  • status_db returns 'db is down', when the service is not functional.
Note SecureTransport includes several utilities that are used internally. All the utility files are stored in the <FILEDRIVEHOME>/bin or <FILEDRIVEHOME>/bin/utils directory.
Note In case of low disk space do not start servers.

Related Links