Installing Workflow Manager Server

[RaghavGupta]

Hello 

While trying to federate Configuring Workflow Manager Server with an ArcGIS Enterprise portal it is mentioned in the ESRI documentation that You must connect to theArcGIS Enterpriseportal through theArcGIS Web AdaptorURL. Please find below screenshot for your reference.

More info here 

I have tried passing server url along with port name while federating and found that it does not accept and says invalid url.

I was thinking if there is any other way out. If anyone has tried without webadaptor url.

Please share your thoughts on this.

[JasonHansel1]

I have had my go at Workflow Manager in Azure and have not had great success. I just upgraded to 11.1 and thankfully the Web Adaptor does not get corrupted after enabling the role.

The documentation for this Product is lack luster to say the least. If ESRI could give us a better idea of where 13443 needs to be opened and the communication needed, aside from the huge port diagram, that would be great. For instance, does 13443 need to be opened from the web server hosting the Web Adaptor to the internal server hosting ArcGIS Server and the Application. 

The Portal is Federated with no issues other then Workflow Manager  

With Google Dev Tools opened, I load the Workflow Manager page from Portal, with a licensed user. I am returned with a flicker, like the page will load and then an error due to the checkstatus not being able to validate what appears to be the token to get the license. If I try to click on the Request captured in DEV tools it brings me to a Web Adaptor Page not being available. 

Method:
GETStatus Code:
500 Internal Server ErrorRemote Address:
XX.XXX.64:443Referrer Policy:
strict-origin-when-cross-origin

[Travis_Esri]

Hello @JasonHansel1,

You will indeed need to enable 13443 from the web server > Workflow Manager for the web adaptor to route traffic correctly.

We are aware this is an area of our documentation where we can expand more and have plans to do so. We also have recently worked with technical support to get a public-facing knowledge article on troubleshooting in this area added to their knowledge base which should be published for viewing within a couple of weeks.

Travis

[JasonHansel1]

Travis,

Thank you for the response. Just an FYI, we had to open port 13443 from WA->Portal and any other server touching WM in order for this to work properly. Looks like Portal tries to reach back over to the WM to grab a token and authenticate the license properly, then it will load the App page correctly. 

One thing I picked up from watching the training video (trying to grab some extra configuration nuggets) that was also not presented by support, was the HealthCheck url for WM. If this isn't working after the initial configuration, obviously the app will not.

This diagram, IMO, is very hard to follow. If the Architecture does not match this diagram, (i.e. Web Servers | WA up top as the Web Tier and Enterprise in the DMZ), the traffic flow from WA is not clear, especially 13443.

Thanks!