locked
ATA 1.8 deploy and IP configuration RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi everyone,

    we have deployed ATA 1.8 in our environment but we couldn't select on which IP the ATA Service (where the comunication from the Lightweight Gateway will arrive) listens.

    How can we see/change such configuration?

    Watching in the MongoDB I found the following JSON Configuration:

    "CenterWebApplicationConfiguration" : {
            "ServiceListeningIpEndpoint" : {
                "_t" : "EndpointData",
                "Address" : "0.0.0.0",
                "Port" : 443
            },
            "CommunicationCookieExpiration" : "00:20:00"
        },
        "CenterWebClientConfiguration" : {
            "RetryDelay" : "00:00:01",
            "ServiceEndpoints" : [ 
                {
                    "_t" : "EndpointData",
                    "Address" : "192.168.50.164",
                    "Port" : 443
                }
            ],
    Which setting do we have to modify to change the Service IP and maintaine the Console IP listening (.50.164)?

    Thanks in advance.

    Simone

    Thursday, July 13, 2017 8:20 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    ATA 1.8 binds to all available IP addresses on the machine.

    Why do you need to change that?


    Thursday, July 13, 2017 10:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Simone,

    Starting from ATA 1.8, ATA Center only needs one IP address and TCP port 443 for both communicating with ATA Gateway and ATA Console access. 

    In addition, if ATA Center has two IP addresses, you can access ATA Console via either of the two IP addresses.


    Best regards,

    Andy Liu

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 25, 2017 7:02 AM