...
| Code Block |
|---|
msiexec /i "C:\MessageHandler.msi" /L*V "C:\MessageHandler_Installer.log" |
How to configure directory and file names for Windows?
Under Windows we recommend using absolute path names including either drive name or UNC paths. For MessageHandler prior to version 3.1.2 we recommend using slashes as path separators:
| Code Block |
|---|
C:/sedex/inbox d:/data/messagehandler/inbox //fileserver.some.domain.ch/sedex/outbox |
MessageHandler doesn't seem to see mounted remote directories on Windows
Suppose you configured an inbox located on a mounted remoted directory such as
| Code Block |
|---|
<outbox dirPath="O:/application_a/interface/outbox" msgType="10301"> |
If MessageHandler complains on startup with a message like
| Code Block |
|---|
Directory: O:\application_a\interface\outbox either not exist or is not a directory |
then first check, if the user account under which the MessageHandler service is run has access to the configured directory. If you can list the directory (using dir O:\application_a\interface\outbox), then it is probable that the Java runtime has problems with the drive letter mapping. Try using the UNC path instead:
| Code Block |
|---|
<outbox dirPath="//fileserver.some.domain.ch/interface/outbox" msgType="10301"> |
MessageHandler logs an ERROR on startup
If starting MessageHandler for the first time after a fresh installation, you will notice the following error message in the file
...