Operational Questions

Q: Where can the sedex Client be downloaded?¶

A: Download the latest version of the sedex Client from here.

Q: How is the sedex Client installed?¶

A: Instructions for installing the sedex Client are available here

Q: Where are the participant's sedex certificate and its password (e.g. to manually migration to other host)?¶

A: The certificate (.p12 file) is in sedexClientHome/conf/certificates/<sedex-ID>.p12. The corresponding password is in sedexClientHome/conf/certificateConfiguration.xml.

Q: Where are the sedex Client log files?¶

A: The sedex Client log files are in the sedex Client installation's logs folder.

Q: How can a sedex Client be migrated to a different host (server)?¶

A: Migrating a sedex Client installation to a different host is more complex and requires that the steps below be followed exactly.

Note the following before starting the migration:

As long as the sedex Client is stopped, it can be installed in several places. Only one installation my run at once, otherwise an alert reporting duplicate running instances will occur.
A sedex Client should only be migrated after the old sedex Client will no longer need to be started. If the old sedex Client is restarted, the migrated data will be obsolete and may result in lost messages.

To migrate a sedex Client to a new server:

Stop the sedex Client using the /bin/sedex-client-stop script or with the operating system's services tool.
If the sedex Client is running as a Windows service, uninstall the Windows service as follows:
- Run the sedexClientHome/bin/controller-UninstallWindowsService.bat script as administrator.
- A console window briefly opens and closes.
Back up the entire sedex Client installation into a Zip file.
Save the following data that needs to be migrated:
- The interface directories and any files they contain (inbox, outbox, receipts, processed).
- The log files.
- The sedex certificate (.p12 file) located in sedexClientHome/conf/certificates/<sedex-ID>.p12.
- The certificate's password found in sedexClientHome/conf/certificateConfiguration.xml.
```
[...]
<privateCertificate>
  <location>${sedex.home}/conf/certificates/3-CH-99999.p12</location>
  <password>ABCDE12345</password>
 </privateCertificate>
[...]
```
  Warning
  
  If several blocks are present, please save all .p12 files and all corresponding passwords!
Move the Zip file to the new host.
Extract the Zip file into the same directory structure as on the old host.
If sedex Client's root or home directory are different, edit the necessary configuration files.
- /conf/sedex-client-configuration.properties
Start the sedex Client as a standalone application. Run the sedexClientHome/bin/controller-start.bat script (no administrator rights are required).
Check the console and logs for errors.
If there are no errors, stop the sedex Client. Run the sedexClientHome/bin/controller-stop.bat script (no administrator rights required)

Ideally, migrate to the newest version of the sedex Client

Info

  The sedex Client **must** be in an operational state before updating/migrating. A manual start as a standalone application is highly recommended in order to check that the sedex Client runs correctly. While it is possible to migrate a non-functional sedex Client installation, the migrated installation will most likely not work either.

If desired, install the Windows service.
- Run the sedexClientHome/bin/controller-InstallAsWindowsService.bat script as administrator.
- A console window appears opens and then closes.
The migration is complete.