<div dir="ltr"><div><br></div>Hello Eric,<div><br></div><div>Thanks a lot for this answer, the configuration you send me works well with a MySQL DB.</div><div><br><div>Regarding the apiman cache container, could you send me the configuration that I need to use in a cluster environment with several apiman nodes ?</div></div><div><br></div><div>Best regards,</div><div><br></div><div>Stéphane</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">-----------------------------------------------------------------------<br>Stéphane Riegel<br><a href="mailto:stephane.riegel@gmail.com" target="_blank">stephane.riegel@gmail.com</a></div></div>
<br><div class="gmail_quote">2016-09-01 2:12 GMT+02:00 Eric Wittmann <span dir="ltr"><<a href="mailto:eric.wittmann@redhat.com" target="_blank">eric.wittmann@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Stéphane.<br>
<br>
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:<br>
<br>
<a href="http://www.apiman.io/latest/installation-guide.html#_how_to_use_a_sql_database_to_store_and_retrieve_metrics_replacing_elasticsearch" rel="noreferrer" target="_blank">http://www.apiman.io/latest/in<wbr>stallation-guide.html#_how_to_<wbr>use_a_sql_database_to_store_<wbr>and_retrieve_metrics_replacing<wbr>_elasticsearch</a><br>
<br>
In addition, here is an example apiman.properties config that uses alternatives for everything (Gateway only):<br>
<br>
<a href="https://gist.github.com/EricWittmann/822911517aa357b8c8c94c3ec79a32f3" rel="noreferrer" target="_blank">https://gist.github.com/EricWi<wbr>ttmann/822911517aa357b8c8c94c3<wbr>ec79a32f3</a><br>
<br>
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):<br>
<br>
<a href="https://gist.github.com/EricWittmann/437432397f03270737d9fbd9bdadeaea" rel="noreferrer" target="_blank">https://gist.github.com/EricWi<wbr>ttmann/437432397f03270737d9fbd<wbr>9bdadeaea</a><br>
<br>
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).<br>
<br>
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. :)<span class="HOEnZb"><font color="#888888"><br>
<br>
-Eric</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
On 8/31/2016 1:30 PM, Stéphane Riegel wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Eric,<br>
<br>
<br>
<br>
I was interested on apiman opensource project and had a look on the<br>
configuration part and have two questions:<br>
<br>
<br>
Is it a way to not use elasticsearch at all on the project (gateway,<br>
metrics, rate …) ? Are there alternatives backend like MySQL for all<br>
these elasticsearch features. I succeed to replace the gateway<br>
information with MySQL but not all others features (metrics, rate …).<br>
<br>
<br>
Do you know if this project has some references in production?<br>
<br>
<br>
Thanks a lot.<br>
<br>
<br>
<br>
Best regards,<br>
<br>
<br>
<br>
Stéphane<br>
<br>
</blockquote>
</div></div></blockquote></div><br></div>