nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Najděte více příspěvků označených jako

Accepted answers

All comments

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!

Travis Shore

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

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:
xyz.xyz.64:443Referrer Policy:
strict-origin-when-cross-origin

RaghavGupta

Hi A_Wyn_Jones

In current scenario we don't have web adaptor.

So are you trying to say that with out web adaptor workflow manager won't work. ?

RaghavGupta

Hi JFarmer

I have validated 13443 is open and working fine. I have tried restarting the services for ArcGIS Workflow Manager, ArcGIS Server and Portal for ArcGIS but then also it is showing Requirement missing.

Now I have doubts on following:

Is it because there is no domain name for the machine.
Is it because there is no web adaptor name.

Could you please confirm.....Please

JFarmer

@RaghavGupta

I presume you are using an internal machine name to federate this server? If you aren't using a FQDN then that would be my guess. If everything works between the federated server and Portal with this setup, there shouldn't be an issues specific to Workflow Manager here. The only communication requirement specific to us would be port 13443 being open and accessible (along with the standard 6443 for ArcGIS Server).

Usually an issue in that area is related to Portal not knowing that Workflow Manager has been installed and licensed on the federated server. If you've done those things, you might try a restart of ArcGIS Server on the federated server (which would also restart Workflow Manager Server). If that doesn't do it, try a restart of Portal. If that doesn't do it, you may need Tech Support to dig into this a bit.

Jonathan

RaghavGupta

Hi JFarmer

Portal is able to communicate with ArcGIS Server without domainnname. But while enabling server roles for workflow manager server it is showing requirements missing .

Do we need a domain name for the system to enable workflow manager server role ?

Aled Wyn Jones

Hi @RaghavGupta,

The line in the documentation is to ensure you're accessing ArcGIS Portal through the web adaptor (and not https://FQDN:7443/arcgis/home) When doing the federation e.g. https://FQDN/portal/home

When adding a server - you will be asked to provide the services and admin URL for that server. That may look like https://FQDN2/WorkflowServer and https://FQDN2:6443/arcgis.

Provide appropriate credentials for this ArcGIS Server when federating. My examples above are assuming you are using a second ArcGIS Server (on another machine) for workflow manager, as this is best practice for production systems.

JFarmer

Hi @RaghavGupta

That line in our documentation is specific to how you access the Portal site when you go to federate the server. So, you wouldn't want to go to machine.domain.com:7443/arcgis but instead go to machine.domain.com/portalwebadaptor. This isn't a Workflow Manager requirement, it's a core ArcGIS Enterprise requirement. See step 2 here: https://enterprise.arcgis.com/en/portal/latest/administer/windows/configure-servers.htm.

For the actual federation of the server, there is nothing different for Workflow Manager Server than what is in this core ArcGIS Server federation doc: https://enterprise.arcgis.com/en/portal/latest/administer/windows/federate-an-arcgis-server-site-with-your-portal.htm. If you meet those requirements, there shouldn't be any issues on our side.

If you can't federate using the port, I'm guessing that Portal cannot communicate with ArcGIS Server using that port and that's why it fails. But you'll need to look at the Portal and Server logs to sort out that piece.

Jonathan

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.