Page 1 of 1
RDML Longrange lansa SSL and default partition - where from?
Posted: Sat Apr 20, 2013 8:16 am
by jimoreilly
When using port 80 access from Longrange client the partition override in the client profile works and allows me to switch between production and development partitions. When I switch to using SSL on our protected port, the Longrange connection always goes to the development partition, ignoring the partition override in the client profile. Where is the default partition to be used stored?
Re: Longrange lansa SSL and default partition - where from?
Posted: Mon Apr 22, 2013 10:20 am
by Paul
The default partition settings is stored in the client.xml file – which is server-wide.
If partition is specified in the client, the server-wide settings should be overridden.
This should be the case with SSL as well.
If you are finding that this is not the case then you should contact LANSA Support, letting them know if you are using Apache or IIS.
Re: Longrange lansa SSL and default partition - where from?
Posted: Tue Apr 23, 2013 12:45 am
by jimoreilly
Thanks for pointing me in the right direction. I found that the Maintain Systems section of the Lansa Web Administrator had the SSL port marked with a partition (the DEV side) so that all transaction to the SSL port were being forced to the DEV partition. Once this was removed, it allowed for the override from the LongRange client side to take affect.