10:22 a.m.
That setting in apiman is for the client (when connecting apiman to the
possibly remote elasticsearch instance). The apiman quickstart also
comes with a built-in elasticsearch *server* which always runs on port
19200. If you no longer want to use the built-in apiman-es instance,
then you can remove "apiman-es.war" from your deployments.
-Eric
On 9/9/2015 9:45 AM, Charles Moulliard wrote:
Hi,
If I change the apiman.properties file located under
standalone/configuration folder of wildfly
(apiman-1.1.7.Final/wildfly-8.2.0.Final/standalone/configuration/apiman.properties),
save it and restart wildfly
# ---------------------------------------------------------------------
# The following are settings for using elasticsearch for various
# apiman components.
# ---------------------------------------------------------------------
apiman.es.protocol=http
#apiman.es.host=localhost
#apiman.es.port=19200
apiman.es.host=localhost
apiman.es.port=9200
apiman.es.username=
apiman.es.password=
apiman continues to use the old setting of ElasticSearch (= port 19200
and not 9200 as changed).
15:19:20,637 INFO [org.wildfly.extension.undertow] (MSC service thread
1-9) JBAS017534: Registered web context: /auth
15:19:21,622 INFO [org.elasticsearch.cluster.service]
(elasticsearch[Bobster][clusterService#updateTask][T#1]) [Bobster]
new_master
[Bobster][JzTqzlrTQtC5lsLhrjrPyQ][localhost][inet[/192.168.1.80:19300]]{local=false},
reason: zen-disco-join (elected_as_master)
15:19:21,649 INFO [org.elasticsearch.http] (MSC service thread 1-13)
[Bobster] bound_address {inet[/0.0.0.0:19200]}, publish_address
{inet[/192.168.1.80:19200]}
15:19:21,650 INFO [org.elasticsearch.node] (MSC service thread 1-13)
[Bobster] started
15:19:21,650 INFO [stdout] (MSC service thread 1-13)
-----------------------------
15:19:21,651 INFO [stdout] (MSC service thread 1-13) apiman-es started!
15:19:21,651 INFO [stdout] (MSC service thread 1-13)
-----------------------------
15:19:21,655 INFO [org.wildfly.extension.undertow] (MSC service thread
1-13) JBAS017534: Registered web context: /apiman-es
Is there something else to do ?
Regards,
--
Charles Moulliard
Principal Solution Architect / JBoss Fuse Expert - Global Enablement @redhat
cmoulliard(a)redhat.com | work: +31 205 65 12 84 | mobile: +32 473 604 014
MC-Square Business "Stockholm", Leonardo Da Vincilaan 19, Diegem 1831 -
Belgium
twitter: @cmoulliard <http://twitter.com/cmoulliard> | blog:
cmoulliard.github.io <http://cmoulliard.github.io>
committer: apache camel, karaf, servicemix, hawtio, fabric8, drools,
jbpm, deltaspike
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user