From Pritam.Lahoti at cognizant.com  Wed Nov 14 06:46:32 2018
From: Pritam.Lahoti at cognizant.com (Pritam.Lahoti at cognizant.com)
Date: Wed, 14 Nov 2018 11:46:32 +0000
Subject: [Apiman-user] APIMAN database query
Message-ID: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>

Hi Team,

We are currently evaluating APIMAN as API lifecycle management solution and have some specific queries around -


  1.  Best Suitable database?
  2.  Re-commanded Sizing of database as per application size?

Thanks and Regards,
Pritam Lahoti
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181114/f112f8e4/attachment-0001.html 

From marc.savy at redhat.com  Wed Nov 21 08:34:58 2018
From: marc.savy at redhat.com (Marc Savy)
Date: Wed, 21 Nov 2018 13:34:58 +0000
Subject: [Apiman-user] publish api to specific gateway
In-Reply-To: <CAP45m-bndU3jqRwzgHQAY3PDNyYS3mUQGY4-cnenGvHZCX=FfQ@mail.gmail.com>
References: <CAP45m-bndU3jqRwzgHQAY3PDNyYS3mUQGY4-cnenGvHZCX=FfQ@mail.gmail.com>
Message-ID: <CAA7j38LDcGodo5FEsDjGtkRxX5B-4Wa1bw1QzS4O__eEOj2MFw@mail.gmail.com>

Apologies for the terribly slow reply. We've had so much spam I've missed
legitimate emails like this.

Did you explicitly untick the other gateway? Was this via the UI or the API?

Did you resolve this issue? If not, please file a bug:
https://github.com/apiman/apiman/issues

On Thu, 4 Oct 2018 at 05:00, Jon Huang <chttl582 at gmail.com> wrote:

> Dears
>
> I had set up 2 gateways.
> When I new an API, I have to choose which gateway to publish. (select list
> at Gateway section in the implementation tab).
> However after creating a client app and contract for test, I found request
> via another gateway still works.
> (I guest when publishing to gateway 1 and request via gateway 2 shall fail)
> Am I misunderstanding or I miss some settings to make it work?
> Thanks
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181121/20b26e78/attachment.html 

From marc.savy at redhat.com  Wed Nov 21 08:35:36 2018
From: marc.savy at redhat.com (Marc Savy)
Date: Wed, 21 Nov 2018 13:35:36 +0000
Subject: [Apiman-user] Keycloak OAuth plugin persistence bug
In-Reply-To: <CAEAM05dxUwm1AqkAAWNLWedNto+gFTgQtLDCmEpOin9uF7UnLQ@mail.gmail.com>
References: <CAEAM05ct2rLhEcw97ZeRMN0Q5-uc6Sq-d7gdvJH5izoiwGGiNg@mail.gmail.com>
	<CAA7j38+KUCUY2-ZLxunV=Hxw52+xxPBUEDdDf=AsymQeSVj3+A@mail.gmail.com>
	<CAEAM05eionJHg-qBySSGCqEbU3aXWHAiR4KyJV1UVPvB1Ga5OA@mail.gmail.com>
	<CAA7j38JwR3xMqbbouMgdvVarW5iidA0nhHHz+Jj_8Uu-ySp9KQ@mail.gmail.com>
	<CAEAM05dxUwm1AqkAAWNLWedNto+gFTgQtLDCmEpOin9uF7UnLQ@mail.gmail.com>
Message-ID: <CAA7j38+W3WdfzYV2U5ixHjZnF7q-wSM9A91V_iVdtOkioDQdjA@mail.gmail.com>

Did this work okay? If not, please file a bug when you have a free moment
https://github.com/apiman/apiman/issues

On Wed, 10 Oct 2018 at 13:28, Mohamed Oukfif <mohamed.oukfif at devoteam.com>
wrote:

>
> Hello Marc,
>
> Thanks,for answer. I just installed the last version of APIMAN :
> Version: 1.5.1.Final
> Built On: 2018-07-27_10:37
>
> I ask custumers to make tests. I hope it will be ok :-)
>
> Mohamed
>
> Le mer. 19 sept. 2018 ? 11:07, Marc Savy <marc.savy at redhat.com> a ?crit :
>
>> Hi Mohamed,
>>
>> So, even with the latest version of Apiman you still see this happening?
>>
>> I thought we'd fixed it, but perhaps not.
>>
>> Regards,
>> Marc
>>
>> On 13 September 2018 at 08:13, Mohamed Oukfif
>> <mohamed.oukfif at devoteam.com> wrote:
>> > Hey Marc,
>> >
>> > There is the link :
>> > http://lists.jboss.org/pipermail/apiman-user/2017-June/000890.html
>> >
>> > We have a millions of records in pd_templates table.
>> >
>> > Regards,
>> > Mohamed
>> >
>> > 2018-09-13 0:52 GMT+02:00 Marc Savy <marc.savy at redhat.com>:
>> >>
>> >> Hey Mohamed,
>> >>
>> >> Appreciate your message about Apiman!
>> >>
>> >> Could you elaborate a bit. What problem are you specifically referring
>> >> to? Could you outline when the constraint is a problem for you?
>> >>
>> >> Regards,
>> >> Marc
>> >>
>> >> On 12 September 2018 at 16:29, Mohamed Oukfif
>> >> <mohamed.oukfif at devoteam.com> wrote:
>> >> > Hello,
>> >> >
>> >> > We have the same issue. Do you think this constraint solves the
>> problem?
>> >> >
>> >> > "constraint_name" UNIQUE CONSTRAINT, btree (policydef_id, template)
>> >> >
>> >> > Best regards,
>> >> > M.Oukfif
>> >> >
>> >> > _______________________________________________
>> >> > Apiman-user mailing list
>> >> > Apiman-user at lists.jboss.org
>> >> > https://lists.jboss.org/mailman/listinfo/apiman-user
>> >> >
>> >
>> >
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181121/8b3608c4/attachment.html 

From marc.savy at redhat.com  Wed Nov 21 08:36:44 2018
From: marc.savy at redhat.com (Marc Savy)
Date: Wed, 21 Nov 2018 13:36:44 +0000
Subject: [Apiman-user] export/import data config in apiman
In-Reply-To: <CAEDnbHAMe_QXpa6bW9jXEjDy35ah=Y+=MEnBMNt2dUcacwutKg@mail.gmail.com>
References: <CAEDnbHB1pHGYigiLLNBWq=A48r-9kg4jMXi_n0_Qa3sxNLc9LQ@mail.gmail.com>
	<CAEDnbHDgnWbo_pFkRhQzy=O1gw3tzxSTa+zS=nPnSY2Jf=a-_g@mail.gmail.com>
	<CAA7j38KXthekVKpfDx4NXsbeqKOG0pn_04x3As=VZVXKyiPo1g@mail.gmail.com>
	<CAEDnbHAMe_QXpa6bW9jXEjDy35ah=Y+=MEnBMNt2dUcacwutKg@mail.gmail.com>
Message-ID: <CAA7j38LOGNJv+3Fu4TQKF=bmqipzQ8ET9195DJ-dsh3R=q3CkA@mail.gmail.com>

Hmm, that error looks like corruption of some sort. How often does it
happen?

On Mon, 24 Sep 2018 at 16:59, Balu S <sbalu27 at gmail.com> wrote:

> Hi Marc,
>
> Thanks for your reply.  If I republish the API, then it works. But if I
> have 100s of API, then it seems a quite a work.
> I wish this can be auto registered when using export/import.
>
> FYI, I noticed an old exception (which did not occur in 1.3.1) version
> when loading the custom plugin. It looks like it is related to snapshot
> versions.
> I shall check further.
>
> 2018-09-24 16:16:57,376 ERROR [org.jboss.msc.service.fail] (ServerService
> Thread Pool -- 82) MSC000001: Failed to start service
> jboss.undertow.deployment.default-server.default-h
> ost./apiman-gateway-api: org.jboss.msc.service.StartException in service
> jboss.undertow.deployment.default-server.default-host./apiman-gateway-api:
> java.lang.RuntimeException: ja
> va.lang.RuntimeException: java.lang.Exception: Invalid plugin file at:
> /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/0.0.1-SNAPSHO
> T/apimancustom-failure.war/plugin.war
>         at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:84)
>         at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>         at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
>         at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.Exception: Invalid plugin file at:
> /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/0.0.1-SNAPSHOT/apiman-custom-failure.war/plugin.war
>         at
> io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:241)
>         at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:99)
>         at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
>         ... 6 more
> Caused by: java.lang.RuntimeException: java.lang.Exception: Invalid plugin
> file at:
> /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/
> 0.0.1-SNAPSHOT/apiman-custom-failure.war/plugin.war
>         at
> io.apiman.gateway.platforms.war.WarEngineConfig.loadConfigClass(WarEngineConfig.java:314)
>         at
> io.apiman.gateway.platforms.war.WarEngineConfig.getPolicyFailureWriterClass(WarEngineConfig.java:212)
>         at
> io.apiman.gateway.platforms.war.WarGateway.loadFailureFormatter(WarGateway.java:70)
>         at
> io.apiman.gateway.platforms.war.WarGateway.init(WarGateway.java:56)
>         at
> io.apiman.gateway.platforms.war.listeners.WarGatewayBootstrapper.contextInitialized(WarGatewayBootstrapper.java:42)
>         at
> io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
>         at
> io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:205)
>         at
> io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:174)
>         at
> io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
>         at
> io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
>         at
> org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
>         at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
>         at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
>         at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
>         at
> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
>         at
> io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:239)
>         ... 8 more
> Caused by: java.lang.Exception: Invalid plugin file at:
> /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/0.0.1-SNAPSHOT/apiman-custom
> -failure.war/plugin.war
>         at
> io.apiman.gateway.engine.impl.DefaultPluginRegistry.readPluginFile(DefaultPluginRegistry.java:309)
>         at
> io.apiman.gateway.engine.impl.DefaultPluginRegistry.loadPlugin(DefaultPluginRegistry.java:246)
>         at
> io.apiman.gateway.platforms.war.WarEngineConfig.loadConfigClass(WarEngineConfig.java:311)
>         ... 23 more
>
>
> On Fri, Sep 21, 2018 at 4:40 PM Marc Savy <marc.savy at redhat.com> wrote:
>
>> Have you tried republishing those APIs and/or migrating the api_gateway
>> index?
>>
>> On 21 September 2018 at 15:04, Balu S <sbalu27 at gmail.com> wrote:
>> > Further to this email.
>> >
>> > The export/import tool provided in Apiman manager seems not complete.
>> After
>> > I have imported the apimanager configuration to new environment using
>> the
>> > tool, accessing the public API URL gives below error. It tries to check
>> the
>> > existence of API in the Elasticsearch. But the import/export tool never
>> > imports anything to ES index.
>> >
>> > Does it mean we have to explicitly migrate the existing ES index to new
>> ES
>> > server ?
>> >
>> > io.apiman.gateway.engine.beans.exceptions.ApiNotFoundException: API not
>> > found.
>> >         at
>> >
>> io.apiman.gateway.engine.impl.ApiRequestExecutorImpl.lambda$execute$5(ApiRequestExecutorImpl.java:340)
>> >         at
>> >
>> io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:123)
>> >         at
>> >
>> io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:112)
>> >         at
>> > io.apiman.gateway.engine.es
>> .CachingESRegistry.getApi(CachingESRegistry.java:117)
>> >
>> >
>> > On Tue, Sep 18, 2018 at 12:38 PM Balu S <sbalu27 at gmail.com> wrote:
>> >>
>> >> Hi Eric, Marc,
>> >>
>> >> I have used this export/import option in Apiman to migrate data from
>> 1.3
>> >> to 1.5.1 version.The tools works fine and I can see the apis, policies
>> and
>> >> client apps, users are created in migrated environment.
>> >>
>> >> However if I notice, there are some config information stored in
>> >> Elasticsearch under the index apiman_gateway. There are like 21
>> records for
>> >> this index in Kibana. These data seems to resemble the client and api
>> >> information.
>> >>
>> >> What are these data ? Is the exported "api manager"data different from
>> >> "apiman gateway" data ? If so why are these not migrated using
>> export/import
>> >> utility ?
>> >>
>> >> Thanks for reading my post.
>> >>
>> >> Best regards
>> >> Balu.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181121/6fd76d8c/attachment-0001.html 

From sbalu27 at gmail.com  Wed Nov 21 11:30:15 2018
From: sbalu27 at gmail.com (Balu S)
Date: Wed, 21 Nov 2018 17:30:15 +0100
Subject: [Apiman-user] export/import data config in apiman
In-Reply-To: <CAA7j38LOGNJv+3Fu4TQKF=bmqipzQ8ET9195DJ-dsh3R=q3CkA@mail.gmail.com>
References: <CAEDnbHB1pHGYigiLLNBWq=A48r-9kg4jMXi_n0_Qa3sxNLc9LQ@mail.gmail.com>
	<CAEDnbHDgnWbo_pFkRhQzy=O1gw3tzxSTa+zS=nPnSY2Jf=a-_g@mail.gmail.com>
	<CAA7j38KXthekVKpfDx4NXsbeqKOG0pn_04x3As=VZVXKyiPo1g@mail.gmail.com>
	<CAEDnbHAMe_QXpa6bW9jXEjDy35ah=Y+=MEnBMNt2dUcacwutKg@mail.gmail.com>
	<CAA7j38LOGNJv+3Fu4TQKF=bmqipzQ8ET9195DJ-dsh3R=q3CkA@mail.gmail.com>
Message-ID: <CAEDnbHB9H5pF7i0Bp0iNq2uSX6duv3+JTffwRhafVd42nY1pWw@mail.gmail.com>

Hi Marc,

sorry forgot to update back. It looks like I played with some data but when
I tried with clean environment it did not happen again.
however below issue still persists and is reproduced everytime. Could you
please check. Thanks.

https://issues.jboss.org/projects/APIMAN/issues/APIMAN-1347


On Wed, Nov 21, 2018 at 2:36 PM Marc Savy <marc.savy at redhat.com> wrote:

> Hmm, that error looks like corruption of some sort. How often does it
> happen?
>
> On Mon, 24 Sep 2018 at 16:59, Balu S <sbalu27 at gmail.com> wrote:
>
>> Hi Marc,
>>
>> Thanks for your reply.  If I republish the API, then it works. But if I
>> have 100s of API, then it seems a quite a work.
>> I wish this can be auto registered when using export/import.
>>
>> FYI, I noticed an old exception (which did not occur in 1.3.1) version
>> when loading the custom plugin. It looks like it is related to snapshot
>> versions.
>> I shall check further.
>>
>> 2018-09-24 16:16:57,376 ERROR [org.jboss.msc.service.fail] (ServerService
>> Thread Pool -- 82) MSC000001: Failed to start service
>> jboss.undertow.deployment.default-server.default-h
>> ost./apiman-gateway-api: org.jboss.msc.service.StartException in service
>> jboss.undertow.deployment.default-server.default-host./apiman-gateway-api:
>> java.lang.RuntimeException: ja
>> va.lang.RuntimeException: java.lang.Exception: Invalid plugin file at:
>> /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/0.0.1-SNAPSHO
>> T/apimancustom-failure.war/plugin.war
>>         at
>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:84)
>>         at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>         at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>         at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>         at java.lang.Thread.run(Thread.java:748)
>>         at org.jboss.threads.JBossThread.run(JBossThread.java:320)
>> Caused by: java.lang.RuntimeException: java.lang.RuntimeException:
>> java.lang.Exception: Invalid plugin file at:
>> /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/0.0.1-SNAPSHOT/apiman-custom-failure.war/plugin.war
>>         at
>> io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:241)
>>         at
>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:99)
>>         at
>> org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
>>         ... 6 more
>> Caused by: java.lang.RuntimeException: java.lang.Exception: Invalid
>> plugin file at:
>> /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/
>> 0.0.1-SNAPSHOT/apiman-custom-failure.war/plugin.war
>>         at
>> io.apiman.gateway.platforms.war.WarEngineConfig.loadConfigClass(WarEngineConfig.java:314)
>>         at
>> io.apiman.gateway.platforms.war.WarEngineConfig.getPolicyFailureWriterClass(WarEngineConfig.java:212)
>>         at
>> io.apiman.gateway.platforms.war.WarGateway.loadFailureFormatter(WarGateway.java:70)
>>         at
>> io.apiman.gateway.platforms.war.WarGateway.init(WarGateway.java:56)
>>         at
>> io.apiman.gateway.platforms.war.listeners.WarGatewayBootstrapper.contextInitialized(WarGatewayBootstrapper.java:42)
>>         at
>> io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
>>         at
>> io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:205)
>>         at
>> io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:174)
>>         at
>> io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
>>         at
>> io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
>>         at
>> org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
>>         at
>> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
>>         at
>> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
>>         at
>> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
>>         at
>> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
>>         at
>> io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:239)
>>         ... 8 more
>> Caused by: java.lang.Exception: Invalid plugin file at:
>> /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/0.0.1-SNAPSHOT/apiman-custom
>> -failure.war/plugin.war
>>         at
>> io.apiman.gateway.engine.impl.DefaultPluginRegistry.readPluginFile(DefaultPluginRegistry.java:309)
>>         at
>> io.apiman.gateway.engine.impl.DefaultPluginRegistry.loadPlugin(DefaultPluginRegistry.java:246)
>>         at
>> io.apiman.gateway.platforms.war.WarEngineConfig.loadConfigClass(WarEngineConfig.java:311)
>>         ... 23 more
>>
>>
>> On Fri, Sep 21, 2018 at 4:40 PM Marc Savy <marc.savy at redhat.com> wrote:
>>
>>> Have you tried republishing those APIs and/or migrating the api_gateway
>>> index?
>>>
>>> On 21 September 2018 at 15:04, Balu S <sbalu27 at gmail.com> wrote:
>>> > Further to this email.
>>> >
>>> > The export/import tool provided in Apiman manager seems not complete.
>>> After
>>> > I have imported the apimanager configuration to new environment using
>>> the
>>> > tool, accessing the public API URL gives below error. It tries to
>>> check the
>>> > existence of API in the Elasticsearch. But the import/export tool never
>>> > imports anything to ES index.
>>> >
>>> > Does it mean we have to explicitly migrate the existing ES index to
>>> new ES
>>> > server ?
>>> >
>>> > io.apiman.gateway.engine.beans.exceptions.ApiNotFoundException: API not
>>> > found.
>>> >         at
>>> >
>>> io.apiman.gateway.engine.impl.ApiRequestExecutorImpl.lambda$execute$5(ApiRequestExecutorImpl.java:340)
>>> >         at
>>> >
>>> io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:123)
>>> >         at
>>> >
>>> io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:112)
>>> >         at
>>> > io.apiman.gateway.engine.es
>>> .CachingESRegistry.getApi(CachingESRegistry.java:117)
>>> >
>>> >
>>> > On Tue, Sep 18, 2018 at 12:38 PM Balu S <sbalu27 at gmail.com> wrote:
>>> >>
>>> >> Hi Eric, Marc,
>>> >>
>>> >> I have used this export/import option in Apiman to migrate data from
>>> 1.3
>>> >> to 1.5.1 version.The tools works fine and I can see the apis,
>>> policies and
>>> >> client apps, users are created in migrated environment.
>>> >>
>>> >> However if I notice, there are some config information stored in
>>> >> Elasticsearch under the index apiman_gateway. There are like 21
>>> records for
>>> >> this index in Kibana. These data seems to resemble the client and api
>>> >> information.
>>> >>
>>> >> What are these data ? Is the exported "api manager"data different from
>>> >> "apiman gateway" data ? If so why are these not migrated using
>>> export/import
>>> >> utility ?
>>> >>
>>> >> Thanks for reading my post.
>>> >>
>>> >> Best regards
>>> >> Balu.
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181121/d9adb611/attachment.html 

From marc.savy at redhat.com  Wed Nov 21 12:15:46 2018
From: marc.savy at redhat.com (Marc Savy)
Date: Wed, 21 Nov 2018 17:15:46 +0000
Subject: [Apiman-user] APIMAN database query
In-Reply-To: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
References: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
Message-ID: <CAA7j38+7n5T_u=E=aLAREvkWL4M2ZwcYU3FWGqHbEx=fLvEpCg@mail.gmail.com>

On Wed, 21 Nov 2018 at 13:34, <Pritam.Lahoti at cognizant.com> wrote:

> Hi Team,
>
> We are currently evaluating APIMAN as API lifecycle management solution
> and have some specific queries around -
>
>
>    1. Best Suitable database?
>
>
Any of the supported datastores should be great.

If you are referring specifically to JDBC, then there are lots of great
options, but PostgreSQL seems to be a favourite amongst open sourcers.


>
>    1. Re-commanded Sizing of database as per application size?
>
>
This really depends on your runtime requirements; I suggest you experiment
a bit (unless someone from the community wants to weigh in and provide some
feedback.


>
> Thanks and Regards,
> Pritam Lahoti
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181121/415b22fa/attachment.html 

From Florian.Volk at scheer-group.com  Thu Nov 22 03:24:31 2018
From: Florian.Volk at scheer-group.com (Volk, Florian)
Date: Thu, 22 Nov 2018 08:24:31 +0000
Subject: [Apiman-user] APIMAN database query
In-Reply-To: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
References: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
Message-ID: <33aa625a6e824d308c9a580c44328d6f@sgrpexc001.scheer.systems>

Hi Pritam,

maybe our anwers help you with your decision:


1.       We use Elasticsearch. Until now it works very well and reliable. Also ES is very fast if it comes to metrics and analysis.

2.       We made around 3 million requests against the gateway, after that we had have around 600 MB of data in our Elasticseach (with metrics enabled of course.)

Regards
Florian

Von: apiman-user-bounces at lists.jboss.org <apiman-user-bounces at lists.jboss.org> Im Auftrag von Pritam.Lahoti at cognizant.com
Gesendet: Wednesday, 14 November 2018 12:47
An: apiman-user at lists.jboss.org
Betreff: [Apiman-user] APIMAN database query

Hi Team,

We are currently evaluating APIMAN as API lifecycle management solution and have some specific queries around -


  1.  Best Suitable database?
  2.  Re-commanded Sizing of database as per application size?

Thanks and Regards,
Pritam Lahoti
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181122/c4e7c342/attachment-0001.html 

From marc.savy at redhat.com  Thu Nov 22 18:25:40 2018
From: marc.savy at redhat.com (Marc Savy)
Date: Thu, 22 Nov 2018 23:25:40 +0000
Subject: [Apiman-user] APIMAN with Keycloak
In-Reply-To: <127746c1-6d2c-7e06-5874-f12d1ebeedeb@3gca.org>
References: <127746c1-6d2c-7e06-5874-f12d1ebeedeb@3gca.org>
Message-ID: <CAA7j38K=T1pVtSeYon1pkxGG-dGojGzn9XKXhSaMVP-4p_r5Yw@mail.gmail.com>

Hi Yasir,

If I understand your query correctly:

Keycloak's JWT tokens have an expiry (i.e. lifetime, often a few minutes).
Even if you log out that session in Keycloak, it might be a few minutes
until the token already issued to the user expires.

There are mechanisms to explicitly revoke/blacklist tokens before the
expiry has been reached, but they are not currently supported by Apiman.

Regards,
Marc

On Wed, 21 Nov 2018 at 13:34, Yasir Zeeshan <yasir.z at 3gca.org> wrote:

> Hi,
>
> I implemented apiman with keycloak, it is working fine with
> <http://192.168.100.211:8081/apimanui/api-manager/admin/plugins/1008>*keycloak
> OAuth policy* and *authorization policy *plugin but if i logout a user
> session from keycloak but it still works on apiman, where it doesn't have
> to give access and show 401.
>
>
> Regards,
>
> Yasir
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181122/af5965d0/attachment.html 

From Pritam.Lahoti at cognizant.com  Tue Nov 27 10:23:38 2018
From: Pritam.Lahoti at cognizant.com (Pritam.Lahoti at cognizant.com)
Date: Tue, 27 Nov 2018 15:23:38 +0000
Subject: [Apiman-user] APIMAN database query
In-Reply-To: <33aa625a6e824d308c9a580c44328d6f@sgrpexc001.scheer.systems>
References: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>,
	<33aa625a6e824d308c9a580c44328d6f@sgrpexc001.scheer.systems>
Message-ID: <SL2PR02MB36601E647360B5CB7C8C22F9F2D00@SL2PR02MB3660.apcprd02.prod.outlook.com>

Thanks for the replies Team.


I have some of the queries as-

  1.  Can we deploy APIMAN on pivotal cloud foundry?
  2.  How to scale the APIMAN?
  3.  Hows is the performance of it?
  4.  Any licencing or cost information ?


Thanks and Regdards,

Pritam Lahoti

________________________________
From: Volk, Florian <Florian.Volk at scheer-group.com>
Sent: Thursday, November 22, 2018 8:24:31 AM
To: Lahoti, Pritam (Cognizant); apiman-user at lists.jboss.org
Subject: AW: APIMAN database query


Hi Pritam,



maybe our anwers help you with your decision:



1.       We use Elasticsearch. Until now it works very well and reliable. Also ES is very fast if it comes to metrics and analysis.

2.       We made around 3 million requests against the gateway, after that we had have around 600 MB of data in our Elasticseach (with metrics enabled of course.)



Regards

Florian



Von: apiman-user-bounces at lists.jboss.org <apiman-user-bounces at lists.jboss.org> Im Auftrag von Pritam.Lahoti at cognizant.com
Gesendet: Wednesday, 14 November 2018 12:47
An: apiman-user at lists.jboss.org
Betreff: [Apiman-user] APIMAN database query



Hi Team,



We are currently evaluating APIMAN as API lifecycle management solution and have some specific queries around -



  1.  Best Suitable database?
  2.  Re-commanded Sizing of database as per application size?



Thanks and Regards,

Pritam Lahoti
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181127/ea14ff6c/attachment.html 

From marc.savy at redhat.com  Tue Nov 27 19:38:15 2018
From: marc.savy at redhat.com (Marc Savy)
Date: Wed, 28 Nov 2018 00:38:15 +0000
Subject: [Apiman-user] APIMAN database query
In-Reply-To: <SL2PR02MB36601E647360B5CB7C8C22F9F2D00@SL2PR02MB3660.apcprd02.prod.outlook.com>
References: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<33aa625a6e824d308c9a580c44328d6f@sgrpexc001.scheer.systems>
	<SL2PR02MB36601E647360B5CB7C8C22F9F2D00@SL2PR02MB3660.apcprd02.prod.outlook.com>
Message-ID: <CAA7j38J_YZWSaTV4bf=BK0+4OVPeHkY9ubzROVqfN2Zj44r3Pw@mail.gmail.com>

On Wed, 28 Nov 2018 at 00:34, <Pritam.Lahoti at cognizant.com> wrote:

> Thanks for the replies Team.
>
>
> I have some of the queries as-
>
>
>    - Can we deploy APIMAN on pivotal cloud foundry?
>
>
I've never used Pivotal Cloud Foundry, I'm afraid. Perhaps another
community member can answer.


>
>    - How to scale the APIMAN?
>
>
You can add as many gateways as you need with the same configuration, which
allows you to scale horizontally



>
>    - Hows is the performance of it?
>
> You'll have to test for your own use-cases and it's highly dependent upon
configuration and which components you use. But, it should be more than
enough for most use-cases.

The real question here is: what are your requirements?

>
>    - Any licencing or cost information ?
>
>
Apiman is a free and open source project.


>
> Thanks and Regdards,
>
> Pritam Lahoti
> ------------------------------
> *From:* Volk, Florian <Florian.Volk at scheer-group.com>
> *Sent:* Thursday, November 22, 2018 8:24:31 AM
> *To:* Lahoti, Pritam (Cognizant); apiman-user at lists.jboss.org
> *Subject:* AW: APIMAN database query
>
>
> Hi Pritam,
>
>
>
> maybe our anwers help you with your decision:
>
>
>
> 1.       We use Elasticsearch. Until now it works very well and reliable.
> Also ES is very fast if it comes to metrics and analysis.
>
> 2.       We made around 3 million requests against the gateway, after
> that we had have around 600 MB of data in our Elasticseach (with metrics
> enabled of course.)
>
>
>
> Regards
>
> Florian
>
>
>
> *Von:* apiman-user-bounces at lists.jboss.org <
> apiman-user-bounces at lists.jboss.org> *Im Auftrag von *
> Pritam.Lahoti at cognizant.com
> *Gesendet:* Wednesday, 14 November 2018 12:47
> *An:* apiman-user at lists.jboss.org
> *Betreff:* [Apiman-user] APIMAN database query
>
>
>
> Hi Team,
>
>
>
> We are currently evaluating APIMAN as API lifecycle management solution
> and have some specific queries around -
>
>
>
>    1. Best Suitable database?
>    2. Re-commanded Sizing of database as per application size?
>
>
>
> Thanks and Regards,
>
> Pritam Lahoti
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181128/44d30b03/attachment-0001.html 

From Florian.Volk at scheer-group.com  Wed Nov 28 03:37:44 2018
From: Florian.Volk at scheer-group.com (Volk, Florian)
Date: Wed, 28 Nov 2018 08:37:44 +0000
Subject: [Apiman-user] APIMAN database query
In-Reply-To: <CAA7j38J_YZWSaTV4bf=BK0+4OVPeHkY9ubzROVqfN2Zj44r3Pw@mail.gmail.com>
References: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<33aa625a6e824d308c9a580c44328d6f@sgrpexc001.scheer.systems>
	<SL2PR02MB36601E647360B5CB7C8C22F9F2D00@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<CAA7j38J_YZWSaTV4bf=BK0+4OVPeHkY9ubzROVqfN2Zj44r3Pw@mail.gmail.com>
Message-ID: <058e68bc19424f91b14b1f532699f40b@sgrpexc002.scheer.systems>

Hello, apiman comunity

I will try to anwser your questions:

  1.  Can we deploy APIMAN on pivotal cloud foundry?
We don?t use this.

  1.  How to scale the APIMAN?
We put the vertx gateway in a docker container so we can easily scale thne number of gateways if we need more than one.

  1.  Hows is the performance of it?
Our product is based on apiman. But we dockerized the whole apiman stack.
Recently we made some load tests with some policies. Your can see the results in our forum blog post.
https://forum.e2ebridge.com/forums/topic/api-management-loadtests-results/

I hope our information will help you.

Best regards
Florian

Von: Marc Savy <marc.savy at redhat.com>
Gesendet: Wednesday, 28 November 2018 01:38
An: Pritam.Lahoti at cognizant.com
Cc: Volk, Florian <Florian.Volk at scheer-group.com>; apiman-user at lists.jboss.org
Betreff: Re: [Apiman-user] APIMAN database query

On Wed, 28 Nov 2018 at 00:34, <Pritam.Lahoti at cognizant.com<mailto:Pritam.Lahoti at cognizant.com>> wrote:

Thanks for the replies Team.



I have some of the queries as-

  *   Can we deploy APIMAN on pivotal cloud foundry?

I've never used Pivotal Cloud Foundry, I'm afraid. Perhaps another community member can answer.


  *   How to scale the APIMAN?

You can add as many gateways as you need with the same configuration, which allows you to scale horizontally



  *   Hows is the performance of it?
You'll have to test for your own use-cases and it's highly dependent upon configuration and which components you use. But, it should be more than enough for most use-cases.

The real question here is: what are your requirements?

  *   Any licencing or cost information ?

Apiman is a free and open source project.



Thanks and Regdards,

Pritam Lahoti

________________________________
From: Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>>
Sent: Thursday, November 22, 2018 8:24:31 AM
To: Lahoti, Pritam (Cognizant); apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Subject: AW: APIMAN database query


Hi Pritam,



maybe our anwers help you with your decision:



1.       We use Elasticsearch. Until now it works very well and reliable. Also ES is very fast if it comes to metrics and analysis.

2.       We made around 3 million requests against the gateway, after that we had have around 600 MB of data in our Elasticseach (with metrics enabled of course.)



Regards

Florian



Von: apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org> <apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org>> Im Auftrag von Pritam.Lahoti at cognizant.com<mailto:Pritam.Lahoti at cognizant.com>
Gesendet: Wednesday, 14 November 2018 12:47
An: apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Betreff: [Apiman-user] APIMAN database query



Hi Team,



We are currently evaluating APIMAN as API lifecycle management solution and have some specific queries around -



  1.  Best Suitable database?
  2.  Re-commanded Sizing of database as per application size?



Thanks and Regards,

Pritam Lahoti
_______________________________________________
Apiman-user mailing list
Apiman-user at lists.jboss.org<mailto:Apiman-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181128/49765f42/attachment-0001.html 

From marc.savy at redhat.com  Wed Nov 28 06:18:58 2018
From: marc.savy at redhat.com (Marc Savy)
Date: Wed, 28 Nov 2018 11:18:58 +0000
Subject: [Apiman-user] APIMAN database query
In-Reply-To: <058e68bc19424f91b14b1f532699f40b@sgrpexc002.scheer.systems>
References: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<33aa625a6e824d308c9a580c44328d6f@sgrpexc001.scheer.systems>
	<SL2PR02MB36601E647360B5CB7C8C22F9F2D00@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<CAA7j38J_YZWSaTV4bf=BK0+4OVPeHkY9ubzROVqfN2Zj44r3Pw@mail.gmail.com>
	<058e68bc19424f91b14b1f532699f40b@sgrpexc002.scheer.systems>
Message-ID: <CAA7j38K1eWpTq2oWFYCsh=O37ULRwytm-uW=vgehGdKbZnBePw@mail.gmail.com>

Hi Florian,

Thanks for sharing! I know there are plenty of points of optimisation we
could do to improve these numbers.

One quick thought: have you tried using the Shenandoah garbage collector?
That is great for reducing GC pauses, which is often responsible for
problematic latency. This is especially true as you increase the heap size
(which will be necessary if you're trying to cope with large numbers of
parallel requests)

We also very much endorse Gatling [1] as a performance framework, as it
allows you to more accurately simulate your real-world application's
behaviour, whilst not suffering from some of the statistical/methodological
issues of traditional benchmarking software.

Thanks again for sharing, Florian -- great stuff.

Regards,
Marc

[1] https://gatling.io/ --  it's a free and open source tool.




On Wed, 28 Nov 2018 at 08:37, Volk, Florian <Florian.Volk at scheer-group.com>
wrote:

> Hello, apiman comunity
>
> I will try to anwser your questions:
>
>    1. Can we deploy APIMAN on pivotal cloud foundry?
>
> We don?t use this.
>
>    1. How to scale the APIMAN?
>
> We put the vertx gateway in a docker container so we can easily scale thne
> number of gateways if we need more than one.
>
>    1. Hows is the performance of it?
>
> Our product is based on apiman. But we dockerized the whole apiman stack.
> Recently we made some load tests with some policies. Your can see the
> results in our forum blog post.
>
> https://forum.e2ebridge.com/forums/topic/api-management-loadtests-results/
>
> I hope our information will help you.
>
>
>
> Best regards
>
> Florian
>
>
>
> *Von:* Marc Savy <marc.savy at redhat.com>
> *Gesendet:* Wednesday, 28 November 2018 01:38
> *An:* Pritam.Lahoti at cognizant.com
> *Cc:* Volk, Florian <Florian.Volk at scheer-group.com>;
> apiman-user at lists.jboss.org
> *Betreff:* Re: [Apiman-user] APIMAN database query
>
>
>
> On Wed, 28 Nov 2018 at 00:34, <Pritam.Lahoti at cognizant.com> wrote:
>
> Thanks for the replies Team.
>
>
>
> I have some of the queries as-
>
>    - Can we deploy APIMAN on pivotal cloud foundry?
>
>
>
> I've never used Pivotal Cloud Foundry, I'm afraid. Perhaps another
> community member can answer.
>
>
>
>
>    - How to scale the APIMAN?
>
>
>
> You can add as many gateways as you need with the same configuration,
> which allows you to scale horizontally
>
>
>
>
>
>
>    - Hows is the performance of it?
>
> You'll have to test for your own use-cases and it's highly dependent upon
> configuration and which components you use. But, it should be more than
> enough for most use-cases.
>
>
>
> The real question here is: what are your requirements?
>
>
>    - Any licencing or cost information ?
>
>
>
> Apiman is a free and open source project.
>
>
>
>
>
> Thanks and Regdards,
>
> Pritam Lahoti
> ------------------------------
>
> *From:* Volk, Florian <Florian.Volk at scheer-group.com>
> *Sent:* Thursday, November 22, 2018 8:24:31 AM
> *To:* Lahoti, Pritam (Cognizant); apiman-user at lists.jboss.org
> *Subject:* AW: APIMAN database query
>
>
>
> Hi Pritam,
>
>
>
> maybe our anwers help you with your decision:
>
>
>
> 1.       We use Elasticsearch. Until now it works very well and reliable.
> Also ES is very fast if it comes to metrics and analysis.
>
> 2.       We made around 3 million requests against the gateway, after
> that we had have around 600 MB of data in our Elasticseach (with metrics
> enabled of course.)
>
>
>
> Regards
>
> Florian
>
>
>
> *Von:* apiman-user-bounces at lists.jboss.org <
> apiman-user-bounces at lists.jboss.org> *Im Auftrag von *
> Pritam.Lahoti at cognizant.com
> *Gesendet:* Wednesday, 14 November 2018 12:47
> *An:* apiman-user at lists.jboss.org
> *Betreff:* [Apiman-user] APIMAN database query
>
>
>
> Hi Team,
>
>
>
> We are currently evaluating APIMAN as API lifecycle management solution
> and have some specific queries around -
>
>
>
>    1. Best Suitable database?
>    2. Re-commanded Sizing of database as per application size?
>
>
>
> Thanks and Regards,
>
> Pritam Lahoti
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181128/21c480dd/attachment.html 

From Florian.Volk at scheer-group.com  Wed Nov 28 07:39:09 2018
From: Florian.Volk at scheer-group.com (Volk, Florian)
Date: Wed, 28 Nov 2018 12:39:09 +0000
Subject: [Apiman-user] APIMAN database query
In-Reply-To: <CAA7j38K1eWpTq2oWFYCsh=O37ULRwytm-uW=vgehGdKbZnBePw@mail.gmail.com>
References: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<33aa625a6e824d308c9a580c44328d6f@sgrpexc001.scheer.systems>
	<SL2PR02MB36601E647360B5CB7C8C22F9F2D00@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<CAA7j38J_YZWSaTV4bf=BK0+4OVPeHkY9ubzROVqfN2Zj44r3Pw@mail.gmail.com>
	<058e68bc19424f91b14b1f532699f40b@sgrpexc002.scheer.systems>
	<CAA7j38K1eWpTq2oWFYCsh=O37ULRwytm-uW=vgehGdKbZnBePw@mail.gmail.com>
Message-ID: <fa142cd8e3ab43d492456f6cdf74e87e@sgrpexc002.scheer.systems>

Hi Marc,

Thank you for the hints with the two tools.
We will look into this if we have more time.

Regards,
Florian

Von: Marc Savy <marc.savy at redhat.com>
Gesendet: Wednesday, 28 November 2018 12:19
An: Volk, Florian <Florian.Volk at scheer-group.com>
Cc: Pritam.Lahoti at cognizant.com; apiman-user at lists.jboss.org
Betreff: Re: [Apiman-user] APIMAN database query

Hi Florian,

Thanks for sharing! I know there are plenty of points of optimisation we could do to improve these numbers.

One quick thought: have you tried using the Shenandoah garbage collector? That is great for reducing GC pauses, which is often responsible for problematic latency. This is especially true as you increase the heap size (which will be necessary if you're trying to cope with large numbers of parallel requests)

We also very much endorse Gatling [1] as a performance framework, as it allows you to more accurately simulate your real-world application's behaviour, whilst not suffering from some of the statistical/methodological issues of traditional benchmarking software.

Thanks again for sharing, Florian -- great stuff.

Regards,
Marc

[1] https://gatling.io/ --  it's a free and open source tool.




On Wed, 28 Nov 2018 at 08:37, Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>> wrote:

Hello, apiman comunity

I will try to anwser your questions:

  1.  Can we deploy APIMAN on pivotal cloud foundry?
We don?t use this.

  1.  How to scale the APIMAN?
We put the vertx gateway in a docker container so we can easily scale thne number of gateways if we need more than one.

  1.  Hows is the performance of it?
Our product is based on apiman. But we dockerized the whole apiman stack.
Recently we made some load tests with some policies. Your can see the results in our forum blog post.
https://forum.e2ebridge.com/forums/topic/api-management-loadtests-results/
I hope our information will help you.

Best regards
Florian

Von: Marc Savy <marc.savy at redhat.com<mailto:marc.savy at redhat.com>>
Gesendet: Wednesday, 28 November 2018 01:38
An: Pritam.Lahoti at cognizant.com<mailto:Pritam.Lahoti at cognizant.com>
Cc: Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>>; apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Betreff: Re: [Apiman-user] APIMAN database query

On Wed, 28 Nov 2018 at 00:34, <Pritam.Lahoti at cognizant.com<mailto:Pritam.Lahoti at cognizant.com>> wrote:

Thanks for the replies Team.



I have some of the queries as-

  *   Can we deploy APIMAN on pivotal cloud foundry?

I've never used Pivotal Cloud Foundry, I'm afraid. Perhaps another community member can answer.


  *   How to scale the APIMAN?

You can add as many gateways as you need with the same configuration, which allows you to scale horizontally



  *   Hows is the performance of it?
You'll have to test for your own use-cases and it's highly dependent upon configuration and which components you use. But, it should be more than enough for most use-cases.

The real question here is: what are your requirements?

  *   Any licencing or cost information ?

Apiman is a free and open source project.



Thanks and Regdards,

Pritam Lahoti

________________________________
From: Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>>
Sent: Thursday, November 22, 2018 8:24:31 AM
To: Lahoti, Pritam (Cognizant); apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Subject: AW: APIMAN database query


Hi Pritam,



maybe our anwers help you with your decision:



1.       We use Elasticsearch. Until now it works very well and reliable. Also ES is very fast if it comes to metrics and analysis.

2.       We made around 3 million requests against the gateway, after that we had have around 600 MB of data in our Elasticseach (with metrics enabled of course.)



Regards

Florian



Von: apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org> <apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org>> Im Auftrag von Pritam.Lahoti at cognizant.com<mailto:Pritam.Lahoti at cognizant.com>
Gesendet: Wednesday, 14 November 2018 12:47
An: apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Betreff: [Apiman-user] APIMAN database query



Hi Team,



We are currently evaluating APIMAN as API lifecycle management solution and have some specific queries around -



  1.  Best Suitable database?
  2.  Re-commanded Sizing of database as per application size?



Thanks and Regards,

Pritam Lahoti
_______________________________________________
Apiman-user mailing list
Apiman-user at lists.jboss.org<mailto:Apiman-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181128/6799d55a/attachment-0001.html 

From Pritam.Lahoti at cognizant.com  Wed Nov 28 11:44:47 2018
From: Pritam.Lahoti at cognizant.com (Pritam.Lahoti at cognizant.com)
Date: Wed, 28 Nov 2018 16:44:47 +0000
Subject: [Apiman-user] APIMAN database query
In-Reply-To: <CAA7j38K1eWpTq2oWFYCsh=O37ULRwytm-uW=vgehGdKbZnBePw@mail.gmail.com>
References: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<33aa625a6e824d308c9a580c44328d6f@sgrpexc001.scheer.systems>
	<SL2PR02MB36601E647360B5CB7C8C22F9F2D00@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<CAA7j38J_YZWSaTV4bf=BK0+4OVPeHkY9ubzROVqfN2Zj44r3Pw@mail.gmail.com>
	<058e68bc19424f91b14b1f532699f40b@sgrpexc002.scheer.systems>,
	<CAA7j38K1eWpTq2oWFYCsh=O37ULRwytm-uW=vgehGdKbZnBePw@mail.gmail.com>
Message-ID: <SL2PR02MB3660329EA1A0F2CE877AD511F2D10@SL2PR02MB3660.apcprd02.prod.outlook.com>

Thanks for the sharing team.


One more question as-

Does APIMAN has developer portal?


Thanks and Regards,

Pritam Lahoti

________________________________
From: Marc Savy <marc.savy at redhat.com>
Sent: Wednesday, November 28, 2018 11:18:58 AM
To: Florian.Volk at scheer-group.com
Cc: Lahoti, Pritam (Cognizant); apiman-user at lists.jboss.org
Subject: Re: [Apiman-user] APIMAN database query

Hi Florian,

Thanks for sharing! I know there are plenty of points of optimisation we could do to improve these numbers.

One quick thought: have you tried using the Shenandoah garbage collector? That is great for reducing GC pauses, which is often responsible for problematic latency. This is especially true as you increase the heap size (which will be necessary if you're trying to cope with large numbers of parallel requests)

We also very much endorse Gatling [1] as a performance framework, as it allows you to more accurately simulate your real-world application's behaviour, whilst not suffering from some of the statistical/methodological issues of traditional benchmarking software.

Thanks again for sharing, Florian -- great stuff.

Regards,
Marc

[1] https://gatling.io/ --  it's a free and open source tool.




On Wed, 28 Nov 2018 at 08:37, Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>> wrote:

Hello, apiman comunity

I will try to anwser your questions:

  1.  Can we deploy APIMAN on pivotal cloud foundry?

We don?t use this.

  1.  How to scale the APIMAN?

We put the vertx gateway in a docker container so we can easily scale thne number of gateways if we need more than one.

  1.  Hows is the performance of it?

Our product is based on apiman. But we dockerized the whole apiman stack.
Recently we made some load tests with some policies. Your can see the results in our forum blog post.

https://forum.e2ebridge.com/forums/topic/api-management-loadtests-results/


I hope our information will help you.



Best regards

Florian



Von: Marc Savy <marc.savy at redhat.com<mailto:marc.savy at redhat.com>>
Gesendet: Wednesday, 28 November 2018 01:38
An: Pritam.Lahoti at cognizant.com<mailto:Pritam.Lahoti at cognizant.com>
Cc: Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>>; apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Betreff: Re: [Apiman-user] APIMAN database query



On Wed, 28 Nov 2018 at 00:34, <Pritam.Lahoti at cognizant.com<mailto:Pritam.Lahoti at cognizant.com>> wrote:

Thanks for the replies Team.



I have some of the queries as-

  *   Can we deploy APIMAN on pivotal cloud foundry?



I've never used Pivotal Cloud Foundry, I'm afraid. Perhaps another community member can answer.



  *   How to scale the APIMAN?



You can add as many gateways as you need with the same configuration, which allows you to scale horizontally





  *   Hows is the performance of it?

You'll have to test for your own use-cases and it's highly dependent upon configuration and which components you use. But, it should be more than enough for most use-cases.



The real question here is: what are your requirements?

  *   Any licencing or cost information ?



Apiman is a free and open source project.





Thanks and Regdards,

Pritam Lahoti

________________________________

From: Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>>
Sent: Thursday, November 22, 2018 8:24:31 AM
To: Lahoti, Pritam (Cognizant); apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Subject: AW: APIMAN database query



Hi Pritam,



maybe our anwers help you with your decision:



1.       We use Elasticsearch. Until now it works very well and reliable. Also ES is very fast if it comes to metrics and analysis.

2.       We made around 3 million requests against the gateway, after that we had have around 600 MB of data in our Elasticseach (with metrics enabled of course.)



Regards

Florian



Von: apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org> <apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org>> Im Auftrag von Pritam.Lahoti at cognizant.com<mailto:Pritam.Lahoti at cognizant.com>
Gesendet: Wednesday, 14 November 2018 12:47
An: apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Betreff: [Apiman-user] APIMAN database query



Hi Team,



We are currently evaluating APIMAN as API lifecycle management solution and have some specific queries around -



  1.  Best Suitable database?
  2.  Re-commanded Sizing of database as per application size?



Thanks and Regards,

Pritam Lahoti

_______________________________________________
Apiman-user mailing list
Apiman-user at lists.jboss.org<mailto:Apiman-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181128/7e638acd/attachment-0001.html 

From msavy at redhat.com  Thu Nov 29 06:11:58 2018
From: msavy at redhat.com (Marc Savy)
Date: Thu, 29 Nov 2018 11:11:58 +0000
Subject: [Apiman-user] APIMAN database query
In-Reply-To: <SL2PR02MB3660329EA1A0F2CE877AD511F2D10@SL2PR02MB3660.apcprd02.prod.outlook.com>
References: <SL2PR02MB366060E7ED623AC1A306C00CF2C30@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<33aa625a6e824d308c9a580c44328d6f@sgrpexc001.scheer.systems>
	<SL2PR02MB36601E647360B5CB7C8C22F9F2D00@SL2PR02MB3660.apcprd02.prod.outlook.com>
	<CAA7j38J_YZWSaTV4bf=BK0+4OVPeHkY9ubzROVqfN2Zj44r3Pw@mail.gmail.com>
	<058e68bc19424f91b14b1f532699f40b@sgrpexc002.scheer.systems>
	<CAA7j38K1eWpTq2oWFYCsh=O37ULRwytm-uW=vgehGdKbZnBePw@mail.gmail.com>
	<SL2PR02MB3660329EA1A0F2CE877AD511F2D10@SL2PR02MB3660.apcprd02.prod.outlook.com>
Message-ID: <e3a3bd9b-6f18-20f6-cdf5-050fd75cf851@redhat.com>

 > Does APIMAN has developer portal?


There is no separate developer portal at this time, no.

On 28/11/2018 16:44, Pritam.Lahoti at cognizant.com wrote:
>
> Thanks for the sharing team.
>
>
> One more question as-
>
> Does APIMAN has developer portal?
>
>
> Thanks and Regards,
>
> Pritam Lahoti
>
> ------------------------------------------------------------------------
> *From:* Marc Savy <marc.savy at redhat.com>
> *Sent:* Wednesday, November 28, 2018 11:18:58 AM
> *To:* Florian.Volk at scheer-group.com
> *Cc:* Lahoti, Pritam (Cognizant); apiman-user at lists.jboss.org
> *Subject:* Re: [Apiman-user] APIMAN database query
> Hi Florian,
>
> Thanks for sharing! I know there are plenty of points of optimisation 
> we could do to improve these numbers.
>
> One quick thought: have you tried using the Shenandoah garbage 
> collector? That is great for reducing GC pauses, which is often 
> responsible for problematic latency. This is especially true as you 
> increase the heap size (which will be necessary if you're trying to 
> cope with large numbers of parallel requests)
>
> We also very much endorse Gatling [1] as a performance framework, as 
> it allows you to more accurately simulate your real-world 
> application's behaviour, whilst not suffering from some of the 
> statistical/methodological issues of traditional benchmarking software.
>
> Thanks again for sharing, Florian -- great stuff.
>
> Regards,
> Marc
>
> [1] https://gatling.io/ --? it's a free and open source tool.
>
>
>
>
> On Wed, 28 Nov 2018 at 08:37, Volk, Florian 
> <Florian.Volk at scheer-group.com <mailto:Florian.Volk at scheer-group.com>> 
> wrote:
>
>     Hello, apiman comunity
>
>     I will try to anwser your questions:
>
>      1. Can we deploy APIMAN on pivotal cloud foundry?
>
>     We don?t use this.
>
>      2. How to scale the APIMAN?
>
>     We put the vertx gateway in a docker container so we can easily
>     scale thne number of gateways if we need more than one.
>
>      3. Hows is the performance of it?
>
>     Our product is based on apiman. But we dockerized the whole apiman
>     stack.
>     Recently we made some load tests with some policies. Your can see
>     the results in our forum blog post.
>
>     https://forum.e2ebridge.com/forums/topic/api-management-loadtests-results/
>
>     I hope our informationwill helpyou.
>
>     Best regards
>
>     Florian
>
>     *Von:*Marc Savy <marc.savy at redhat.com <mailto:marc.savy at redhat.com>>
>     *Gesendet:* Wednesday, 28 November 2018 01:38
>     *An:* Pritam.Lahoti at cognizant.com <mailto:Pritam.Lahoti at cognizant.com>
>     *Cc:* Volk, Florian <Florian.Volk at scheer-group.com
>     <mailto:Florian.Volk at scheer-group.com>>;
>     apiman-user at lists.jboss.org <mailto:apiman-user at lists.jboss.org>
>     *Betreff:* Re: [Apiman-user] APIMAN database query
>
>     On Wed, 28 Nov 2018 at 00:34, <Pritam.Lahoti at cognizant.com
>     <mailto:Pritam.Lahoti at cognizant.com>> wrote:
>
>         Thanks for the replies Team.
>
>         I have some of the queries as-
>
>           * Can we deploy APIMAN on pivotal cloud foundry?
>
>     I've never used Pivotal Cloud Foundry, I'm afraid. Perhaps another
>     community member can answer.
>
>           * How to scale the APIMAN?
>
>     You can add as many gateways as you need with the same
>     configuration, which allows you to scale horizontally
>
>           * Hows is the performance of it?
>
>     You'll have to test for your own use-cases and it's highly
>     dependent upon configuration and which components you use. But, it
>     should be more than enough for most use-cases.
>
>     The real question here is: what are your requirements?
>
>           * Any licencing or cost information ?
>
>     Apiman is a free and open source project.
>
>         Thanks and Regdards,
>
>         Pritam Lahoti
>
>         ------------------------------------------------------------------------
>
>         *From:*Volk, Florian <Florian.Volk at scheer-group.com
>         <mailto:Florian.Volk at scheer-group.com>>
>         *Sent:* Thursday, November 22, 2018 8:24:31 AM
>         *To:* Lahoti, Pritam (Cognizant); apiman-user at lists.jboss.org
>         <mailto:apiman-user at lists.jboss.org>
>         *Subject:* AW: APIMAN database query
>
>         Hi Pritam,
>
>         maybe our anwers help you with your decision:
>
>         1.We use Elasticsearch. Until now it works very well and
>         reliable. Also ES is very fast if it comes to metrics and
>         analysis.
>
>         2.We made around 3 million requests against the gateway, after
>         that we had have around 600 MB of data in our Elasticseach
>         (with metrics enabled of course.)
>
>         Regards
>
>         Florian
>
>         *Von:*apiman-user-bounces at lists.jboss.org
>         <mailto:apiman-user-bounces at lists.jboss.org>
>         <apiman-user-bounces at lists.jboss.org
>         <mailto:apiman-user-bounces at lists.jboss.org>> *Im Auftrag von
>         *Pritam.Lahoti at cognizant.com <mailto:Pritam.Lahoti at cognizant.com>
>         *Gesendet:* Wednesday, 14 November 2018 12:47
>         *An:* apiman-user at lists.jboss.org
>         <mailto:apiman-user at lists.jboss.org>
>         *Betreff:* [Apiman-user] APIMAN database query
>
>         Hi Team,
>
>         We are currently evaluating APIMAN as API lifecycle management
>         solution and have some specific queries around -
>
>          1. Best Suitable database?
>          2. Re-commanded?Sizing of database as per application size?
>
>         Thanks and Regards,
>
>         Pritam Lahoti
>
>         _______________________________________________
>         Apiman-user mailing list
>         Apiman-user at lists.jboss.org <mailto:Apiman-user at lists.jboss.org>
>         https://lists.jboss.org/mailman/listinfo/apiman-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181129/2433e4fa/attachment-0001.html 

From chttl582 at gmail.com  Thu Nov 29 21:27:51 2018
From: chttl582 at gmail.com (Jon Huang)
Date: Fri, 30 Nov 2018 10:27:51 +0800
Subject: [Apiman-user] publish api to specific gateway
In-Reply-To: <CAA7j38LDcGodo5FEsDjGtkRxX5B-4Wa1bw1QzS4O__eEOj2MFw@mail.gmail.com>
References: <CAP45m-bndU3jqRwzgHQAY3PDNyYS3mUQGY4-cnenGvHZCX=FfQ@mail.gmail.com>
	<CAA7j38LDcGodo5FEsDjGtkRxX5B-4Wa1bw1QzS4O__eEOj2MFw@mail.gmail.com>
Message-ID: <CAP45m-Y=zXnk1gRj=00aC5f8TwC+gTPD7Lw8v_1yjJnJwcO2MA@mail.gmail.com>

Dear Marc

Yes I untick another gateway however request towards both gateways still
works.
Besides I tried to publish API via admin REST API (post api version then
put gateway info), both gateways forwards request too.
Before filing a bug is there any apigw setting I shall check? (such as
parameter in apiman.properties or etc...)
Thanks for your help.
Regards

Marc Savy <marc.savy at redhat.com> ? 2018?11?21? ?? ??9:35???

> Apologies for the terribly slow reply. We've had so much spam I've missed
> legitimate emails like this.
>
> Did you explicitly untick the other gateway? Was this via the UI or the
> API?
>
> Did you resolve this issue? If not, please file a bug:
> https://github.com/apiman/apiman/issues
>
> On Thu, 4 Oct 2018 at 05:00, Jon Huang <chttl582 at gmail.com> wrote:
>
>> Dears
>>
>> I had set up 2 gateways.
>> When I new an API, I have to choose which gateway to publish. (select
>> list at Gateway section in the implementation tab).
>> However after creating a client app and contract for test, I found
>> request via another gateway still works.
>> (I guest when publishing to gateway 1 and request via gateway 2 shall
>> fail)
>> Am I misunderstanding or I miss some settings to make it work?
>> Thanks
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181130/3d5a6092/attachment.html 

From Florian.Volk at scheer-group.com  Fri Nov 30 04:36:01 2018
From: Florian.Volk at scheer-group.com (Volk, Florian)
Date: Fri, 30 Nov 2018 09:36:01 +0000
Subject: [Apiman-user] [DKIM] Re:  publish api to specific gateway
In-Reply-To: <CAP45m-Y=zXnk1gRj=00aC5f8TwC+gTPD7Lw8v_1yjJnJwcO2MA@mail.gmail.com>
References: <CAP45m-bndU3jqRwzgHQAY3PDNyYS3mUQGY4-cnenGvHZCX=FfQ@mail.gmail.com>
	<CAA7j38LDcGodo5FEsDjGtkRxX5B-4Wa1bw1QzS4O__eEOj2MFw@mail.gmail.com>
	<CAP45m-Y=zXnk1gRj=00aC5f8TwC+gTPD7Lw8v_1yjJnJwcO2MA@mail.gmail.com>
Message-ID: <5f5fcb84c65548c99fe5a81b5f97aa3b@sgrpexc001.scheer.systems>

Hello together,

I was interested in this and made a short test in my loacal environment and I am able to reproduce this.
I created a ticket on github for this (https://github.com/apiman/apiman/issues/711). We may can fix this shortly.

Regards,
Florian

Von: apiman-user-bounces at lists.jboss.org <apiman-user-bounces at lists.jboss.org> Im Auftrag von Jon Huang
Gesendet: Friday, 30 November 2018 03:28
An: marc.savy at redhat.com
Cc: apiman-user at lists.jboss.org
Betreff: [DKIM] Re: [Apiman-user] publish api to specific gateway

Dear Marc

Yes I untick another gateway however request towards both gateways still works.
Besides I tried to publish API via admin REST API (post api version then put gateway info), both gateways forwards request too.
Before filing a bug is there any apigw setting I shall check? (such as parameter in apiman.properties or etc...)
Thanks for your help.
Regards
Marc Savy <marc.savy at redhat.com<mailto:marc.savy at redhat.com>> ? 2018?11?21? ?? ??9:35???
Apologies for the terribly slow reply. We've had so much spam I've missed legitimate emails like this.

Did you explicitly untick the other gateway? Was this via the UI or the API?

Did you resolve this issue? If not, please file a bug: https://github.com/apiman/apiman/issues

On Thu, 4 Oct 2018 at 05:00, Jon Huang <chttl582 at gmail.com<mailto:chttl582 at gmail.com>> wrote:
Dears

I had set up 2 gateways.
When I new an API, I have to choose which gateway to publish. (select list at Gateway section in the implementation tab).
However after creating a client app and contract for test, I found request via another gateway still works.
(I guest when publishing to gateway 1 and request via gateway 2 shall fail)
Am I misunderstanding or I miss some settings to make it work?
Thanks
_______________________________________________
Apiman-user mailing list
Apiman-user at lists.jboss.org<mailto:Apiman-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181130/73b4cf04/attachment.html 

From eric.wittmann at redhat.com  Fri Nov 30 08:22:27 2018
From: eric.wittmann at redhat.com (Eric Wittmann)
Date: Fri, 30 Nov 2018 08:22:27 -0500
Subject: [Apiman-user] [DKIM] Re: publish api to specific gateway
In-Reply-To: <5f5fcb84c65548c99fe5a81b5f97aa3b@sgrpexc001.scheer.systems>
References: <CAP45m-bndU3jqRwzgHQAY3PDNyYS3mUQGY4-cnenGvHZCX=FfQ@mail.gmail.com>
	<CAA7j38LDcGodo5FEsDjGtkRxX5B-4Wa1bw1QzS4O__eEOj2MFw@mail.gmail.com>
	<CAP45m-Y=zXnk1gRj=00aC5f8TwC+gTPD7Lw8v_1yjJnJwcO2MA@mail.gmail.com>
	<5f5fcb84c65548c99fe5a81b5f97aa3b@sgrpexc001.scheer.systems>
Message-ID: <CAP4n9Q9-Na4VbXpiGGRQ-zgNPVvYRpt7OC=FxQ5PoOe1+L621Q@mail.gmail.com>

Are both gateways using the same persistent storage?  Each gateway would
need separate, independent persistence otherwise they will behave as a
single "logical" gateway.

-Eric


On Fri, Nov 30, 2018 at 4:39 AM Volk, Florian <Florian.Volk at scheer-group.com>
wrote:

> Hello together,
>
>
>
> I was interested in this and made a short test in my loacal environment
> and I am able to reproduce this.
>
> I created a ticket on github for this (
> https://github.com/apiman/apiman/issues/711). We may can fix this shortly.
>
>
>
> Regards,
>
> Florian
>
>
>
> *Von:* apiman-user-bounces at lists.jboss.org <
> apiman-user-bounces at lists.jboss.org> *Im Auftrag von *Jon Huang
> *Gesendet:* Friday, 30 November 2018 03:28
> *An:* marc.savy at redhat.com
> *Cc:* apiman-user at lists.jboss.org
> *Betreff:* [DKIM] Re: [Apiman-user] publish api to specific gateway
>
>
>
> Dear Marc
>
>
>
> Yes I untick another gateway however request towards both gateways still
> works.
>
> Besides I tried to publish API via admin REST API (post api version then
> put gateway info), both gateways forwards request too.
>
> Before filing a bug is there any apigw setting I shall check? (such as
> parameter in apiman.properties or etc...)
>
> Thanks for your help.
>
> Regards
>
> Marc Savy <marc.savy at redhat.com> ? 2018?11?21? ?? ??9:35???
>
> Apologies for the terribly slow reply. We've had so much spam I've missed
> legitimate emails like this.
>
>
>
> Did you explicitly untick the other gateway? Was this via the UI or the
> API?
>
>
>
> Did you resolve this issue? If not, please file a bug:
> https://github.com/apiman/apiman/issues
>
>
>
> On Thu, 4 Oct 2018 at 05:00, Jon Huang <chttl582 at gmail.com> wrote:
>
> Dears
>
>
>
> I had set up 2 gateways.
>
> When I new an API, I have to choose which gateway to publish. (select list
> at Gateway section in the implementation tab).
>
> However after creating a client app and contract for test, I found request
> via another gateway still works.
>
> (I guest when publishing to gateway 1 and request via gateway 2 shall fail)
>
> Am I misunderstanding or I miss some settings to make it work?
>
> Thanks
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181130/e4264cfd/attachment-0001.html 

From Florian.Volk at scheer-group.com  Fri Nov 30 08:37:51 2018
From: Florian.Volk at scheer-group.com (Volk, Florian)
Date: Fri, 30 Nov 2018 13:37:51 +0000
Subject: [Apiman-user] [DKIM] Re: publish api to specific gateway
In-Reply-To: <CAP4n9Q9-Na4VbXpiGGRQ-zgNPVvYRpt7OC=FxQ5PoOe1+L621Q@mail.gmail.com>
References: <CAP45m-bndU3jqRwzgHQAY3PDNyYS3mUQGY4-cnenGvHZCX=FfQ@mail.gmail.com>
	<CAA7j38LDcGodo5FEsDjGtkRxX5B-4Wa1bw1QzS4O__eEOj2MFw@mail.gmail.com>
	<CAP45m-Y=zXnk1gRj=00aC5f8TwC+gTPD7Lw8v_1yjJnJwcO2MA@mail.gmail.com>
	<5f5fcb84c65548c99fe5a81b5f97aa3b@sgrpexc001.scheer.systems>
	<CAP4n9Q9-Na4VbXpiGGRQ-zgNPVvYRpt7OC=FxQ5PoOe1+L621Q@mail.gmail.com>
Message-ID: <fad9e76a5284416ab9a57a34af272777@sgrpexc001.scheer.systems>

Hi Eric,

now I?m confused. We use Elasticsearch as backend. If I understand you correctly it would mean that we have to setup an Elasticsearch instance for each gateway?
On the other point, if the gateways operate as logical unit, why is there a configuration option in the ui?

Can you explain this a little bit more detailed? Maybe you have a configuration example.

Regards,
Florian

Von: Eric Wittmann <eric.wittmann at redhat.com>
Gesendet: Friday, 30 November 2018 14:22
An: Volk, Florian <Florian.Volk at scheer-group.com>
Cc: chttl582 at gmail.com; Marc Savy <marc.savy at redhat.com>; Kihm, Benjamin <Benjamin.Kihm at scheer-group.com>; Gebert, Alfred <Alfred.Gebert at scheer-group.com>; apiman-user at lists.jboss.org
Betreff: Re: [Apiman-user] [DKIM] Re: publish api to specific gateway

Are both gateways using the same persistent storage?  Each gateway would need separate, independent persistence otherwise they will behave as a single "logical" gateway.

-Eric


On Fri, Nov 30, 2018 at 4:39 AM Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>> wrote:
Hello together,

I was interested in this and made a short test in my loacal environment and I am able to reproduce this.
I created a ticket on github for this (https://github.com/apiman/apiman/issues/711). We may can fix this shortly.

Regards,
Florian

Von: apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org> <apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org>> Im Auftrag von Jon Huang
Gesendet: Friday, 30 November 2018 03:28
An: marc.savy at redhat.com<mailto:marc.savy at redhat.com>
Cc: apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Betreff: [DKIM] Re: [Apiman-user] publish api to specific gateway

Dear Marc

Yes I untick another gateway however request towards both gateways still works.
Besides I tried to publish API via admin REST API (post api version then put gateway info), both gateways forwards request too.
Before filing a bug is there any apigw setting I shall check? (such as parameter in apiman.properties or etc...)
Thanks for your help.
Regards
Marc Savy <marc.savy at redhat.com<mailto:marc.savy at redhat.com>> ? 2018?11?21? ?? ??9:35???
Apologies for the terribly slow reply. We've had so much spam I've missed legitimate emails like this.

Did you explicitly untick the other gateway? Was this via the UI or the API?

Did you resolve this issue? If not, please file a bug: https://github.com/apiman/apiman/issues

On Thu, 4 Oct 2018 at 05:00, Jon Huang <chttl582 at gmail.com<mailto:chttl582 at gmail.com>> wrote:
Dears

I had set up 2 gateways.
When I new an API, I have to choose which gateway to publish. (select list at Gateway section in the implementation tab).
However after creating a client app and contract for test, I found request via another gateway still works.
(I guest when publishing to gateway 1 and request via gateway 2 shall fail)
Am I misunderstanding or I miss some settings to make it work?
Thanks
_______________________________________________
Apiman-user mailing list
Apiman-user at lists.jboss.org<mailto:Apiman-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
_______________________________________________
Apiman-user mailing list
Apiman-user at lists.jboss.org<mailto:Apiman-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181130/e1c79ffe/attachment.html 

From eric.wittmann at redhat.com  Fri Nov 30 08:57:20 2018
From: eric.wittmann at redhat.com (Eric Wittmann)
Date: Fri, 30 Nov 2018 08:57:20 -0500
Subject: [Apiman-user] [DKIM] Re: publish api to specific gateway
In-Reply-To: <fad9e76a5284416ab9a57a34af272777@sgrpexc001.scheer.systems>
References: <CAP45m-bndU3jqRwzgHQAY3PDNyYS3mUQGY4-cnenGvHZCX=FfQ@mail.gmail.com>
	<CAA7j38LDcGodo5FEsDjGtkRxX5B-4Wa1bw1QzS4O__eEOj2MFw@mail.gmail.com>
	<CAP45m-Y=zXnk1gRj=00aC5f8TwC+gTPD7Lw8v_1yjJnJwcO2MA@mail.gmail.com>
	<5f5fcb84c65548c99fe5a81b5f97aa3b@sgrpexc001.scheer.systems>
	<CAP4n9Q9-Na4VbXpiGGRQ-zgNPVvYRpt7OC=FxQ5PoOe1+L621Q@mail.gmail.com>
	<fad9e76a5284416ab9a57a34af272777@sgrpexc001.scheer.systems>
Message-ID: <CAP4n9Q9aYaQ2Lm0OC6D6rde1LseBnsgDRE03fdZ81pOzamXy=w@mail.gmail.com>

Sure no problem.  The typical use-case for having multiple Gateway nodes is
to scale the gateway layer horizontally and then put a load balancer in
front of them.  So for example you might start up 5 apiman gateway
instances and configure them all to use the same Elasticsearch instance for
persistence (i.e. where to store configuration info like which APIs have
been published).  In this use-case, every gateway instance has the same set
of APIs "published" to it.  You can publish an API from the UI/manager to
**any** of the gateway instances and they will all know about that API.
This is the "Single Logical Gateway" use-case -- the UI/manager and all
consumers don't know or care how many gateway nodes there are - there could
be 1 node, or there could be 100.  It behaves the same logically.

An **alternate** use case for having multiple gateways is when you actually
want different APIs to be deployed to different gateways.  So let's say you
wanted Gateway Alpha to be able to proxy traffic to APIs A, B, and C.  Then
you have Gateway Beta which you want to proxy traffic to APIs C, D, and E.
In that case, consumer traffic MUST be routed through Gateway Alpha in
order to access APIs A and B.  Consumer traffic MUST be routed through
Gateway Beta to access APIs D and E.  Finally, consumer traffic can be
routed to **either** Gateway Alpha or Gateway Beta in order to access API
C.  Think of this as the "Two Logical Gateways" use-case.

In order to achieve the "Two Logical Gateways" use-case, you will need
**two** separate persistence stores (Elasticsearch instances).  Then you
configure Gateway Alpha to use persistence store #1 and configure Gateway
Beta to use persistence store #2.

Note that you can have multiple gateway nodes for EACH of the two logical
gateways.  So for example you could have 5 gateway instances all pointing
to persistence store #1 - these 5 nodes would make up a single logical
gateway called "Gateway Alpha".  Then you could have 10 gateway instances
all pointing to persistence store #2 - and these would be a single logical
gateway called "Gateway Beta".

Here is a diagram of what the architecture might look like:

[image: image.png]


On Fri, Nov 30, 2018 at 8:38 AM Volk, Florian <Florian.Volk at scheer-group.com>
wrote:

> Hi Eric,
>
>
>
> now I?m confused. We use Elasticsearch as backend. If I understand you
> correctly it would mean that we have to setup an Elasticsearch instance for
> each gateway?
>
> On the other point, if the gateways operate as logical unit, why is there
> a configuration option in the ui?
>
>
>
> Can you explain this a little bit more detailed? Maybe you have a
> configuration example.
>
>
>
> Regards,
> Florian
>
>
>
> *Von:* Eric Wittmann <eric.wittmann at redhat.com>
> *Gesendet:* Friday, 30 November 2018 14:22
> *An:* Volk, Florian <Florian.Volk at scheer-group.com>
> *Cc:* chttl582 at gmail.com; Marc Savy <marc.savy at redhat.com>; Kihm,
> Benjamin <Benjamin.Kihm at scheer-group.com>; Gebert, Alfred <
> Alfred.Gebert at scheer-group.com>; apiman-user at lists.jboss.org
> *Betreff:* Re: [Apiman-user] [DKIM] Re: publish api to specific gateway
>
>
>
> Are both gateways using the same persistent storage?  Each gateway would
> need separate, independent persistence otherwise they will behave as a
> single "logical" gateway.
>
>
>
> -Eric
>
>
>
>
>
> On Fri, Nov 30, 2018 at 4:39 AM Volk, Florian <
> Florian.Volk at scheer-group.com> wrote:
>
> Hello together,
>
>
>
> I was interested in this and made a short test in my loacal environment
> and I am able to reproduce this.
>
> I created a ticket on github for this (
> https://github.com/apiman/apiman/issues/711). We may can fix this shortly.
>
>
>
> Regards,
>
> Florian
>
>
>
> *Von:* apiman-user-bounces at lists.jboss.org <
> apiman-user-bounces at lists.jboss.org> *Im Auftrag von *Jon Huang
> *Gesendet:* Friday, 30 November 2018 03:28
> *An:* marc.savy at redhat.com
> *Cc:* apiman-user at lists.jboss.org
> *Betreff:* [DKIM] Re: [Apiman-user] publish api to specific gateway
>
>
>
> Dear Marc
>
>
>
> Yes I untick another gateway however request towards both gateways still
> works.
>
> Besides I tried to publish API via admin REST API (post api version then
> put gateway info), both gateways forwards request too.
>
> Before filing a bug is there any apigw setting I shall check? (such as
> parameter in apiman.properties or etc...)
>
> Thanks for your help.
>
> Regards
>
> Marc Savy <marc.savy at redhat.com> ? 2018?11?21? ?? ??9:35???
>
> Apologies for the terribly slow reply. We've had so much spam I've missed
> legitimate emails like this.
>
>
>
> Did you explicitly untick the other gateway? Was this via the UI or the
> API?
>
>
>
> Did you resolve this issue? If not, please file a bug:
> https://github.com/apiman/apiman/issues
>
>
>
> On Thu, 4 Oct 2018 at 05:00, Jon Huang <chttl582 at gmail.com> wrote:
>
> Dears
>
>
>
> I had set up 2 gateways.
>
> When I new an API, I have to choose which gateway to publish. (select list
> at Gateway section in the implementation tab).
>
> However after creating a client app and contract for test, I found request
> via another gateway still works.
>
> (I guest when publishing to gateway 1 and request via gateway 2 shall fail)
>
> Am I misunderstanding or I miss some settings to make it work?
>
> Thanks
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181130/cfaeb6ee/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 92068 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20181130/cfaeb6ee/attachment-0001.png 

From Florian.Volk at scheer-group.com  Fri Nov 30 09:24:33 2018
From: Florian.Volk at scheer-group.com (Volk, Florian)
Date: Fri, 30 Nov 2018 14:24:33 +0000
Subject: [Apiman-user] [DKIM] Re: publish api to specific gateway
In-Reply-To: <CAP4n9Q9aYaQ2Lm0OC6D6rde1LseBnsgDRE03fdZ81pOzamXy=w@mail.gmail.com>
References: <CAP45m-bndU3jqRwzgHQAY3PDNyYS3mUQGY4-cnenGvHZCX=FfQ@mail.gmail.com>
	<CAA7j38LDcGodo5FEsDjGtkRxX5B-4Wa1bw1QzS4O__eEOj2MFw@mail.gmail.com>
	<CAP45m-Y=zXnk1gRj=00aC5f8TwC+gTPD7Lw8v_1yjJnJwcO2MA@mail.gmail.com>
	<5f5fcb84c65548c99fe5a81b5f97aa3b@sgrpexc001.scheer.systems>
	<CAP4n9Q9-Na4VbXpiGGRQ-zgNPVvYRpt7OC=FxQ5PoOe1+L621Q@mail.gmail.com>
	<fad9e76a5284416ab9a57a34af272777@sgrpexc001.scheer.systems>
	<CAP4n9Q9aYaQ2Lm0OC6D6rde1LseBnsgDRE03fdZ81pOzamXy=w@mail.gmail.com>
Message-ID: <517bbd0247ee4e6bac5f40e1dc032fee@sgrpexc001.scheer.systems>

Hi Eric,

thanks for this detailed answer ?
This is quite interesting. We didn?t expected this behavior. Maybe it would be good to place this in the documentation, maybe with this picture ;)

But this raises a few new questions for us. I try to explain:


?         Do we need for alternate setup two UIs if we don?t want to use the REST interface or CLI-Tool?

o   One for ?Gateway Alpha? and one for ?Gateway Beta??

o   Because I think you can only connect one elasticseach instance with the UI. Am I right on this?

o   What about the metrics in this use case --> leads to two UIs?


?         For the ?one logical gateway?

o   If I understand you correctly this would mean that I also have to configure only one gateway in my UI and can add X more without adding them into the UI.
I just have to point them against the same elasticsearch instance.
I also post this mail to the github issue, so we can stay within the mailinglist.

Thanks again,
Florian


Von: Eric Wittmann <eric.wittmann at redhat.com>
Gesendet: Friday, 30 November 2018 14:57
An: Volk, Florian <Florian.Volk at scheer-group.com>
Cc: chttl582 at gmail.com; Marc Savy <marc.savy at redhat.com>; Kihm, Benjamin <Benjamin.Kihm at scheer-group.com>; Gebert, Alfred <Alfred.Gebert at scheer-group.com>; apiman-user at lists.jboss.org
Betreff: Re: [Apiman-user] [DKIM] Re: publish api to specific gateway

Sure no problem.  The typical use-case for having multiple Gateway nodes is to scale the gateway layer horizontally and then put a load balancer in front of them.  So for example you might start up 5 apiman gateway instances and configure them all to use the same Elasticsearch instance for persistence (i.e. where to store configuration info like which APIs have been published).  In this use-case, every gateway instance has the same set of APIs "published" to it.  You can publish an API from the UI/manager to **any** of the gateway instances and they will all know about that API.  This is the "Single Logical Gateway" use-case -- the UI/manager and all consumers don't know or care how many gateway nodes there are - there could be 1 node, or there could be 100.  It behaves the same logically.

An **alternate** use case for having multiple gateways is when you actually want different APIs to be deployed to different gateways.  So let's say you wanted Gateway Alpha to be able to proxy traffic to APIs A, B, and C.  Then you have Gateway Beta which you want to proxy traffic to APIs C, D, and E.  In that case, consumer traffic MUST be routed through Gateway Alpha in order to access APIs A and B.  Consumer traffic MUST be routed through Gateway Beta to access APIs D and E.  Finally, consumer traffic can be routed to **either** Gateway Alpha or Gateway Beta in order to access API C.  Think of this as the "Two Logical Gateways" use-case.

In order to achieve the "Two Logical Gateways" use-case, you will need **two** separate persistence stores (Elasticsearch instances).  Then you configure Gateway Alpha to use persistence store #1 and configure Gateway Beta to use persistence store #2.

Note that you can have multiple gateway nodes for EACH of the two logical gateways.  So for example you could have 5 gateway instances all pointing to persistence store #1 - these 5 nodes would make up a single logical gateway called "Gateway Alpha".  Then you could have 10 gateway instances all pointing to persistence store #2 - and these would be a single logical gateway called "Gateway Beta".

Here is a diagram of what the architecture might look like:

[image.png]


On Fri, Nov 30, 2018 at 8:38 AM Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>> wrote:
Hi Eric,

now I?m confused. We use Elasticsearch as backend. If I understand you correctly it would mean that we have to setup an Elasticsearch instance for each gateway?
On the other point, if the gateways operate as logical unit, why is there a configuration option in the ui?

Can you explain this a little bit more detailed? Maybe you have a configuration example.

Regards,
Florian

Von: Eric Wittmann <eric.wittmann at redhat.com<mailto:eric.wittmann at redhat.com>>
Gesendet: Friday, 30 November 2018 14:22
An: Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>>
Cc: chttl582 at gmail.com<mailto:chttl582 at gmail.com>; Marc Savy <marc.savy at redhat.com<mailto:marc.savy at redhat.com>>; Kihm, Benjamin <Benjamin.Kihm at scheer-group.com<mailto:Benjamin.Kihm at scheer-group.com>>; Gebert, Alfred <Alfred.Gebert at scheer-group.com<mailto:Alfred.Gebert at scheer-group.com>>; apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Betreff: Re: [Apiman-user] [DKIM] Re: publish api to specific gateway

Are both gateways using the same persistent storage?  Each gateway would need separate, independent persistence otherwise they will behave as a single "logical" gateway.

-Eric


On Fri, Nov 30, 2018 at 4:39 AM Volk, Florian <Florian.Volk at scheer-group.com<mailto:Florian.Volk at scheer-group.com>> wrote:
Hello together,

I was interested in this and made a short test in my loacal environment and I am able to reproduce this.
I created a ticket on github for this (https://github.com/apiman/apiman/issues/711). We may can fix this shortly.

Regards,
Florian

Von: apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org> <apiman-user-bounces at lists.jboss.org<mailto:apiman-user-bounces at lists.jboss.org>> Im Auftrag von Jon Huang
Gesendet: Friday, 30 November 2018 03:28
An: marc.savy at redhat.com<mailto:marc.savy at redhat.com>
Cc: apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>
Betreff: [DKIM] Re: [Apiman-user] publish api to specific gateway

Dear Marc

Yes I untick another gateway however request towards both gateways still works.
Besides I tried to publish API via admin REST API (post api version then put gateway info), both gateways forwards request too.
Before filing a bug is there any apigw setting I shall check? (such as parameter in apiman.properties or etc...)
Thanks for your help.
Regards
Marc Savy <marc.savy at redhat.com<mailto:marc.savy at redhat.com>> ? 2018?11?21? ?? ??9:35???
Apologies for the terribly slow reply. We've had so much spam I've missed legitimate emails like this.

Did you explicitly untick the other gateway? Was this via the UI or the API?

Did you resolve this issue? If not, please file a bug: https://github.com/apiman/apiman/issues

On Thu, 4 Oct 2018 at 05:00, Jon Huang <chttl582 at gmail.com<mailto:chttl582 at gmail.com>> wrote:
Dears

I had set up 2 gateways.
When I new an API, I have to choose which gateway to publish. (select list at Gateway section in the implementation tab).
However after creating a client app and contract for test, I found request via another gateway still works.
(I guest when publishing to gateway 1 and request via gateway 2 shall fail)
Am I misunderstanding or I miss some settings to make it work?
Thanks
_______________________________________________
Apiman-user mailing list
Apiman-user at lists.jboss.org<mailto:Apiman-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
_______________________________________________
Apiman-user mailing list
Apiman-user at lists.jboss.org<mailto:Apiman-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20181130/2fd7527d/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 82777 bytes
Desc: image002.png
Url : http://lists.jboss.org/pipermail/apiman-user/attachments/20181130/2fd7527d/attachment-0001.png