How to Intergrate? about product-apim HOT 10 CLOSED

Guys, Need help. Any pointers?

from product-apim.

Hi,
Have you tried out the official documentation for API Manager? see https://docs.wso2.com/display/AM1100/WSO2+API+Manager+Documentation. You could try out the tutorials as well in https://docs.wso2.com/display/AM200/Tutorials . In these tutorial https://docs.wso2.com/display/AM200/Create+and+Publish+an+API describes basics thing on how to expose a backend web service (in your case RESTful web service) using api manager. You could start from this tutorials first. Then you could dive in to more advanced stuff

Default WSO2 API manager provides OAuth token based authentication mechanism for rest apis. To Provide RBAC you can use scopes. This article (This is written for AM 1.9.1 but applicable for all API manager versions) http://wso2.com/library/articles/2015/12/article-role-based-access-control-for-apis-exposed-via-wso2-api-manager-using-oauth-2.0-scopes/ provides a sample on how to use scopes for access control mechanism.

Regarding Databases, Default API manager uses H2 database. but you can configure Mysql, Postgres , Oracle, mssql, databases as well. All the database scripts can be found in the pack. You could read about that in https://docs.wso2.com/display/AM200/Working+with+Databases. API manager database has user and permission related data, api related data, analytic data etc.

So I think you should go through the official API manger document and the tutorials first. that would help you to get some understanding of the product

Regards
Chamila

from product-apim.

Thank your for the link. I have read them.

I am getting it working if I deploy the WSO2 API gateway and our rest service inside the same WSO2 webserver (carbon, looks like this can be changed to Tomcat, Can this be changed to JETTY too ??)

But, my aim was to run the API gateway and my REST Service separate. The API gateway can just route the request to different REST Servers. For example say for URL1 go to REST Server 1, and for URL2 go to REST Server 2 etc. Is this supported? I am sure this must be. Could you please share some info on this topic, please.

Thanks a ton in advance.

Regards, Santos

from product-apim.

This is what I have tried till now. Not able to route the request via ws02 gateway yet.

Step1:

I have created a sample REST web service with below URL

http://172.16.241.3:8080/Jersey-Spring-Hibernate/rest/bookservice/getallbook ==> Gets list of books from SQL DB.

Step2:

I have copied this war file to below path

/home/santos/afn_asap/wso2am-2.0.0/repository/deployment/server/webapps/mywar.war?

Step3:
Created and published the new API.I have configured the API with below details. Need to validate this. Rest of the configuration looks straightforward.

1. Remote end point:

/home/santos/afn_asap/wso2am-2.0.0/repository/deployment/server/webapps/mywar.war?

1. Used only HTTP now.

Step3:
After subscribing for the API the request is sent with following parameters from the API manger console.

curl -X GET --header 'Accept: json' --header 'Authorization: Bearer ' 'http://172.16.241.3:9443/Jersey-Spring-Hibernate/rest/bookservice/getallbook/1.00/*'

Questions:

Couple of things looks wrong in the request. Need to figure out the root cause for the same.

a. 9443 looks to be HTTPS port. Default port for HTTP is 9763. I have created/published the API only with HTTP not sure why it sends HTTPS port.

b. The version gets appended in the URL. How to remove this.

I tried the same request from POSTMAN client with port 9763 which is the default HTTP port and it works.
URI from postman:
http://172.16.241.3:9763/Jersey-Spring-Hibernate/rest/bookservice/getallbook

Please let me know how to debug this ?
Or any logs you need to trouble shoot.

Kindly let me know.

Thanks.
Santos

from product-apim.

Hi,

Can you post this question in stackoverflow please? This way you could reach out to more people regarding your issue. Please tag with 'wso2-am'.

Regarding the questions

1. Your remote endpoint is wrong. you have pointed to a file location as the remote endpoint. set it to http://172.16.241.3:9763/Jersey-Spring-Hibernate/rest/bookservice/getallbook .

When an API is fronted by API manager gateway, all the request should come to port 8243 or 8280. 9443 and 9763 are to access the web service directly. When you use the postman you are directly accessing the backend (http://172.16.241.3:9763/Jersey-Spring-Hibernate/rest/bookservice/getallbook )

To get the correct url. go to api store and go to the Overview section. It shows the correct url (ex http://172.17.0.1:8280/pizzashack/1.0.0)

If you want to remove the version from the url, there is a tick 'Make this the Default Version' you have to enable when creating the api. This is in the 'Manage' tab when creating the API in the publisher.

You can use wirelogs to debug the requests going in and out from the api manager. see http://mytecheye.blogspot.com/2013/09/wso2-esb-all-about-wire-logs.html. This method is applicable for API manager as well.

Again, Please use stackoverflow. :)

Regards
Chamila

from product-apim.

Thank you @chamilaadhi for your reply. As you might have seen I have started using stackoverflow now.

We tried few things but not able to route the request via gateway yet.

I can see some request logs in the gateway but it is not getting response from the production URL. One thing we suspect is our end URL is not secured. PLEASE LET ME KNOW IF THIS NEEDS TO BE ? I will generate the certificates and see if it helps. But, I am thinking I am missing somethings.

Configuration:

There are two URL's generated when the API is published. One for HTTPS & other for HTTP.

Gateway URL:
https://172.16.241.3:8243/Jersey-Spring-Hibernate/v1/rest/bookservice/getAllbook
http://172.16.241.3:8280/Jersey-Spring-Hibernate/v1/rest/bookservice/getAllbook

REST server URL
http://172.16.241.3:9763/ Jersey-Spring-Hibernate/v1/rest/bookservice/getAllbook

I tried with both HTTP & HTTPS gateway URL. Other option need to try is to enable the certificates for REST server so that end to end is secured.

I will post this question in stackoverflow to see if I get response. But, I would request if you could kindly quickly help me out in case you think what could be the problem.

Note: I will keep hunting the google & other open forums to figure out the gateway configuration issue.

Please let me know if you need any logs/configurations to debug this.

Thank you for your time.

Thanks
Santos

from product-apim.

I do not think it is related to certificate issue because your rest api is also hosted as a web app in API manager.
Enable wirelogs as mentioned in http://mytecheye.blogspot.com/2013/09/wso2-esb-all-about-wire-logs.html and do a request and attach the wirelog please.

from product-apim.

Thank you @chamilaadhi .

It’s working now. Request is routed via gateway. Please accept my since thanks for the support.

Tested with CURL commands. Both HTTP & HTTPS is working.

Issues:
There were couple of issues in the setup

1. Remote end point should end at the context.
   http://172.16.241.3:9763/Jersey-Spring-Hibernate/v1 --> correct
   http://172.16.241.3:9763/Jersey-Spring-Hibernate/v1/rest/ rest/bookservice/getAllbook
2. In the curl command the content type needs to be specified as JSON.

This one with direct access(will not be exposed to client)
curl -i -X GET -s "http://172.16.241.3:9763/Jersey-Spring-Hibernate/v1/rest/bookservice/getallbook"

This one works-->with http
curl --insecure -i -v -X GET --header 'Accept: application/json' --header 'Authorization: Bearer 83afd809-a1f0-31e1-b905-49b455bce7d9' 'http://172.16.241.3:8280/Jersey-Spring-Hibernate/v1/rest/bookservice/getallbook'

THis one works with https
curl --insecure -i -v -X GET --header 'Accept: application/json' --header 'Authorization: Bearer 83afd809-a1f0-31e1-b905-49b455bce7d9' 'https://172.16.241.3:8243/Jersey-Spring-Hibernate/v1/rest/bookservice/getallbook'

Having some issues with POSTMAN. I am figuring this out.

Also, do you know what should I do when my REST Server is not co-hosted. If you have any pointers kindly share.

Thank you.

Regards, Santos

from product-apim.

@chamilaadhi - What I feel deploying a REST Server outside should work. I am going to set this up and try. Is there anything difference ?

I guess, I can deploy the rest server in anywhere in the network and give the corresponding the URI when API is published.

Let us assume API gateway is running in 172.16.241.3. Production URI can be:

http://172.16.241.5/Jersey-Spring-Hibernate/v1

Need try this setup in our local lab. This will listen on the default HTTP port 8080.

Is this okay or anything else, I should be worried of?

Please let me know.

Thanks, Santos

from product-apim.

Please raise more concerns on [email protected].

from product-apim.