You might not have even noticed, but in the wave of new RTM bits that has hit us during past few weeks, Workflow Manager<\/a> has been one of them. And it seams the name is final now \u2013 it\u2019s \u201cWorkflow Manager\u201d after all. No \u201cWindows Azure Workfow\u201d, \u201cWorkflow 1.0\u201d or even \u201cAppFabric Workflow\u201d, how it has been called in the past few months. Workflow manager it is.<\/p>\n

<\/p>\n

RTM bits solved few nasty bugs which were present in the beta version, but the technique of pairing it with SharePoint Server 2013<\/a> has not changed (look at this article about WFM and SP2013 pairing<\/a>), except of one minor thing: the parameters in the Workflow Manager PowerShell commands for finding out the workflow ports has changed slightly.<\/p>\n

No2 it is:<\/p>\n

Get-WFFarm | ft HttpPort<\/span><\/p>\n

and<\/p>\n

Get-WFFarm | ft HttpsPort<\/span><\/p>\n

for HTTP and HTTPS ports respectively.<\/p>\n

<\/a><\/p>\n

Oh yes, and the service application is not called \u201cApp Fabric Application Proxy\u201d anymore, it\u2019s \u201cWorkflow Service Application Proxy\u201d now <\/p>\n

<\/a><\/p>\n

Everything else has remained the same way as in the beta version. Yes, I\u2019ll update my previous article<\/a>\u00a0<\/p>\n