From stephane.riegel at gmail.com Sat Sep 3 10:14:49 2016 From: stephane.riegel at gmail.com (=?UTF-8?Q?St=C3=A9phane_Riegel_?=) Date: Sat, 3 Sep 2016 16:14:49 +0200 Subject: [Apiman-user] Apiman & Elasticsearch In-Reply-To: <7a8338dd-7ff5-42ce-09b0-2e1031cf0ac1@redhat.com> References: <7a8338dd-7ff5-42ce-09b0-2e1031cf0ac1@redhat.com> Message-ID: Hello Eric, Thanks a lot for this answer, the configuration you send me works well with a MySQL DB. Regarding the apiman cache container, could you send me the configuration that I need to use in a cluster environment with several apiman nodes ? Best regards, St?phane ----------------------------------------------------------------------- St?phane Riegel stephane.riegel at gmail.com 2016-09-01 2:12 GMT+02:00 Eric Wittmann : > Hi St?phane. > > Yes, it is possible to run apiman without using Elasticsearch at all. You > mentioned that you already replaced ES with mysql for the gateway > registry. There are several other components as well, including metrics. > We have documentation for metrics here: > > http://www.apiman.io/latest/installation-guide.html#_how_to_ > use_a_sql_database_to_store_and_retrieve_metrics_replacing_elasticsearch > > In addition, here is an example apiman.properties config that uses > alternatives for everything (Gateway only): > > https://gist.github.com/EricWittmann/822911517aa357b8c8c94c3ec79a32f3 > > Note that several of the components use Infinispan instead of > elasticsearch. In order to use the Infinispan components you'll need to be > using Wildfly *and* also add the following in your standalone-apiman.xml > file (in the right spot in that file): > > https://gist.github.com/EricWittmann/437432397f03270737d9fbd9bdadeaea > > There are other choices for these components, but currently only the > Elasticsearch and Infinispan implementations support multiple gateway > nodes. If you're just running a single Gateway node, you could use the > in-memory implementations of these components (although you would lose > state if the server was restarted). > > As for production references, I'm sorry to say that we don't really > solicit that information in the community. However I have CC'd this > response on the apiman users mailing list so perhaps someone will raise a > hand and describe their production experience. :) > > -Eric > > > > > On 8/31/2016 1:30 PM, St?phane Riegel wrote: > >> Hi Eric, >> >> >> >> I was interested on apiman opensource project and had a look on the >> configuration part and have two questions: >> >> >> Is it a way to not use elasticsearch at all on the project (gateway, >> metrics, rate ?) ? Are there alternatives backend like MySQL for all >> these elasticsearch features. I succeed to replace the gateway >> information with MySQL but not all others features (metrics, rate ?). >> >> >> Do you know if this project has some references in production? >> >> >> Thanks a lot. >> >> >> >> Best regards, >> >> >> >> St?phane >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160903/56993cce/attachment-0001.html From David.Rush at ihsmarkit.com Tue Sep 13 18:05:02 2016 From: David.Rush at ihsmarkit.com (David Rush) Date: Tue, 13 Sep 2016 22:05:02 +0000 Subject: [Apiman-user] Question about cross version compatibility Message-ID: <356f6b00211f4901b408c0ab4d9e8c5a@RIC1PDMSGDAG02.markit.partners> Good afternoon, I have a question about cross version compatibility between components. We currently have an install of 1.2.2-final but are looking to upgrade some hosts in the cluster to 1.2.7-final. Can a 1.2.7 manager publish to a 1.2.2 gateway? Or do I need to upgrade the whole cluster? Thanks David ________________________________ This e-mail, including accompanying communications and attachments, is strictly confidential and only for the intended recipient. Any retention, use or disclosure not expressly authorised by Markit is prohibited. This email is subject to all waivers and other terms at the following link: http://www.markit.com/en/about/legal/email-disclaimer.page Please visit http://www.markit.com/en/about/contact/contact-us.page for contact information on our offices worldwide. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160913/2a64af1f/attachment.html From eric.wittmann at redhat.com Wed Sep 14 07:49:04 2016 From: eric.wittmann at redhat.com (Eric Wittmann) Date: Wed, 14 Sep 2016 07:49:04 -0400 Subject: [Apiman-user] Question about cross version compatibility In-Reply-To: <356f6b00211f4901b408c0ab4d9e8c5a@RIC1PDMSGDAG02.markit.partners> References: <356f6b00211f4901b408c0ab4d9e8c5a@RIC1PDMSGDAG02.markit.partners> Message-ID: <023b3b20-05c4-43ee-8b2a-634bacdcb718@redhat.com> Hi David. I'm sorry to report that a 1.2.7 manager will not be able to publish to a 1.2.2 gateway - the data model for a published API changed a bit between those two versions. -Eric On 9/13/2016 6:05 PM, David Rush wrote: > Good afternoon, > > > > I have a question about cross version compatibility between components. > We currently have an install of 1.2.2-final but are looking to upgrade > some hosts in the cluster to 1.2.7-final. Can a 1.2.7 manager publish > to a 1.2.2 gateway? Or do I need to upgrade the whole cluster? > > > > Thanks > David > > > > > ------------------------------------------------------------------------ > > This e-mail, including accompanying communications and attachments, is > strictly confidential and only for the intended recipient. Any > retention, use or disclosure not expressly authorised by Markit is > prohibited. This email is subject to all waivers and other terms at the > following link: http://www.markit.com/en/about/legal/email-disclaimer.page > > Please visit http://www.markit.com/en/about/contact/contact-us.page for > contact information on our offices worldwide. > > > _______________________________________________ > Apiman-user mailing list > Apiman-user at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user >