load babalance requests
by Charles Moulliard
Hi,
Is it planned that Apiman will support active-active scenario and will
like Fuse HTTP Gateway load babalance requests to one of the available
endpoints ?
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
9 years, 1 month
Announcement: apiman 1.1.8.Final
by Eric Wittmann
Hey everyone.
Today we released apiman version 1.1.8.Final. This release is primarily
a bug-fix release (no new significant features are planned for 1.1.x).
You can see the release notes here:
http://red.ht/1igFSrj
We're continuing to work on the 1.2.x branch of apiman, where we should
have some cool new features coming soon.
-Eric
9 years, 1 month
Build failing due to missing vertx3 snapshot
by Marc Savy
Hi,
As many of you know, we have a preview of the Vert.x 3 gateway sitting
in master (if you use Java 8); however, it uses a 3.1.0-SNAPSHOT build
as there are a few bug-fixes and features we require that haven't
been released yet. Unfortunately, it looks like someone pulled the
snapshot over the weekend, and the build fails at the moment.
If you've built any time recently, you likely have the artefacts you
need cached in your .m2 repo, and all will be well.
We'll be switching to a released version of Vert.x 3 ASAP, which seems
to be scheduled for the near future. If not, we'll have to take some
more drastic action until things are available.
Regards,
Marc
9 years, 1 month
Call for testers: Vert.x 3 Gateway
by Marc Savy
Hi,
As you may (or may not) know, we have had a Vert.x 3-based gateway
hiding in our code-base for a couple of months now. Over that time it's
received a fair bit of automated and manual testing, in addition to a
good few tweaks and bug-fixes.
The next step is to have a few intrepid community members try it out!
It still has a few areas where we'll be looking to do improvements as
features arrive from upstream, but generally things should work fine.
Without further ado -
= Prerequisites:
* At the moment, ElasticSearch is the only component type supported. So,
you'll need ES available on the machine(s) you're testing this on.
* You need Java 8 and Maven
= Build apiman master:
git clone https://github.com/apiman/apiman.git && cd apiman
mvn clean install
cd gateway/platforms/vertx3/vertx3/
= Edit src/conf/conf.json:
To better understand how this works, check out this README:
https://github.com/apiman/apiman/blob/master/gateway/platforms/vertx3/ver...
Take particular note of which port your 'api' and 'http' verticles are
running on. Feel free to change the 'count' of each type (e.g. 5 policy
verticles).
For each of the ES components, you'll need to edit it to match your
local config - it might well be the same.
= Run:
java -jar
target/apiman-gateway-platforms-vertx3-1.2.0-SNAPSHOT-fat.jar -conf
src/conf/conf.json
= Add the gateway:
Fire up the apiman manager in the usual way, and in the Administration
section, 'Manage Gateways'. Put in the details of your Vert.x Gateway,
and give it a test
Remember: you need to add the *API* endpoint here - by default
http://localhost:8081; username: admin, password: admin.
You should be able to explicitly publish stuff to your Vert.x 3 gateway now!
= Are you brave?
Run with -cluster to run in clustered mode.
Let us know how it goes.
Regards,
Marc
9 years, 1 month
