Two ESD instances for Email and SMS campaign treatments on the same host - QueueDir Destination Folder Issue
(Doc ID 1574257.1)
Last updated on JANUARY 03, 2023
Applies to:
Siebel Email Marketing Server - Version 8.0.0.10 SIA [20436] and laterInformation in this document applies to any platform.
we have two ESD instances for Email and SMS campaign treatments on the same host (EMS 80 [EMS 2020] integrated with Siebel Marketing 8.0.0.10.
ESD has been installed in the following path:
ESD (Email) --> D:\Siebel EMS\esd
ESD (Sms) --> D:\Siebel EMS\esd_sms
We noticed that:
- ESD components does not use the queuedir under the installation folder. ESD creates dataq files in C:\Windows\system32\queueDir
- Both Mail ESD and SMS ESD make use of the same folder C:\Windows\system32\queueDir
- Restarting both ESD (while queuedir is not empty), both ESD components try to process the same dataq files
Our concer is that, due to this behaviour, the two ESD can face some critical-section or deadlock processing the same dataq files.
Can we change the ESD queuedir destination path in order to have a dedicated queuedir folder for each ESD instance?
Doc [ID 1491606.1] shows how to change queue folder for CTD. Is there a similar parameter for ESD?
Symptoms
- ESD components does not use the queuedir under the installation folder. ESD creates dataq files in C:\Windows\system32\queueDir
- Both Mail ESD and SMS ESD make use of the same folder C:\Windows\system32\queueDir
- Restarting both ESD (while queuedir is not empty), both ESD components try to process the same dataq files
Changes
none
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |