Optimize SPS Commerce Cloud EDI and reduce system slowdown

  • 0
  • 1
  • Article
  • Updated 4 years ago
  • (Edited)

Settings that are applied to your SPS Commerce Cloud EDI system can sometimes result in system slowdown, especially in systems transitioning from test/development to live/production. On test environments, low volumes of transactions occur and full logging details are typically desired, whereas on live systems, high volumes of transactions occur and full logging details are only needed when issues arise. Listed below are some configuration settings that help to optimize performance of your system to balance resource usage with functionality to avoid this type of system slowdown.

Workflow XML Setup

On production systems, workflow execution should be limited to once every 5 minutes or longer to avoid system slowdown caused by running the service more frequently than needed. To avoid resource overhead, configure workflow execution so it's set to 300 seconds or more by configuring the workflow schedues as described in zedSuite's workflow documentation: http://www.zedsuite.com/help/portals/current/wit/workflow-api/schedule/

B1WorkflowService.exe.config

The following updates to your workflow service config file B1WorkflowService.exe.config will help avoid system slowdown:


  • Set the "RetryWorkerTimer" property to 100 seconds or more.
  • On a live production system that doesn't require troubleshooting, set logging to "on error only". To do this, set the log4net root level mode to "ERROR" instead of "DEBUG. For example:

    <log4net>
        <!-- ... other log4net settings ... -->
        <root>
            <level value="ERROR" />
            <appender-ref ref="RollingFile" />
        </root>
    </log4net>

Database Maintenance

In general, data older than 30 days can be archived and purged from the live system. zedSuite strongly recommends performing regular database backups to allow for recovery of older data, as needed. For sample purge queries, speak with your implementation consultant.

  • "zed_WorkFlowBatchLog" table - This table records the batch ID and success/failure status of executed workflows.
  • "zed_Log" table - This table records the detailed log for executed workflows. If the log4net setting mentioned above is set to "DEBUG", then this table can get quite large. If this is your situation, you can purge this data. zedSuite strongly recommends performing backups prior to making this type of data change.
  • "zed_WorkFlowMessages" table - This table can get large for high volume systems. Purge this data once it is no longer needed to improve performance of high-volume systems. zedSuite strongly recommends performing backups to avoid losing transaction history records.

XML Transform Logging

By default, workflow trace is set to "ON", which means that all custom XML Transforms are appended to the logs. On a live system, this can result in files growing large quite quickly. To avoid files becoming too large too quickly, set the workflow trace property to "OFF". See zedSuite workflow documentation for more details: http://www.zedsuite.com/help/portals/current/wit/workflow-api/workflow/

Photo of zedSuite

zedSuite, zedSuite Employee

  • 80 Points 75 badge 2x thumb

Posted 4 years ago

  • 0
  • 1

Be the first to post a reply!