By the way, I had to give http://192.168.11.65:8000/BizBrainTally/api
<http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/%7Bcompany%7D>
as
the end point and not http://192.168.11.65:8000/BizB
rainTally/api/ledgers/customers/
<http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/%7Bcompany%7D>
This allowed the call to succeed but the clicking the test button showed
failed


On Thu, Aug 3, 2017 at 1:29 PM, Sagar Kapadia <[email protected]> wrote:

> Thanks Rasika,
> Thanks, I got it working.
>
> On Thu, Aug 3, 2017 at 1:18 PM, Rasika Perera <[email protected]> wrote:
>
>> Hi Sagara,
>>
>> I think you are confused with API endpoint and the resource paths. Please
>> refer [1] as an example. Path parameters are not allowed for the
>> "Production EndPoint".
>>
>> *Your resource path should be:*
>> /{Company}
>>
>> *Your endpoint should be : *
>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/
>> <http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/%7Bcompany%7D>
>>
>> You can also try "/customers/{Company}" as resource path and "
>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/"; as the endpoint
>> too. This depends on the granularity and resource paths of the API that
>> you are hoping to expose through WSO2 API Manager.
>>
>> [1] https://docs.wso2.com/display/AM210/Create+and+Publish+an+API
>>
>> On Thu, Aug 3, 2017 at 1:05 PM, Sagar Kapadia <[email protected]> wrote:
>>
>>> Hi Rasika and Abimaran,
>>>
>>> I am accepting a parameter on the front end rest api. Now I need to pass
>>> this parameter to the implementing api. How do I do that.
>>>
>>> The following is the implementing api
>>>
>>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/{company}
>>>
>>> But adding {company} causes the test to fail with invalid message, and
>>> if I remove {company}, I get a 404 Error from the implementing server.
>>>
>>> The test succeeds if I put the following url
>>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/Test
>>> where "Test" is the parameter
>>>
>>> I am attaching screen shots to show what I mean.
>>>
>>> Sagar
>>>
>>> On Thu, Aug 3, 2017 at 12:37 PM, Sagar Kapadia <[email protected]>
>>> wrote:
>>>
>>>> Hi Rasika!
>>>> Thanks for your reply. I checked via ipconfig and its my IP. sorry for
>>>> the confusion. I have two ips. Now the next question is how to pass
>>>> parameters to the implementation endpoint. Or at least, if I can log the
>>>> request being made to the end point it would be very helpful, since I am
>>>> not getting any response from the server, but if I call the end point from
>>>> the browser, I get a valid response
>>>> Sagar
>>>>
>>>> On Thu, Aug 3, 2017 at 11:59 AM, Rasika Perera <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi Sagar,
>>>>>
>>>>> Are you using VMware or virtualbox? Please check your network
>>>>> interfaces. Sometimes WSO2 Server could have binded into a wrong network
>>>>> interface when there are multiple network interfaces in the host machine.
>>>>>
>>>>> You can check this with ifconfig(in linux) or ipconfig(in windows).
>>>>>
>>>>> Best Regards,
>>>>> Rasika
>>>>>
>>>>> On Wed, Aug 2, 2017 at 8:28 PM, Sagar Kapadia <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Abimaran,
>>>>>> Actually, API manager is running on 192.168.11.68 and not 192.168.144.2.
>>>>>> I am making a call to API manager via the swagger definition in the api
>>>>>> store. However, the end point doesnt get hit because it is pointing to 
>>>>>> the
>>>>>> wrong url [192.168.144.2.] instead of 192.168.11.65
>>>>>> Sagar
>>>>>>
>>>>>> On Wed, Aug 2, 2017 at 6:15 PM, Abimaran Kugathasan <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Hi Sagar,
>>>>>>>
>>>>>>> API Manager runs on 192.168.144.2 and this IP is shown in Store UI.
>>>>>>> If you want to hit the backend directly from your client, then there 
>>>>>>> isn't
>>>>>>> any reason for using API Manager. I don't understand why you are 
>>>>>>> expecting
>>>>>>> to hit backend URL directly. API Manager function as a proxy to route 
>>>>>>> the
>>>>>>> request to the backend which runs on 192.168.11.65.
>>>>>>>
>>>>>>> There can be many reasons not receiving a response, this might help
>>>>>>> you on this [1]. Also, You can try using cURL.
>>>>>>>
>>>>>>> [1]: http://blog.lakmali.com/2014/11/troubleshooting-issues-
>>>>>>> with-swagger-in.html
>>>>>>>
>>>>>>> On Wed, Aug 2, 2017 at 5:15 PM, Sagar Kapadia <[email protected]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Thuistha,
>>>>>>>> Thanks for your quick response. I had followed the tutorial below.
>>>>>>>> My problem is my pc has ip 192.168.11.68 and not 192.168.144.2.
>>>>>>>> when I try to call the api from the api store page via it's swagger
>>>>>>>> definition ,there is a call to my server but, i get no response from 
>>>>>>>> the
>>>>>>>> server. I believe the reason is that the implementation url of the api
>>>>>>>> points to an invalid ip (192.168.144.2), instead of the ip i
>>>>>>>> specified in production and sandbox url.
>>>>>>>> This is my confusion.
>>>>>>>> Sagar
>>>>>>>>
>>>>>>>> On Aug 2, 2017 4:24 PM, "Thusitha Thilina Dayaratne" <
>>>>>>>> [email protected]> wrote:
>>>>>>>>
>>>>>>>>> Hi Sagar,
>>>>>>>>>
>>>>>>>>> 192.168.144.2 is the IP address of your APIM running instance and
>>>>>>>>> 8280 is the port which exposes your API through the API manager. When 
>>>>>>>>> you
>>>>>>>>> invoke the http://192.168.144.2:8280/<context>/<api>/<resource>
>>>>>>>>> it will be sent to the production endpoint that you configured 
>>>>>>>>> through the
>>>>>>>>> UI.
>>>>>>>>>
>>>>>>>>> You can refer to APIM Docs[1] for more details
>>>>>>>>>
>>>>>>>>> [1] - https://docs.wso2.com/display/AM210/Create+and+Publish+an+
>>>>>>>>> API
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Aug 2, 2017 at 4:19 PM, Sagar Kapadia <[email protected]>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Aug 2, 2017 at 4:18 PM, Sagar Kapadia <[email protected]
>>>>>>>>>> > wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>> I tried to create an API in the API manager. Everything is ok,
>>>>>>>>>>> except for the fact that the end point ip anddress and port in the
>>>>>>>>>>> implementation page are ignored. I get the following ip address and 
>>>>>>>>>>> port
>>>>>>>>>>> 192.168.144.2:8280
>>>>>>>>>>>
>>>>>>>>>>> The screen shots show the issue
>>>>>>>>>>> Sagar
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Dev mailing list
>>>>>>>>>> [email protected]
>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thusitha Dayaratne
>>>>>>>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>>>>>>>
>>>>>>>>> Mobile  +94712756809 <+94%2071%20275%206809>
>>>>>>>>> Blog      alokayasoya.blogspot.com
>>>>>>>>> About    http://about.me/thusithathilina
>>>>>>>>> <http://wso2.com/signature>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Dev mailing list
>>>>>>>> [email protected]
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks
>>>>>>> Abimaran Kugathasan
>>>>>>> Senior Software Engineer - API Technologies
>>>>>>>
>>>>>>> Email : [email protected]
>>>>>>> Mobile : +94 773922820 <+94%2077%20392%202820>
>>>>>>>
>>>>>>> <http://stackoverflow.com/users/515034>
>>>>>>> <http://lk.linkedin.com/in/abimaran>
>>>>>>> <http://www.lkabimaran.blogspot.com/>
>>>>>>> <https://github.com/abimarank>  <https://twitter.com/abimaran>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Dev mailing list
>>>>>> [email protected]
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> With Regards,
>>>>>
>>>>> *Rasika Perera*
>>>>> Senior Software Engineer
>>>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>>>
>>>>> <http://wso2.com/signature>
>>>>>
>>>>> WSO2 Inc. www.wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Senior Software Engineer
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> <http://wso2.com/signature>
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to