Having different ports for different products will be a problem. Right now if one knows how to access the management console of a single product, he knows what to do to access any of the management consoles of any product in the platform. Similar to other ports as well, such as the ESB and APIM use 8280 as the default passthrough port, similar for default thrift ports as well.
So having different offsets for different products will confuse users more IMO. On Thu, Nov 13, 2014 at 5:49 PM, Sameera Jayasoma <[email protected]> wrote: > I also have the same opinion on this change. All our users are familiar > with the default http/https ports, changing them will confuse them. > > Thanks, > Sameera. > > On Wed, Nov 12, 2014 at 8:33 PM, Afkham Azeez <[email protected]> wrote: > >> >> >> On Wed, Nov 12, 2014 at 6:12 PM, Isuru Perera <[email protected]> wrote: >> >>> Hi, >>> >>> I'm -0 on this proposal. If we have different offsets for different >>> products, we will have to maintain a document to show the offsets we have >>> given for each product. >>> >>> >> Due to the same reason, I too think having multiple port offsets will be >> confusing since most users have got used to the standard ports, and are >> quite comfortable with setting different port offsets. >> >> >>> When doing product integrations, setting offset is not the only >>> configuration step. It is a simple operation and I think it's better to let >>> the user to do that along with other configurations. Then the user will >>> know what really happens with ports and how to configure URLs. >>> >>> In most of the production deployments, the WSO2 instances will be in >>> separate servers/VMs and we rarely modify the offset. Most of the time, we >>> define common security groups to open ports. So, if we don't change offsets >>> by default, we will be having common ports for each server. >>> >>> So, I think it's better to have no offsets by default in WSO2 products. >>> >>> Thanks! >>> >>> Best Regards, >>> >>> On Wed, Nov 12, 2014 at 5:42 PM, Paul Fremantle <[email protected]> wrote: >>> >>>> Ack? >>>> >>>> Paul >>>> >>>> On 10 October 2014 09:27, Paul Fremantle <[email protected]> wrote: >>>> >>>>> I have a simple proposal, which is that we predefine a standard offset >>>>> for each product. >>>>> >>>>> e.g. AS 0, ESB 1, AM 2, GovReg 3, BAM 4, IS 5, etc... >>>>> >>>>> These would be baked into the distros. This would make life a lot >>>>> easier for customers doing more than one product. Also for say BAM >>>>> integration, life would be much better. >>>>> >>>>> Paul >>>>> >>>>> -- >>>>> Paul Fremantle >>>>> CTO and Co-Founder, WSO2 >>>>> OASIS WS-RX TC Co-chair, Apache Member >>>>> >>>>> UK: +44 207 096 0336 >>>>> >>>>> blog: http://pzf.fremantle.org >>>>> twitter.com/pzfreo >>>>> [email protected] >>>>> >>>>> wso2.com Lean Enterprise Middleware >>>>> >>>>> Disclaimer: This communication may contain privileged or other >>>>> confidential information and is intended exclusively for the addressee/s. >>>>> If you are not the intended recipient/s, or believe that you may have >>>>> received this communication in error, please reply to the sender >>>>> indicating >>>>> that fact and delete the copy you received and in addition, you should not >>>>> print, copy, retransmit, disseminate, or otherwise use the information >>>>> contained in this communication. Internet communications cannot be >>>>> guaranteed to be timely, secure, error or virus-free. The sender does not >>>>> accept liability for any errors or omissions. >>>>> >>>> >>>> >>>> >>>> -- >>>> Paul Fremantle >>>> CTO and Co-Founder, WSO2 >>>> OASIS WS-RX TC Co-chair, Apache Member >>>> >>>> UK: +44 207 096 0336 >>>> >>>> blog: http://pzf.fremantle.org >>>> twitter.com/pzfreo >>>> [email protected] >>>> >>>> wso2.com Lean Enterprise Middleware >>>> >>>> Disclaimer: This communication may contain privileged or other >>>> confidential information and is intended exclusively for the addressee/s. >>>> If you are not the intended recipient/s, or believe that you may have >>>> received this communication in error, please reply to the sender indicating >>>> that fact and delete the copy you received and in addition, you should not >>>> print, copy, retransmit, disseminate, or otherwise use the information >>>> contained in this communication. Internet communications cannot be >>>> guaranteed to be timely, secure, error or virus-free. The sender does not >>>> accept liability for any errors or omissions. >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> Isuru Perera >>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/ >>> Lean . Enterprise . Middleware >>> >>> about.me/chrishantha >>> >> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>* >> *email: **[email protected]* <[email protected]> >> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: * >> *http://blog.afkham.org* <http://blog.afkham.org> >> *twitter: **http://twitter.com/afkham_azeez* >> <http://twitter.com/afkham_azeez> >> *linked-in: **http://lk.linkedin.com/in/afkhamazeez >> <http://lk.linkedin.com/in/afkhamazeez>* >> >> *Lean . Enterprise . Middleware* >> > > > > -- > Sameera Jayasoma, > Software Architect, > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://sameera.adahas.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > Mobile: 0094776364456 > > Lean . Enterprise . Middleware > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : [email protected] Phone : +94 777 775 729
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
