Hi Udara, I faced the same problem and ended up with the error message you have mentioned above. In my case I have enabled dep-sync in both gateway nodes and used WSClient client type. There was a configuration issue in my dep-sync configuration and it was the root cause for my issue. Have you enabled dep-sync in gateway nodes in your deployment ? If you have enabled dep-sync , you can cleanup existing artifacts and retry if possible.
Regards, Malintha On Wed, Sep 23, 2015 at 8:48 AM, Amila De Silva <[email protected]> wrote: > Hi Udara, > > What is the client type you are using? Can you switch it to WSClient and > check. > > > On Wednesday, September 23, 2015, Udara Liyanage <[email protected]> wrote: > >> Hi Ajith, >> >> APIM2 is only acting as a gateway. The only difference to have two >> distributed gateways[1]is when APIs are created in API1, it should be >> available in APIM2 too. >> >> [1] https://docs.wso2.com/display/CLUSTER420/Clustering+API+Manager >> >> On Tue, Sep 22, 2015 at 1:15 PM, Ajith Vitharana <[email protected]> wrote: >> >>> If you have created the API from APIM1 , then API meta data has stored >>> in APIM1 databases (registry and AM db). AFAIU you need to share the >>> databases (registry and AM db) with APIM2 >>> >>> -Ajith >>> >>> On Tue, Sep 22, 2015 at 4:04 PM, Udara Liyanage <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> [1] I am trying to do what described in [1]. I have two APIMs in two >>>> regions. >>>> >>>> In APIM1 , I added second APIM as an environment. >>>> >>>> <Environment type="hybrid"> >>>> <Name>Gateway B</Name> >>>> <ServerURL>https://apim2.com:9443/services/ >>>> </ServerURL> >>>> <Username>admin</Username> >>>> <Password>admin</Password> >>>> <GatewayEndpoint>http://apim2.com:8280, >>>> https://apim2.com:8243</GatewayEndpoint> >>>> </Environment> >>>> </Environments> >>>> >>>> In APIM2 , I pointed APIM as the Key manager. >>>> >>>> <APIKeyValidator> >>>> <ServerURL>https://apim1:9443/services/</ServerURL> >>>> <Username>admin</Username> >>>> <Password>admin</Password> >>>> >>>> Now when I create an API in APIM, artifacts are successfully published >>>> to APIM2 too as expected. I manually check the artifacts and both has the >>>> same API artifacts. >>>> >>>> Then I tried accessing the API from APIM1 which got succeeded. >>>> However when I try to access the API from APIM2, I get the following >>>> error message >>>> >>>> *No matching resource found in the API for the given >>>> request</ams:message><ams:description>Access failure for API: /sample/v1, >>>> version: v1 with key: c0dca4351fa3f074cd52a6087409743. Check the API >>>> documentation and add a proper REST resource path to the invocation URL* >>>> >>>> *[1] * >>>> https://docs.wso2.com/display/AM170/Maintaining+Separate+Production+and+Sandbox+Gateways >>>> -- >>>> >>>> Udara Liyanage >>>> Software Engineer >>>> WSO2, Inc.: http://wso2.com >>>> lean. enterprise. middleware >>>> >>>> web: http://udaraliyanage.wordpress.com >>>> phone: +94 71 443 6897 >>>> >>> >>> >>> >>> -- >>> Ajith Vitharana. >>> >>> WSO2 Inc. - http://wso2.com >>> Email : [email protected] >>> Blog : http://vitharana.org >>> Mobile : +1-812-360-5335 >>> >>> >> >> >> -- >> >> Udara Liyanage >> Software Engineer >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> web: http://udaraliyanage.wordpress.com >> phone: +94 71 443 6897 >> > > > -- > *Amila De Silva* > > WSO2 Inc. > mobile :(+94) 775119302 > > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Malintha Adikari* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile: +94 71 2312958 Blog: http://malinthas.blogspot.com Page: http://about.me/malintha
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
