Release Automation

Expand all | Collapse all

NES routing configuration between intranet NES and DMZ NES

Jump to Best Answer
  • 1.  NES routing configuration between intranet NES and DMZ NES

    Posted 12-28-2015 10:28 AM

    Hi,


    we're using an execution server in the MZ (intranet) and another one in the DMZ. We are only allowed for outbound communication.
    On some CA architecture sheets I saw that the direct communication (e.g. for artifact file transfer / retrieval agent on the intranet) can be handled between the two NES by configuring/enabling NES routing.
    This way the artifacts taken by the retrieval agent on the intranet side can be sent via intranet NES to the DMZ NES for further agent deployment...

     

    Can this be done via the "Edit Execution Server > Connected Execution Servers" dialogue?

    Maybe somebody can explain, how the so called NES routing will be configured / enabled.


    Thank you,
    Ralf



  • 2.  Re: NES routing configuration between intranet NES and DMZ NES
    Best Answer

    Posted 12-28-2015 02:05 PM
      |   view attached

    You can set this up from either the ASAP UI (which updates the relevant execution server’s nimi config file) or you can update the nimi config file directly.

    From within  the ASAP UI go to the Administration tab:

    Select Agent Management

    Under the Agent Title, select the execution server that is inside the firewall

    Select the edit icon at the top right (pencil)

    At the bottom tick the execution server(s) that is outside the firewall.

    This will set up a link between the two execution servers with the inside execution server driving the connection

     

    regards



  • 3.  Re: NES routing configuration between intranet NES and DMZ NES

    Posted 12-29-2015 06:15 AM

    Hi Billy,

     

    thank you for the answer. That's the solution we need, we'll try that with our DMZ.

     

    Happy New Year,
    Ralf