Workflow and ServiceDesk Community

 View Only
  • 1.  Workflow's WAS Management Service

    Posted May 27, 2015 02:48 PM

    Hello all - I'm having some troubles figuring out the magic that makes the WAS connection successful when attempting to publish to a remote server.

    2015-05-27_12-36-53.png

    In the screenshot above, ATMA is the machine I'm publishing FROM, and WF76A is the machine I want to publish to.  Note that SDB is another remote workflow server and connects fine.  I've gone over all the settings on each remote server and am unable to find any obvious discrepancies.

    I'd assumed that the Process Manager login info here was determining the authentication method, but I haven't had any success getting that to work:

    2015-05-27_12-38-45.png

    So I'm hoping someone can shed some light on what I'm doing wrong here.

    2015-05-27_12-40-55.png

    2015-05-27_12-41-43.png

    Thanks!



  • 2.  RE: Workflow's WAS Management Service
    Best Answer

    Posted Jun 01, 2015 09:06 PM

    As it happens, I fixed this unintentionally.  I connected with Windows file explorer and authenticated to the remote server to transfer the Workflow packages over (since I wasn't able to publish), and that Windows connection seems to be what was missing.  After making the UNC connection the server is publishable.