[Apiman-user] apiman using external keycloak and elasticsearch

jazz at sqmail.me jazz at sqmail.me
Thu Mar 31 02:38:51 EDT 2016


OK, I'll try to use the older elasticsearch version. The apiman-es.war  
is not ideal. It slows down deployment of other war's. During  
deployment an elasticsearch maintenance action is started. Until it's  
finished no progress in the deployment sequence.

What got me stuck yesterday was that the apiman overlay includes  
keycloak as a module so it overwrites the keycloak version installed  
on wildfly (also as a module). To versions using the same local H2  
database doesn't work.

My experience so far with apiman, it works great, but the modularity  
could be improved:
1. Option to disable elasticsearch
2. Don't include keycloak in overlay
3. use cli files (like keycloak-install.cli)


Eric Wittmann – Wed., 30. March 2016 16:58
> OK that's reasonable.  Honestly I don't know why you would have any  
> problems with timing, unless you're trying to perform some sort of  
> data import on startup.
>
> Note that you can absolutely use an external, standalone  
> elasticsearch instance (I do this all the time) - you'll just need  
> to download an older version.  For example:
>
> www.elastic.co/downloads/past-releases/elasticsearch-1-7-5
>
> -Eric
>
> On 3/29/2016 4:08 PM, jazz wrote:
> > Hi Eric,
> >
> > Thanks for the pointer. I am back to using apiman-es.war i.s.o
> > elasticsearch 2.2.1
> >
> > If the wars are started in this order it seems to work:
> > 1. keycloak (seperate server)
> > 2. apiman & apimanui
> > 3. apiman-es (this takes time), when finished start 4
> > 4. apiman-gateway-engine-beans.jar
> > 5. apiman-gateway
> > 6. apiman-gateway-api
> >
> > Now working to get keycloak working... I will post logs when I get stuck
> > again.
> >
> > Thanks!
> >
> > Bart
> >
> > On Tue, 2016-03-29 at 11:54 -0400, Eric Wittmann wrote:
> >> Couple things here. First, we have not tested using Elasticsearch 2.x,
> >> so you should probably expect failures there.  We currently only support
> >> 1.x (e.g. 1.7.2).
> >>
> >> Next, in order to diagnose the startup problem, I need a bit more info.
> >>   Can you send the full wildfly startup log?  Can you also do a file
> >> listing here:
> >>
> >> ls -al $WILDFLY/standalone/deployments
> >>
> >> Thanks,
> >>
> >> -Eric
> >>
> >> On 3/29/2016 9:44 AM, jazz wrote:
> >>>
> >>> Hi,
> >>>
> >>> I would like to use apiman deployed on wildfly 10, without the included
> >>> keyloak and elasticsearch instances.
> >>>
> >>> keycloak (v1.9.1): localhost:8080/auth
> >>> elasticsearch (v2.2.1): localhost:9200
> >>> apiman (v1.2.3): localhost:8080/apiman
> >>>
> >>> This guide got me started:
> >>> www.apiman.io/latest/production-guide.html
> >>>
> >>> I use the overlay:
> >>>  
> downloads.jboss.org/apiman/1.2.3.Final/apiman-distro-wildfly10-1.2.3.Final-overlay.zip
> >>>
> >>> 2016-03-29 11:41:01,770 ERROR
> >>> [org.jboss.as.controller.management-operation] (DeploymentScanner-threads
> >>>   - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed -
> >>> address: ([]) - failure description:
> >>> {"WFLYCTL0288: One or more services were unable to start due to one or
> >>> more indirect dependencies not being available." => {
> >>>      "Services that were unable to start:" =>
> >>> ["jboss.deployment.unit.\"apiman-gateway-engine-beans.jar\".PARSE"],
> >>>      "Services that may be the cause:" => [
> >>>           
> "jboss.module.spec.service.\"deployment.apiman-gateway-engine-beans.jar\".main",
> >>>           
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
> >>>           
> "module.resolved.service.\"deployment.apiman-gateway-api.war\".main",
> >>>          "module.resolved.service.\"deployment.apiman-gateway.war\".main"
> >>>      ]
> >>> }}
> >>>
> >>> 2016-03-29 12:05:47,782 ERROR [org.jboss.msc.service.fail] (MSC service
> >>> thread 1-2) MSC000001: Failed t
> >>> o start service
> >>> jboss.deployment.unit."apiman-gateway-api.war".STRUCTURE:
> >>> org.jboss.msc.service.StartEx
> >>> ception in service
> >>> jboss.deployment.unit."apiman-gateway-api.war".STRUCTURE: WFLYSRV0153:
> >>> Failed to pro
> >>> cess phase STRUCTURE of deployment "apiman-gateway-api.war"
> >>>
> >>> Deployment in the web console works fine for these wars
> >>> apiman.war
> >>> apimanui.war
> >>>
> >>> The apiman-gateway.war and apiman-gateway-api.war fail.
> >>>
> >>> Question: how to deploy apiman using external keycloak and elasticsearch
> >>> instances running on the same host?
> >>>
> >>> Thanks in advance for any pointers.
> >>>
> >>> Regards, Bart
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Apiman-user mailing list
> >>> Apiman-user at lists.jboss.org <mailto:Apiman-user at lists.jboss.org>
> >>> lists.jboss.org/mailman/listinfo/apiman-user
> >>>
>



More information about the Apiman-user mailing list