Skip to content
Swiss federal authorities

System requirements

Java Requirements for sedex-Client🔗

If the sedex-Client is installed on a Windows operating system, a supported JRE (Eclipse Temurin) will be automatically installed as part of the setup process.

If the sedex-Client is installed on another operating system (e.g., Linux), a Java Runtime Environment (JRE or JDK) must be either already present or manually installed.

Supported Java Versions🔗

The sedex-Client requires one of the following Java Runtime Environments (JRE or JDK):

  • Java 17 LTS
  • Java 21 LTS

Non-LTS Versions

We do not recommend using non-LTS versions such as Java 22, as they are not tested and therefore not officially supported by sedex.

Compatibility🔗

The sedex-Client has been fully tested with Eclipse Temurin Java SE 17 and 21, but it should also be compatible with other runtime implementations (e.g., Oracle, IBM, Amazon Corretto, etc.).

Auto-startable Client (service/daemon)🔗

In normal installations the sedex-Client must run permanently.

To ensure an automatic restart of the sedex-Client after a reboot of the host, the sedex Controller process can be configured to run as a service (on Windows) or as a daemon using a start script (on Linux).

Alternatively, user-specific mechanisms may be used to ensure that the sedex Controller process is started after a reboot of the host.

Note: Only the sedex Controller process must be made auto-startable; the other processes are started/stopped indirectly through the sedex Controller.

CPU🔗

Because the sedex-Client is more I/O than CPU intensive, any CPU capable of running one of the supported operating systems should normally suffice. The CPU performance may become a bottleneck only for high traffic installations.

RAM🔗

There should be at least 768 MB of memory available for all the sedex-Client’s processes combined.

Disk space🔗

The disk space needed for the sedex-Client installation is about 300 MB.

The total disk space which the sedex-Client needs at runtime depends on the number and size of messages being sent and received and how fast these messages are processed and cleaned up by the business application. Specifically, the disk space usage depends on how long messages are stored in the inbox, outbox, and processed folders, and how long receipts are stored in the receipts folder.

The following rules may be considered as heuristics.

  • Sending messages

    The disk space required for all sent messages may be up to 4 times the original messages’ size.

    • The outbox folder must be capable of holding all messages.
    • Internal copies of all the messages are generated.
    • The internal copies may be split into segmented copies.
    • The processed messages folder must be capable of holding all messages.

    Note: The sedex-Client has an option to remove messages that have been sent or processed from the outbox folder. By default, this option is disabled. Therefore, the business application must clean up the processed messages folder, or the sedex-Client can be configured to perform periodic cleanups automatically. Refer to messaging.processed-messages.delete-after-x-days in the Properties section for more details.

  • Receiving messages

    The disk space required for all received messages may be up to 3 times the received messages’ size.

    • The inbox folder must be capable of holding all messages.
    • The segmented messages are received and stored internally.
    • The segmented messages are assembled internally to complete messages.

    Note: The sedex-Client will never remove received messages from the inbox folder. Therefore, the inbox folder must be cleaned up by the business application.

Maximum message size🔗

A single message that the sedex-Client can send is currently limited to a size of 10 GB.

Firewall🔗

The firewall must be configured so that the sedex-Client can communicate with the sedex server. Outgoing connections to the following network end point are created by the sedex-Client:

  • Host: sedex-service.admin.ch
  • Port: 443
  • Protocol: HTTPS

Execution of batch files / shell scripts🔗

The sedex-Client executes batch files or shell scripts to start processes (.bat or .ps1 on Windows, .sh on Linux).

If a permission or a security policy of your system prohibits the execution of batch files or shell scripts, the sedex-Client will not run.

Network speed🔗

The sedex-Client needs a network connection that allows an upload speed of at least 5 megabytes in 5 minutes. Therefore, the recommended minimum upload speed is 150 kbit/s.

Note: This recommendation assumes that the whole bandwidth of the connection is available to the sedex-Client. If the sedex-Client must share the available bandwidth with other applications, the necessary bandwidth must be guaranteed for the sedex-Client.

In practice, the minimum upload/download speed must be adapted to the message volume being handled by the sedex-Client. The following table gives an overview of the typical durations required for the transfer of messages:

Message Size Network speed
150 kbits/s 300 kbit/s 1,000 kbit/s 10,000 kbit/s
5 MB 4.5 minutes 2.3 minutes 36 seconds 3.6 seconds
50 MB 44.5 minutes 22.3 minutes 6.6 minutes 36 seconds
500 MB 7.4 hours 3.7 hours 1.2 hours 6.7 minutes
1000 MB 14.8 hours 7.4 hours 2.3 hours 13.4 minutes

Note: These transfer times are calculated for messages sent as single files and will vary depending on the size and number of messages sent.