From marc.savy at redhat.com  Mon Feb  1 11:51:59 2016
From: marc.savy at redhat.com (Marc Savy)
Date: Mon, 1 Feb 2016 16:51:59 +0000
Subject: [Apiman-user] Dropping Java 7 support on master
Message-ID: <56AF8D2F.1060500@redhat.com>

Hi,

Does anyone object if we drop Java 7 and move to Java 8 on master?

If so, what are said objections?

Regards,
Marc

From kstam at redhat.com  Mon Feb  1 20:16:03 2016
From: kstam at redhat.com (Kurt Stam)
Date: Mon, 1 Feb 2016 20:16:03 -0500
Subject: [Apiman-user] [Apiman-dev] Dropping Java 7 support on master
In-Reply-To: <56AF8D2F.1060500@redhat.com>
References: <56AF8D2F.1060500@redhat.com>
Message-ID: <-5767588634740236754@unknownmsgid>

I believe fabric8 is still on 1.7, so yeah that would be an issue. You
may have to hold off till after productization.

> On Feb 1, 2016, at 11:52, Marc Savy <marc.savy at redhat.com> wrote:
>
> Hi,
>
> Does anyone object if we drop Java 7 and move to Java 8 on master?
>
> If so, what are said objections?
>
> Regards,
> Marc
> _______________________________________________
> Apiman-dev mailing list
> Apiman-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-dev

From kbabo at redhat.com  Mon Feb  1 20:19:10 2016
From: kbabo at redhat.com (Keith Babo)
Date: Tue, 2 Feb 2016 02:19:10 +0100
Subject: [Apiman-user] [Apiman-dev] Dropping Java 7 support on master
In-Reply-To: <-5767588634740236754@unknownmsgid>
References: <56AF8D2F.1060500@redhat.com> <-5767588634740236754@unknownmsgid>
Message-ID: <580F1DA0-C796-436A-A773-0BFE830079F7@redhat.com>

Hey Kurt,

The FIS images all use Java 8, IINM.  Are there other pieces of Fabric8 related to apiman which require Java 7?

regards,
keith

> On Feb 2, 2016, at 2:16 AM, Kurt Stam <kstam at redhat.com> wrote:
> 
> I believe fabric8 is still on 1.7, so yeah that would be an issue. You
> may have to hold off till after productization.
> 
>> On Feb 1, 2016, at 11:52, Marc Savy <marc.savy at redhat.com> wrote:
>> 
>> Hi,
>> 
>> Does anyone object if we drop Java 7 and move to Java 8 on master?
>> 
>> If so, what are said objections?
>> 
>> Regards,
>> Marc
>> _______________________________________________
>> Apiman-dev mailing list
>> Apiman-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/apiman-dev
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user



From cmoulliard at redhat.com  Tue Feb  2 07:13:56 2016
From: cmoulliard at redhat.com (Charles Moulliard)
Date: Tue, 2 Feb 2016 13:13:56 +0100
Subject: [Apiman-user] Deploy Apiman Manager, Gateway,
 Elasticsearch locally - new bash script
Message-ID: <56B09D84.9030102@redhat.com>

Hi,

FYI, I have created a new bash script to install / deploy locally Apiman 
on one machine. Here is the link of the PR : 
https://github.com/apiman/apiman-deployer/pull/1
When you will use it, you can accept the default values

Apiman Version :1.2.1.Final
ElasticSearch Version :1.7.2
Wildfly version : 9.0.2.Final

ElasticSearch Server : http://localhost:9200
Apiman Manager : http://localhost:8080. (Keycloak Server is running with 
Apiman Manager)
Database : h2
Apiman Gateway :
Gateway Public Endpoint : https://localhost:8543/apiman-gateway/
Keycloak Server : https://localhost:8443/auth

Here is the offset of the port defined
- Apiman Manager offset: 0 (-> 8080, 8443)
- Apiman Gateway offset: 100 (-> 8180, 8543)
- Apiman Keycloak Server offset: 200 (-> 8280, 8643)

Remark :
- The script has been tested on MacOS X (= Darwin OS) with the 
simple-echo service part of the apiman-quickstart project (mvn jetty:run).

http --verify=no GET https://localhost:8543/apiman-gateway/fuse/echo/1.0
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 317
Content-Type: application/json
Date: Tue, 02 Feb 2016 11:58:29 GMT
Server: Jetty(9.3.0.v20150612)
X-Powered-By: Undertow/1

{
     "bodyLength": null,
     "bodySha1": null,
     "headers": {
         "Accept": "*/*",
         "Accept-Encoding": "gzip, deflate",
         "Connection": "keep-alive",
         "Host": "localhost:9999",
         "User-Agent": "HTTPie/0.9.2"
     },
     "method": "GET",
     "resource": "/apiman-echo/hello",
     "uri": "/apiman-echo/hello"
}

- The only thing that I have done manually is to add a NEW gateway 
within the Apiman Manager GUI 
(http://localhost:8080/apimanui/api-manager/admin/gateways) using this 
address : https://localhost:8543/apiman-gateway/ and user : apimanager & 
pwd : apiman123!

Regards,
-- 
Charles Moulliard
Principal Solution Architect / JBoss Fuse Expert - Global Enablement @redhat
cmoulliard at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160202/cef6dee9/attachment.html 

From cmoulliard at redhat.com  Tue Feb  2 07:37:17 2016
From: cmoulliard at redhat.com (Charles Moulliard)
Date: Tue, 2 Feb 2016 13:37:17 +0100
Subject: [Apiman-user] Change default gateway instance
Message-ID: <56B0A2FD.2090909@redhat.com>

Hi,

Is it possible to change during installation (download of apiman distro, 
wildfly9, unzip, ...) of Apiman Manager the gateway defined by default 
(Gateway name: 'The Gateway , description: 'This is the gateway', 
Configuration endpoint: 'https://localhost:8443/apiman-gateway-api') . I 
would like to delete the existing and add a new one corresponding to an 
external Apiman Gateway ?

Regards,

Charles

From eric.wittmann at redhat.com  Tue Feb  2 08:20:26 2016
From: eric.wittmann at redhat.com (Eric Wittmann)
Date: Tue, 2 Feb 2016 08:20:26 -0500
Subject: [Apiman-user] Change default gateway instance
In-Reply-To: <56B0A2FD.2090909@redhat.com>
References: <56B0A2FD.2090909@redhat.com>
Message-ID: <56B0AD1A.7010605@redhat.com>

At the moment it is not possible to do this at installation time.  Of 
course, once apiman is running you can use the REST layer to change the 
gateway information.

We have an Import feature which could also be used, but we don't yet 
have a feature that will trigger the import during startup.

I think there is a JIRA kicking around for the latter issue.

https://issues.jboss.org/browse/APIMAN-566

I can kick it up the priority list since it's been requested a few times 
now (and would be particularly handy when using e.g. docker).

Would that solve the issue for you?

-Eric

On 2/2/2016 7:37 AM, Charles Moulliard wrote:
> Hi,
>
> Is it possible to change during installation (download of apiman distro,
> wildfly9, unzip, ...) of Apiman Manager the gateway defined by default
> (Gateway name: 'The Gateway , description: 'This is the gateway',
> Configuration endpoint: 'https://localhost:8443/apiman-gateway-api') . I
> would like to delete the existing and add a new one corresponding to an
> external Apiman Gateway ?
>
> Regards,
>
> Charles
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>

From cmoulliard at redhat.com  Tue Feb  2 08:45:25 2016
From: cmoulliard at redhat.com (Charles Moulliard)
Date: Tue, 2 Feb 2016 14:45:25 +0100
Subject: [Apiman-user] Change default gateway instance
In-Reply-To: <56B0AD1A.7010605@redhat.com>
References: <56B0A2FD.2090909@redhat.com> <56B0AD1A.7010605@redhat.com>
Message-ID: <56B0B2F5.2070505@redhat.com>

I will add a separate bash script to execute a curl or http request in 
order to add/remove the gateway till we have this import feature 
(https://issues.jboss.org/browse/APIMAN-566).

On 02/02/16 14:20, Eric Wittmann wrote:
> At the moment it is not possible to do this at installation time.  Of 
> course, once apiman is running you can use the REST layer to change 
> the gateway information.
>
> We have an Import feature which could also be used, but we don't yet 
> have a feature that will trigger the import during startup.
>
> I think there is a JIRA kicking around for the latter issue.
>
> https://issues.jboss.org/browse/APIMAN-566
>
> I can kick it up the priority list since it's been requested a few 
> times now (and would be particularly handy when using e.g. docker).
>
> Would that solve the issue for you?
>
> -Eric
>
> On 2/2/2016 7:37 AM, Charles Moulliard wrote:
>> Hi,
>>
>> Is it possible to change during installation (download of apiman distro,
>> wildfly9, unzip, ...) of Apiman Manager the gateway defined by default
>> (Gateway name: 'The Gateway , description: 'This is the gateway',
>> Configuration endpoint: 'https://localhost:8443/apiman-gateway-api') . I
>> would like to delete the existing and add a new one corresponding to an
>> external Apiman Gateway ?
>>
>> Regards,
>>
>> Charles
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>


From cmoulliard at redhat.com  Fri Feb 19 13:17:52 2016
From: cmoulliard at redhat.com (Charles Moulliard)
Date: Fri, 19 Feb 2016 19:17:52 +0100
Subject: [Apiman-user] Error 401 - Unit test with gateway
Message-ID: <56C75C50.1090407@redhat.com>

Hi,

I have developed a unit test to control the REST Gateway Api when 
deployed into Karaf using Apache HttpClient but when I issue this request

https://localhost:8444/apiman-gateway-api/system/status

I receive an error 401

https://gist.githubusercontent.com/cmoulliard/daa13f336b04ba625af4/raw/f9147c9d426c5457ba0a9df09c4af324f2879982/gistfile1.txt

2016-02-19 19:09:10,722 | INFO  | (3)-192.168.1.80 | 
HttpServiceFactoryImpl           | 66 - 
org.ops4j.pax.web.pax-web-runtime - 3.2.4 | Unbinding bundle: 
[io.apiman.apiman-gateway-osgi-api [212]]
javax.servlet.ServletException
     at org.eclipse.jetty.server.Request.login(Request.java:2109)
     at 
io.apiman.common.servlet.AuthenticationFilter.doBasicAuth(AuthenticationFilter.java:232)

As the same request works pretty well when issued using curl/httpie tool 
against the Karaf container running in standalone mode, I 'm wondering 
why it fails with HttpClient & Basic Authentication ?

Regards,

Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160219/d2ec325e/attachment.html 

From aikeaguinea at xsmail.com  Tue Feb 23 17:07:20 2016
From: aikeaguinea at xsmail.com (Aikeaguinea)
Date: Tue, 23 Feb 2016 17:07:20 -0500
Subject: [Apiman-user] Elasticsearch configuration
Message-ID: <1456265240.2661102.529881690.421DF35F@webmail.messagingengine.com>

I'm moving toward a production deployment of apiman on AWS. At least for
now we're using Amazon's Elasticsearch service and have been able to
configure and use it.

For production, we need to pay attention to some of the finer details of
clustering, etc. It looks like sharding is mainly controlled when an
index is created. How does apiman manage creating replica shards? Does
this need to be configured somehow?

-- 
http://www.fastmail.com - IMAP accessible web-mail


From cmoulliard at redhat.com  Wed Feb 24 04:13:52 2016
From: cmoulliard at redhat.com (Charles Moulliard)
Date: Wed, 24 Feb 2016 10:13:52 +0100
Subject: [Apiman-user] Test util class to start ES
Message-ID: <56CD7450.3010905@redhat.com>

Hi,

Do we have a utility class that we can use to create an instance of 
Elasticsearch that we can start before to run a unit test ?

Regards,

Charles

From eric.wittmann at redhat.com  Wed Feb 24 10:44:13 2016
From: eric.wittmann at redhat.com (Eric Wittmann)
Date: Wed, 24 Feb 2016 10:44:13 -0500
Subject: [Apiman-user] Elasticsearch configuration
In-Reply-To: <1456265240.2661102.529881690.421DF35F@webmail.messagingengine.com>
References: <1456265240.2661102.529881690.421DF35F@webmail.messagingengine.com>
Message-ID: <56CDCFCD.9010408@redhat.com>

Apiman will automatically create the appropriate ES indexes if they do 
not exist.  However, it does this in a very naive way:

https://github.com/apiman/apiman/blob/master/gateway/engine/es/src/main/java/io/apiman/gateway/engine/es/ESClientFactory.java#L220-L233

That said, we aren't really elasticsearch experts, so I'm not too 
confident offering advice on how to scale/cluster a production instance 
of Elasticsearch (note that we are working on alternatives).

My suggestion is probably to create the indexes manually, and shard them 
however you think is appropriate.  Apiman will then simply use the 
indexes you create rather than create them for you.  You can use the ES 
Mappings files when configuring the indexes:

https://github.com/apiman/apiman/tree/master/gateway/engine/es/src/main/resources/io/apiman/gateway/engine/es

-Eric

On 2/23/2016 5:07 PM, Aikeaguinea wrote:
> I'm moving toward a production deployment of apiman on AWS. At least for
> now we're using Amazon's Elasticsearch service and have been able to
> configure and use it.
>
> For production, we need to pay attention to some of the finer details of
> clustering, etc. It looks like sharding is mainly controlled when an
> index is created. How does apiman manage creating replica shards? Does
> this need to be configured somehow?
>

From aikeaguinea at xsmail.com  Wed Feb 24 13:52:07 2016
From: aikeaguinea at xsmail.com (Aikeaguinea)
Date: Wed, 24 Feb 2016 13:52:07 -0500
Subject: [Apiman-user] Elasticsearch configuration
In-Reply-To: <56CDCFCD.9010408@redhat.com>
References: <1456265240.2661102.529881690.421DF35F@webmail.messagingengine.com>
	<56CDCFCD.9010408@redhat.com>
Message-ID: <1456339927.2956591.530835378.6139C8A8@webmail.messagingengine.com>

Thanks!

On Wed, Feb 24, 2016, at 10:44 AM, Eric Wittmann wrote:
> Apiman will automatically create the appropriate ES indexes if they do 
> not exist.  However, it does this in a very naive way:
> 
> https://github.com/apiman/apiman/blob/master/gateway/engine/es/src/main/java/io/apiman/gateway/engine/es/ESClientFactory.java#L220-L233
> 
> That said, we aren't really elasticsearch experts, so I'm not too 
> confident offering advice on how to scale/cluster a production instance 
> of Elasticsearch (note that we are working on alternatives).
> 
> My suggestion is probably to create the indexes manually, and shard them 
> however you think is appropriate.  Apiman will then simply use the 
> indexes you create rather than create them for you.  You can use the ES 
> Mappings files when configuring the indexes:
> 
> https://github.com/apiman/apiman/tree/master/gateway/engine/es/src/main/resources/io/apiman/gateway/engine/es
> 
> -Eric
> 
> On 2/23/2016 5:07 PM, Aikeaguinea wrote:
> > I'm moving toward a production deployment of apiman on AWS. At least for
> > now we're using Amazon's Elasticsearch service and have been able to
> > configure and use it.
> >
> > For production, we need to pay attention to some of the finer details of
> > clustering, etc. It looks like sharding is mainly controlled when an
> > index is created. How does apiman manage creating replica shards? Does
> > this need to be configured somehow?
> >


-- 
  Aikeaguinea
  aikeaguinea at xsmail.com

-- 
http://www.fastmail.com - Choose from over 50 domains or use your own


From eric.wittmann at redhat.com  Thu Feb 25 07:50:03 2016
From: eric.wittmann at redhat.com (Eric Wittmann)
Date: Thu, 25 Feb 2016 07:50:03 -0500
Subject: [Apiman-user] Elasticsearch configuration
In-Reply-To: <1456339927.2956591.530835378.6139C8A8@webmail.messagingengine.com>
References: <1456265240.2661102.529881690.421DF35F@webmail.messagingengine.com>
	<56CDCFCD.9010408@redhat.com>
	<1456339927.2956591.530835378.6139C8A8@webmail.messagingengine.com>
Message-ID: <56CEF87B.60404@redhat.com>

No problem.  If you end up with a production configuration strategy for 
elasticsearch+apiman we'd love to hear about it!  Perhaps a guest blog 
post?  :)

Just a thought...

-Eric

On 2/24/2016 1:52 PM, Aikeaguinea wrote:
> Thanks!
>
> On Wed, Feb 24, 2016, at 10:44 AM, Eric Wittmann wrote:
>> Apiman will automatically create the appropriate ES indexes if they do
>> not exist.  However, it does this in a very naive way:
>>
>> https://github.com/apiman/apiman/blob/master/gateway/engine/es/src/main/java/io/apiman/gateway/engine/es/ESClientFactory.java#L220-L233
>>
>> That said, we aren't really elasticsearch experts, so I'm not too
>> confident offering advice on how to scale/cluster a production instance
>> of Elasticsearch (note that we are working on alternatives).
>>
>> My suggestion is probably to create the indexes manually, and shard them
>> however you think is appropriate.  Apiman will then simply use the
>> indexes you create rather than create them for you.  You can use the ES
>> Mappings files when configuring the indexes:
>>
>> https://github.com/apiman/apiman/tree/master/gateway/engine/es/src/main/resources/io/apiman/gateway/engine/es
>>
>> -Eric
>>
>> On 2/23/2016 5:07 PM, Aikeaguinea wrote:
>>> I'm moving toward a production deployment of apiman on AWS. At least for
>>> now we're using Amazon's Elasticsearch service and have been able to
>>> configure and use it.
>>>
>>> For production, we need to pay attention to some of the finer details of
>>> clustering, etc. It looks like sharding is mainly controlled when an
>>> index is created. How does apiman manage creating replica shards? Does
>>> this need to be configured somehow?
>>>
>
>

From eric.wittmann at redhat.com  Thu Feb 25 07:51:29 2016
From: eric.wittmann at redhat.com (Eric Wittmann)
Date: Thu, 25 Feb 2016 07:51:29 -0500
Subject: [Apiman-user] Error 401 - Unit test with gateway
In-Reply-To: <56C75C50.1090407@redhat.com>
References: <56C75C50.1090407@redhat.com>
Message-ID: <56CEF8D1.9000004@redhat.com>

My guess is that the credentials are incorrect.  I can't think of any 
other reason.  The credentials used in the unit test must be different 
from the user configuration you have in karaf?

On 2/19/2016 1:17 PM, Charles Moulliard wrote:
> Hi,
>
> I have developed a unit test to control the REST Gateway Api when
> deployed into Karaf using Apache HttpClient but when I issue this request
>
> https://localhost:8444/apiman-gateway-api/system/status
>
> I receive an error 401
>
> https://gist.githubusercontent.com/cmoulliard/daa13f336b04ba625af4/raw/f9147c9d426c5457ba0a9df09c4af324f2879982/gistfile1.txt
>
> 2016-02-19 19:09:10,722 | INFO  | (3)-192.168.1.80 |
> HttpServiceFactoryImpl           | 66 -
> org.ops4j.pax.web.pax-web-runtime - 3.2.4 | Unbinding bundle:
> [io.apiman.apiman-gateway-osgi-api [212]]
> javax.servlet.ServletException
>      at org.eclipse.jetty.server.Request.login(Request.java:2109)
>      at
> io.apiman.common.servlet.AuthenticationFilter.doBasicAuth(AuthenticationFilter.java:232)
>
> As the same request works pretty well when issued using curl/httpie tool
> against the Karaf container running in standalone mode, I 'm wondering
> why it fails with HttpClient & Basic Authentication ?
>
> Regards,
>
> Charles
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>

From marc.savy at redhat.com  Thu Feb 25 07:54:53 2016
From: marc.savy at redhat.com (Marc Savy)
Date: Thu, 25 Feb 2016 12:54:53 +0000
Subject: [Apiman-user] FWD Re:  Error 401 - Unit test with gateway
In-Reply-To: <56CD74C5.4010609@redhat.com>
References: <56CD74C5.4010609@redhat.com>
Message-ID: <56CEF99D.4030000@redhat.com>

To avoid further duplicated replies, fwding Charles' mail to me...

-------- Forwarded Message --------

Problem solved. My karaf unit test missed the file containing the Jetty
REALM to authenticate the use.

On 19/02/16 20:34, Marc Savy wrote:
> The only thing I can imagine is that you constructed the Authorization
> header incorrectly and/or the test isn't using the auth information
> you're assuming?
>
> It's impossible to guess from the information you've provided I'm afraid
>
> On 19/02/2016 18:17, Charles Moulliard wrote:
>> Hi,
>>
>> I have developed a unit test to control the REST Gateway Api when
>> deployed into Karaf using Apache HttpClient but when I issue this
>> request
>>
>> https://localhost:8444/apiman-gateway-api/system/status
>>
>> I receive an error 401
>>
>> https://gist.githubusercontent.com/cmoulliard/daa13f336b04ba625af4/raw/f9147c9d426c5457ba0a9df09c4af324f2879982/gistfile1.txt
>>
>>
>> 2016-02-19 19:09:10,722 | INFO  | (3)-192.168.1.80 |
>> HttpServiceFactoryImpl           | 66 -
>> org.ops4j.pax.web.pax-web-runtime - 3.2.4 | Unbinding bundle:
>> [io.apiman.apiman-gateway-osgi-api [212]]
>> javax.servlet.ServletException
>>      at org.eclipse.jetty.server.Request.login(Request.java:2109)
>>      at
>> io.apiman.common.servlet.AuthenticationFilter.doBasicAuth(AuthenticationFilter.java:232)
>>
>>
>> As the same request works pretty well when issued using curl/httpie tool
>> against the Karaf container running in standalone mode, I 'm wondering
>> why it fails with HttpClient & Basic Authentication ?
>>
>> Regards,
>>
>> Charles
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>
>




From michele.danieli at gmail.com  Thu Feb 25 08:58:25 2016
From: michele.danieli at gmail.com (michele danieli)
Date: Thu, 25 Feb 2016 14:58:25 +0100
Subject: [Apiman-user] Extending the Client lifecycle
Message-ID: <CAH+8e1fPBOApejpZpe8L8kP4d=5Vc7eYPE9B2ouD0qqT1impCA@mail.gmail.com>

I have to integrate an external (and existing) Authentication provider that
will support the OAuth flow.

While I understand the implementation aspects of the plugin (looking at the
code was useful) I am wondering how can I extend the client life-cycle in
order to create a client on the external provider (via a REST end-point)
and receive a client id and secret.  Additionally I would like to extend
the client model in order to make this information in the ClientApp
property page.

Anyone considered a similar scenario?

Thanks
Michele
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160225/49eaa311/attachment-0001.html 

From santhoshjoy at gmail.com  Fri Feb 26 12:45:52 2016
From: santhoshjoy at gmail.com (Santhosh)
Date: Fri, 26 Feb 2016 09:45:52 -0800
Subject: [Apiman-user] Amazon ES 443 issue
Message-ID: <CAGj2ZHEU_e7cScuh7Fz3Pcfck0fWegXOsOV3C8F+ooWCjXo+qQ@mail.gmail.com>

Hi Eric and Team,


   I saw a discussion you were doing about Amazon ES when we try to connect
through 443 (below is the link). Did you guys find out any solution for it.


http://lists.jboss.org/pipermail/apiman-user/2015-December/000423.html


  I am facing the same and trying to reach you to get If you have any
solutions for it.


Thanks,

Santhosh

-- 
Thanks,
Santhosh
(650)430-6581
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160226/10383215/attachment.html 

From eric.wittmann at redhat.com  Fri Feb 26 13:35:16 2016
From: eric.wittmann at redhat.com (Eric Wittmann)
Date: Fri, 26 Feb 2016 13:35:16 -0500
Subject: [Apiman-user] Amazon ES 443 issue
In-Reply-To: <CAGj2ZHEU_e7cScuh7Fz3Pcfck0fWegXOsOV3C8F+ooWCjXo+qQ@mail.gmail.com>
References: <CAGj2ZHEU_e7cScuh7Fz3Pcfck0fWegXOsOV3C8F+ooWCjXo+qQ@mail.gmail.com>
Message-ID: <56D09AE4.7090300@redhat.com>

I think the solution to the problem you are referencing can be found here:

http://lists.jboss.org/pipermail/apiman-user/2015-December/000453.html

It was an issue with the ordering of properties (standalone.xml 
properties vs. properties in apiman.properties).

If this doesn't sound relevant, I'd be happy to try and help with given 
additional context.  :)

-Eric

On 2/26/2016 12:45 PM, Santhosh wrote:
> Hi Eric and Team,
>
>
>     I saw a discussion you were doing about Amazon ES when we try to
> connect through 443 (below is the link). Did you guys find out any
> solution for it.
>
>
> http://lists.jboss.org/pipermail/apiman-user/2015-December/000423.html
>
>
>    I am facing the same and trying to reach you to get If you have any
> solutions for it.
>
>
> Thanks,
>
> Santhosh
>
>
> --
> Thanks,
> Santhosh
> (650)430-6581
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>

From kstam at redhat.com  Fri Feb 26 13:48:23 2016
From: kstam at redhat.com (Kurt Stam)
Date: Fri, 26 Feb 2016 13:48:23 -0500
Subject: [Apiman-user] Amazon ES 443 issue
In-Reply-To: <CAGj2ZHEU_e7cScuh7Fz3Pcfck0fWegXOsOV3C8F+ooWCjXo+qQ@mail.gmail.com>
References: <CAGj2ZHEU_e7cScuh7Fz3Pcfck0fWegXOsOV3C8F+ooWCjXo+qQ@mail.gmail.com>
Message-ID: <CACkpAAbCucP-5dej-+Xdzk8bQWi_Kto7XFre6DiFKuybtsg69g@mail.gmail.com>

Hi Santhosh, the stack trace suggests that it simply can't get to the
endpoint. Can you try

1. do  wget '*search-testapi-....us-west-2.es.amazonaws.com:443
<http://us-west-2.es.amazonaws.com:443>' (whatever the full ES URL is you
are using)*

*2. If 1 works then log into the apiman-gateway container using*

*docker exec -it <container id>*

*where you can find the container-id from *

*docker ps | grep apiman-gateway*

*(or in the latest fabric8 console you can get a terminal too)*

*and then execute the same wget from step 1 (or curl) to ES and see if that
works*

*--Kurt*

On Fri, Feb 26, 2016 at 12:45 PM, Santhosh <santhoshjoy at gmail.com> wrote:

> Hi Eric and Team,
>
>
>    I saw a discussion you were doing about Amazon ES when we try to
> connect through 443 (below is the link). Did you guys find out any solution
> for it.
>
>
> http://lists.jboss.org/pipermail/apiman-user/2015-December/000423.html
>
>
>   I am facing the same and trying to reach you to get If you have any
> solutions for it.
>
>
> Thanks,
>
> Santhosh
>
> --
> Thanks,
> Santhosh
> (650)430-6581
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>


-- 
Kurt T. Stam

twitter: @KurtStam
google+: kurt.stam at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20160226/a2548983/attachment.html