When Workflow application is republished, it will not retain its previous Application Pool.
Last Updated November 27, 2015
When Workflow application is republished, it will not retain its previous Application Pool. This may be problematic when specific Application Pool is desired for security, separation or performance reasons.
Design change in Workflow 7.6. After reviewing the behaviour, it was decided to change this back to previous way.
This issue has been fixed in Workflow 7.6 Rollup (build 7.6.4383.496 and newer). See INFO2509 for a list of fixed issues in Rollup. To acquire the roll-up please contact Symantec Technical Support and reference this article or the Rollup article.
A workaround exists in the form of clearing out the App Pool Id field in Deployment Info settings.
Start LocalMachineInfo Editor tool
In Workflow Server section, click ellipsis '...' button next to Workflow Server Configuration setting
In dialog that opens, in Deployment section click ellipsis '...' button next to Deployment Info setting
Clear the App Pool Id field (do not select an application pool just delete what is in the field)
Applications no longer retain their custom App Pool after republishing and are being defaulted to ProcessManagerPool
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe