UNSOLVED

doronm

updated

15 years ago

D

doronm

6 Posts

0

1072

January 11th, 2012 02:00

Using ports other than 443 and 80

Hi,

I’m writing an application that uses Atmos REST API with the .net binding (ESU).

I would like to allow my users to work with other ports (other than the default 80 & 443)

Does this kind of option supported in the atmos and in the ESU?

Thanks.

  • rbala1

    1 Rookie

    •

    222 Posts

    192

    0

    Posted January 17th, 2012 06:00

    You can use alternate ports in the wrapper and the configuration with Atmos is largely dependent on the front-end network that load balances across Atmos nodes. 

    Are you using Atmos on-premise or through a service provider?

  • doronm

    6 Posts

    192

    0

    Posted January 17th, 2012 22:00

    Although both options are relvevant, let's say I'll use Atmos on-premise.

    So basically (just to make sure I got this right) - Atmos on-premiseto can be configured to use other ports as well and not only 80 & 443. right?

  • chris_arnett

    1 Rookie

    •

    110 Posts

    192

    0

    Posted January 18th, 2012 06:00

    Yes, but you would do that by putting a load balancer or proxy in front of the Atmos cluster (which is recommended anyway).  Your topology would look like this:

    Atmos <--> load balancer/proxy <--> application client

    The listen port of the proxy is what you would configure.  I don't think we support changing the listen port of access nodes.