Re: [Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

[Chamalee De Silva]

[1] Port offsetting the Thrift port in APIM

On Fri, Nov 24, 2017 at 7:01 PM, Chamalee De Silva 
wrote:

> hi Dushantha,
>
> For API Manager 2.0.0 and later versions, we do not need to configure the
> ThriftClient and ThriftServer ports as they get incremented according to
> the offset.
>
> For API Manager versions prior to APIM 2.0.0 we need to modify these ports
> according to the port offset.
>
> Please refer mail thread [1] for more information.
>
>
>
> Thanks,
> Chamalee
>
> On Fri, Nov 24, 2017 at 11:40 AM, Samitha Chathuranga 
> wrote:
>
>> Hi Dushantha,
>>
>> The point is that by default those thrift port values are commented out.
>> (if they are commented-out the all the port values are changed by the
>> offset value ) If you uncomment them, you have to configure them correctly.
>> By the way in the doc [1] you mentioned, note the below section, under the
>> 3rd point under the topic "Installing and configuring API Manager".
>>
>> [image: Inline image 1]
>>
>> So the doc has been written not considering that optional step of port
>> offsetting. So all ports mentioned in the doc are considering that there
>> are no offsets.
>>
>> [1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Mana
>> ger+2.0.0
>>
>> Regards,
>> Samitha
>>
>> On Fri, Nov 24, 2017 at 9:09 AM, Viduranga Gunarathne > > wrote:
>>
>>> Hi Dushantha,
>>>
>>> Yes. If you are using port offset to deploy the Gateway and KeyManager
>>> nodes, then the default Thrift port (10397) in both the nodes will get
>>> offset by the specified offset value.
>>> Eg:
>>> Gateway offset = 2,
>>> Then  will be 10399
>>>
>>> KeyManager offset = 3,
>>> Then  will be 10400
>>>
>>> In a clustered deployment, the KeyManager acts as the Thrift Server and
>>> the Gateway as the Thrift client. Hence the Gateway uses the
>>>  to send a request to the KeyManager where the request is
>>> handled at the . For the communication to happen, both
>>> the port values (ThriftServerPort in KeyManager and ThriftClientPort in
>>> Gateway) should be of the same value. Unless the port offset of both the
>>> Gateway and the KeyManager is the same, you will have to manually set the
>>> two values.
>>>
>>> Thanks,
>>> Viduranga.
>>>
>>> On Thu, Nov 23, 2017 at 9:24 PM, Chamara Silva  wrote:
>>>
 This already in the public documentation. Please refer "Changing the
 Thrift client and server ports" section.


 [2] https://docs.wso2.com/display/AM210/Changing+the+Default
 +Ports+with+Offset

 Thanks,
 Chamara Silva

 On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita  wrote:

> Hi
> I'm involved in a gateway cluster set up in the local machine where
> the architecture is explained as follows
>
>1. IS 5.3.0 as KM offset 0
>2. Publisher/store/TM  offset 1
>3. Gateway worker   offset 3
>4. GatewayWorkerManger  offset 2
>
> I'm following the [1] Clustering API Manager document where it
> explains
> Configuring the Gateway > Configure key management related
> communication. >  c.  Specify the ThriftClientPort and Thrif
> tServerPort values. 10397 is the default.
> 10397
> 10397
> My query is should this port values be incremented according to the
> given offset values
>
>
> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
> Manager+2.0.0#b099f11ea91344af8835595ac455a7c1
>
>
> many thanks
> --
> *Dushantha Nayanajith Chandima Batuwita*
> Software Engineer Support | WSO2
> dushan...@wso2.com
> mobile : 0094777453010 <077%20745%203010>
>



 --
 Suminda Chamara Silva
 Technical Lead
 WSO2 Inc.
 Mobile: +94718302858 <+94%2071%20830%202858>
 blog: http://chamaras.blogspot.com


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Regards,
>>>
>>> *Viduranga Gunarathne*
>>>
>>> *Software Engineer Intern*
>>>
>>>
>>> *WSO2*
>>> Email : vidura...@wso2.com
>>> Mobile : +94712437484 <+94%2071%20243%207484>
>>> Web : http://wso2.com
>>> [image: https://wso2.com/signature] 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Samitha Chathuranga
>> Software Engineer, WSO2 Inc.
>> lean.enterprise.middleware
>> Mobile: +94715123761
>>
>> [image: http://wso2.com/signature] 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. :http://wso2.com/
>
> Office   :- *+94 11 2145345 

Re: [Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

[Chamalee De Silva]

hi Dushantha,

For API Manager 2.0.0 and later versions, we do not need to configure the
ThriftClient and ThriftServer ports as they get incremented according to
the offset.

For API Manager versions prior to APIM 2.0.0 we need to modify these ports
according to the port offset.

Please refer mail thread [1] for more information.



Thanks,
Chamalee

On Fri, Nov 24, 2017 at 11:40 AM, Samitha Chathuranga 
wrote:

> Hi Dushantha,
>
> The point is that by default those thrift port values are commented out.
> (if they are commented-out the all the port values are changed by the
> offset value ) If you uncomment them, you have to configure them correctly.
> By the way in the doc [1] you mentioned, note the below section, under the
> 3rd point under the topic "Installing and configuring API Manager".
>
> [image: Inline image 1]
>
> So the doc has been written not considering that optional step of port
> offsetting. So all ports mentioned in the doc are considering that there
> are no offsets.
>
> [1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
> Manager+2.0.0
>
> Regards,
> Samitha
>
> On Fri, Nov 24, 2017 at 9:09 AM, Viduranga Gunarathne 
> wrote:
>
>> Hi Dushantha,
>>
>> Yes. If you are using port offset to deploy the Gateway and KeyManager
>> nodes, then the default Thrift port (10397) in both the nodes will get
>> offset by the specified offset value.
>> Eg:
>> Gateway offset = 2,
>> Then  will be 10399
>>
>> KeyManager offset = 3,
>> Then  will be 10400
>>
>> In a clustered deployment, the KeyManager acts as the Thrift Server and
>> the Gateway as the Thrift client. Hence the Gateway uses the
>>  to send a request to the KeyManager where the request is
>> handled at the . For the communication to happen, both
>> the port values (ThriftServerPort in KeyManager and ThriftClientPort in
>> Gateway) should be of the same value. Unless the port offset of both the
>> Gateway and the KeyManager is the same, you will have to manually set the
>> two values.
>>
>> Thanks,
>> Viduranga.
>>
>> On Thu, Nov 23, 2017 at 9:24 PM, Chamara Silva  wrote:
>>
>>> This already in the public documentation. Please refer "Changing the
>>> Thrift client and server ports" section.
>>>
>>>
>>> [2] https://docs.wso2.com/display/AM210/Changing+the+Default
>>> +Ports+with+Offset
>>>
>>> Thanks,
>>> Chamara Silva
>>>
>>> On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita 
>>> wrote:
>>>
 Hi
 I'm involved in a gateway cluster set up in the local machine where the
 architecture is explained as follows

1. IS 5.3.0 as KM offset 0
2. Publisher/store/TM  offset 1
3. Gateway worker   offset 3
4. GatewayWorkerManger  offset 2

 I'm following the [1] Clustering API Manager document where it explains
 Configuring the Gateway > Configure key management related
 communication. >  c.  Specify the ThriftClientPort and ThriftServerPort
  values. 10397 is the default.
 10397
 10397
 My query is should this port values be incremented according to the
 given offset values


 [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
 Manager+2.0.0#b099f11ea91344af8835595ac455a7c1


 many thanks
 --
 *Dushantha Nayanajith Chandima Batuwita*
 Software Engineer Support | WSO2
 dushan...@wso2.com
 mobile : 0094777453010 <077%20745%203010>

>>>
>>>
>>>
>>> --
>>> Suminda Chamara Silva
>>> Technical Lead
>>> WSO2 Inc.
>>> Mobile: +94718302858 <+94%2071%20830%202858>
>>> blog: http://chamaras.blogspot.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> *Viduranga Gunarathne*
>>
>> *Software Engineer Intern*
>>
>>
>> *WSO2*
>> Email : vidura...@wso2.com
>> Mobile : +94712437484 <+94%2071%20243%207484>
>> Web : http://wso2.com
>> [image: https://wso2.com/signature] 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Samitha Chathuranga
> Software Engineer, WSO2 Inc.
> lean.enterprise.middleware
> Mobile: +94715123761
>
> [image: http://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

[Samitha Chathuranga]

Hi Dushantha,

The point is that by default those thrift port values are commented out.
(if they are commented-out the all the port values are changed by the
offset value ) If you uncomment them, you have to configure them correctly.
By the way in the doc [1] you mentioned, note the below section, under the
3rd point under the topic "Installing and configuring API Manager".

[image: Inline image 1]

So the doc has been written not considering that optional step of port
offsetting. So all ports mentioned in the doc are considering that there
are no offsets.

[1] - https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+2.0.0

Regards,
Samitha

On Fri, Nov 24, 2017 at 9:09 AM, Viduranga Gunarathne 
wrote:

> Hi Dushantha,
>
> Yes. If you are using port offset to deploy the Gateway and KeyManager
> nodes, then the default Thrift port (10397) in both the nodes will get
> offset by the specified offset value.
> Eg:
> Gateway offset = 2,
> Then  will be 10399
>
> KeyManager offset = 3,
> Then  will be 10400
>
> In a clustered deployment, the KeyManager acts as the Thrift Server and
> the Gateway as the Thrift client. Hence the Gateway uses the
>  to send a request to the KeyManager where the request is
> handled at the . For the communication to happen, both
> the port values (ThriftServerPort in KeyManager and ThriftClientPort in
> Gateway) should be of the same value. Unless the port offset of both the
> Gateway and the KeyManager is the same, you will have to manually set the
> two values.
>
> Thanks,
> Viduranga.
>
> On Thu, Nov 23, 2017 at 9:24 PM, Chamara Silva  wrote:
>
>> This already in the public documentation. Please refer "Changing the
>> Thrift client and server ports" section.
>>
>>
>> [2] https://docs.wso2.com/display/AM210/Changing+the+Default
>> +Ports+with+Offset
>>
>> Thanks,
>> Chamara Silva
>>
>> On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita 
>> wrote:
>>
>>> Hi
>>> I'm involved in a gateway cluster set up in the local machine where the
>>> architecture is explained as follows
>>>
>>>1. IS 5.3.0 as KM offset 0
>>>2. Publisher/store/TM  offset 1
>>>3. Gateway worker   offset 3
>>>4. GatewayWorkerManger  offset 2
>>>
>>> I'm following the [1] Clustering API Manager document where it explains
>>> Configuring the Gateway > Configure key management related
>>> communication. >  c.  Specify the ThriftClientPort and ThriftServerPort
>>>  values. 10397 is the default.
>>> 10397
>>> 10397
>>> My query is should this port values be incremented according to the
>>> given offset values
>>>
>>>
>>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
>>> Manager+2.0.0#b099f11ea91344af8835595ac455a7c1
>>>
>>>
>>> many thanks
>>> --
>>> *Dushantha Nayanajith Chandima Batuwita*
>>> Software Engineer Support | WSO2
>>> dushan...@wso2.com
>>> mobile : 0094777453010 <077%20745%203010>
>>>
>>
>>
>>
>> --
>> Suminda Chamara Silva
>> Technical Lead
>> WSO2 Inc.
>> Mobile: +94718302858 <+94%2071%20830%202858>
>> blog: http://chamaras.blogspot.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> *Viduranga Gunarathne*
>
> *Software Engineer Intern*
>
>
> *WSO2*
> Email : vidura...@wso2.com
> Mobile : +94712437484 <+94%2071%20243%207484>
> Web : http://wso2.com
> [image: https://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Samitha Chathuranga
Software Engineer, WSO2 Inc.
lean.enterprise.middleware
Mobile: +94715123761

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

[Viduranga Gunarathne]

Hi Dushantha,

Yes. If you are using port offset to deploy the Gateway and KeyManager
nodes, then the default Thrift port (10397) in both the nodes will get
offset by the specified offset value.
Eg:
Gateway offset = 2,
Then  will be 10399

KeyManager offset = 3,
Then  will be 10400

In a clustered deployment, the KeyManager acts as the Thrift Server and the
Gateway as the Thrift client. Hence the Gateway uses the 
to send a request to the KeyManager where the request is handled at the
. For the communication to happen, both the port values
(ThriftServerPort in KeyManager and ThriftClientPort in Gateway) should be
of the same value. Unless the port offset of both the Gateway and the
KeyManager is the same, you will have to manually set the two values.

Thanks,
Viduranga.

On Thu, Nov 23, 2017 at 9:24 PM, Chamara Silva  wrote:

> This already in the public documentation. Please refer "Changing the
> Thrift client and server ports" section.
>
>
> [2] https://docs.wso2.com/display/AM210/Changing+the+
> Default+Ports+with+Offset
>
> Thanks,
> Chamara Silva
>
> On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita 
> wrote:
>
>> Hi
>> I'm involved in a gateway cluster set up in the local machine where the
>> architecture is explained as follows
>>
>>1. IS 5.3.0 as KM offset 0
>>2. Publisher/store/TM  offset 1
>>3. Gateway worker   offset 3
>>4. GatewayWorkerManger  offset 2
>>
>> I'm following the [1] Clustering API Manager document where it explains
>> Configuring the Gateway > Configure key management related communication.
>> >  c.  Specify the ThriftClientPort and ThriftServerPort values. 10397 is
>> the default.
>> 10397
>> 10397
>> My query is should this port values be incremented according to the given
>> offset values
>>
>>
>> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+
>> Manager+2.0.0#b099f11ea91344af8835595ac455a7c1
>>
>>
>> many thanks
>> --
>> *Dushantha Nayanajith Chandima Batuwita*
>> Software Engineer Support | WSO2
>> dushan...@wso2.com
>> mobile : 0094777453010 <077%20745%203010>
>>
>
>
>
> --
> Suminda Chamara Silva
> Technical Lead
> WSO2 Inc.
> Mobile: +94718302858 <+94%2071%20830%202858>
> blog: http://chamaras.blogspot.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,

*Viduranga Gunarathne*

*Software Engineer Intern*


*WSO2*
Email : vidura...@wso2.com
Mobile : +94712437484
Web : http://wso2.com
[image: https://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

[Dushantha Batuwita]

Hi
I'm involved in a gateway cluster set up in the local machine where the
architecture is explained as follows

   1. IS 5.3.0 as KM offset 0
   2. Publisher/store/TM  offset 1
   3. Gateway worker   offset 3
   4. GatewayWorkerManger  offset 2

I'm following the [1] Clustering API Manager document where it explains
Configuring the Gateway > Configure key management related communication.
>  c.  Specify the ThriftClientPort and ThriftServerPort values. 10397 is
the default.
10397
10397
My query is should this port values be incremented according to the given
offset values


[1]
https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+2.0.0#b099f11ea91344af8835595ac455a7c1


many thanks
-- 
*Dushantha Nayanajith Chandima Batuwita*
Software Engineer Support | WSO2
dushan...@wso2.com
mobile : 0094777453010
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to set ThriftClientPort in APIM Gate Way Node in a cluster setup

[Chamara Silva]

This already in the public documentation. Please refer "Changing the Thrift
client and server ports" section.


[2]
https://docs.wso2.com/display/AM210/Changing+the+Default+Ports+with+Offset

Thanks,
Chamara Silva

On Thu, Nov 23, 2017 at 7:57 PM, Dushantha Batuwita 
wrote:

> Hi
> I'm involved in a gateway cluster set up in the local machine where the
> architecture is explained as follows
>
>1. IS 5.3.0 as KM offset 0
>2. Publisher/store/TM  offset 1
>3. Gateway worker   offset 3
>4. GatewayWorkerManger  offset 2
>
> I'm following the [1] Clustering API Manager document where it explains
> Configuring the Gateway > Configure key management related communication.
> >  c.  Specify the ThriftClientPort and ThriftServerPort values. 10397 is
> the default.
> 10397
> 10397
> My query is should this port values be incremented according to the given
> offset values
>
>
> [1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+2.0.0#
> b099f11ea91344af8835595ac455a7c1
>
>
> many thanks
> --
> *Dushantha Nayanajith Chandima Batuwita*
> Software Engineer Support | WSO2
> dushan...@wso2.com
> mobile : 0094777453010 <077%20745%203010>
>



-- 
Suminda Chamara Silva
Technical Lead
WSO2 Inc.
Mobile: +94718302858
blog: http://chamaras.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev