Parameters affecting the overall behavior of event-driven payments processing are specified in the EDPGlobalConfigs.xml file. This file is located in the following directory:
WAS_installdir/installedApps/cell_name/ WC_instance_name.ear/xml/config/payments/edp
WAS_userdir/installedApps/cell_name/WC_instance_name.ear/xml/config/payments/edp
WCDE_installdir/xml/config/payments/edp
Example:
<?xml version="1.0" encoding="UTF-8"?> <EDPGlobalConfigs xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="com/ibm/commerce/edp/eut/parsers/EDPGlobal.xsd"> <MainThreadTimeOutInSeconds>4</MainThreadTimeOutInSeconds> <MainThreadVerifyStatusIntervalInMilliSeconds>300</MainThreadVerifyStatusIntervalInMilliSeconds> <EDPTicklerFactory>WasLog</EDPTicklerFactory> </EDPGlobalConfigs>
The following parameters affect the performance of event-driven payments:
- MainThreadTimeOutInSeconds
- Specifies how long (number of seconds) the main foreground thread will wait for the background thread to finish running. Actual payment actions (connections to payment back-end systems) are not run in the same thread of the code that invokes the event-driven payments subsystem (the primary thread). A secondary or background thread is used to run payment actions in the background. The default is 4 seconds.
Decrease this value if you have a significant number of bottlenecks and very few transactions pending. Decreasing the value will cause more transactions to pend.
Increase this value if you have very few bottlenecks and many transactions pending. Increasing the value will cause fewer transactions to pend.
- MainThreadVerifyStatusIntervalInMilliSeconds
- Specifies how long (number of milliseconds) before the main foreground thread will sleep before waking up to check the status of the background thread to see if the background thread is finished running. The default is 300 milliseconds.
- EDPTicklerFactory
- Specifies where ticklers are sent. Valid values are Waslog, WebSphereCommerce, and EDPSelf. You should not change the value shown. EDPSelf indicates event-driven payments can be processed independently of WebSphere Commerce.
Examples:
- Default:
MainThreadTimeOutInSeconds = 4 MainThreadVerifyStatusIntervalInMilliseconds = 300
- No polling occurs (for example, 5, 5000):
MainThreadTimeOutInSeconds = n MainThreadVerifyStatusIntervalInMilliseconds = nx 1000
- No waiting (always pends):
MainThreadTimeOutInSeconds = 0 MainThreadVerifyStatusIntervalInMilliseconds = 0