Hi,
Yeah. I think having different offsets for different products will
definitely confuse the customers who are already familiar with our
products. But as Shammi has mentioned if we could have standard
port-offsets for production deployments that might be useful in
troubleshooting support
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 az...@wso2.com wrote:
On Wed, Nov 12, 2014 at 6:12 PM, Isuru Perera isu...@wso2.com
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
Ack?
Paul
On 10 October 2014 09:27, Paul Fremantle p...@wso2.com 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
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.
When doing product integrations, setting offset is not the only
configuration step. It is a simple operation and I think it's
regards,
Johan,
*From:* Architecture [mailto:architecture-boun...@wso2.org] *On Behalf Of
*Isuru Perera
*Sent:* woensdag 12 november 2014 13:43
*To:* WSO2 Architecture
*Subject:* Re: [Architecture] Proposal for Carbon Offsets
Hi,
I'm -0 on this proposal. If we have different offsets
Hi,
If we come up with this standard port offset for each product , AFAIU we
are only thinking on scope within WSO2 products. Generally In most of the
cases , there is a standard default port for most of the products which is
related with their functionality. As an example most of the message
by the relevant number.
Kind regards,
Johan,
*From:* Architecture [mailto:architecture-boun...@wso2.org] *On Behalf Of
*Isuru Perera
*Sent:* woensdag 12 november 2014 13:43
*To:* WSO2 Architecture
*Subject:* Re: [Architecture] Proposal for Carbon Offsets
Hi,
I'm -0 on this proposal. If we have
On Wed, Nov 12, 2014 at 8:33 PM, Afkham Azeez az...@wso2.com wrote:
On Wed, Nov 12, 2014 at 6:12 PM, Isuru Perera isu...@wso2.com 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
We need to pick offset values wisely which requires less number of changes
(in configurations)
for example: if we change Port Offset of APIM we require changes in 3 files
(carbon.xml, synapse token api etc).
On Thu, Nov 13, 2014 at 5:10 AM, Thilina Piyasundara thili...@wso2.com
wrote:
On
10 matches
Mail list logo
