Product: Sage X3
Transaction Manager connects to Sage X3 through an App Pool sometimes referred to as an Endpoint. These App Pools send and receive data and provide the overall communication with Transaction Manager.
Often an App Pool can get cluttered and requires a restart in order to return to a working state so that Transaction Manager can continue to operate normally.
Identifying Your App Pool
Since Sage X3 can have multiple App Pools you'll need to make sure you've identified the correct one that Transaction Manager was setup to use during its initial setup.
This will be marked within the Business System Settings under the Integration Options as your X3 Pool Alias.
Navigate: Business System → (Company) → Company Configuration → Integration Options
Find: X3 Pool Alias
Restarting Your App Pool
Once you know which App Pool that Transaction Manager is communicating with you'll need to log in as an Administrator account within Sage X3 and perform the Start/Update command on it.
You'll need to have Administrator rights within your Sage X3 system to be able to restart your App Pool properly
Finding the App Pools
You can find your App Pools listed under the Classic SOAP pools configuration window within the Administration group of Sage X3.
Navigate: Administration → Web Services → Classic SOAP Pools Configuration
Restarting the App Pool
After you find the App Pool Alias that was marked within Transaction Manager inside of your SOAP Pool list you will need to select the three-dots next to it, and select Start/Update to perform a restart of the service.
Select: Three-Dots → Start/Update
Restart Complete
The App Pool will begin to restart and a window will popup to let you know of the operation running - once completed you'll see the Phase change to Completed and a log will be produced on the status of the operation.
Additional Resources
rev 7/3/2023