Forum Discussion
You will need to create a separate pool and add the Workflow servers at either port 12290 (https) or 12291 (http). Assign either a default https/http or tcp monitor to the pool.
You'll also need to create a standard virtual server at the IP you'll be directing clients to, on either port 12290 or 12291, and select the pool you created as the target for the VIP. If you are doing SSL, you have to assign client and server SSL profiles, which means you'll need to import the cert and key for you workflow server(s) into BIG-IP.
After typing all that out, I think probably the way to go is to use the f5.iis iApp template and use the appropriate ports for the virtual server and pool members. We also have an f5.tcp iApp that supports deploying in a fastl4 mode if you don't need to decrypt the workflow traffic.
Mike Hi,
I tried adding the Workflow Manager Server with 12290 port but still not working. I also noticed that there is AS involved on the traffic
Client -> SharePoint Server -> SP Application Server -> WorkFlow Manager.
Our issue in only getting information from Workflow Manager to SharePoint Server.
Thanks,
-Nat