Hi Nicolas,

I saw the documentation of wso2, normally we should share the same file
system between the wso2 api-m and point to one wso2 api-m, my question is
what folder we share all the wso2 api-m folder ?

We share the file system because to sync the artifacts among gateway nodes.
So what you have to share is <api-m_server>/repository/deployment/server
folder of gateway nodes.


In order to enable communication between gateway and is-km you have to
configure gateway server url in identity.xml of IS server.
For that If you use NFS as the file sharing mechanism you can use server
url of *any of the gateway* nodes.

But if you use rsync you have to use gateway manager server url as the
gateway url in identity.xml of IS server.

Thanks & Regards,
Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

On Fri, Aug 31, 2018 at 3:12 AM, Nicolas Maujean <
nicolas.maujean.fra...@gmail.com> wrote:

> hi,
>
>    how can we connect one wso2-is to several wso2-apim ?
> I saw the documentation of wso2, normally we should share the same file
> system between the wso2 api-m and point to one wso2 api-m, my question is
> what folder we share all the wso2 api-m folder ?
>
> When users and roles are removed via the Key Manager, if the corresponding
> user tokens are cached on the Gateway, these tokens will only get
> invalidated when the cache is timed out. However, if Hazelcast clustering
> is enabled, token invalidation takes place immediately. Therefore, you need
> to enable communication between the Key Manager and Gateway to enable
> immediate token invalidation.
>
> For this purpose open the <IS_HOME>/repository/conf/api-manager.xml file
> and change the <ServerURL> element that appears under the <APIGateway>
> section, so that it points to the API Manager server.
>
> <ServerURL>https://${gateway-server-host}:{port}/services/</ServerURL>
> If you are working with a hybrid single node or active-active node
> deployment where WSO2 IS is the Key Manager and the rest of the API-M
> components are in one node, you need to replace  {gateway-server-host} with
> the host of the WSO2 API-M node.
> If you are working with a single Gateway in distributed set up, you need
> to replace {gateway-server-host} with the host of the Gateway node.
> If you are working with Gateways in a High Availability (HA) set up that
> uses a shared file system (e.g., NFS), you need to replace
> {gateway-server-host} with the host of any Gateway node as all nodes have
> the worker manager capability when using shared file system.
> If you are working with Gateways in a High Availability (HA) set up that
> uses rsync, you need to replace {gateway-server-host} with the host of the
> Gateway Manager node.
>
> The port value you enter here should be the management transport port. For
> more information, see Default Product Ports.
>
> best regards,
>
> Nicolas Maujean
>
> Le mer. 29 août 2018 à 13:48, Nicolas Maujean <
> nicolas.maujean.fra...@gmail.com> a écrit :
>
>> Hi,
>>
>>    Thank you for your feedback. Wso2 IS  as Key manager,
>>
>> Best regards,
>>
>> Nicolas Maujean
>>
>>
>> Le mer. 29 août 2018 à 13:26, Pubudu Gunatilaka <pubu...@wso2.com> a
>> écrit :
>>
>>> Hi,
>>>
>>> What is the use case? Is this for IS as Key Manager? SSO?
>>>
>>> Thank you!
>>>
>>> On Wed, Aug 29, 2018 at 3:11 AM Nicolas Maujean <
>>> nicolas.maujean.fra...@gmail.com> wrote:
>>>
>>>> hi,
>>>>
>>>>   I would like to connect several wso2 api-m to a single wso2 is. Is it
>>>> possible ? if yes how I can make the connection between the wso2 api-m and
>>>> wso2 is ?
>>>>
>>>> best regards,
>>>>
>>>> Nicolas Maujean
>>>>
>>> _______________________________________________
>>>> Architecture mailing list
>>>> Architecture@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>>>
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>
> _______________________________________________
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to