...
| Panel | ||||||
|---|---|---|---|---|---|---|
|
...
Does MessageHandler work on Microsoft Windows 64 bit?
MessageHandler works perfectly under the 64bit edition of Windows. However, we recommend using it with the 32bit version of the Java runtime. In order to use the MessageHandler product with a 64bit Java runtime, the supplied Service Wrapper (wrapper.dll) must be replaced with a 64bit version. Please note, that the 64bit version of the Service Wrapper is a commercial product of Tanuki Software, which we cannot redistribute for free.
...
- start you favourite file editor and load the the certificate configuration file of your sedex adapter (usually
..\adapter\conf\certificateConfiguration.xml) - replace the all occurences of
${ADAPTER_HOME}with the path of your sedex installation directory
MessageHandler startup fails which error 'Unable to validate sedex certificate config. ex: Content is not allowed in prolog.'
When you try to configure a signing outbox for a nativeApp and the startup of MessageHandler fails with an error message (found in log file log\message-handler.log) like
| Code Block |
|---|
org.apache.commons.configuration.ConfigurationException: Unable to validate sedex certificate config. ex: Content is not allowed in prolog.
at ch.admin.suis.msghandler.util.XMLValidator.validateSedexCertificateConfig(XMLValidator.java:62)
at ch.admin.suis.msghandler.config.SedexCertConfigFactory.<init>(SedexCertConfigFactory.java:57)
at ch.admin.suis.msghandler.config.SigningOutboxSedexCfg.refresh(SigningOutboxSedexCfg.java:67)
at ch.admin.suis.msghandler.config.SigningOutboxSedexCfg.<init>(SigningOutboxSedexCfg.java:56)
at ch.admin.suis.msghandler.config.ClientConfigurationFactory.init(ClientConfigurationFactory.java:247)
at ch.admin.suis.msghandler.config.ClientConfigurationFactory.<init>(ClientConfigurationFactory.java:106)
at ch.admin.suis.msghandler.common.MessageHandlerService.start(MessageHandlerService.java:95)
at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4042)
Caused by: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog. |
in this case there is most probaly a UTF-8 BOM (byte order mark) at the very beginning of the certificate configuration file of your sedex client (usually ..\adapter\conf\certificateConfiguration.xml). Use a text editor like Notepad++ (on Windows) to convert the file to a UTF-8 file without the BOM (or use a binary editor and remove the 3 first bytes EF BB BF).
MessageHandler verarbeitet die Files aus der sedex inbox nicht
...